Choosing a CMS: An Honest Guide to Getting It Right

The question we get asked most often is not 'how do I build a website' but 'which CMS should I use' — and most answers online are really an argument for whichever platform the writer happens to sell. A content management system is the software your team uses to publish and edit pages without touching code, and the right one depends far more on who will run the site than on any feature list. Here is how we think through the choice, honestly, before a line of code is written.

There is no default answer, and anyone who has one is selling

The most common mistake in CMS selection is starting from the platform instead of the team. WordPress, Joomla, Drupal and Ghost are all good software; they are simply good at different things. We start from your side of it — how often you publish, how many people edit, how complex your content really is, and how much technical help you will have day to day. Only then does a platform recommendation mean anything, and our CMS development work is built around giving that recommendation without a house preference quietly tilting it.

Match the platform to the people who use it

The people who live in the admin every day should decide more of this than the developers do. A small marketing team publishing a few posts a month is well served by WordPress, which has the gentlest learning curve and the broadest ecosystem behind it. An organisation with strict permissions and multiple languages leans toward Joomla or Drupal. A writer or newsletter publisher who wants to focus on words rather than plugins is usually happiest on Ghost. Matching the tool to the people who use it is what keeps a site alive and updated, instead of quietly abandoned after six months.

Built to each platform's own standards

A CMS chosen well can still be built badly, and that is the failure mode we inherit most often: a site assembled from a marketplace theme and a stack of overlapping plugins, where the next core update breaks something and nobody can say why. We build themes, templates and extensions to each platform's own coding conventions, so updates are routine rather than a gamble every time. Boring, standards-compliant engineering is exactly what you want underneath a site you intend to keep for years, not months.

SEO foundations, whichever platform you land on

Search visibility is decided by structure, not by the logo on your CMS. Every build ships with clean, semantic markup, one H1 per page, a heading hierarchy that mirrors the content, schema where it applies, and an XML sitemap — the same groundwork our engineers run through in our technical SEO checklist. Doing this at build time is nearly free; retrofitting it onto a finished site is slow and expensive. That is why we treat it as part of the scope from the first commit rather than an upsell after launch.

Migrations that keep the rankings you earned

Moving between platforms is where sites quietly lose traffic they spent years building. A migration done properly carries across content, media and structure, and — most importantly — maps every old URL to its new home with 301 redirects, so search engines and bookmarks still land in the right place. We plan that redirect map before touching the new build, because a handsome new site that dropped your rankings is a failure however good it looks. The care is in the boring parts nobody sees.

Ownership, training and what it costs

You own everything at the end — code, content and every account — with the IP assigned in writing, and every build includes a training session on the actual admin you will be using, so routine changes never require a developer on call. Cost depends entirely on platform and scope: a hosted setup is far cheaper than a custom Drupal build, and we quote a fixed, itemised number once the platform is settled. If you want the wider picture on pricing, our breakdown of what a website actually costs uses the same honest framing we apply to every quote.

The right CMS is the one your team can run without us, on foundations that survive the next update — and choosing it well is mostly a matter of asking the right questions before the build begins. If you would rather have that conversation with someone who has no platform to push, our CMS development service starts with exactly that recommendation, and a fixed quote once it is made.