Probably yes if
- every new page goes through a developer today, and your team publishes often
- you launch a new landing page or microsite for most campaigns
- the same content has to show up in more than one place, like your site and an app
Headless CMS your editors can run
Does your team wait on a developer every time it needs a new page? I set up the CMS so they can publish on their own. PS260 and HOUS both do, in Storyblok.
StoryblokHeadless WordPressNext.jsReactNuxtVueTypeScriptVercel
What your editors get
Most CMS pain isn't the tool, it's how it was set up. I build the editing side for the people who use it. Fields use their words, and the help text sits where they'd get stuck. Validation stops a half-finished page from going live.
Your marketers build new pages from blocks that already match your design, so a campaign page doesn't need a ticket and stays on-brand. For PS260, that meant a Storyblok setup their team runs without a developer.
“He also integrated a custom CMS that makes updating our content and building new pages simple, even for non-developers.”
What's included
- A workshop with your editors before anything is built, to map out what they publish (content modeling)
- Your existing pages moved across, with a plan for every old URL (migration plan)
- A preview that shows each page as it will look on the site (live preview)
- Roles and sign-off steps, so the right person approves each page (workflows and role-based publishing)
For your developers
- Content types and nestable blocks with typed schemas (Zod or generated types), so the frontend never breaks silently
- Next.js or Nuxt frontends, statically generated and refreshed by CMS publish webhooks
- Signed preview links for the visual editor
- Image optimization, responsive media and localization where you need it
- Webhooks to the rest of your stack (Algolia, Slack, Make, Zapier)
Is headless worth it for you?
Probably not if
- it's a five-page site that changes a couple of times a year
Questions about switching
Which headless CMS should I pick?
It depends on your editors and how much content you have. Storyblok suits marketing teams who want to edit pages visually, and it's what PS260 and HOUS run on. Sanity suits highly structured content. Contentful is the safe enterprise choice. For developer-led teams, Payload or Sanity with a custom studio is hard to beat. I'll recommend one based on how your editors work.
Do my editors have to learn new software?
Some, but a headless CMS is usually friendlier than the WordPress admin. Storyblok has a visual editor that looks like the live site. I include a recorded training and a written handbook for the jobs your editors do most.
Can I migrate from WordPress without losing SEO?
It's doable, and it's the part I plan around most. For HOUS, an LA real estate site, I moved hundreds of journal posts and its listings from WordPress to Storyblok. Every old link that changed now redirects straight to its new page (55 of them). The plan also covers structured data, a new sitemap and a content audit. How the HOUS move worked
How long does a move take?
It depends on how much content has to come across and how many page types you need. The written scope, which you get within 48 hours of the call, lays out the milestones.
What does it cost, and how does it compare with WordPress?
There are two costs: my fee to set it up, and the CMS subscription. You get a fixed price for my part before any work starts. Compared with WordPress, you pay more for the CMS and less for hosting and upkeep.
Teams that publish on their own
PS260
PS260, a New York editorial and post studio, started with a concept video. Now its reels play full-screen, and its producers update the site themselves.
HOUS
A headless rebuild of an LA architecture real-estate site on Next.js and Storyblok, migrating 373 articles and 42 listings from WordPress.
How does your team publish today?
Book a free 30-minute call and walk me through it. I'll tell you whether headless is worth it for your team, and roughly what it would cost.
