NUXT CMS
The Nuxt CMS made for your static sites
Keep your Nuxt development workflow. Give content teams visual editing that works seamlessly with your deployment pipeline.
Vue composability meets editorial ease.
CloudCannon works directly with your Nuxt static site repository. Content editors manage updates through our polished interface while you keep full control over your composables, layouts, and build processes.
Git-first content collaboration
Content teams develop material in separate branches, test changes on staging sites, then merge to publish fresh static sites. Your Nuxt development stays completely uninterrupted.
Visual page building with Vue architecture
Build Vue components using Nuxt patterns once. Content teams assemble pages using visual tools with real-time feedback. Your auto-imports, middleware, and static generation configuration work exactly as you've set them up.
Static speed, universal reach
Nuxt's optimized static generation paired with CloudCannon's optional global hosting delivers blazing performance worldwide. Pre-rendered pages, automatic code splitting, and smart caching create exceptional user experiences.
Focus on features. Forget content hassles.
Put your development energy into building new capabilities instead of handling content changes. Spin up new Nuxt static sites quickly with your existing component library and styling solutions.
Real results from real migrations
Web development agency Croissant & Baguette use CloudCannon for their static sites, with full confidence that their clients will have a consistent and intuitive editing experience.
Three steps to visual editing with Nuxt
Build with Nuxt
Build your static Nuxt site in SSG mode locally with your preferred stack and structure.
Configure with CloudCannon
Configure collections, set editing rules, and transform your shortcodes and content blocks into visual components.
Hand off confidently
Hand off to content teams who can update content visually — without touching your code.
No vendor lock-in. Period.
Your Nuxt code and content stays in Git.
Your repos stay yours.
Tiaan Fairchild
Software Engineer
