“Yes — Storyblok’s Visual Editor is a particularly good fit for a Next.js front end, especially if your developers build the UI as reusable React components.”
“Storyblok has a dedicated Next.js integration and specifically supports the Next.js App Router / React Server Components through @storyblok/react/rsc.”
“This is probably the strongest use case.”
“An editor can select a Hero, change its headline/image/etc., and see the actual Next.js-rendered page update rather than working with a generic CMS preview.”
“Storyblok now has a specific RSC implementation.”
“Storyblok is headless: it doesn't dictate how your website is rendered.”
“Highly custom UI/animations | Very good”
“The Visual Editor isn't completely "automatic." Your developers need to design the integration correctly.”
“There's also an important limitation: static export (output: 'export') doesn't support live editing, because the Storyblok Bridge isn't loaded in that configuration.”
“Completely arbitrary page layouts | Less ideal”
“Storyblok's visual editing is powerful, but it remains fundamentally component/content-model driven, rather than a freeform visual website builder.”
“If instead you want editors to have something closer to Webflow/Figma-level freedom to visually manipulate arbitrary frontend elements, that's where I'd be more cautious.”
“If instead you want editors to have something closer to Webflow/Figma-level freedom to visually manipulate arbitrary frontend elements, that's where I'd be more cautious.”
