Grav CMS: file-based content and editing
Assess Grav CMS for a retail content site. Check file-based content, editor access, themes and plugins, with a clear plan for publishing and recovery.
- Published
- Last updated
Grav CMS suits a small retail publication when you want content in files and have a developer responsible for the publishing setup. Editors can use a browser interface, while the developer controls how those files become pages. File storage makes the authored text portable, but you still need permissions, a review process and recoverable backups.
Understand Grav’s content structure
Grav stores pages as Markdown files with YAML frontmatter, which holds settings such as the title and taxonomy. Its page documentation explains how folders organise content and how the Markdown filename selects a matching theme template. For example, guide.md can use a guide.html.twig template.
A retail buying guide can hold its advice in Markdown and its product references in named frontmatter fields. Keep a stable product identifier alongside each reference. That gives the template a way to connect advice to the catalogue without treating a copied price as authoritative.
The core platform reads content and renders the site. Themes control presentation, while plugins add behaviour. These responsibilities remain separate from the interface editors use.
Grav 2 uses Admin Next, delivered by the Admin2 plugin and backed by the first-party Grav API plugin. The administration overview explicitly distinguishes this interface from Admin Classic for Grav 1.x. An inherited site’s version therefore changes which admin instructions apply.
Give editors the right controls
Use page blueprints to define the fields an editor can maintain. Grav’s blueprint system defines page forms as well as plugin and theme settings. A developer can give a buying guide fields for its category, product references and a reusable policy reference, alongside its main text.
Admin Next renders blueprint fields with validation and includes page media controls. It also exposes raw frontmatter through Expert mode. User management has a permission tree, so assess access with an editor account instead of assuming the form itself prevents unwanted changes.
For a hypothetical mattress guide, let the editor change the buying advice and select product references. Keep the approved returns wording in one policy page. Have the theme render that shared text wherever it is needed, so an editor does not maintain separate copies in every guide. This reuse needs an implemented template or extension and an agreed reference convention.
Give the policy approver access to the relevant content without granting routine plugin or system configuration access. Test whether the editor can upload the intended image and save a valid guide. Then attempt a restricted configuration change with the same account.
Choose a revision process explicitly. A saved file is the latest content, but your approval record must identify which version was reviewed. If you use a repository, decide how browser edits enter it and how conflicting edits are resolved. File-based storage alone does not establish that workflow.
Turn a file change into published guidance
Decide whether editors save directly to the serving site or to a separate authoring copy. A direct save can affect customer-facing content without a later deployment. A separate copy needs a defined transfer step and a way to preserve edits when code is released.
Use one policy change to prove the whole path before handing the site to editors:
- Save revised returns wording in the authoring copy and record the approved file version.
- Preview the policy page and a guide that reuses it. Confirm that both display the same wording.
- Transfer the approved files through your release process, preserving unrelated content changes.
- Refresh the relevant caches and inspect both public pages while signed out.
Grav has a command-line cache clear operation. Include any separate hosting cache in the release procedure. If the policy page changes but the guide stays stale, check its reuse logic and cache before editing a second copy of the policy.
Keep credentials, account files and backup archives outside customer-facing content. Configure the web server to deny direct access to private files, then check that denial independently of the page template. A page missing from navigation is not an access rule.
Maintain plugins and recover the site
Grav 2’s runtime requirements specify PHP 8.3.11 or later, with required PHP modules and suitable web-server permissions. Hosting must support the actual release you choose. The absence of a content database does not remove runtime updates or writable-file risks.
Before adding an extension, examine its supported Grav and PHP versions and its maintained release history. Keep an inventory of the plugins and theme customisations the site relies on. Test updates on a separate copy with a buying guide, shared policy text and media uploads before updating the serving site.
Grav’s backup system supports profiles with file exclusions and scheduled backups. Configure the schedule deliberately: its documented default profile is not automatically scheduled. Keep an off-server copy and protect account data included in the archive.
Practise recovery into a separate location. Restore the content, media and configuration with compatible theme and plugin versions, then check navigation, shared policy text and editor access. Markdown remains readable outside Grav, but template logic and custom fields need mapping when moving elsewhere. Choose Grav when your team can own that operating work as well as the files.
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.