PHP CMS: choose the editorial and operating duties
Choose a PHP CMS for retail content by checking the supported runtime, editing workflow, publication and maintenance rather than the language label alone.
- Published
- Last updated
Choose a PHP CMS by the editing workflow you need and the environment your team can maintain. Kirby suits a site whose maintainers want file-based content and a tailored editor. Silverstripe suits a database-backed application with structured records and configured publication permissions.
Either choice needs an implementation that takes an approved correction to the public page. The PHP language label alone doesn’t tell you who owns that work.
Identify the supported PHP environment
Start with the PHP version running on the web server, then match it to the proposed CMS release. A host’s available PHP versions and the CMS’s supported versions must overlap. The command-line runtime can differ from the one serving your website.
The PHP support policy separates active support from security-only support. A runtime can still run a site after its support ends, but that doesn’t give your retailer security fixes. Include the next runtime upgrade in the maintenance agreement.
For Kirby 5, the requirements table distinguishes compatibility by point release. Later Kirby 5 releases support PHP 8.5, while the original Kirby 5 range starts with PHP 8.2 through 8.4. Record the exact CMS version instead of treating every Kirby 5 installation as identical.
Silverstripe CMS 6 requirements list PHP 8.3 through 8.5, required extensions and a database connector. Image processing also needs a supported image extension. The hosting proposal must cover those dependencies, along with file permissions and the public webroot.
Check the real hosting constraints before comparing editor screens. Confirm that the maintainer can install the required extensions and PHP can write content and uploaded media. Identify who controls runtime changes and restores backups. Shared hosting with a PHP label doesn’t establish those capabilities.
Compare the retail editorial task
Use one product guide, a reusable policy and a stable catalogue reference to compare Kirby with Silverstripe. The content model must let an editor correct the policy once and have every affected guide use the approved version.
Consider an illustrative furniture retailer. A dining-table guide explains timber care and links to a table through its catalogue identifier. A shared delivery policy appears in the guide and on a delivery-information page. The retailer changes the policy wording while keeping current prices and stock in its commerce system.
Kirby’s content model uses files and folders as its primary data source. Its Panel lets editors change content through a browser. The developer must define the guide fields and how templates resolve the reusable delivery policy. File-based storage still needs permissions, backups and a deployment process that preserves editorial changes.
Silverstripe stores content in database-backed records. Its versioning system separates draft and live content for pages. A custom reusable policy record needs the appropriate versioning and relationship configuration. A relationship to a record alone doesn’t establish how that record publishes with its parent.
Compare the proposed arrangements
| Decision | Kirby proposal | Silverstripe proposal |
|---|---|---|
| Guide editing | Panel fields defined for the guide | Page or record fields defined for the guide |
| Reusable policy | Shared content record resolved by the template | Related record with an explicit publication model |
| Catalogue link | Stable catalogue identifier stored in guide content | The same identifier stored in the guide record |
| Recovery | Restore content files and media with the matching application | Restore the database and assets with the matching application |
| Deployment risk | A code release must preserve files changed by editors | A release must preserve records and apply compatible schema changes |
API delivery is a separate decision from storage. A file-backed CMS can supply content to another application, and a database-backed CMS can render its own pages. Choose API delivery when a separate storefront needs the content and its team can own rendering and refresh behaviour.
Kirby’s REST API requires authentication and exposes management operations. A public content response needs deliberately limited fields and permissions. Don’t put an editor’s credentials in browser code to make the guide load.
The catalogue stays responsible for the referenced product. The guide can explain timber choices without becoming another source of price or availability. The same delivery correction must reach any public content a shopping assistant reads.
Check publication and public access
Check the saved draft, preview and anonymous public page as separate states. Editing a policy and seeing it inside the CMS doesn’t prove that shoppers receive it.
Kirby’s publishing workflow distinguishes draft, unlisted and listed pages. Unlisted pages remain accessible through their URL. Draft access can include secret preview links, so treat those links as controlled access. A renamed status isn’t proof of a separate approval permission.
In Silverstripe, pages have draft and live stages through versioning. The developer must apply the intended controls to custom policy records as well. Demonstrate the actual editor and publisher roles, including any approval extension selected for the project.
Run the furniture example in a non-production environment:
- Change the shared delivery policy, attach a guide image and save without publishing.
- Preview the guide with the proposed policy and media. Confirm the public guide still shows the approved version.
- Try publication with an editor account that lacks that permission, then publish with the authorised account.
- Open the guide and delivery page without a staff session. Check the wording and image, including any separate storefront cache.
- Restore the earlier approved content and confirm both public pages recover together.
Detect publication failures
| Failure | What the customer receives | What the operator checks |
|---|---|---|
| Update fails to save | The existing public policy remains | Save error and whether the intended draft exists |
| Draft is unpublished | Approved public wording stays in place | Draft visibility and publication permissions |
| Public content is stale | Older wording persists after release | Published version against page output and cache state |
| Media is missing | A controlled fallback avoids a broken guide | File availability, permissions and published references |
| API request fails | A designed error or permitted saved version | Delivery response and consuming application logs |
Agree whether a saved older policy is safe to serve during an outage. A materially incorrect delivery promise needs a different response from a missing decorative image.
Assign the ongoing work
Compare the complete maintenance agreement for the same site and editorial team. Kirby’s licence agreement requires a paid licence for a public site and defines the included update rights. Silverstripe’s core is open source under the BSD licence, as described in its contribution policy. Hosting and implementation support remain separate costs.
Name the owner of each dependency in the proposal:
- Your implementation partner owns templates, content relationships and publication configuration.
- Your hosting operator owns PHP patching and the required server services under the hosting agreement.
- Your CMS maintainer owns product and extension upgrades, including compatibility checks before installation.
- Your operations team owns recoverable backups of content and media, plus restoration of the matching application.
- Your content lead owns staff permissions and acceptance of the restored public policy.
Include extension licences and ongoing support in the comparison. A feature available through an add-on needs a maintained version compatible with the selected CMS and runtime. The core product’s licence doesn’t establish that add-on’s entitlement.
Choose Kirby when your team wants file-based content and can maintain the tailored fields and publication controls. Choose Silverstripe when its database-backed records and configured draft-to-live workflow fit the application. Require the chosen maintainer to demonstrate the shared policy correction, a restricted editor and a working restore before accepting the operating agreement.
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.