Edit content and preview the page
Your editors work with components for articles, teasers, images and buttons. The Visual Editor shows how that content will appear on the website.
We build content blocks around your design and editorial tasks. A button might have fields for its label, style and destination; an article also needs images, SEO metadata and links to related content. We define which blocks can be combined and which fields must be completed before publishing.
Storyblok manages the content and makes it available through APIs. The website can use a separate frontend or continue to be rendered by an existing CMS. We connect the systems so editors can preview drafts and published content appears where it belongs.
Edit content beside its preview
Editors see the page alongside its content blocks. This official Storyblok demo shows how structured editing connects to the frontend preview.
Product view: © Storyblok
Storyblok Visual Editor
Where Storyblok fits
A useful option when editorial independence and frontend flexibility are both important.
- Let editors work visually within the rules of the design system.
- Reuse components across websites, brands, countries and channels.
- Develop and release the frontend independently of the CMS.
- Support multilingual publishing, versions, approvals and defined editorial workflows.
- Add dynamic content gradually to an existing TYPO3 installation or portal.
- Use a managed SaaS CMS where its privacy, operational and commercial terms fit the organisation.
From content model to published page
We connect Storyblok blocks to your frontend components and set up previews, approvals and publishing.
- Content strategy, component models, naming, validation and editorial ownership
- Visual Editor setup with responsive previews and reliable block-to-component mapping
- Spaces, roles, workflows, versioning, languages, assets and reusable data sources
- Content Delivery and Management API integration for websites, apps, portals and existing CMS platforms
- Preview, build, publishing and cache strategies, including failure handling
- Search-friendly delivery with URLs, metadata, structured data, canonicals, redirects and sitemaps
- Migration, testing, documentation, training and ongoing development
Connecting Storyblok to existing systems
We define where each type of content is maintained and where it is used. Articles can come from Storyblok while existing pages, forms and custom extensions remain in TYPO3. Where needed, we connect a digital asset management system such as Bynder and specify which image source takes priority.
The integration handles publication status: new articles must appear, updates must reach the website and withdrawn content must be removed. Images, links and SEO metadata are part of that process. We map content between the systems and configure updates, caching and error handling around the publishing workflow.
We first test the full path from editing to delivery with selected content. We then bring across further content types and introduce the editorial team to the new workflow. Your IT team or existing agency is involved in integrations, deployment and ongoing maintenance.
Storyblok in a hybrid platform
For lotterien.at, we built the integration between Storyblok and TYPO3. Our journal article explains how it brings together articles, publication status, images from Bynder and Storyblok, and SEO metadata.