A Connector That Outlived the Shop
Our content lives in Storyblok and the shop is a separate system, so something has to connect the two. I built the first integration when we started with Storyblok and worked on the connector with the team. Over the years the same content had to run on three shop platforms: Oxid, Magento and Shopware. I also wrote most of the editor plugins the content team uses every day.
- Client
- Calida Group Digital GmbH, in-house
- Engagement
- Six years next to other work, with the content team
- Role
- Web Developer, Storyblok lead
- Year
- 2019 to 2025
- Stack
- Storyblok, Vue 3, TypeScript, Node.js, Shopware 6, Magento, Oxid
- shop platforms, one content setup
- 3Oxid, Magento and Shopware read the same content. We only rewrote the part that talks to the shop, so the existing landing pages kept working after a platform change.
- editor plugins I wrote
- 5A WYSIWYG editor, image and video upload that goes to Azure, a dropdown with search that always shows the current shop categories, and a color picker with our brand colors.
- developers needed to publish a landing page
- 0The content team builds landing pages from our widgets and publishes them. They only need a developer when a widget does not exist yet.
I was one of the first here to work with Storyblok, so I ended up being the person people asked about it. The first thing I connected was landing pages, before the shop was involved at all. After that I had the lead for the topic until I changed teams internally.
Most of my own work was on the editor side. Storyblok brings its own fields, but they do not know our media storage or our shop categories, so I wrote plugins for that: a WYSIWYG with the options the shop can actually render, uploads that go to Azure, and a dropdown with search for categories. I built them together with the content managers, based on what they needed for their pages.