Choosing a content management system, or CMS, means choosing how your team will keep a website useful. Beyond the first design, people need to publish pages, correct information, work in different languages and maintain the features their customers rely on.
A familiar CMS is not automatically the best choice for every project. The right fit depends on your needs, resources and the people using it. These questions help you compare options before committing to a platform or a redesign.
Start with people and everyday tasks
Ask the people who will publish content to try the same tasks: update a service, add an image with alternative text, prepare a French version and review a page on a phone. A guided demonstration is useful, but it does not replace this short practical exercise.
Define responsibilities too. Who can prepare a draft, review it, publish it or change site settings? WordPress roles and capabilities illustrate the distinction between editorial work and administration. Check the actual permissions in your chosen solution, including the effect of any plugins.
Your team should have an understandable way to handle routine work. Document the operations that need technical assistance instead of suggesting that every part of the site will be editable without help. The aim is useful independence, with a clear route to support when needed.
Compare a short list of requirements
A concise, prioritized brief is more useful than a long feature catalogue. Check the following for each option:
- Publishing: page types, documents, catalogues, revisions and approval before release.
- Languages: translated content, menus, forms and messages, with someone responsible for each version.
- Customer tasks: inquiries, bookings or purchases, according to your business.
- Connections: email, payments, customer management and other essential tools.
- Upkeep: accountable people, available skills and recurring costs.
Distinguish what is included, what needs a plugin and what requires development. Ask to see essential features working with your own example. You might compare a CMS installed on your hosting, a hosted platform or a more tailored implementation. Assess what each choice means for the people who will operate it.
Include accessibility in the decision
Accessibility matters to visitors and to the people editing the website. The W3C’s ATAG guidance identifies both aspects: access to the authoring tool itself and support for creating accessible content.
In your trial, check keyboard navigation, heading structure, form fields and ways to describe images. Observe what happens when an editor adds a long sentence or a table. A theme, plugin or marketing label does not establish the accessibility of the finished website; its implementation and content need evaluation.
Plan maintenance from the start
The cost of a CMS extends beyond its licence. Hosting, plugins, renewals, updates, testing and help for the team all belong in the budget.
Ask who follows security notices and who checks changes before they reach the public site. WordPress’s update guidance includes preparing a backup before an upgrade. The testing arrangements should reflect the importance of the website and its functions.
Choose plugins for a clear purpose and consider how they are maintained. For each one, you should be able to explain why it is there, who looks after it and what replacement would involve. Managed hosting and application maintenance are responsibilities to clarify together.
Check integrations and control of your data
A payment or business-system connection may matter as much as the visible pages. Establish which data is exchanged, which permissions are needed and who is notified when an exchange fails. Test the whole customer journey, including confirmations received by the customer and your team.
Clarify control of accounts, the domain, content, media and licences. Your business should know what it can retrieve, in which format and through which steps if it changes suppliers. Record who holds the necessary administrative access rather than discovering this during a future handover.
A WordPress export produces a content file; that file alone is not a complete copy of a working website. A WordPress site backup includes its files and database. The distinction matters for both migration and restoration.
Decide using a real example
Before choosing, compare two or three options using a representative page and an important customer task. Record what your team can do independently, where it encounters limits and what additional work is required. When replacing an existing site, include important addresses to preserve, media to transfer and integrations to check.
Tell Nuagerie about your project, including your current site, languages and publishing needs. Our website and application services can cover selection, implementation and maintenance within an agreed engagement. The goal is a website your team can evolve with clear responsibilities and a practical way to get help.
To go further, our sister brand Nuagiciel has a guide: Website redesign: where to start.
