Migrating to CloudCannon

This skill orchestrates a full migration of an existing SSG site to CloudCannon. It coordinates five phases, delegating domain-specific work to standalone skills that can also be used independently.

Model recommendation: Migrations involve multi-file architectural decisions across five phases. Use a high-reasoning model (not a fast/lightweight one) for best results.

When to use

• An existing SSG site needs to work with CloudCannon end to end
• A site template needs to be made CloudCannon-compatible
• A site is being generated as part of the task (e.g. from WordPress) and should land CloudCannon-ready

When not to use

• The site is already on CloudCannon and needs one piece added — go straight to the capability skill: cloudcannon-configuration, cloudcannon-snippets, or cloudcannon-visual-editing
• Only multilingual or translation work is wanted — make-site-multilingual, then translate-site. Neither is part of the five phases.
• One CloudCannon feature is misbehaving on a working site — the capability skill that owns it, not a full migration

Contents