Colocate content and assets with Hugo leaf page bundles
Keep images and Markdown together in a Hugo leaf bundle so pages stay portable and assets publish reliably.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Keep images and Markdown together in a Hugo leaf bundle so pages stay portable and assets publish reliably.
Stop overloading your tags. Learn how to use Hugo's custom taxonomies to create structured classification systems like 'Series' or 'Difficulty' for better content organization.
Decide between Hugo Modules and traditional themes: compare versioning, overrides, and CI caching. Follow a step‑by‑step guide to set up modules, validate builds, and migrate legacy sites.
Hard-coded image URLs in static/ break when baseURL or language settings change. Model post images as Hugo page resources in leaf bundles so Hugo generates portable URLs and you gain image-processing control.
Learn how to implement custom taxonomies in Hugo to organize content beyond simple tags and categories, including configuration and template logic.
Learn how Hugo Pipes let you compile SCSS, minify output, and add content‑based fingerprints for reliable caching—all inside your templates.
An architecture note on using Hugo page bundles and resource processing to build a marketing site with clear trust boundaries, reproducible builds, and co-located assets.
Hugo content bundles let you co-locate content with its assets and create hierarchical sections without extra configuration. This guide covers branch vs. leaf bundles, a worked documentation example, permalink gotchas, and when to adopt (or avoid) the pattern.
When a Markdown file under content/ disappears from your built site with no build error, it’s usually a filter, not a bug. This guide walks through the most common causes—drafts, dates, ignore patterns, template lookups—provides a diagnostic table, concrete commands, and when to raise the issue.