I want to try it today
Start with getting started, then keep feature overview open while comparing the generated output to sample-site.
Documentation Map
Use the docs pages for orientation and setup, then move into the blog for deeper writing on features, configuration, CLI workflows, and AI-powered localization.
These pages are the fastest route from zero context to a successful local run.
Project identity, current capability range, and recommended reading paths.
Run sample-site or docs locally and inspect the generated output.
Publish the docs folder or align a workflow around the generated site.
See the implemented, partial, and intentionally out-of-scope areas.
The blog now carries the detailed documentation.
The end-to-end handbook from setup and preview to release and troubleshooting.
Rendering, publishing semantics, filters, pagination, and site-building behavior.
Site options, defaults, include or exclude rules, footer metadata, analytics, and pagination config.
Build, watch, serve, dotnet tool packaging, GitHub Actions, and local preview.
Locales, translation links, provider selection, cache, incremental translation, and glossary.
A fast route based on team role or delivery phase.
Different contributors usually start with different questions.
Start with getting started, then keep feature overview open while comparing the generated output to sample-site.
Read compatibility first, then move to the feature overview and configuration guide for the details behind that matrix.
Read the AI translation article and inspect how the docs folder mirrors English and Chinese routes.
If you want to understand the current maturity quickly, read these next.