Skip to content
02.c Software & Plugins

Concrete CMS add-on development
blocks and tools your editors can use visually

Concrete CMS add-on development is the work of building custom blocks and add-ons that editors can use without code.

Built by us: Concrete Blocks Suite

Concrete CMS builds pages from blocks. A block is an editable element that visitors see on the page, and editors place it in an area of the page and fill it in. When the standard blocks don't cover what your pages need, a custom block gives your editors a new building piece without asking a developer each time.

True Media Design builds Concrete CMS add-ons: content blocks, page-building tools, and packages that bundle them. Our own add-on, Concrete Blocks Suite, comes with 45 blocks and an AI chat assistant. This page belongs to our Software & Plugins service.

Hands arranging paper cut-out blocks, one of them orange, into a page layout on a white table

Where Concrete CMS code can live

Concrete CMS lets you add functionality in a few ways, and the right one depends on how widely you want to use it. Here is how they compare:

Format What it is How it reaches the site
Custom block A block type made for one site Lives in the site's own application folder
Package A bundle of blocks, themes, and other components with its own controller Installed from the Dashboard under Extend Concrete, and upgraded through a version number
Custom block template An alternate look for an existing block Added to the block's templates folder, then chosen by editors in the editing interface

What we can build

Content blocks and page-building tools that editors use visually, without code, packaged so they install and upgrade like any other Concrete CMS add-on. Concrete Blocks Suite is our own example.

The parts of a well-built add-on

01

Block files that follow the Concrete structure

  • A controller and a view template, which every block needs
  • Add and edit forms, so editors can fill in the block
  • A database definition when the block stores its own data
02

Templates for different looks

  • Custom templates that editors can pick for the same block
03

A package that manages itself

  • A package controller with a handle and a version number
  • Install, upgrade, and uninstall steps
04

Page type support

  • A composer template, when the block should appear in page type forms
05

Caching rules

  • Cache settings in the block controller, which can be changed per block in edit mode
06

Translatable names and labels

  • Block names and descriptions prepared for translation

Common problems and how to solve them

Forms that confuse editors

ProblemThe add and edit forms are what editors see every day, and an unclear form leads to wrong or empty content.

Solution
  • Keep the fields few, named in plain language, and in the order editors think about the content
  • Share one form between add and edit, so both behave the same way

Upgrades on live sites

ProblemA new version needs a new block or table, and reinstalling the package could lose data.

Solution
  • Raise the package version and add an upgrade step, so administrators see the update and data stays in place

Cached output that goes stale

ProblemA block that shows changing content is cached, and visitors see old data.

Solution
  • Set the caching rules in the block controller to match how often the content changes

Tables left behind after uninstall

ProblemBlocks and themes are removed with the package, but custom database tables stay.

Solution
  • Add an uninstall step that removes the custom tables, where that is what you want

What to prepare before an add-on project

  • Your Concrete CMS version, and whether the add-on is for one site or several
  • The content the block should hold, field by field
  • Who edits the pages, and how comfortable they are with the editor
  • Whether the block should appear in page type forms
  • The theme the blocks need to match

The first step is the audit, with its steps described in the Analyze Report. Each of our tools, apps, and plugins has a site where you can buy the right license.

Proof: an add-on we built for ourselves

Tray of page design blocks, with several already placed into a web page layout
Available

Concrete Blocks Suite

45 blocks and an AI chat assistant for Concrete CMS.

More products are listed on our Products page.

Common questions

Didn't find your answer? Write to us and we'll reply.

Contact us
Can editors use the blocks without a developer?

Yes. Blocks are built for editors: they add them to a page from the editing interface and fill in the fields.

Can one block have more than one look?

Yes. A block can have several templates, and editors choose between them in the editing interface.

How do updates reach my site?

An add-on built as a package carries a version number. When a newer version is available, Concrete CMS tells administrators, and the package runs its upgrade step.

Do you also build add-ons for WordPress?

Yes. See WordPress plugins.

Let's talk about your blocks

Tell us what your pages need and which Concrete CMS version you run. You can reach us through the contact page.

Request a quote

Questions about plugins, add-ons, and tools are welcome, and we are happy to look at your specific setup. You can also check our FAQ section for answers to common questions about our services.

Contact us

IRIS - Your AI Assistant

This assistant uses AI to answer your questions. Your messages are sent to an AI service to create the answers and are saved on this website for 90 days, then deleted automatically. We do not save your IP address; a short-lived code made from it is kept for up to one day to limit abuse. When you start the chat, a random number is stored in this browser so that you can delete your conversation. Do not share personal or sensitive information. You can delete this conversation at any time from the chat menu.

Messages may be sent to: Anthropic (Processed globally or in the United States.)