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.
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.
Four services 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.
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.
Languages, translation workflows and fallback rules set up and tested up front, with hreflang pairs that stay honest. Your editors translate content, not markup.
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.
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 fast rental site that makes choosing and requesting simple
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 findable 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
Clear and personal: you always know what is happening, what I 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 I explain in plain language.
I do the build, share work in progress and check the content, speed, technical quality and mobile usability.
After launch I 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.
Yes. We first create a content inventory and map the URLs, media, metadata, and relationships. We then run a controlled import and verify the result.
The CMS itself is a SaaS product. The frontend, components, integrations, and build chain still need technical maintenance, which Straffe Sites can handle.
Technical terms from this page, explained briefly and linked to the full knowledge base.
a content management system that stores and manages structured content separately from presentation and delivers it via an API to websites or other channels.
a formal description of content types, fields, relationships, and validation rules that defines how content is stored as structured data.
the infrastructure and services that store website files, run server processes, and make a website available online.
machine-readable information that describes a page, organization, article, product, or other entity and how its parts relate.
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