Storyblok websites your team edits right on the page

Because your editors see exactly what they're changing. Storyblok's visual editor shows the real page next to its fields, so you click a section and edit it in place. We build you a library of components, called Bloks, that nest inside each other, so pages stay flexible without anyone breaking the design. It's also strong when one team runs several sites, brands or languages from one place.

We're partners of both, and we pick per project. Storyblok suits teams that want to edit visually on the page, run several brands or markets from one space, or need approval workflows. Prismic suits marketing teams who want a focused page builder at a lower price. If you're not sure, we'll give you an honest view in a first call.

There's Storyblok itself, and there's us. Storyblok has a free plan, and paid plans are priced by seats and features, so it's worth planning who needs access. What we charge depends on how many components you need, how much content is moving over, and what the site connects to, such as Shopify or search. After a first chat we send a fixed quote.

We get a staging site running with your real content early, so you see progress every week rather than at the end.

Yes, alongside Shopify. Storyblok runs the content, such as campaigns, landing pages and editorial, and Shopify runs products and checkout, both on one fast front end. We built Thrift+ this way, with search across more than 100,000 items.

Yes. Storyblok can translate content field by field, or give each market its own folder with its own pages, and you can share components across all of them. We help you pick the setup that fits how your team works.

Not if the migration is done carefully, and that's most of the work. We map every old URL to its new one, carry over titles, descriptions and structured data, and check it all on staging before the switch.

No. Your content is available through Storyblok's API, so it can move if you ever need it to. We build with Nuxt and Next.js, which most developers know, so another team can pick up the code without starting over.

No. Once your component library is built, editors create and update pages in the visual editor. We train the team at handover and stay around for questions.

Yes. We usually start with a health check: we run your space through Cojack, our own audit tool, which reads drafts as well as published pages, find unused Bloks, broken links and empty SEO fields, and come back with a list of what to fix first.

We're still around. Most clients keep working with us on new components, campaigns and improvements, either on a monthly plan or project by project.