Get a Site Ready for Rosey (+ the RCC)

Step-by-step workflow for making a single-language site translatable with Rosey, and — optionally — wiring up the Rosey CloudCannon Connector (RCC) so editors can translate inline in CloudCannon's Visual Editor.

When to use

• A single-language site needs to become translatable — the main workflow, setup.md
• The site already has an i18n system (astro-i18n, next-intl, dictionaries + t()) that should be replaced with Rosey — migrating-from-i18n.md
• The site runs RCC v1 and should move to v2 — rcc-v1-to-v2-upgrade.md
• A Rosey-ready site needs the CloudCannon inline-translation layer added — setup.md § Phase 5

When not to use

• Filling in translations on a site that is already Rosey-ready — that's translate-site
• General CloudCannon configuration unrelated to locales — that's cloudcannon-configuration
• Setting up editable regions themselves — that's cloudcannon-visual-editing. This skill covers only where data-rosey and regions interact.

Contents