CMS

A CMS is the software that stands between your content and your database so a human who does not write code can still publish. It exists because hardcoding every headline into raw HTML stopped scaling somewhere around 2005, and someone other than the engineer had to own the words. A CMS gives editors a form, a preview, and a publish button, then quietly handles storage, versioning, and delivery underneath.

The word covers a huge range. WordPress, launched in 2003, still runs somewhere north of 40 percent of the entire web. But the category split hard after 2015 into two camps that barely resemble each other anymore, and knowing which camp you want is most of the decision.

A CMS is not a website. This trips people up constantly. The CMS holds and structures your content, and a separate layer decides how it looks and where it renders. Old monolithic systems fused the two together, which is why editing a legacy WordPress theme feels like pouring wet cement over your design. Modern setups keep the two apart on purpose.

The real divide is headless versus visual. A headless CMS like Sanity or Contentful stores content as pure structured data and serves it to any front end through an API, with zero opinion about design. A visual CMS like Webflow or Framer bolts the editor directly onto the rendered page, so you change content in place, right where it actually lives on screen.

Say you run a product with a marketing site, an iOS app, and a smart TV app. Headless is the only sane choice, because one Sanity content lake feeds all three surfaces from a single source of truth. Contentful, founded in 2013, charges real money for this, its team tier starts around 300 dollars a month, which tells you exactly who it is built for: engineering orgs, not a solo designer.

Now say you are a designer shipping a 12-page agency site next week. A visual CMS wins outright. Webflow lets you define a Collection, wire fields onto the canvas, and hand the client an editor that cannot break the layout. Framer, which pivoted from prototyping to full site publishing in 2022, does the same with a lighter, faster feel and native CMS collections since 2023.

Reach for headless when content outlives any single front end, when several surfaces consume the same data, or when engineers own the build. The cost is real. You assemble the front end yourself, wire the API, host it somewhere, and nothing is visual until you build it. A five-page brochure site does not need any of that overhead.

Reach for visual when the person editing is also the person designing, and time to launch beats long-term portability. The cost there is lock-in. Your content, your design, and your hosting all live inside one vendor, so leaving Webflow later means rebuilding from scratch. Both Webflow and Framer export code, but that export is a rough starting point, not a clean handoff.

The interesting middle is Next.js paired with a headless CMS, where incremental static regeneration rebuilds only the pages that actually changed. You get the structured editing of Contentful and the raw speed of a static site, without a full redeploy for every typo fix. This is why so many 2025 marketing stacks converge on Sanity plus Next.js on Vercel.

First step before you pick anything: sketch your content model on paper. Count your content types, count the front ends that will read them, and count the non-engineers who will edit them daily. Those three numbers point at headless or visual faster than any feature comparison chart will.

Choose your CMS by answering one question: who edits, and how far does the content have to travel? A CMS is not where your website lives, it is where your words wait until something decides how to show them.