ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #eleventy
Eleventy’s pagination is a build-time loop declared in front matter. Here is how the size, alias, and permalink mechanics work, and what breaks when datasets grow.
Decide whether to keep Eleventy’s built‑in marked parser or switch to the markdown‑it plugin. This guide compares the two options, explains trade‑offs, and walks through a concrete implementation and validation steps.
Move navigation and blog metadata out of Eleventy templates into _data files. Use global files for site-wide variables and directory-scoped data for section-specific data to keep templates clean and content-driven.
Stop repeating layout and tag declarations in every Markdown file. Learn how the Eleventy Data Cascade merges global, directory, and template data to keep your project DRY.
Leverage Eleventy's collection-driven pagination to generate archive pages from a single template, with a concrete configuration and build-trade-off analysis.
A diagnostic guide for Eleventy pagination when templates produce missing, duplicated, or mislabeled pages. Covers data source, size/alias, and permalink checks with fixes and escalation criteria.
Eleventy's data cascade offers four practical layers for shared values. This guide compares global data, directory data, layout front matter, and page front matter, then shows a scratch project that proves the override order.
Eleventy's --incremental flag caches the dependency graph to rebuild only changed templates, cutting dev-server latency from seconds to milliseconds on large sites. Here's how it works, a hands-on verification, and the plugin caveats that can silently break it.
An architecture note on using Eleventy's data cascade (global data, directory data, front matter, computed data) as the minimal design for page data assembly, covering trust boundaries, failure modes, and operational verification steps.
jamstack