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
Running Eleventy?
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.
What it is
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.
The honest version
No technology is all upside. This is where Eleventy (11ty) earns its place and where it tends to cause trouble.
Sound familiar?
The Eleventy (11ty) problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Fix one broken build, or let us build the whole 11ty site with you.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: