← Knowledge Base • platform

Concrete CMS

An open-source CMS offering in-context editing for marketing sites and intranets.

What is Concrete CMS?

Concrete CMS (formerly concrete5) is an open-source content management system known for its intuitive in-context editing experience. It allows editors to click directly on page elements to edit them, making it accessible for non-technical users.

Originally developed in 2003 and rebranded in 2021, Concrete CMS serves organizations needing user-friendly content management with strong permission systems.

Free open-source version (MIT License) with commercial hosting and support options.

Architecture and Technology

Concrete CMS is built on PHP with Symfony components.

Core Components

  • Stacks/Blocks: Reusable content elements
  • Page Types: Structured page templates
  • Attributes: Custom metadata
  • Express: Custom data objects
  • Workflows: Approval processes

In-Context Editing

  • Edit directly on the live page
  • Drag-and-drop blocks
  • Real-time preview
  • Stack reusable content

Typical Use Cases

Concrete CMS is commonly used for:

  • Corporate intranets: Employee portals
  • Marketing sites: Brand and campaign pages
  • Government sites: Public sector needs
  • Educational institutions: School and university sites
  • Non-profits: Organizational websites

Strengths

  • In-context editing: Edit on the actual page
  • User-friendly: Accessible to non-technical users
  • Permissions: Granular access control
  • Workflow: Built-in approval processes
  • Open source: Free to use
  • Multi-language: i18n support

Limitations and Trade-offs

  • Market awareness: Less known than alternatives
  • Smaller ecosystem: Fewer add-ons
  • Performance: Can be resource-heavy
  • Developer community: Smaller than major CMSs
  • Modern features: Headless capabilities available via REST API

SEO, Performance, and Content Governance

SEO

Built-in SEO tools with configurable URLs and meta management.

Performance

Caching available. Optimization may be needed for larger sites.

Content Governance

Strong user permissions and workflow system. Version history.

Tips and Best Practices

  • Train editors on in-context editing
  • Use page types for consistent structure
  • Implement workflows for content governance
  • Explore marketplace for add-ons
  • Consider hosting options for support

Who Should (and Should Not) Choose Concrete CMS

Best Fit For

  • Organizations needing simple editing
  • Intranet projects
  • Government and education
  • Existing Concrete CMS users

Not Ideal For

  • Headless projects
  • Developer-focused teams
  • Maximum plugin ecosystem needs

Common Alternatives

Concrete CMS works well for organisations prioritising simple content editing.