Nuxt

Nuxt's advanced integration work is about balancing prerendering, route rules, and server-side preview so content-heavy pages stay fast without giving up editorial control.

Rendering strategy

• use nuxt generate or Nitro prerendering for stable routes and route rules for selective runtime behavior;
• add CMS-derived routes explicitly when the crawler cannot discover them;
• keep payload size under control by separating global and page-specific queries; and
• define which CMS routes are prerendered, skipped, or revalidated at runtime.

Preview and publishing

• put draft reads in server-only utilities or endpoints;
• keep preview credentials environment-specific;
• trigger rebuilds or invalidation from publish webhooks with route-level data; and
• make localized route generation deterministic so editors do not publish pages to mismatched URLs.

Operational guardrails

• validate route coverage for dynamic content before deployment;
• watch prerender duration and payload growth as content scales;
• generate feeds, robots, and sitemap output from the same route inventory; and
• fail loudly when linked CMS content needed for a route is missing or unpublished.