Jekyll Front Matter Defaults: Share Metadata Across Pages
Stop repeating layout and permalink values in every Jekyll page. Learn how defaults in _config.yml inherit metadata, where shallow merging breaks, and how to verify the result.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Stop repeating layout and permalink values in every Jekyll page. Learn how defaults in _config.yml inherit metadata, where shallow merging breaks, and how to verify the result.
Eleventy merges global `_data` files, directory data files, and template front matter in a strict cascade. Learn how to verify the final data object and avoid silent overrides.
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.
A step‑by‑step guide to find why a Jekyll source file is silently skipped during build, covering front‑matter, dates, excludes, and permalink issues.
Eleventy’s data cascade lets you write shared values once in global, directory, or template data files, eliminating repetitive front‑matter and simplifying site maintenance. This guide walks through a concrete example, explains merge rules, and highlights trade‑offs.
Learn how to spot and fix Jekyll build failures caused by malformed front‑matter YAML, with a step‑by‑step diagnostic flow, fixes, and verification steps.
Learn how to diagnose missing or overridden data in Eleventy by checking the data cascade, merge behavior, and async resolution, with concrete checks and fixes.
Goal: decide whether to use Eleventy’s built‑in front‑matter pagination or to generate paginated pages programmatically from a custom collection in .eleventy.js for a blog that needs clean URLs and reliable template aliasing. Constraints: the front‑matter approach is declarative and works with any data source, but it hides the page‑creation logic; the custom
Integrating Custom Taxonomies with Dynamic Content Hugo allows the definition of custom taxonomies in the configuration file to group content beyond standard tags and categories. When scaling a site with numerous domain-specific groupings, the relationship between front matter arrays and the generated taxonomy pages becomes critical for build performance and