Concrete CMS is an open-source content management system designed around in-context page editing. Authorized editors can work directly with page content and reusable blocks, while administrators can manage page structure, users, permissions, versions and extensions. Bluechip Kenya can help assess, build or modernize a Concrete CMS website around your organization’s actual content and technical requirements.

Why Use Concrete CMS? 

  • In-context editing — Update page content while viewing the layout you are editing. 
  • Reusable blocks — Manage repeatable content components more consistently across the site. 
  • Page versions — Review previous versions and revert when necessary. 
  • Roles and permissions — Control which users can edit or administer specific areas. 
  • Extensions and custom development — Add functionality through carefully selected packages or custom code where justified. 
  • Integration options — Connect suitable external services or systems through supported integration approaches. 

What Bluechip Kenya Can Provide 

  • New Concrete CMS website development and setup. 
  • Theme implementation and front-end customization. 
  • Custom blocks, page types and packages where required. 
  • Extension installation and configuration after compatibility review. 
  • Upgrade assessment for older Concrete5 / Concrete CMS sites. 
  • Content migration and restructuring support. 
  • API or third-party integration where technically appropriate. 
  • Ongoing updates, backup, troubleshooting and maintenance under an agreed scope. 

Why Work With Bluechip Kenya 

Replace With: A CMS project should be planned around how your team will publish, review and maintain content after launch. Our approach focuses on requirements, editing roles, extension dependencies, integrations, hosting compatibility and maintainability before deciding what should be customized. Where an older Concrete5 installation is involved, we recommend reviewing the current version, PHP environment, theme, packages and backups before planning the upgrade route. 

Planning a Concrete CMS Project or Upgrade?

If you are building a new site or maintaining an older Concrete5 installation, Bluechip Kenya can review your current setup, content workflow and technical dependencies before recommending the next practical step.

Concrete CMS Development Services We Provide

Full Content: We can support new site setup, theme implementation, reusable blocks, page types, extension configuration, custom packages where justified, integrations, upgrade assessments, migrations and ongoing maintenance. Scope should be agreed after reviewing content, user roles, hosting and technical dependencies. 

When Concrete CMS Is a Good Fit

Concrete CMS can be a practical choice when editors value in-context page editing, the site uses reusable blocks or page structures, multiple users need controlled permissions, and the organization wants an open-source CMS that can be extended without turning every content change into a development task. If the requirement is primarily a simple brochure website or a heavily application-driven platform, another CMS or custom approach may be more appropriate.

Planning an Upgrade from an Older Concrete5 Site

Before upgrading, identify the current Concrete version, PHP/database compatibility, theme, packages, custom code, integrations and backups. Test the upgrade path in a staging environment, resolve compatibility issues, validate content and forms, then deploy with a rollback plan. Some legacy sites are better served by a staged rebuild rather than a direct in-place upgrade.

Concrete CMS Maintenance After Launch

Keep the CMS core, packages and hosting environment on supported versions. Maintain backups, test updates, review extension compatibility, monitor forms and integrations, and check performance or error issues after significant changes. Security depends on configuration and maintenance, not on the CMS name alone.

FAQ

Concrete CMS is the current name of the open-source platform previously known as Concrete5. Older websites, URLs and search terms may still use “Concrete5,” but current official documentation and releases use “Concrete CMS.” 

A project may include platform setup, theme implementation, reusable blocks, page types, permissions, package configuration, custom functionality, integrations, testing and launch support. The exact scope should be based on documented business and editorial requirements. 

An upgrade can be assessed, but the safest route depends on the current Concrete version, PHP/database environment, theme, packages and custom code. Older installations should be reviewed before deciding between an in-place upgrade, staged migration or rebuild. 

Yes, one of the platform’s core strengths is in-context editing. Authorized users can update page content and blocks without editing source code, although permissions and page structure still need to be configured carefully. 

Yes. Concrete CMS includes users, groups and permissions that can be configured for different responsibilities. The permission model should be planned around how your organization publishes and approves content. 

It can. Integrations may use existing packages, custom development or API-based approaches depending on the system involved. Integration scope should be assessed for authentication, data flow, security, maintenance and error handling. 

Maintenance normally includes core and package updates, backups, compatibility checks, performance review, monitoring of forms/integrations and keeping the hosting environment on supported software versions. 

There is no single CMS that is best for every website. Concrete CMS is attractive when in-context editing and its block/page model fit the editorial workflow. WordPress, Joomla, Drupal or a custom CMS may be more suitable for other requirements. Platform selection should follow the actual content, integration and governance needs. 

Planning a Concrete CMS Project or Upgrade?

If you are building a new site or maintaining an older Concrete5 installation, Bluechip Kenya can review your current setup, content workflow and technical dependencies before recommending the next practical step.