Yuri Osipov · Founder, SEO & analytics

Storyblok: the CMS your marketing team can see

Storyblok starts from a different assumption than most headless CMS products: editors should not have to imagine the page. The preview is the site, the fields sit on top of it, and the content model — a tree of components — is designed so that clicking what you see is how you edit it.

In short

What Storyblok actually is

Every piece of content is a story — a page or a global fragment — and its content is a recursive tree of bloks. Each blok has a component name and a set of fields, and nested bloks can be reordered or added by the editor within limits you define.

You define those components in the Storyblok space (or sync them from a schema file), then build the matching Astro components. The naming convention is the contract: a blok called hero renders through the component registered as hero.

---
// src/components/StoryblokComponent.astro (simplified)
import Hero from './Hero.astro'
import FeatureGrid from './FeatureGrid.astro'

const { blok } = Astro.props
const map = { hero: Hero, feature_grid: FeatureGrid }
const Component = map[blok.component]
---
{Component && <Component blok={blok} />}

The official integration ships its own StoryblokComponent that does this lookup, so in practice you register components once and let it render the tree.

A practical detail that shapes the project: Storyblok separates spaces, environments and releases. Staging content can live in a preview environment inside the same space, and a release groups a set of changes to publish together. That is closer to how a real editorial calendar works than a single “draft” toggle — but it also means your build pipeline needs to know which environment it is reading.

Who it fits

Less suitable when: the content is mostly articles rather than composed pages, when the budget cannot carry a recurring platform cost, or when the client’s security policy forbids another vendor holding their content.

How it connects to Astro

---
import { useStoryblokApi, StoryblokComponent } from '@storyblok/astro'

const storyblokApi = useStoryblokApi()
const slug = Astro.params.slug ?? 'home'
const { data } = await storyblokApi.get(`cdn/stories/${slug}`, { version: 'published' })
const story = data.story
---
<StoryblokComponent blok={story.content} />

Three things to plan for:

Publishing should trigger a rebuild through a webhook to your hosting platform. For pages that change hourly, add an on‑demand route; for everything else, a build is cheaper and simpler.

Strengths

Weaknesses

When to choose Storyblok

Choose it when the approval happens visually: marketing signs off on pages, not on JSON, and every extra round of “can you send me a screenshot” costs real time. It is also strong when the site is a composition of reusable sections rather than a stream of articles.

If your content is mostly long‑form text with references, Sanity structures it better. If the priority is owning the stack and writing the schema in code, read the Payload guide.

Summary

Storyblok sells a shorter feedback loop, and for a marketing site that loop is most of the value. You pay for it with a subscription, a vendor dependency and one more mapping layer between the CMS tree and your components — a fair price when editors are the bottleneck.

See where it lands against the alternatives in the headless CMS comparison for Astro, or start from the headless CMS hub. We build Storyblok‑backed Astro front‑ends as part of web development.

Screenshots in this series are placeholders — we will replace them with our own, taken on real projects.

Yuri Osipov

Yuri Osipov

Founder, SEO & analytics

Runs Take the Space. Specialises in technical SEO, measurable analytics setups and AI search visibility.

All posts by the author →
What makes Storyblok different from other headless CMS?
The visual editor. Storyblok loads your actual site in a panel and lets editors click a headline, an image or a card in the preview and land on the matching field. Content is a tree of components, so the preview is the real front‑end rather than a separate rendering.
Does Storyblok work with Astro?
Yes, through the official @storyblok/astro integration. It provides the API client, a component that renders a blok by its name, and the bridge script that enables click‑to‑edit inside the preview.
Is Storyblok self‑hosted?
No. Storyblok is a SaaS platform: content, assets and the editor run on their infrastructure, and you consume it through the Content Delivery API. Self‑hosting is not an option, so vendor dependence is part of the deal.
How do I type Storyblok content in TypeScript?
Generate types from your component schemas rather than hand‑writing them. The integration and CLI can produce TypeScript definitions per component, and mapping each blok name to an Astro component gives you a compile‑time check that the tree matches your library.
Can editors publish without triggering a full rebuild?
They can, if you use on‑demand rendering or incremental rebuilds. Most Astro setups trigger a build through a webhook when content is published, and use the CDN cache plus cache invalidation for the rest.

Want a high‑performance website?

Let’s discuss how we can help your business grow.