Skip navigation

From the JoyConf talk “Fit for Years”

How healthy is your space?

Storyblok brings speed to your team. To keep your space from drifting along the way, we take a look at it together in the Space Health Check. You get a clear picture and know where to start.

Space Health Check

What this is about

Structure just got cheap. Now change has to stay cheap.

To keep it that way, your space needs two things: a structure your team and every agent understand, and shared rules that everyone sticks to.

Building is fast

Through the Storyblok MCP Server and Agent Skills, AI agents create components and fields directly in the space.

Your space grows with it

More speed means more components, variants and fields. For some of them, it is no longer clear later what they are for.

The agent reads along

Your team knows the story behind every block. The agent only sees names, descriptions and rules, and works only as well as they do.

Space Health Check

What you get in the Space Health Check

We look at your space together with you and your team. Afterwards, you know where it stands and where to start.

Analysis

We check your space for the five typical signals.

Conversation

We talk to your editors about their day-to-day work in the space.

Plan

You get findings and an action plan.

Space Health Check

For teams whose Storyblok space has grown over the years.

What you get

  • Evaluation of all five signals, with concrete findings
  • Conversation with your editors about their real day-to-day work
  • Findings per signal: where it shows up and what it costs
  • Prioritised action plan along our four practices
  • Clear recommendations on which Storyblok tools to use for what

Approach

The five signals we check

They show up in almost every grown space. In the check, we look at each one in your space and show you which Storyblok tools solve it.

teaser, teaser_dark, teaser_v2: variants appear quickly, often for a single special case. Over time, components share most of their fields, and the block picker no longer makes clear which one is right. That goes for your editors as much as for an agent.

How Storyblok helps: Variants as an option within one component instead of separate components, retire old ones with an internal tag and move content over cleanly with CLI migrations.

A field was added for a campaign and today isn't filled in any published story. It bothers no one until someone uses it without knowing what it was meant for, and something unexpected happens on the page.

How Storyblok helps: A script on the Management API shows which fields aren't filled in any story. Whatever isn't needed can be removed cleanly with a migration.

What a block is meant for is often known only to the person who created it. Without a description in the space, new team members and agents have to guess when to use it and when not to.

How Storyblok helps: Field descriptions and tooltips right in the editor. Written like a prompt, they tell people and agents what a block is for, what it isn't for and what to use instead.

An image in the “Content” tab and another one in the “SEO” tab, a date as text and as a date field: which one counts? Duplicate fields lead to contradictory content and to workarounds in the editorial team.

How Storyblok helps: Define one source and secure it with validation and default values, so the second place is never needed.

Is the component still in use, or can it go? If nobody can say for sure, it stays, and the space gets a little harder to change every year.

How Storyblok helps: With internal tags, tag restrictions and CLI migrations, retiring a component becomes a planned change instead of a risk.

LET'S TALK!

How is your space doing?

In a short conversation, we find out how you work with Storyblok today and where the check would start for your team.

Contacts

Your contacts

Questions about the Space Health Check or your space? Write to us directly or use the form.

  • Benedikt Grimm
    Benedikt Grimm

    Head of Frontendsynaigy

    Show email address
  • A black and white portrait of a person wearing a cap and hoodie, looking directly at the camera with a neutral expression.
    Christoph Korfhage

    Head of UXsynaigy

    Show email address

Let's talk about your space

Tell us in two or three sentences how you use Storyblok and what's on your mind. We'll get back to you personally and talk through what the Space Health Check looks like for your team.

Please accept the corresponding cookies to view this embedded content.