What Is a CMS? Types, Tool Comparison, and Selection Checklist
Shusaku Yosa

A content management system (CMS) stores, edits, organizes, and publishes content such as articles and images. Before choosing one, define who updates content, who approves publication, and who maintains the system. An easy editor is useful, but architecture, permissions, cost, and migration also determine whether the system fits.
How a CMS publishes content
The basic flow is editor → stored content → delivery website → reader. A coupled CMS often generates the website's HTML. In a headless architecture, a separate frontend receives content through APIs and builds the user interface.
Routine editing may need no code, while initial setup, design changes, data-model changes, and frontend development can require technical support. Define the actual boundary rather than saying a CMS removes the need for developers. Start by listing the content types you need to manage.
CMS categories describe different dimensions
Dimension | Examples | Decision |
|---|---|---|
Delivery and operations | SaaS, self-hosted, managed hosting | Where it runs and who operates it |
License | Open source, commercial terms | Conditions for use and modification |
Architecture | Coupled, headless, mixed | How content and presentation connect |
These are not mutually exclusive choices. A system can be open source, self-hosted, and headless. WordPress exposes a REST API, so it is not restricted to one presentation architecture.
Compare responsibilities, not popularity
Example | Architectural characteristics | Investigate |
|---|---|---|
WordPress | Commonly coupled; REST API also available | Hosting, plugins, updates, compatibility, existing publishing assets |
Payload | Open source and self-hostable, with API-based content architecture | Application, database, storage, delivery, and maintenance ownership |
Contentful | Content delivery through APIs | Separate frontend, plan limits, permissions, and migration |
This is not a ranking. Workflow, localization, preview, permissions, and usage limits depend on the selected product, host, plan, and implementation. Review Payload's deployment requirements and Contentful's Content Delivery API and GraphQL API before assuming a required feature is included.
Write a requirements sheet
Requirement | Define | Test |
|---|---|---|
Editors | People, frequency, skills, external contributors | Can the actual editor complete a task? |
Approval | Draft, review, scheduling, rejection | Can unapproved content escape? |
Permissions | Editing scope and offboarding | Use a restricted account |
Languages | Owners, URLs, untranslated states | Translate and preview an update |
SEO | Metadata, canonical, sitemap, redirects | Inspect published behavior |
Migration | Articles, images, authors, dates, URLs | Export and import representative content |
Maintenance | Updates, backup, support, recovery | Restore a tested backup |
A CMS change does not automatically improve rankings. Check whether it can implement and maintain the needed controls with the SEO checklist. Compare measurement requirements with the GTM management guide.
Compare three-year total cost
Use the same cost scope: initial design and build, migration, three years of service and hosting, maintenance, additional development, training, operations, and eventual exit. No fictional vendor price is needed; obtain estimates for your own requirements.
- Licenses, users, API usage, storage, and transfer limits.
- Frontend, design, forms, search, and integrations.
- Updates, backups, monitoring, incident recovery, and internal time.
- Content migration, URL mapping, training, and documentation.
- Export and rebuild requirements if the contract ends.
A free license does not make operation free. SaaS does not necessarily include your custom website development or every operational task. Make the service provider's and your team's responsibilities explicit.
Run the same trial in each candidate
For a fictional evaluation task, create a Japanese article, add an English version, insert a table and links, have another person approve it, and restore a previous version. Record technical intervention, validation quality, and workflow limitations as well as editing time.
Before migration, preserve URLs, images, publication dates, authors, categories, and search settings. Prepare the old-to-new URL map, test environment, and rollback conditions. CMS selection should be a joint decision between editorial, development, and operations teams.
When using Xtrategy to manage the project, separate build, migration, training, and ongoing costs in the budget review, and assign each validation task to an owner.
Test delivery and recovery, not only editing
In a headless implementation, saving content and delivering a new public page can be separate steps. Test draft previews, scheduling, cache updates, and restoring a previous version with the actual frontend. Define what “published” means and who investigates delayed delivery.
A backup policy also needs a restore test. Check the database, files, required configuration, recovery environment, and export format. If one person maintains the system, include documentation and a second responsible person in the handover requirements. These checks often reveal costs and dependencies that a simple editor demonstration misses.