As a Storyblok agency, Straffe Sites designs, builds, migrates and maintains Storyblok websites for small teams: a visual editor your editors trust, components that protect the design, and a fast frontend under it.
4.9/5 on Google26 reviewsYour team sees what will go live, works with reusable blocks, and only gets the choices designed for the website.
These services complement this one and help you choose the right approach for your project.
The dashboard should simplify everyday content work rather than expose every technical possibility at once. Nine of the projects on our cases page run on Storyblok.
Editors see pages in context and can check drafts before they are published.
Hero sections, FAQs, case studies, and other blocks have fixed fields. That protects the design, accessibility, and content quality.
You decide who writes, checks and publishes. Technical updates stay separate from normal content changes.
Implementation, migration, multilingual setup, maintenance and hosting around one CMS, plus an honest answer to whether Storyblok fits your team. Open the part you need.
Custom components, visual previews, forms and integrations built around your content model. We keep the component library small and typed, so editors get real freedom inside fixed rails. Technical SEO (structured data, sitemaps, canonicals, hreflang) is part of the build, not an afterthought.
For CLW Antwerpen, we built a school website that the school team manages itself in Storyblok. The sympl SaaS site runs on SvelteKit and Storyblok, and Storyblok features it in its own customer story about sympl.
Coming from WordPress, a classic CMS or a replatform: we inventory pages, blocks, media and metadata, map the URLs, run a controlled import and verify the result before anything goes live.
Moving from WordPress takes more than an export. Page builder layouts and shortcodes do not map one to one onto Storyblok blocks. So we decide per content type what becomes a block, a field, or plain rich text. Every old URL gets a redirect, and titles, descriptions, and alt text move along. Our Storyblok migration guide walks through the steps per source CMS.
Languages, translation workflows and fallback rules set up and tested up front, with hreflang pairs that stay honest. Your editors translate content, not markup. Our guide to Storyblok localization explains how to choose between field-level and folder-level translation.
For New Impact, each language lives in its own Storyblok folder, such as fr/ for French. That way the team publishes new work in every language itself, without a developer.
The CMS itself is SaaS; the frontend, components and build chain are not. We keep dependencies healthy, watch performance and Core Web Vitals, and refine the content model as your site grows. Want AI agents to prepare drafts in your space? We connect AI agents to your CMS with limited permissions and keep a human review before anything is published.
Integrations need the same care. For Verhuurwinkel, several API integrations connect the client's ERP system and Storyblok directly to the frontend. Product data and CMS content meet on the same pages.
We set up hosting for the Storyblok frontend and the publishing steps, so approved content actually appears on the live site. Preview and production stay separate, and we test the link between publishing in the CMS and updating the website. Drafts never reach the public site.
Before go-live we check the domain, HTTPS and forms, and we document how to roll back to the previous site version if a release goes wrong. Tell us where your site runs today and who manages the domain; we align the move and the responsibilities around that.
Storyblok is a good choice when multiple pages use the same kinds of content and editors want a visual preview. For a small site that rarely changes, a simpler local content setup may be enough.
We first review the pages, blocks, languages, relationships, and approval steps. Then every content type gets only the fields it needs. That prevents the CMS from filling up with dozens of unclear options.
For more context on managing content separately from the frontend, read what a headless CMS is.
Digital experiences that feel like the company behind them.
A rental store with twice the daily Google clicks it had at launch
Our own site as a running case: measured monthly, reported honestly
A premium site for practical AI agents under human control
Guitar lessons in Antwerp: page one for teacher Ben Boeckx
A boxing site with punch for personal trainer Brian, on a small budget
Beautiful and easy to find on a budget: Astro and custom bookings
A cinematic site for professional content creation and video production
A light portfolio site where prospects find the right video type
A sharp SaaS site that explains social recruitment and leads to a demo
A clear site for heat pumps and air conditioning, DIY to installation
One clear digital story for facility and industrial services
A warm school website for dual education, managed in Storyblok
A rotating selection of the reviews clients left on Google — Dutch reviews shown in English translation. An average of 4.9 out of 5 stars across 26 Google reviews (September 18, 2026).
Two years ago I started looking for someone who could help me with a website that scored well. In terms of approach, Seppe immediately made a good impression on me; he is patient (which I definitely need), professional, and transparent. You can always reach out to him with questions and he charges fair prices. Shortly after we first got in touch he launched a new website that I am very happy with, and he manages the SEO and SEA features to the best of his ability. As a proud ambassador of Straffe Sites, I look to the future with confidence!
Fast & perfect service.
A pleasant collaboration for 15 years now, with knowledge and skill at the center.
Clear and personal: you always know what is happening, what we need from you, and what the next step is.
We discuss your business, your customers, the bottleneck, and what the website or workflow needs to achieve.
You get a clear structure and visual direction, with choices we explain in plain language.
We do the build, share work in progress, and check the content, speed, technical quality, and mobile usability.
After launch we stay available for maintenance, performance tracking, and targeted improvements.
At Straffe Sites you work directly with the team. Seppe stays your dedicated point of contact and builds your website; the team supports him with commerce, code, and photography where needed. Communication stays direct, and your questions never get lost between account managers.
Straightforward answers before you decide whether this service fits your business.
Storyblok is a headless CMS with a visual editor. Content is managed separately from the frontend and delivered through an API.
Yes, using the components designed for your website. That gives you freedom without spacing, colors, or semantics changing from page to page.
Yes. Languages, translation workflows and fallback rules do need to be set up and tested properly in advance.
We list every page, block type, and media file, decide what becomes a Storyblok block or field, and import in a controlled run. Old URLs get redirects, and we check titles, descriptions, and alt text before go-live.
The CMS itself is a SaaS product. The frontend, components, integrations, and build chain still need technical maintenance, which Straffe Sites can handle.
Structured fields help, because each piece of content has a clear role. Search engines and AI crawlers read the published page, so we render clean HTML with structured data. Nobody can guarantee a mention in AI answers.
Technical terms from this page, explained briefly and linked to the full knowledge base.
a CMS that manages content but leaves the presentation to a separate frontend, connected via an API.
the agreed structure of content types, fields and relationships in a CMS, designed around what editors need.
the service and infrastructure that keeps a website’s files online and accessible, with provisions for performance, security and updates.
machine-readable information about a page’s content, added in a standardized format such as schema.org.
Tell us who manages the content and which pages change often. We’ll turn that into a clear editing experience and a fast frontend.
Discuss your project
Hi, I am Hermes, the AI agent of Straffe Sites. I answer your questions about websites, online stores, SEO and how we work, and pass your request on to Seppe when you ask me to.