CMS Planning
Review the starter’s local content model, choose what you want a CMS to manage, and generate a migration brief to guide a separately implemented integration.
Start with the local content model
Section titled “Start with the local content model”The supplied starter uses local JSON and MDX. No CMS account is required. Designed pages use JSON plus Astro composition; articles, products, projects and ordinary documents use their respective content models.
The first release scope is the plain starter. There is no supported ready-integrated EmDash edition in this release. A CMS target in the prompt assistant is a planning choice, not an installed product flavor.
Choose what should move
Section titled “Choose what should move”The RT-Themes CLI reads this release’s .rtthemes/kit.json and asks which modules you want to manage through the chosen CMS. NaturaLife’s modules cover pages, blog, portfolio and products. Decide separately whether shared settings should move and whether existing content should be preserved or migrated.
For example, you can plan a blog-only move to Sanity while keeping designed pages, products and portfolio local. Preserve author/category/tag identities, stable public URLs, image alt/crop data and relationships to modules that remain local. A catalog-only product migration is different from connecting a real checkout.
Generate and review the brief
Section titled “Generate and review the brief”Use the shared CMS integration kit guide for the wizard, output rules and availability. The assistant creates an English Markdown planning brief, normally named CMS-INTEGRATION.naturalife-astro.<cms-id>.md. It does not call an AI API, create a CMS account or modify your content.
Give the brief and your actual customer project to your chosen AI agent. Ask it to inspect the installed files and propose a plan before implementation. Include decisions about body rendering, media handling, IDs, drafts, redirects, settings and hosting. Remote rich text does not automatically become compiled MDX.
Keep the version reference intact
Section titled “Keep the version reference intact”Do not hand-edit the generated kit or use a kit from another core version. Resolve vendor/lock/reference mismatches first. Generated briefs are local outputs; they are not maintained copies of the theme reference. Reassess the plan after changing the theme or your local architecture.
A real CMS migration may add credentials, dependencies, runtime routes and deployment requirements. Review and test those changes separately. Neither the brief nor the theme guarantees an automatic integration or a particular AI service’s result.
Get all RT-Themes designs, updates and support with a single Club license.
Join the Club