Storyblok meets TYPO3: A new way to publish at lotterien.at, without rebuilding the website

Storyblok for articles, TYPO3 for the existing website

lotterien.at brings together editorial content, standard pages and a range of custom TYPO3 extensions. Storyblok provides the content hub. Editors create structured articles there and check them in preview. TYPO3 still handles how they appear on the website.

Static pages and complex extensions stay in TYPO3 for now. We did not need to rebuild what already worked. The work was in connecting the two systems.

Publishing, updating and taking articles offline

Our integration sends articles from Storyblok to TYPO3 in real time. It handles the full publishing cycle: a new article goes live (Publish), an existing one changes (Update), or an article is taken offline (Unpublish).

The article’s status travels with its content. Editors manage the whole process in Storyblok without having to repeat changes in TYPO3.

Images from Bynder and Storyblok

Article images come from two sources: Bynder, the digital asset management system, and Storyblok’s own assets. The TYPO3 integration handles both. Austrian Lotteries decides which source takes priority, and the integration applies those rules.

SEO metadata alongside the article

Editors manage the page title, description and other SEO metadata alongside each article in Storyblok. The integration sends the metadata to TYPO3 with the article. There is only one place to keep it up to date.

One reusable block for buttons

We built a custom button block in Storyblok with fields for the label, link and style. TYPO3 receives everything it needs to display the button in the chosen style on the website.

Editors use the same building block for every button. They can change the text or link without creating the button again.

Arranging homepage content automatically

We also built logic that arranges the homepage content blocks according to rules set by Austrian Lotteries. Editors do not have to put the modules in order by hand.