Blog as a First-Class Surface#
When blog content keeps getting rebuilt in every new codebase, the pattern is clear: it belongs in the library.
Why make it a sibling to docs?#
The docs system already solved several hard problems:
- content in the repo
- locale-aware routing
- prerender-friendly metadata
- a shared MDX rendering pipeline
The blog feature should reuse those same decisions instead of creating a second content stack with slightly different rules.
The goal is not to turn blog posts into docs pages. The goal is to give both surfaces the same reliable content and rendering foundation.
What changes for consumers?#
Consumers now get a dedicated blog source, reusable directory and detail pages, and a default route model that matches the docs package philosophy.
That means the example site can show:
- a directory page
- a detail page
- categories and search
- suggested posts without custom glue code
What stays flexible?#
The library stays intentionally narrow. Consumers still choose the surrounding shell, the page copy, and any extra marketing chrome around the blog surface.
