SvelteKit

SvelteKit fits Paragraph CMS when you want fast static delivery, server-side data loading, and explicit control over which CMS routes are prerendered.

Recommended architecture

• fetch published content in +page.server and +layout.server files;
• prerender stable content routes and provide entries for dynamic CMS paths;
• keep draft preview on server-rendered paths instead of client-only reads; and
• make locale and slug generation part of the same server-side content layer.

Implementation checklist

• define entry generation for dynamic routes sourced from the CMS;
• keep global content in shared layout loads and page content in route-specific loads;
• align asset rendering rules across all rich content blocks; and
• rebuild or selectively invalidate output when editors publish.

When SvelteKit is a good fit

Choose this path when you want SSG-first performance with an easy path to server rendering for preview and selective dynamic behavior.