Manual

Use this page when you are building a custom production setup and do not want to rely on an advanced starter project.

Recommended architecture

1. Keep Client, site, and SEO configuration in a shared paragraph.config file.
2. Define a clear locale strategy before building routes or generating static params.
3. Centralize your public route map so sitemap, RSS, robots.txt, and llms.txt all use the same source of truth.
4. Split list routes, detail routes, and localized routes cleanly so generated URLs stay predictable.
5. Render content with stable slug-based lookups and avoid duplicating routing rules in multiple places.
6. Generate SEO documents during build or request time from the same content source as the app.

Pick the closest implementation

• Next.js
• Astro
• React Router
• Nuxt
• SvelteKit

Production checklist

• Verify the default locale and translated locale URL structure.
• Confirm every public route can be reproduced from CMS data during build.
• Keep canonical URLs, sitemap entries, and RSS items aligned with the same route helpers.
• Decide how preview content, unpublished pages, and cache invalidation should work before launch.

This manual page is the framework-agnostic checklist. For concrete code, use the advanced guide for the framework you are shipping.