Event
JoyConf 2026 in Mainz with synaigy as Platinum Extra Partner
On October 28 and 29, 2026, the Storyblok community will meet for JoyConf in the Rheingoldhalle Mainz. We will be there as a Platinum Extra Partner and are looking forward to two days full of inspiration, practical knowledge, and good conversations about content, commerce, and digital experience.

Structure has become cheap, maintenance has not
Benedikt opened the session with a number. Today, 83 components including a multilingual setup are created with an AI agent via MCP in around one hour. By hand it would take five to six hours. Building structure in Storyblok has therefore become cheaper than ever. But this creates a new problem. Speed builds structure, but it does not maintain it. And by now every space has a second reader alongside the editorial team: the agent.

How to recognize space drift in your Storyblok space
Space drift does not hurt for a long time. That is why it is worth looking at a few typical signals before a redesign, a new team member or an AI agent exposes the weaknesses of the model. In the session, Benedikt presented five of these signals. These include components that share almost all fields, fields that are not filled in any published story, and blocks without descriptions whose purpose is known to only a single person. On top of that come parallel fields with the same content in different tabs or types and the question of whether a block marked as deprecated is still being used anywhere at all, because no one dares to delete it.
Anyone who recognizes these patterns in their own space has already taken the first step. The slide deck shows in detail how to systematically track down the signals.

Storyblok best practices against space drift
The good news from the session is that Storyblok already comes with the tools to counter space drift. It is less about new tools and more about habits in how you work with the content model. Benedikt presented four practices, which we will only touch on briefly here.
Every component is born with an exit
Creating a component is easy, deleting it is a risk. That is why blocks should be restricted from the very beginning via tags rather than by names. Deprecating a component then becomes a pure tag change, without any editor or agent still seeing it.
The why stays in the space
The reason for a block leaves the company together with the people who built it. Benedikt therefore recommends writing field descriptions like prompts. What is the block for, what is it not for, and what should be used instead. New colleagues benefit from this just as much as the AI agent.
Workarounds as the earliest signal and treating the model like code
The two other practices revolve around observing real editorial work and around the schema in the repository. Every workaround is an indication of a gap in the model, and every diff in the schema is a finding. Which Storyblok features Benedikt recommends for this and what the concrete space health playbook in four steps looks like can be found in the complete slide deck.
