Can my marketing team edit a headless website without a developer?

Yes, for anything the developer has modeled as content: text, images, blog posts, case studies, team members, FAQs and pages built from pre-designed sections. What they usually cannot do alone is invent a new layout or component that does not exist yet. That still needs a developer.

Can editors preview changes before publishing on a headless CMS?

They can if it is set up. Next.js has a draft mode that renders unpublished content, and CMSs like Sanity and Storyblok offer visual editing where the editor sees the real page while typing. Without that setup, editors work in forms and only see the result after publishing, which is the most common complaint about headless sites.

Is a headless CMS worth it for a small business website?

Not always. A five-page site that changes twice a year does not need one. It starts paying off when several people publish regularly, the same content feeds more than one place, or the site needs to be faster and more custom than a template builder allows.

Headless CMS Explained: Can My Team Still Edit the Site?

Q: What is a headless CMS?

A headless CMS is a content editing system that stores your text, images and page content but does not decide how the website looks. The website is a separate piece of code that asks the CMS for content and displays it. The 'head' that was removed is the front end.

When I recommend a headless setup to a client, the first question is almost never about speed or SEO. It’s this: “If we go headless, can my team still change the website, or do we have to email you every time?”

Short answer: yes, your team can still edit it, and often more comfortably than before. The longer answer depends on how the site is set up, and that’s worth understanding before you sign off on the architecture.

What “headless” actually means

A traditional CMS like WordPress does two jobs. It stores your content, and it also decides how that content looks, through a theme. The content and the design live in the same system.

A headless CMS only does the first job. It’s a place to write and organize content: pages, blog posts, case studies, team bios, FAQs. The website itself is a separate piece of code, often built with React and Next.js, that asks the CMS for content and displays it. The “head” that got cut off is the front end.

Popular options include Sanity, Contentful, Storyblok and Payload. They differ in price and in how editing feels, but they all work on that same split.

Why anyone would split them up

Speed. The front end can be built for performance without a theme’s plugins and leftover code dragging it down.
Freedom. The design isn’t limited to what a theme or page builder allows.
Reuse. The same content can feed the website, a mobile app, a partner portal or a sales deck generator.
Security. There’s no public WordPress login page and no stack of plugins to keep patched.

None of that matters if the people who run your marketing can’t use it. So here’s the honest picture.

What your team can edit on their own

Anything the developer has set up as content. In a well-built headless site, that covers most of what a marketing team touches week to week:

Headlines, body copy, buttons and calls to action
Images and their alt text
Blog posts, case studies, news and job listings
Team members, testimonials, logos and FAQs
SEO titles, meta descriptions and social share images
New landing pages built from a library of existing sections

That last one is the important bit. A good headless build gives editors a set of blocks, such as hero, feature grid, testimonial strip, pricing table and FAQ, and lets them stack those blocks to make a new page. Your team can launch a campaign page on a Tuesday afternoon without anyone writing code.

What still needs a developer

Your team can rearrange what exists. They can’t invent something new. If the marketing lead wants a section type that has never been built, like an interactive comparison tool or a new kind of carousel, that’s a development job.

In practice that’s healthy. It stops a site turning into fifty slightly different hero sections, which is what tends to happen with unlimited page builders. But it does mean you should plan the block library carefully at the start, around the pages your team actually makes.

The question to ask before you build

“What pages will we create in the next twelve months that don’t exist yet?” The answers become the block library. If the list is “campaign landing pages, case studies and webinar pages”, those three templates and their sections get designed first, so nobody needs a developer to publish them later.

Previews: the part that makes or breaks it

The most common complaint about headless sites is editing blind. The editor fills in fields in a form, hits publish, then opens the website to see whether it looks right. That’s a real problem, and it’s a setup problem, not something you have to accept.

Next.js has a draft mode that renders unpublished content, so editors can click “preview” and see the real page before it goes live. Some CMSs go further. Storyblok’s visual editor and Sanity’s presentation view show the actual page next to the editing panel and update as you type. If a developer proposes headless without previews, push back.

How publishing works

When an editor hits publish, the CMS tells the website that something changed, and the site rebuilds the affected pages. On a well-configured Next.js site that takes seconds. On a badly configured one it can mean waiting for a full rebuild, or worse, the change not showing until someone redeploys. Ask how long a typo fix takes to appear live. The answer should be “seconds to a minute”.

When headless is overkill

I’d steer you away from it if:

The site is a handful of pages that change a couple of times a year.
Only one person ever edits it.
The budget doesn’t stretch to building a proper block library and previews. A half-built headless setup is worse than a good template.

My own portfolio is a fair example. I’m the only person who edits it, so the content lives in the code and I change it directly. Adding a CMS would be ceremony for an audience of one. For a client with a marketing team of three publishing every week, the answer is different.

If you’re weighing headless against a visual builder like Webflow, I compare the two directly in Next.js vs Webflow: when a no-code site stops being enough.

What to ask before you agree to a headless build

Which CMS, and why that one for our team?
Can we see the editing screen before we commit?
Will editors get a live preview, and is it visual or a separate preview link?
Which page types and sections can we build ourselves on day one?
How long does a published change take to appear?
What does the CMS cost per seat as the team grows?
Who owns the CMS account and the content if we part ways? (It should be you.)

Frequently Asked Questions

What is a headless CMS?
A content system that stores your text, images and page content but doesn’t control how the site looks. The website is separate code that fetches the content and displays it.

Can my marketing team edit a headless site without a developer?
Yes, for anything set up as content, including new pages built from existing sections. Brand-new section types still need a developer.

Can editors preview changes before publishing?
If it’s set up properly, yes, through draft mode or a visual editor. Ask for it explicitly.

Is a headless CMS worth it for a small business?
Only when several people publish regularly or the site needs to go beyond what a template builder allows. A small, rarely changed site doesn’t need one.