Kirby CMS: files, editing and retail content delivery
Assess Kirby CMS for retail content by following a page from its files and editor to publication, with clear commerce boundaries and maintenance duties.
- Published
- Last updated
Kirby CMS stores content in files and gives editors a browser-based Panel configured for their site. It suits a retailer that wants tailored content structures and has a maintainer for the templates, publishing path and updates. Assess that arrangement by following one product-care correction through to the version customers receive.
Identify the Kirby setup
Identify the production release and where Kirby renders or supplies the content before assessing the editor’s screen. The Kirby release list distinguishes Kirby 5 releases from the Kirby 6 beta. A preview feature demonstrated in a proposal is not evidence that the production release includes it.
Kirby’s content documentation describes a folder-based page structure, text content files and media stored beside page content. The Panel edits that content through a browser. Its fields and layout come from developer-maintained blueprints, so two Kirby sites can give editors different controls.
Ask the supplier to identify the deployed release, supported PHP runtime and installed extensions. Have them show where production content lives, who can write to it and how it is backed up. These answers establish whether an editor’s saved change reaches production directly or waits for a separate transfer.
The delivery route needs the same detail. Kirby can render pages with templates or supply another format through content representations. In a headless arrangement, a separate front end consumes that output. Its build, cache and deployment can delay a correction after Kirby has saved it. Include those components in the proposal’s responsibilities.
Maintain the product guidance
Model retail guidance as editable records with explicit references to shared policies and commerce products. Avoid making editors repeat the same policy inside every care page.
Consider this hypothetical arrangement for a homewares retailer. A care page contains washing instructions and an image. It refers to one shared returns-policy record and a stable product identifier from the commerce catalogue. The rendering code resolves those references when it prepares the customer-facing page.
The blueprint guide explains how fields structure content and how reusable definitions configure the Panel. Ask the maintainer to demonstrate the proposed care-page fields and product-reference control. A text box containing a product code needs different validation from a control that checks a live catalogue.
Correct the care instructions in the Panel, save the change and complete the configured publication step. Then open the public page in a signed-out session. Check the corrected sentence and image caption, including any separate content output used by other channels. Change the shared policy once and confirm every dependent page displays the new wording.
Keep price and available stock with the commerce system. Orders remain there too. The Kirby record can point to a product without becoming the authority for its availability. Require a defined result when that reference no longer resolves, such as removing its product card while retaining useful care instructions.
Check publication and recovery
Kirby distinguishes drafts from public pages, but an unlisted page is still public at its address. Its publishing workflow also permits blueprint-specific state labels and restrictions. A label such as review needs a demonstration of the permissions behind it.
Use an editor account to attempt a restricted publication, then use the authorised publisher account to complete it. Check draft access while signed out and test any shared preview link separately. Inspect direct media addresses as well as the page, because hiding a navigation item does not establish media privacy.
Run the following recovery exercise on a disposable copy of the proposed site:
- Remove a sample product reference and publish. Confirm the public page handles the missing reference without showing a broken product card.
- Restore the intended content and its original media from the backup. Include any configuration and extensions needed to read those records.
- Rebuild or refresh the delivery layer when the arrangement requires it. Confirm the restored page, image and product reference from a signed-out browser.
A copied content folder proves that files can be copied. The exercise proves whether the maintainer can restore the customer-facing result. Record who handles a failed transfer and which previously published version remains available during recovery.
Budget the operating work
Separate the Kirby licence from hosting and maintenance when comparing proposals. The licence purchase page distinguishes licence options and update entitlements. The supplier’s quote must identify the applicable licence and any separately charged extensions.
Include the initial content model and templates, catalogue-reference work, editor training and backup setup. Recurring work covers hosting, supported runtime updates, Kirby and extension updates, recovery checks and support. Name the person responsible for changing a blueprint when the retailer needs a new field.
Kirby’s security guide assigns work to the installation and hosting setup, including supported software and production configuration. A file-based content store still needs that work funded. Accept the proposal when an editor can correct the sample guidance, the published result updates through the agreed path and a named maintainer can restore it.
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.