Websites

How to choose a website content management system your team can use

Compare editing tasks, ownership, security and portability before choosing the platform behind your website.

By Graphic Core   /   Published
Monthly guide series: September 2020

A stack of geometric blocks beside a laptop with a blank screen.

Start with editing jobs, not a product name

A content management system, or CMS, helps people create and update website content. Platforms differ in how pages are built, what can be changed without a developer and who manages software updates. The useful question is not which platform wins every comparison, but which one supports your team’s real tasks and responsibilities.

List the updates your business expects to make: changing an opening time, publishing an article, adding a project image or creating a new service page. Note who will do each task and how often. If the site needs booking, payments or customer accounts, include those journeys in the requirements rather than treating them as later surprises.

Ask to see a realistic editing demonstration

A demonstration should use the kind of change your team will actually make. Ask to update a heading, add a paragraph and image, check the page on a phone and publish or schedule the change. Include a task involving a reusable section if the proposed design uses them, so you can see whether editing one area affects several pages.

Give the controls to the person who will maintain the website, not just the project lead. Note the number of steps, the clarity of the labels and whether help is available when something goes wrong. A polished homepage preview cannot show how manageable everyday editing will be six months after launch.

Understand the hosting and maintenance model

Some systems are hosted and maintained as part of a managed service; others are installed on hosting arranged separately. WordPress, for example, can be hosted under different arrangements with different responsibilities. Ask who applies platform, theme and plugin updates, who monitors compatibility and what the support agreement actually includes.

Discuss backups, restore testing, security, certificates and access recovery. A managed platform can reduce some operational work, but the business still needs to understand account ownership, included support and what happens if the service changes. Do not assume that paying for hosting automatically includes content updates or repairs.

AT A GLANCE

Compare a CMS around the work it supports

  • EditingCan staff complete common changes?
  • CareWho updates and restores the site?
  • AccessWho owns and approves changes?
  • ExitCan content and assets be exported?
Use these questions in a demonstration of each platform you are considering.

Check access and approval controls

The people writing an article may not need permission to change all site settings. Ask whether the platform can provide appropriate roles for owners, editors and contributors, and whether publishing can be reviewed before it goes live. The exact options vary, and additional tools can change what is available.

Keep at least one reliable route for the business owner to recover access. Protect important accounts with unique credentials and additional sign-in protection where supported. Agree how an outside supplier receives access and how it will be removed at the end of a project. Avoid a setup that depends entirely on an individual’s personal account.

Test accessibility and content structure

Ask how the system handles headings, links, meaningful image alternatives, captions and form labels. A CMS can offer tools for accessible content, but the final result also depends on the theme, components and the way editors use them. Preview common content with a keyboard and test representative pages on different screen sizes.

Check whether editors can create a clear page structure without relying on text inside images or an inaccessible custom component. If a design uses a complex visual effect, confirm that the information remains available to people using assistive technology. Include accessibility checks in the project scope rather than assuming the platform guarantees compliance.

Compare costs and the ability to leave

Request a full cost picture: platform or hosting fees, paid themes or plugins, support, maintenance, backups and charges for new features. Compare renewal terms as well as introductory offers. Ask what happens if a required extension is no longer maintained or its subscription changes.

Before committing, ask what can be exported and in which formats: page text, images, product details, customer records and design components may have different routes. Some platforms are less portable than others. Confirm who owns the domain, content and commissioned files, and whether a future supplier could help without being locked out.

An illustrative choice for a small team

Imagine a Hertfordshire organisation with one person updating news and another approving service information. The team compares a managed website platform with a separately hosted CMS. Both can display the proposed design, but the team asks each supplier to demonstrate a news update, role-based approval, backup recovery and an export.

The organisation records the annual cost and who performs updates, then chooses the arrangement its staff can maintain with the support available. This hypothetical example is not a recommendation for a particular product. The decision might be different for an online shop, a single-page website or a team with dedicated technical support.

Questions to settle before sign-off

Who controls the platform account and domain? Can the team carry out its common edits? Who provides training, updates and backups? Are accessibility checks and third-party integrations included? What happens when a plugin, subscription or supplier relationship ends? Ask for the answers in writing and make sure they match the project contract.

Once the site is handed over, keep a short guide showing the ordinary editing tasks, approval route and support contact. Review access when staff change. A CMS should make accurate information easier to maintain; it should not leave the business dependent on an undocumented process or a single inaccessible account.

Run the same editing trial on each option

Prepare a small test brief with a heading change, a new image with suitable alternative text and a link to a relevant service page. Ask the person who will normally edit the site to complete the task on each candidate platform. Include a preview and an approval step, and check whether an accidental change can be reversed without technical help.

Then ask the supplier to show a backup or export route using the proposed account arrangement. Note which features depend on paid add-ons, which tasks require an administrator and what happens when a subscription ends. Compare the answers against the team’s capacity rather than a feature count. Keep the trial notes as part of the project brief so future training can focus on the steps staff actually found difficult. Record which account was used for the trial and whether an editor can access the same controls without being an administrator.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION