Pipeline-enhanced front matter
Site Pipeline preserves authored page metadata and adds a reserved, normalized namespace that renderers can use without reconstructing publication context.
Concepts
Use this section when you want the Site Pipeline mental model before diving into procedures or contracts.
These pages explain what the pipeline owns, what a minimal site looks like, and how authored inputs become a staged output that renderers and deployment adapters can consume safely.
Start here
- Tiny site shape for the first concrete repository and catalog shape
- Pipeline-enhanced front matter for the boundary between authored metadata and pipeline-owned publication context
- Staged output and consumers for the manifest, staged front matter, and aggregate-data boundary
Read next
- Tiny getting started for the smallest supported onboarding path
- Create a tiny site for the first copy-pasteable setup
- Unreleased development staged-output contract for the detailed downstream contract
What a tiny site looks like
This page shows the smallest concrete example thread used across the user-facing docs.
Staged output and consumers
The staged tree is the durable hand-off point between Site Pipeline and the systems that render, serve, or audit the site.