Concrete CMS: page editing and store content

Evaluate Concrete CMS for store guides and policy pages. Check page editing, permissions, extensions and the maintenance behind the finished site.

Concrete CMS is a content management system for teams that want to edit pages visually and control who publishes changes. For a retailer, it can manage buying guides and policy pages around an existing store. The commerce system still owns current stock and transactions.

Understand the page-editing model

Concrete CMS organises a site into pages with editable areas that contain blocks. Its current name is Concrete CMS. Older material uses concrete5, so match instructions and extensions to the version you intend to run.

The Concrete CMS site describes an open-source system for creating and publishing websites. Its page-building documentation explains how themes control presentation and blocks supply content or functionality. Editors place a text block or image block within the areas the theme exposes.

This model gives the developer a practical way to limit the editing surface. A category guide can have a fixed introduction area and a separate area for advice sections. The editor changes those sections without redesigning the surrounding navigation.

Shared stacks group blocks for reuse across pages. Use a stack for a short care-information panel that must stay consistent wherever it appears. Page-specific buying advice belongs in a local area so one edit doesn’t change unrelated guides.

Author permissions determine what an editor can change. Concrete’s advanced permissions distinguish actions on pages and can also apply to blocks and files. Give content staff the actions they need and reserve site administration for the people maintaining the installation.

Keep page content aligned with product facts

A buying guide holds authored advice, while the commerce system supplies the product facts that change with trading activity. Define that boundary before building a product block.

For a hypothetical garden-furniture guide, editors explain materials and care requirements in Concrete. A product card uses a stable product identifier to obtain the item’s current price and availability from the store. A copied price inside an ordinary text block will stay unchanged until someone edits it.

Specify what the product card does when an item is withdrawn. It can hide the card or show an explicit unavailable state, according to the retailer’s design. Don’t leave an old purchase link active because the guide itself still exists.

A delivery-policy page has a different content owner. Staff approve its regional rules and oversized-item conditions as editorial content. The status of a particular delivery comes from the order system. A shopper reading the policy must be able to distinguish a general delivery estimate from their order’s actual status.

Use one hypothetical oversized-item policy change to check the handover. Revise the policy as an editor, obtain approval and confirm the published page after a reload. If another service consumes that page, include its content refresh in the same check.

Check extensions and publishing controls

Choose extensions against a written requirement and the exact site version. A marketplace listing establishes that a package exists. It doesn’t establish compatibility with your theme, custom code or commerce connection.

For each proposed commerce extension, record which product fields it reads and whether it changes orders or stock. Distinguish an embedded purchase button from a connection that synchronises catalogue records. Include refresh timing, access credentials and failure behaviour in the implementation scope.

Concrete’s marketplace guidance separates keeping installed code from receiving future updates. Include renewal and support terms when comparing an extension with custom development. An old concrete5 add-on needs a supported upgrade path before it belongs in the proposal.

The Basic Workflow provides a single approval step in the core system. Enterprise Workflow supports more complex approval processes. Attach the selected workflow to the relevant page permissions so an editor’s policy revision reaches a reviewer before publication.

Concrete’s multilingual tools manage locales and corresponding page trees. They help organise translated pages, but the retailer still needs someone responsible for each translation. Include the delivery policy in every locale’s approval process.

The File Manager manages content assets with permissions and versions. Test replacing a guide image and downloading its associated care document with the intended visitor access. Include alternative text and image sizes in the content handover.

Maintain and move the site

A Concrete site needs a maintained hosting environment as well as an editing interface. Its system requirements cover PHP, required extensions and a compatible database. Match the runtime to the selected Concrete release and include its maintenance in the hosting agreement.

Assign responsibility for core updates separately from theme and extension updates. Concrete’s upgrade instructions require database and file backups, compatibility checks and testing on a copy of the site. Recovery uses the pre-upgrade backup because there is no downgrade process.

Page versions are useful editorial history. A recovery copy must also preserve the files and database needed to run the site. Test restoring that copy into an isolated environment before accepting the maintenance arrangement.

Moving the same Concrete site to another host requires its database and site files, with configuration adjusted for the destination. Moving to a different CMS needs a separate content export and mapping plan. Include reusable blocks and media in that plan so a page export doesn’t lose its dependencies.

Compare proposals by the work the retailer receives after launch. Name the person who restores a failed update, the person who repairs an extension and the editor who approves a policy change. Those responsibilities determine whether staff can keep the store’s content accurate after the original build is finished.

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