Running Eleventy?

Eleventy build broken or data cascade confusing? We sort it out.

Eleventy is small enough that most problems are fixable in one sitting, and that is usually when the team wants someone who already knows where the sharp edges are. Data cascade order, template language choice, image plugins and deploy configuration cover most of the calls we get. We fix it and leave the site faster than we found it.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

eleventy-build.log

still broken

What it is

Eleventy (11ty) at a glance

Eleventy, usually written 11ty, is a static site generator written in JavaScript by Zach Leatherman, first released in 2018. It produces HTML from templates and data without shipping a JavaScript framework to the browser, which keeps the output small and fast by default.

It supports many template languages in one project, including Nunjucks, Liquid, Markdown, Handlebars, JavaScript and WebC. Data can come from front matter, directory data files, computed data or remote APIs through the data cascade, which is the feature Eleventy is both admired and quietly feared for. Version 3, released in 2024, moved to an ESM first design. It is often chosen for marketing sites, technical documentation and blogs where the JavaScript bundle of a React based generator is unwelcome.

Type
JavaScript static site generator
First released
2018, 1.0 in January 2022, 3.0 in September 2024
License
MIT, open source
Maintained by
Zach Leatherman and contributors
Typically used for
Marketing sites, documentation, blogs, personal sites, anywhere the JS bundle of a framework is unwanted

The honest version

Eleventy (11ty) pros and cons

No technology is all upside. This is where Eleventy (11ty) earns its place and where it tends to cause trouble.

Where Eleventy (11ty) is strong

  • Zero JavaScript by defaultThe output is HTML and CSS with whatever scripts you actually choose to write. No framework runtime ships to the browser, which is terrific for performance and accessibility.
  • Multiple template languagesNunjucks, Liquid, Markdown, Handlebars, JavaScript and WebC can be mixed in one project, which makes migrating an existing content source much easier than a single language generator.
  • Powerful data cascadeDirectory data files, computed data, remote data and front matter merge in a predictable order, which lets content authors and engineers keep data close to where it is actually used.
  • Fast enough for most sitesA few hundred pages build in seconds on a laptop. Builds slow down at serious scale but most sites never reach that scale.
  • Small surface areaThe core API is small, the documentation is honest, and most of the project can be understood by reading it end to end in an afternoon.
  • Great community of practiceThe 11ty starter set, Image plugin, Bundle plugin and community posts cover almost every common need without a plugin store ecosystem.

Where Eleventy (11ty) bites

  • The data cascade confuses newcomersSix layers of data merging in a specific order is powerful and unforgiving. Figuring out which layer set a particular value is a skill that takes time, and until it is learned the build can feel magical.
  • No bundled client frameworkInteractive components need to be added by hand or via Alpine, htmx or Islands patterns. For sites with genuinely dynamic UI this is more work than Next.js would be.
  • Build times climb at large scaleA few thousand pages with heavy image processing can push builds past ten minutes, and the incremental build story is better in version 3 but still needs tuning.
  • Plugin ecosystem is thin by framework standardsMost problems have a documented plugin or a short script, but there is no vast Gatsby or Next.js style marketplace. Expect to write small amounts of glue code.
  • ESM migration still bitesVersion 3 moved to ESM first, which caught some plugins and some older projects off guard. Mixing CommonJS and ESM in config and data files has footguns.
  • Hiring is nicheDevelopers who know 11ty specifically are a smaller pool than React developers. The upside is that the generator is small enough to learn in a week for anyone who knows JavaScript.

Sound familiar?

Common Eleventy (11ty) problems we fix

The Eleventy (11ty) problems that bring people to us, and what you have once each one is fixed.

pagination.data points to posts, which has 0 items

Pagination silently generates nothing

A data source that is empty at build time because a glob did not match, a filter removed everything, or the data file lives in a directory the cascade is not reading.

Pagination fed from the right data

ReferenceError: title is not defined

Templates break after a data refactor

A template that assumed a front matter field exists on every page breaks on one page that forgot to set it, and the whole build fails at that file.

Templates defensive, data complete

Benchmark: 94.3s for 1284 templates

Builds getting slow

Image processing on every build, remote data fetched without a cache, or a global data file that recomputes a large tree every time the site builds.

Build back to seconds, not minutes

Shortcode 'image' errored

Image shortcodes failing

A missing image on disk, a remote URL that redirected or timed out, or an Eleventy Image plugin version that disagrees with the project configuration.

Image pipeline reliable in build

module '@11ty/eleventy-img' not found

Build fails after an upgrade

A version 2 to 3 upgrade that silently needed a different plugin major, or a package that is now ESM only while the config is still CommonJS.

Dependencies consistent across the project

Unknown block tag: endraw

Template language confusion in one file

A page written for Liquid being rendered as Nunjucks, or the other way round, because the extension or the templateEngineOverride got out of step with the content.

Templates rendered by the right engine

layout.njk not found

Layout references that do not resolve

A layout moved during a refactor without updating the front matter that referenced it, or a layouts directory that is not where Eleventy expects it to be.

Layout chain complete and documented

jekyll site, 1800 posts

Migration from Jekyll or Hugo

A team outgrowing a Ruby or Go generator, wanting to stay in JavaScript, with eight years of posts, categories and permalinks that cannot be broken in the move.

Live on 11ty with URLs preserved

What we do

Eleventy help, from fix to migration

Fix one broken build, or let us build the whole 11ty site with you.

Build rescue
Builds failing or silently producing the wrong output. We trace the specific template, data file or plugin and leave the build green.
New site builds
A new Eleventy site from an existing design, with a sensible content model, the image pipeline configured, deploys wired to Netlify, Cloudflare Pages or your host of choice.
Migrations
Moving a Jekyll, Hugo or Gatsby site onto Eleventy with URLs preserved, redirects set and content converted rather than rewritten by hand.
Performance
Images, fonts and critical CSS tuned so the Core Web Vitals scores reflect what Eleventy makes possible rather than what a default theme ships.
Upgrades
Eleventy 1 or 2 onto 3, including the ESM migration, plugin replacements and config refactors needed to land on the current major cleanly.
Managed Tech
Dependency updates tracked, builds monitored, deploys watched, and a human to call when a plugin release breaks the site on the next content push.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Eleventy (11ty) alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Eleventy (11ty) questions

Something else? Call+1 737 727 7327

Should we use Eleventy or Next.js?

Eleventy wins for content sites where speed, accessibility and simple hosting matter more than an interactive UI. Next.js wins for products with authenticated users, dashboards or heavy client side state. A lot of teams end up with both, Next.js for the app and Eleventy for the marketing site, which is often the right split.

Why does our Eleventy build keep breaking?

The common causes are a template expecting a front matter field that is missing on one page, a pagination data source that returned zero items after a filter change, or a plugin major that changed its API in an upgrade. Build breakage is usually a two line fix once the cause is clear, which the error message sometimes buries.

Can you migrate our Jekyll or Hugo site to Eleventy?

Yes, and the pattern is well worn. We carry the posts over keeping URLs identical, port the templates to Nunjucks or Liquid, rebuild the taxonomy pages in the data cascade, and add any shortcodes the old site relied on. Search engine rankings and existing links come through intact because the URLs do.

How do we make Eleventy builds faster on a large site?

Cache remote data between builds, run the Image plugin incrementally rather than from scratch each time, use the incremental build flag in Eleventy 3 for content only changes, and move heavy template work into computed data that caches. A site that built in six minutes can often land back under one.

Is Eleventy good for a documentation site?

Yes, and it is one of the most natural fits. Markdown first, reasonable defaults for navigation, and no JavaScript shipped unless you add it, which keeps the docs fast and crawlable. We will often pair it with Pagefind or a small search index and call it done.

How much does Eleventy help cost?

Estimates do not cost anything. Send the repo link or a description of the site and what is going wrong, and we return a written price before anyone opens an editor.

Free estimate

Eleventy giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.