CMS Integration Kit
Prepare the project
Section titled “Prepare the project”Use the matching .rtthemes/kit.json included with your product. It describes the exact core version, content modules and architectural reference. The theme owns that reference; the CLI uses a shared questionnaire and planning template. Resolve vendor/lock/reference mismatches before proceeding.
Complete CLI setup and verification before running the commands below.
Choose a planning scope
Section titled “Choose a planning scope”npx @rtthemes/cli@latest kit --project /path/to/customer-projectThe wizard asks you to select:
- A CMS from the supported prompt-target catalog, currently Sanity or EmDash.
- Content modules declared by the product.
- Whether shared settings should move into the CMS.
- How to handle existing content.
- Catalog versus real checkout, when a commerce-capable module is selected.
Use arrows and Enter for choices, and Space for multiple content modules. Review the summary before writing. Ctrl+C cancels. Unknown CMS targets are rejected; use the wizard to see the product’s actual module IDs.
For the NaturaLife Astro blog-only example, with local settings and existing content preserved:
npx @rtthemes/cli@latest kit --project /path/to/customer-project \ --cms sanity --content blog --settings no --migration preserveSelecting a CMS prompt target does not install that CMS or imply a ready-integrated starter. NaturaLife Astro’s first release scope remains the plain local MDX/JSON starter; an integrated EmDash edition is outside that scope.
Use the generated brief
Section titled “Use the generated brief”The default output is a new local Markdown file named CMS-INTEGRATION.<product-id>.<cms-id>.md. Existing files and symlinks are rejected; output must be a new .md file within the selected project and an existing directory. Keep generated briefs as local outputs, rather than maintained copies of the product reference.
The CLI makes no AI API call and sends no project content to an AI or CMS service. It does not require an AI account for generation. Give the English brief and your actual project to your chosen agent, then ask it to inspect files, clarify decisions and prepare a plan before making changes.
Review IDs/relationships, rich-text rendering, images/crops, drafts, URL redirects, settings and hosting requirements. A generated brief is not a successful migration, an automatic integration or a guarantee about a third-party service. See NaturaLife Astro CMS planning for product-specific boundaries.