Components, not pages.
Storyblok holds content as blocks with defined fields, not as slabs of markup. We model those blocks, wire the front end to them, and connect the CMS to the CRM so a page and the form on it are not two separate sources of truth.
The CMS holds the copy. The code holds the layout.
Text is editable and everything that decides how it looks is not. Adding a section, reordering one, or launching a page shaped differently from the last one is still a release — so the only person who can ship a landing page is whoever built the previous one.
Content the team can move.
StoryblokWhat the model has to hold.
A component library, not a page dump
Blocks modelled once with real constraints on what nests inside what, so a marketer composes a page from parts that were designed to sit together. No rich text field standing in for a layout.
Front end wired to the schema
The site renders from the content types rather than from fixed templates, so a new block is a component and a schema change, not a rebuild of the page it appears on.
Locales as a workflow
Field-level translation, fallbacks and a review path per market, so a second language is a queue somebody owns instead of a folder of duplicated stories that drift apart.
The CMS to CRM boundary
Forms, campaign attribution and gated content resolved against the CRM, so a submission on a Storyblok page lands on the same contact record as every other touch.
Preview and release the team trusts
Visual editing that renders the actual production components, and scheduled releases so a campaign page goes live at the hour it was planned for.
Search, sitemaps and the technical floor
Structured data, redirects and canonical rules generated from the content model, so a page that gets renamed does not quietly become a broken link.
Model, build, migrate, hand over.
Model
The blocks the site actually needs, written down as content types with their fields and nesting rules, before anyone opens the editor.
Build
Components against the schema, the preview environment, and the integration to the CRM so forms and attribution work on day one.
Migrate
Existing pages moved into the model with redirects mapped, rather than left on the old stack as a second site nobody maintains.
Hand over
The component library documented in the editor's language, and the first campaign after launch composed by the marketing team rather than by us.
The model is drawn for one page.
A schema built around the launch homepage survives until the third campaign, then editors start nesting blocks in ways the components were never written for. What follows is a library of near-duplicate blocks and a translation queue nobody can finish. The model is the project, and it is worth a week before the build.
Tell us which block you keep duplicating.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.