Project File Structure

Master the HugoBlox project structure. Learn where to place content, assets, config files, and templates for optimal site organization.

Understanding the folder structure is key to mastering HugoBlox.

Project Root

.github/ # GitHub's workflow to automatically deploy your site

media/ # Images, icons, and videos

css/ # Any custom styles

_default/ # Configuration files (hugo.yaml, params.yaml)

content/ # Your markdown content

authors/ # Author profiles (YAML files, e.g., jane-doe.yaml)

layouts/ # Any custom HTML overrides

static/ # Static files served as-is (CNAME)

hugoblox.yaml # HugoBlox template metadata

go.mod # List of installed Hugo modules

netlify.toml # If you host your site with Netlify

Directory	Description
`content/`	Where you write your posts, pages, and publications. This mirrors your site's URL structure.
`assets/`	Assets processed by Hugo (Images, Videos, Custom Styles).
`static/`	Files copied directly to the `public/` folder without processing. Useful for SEO verification files.
`config/`	Site settings. Split into multiple files for better organization (`params.yaml`, `menus.yaml`).
`layouts/`	Used to override built-in layouts or create custom blocks/hooks.

Hugo File Naming:

_index.md: Represents a section (folder) homepage/listing.
index.md: Represents a Leaf Bundle (a page with its own folder and resources).