Backdrop CMS for publishers: a lighter descendant of Drupal 7

What is Backdrop CMS?

Backdrop CMS is a content management system forked from Drupal 7. Its site describes it as a simple, lightweight, easy-to-use system and as a modernised version of Drupal 7, created when its founders saw large changes coming in Drupal 8 and wanted to carry on with the Drupal 7 codebase. It is run as a non-profit project under the Software Freedom Conservancy, which holds the trademark.

The repository describes it as a full-featured content management system that allows non-technical users to manage a wide variety of content. It is GPL v2 or higher.

See the licence guide for how GPL licences work.

Who is Backdrop best for?

It suits small publishers, community sites and organisations, particularly teams that already know Drupal 7 and want to keep the same concepts without Drupal’s later complexity. The project says it targets everything from a single administrator’s personal blog to complex business sites, and names non-profit, educational, government and corporate websites as good fits.

It is a harder sell for a newsroom that needs a large pool of plugins, formal moderation out of the box or the widest choice of developers. Compare Drupal for scale and WordPress for ecosystem.

Editorial workflow

Backdrop’s features page lists permission-based access control and administration tools included in core. The core module list includes node, comment, taxonomy, menu, user, block, dashboard and book modules, so the basics of writing, categorising and managing users are there.

We found no moderation, workflow or scheduling module in the core list. Teams that need draft-to-review-to-publish stages or timed publishing should check for contributed modules, and verify how they behave, before choosing Backdrop. The 1.35.0 release added field group functionality to core, which helps organise long editing forms.

SEO, structured data and feeds

The features page lists automatic path aliasing for pattern-based URL generation, and the core module list includes path, redirect and search modules. That covers readable URLs, redirects and site search from core.

We did not find a core XML sitemap module, a meta tag module or structured data output in the sources we opened, and we did not verify RSS behaviour. Plan on checking contributed modules for sitemaps, meta tags and schema.org markup. Compare against Google’s own documentation, not an extension’s marketing page. The features checklist has the items to test.

Media, multilingual and performance

The core module list includes image and file modules for media, plus language, locale and translation modules for multilingual sites. We did not open documentation on how those work together, so we cannot describe the translation workflow.

The features page says Backdrop includes performance optimisation for shared hosting environments. We did not verify caching or CDN options. For a high-traffic news site, ask the project or your host about caching strategy, because the sources we opened say little about it.

Hosting and requirements

The requirements page says PHP 7.1 or higher (as of 1.31.0), MySQL or MariaDB 5.5.0 or higher (as of 1.30.0), and Apache, recommended, or Nginx. Apache needs mod_rewrite and AllowOverride All for clean URLs. The page does not mention PostgreSQL or SQLite, so a host offering only those would not fit.

Those are minimums. The page recommends a modern, supported PHP version and says Backdrop aims to work with the latest PHP releases, though contributed modules may lag behind. Choose your PHP version deliberately, test your modules against it and keep it supported.

Extending Backdrop

Backdrop has a community marketplace for add-ons, according to the features page, and an API for customisation. We did not verify the number of contributed modules, so we give none. Views and layouts are part of core, which reduces how many extras a typical site needs.

The configuration system is the distinctive feature for developers. All configuration is stored as JSON files, which can be exported and imported for part of a site, replicated across local, staging and live environments independently of content, and kept in version control. That suits a team that wants repeatable deployments. See our headless guide if you are considering a decoupled front end; we did not verify a core API for it.

What Backdrop costs

The licence is free. Hosting requirements are modest and the project says it is tuned for shared hosting, but we have not verified any host pricing. Add developer time for site building, theming, any needed contributed modules, and a Drupal 7 migration if applicable. We give no figures. See the cost guide.

Where Backdrop falls short

• The ecosystem is small compared with WordPress and Drupal, though we did not measure it.
• No core moderation, workflow or scheduling module appears in the core list.
• Sitemaps, meta tags and structured data were not found in core, so expect contributed modules.
• Database support is MySQL or MariaDB only, according to the requirements page.
• The stated minimums (PHP 7.1) are old, and contributed modules may lag on new PHP versions.

Checks before you commit to Backdrop

Run three checks on a staging install. First, list every feature your newsroom needs that is not in the core module list: moderation, scheduling, sitemaps, meta tags and structured data are the usual ones. Look for a contributed module for each and note its release status and how recently it was updated.

Second, test your host’s PHP version against the modules you plan to use, since the requirements page warns contributed modules may lag behind new PHP releases. Third, if you are migrating from Drupal 7, run the built-in upgrade path on a copy and count what breaks. Those three results will tell you more about the real cost than the licence or version number will.

The verdict for publishers

Backdrop is a sensible home for a small publication with Drupal 7 history or a team that values Views, layouts and configuration management in a lighter package. Its governance by a non-profit and GPL licence are in its favour.

For a newsroom that needs moderation, scheduling and strong SEO tooling out of the box, the gaps are real. Drupal and WordPress are the better-supported options. This profile rests on vendor documentation and the repository, not an install of our own; see how we test.