ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #jekyll
Jekyll currently applies a single timezone—set via timezone in _config.yml or the TZ environment variable—to all dates parsed from front matter and formatted by the Liquid date filter. There is no built‑in way for an individual post or page to specify a different zone, and the project has not decided whether a front‑matter timezone: key should be honored. In
Jekyll Build Process Jekyll catches exceptions originating from plugins during the site generation phase. Build Continuation Behavior The default behavior allows the build to continue even after a plugin exception is logged. Does Jekyll inherently fail the entire build when a plugin throws an exception, or does it proceed with a potentially incomplete site?
Build Strategy for High-Volume Content Managing a Jekyll site with thousands of pages creates a significant trade-off between development velocity and output reliability. When utilizing jekyll build --incremental , the build time is reduced by regenerating only changed files, which is critical for maintaining a fast local feedback loop. However, the incremen
Jekyll utilizes a collection system to manage groups of documents, which are typically rendered via Liquid loops in the frontend templates. While this allows for flexible content organization, the resulting HTML output often defaults to flat lists of links or elements. To meet WCAG accessibility standards, complex navigation and content groupings require a n
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
A site is built with Jekyll 4.x locally and intended for deployment to GitHub Pages production. The goal is consistent asset and link generation across the two environments. The configuration involves site.url and site.baseurl for absolute and relative links, conditional content controlled by JEKYLL_ENV , and plugin availability. Local development often uses
When implementing pagination in Jekyll 4.x, there is a trade-off between the simplicity of the core jekyll-paginate plugin and the extended capabilities of jekyll-paginate-v2 . The core plugin is designed for a single pagination context, typically limited to the site's index page. In contrast, jekyll-paginate-v2 allows for multiple pagination contexts, enabl
Jekyll utilizes the exclude setting in _config.yml to prevent specific files, directories, or glob patterns from being copied into the final _site output folder. While files starting with an underscore are excluded by default, other sensitive environment files or custom data directories must be explicitly listed to avoid public exposure. A challenge arises w
Jekyll generates a static site by processing source files and Liquid templates into a destination directory, typically _site . This directory serves as the final production-ready output of the build pipeline. Because the build process is designed to reflect the current state of the source files and _config.yml settings, the destination folder is treated as e