Public Content System

Keep the public surface simple and indexable.

In this starter

• Markdown pages are registered in one content catalog.
• Each page gets a stable route under /guides.
• The server renders those pages for sharing, SEO, and fast first paint.

Why split public content from the app shell?

• Marketing and docs can evolve without dragging app state into every route.
• The authenticated app can change faster than the public website.
• It keeps the codebase honest about what must work without login.

What to replace

• The example guide pages with your own acquisition, help, onboarding, or product education content.