Concrete CMS

Concrete CMS is a PHP content management system where editing happens directly on the page. Rather than navigating to a backend editor and previewing changes separately, editors click on a content block in the browser, make their edits inline, and publish from the same view. For organisations with non-technical content teams, this eliminates the disconnect between the admin panel and what visitors actually see.

The block system is the building unit for pages. Text blocks, image blocks, video embeds, forms, and custom block types are placed and arranged within layout areas. Each page has a version history, so any change can be reviewed, rolled back, or routed through an approval workflow before it reaches visitors. For regulated industries, government agencies, and universities with compliance requirements around content changes, this is a core feature rather than a nice-to-have.

Multi-language support is built in, not an add-on. A site tree can have language variants, and editors manage translations through the same in-context interface. Multi-site configurations allow a single Concrete CMS installation to serve multiple domains with separate content and separate user permissions.

The community edition is MIT licensed with no feature restrictions. The commercial platform adds cloud hosting and support, but for self-hosted use, there is no paywall on core functionality.

The limitation is ecosystem size. With 837 GitHub stars and a smaller developer community than WordPress or Drupal, the add-on marketplace is narrower and less actively maintained. Custom development is the answer for integrations that do not have a ready-made add-on, which raises the technical barrier for teams without a PHP developer.

Concrete CMS: Pros & Cons