CMS or website builder: choosing a foundation

Who will add a service, change the composition, introduce another language or hand the project to a new team? List the real workflows. A small site may need a handful of simple pages; another project may need content types, custom components, integrations and several roles. Product categories overlap, so compare working scenarios rather than labels.

Ready-made compositions can be useful when they fit the brief. A bespoke theme lets you define typography, page structure, motion and component behavior. Ask to see complete pages: long text, galleries, mobile views, search and a 404. Check both implementation and maintenance of the design; a visual editor or code access alone is not enough evidence.

A small website can work with manually assembled pages. A substantial collection benefits from content types, required fields, repeatable blocks and an organized media library. Watch an editor create material, change a cover, edit navigation and prepare publication. Check export and programmatic operations if the workflow needs them. Progressive CMS separates structured content from the theme so design and editorial work can develop alongside each other.

Who owns the project, applies updates and restores it after a failure? Can a studio, editor or agent receive appropriate access? What happens when the first supplier leaves?

Self-hosting gives operational control and also responsibility. Managed products may cover some operations, depending on their actual terms. Compare development, content, infrastructure, support and migration costs rather than a license price alone.

Review a page with its own composition, an editor’s new article, a preview before publication, a second supplier’s access and handover to another team. Compare the result and how it will be maintained. Progressive CMS combines bespoke themes, content models and tools for people and agents. Test those capabilities against your requirements.