Storyblok for dynamic content, TYPO3 for existing extensions
lotterien.at serves several audiences. Its platform and underlying features have developed over time. In this situation, asking which CMS should replace everything would miss part of the picture.
Our approach adds Storyblok to the existing TYPO3 solution. Content that changes frequently moves into the content hub; other pages and existing TYPO3 extensions stay in place initially. That gives us a defined first step without replacing the entire platform.
What we mean by content hub
Here, a content hub is the place where selected content is maintained in a structured form and made available for use. Each interface does not have to manage another copy of it. Storyblok separates content editing from delivery in the frontend.
Editors still need to understand how content will appear. An appropriate preview is therefore part of the integration. A successful API call alone does not establish whether editors see the correct content variant or can reliably assess their changes.
Editing, links and caches across two CMSs
A hybrid setup must not leave people wondering where to maintain a piece of information. We consider content, responsibilities and technical dependencies together: what belongs in each system, what is referenced and which changes need to trigger delivery or cache updates?
Navigation, links and search-engine access also need to remain consistent across the technical division. Visitors should be able to move through the site without noticing where one CMS ends and the other begins.
Evolving without replacing everything at once
The existing TYPO3 extensions do not need to be rebuilt for this stage at lotterien.at. The project can concentrate on dynamic content and its delivery from Storyblok.
This approach can also suit other established platforms. Running two systems adds responsibilities of its own. The benefit comes from giving each a well-defined role and making sure someone owns the connection between them.
Storyblok takes on dynamic content while static pages and complex extensions initially remain in TYPO3. The integration connects previews, APIs and publishing.