“If Next.js is your primary framework, I'd actually choose Sanity.”
“- Best Next.js developer experience: Sanity”
“Its next-sanity package is extremely polished and deeply integrated with modern Next.js concepts—App Router, Server Components, caching, Draft Mode, Visual Editing and live content.”
“Sanity also has first-party tooling for Next.js, Nuxt and Astro, with Svelte-specific tooling around its content formats.”
“Its documentation currently has dedicated framework quickstarts for Next.js, Astro and Nuxt and a specific SvelteKit integration guide.”
“- Best if content querying/schema flexibility is central: Sanity”
“Storyblok's official Svelte SDK is a particularly strong fit, whereas Sanity's framework-specific ecosystem is more React/Next-centric.”
“If your priority is official SDK quality + first-party integration guidance across Next.js, Nuxt, SvelteKit, and Astro, I’d put Storyblok slightly ahead overall.”
“If your priority is official SDK quality + first-party integration guidance across Next.js, Nuxt, SvelteKit, and Astro, I’d put Storyblok slightly ahead overall.”
“Storyblok has unusually broad framework-specific first-party SDK coverage: its current docs list official packages for React, Astro, Nuxt, Vue, Svelte, plus the general JavaScript SDK.”
“It also has dedicated quickstarts for Next.js, Nuxt, Astro and Svelte, covering fetching/rendering content and connecting the Visual Editor.”
“Its Core Blueprints extend that into ready-to-run starter projects for Astro, Next.js, Nuxt and Svelte.”
“That makes it particularly attractive if you maintain a multi-framework frontend stack rather than being heavily committed to React.”
“- Best if visual editing is central: Storyblok”
“Storyblok therefore has the more uniform experience across all four frameworks.”
