Backdrop CMS: editing, modules and maintenance

Evaluate Backdrop CMS for a retail content site. Check editing, layouts, modules and maintenance, with product and checkout records kept separate.

Backdrop CMS suits a retail content site when its built-in publishing tools meet your editors’ needs and someone owns the installation’s maintenance. It can keep buying guides and policies organised while your commerce platform owns product prices, stock and checkout. An inherited site is worth keeping when its content model remains usable and its extensions can run on supported hosting.

Check the Backdrop publishing model

Backdrop’s built-in content types, fields, layouts and menus cover the structure of a publishing site. Content types define the records editors create, such as a buying guide or policy. Fields hold their structured details. Layouts decide where page content and blocks appear, while menus control navigation.

The Backdrop user guide separates these functions from installing additional modules, themes and layout templates. For an inherited site, list which functions come from core and which depend on contributed or custom code. A feature visible in the editor can still depend on an extension that needs separate maintenance.

Create a guide content type with fields for the relevant category and guidance, plus a person responsible for updates. Keep product identifiers as references to commerce records. Copying stock quantities into an editorial page creates another value someone must maintain.

Set editor permissions around actual responsibilities. Someone who updates a sizing guide needs content access, while installing modules and changing layouts belong with the site administrator. Review the permissions assigned to each role before giving an editor a shared administrator account.

Keep guidance current across the store

A sizing change needs a saved revision, a publication decision and a check of every destination that uses the guidance. Backdrop’s content-type settings control whether revisions are available and created by default. Enable an appropriate revision policy before relying on the history to recover an earlier answer.

Consider this hypothetical update: a retailer corrects the garment measurements for a jacket range and changes its exchange instructions. The guide and policy have different owners, so each owner approves their part. Record which products the measurements cover and retain the earlier text through revisions.

Preview the revised guide in its layout, including the measurement units and links to the affected range. Confirm the policy wording agrees with the store’s approved exchange process. Publish each approved change, then inspect the public pages without an editor session.

Publication in Backdrop does not establish that a separately connected destination has received the change. If a product page copies the sizing text, update that copy or replace it with a maintained reference. If a shopping agent uses uploaded documents, refresh its approved source through that system’s process. Ask a sizing question and an exchange question there to confirm the corrected information appears.

Keep each destination tied to the approved revision or document version. This gives the team a way to distinguish a failed refresh from an error in the original guidance.

Review modules and maintenance

Use a supported hosting stack and a documented update process for the installation you will operate. Backdrop’s system requirements list PHP 7.1 or higher and MySQL or MariaDB 5.5.0 or higher. These are compatibility minimums. The documentation recommends a supported PHP version and warns that contributed modules can lag behind core compatibility.

Do not select an old runtime because it meets the minimum. Have the developer match the proposed supported PHP and database versions against core, the enabled modules and custom code. This assessment does not require adding an extension for ordinary guide publishing.

For each existing module, record its purpose, installed release and available updates. Review its project page for maintenance status and compatibility with the proposed runtime. Include any custom changes that would be overwritten during an update. Retire an unnecessary dependency only after checking the content or integrations that use it.

The Project Installer documentation describes update notices for core and installed projects. Assign someone to act on security notices. A notice appearing in an administration screen is useful only if a responsible person sees it.

Backdrop’s core update procedure includes backups and running database updates. Keep recoverable copies of the database, uploaded files, code and active configuration together. Test an update and restoration on an isolated copy before applying the change to the store’s publishing site. Include a published guide and its revisions in that recovery check.

Decide whether the existing site can stay

Keep the Backdrop site when editors can maintain the required guidance and the developer can support its dependencies without recurring workarounds. Compare that work with the full cost of replacing the publishing layer, including rebuilding layouts and reconnecting commerce references.

A useful decision record names the broken or slow publishing task, the focused repair and the ongoing maintenance owner. Replacing the site has a stronger case when essential custom code cannot be maintained or editors repeatedly need developers for routine changes.

Before committing to a replacement, establish how to extract content fields, media and relationships, plus revisions that must be retained. Preserve current page addresses or plan redirects, and identify which integrations need new source identifiers. A database backup supports recovery of the existing site. A transfer to another publishing system also needs a usable mapping of its content.

Use the CMS migration guide to plan that transfer if replacement wins. Make the decision on the work needed to keep approved retail guidance accurate across its destinations, then assign a person to maintain that process.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup