Nuxt

Nuxt works well with Paragraph CMS when you want Vue-based routing, built-in data fetching, and flexible static or hybrid delivery from one codebase.

Recommended architecture

• fetch published content with useAsyncData or server routes close to the page boundary;
• prerender stable marketing routes during build and leave volatile routes on runtime rules only where needed;
• keep preview reads behind server-only logic; and
• generate locale-aware routes directly from CMS entries.

Implementation checklist

• centralize CMS fetch logic in composables or server utilities;
• define prerender routes for pages the crawler cannot discover automatically;
• keep global settings and page content in separate queries; and
• trigger rebuilds, route invalidation, or cache purge from publish webhooks.

When Nuxt is a good fit

Choose this path when your front end is already Vue-based and you want SSG, SSR, and controlled preview behavior without splitting the architecture.