Where to Find Eleventy Documentation, Tutorials, and Community Resources

Updated

The official Eleventy site (11ty.dev) is the single entry point for everything: the Get Started and Quick Start pages cover installation and your first file, the Guide section holds the full reference documentation, and Starter Projects, Tutorials, and Community pages cover learning and support. If you only need one thing, start at the Quick Start on the homepage — it tells you to install Node.js (version 18 or newer), verify it with node --version, then create an index.md file.

Documentation: where each part lives

The site organizes docs into a few distinct areas, and knowing which one you want saves time:

Section What it covers
Get Started / Quick Start Installing Node.js, creating your first Markdown file, running the build
Guide The full reference: configuration, templates, data, plugins, deployment
Learn Glossary, "Opening a Terminal," "Installing JavaScript," and background concepts
Advanced Programmatic API, configuration events, order of operations
Common Pitfalls Known traps to check before you debug from scratch

The Guide is the largest section and is where most reference questions land. Its subsections include Command Line Usage, Add a Configuration File, Copy Files to Output, Importing Content, Permalinks, Layouts, Collections, Pagination, and Using Data in Templates. There is also a dedicated Template Languages area covering HTML, Markdown, MDX, JavaScript, JSX, TypeScript, WebC, Nunjucks, Liquid, Handlebars, Mustache, EJS, HAML, Pug, and Sass — so you can check support for your preferred language before committing to it.

Version information

The site lists Stable 3.1.6 and Canary 4.0.0-alpha.10. If you are starting a new project, the stable release is the one the documentation is written against; the canary build is for testing upcoming changes.

Tutorials and starter projects

Two separate resources serve different needs:

  • Starter Projects — pre-built project scaffolds you can clone and modify. Useful when you want a working site structure rather than a blank directory.
  • Tutorials — step-by-step walkthroughs. Useful when you want to understand each piece as you build it.

There is also Try Eleventy in Your Browser, which lets you evaluate the tool without installing anything locally. That is the fastest way to decide whether the template syntax suits you before setting up Node.js.

The Quick Tips page sits alongside these and collects shorter, task-specific guidance.

Community and events

The Community section links to several ongoing resources:

  • Blog and Firehose — announcements and a stream of Eleventy-related posts
  • 11ty Bundle — a curated collection of Eleventy resources
  • Leaderboards — contributor activity
  • Eleventy Meetup — a recurring community meetup
  • 11ty Conference — a dedicated conference

There is also a How can I contribute? page and a Code of Conduct if you want to participate rather than just read.

Plugins, services, and deployment

Beyond core docs, the site documents an ecosystem:

Official plugins include Image, Fetch, Render, Internationalization (i18n), Upgrade Helper, RSS, Syntax Highlighting, InputPath to URL, Navigation, and HTML Bundle Id Attribute. There is also a Community Plugins listing and a Retired Plugins page, which is worth checking before adopting an older plugin.

Services covers Deployment & Hosting, Using a CMS, Runtime APIs, Screenshots, OpenGraph Image, IndieWeb Avatar Generator, Image Hosting, and Image Sparklines.

The Upgrade Helper plugin is specifically relevant if you are moving an existing project between major versions — check it before upgrading rather than after.

A practical path through the site

If you are new, this order avoids backtracking:

  1. Try Eleventy in Your Browser — confirm the workflow fits how you think.
  2. Quick Start — install Node.js 18+, create index.md, run the build.
  3. Starter Projects — pick a scaffold instead of building structure by hand.
  4. Tutorials — work through one end to end.
  5. Guide — return here for reference as specific needs come up (collections, pagination, data cascade).
  6. Common Pitfalls — read before filing a bug report.

For a specific decision — which template language, whether to use a CMS, where to host — the relevant Guide or Services page is the authoritative source, since these choices depend on your existing stack rather than on a single recommendation.