Using Jekyll Collections to Organize Custom Content Types
Learn how to create and use Jekyll Collections for custom content types, from configuration to Liquid rendering and verification steps.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to create and use Jekyll Collections for custom content types, from configuration to Liquid rendering and verification steps.
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.
Learn how to separate site state from presentation in Jekyll using the _data directory and Liquid templating to reduce maintenance and improve build security.
Learn how to decouple navigation and reusable components in Jekyll using data files and Liquid includes for easier updates and cleaner templates.
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.
Compare Jekyll's built-in paginate with jekyll-paginate-v2 for 500+ posts. Core only paginates the main index; v2 adds category/tag/collection pagination, trail links, and JSON output but multiplies output files ~5× and needs GitHub Actions. Includes config, layout, and verification steps.
Stop forcing everything into _posts. Learn how to use Jekyll Collections to create structured, custom content types like project portfolios or staff directories.
Learn how to diagnose and fix missing content in Jekyll Collections, from naming mismatches in _config.yml to missing YAML front matter and Liquid syntax errors.
Stop forcing non-chronological data into _posts. Learn how to use Jekyll Collections to create structured content types like team directories or product catalogs.