The visual frontend & visual editor for Storyblok – without a custom build

Storyblok is a headless, component-based CMS: content, bloks, datasources, multiple spaces, and languages are its strength – served via the Content Delivery API (REST) and the GraphQL API. Storyblok comes with a visual editor for content, but not a finished, production frontend. That's exactly where Laioutr comes in: as a visual page builder and frontend layer that reads your Storyblok content and serves it as a fast website. Storyblok stays your content backend, Laioutr delivers the frontend.

Storyblok continues to manage content, bloks, datasources, permissions, workflows, multiple spaces, and translations. You use the Storyblok editor and your established processes unchanged – with all apps and webhooks.

For the frontend, you have several options: the official Storyblok starter, a community framework with Storyblok integration, a custom build (Next.js/Nuxt) – or a page builder like Laioutr. Each option has pros and cons.

No data duplication, no sync conflicts. Laioutr reads your Storyblok content via the Content Delivery API (REST) and the GraphQL API and renders it – including multilingual support and multiple spaces.

Storyblok provides the building blocks with the visual editor, bloks, and an end-to-end Content Delivery API, but not a finished, production frontend product. So the frontend question comes up on every Storyblok project. Four options are established in the market.

The official Storyblok starters and Technology Hub examples (Next.js, Nuxt, Astro, among others) are an ideal starting point for learning and proofs of concept. As a production frontend, you keep developing the design system, components, and page logic yourself. Makes sense for small sites or as an interim solution.

Open-source frontend frameworks with Storyblok SDKs and community integrations. Active community, but no official production frontend product and no direct enterprise support network. Makes sense with a suitable frontend team for whom open source is strategically important.

Maximum control, highest effort. A six- to twelve-month build phase and ongoing maintenance by an in-house frontend team that connects the Storyblok Content Delivery API itself. Makes sense if frontend engineering is your strategic core competency.

Visual page builder and frontend platform with 70+ components, EU hosting, and a connection to Storyblok. Fastest time-to-launch, lowest learning curve, marketing and editorial build pages themselves. Makes sense if you want to go live fast, without a custom-build investment.

Laioutr is built for Storyblok setups that need to change and scale fast. From the corporate website through multi-brand portfolios to campaign landing pages with heavy editorial volume.

Storyblok is strong with multiple spaces and brands. Laioutr turns it into standalone frontends – one component pool, many brand presences, each with its own design and its own domain.

Marketing builds landing pages visually from ready-made building blocks – without custom code and without a developer ticket. Content comes from Storyblok, the layout takes shape in the page builder.

Storyblok manages translations and language dimensions, Laioutr serves them consistently. Languages, layouts, and content controllable per space, compatible with the Storyblok i18n concept.

One Storyblok, many channels. Content, languages, and layouts controllable per channel – the structured content from Storyblok is served consistently across web and further touchpoints.

Renew an existing Storyblok frontend without touching bloks, spaces, or editorial processes. Migration in phases, with a clear rollback plan.

New Storyblok project, clean slate. With Laioutr themes and the UI library, you go live in weeks instead of pouring months into a custom build.