How to choose between a static website and a CMS

The right editing setup depends on who changes the content and how often. Decide that before choosing a platform. A small information site and a frequently updated publishing site can need different tools.

List the changes you expect

Write down actual tasks: replace a phone number, add a service, publish an article or manage a product catalogue. Give each an expected frequency and an owner. “We want to edit everything” is less useful than identifying the changes staff must make without a developer.

Try an editing task

Ask for a demonstration using realistic content. Watch someone update a heading, replace an image and preview the result. Check whether they can undo the change and whether page design can be accidentally damaged. WordPress provides page-management and editing tools; available interfaces depend on its setup and theme.

Understand the static option

A static site publishes prebuilt files. Content may be changed in source files or through an additional content workflow; do not assume there is a dashboard. Ask how an update is made, reviewed and deployed, and whether another developer could repeat that process from the handover.

Compare operational needs

Choose against your tasks

For an illustrative five-page site updated twice a year, developer-managed files may be practical. A team publishing weekly may value an editing interface. Neither example settles your choice: costs, support and required integrations matter too.

Record the chosen editing method in the quote. Ask for the relevant training or setup notes at handover. A website that looks custom may still rely on a CMS, and a static site may still connect to external services. Discuss those dependencies openly rather than choosing by labels alone.

Practical guidance with illustrative examples. Read our editorial standards or send a correction.