When off-the-shelf doesn't fit the content model
Custom CMS builds for content structures that don't map cleanly onto WordPress, Shopify, or any off-the-shelf platform.
Where this usually breaks down
Most content management problems get solved by forcing an unusual content structure into a platform that wasn't built for it - a listings site jammed into custom fields, a multi-dimensional catalogue flattened to fit assumptions the platform makes about what a 'product' looks like. It usually ships, but every workaround adds fragility, and the editor experience degrades as the mismatch compounds.
The tell is usually a support pattern - the same confusing workaround explained to a new hire every few months, or a 'quick edit' that actually requires touching three unrelated fields because the content model never matched how the content actually works.
What this service actually solves
Sometimes the right answer is to build a CMS around the content instead of the other way around. That doesn't mean a full custom application from scratch every time - flat-file systems like Grav, the platform running this site, give you a real admin interface and clean content modelling without the overhead of a database, and for genuinely unusual structures, a fully custom build gets the content model exactly right instead of approximately right.
A custom CMS is a content management system, often flat-file like Grav, built around a specific content structure that off-the-shelf platforms would otherwise force into an awkward workaround.
How we run it
We start by mapping the actual content relationships before picking a technology, because the content model is the hard part - the admin interface and hosting are comparatively easy once that's right. Where a flat-file system like Grav fits, we use it, since reinventing a CMS from scratch when a proven flat-file framework already does most of the job is wasted effort.
Capabilities & deliverables
Content Model Design
- Mapping real content relationships before choosing a platform
- Custom taxonomies that match how the content actually works
- Avoiding forced workarounds from day one
Flat-File CMS Builds
- Grav and comparable flat-file platform builds
- No database dependency where it is not needed
- Version-controllable content
Admin Interface Design
- Editor interfaces designed for non-technical users
- Custom fields that match the real content structure
- Preview and workflow tooling
Long-Term Maintainability
- Documentation of the content model and admin setup
- Architecture decisions made for a five-year horizon, not just launch
What's in scope, area by area
| Area | What we deliver |
|---|---|
| Content Model | A documented content structure and taxonomy built around your actual data |
| Admin Interface | A working editor experience non-technical staff can use without a developer's help |
| Platform | A built and deployed flat-file or custom CMS matched to the content model |
How an engagement runs
Content Relationship Mapping
We document how content actually relates - categories, taxonomies, cross-references - before touching any platform decision.
Platform Decision
We decide between a flat-file framework like Grav and a fully custom build based on how far the content model departs from what an existing framework handles.
Content Model Build
The taxonomy and content structure are implemented to match the mapping exactly, not approximately.
Admin Interface Design
The editor experience is built around how your non-technical team actually needs to work day to day.
Testing & Handover
We test the admin experience with the actual people who will use it, not just internally, before handover.
Documentation & Maintainability Planning
You get documentation of the content model and admin setup so a future developer is not starting from zero.
How this compares
| Custom-Fit CMS | Forced Off-the-Shelf Platform |
|---|---|
| Content model matches how the data actually works | Content model bends to fit platform assumptions |
| Editor workflow reflects real day-to-day tasks | Editors work around awkward custom-field patterns |
| No database overhead for genuinely simple content needs | Full database and admin overhead regardless of actual need |
A custom or flat-file CMS is not automatically better - for a standard content model, it is more work for no benefit. It earns its cost when the content genuinely does not fit an off-the-shelf pattern.
What this changes for the business
- Editors stop working around a content model that was never actually built for their content
- New content types can be added without retrofitting a platform assumption that does not apply
- Hosting and security overhead drops where a database was never actually necessary
Who needs this
Content structures that keep getting forced into workarounds
Repeated awkward custom-field patterns are usually a sign the underlying platform is the wrong fit.
Teams that want full control without database overhead
A flat-file CMS gives real editing capability without the hosting and security surface of a database-backed platform.
Related work
We're still building out published proof for this specific service — ask us directly and we'll walk through relevant examples.
Common questions
If your content keeps getting forced into custom fields that do not really fit, or the editor experience requires workarounds to do simple things, that is the signal. Most content genuinely does fit WordPress or similar platforms - custom CMS work is for the exceptions, not the default.
It's differently capable, not universally less. Flat-file systems handle content-driven sites extremely well and remove database overhead entirely - they are a worse fit for high-volume transactional data or real-time multi-user editing at scale.
We design the content model to be portable where possible, but a genuine outgrowing of the platform is a real migration, not a quick patch. We would tell you honestly if that point was approaching rather than stretching the original build past its limits.
Longer, generally - a custom content model and admin interface takes more time than configuring an established platform. The exact timeline depends on how far the content structure departs from anything off-the-shelf.
We cannot guarantee ease of use in the abstract, since that depends partly on how your team adapts to a new interface. What we can do is design the admin experience around the actual tasks your team performs, which is the biggest lever for making a CMS feel easier rather than harder.
Fighting an off-the-shelf CMS that was never built for your content?
We'll map your actual content model before recommending a custom or flat-file build.
Talk to us →