Marketing Routes
Marketing routes render public product, pricing, content, legal, contact, and team surfaces.
On this page
Route structure
| Sub-route | Purpose | Data source |
|---|---|---|
| / | Landing page with hero, features, pricing, FAQ, and calls to action. | Settings, billing catalog, published FAQ content, landing components. |
| /about, /pricing, /contact, /faq | Core marketing and lead-capture pages. | Marketing components, contact feature, billing config, published FAQ content. |
| /blog, /blog/[slug], /case-studies, /blog/case-studies/[slug] | Content marketing and case-study pages. | features/posts |
| /changelog, /changelog/[version]/[slug] | Public product updates. | features/posts |
| /team, /team/[id] | Public team directory. | features/team |
| /privacy, /terms, /disclaimer | Legal and informational pages. | features/posts and route content |
| /thank-you | Post-conversion confirmation page. | Marketing route content. |
Marketing shell
Marketing layout, navigation, footer, and reusable landing sections live outside product server logic.
SEO integration
Public pages should use metadata builders, canonical URLs, structured data, and content-owned metadata.
Content-driven pages
Blog, changelog, FAQ, legal, case study, and team pages read from the content and team modules where applicable.
Marketing modification rules
- Add metadata for every public page.
- Keep marketing pages server-rendered unless interaction requires a client component.
- Use route-private or landing components for presentation and feature modules for business data.
- Check authenticated and unauthenticated navigation states after nav changes.