What Is a CMS? WordPress, Shopify and Friends Explained

Somewhere in the process of getting a website built, someone will ask you which CMS you want. If your honest reaction is "which what?", you are in good company — it is one of those industry acronyms that gets used as though everybody was born knowing it. CMS stands for content management system, and understanding it matters more than most technical terms you will encounter, because it decides something very practical: whether you can update your own website, or whether you have to email someone every time a price changes.

This guide explains what a CMS actually is, how the popular ones differ, which type suits which kind of business, and the ownership questions worth asking before you commit. No jargon without a definition, and no assumption that you have done this before.

The filing cabinet analogy

Imagine your website is an office. The design is the décor — the paint, the furniture, the layout of the rooms. The content is the paperwork: your text, images, prices, blog posts, product details. In a website built without a CMS, the paperwork is glued to the walls. Changing a single price means someone has to come in, peel it off, and reprint the wall.

A CMS is the filing cabinet. The paperwork lives inside it, neatly labelled, and the walls simply display whatever the cabinet currently holds. You open a drawer, swap a sheet, close it — and the office updates itself. Nobody has to touch the paint.

In practical terms, a CMS gives you a private admin area you log into. Inside, you see your pages, posts, and products in a form that looks more like a word processor than code. You edit, you press publish, and the live site changes. That is the whole idea: separating the content that changes often from the design and code that change rarely, so that updating one does not require touching the other.

This is why the CMS decision outlives almost every other decision in a web project. Designs get refreshed. The CMS is what you personally live with every week for years.

The popular systems, compared honestly

There are hundreds of content management systems. In practice, most small and medium businesses end up choosing between a handful.

WordPress is the most widely used CMS in the world, and it earned that position by being flexible. It runs everything from one-page brochure sites to large publications. Its strength is the enormous ecosystem of themes (ready-made designs) and plugins (bolt-on features — booking forms, galleries, SEO tools, and so on), which means most things you want to do have already been built by somebody. Its weakness is the flip side of the same coin: that flexibility invites clutter. A WordPress site with thirty plugins is thirty things that need updating and can conflict with one another. Well built and maintained, WordPress is superb. Neglected, it degrades faster than the alternatives. You can see what a properly structured build involves on our WordPress service page.

Shopify is a CMS built specifically for selling. Products, variants, inventory, payments, shipping rules, taxes, discount codes, and abandoned-cart recovery are all built in rather than bolted on. It is hosted for you, meaning Shopify handles the servers, the security patching, and the certificate renewals as part of the subscription. The trade-off is control and cost structure: you work within Shopify's framework, you pay monthly fees plus transaction charges, and heavily custom functionality can hit a ceiling. For most businesses whose core activity is selling products online, that trade is worth making — more on the specifics on our Shopify page.

WooCommerce is the e-commerce extension for WordPress. It turns a WordPress site into a shop, which appeals to businesses that already run WordPress or want maximum control over how the store behaves. You gain flexibility and avoid transaction fees; you take on responsibility for hosting, security, and keeping the whole stack updated.

Website builders such as Wix and Squarespace bundle the CMS, the design tools, and the hosting into one drag-and-drop product. They are genuinely good at getting a simple, tidy site live quickly with no technical help. Their limits appear later — with custom functionality, with performance at scale, and with moving elsewhere, since content built in a proprietary builder does not transfer cleanly.

Headless and custom systems are the option larger or more unusual projects reach for. "Headless" means the content store is separated from the presentation layer entirely, so the same content can feed a website, a mobile app, and a kiosk screen. It is powerful and it is not a beginner's choice — the flexibility comes with developer dependency.

Which one fits which business

Rather than asking which CMS is best, ask which set of trade-offs matches your situation.

If you mainly publish information — a service business, a consultancy, a clinic, a firm with pages and a blog — WordPress is the default for good reason, and a builder is a reasonable choice if the site is small and you want to manage everything yourself.

If selling products online is the core of the business, start from Shopify. The features you would spend a year bolting onto a general-purpose CMS are already there and already tested. Choose WooCommerce instead when you need unusual product logic, deep integration with existing systems, or you are already committed to WordPress for other reasons.

If you need to update things constantly — daily posts, frequent price changes, an events calendar, multiple people publishing — prioritise the quality of the editing experience above everything else. You will be in that admin area more than any visitor will be on your site.

If your site is essentially a digital brochure that changes twice a year, do not over-buy. A simpler system with fewer moving parts means less to maintain and less to go wrong.

If you are building something that behaves more like software than a website — accounts, dashboards, workflows, calculations — you have probably outgrown the CMS question and are looking at a web application instead. That is a different conversation, and a legitimate one.

One more consideration people underestimate: who will actually use it. If the person updating the site is not technical, the friendliest admin interface may matter more than any feature comparison. A powerful CMS nobody on your team is willing to log into is functionally a static website with extra bills.

The ownership questions to ask before you commit

This is the part that gets skipped, and the part that causes real pain two years later. Before agreeing to any CMS, get clear answers to five questions.

1. Who owns the site, and where does it live? With a self-hosted CMS like WordPress, the site is yours and sits on hosting you control. With a hosted platform like Shopify or a builder, you are renting a place in their system. Neither is wrong — but you should know which one you are choosing, because it determines what happens if you ever want to leave.

2. Can I export my content? Ask specifically: if I leave in three years, what do I get back, and in what format? Text and images should be exportable in a usable form. Proprietary page layouts generally are not — expect to rebuild the design, not the content.

3. Do I have full administrator access? You should hold the top-level login to your own website, your own hosting, and your own domain registrar, from day one. Agencies and freelancers can have their own accounts underneath yours. If any provider is reluctant to give you owner access to assets you paid for, treat that as a serious warning sign.

4. Who is responsible for updates and security? Hosted platforms handle the underlying system; self-hosted ones make it your responsibility, whether you do it or pay someone to. Either is fine as long as somebody has actually agreed to do it. The failure mode is everyone assuming it was the other party. Our website maintenance page sets out what that ongoing work involves.

5. Do I get the source files and design assets? Themes, custom code, logo files, and design source files should come to you as a matter of course. At TRODAD you get instant access to all design and source files on approval — no ransom, no chasing. Make sure whoever you hire commits to the same, in writing, before work starts.

Answer those five and you have removed the great majority of the risk in this decision — which is, after all, mostly a decision about who holds the keys.

Questions about your own situation?

Choosing a CMS is one of those decisions that feels enormous from the outside and becomes obvious once someone maps your requirements against the trade-offs. If you are weighing options — or you have inherited a site and are not sure what it is even built on — a short conversation usually settles it faster than a week of reading comparison articles.

Questions about your specific situation? Book a free consultation — no obligation.