Description
Context & Motivation
Our main application is built with Vue, but our current website and documentation run on 11ty. To unify our tech stack, share components between our app and site, and improve developer velocity, we are migrating the website to Nuxt 3.
Why Nuxt?
- Vue Ecosystem: It aligns perfectly with our core app's Vue development, allowing us to reuse UI components and developer knowledge.
- Built-in CMS: Nuxt Content provides an excellent, markdown-driven CMS that will massively improve the authoring experience for our docs, handbook, and blog.
- Incremental Adoption: Using the "Strangler Fig Pattern," Nuxt's Nitro server allows us to proxy traffic seamlessly to 11ty. This means we can migrate page-by-page without a massive "big bang" rewrite, ensuring zero downtime and a smooth developer experience.
Strategy Overview
We will move to a monorepo structure. Nuxt will act as the front door. If Nuxt has a route (e.g., a newly migrated page), it will serve it. If it doesn't, it will proxy the request to the legacy 11ty build.
Description
Context & Motivation
Our main application is built with Vue, but our current website and documentation run on 11ty. To unify our tech stack, share components between our app and site, and improve developer velocity, we are migrating the website to Nuxt 3.
Why Nuxt?
Strategy Overview
We will move to a monorepo structure. Nuxt will act as the front door. If Nuxt has a route (e.g., a newly migrated page), it will serve it. If it doesn't, it will proxy the request to the legacy 11ty build.