Content Organization

Pages, sections, and bundles explained

3 pages in this section

Your folder structure becomes your site structure. No configuration required.

The Three Content Types

flowchart TB subgraph "Your Files" A["📄 about.md"] B["📁 blog/_index.md"] C["📦 gallery/index.md"] end subgraph "Your Site" D["/about/"] E["/blog/ + children"] F["/gallery/ + assets"] end A --> D B --> E C --> F

A single.mdfile → a single HTML page.

content/
└── about.md  →  /about/

Use for: standalone pages like About, Contact, Privacy Policy.

A folder with_index.md→ a list page with children.

content/
└── blog/
    ├── _index.md     →  /blog/ (list page)
    ├── post-1.md     →  /blog/post-1/
    └── post-2.md     →  /blog/post-2/

Use for: blog posts, documentation chapters, any collection.

A folder withindex.md→ a page with co-located assets.

content/
└── gallery/
    ├── index.md      →  /gallery/
    ├── photo-1.jpg   (private to this page)
    └── photo-2.jpg   (private to this page)

Use for: pages with images, data files, or other assets.

Quick Reference

Pattern File Creates Assets
Page name.md Single page Usestatic/
Section name/_index.md List + children Usestatic/
Bundle name/index.md Single page Co-located

Tip

Key difference:_index.mdcreates a section (with children).index.mdcreates a bundle (with assets). The underscore matters!

Advanced: Nesting and Cascades

Sections can nest to any depth:

docs/
├── _index.md
├── getting-started/
│   ├── _index.md
│   └── installation.md
└── advanced/
    ├── _index.md
    └── plugins.md

Configuration cascades from parent to children:

1
2
3
4
5
6
---
title: Docs
cascade:
  type: doc
  toc: true
---

All pages underdocs/inherittype: docandtoc: trueunless they override it.

In This Section