Diagnosing Slow Eleventy Builds Caused by Large Data Files and Excessive Includes
A step‑by‑step guide to spot whether big _data files or many template includes are slowing your Eleventy site, with checks, fixes, and when to escalate.
Loading…
ReadMeFeed / Community knowledge
#data-files
Real questions. Useful conversations. Find the people who know your stack.
eleventyDiagnosing Missing Global Data in Eleventy Templates
A diagnostic guide for when Eleventy global data files in _data don't appear in templates—covering recognizable symptoms, a cause table, ordered checks, targeted fixes, and escalation steps.
Using Jekyll Data Files and Includes to Build Maintainable Navigation
Learn how to decouple navigation and reusable components in Jekyll using data files and Liquid includes for easier updates and cleaner templates.
Decoupling Blog Logic with Eleventy Global and Directory Data
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.
jamstackData file cache limits: schema changes ignored
Goal Understand how Hugo’s data file cache behaves when the schema of a data file changes without a file-modification timestamp change, and whether this limitation can be addressed. Constraints Hugo caches parsed YAML, JSON, and TOML files in resources/_gen . The cache key is built from the file path and its last-modified timestamp. If the internal structure
hugoDoes Jekyll's incremental regeneration reliably rebuild pages after data file changes?
Goal: Verify if Jekyll’s incremental regeneration (enabled with --incremental ) reliably rebuilds every page that references a changed global data file ( _data/*.yaml ). Uncertainty: Although the .jekyll-metadata manifest marks data files as dependencies, some observers note that dependent pages are not regenerated after a data file edit, requiring a full re
jekyll