Collections

Overview

Collections are groups of related content. Each collection has its own directory under content/, URL prefix, and template. Five presets are available:

Defining Collections

Collections are configured in seite.toml:

[[collections]]
name = "posts"

[[collections]]
name = "docs"

[[collections]]
name = "pages"

Each preset comes with sensible defaults. You can override any field:

[[collections]]
name = "posts"
label = "Blog"
paginate = 10

Collection Fields

Posts

Posts are date-based content. Filenames should include the date:

content/posts/
├── 2026-01-15-hello-world.md
├── 2026-02-01-rust-tips.md
└── 2026-02-18-new-feature.md

The date is parsed from the filename (YYYY-MM-DD-slug.md) or from frontmatter. Posts are sorted by date (newest first) and included in the RSS feed.

Docs

Docs support nested directories for grouped navigation:

content/docs/
├── getting-started.md
├── guides/
│   ├── setup.md
│   └── advanced.md
└── reference/
    ├── api.md
    └── config.md

Nested docs get URLs like /docs/guides/setup. The docs theme shows a sidebar with sections grouped by directory.

Sidebar Ordering

By default, docs are sorted alphabetically by title. Use weight in frontmatter to control the order:

---
title: "Getting Started"
weight: 1
---

Lower values appear first. Items without weight sort alphabetically after all weighted items. This lets you create a guided learning path instead of a plain alphabetical list.

Pages

Pages are standalone content at root URLs. They're unlisted (not shown on the index page):

content/pages/
├── about.md        → /about
├── contact.md      → /contact
└── index.md        → / (homepage content)

The special file content/pages/index.md injects its content into the homepage template as {{ page.content }}.

Changelog

The changelog collection is for release notes and version history. Entries are date-based with RSS support, so users can subscribe to updates.

content/changelog/
├── 2026-01-15-v0-1-0.md
├── 2026-02-01-v0-2-0.md
└── 2026-02-18-v1-0-0.md

Use tags to categorize changes. Tags render as colored badges in the changelog templates:

• new — new features (green)
• fix — bug fixes (blue)
• breaking — breaking changes (red)
• improvement — enhancements (purple)
• deprecated — deprecations (gray)

seite new changelog "v1.0.0" --tags new,improvement

Roadmap

The roadmap collection is for sharing your project's public roadmap. Items are ordered by weight (not date) and grouped by status tags.

content/roadmap/
├── dark-mode.md
├── api-v2.md
└── initial-release.md

Use tags for status and weight for priority ordering within each group:

• planned — upcoming work
• in-progress — actively being worked on
• done — completed
• cancelled — no longer planned

---
title: "Dark Mode"
tags:
  - planned
weight: 1
---

Three index layouts are available. The default groups items by status. To switch layouts, create templates/roadmap-index.html:

{# Kanban board (3-column CSS grid): #}
{% extends "roadmap-kanban.html" %}

{# Or timeline (vertical milestones): #}
{% extends "roadmap-timeline.html" %}

seite new roadmap "Feature Name" --tags planned

Pagination

Enable pagination on any listed collection:

[[collections]]
name = "posts"
paginate = 10

This generates:

• /posts/ — page 1
• /posts/page/2/ — page 2
• /posts/page/3/ — page 3, etc.

Templates receive pagination context:

{{ pagination.current_page }}
{{ pagination.total_pages }}
{{ pagination.prev_url }}
{{ pagination.next_url }}

Singular/Plural

Both seite new post and seite new posts work — the CLI normalizes singular to plural automatically.

Tag Pages

Tags are collected from all posts and generate archive pages:

• /tags/ — tag index with all tags and counts
• /tags/rust/ — all posts tagged "rust"

Tag pages are i18n-aware and included in the sitemap.

Next Steps

• Configuration — full reference for all collection fields and site settings
• Templates & Themes — customize how collections are rendered
• Shortcodes — add rich content like videos, callouts, and figures to your pages