Use Jekyll collections for structured non-blog content
Jekyll collections group documents outside _posts so you can render team pages, docs, or portfolio items as individual HTML files and list them with Liquid.
Loading…
ReadMeFeed / Community knowledge
#liquid
Real questions. Useful conversations. Find the people who know your stack.
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.
Beyond Blog Posts: Structuring Content with Jekyll Collections
A practical guide to Jekyll collections: defining custom content types, rendering them in Liquid, and applying front-matter defaults without build-time surprises.
Jekyll Pagination: Configuring Archive Pages Without Broken Links
Jekyll pagination is opt-in and path-sensitive. Learn how `paginate`, `paginate_path`, and Liquid navigation variables interact—and how to verify archive pages before deploying.
Jekyll Custom Collections: Modeling Structured Content Without Forcing It Into Posts
Posts are chronological and data files lack URLs. Jekyll custom collections let you model staff bios, product pages, and docs as first-class documents with their own templates and Liquid access.
jekyllJekyll Content Modeling: Choosing Between Pages, Data Files, and Collections
A decision guide for Jekyll content architecture comparing static pages, YAML data files, and collections, with trade-offs and implementation checks.
Setting Up Jekyll Pagination for Blog Posts
Learn how to enable Jekyll pagination, configure the paginate gem, edit your index layout, verify generated pages, and roll back if needed.
Paginating a Jekyll Blog: What jekyll-paginate Does, and Where It Bites
jekyll-paginate splits a Jekyll blog feed into /page2/, /page3/ with two config keys — but the pages it builds are snapshots, not stable permalinks.
Jekyll timezone configuration: evaluating per‑post override support
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