Learn by building
Tutorials
Step-by-step lessons that introduce the framework by building a real site.
Framework documentation
Rust-First Site Toolkit
A Rust-first static site generator where routes, markdown rendering, assets, and build behavior stay explicit. This site is also the dogfooding app for the framework itself.
Solve one concrete task
Cookbooks
Task-oriented recipes for routes, frontmatter, media, and non-HTML outputs.
Look up exact behavior
Reference
Precise API behavior, route semantics, and public types for site authors.
Understand the design
Explanation
Architecture notes that explain why the engine is shaped the way it is.
Start here
A docs site organized by intent
First stops
The best entry points are a tutorial, one focused recipe, the API reference, and an architecture note that explains the execution model.
Getting started
Understand the workspace layout, the site program, and the build flow before changing code.
Build paginated sitemaps
Use generated route families and the pagination helper to emit a sitemap index plus many sitemap pages.
Site-building API
Reference for the main builder methods, context types, route metadata, artifacts, and asset requests.
Architecture
Understand the workspace split, rendering model, asset pipeline, and incremental build strategy.
Latest release note
The sample app is now the documentation site
The repository’s sample site now serves as the framework documentation site and exercises the public API directly.
- The site is now organized around tutorials, cookbooks, reference, explanation, blog, and release notes.
- The documentation content lives under content/ and is rendered by the same framework it documents.
- The site crate was refactored into smaller route modules to keep the application code legible.
Engineering journal
From the blog
2026-03-30
Build Reports Make Incremental Work Visible
The build report API exposes which routes and assets were emitted, skipped, restored, or removed so incremental behavior is observable instead of mysterious.
2026-03-30
Flat Files, Artifact Kinds, and Page Output Policy
Route shape, artifact semantics, and page output policy are separate decisions so the site can emit pages, XML, JSON, and literal flat files without awkward special cases.