Short answer
The built-in editorial starter shows how the template handles metadata, slugs, CMS migration, and long-form content.
Why the blog exists from day one
Most projects need editorial content sooner than expected. Shipping the route, slug, and metadata architecture up front keeps us from rebuilding the app once articles, updates, or resources arrive.
How this will connect to Sanity later
The starter uses the same view model for static content and CMS content. That means we can swap the source from local defaults to Sanity loaders without rewriting the page layout or section components.
Localization stays outside the section components
Resolved strings, links, and metadata should be prepared in loaders or route composition. Presentation components should stay focused on layout and visual behavior.
Key points
What the editorial system keeps aligned
Support blocks stay optional, structured, and editable without turning the article route into a one-off page.
Trust cards, FAQs, and CTAs map from plain Sanity fields.
Canonical metadata and article schema use the same post model.
Headings feed a keyboard-friendly table of contents.
Dates, labels, links, and shared content follow the active locale.
Frequently asked questions
Ready to turn the starter into your publication?
Use the existing article system, then replace the example content with your CMS records.