A bespoke CMS for aumenso.com

aumenso.com runs on a content platform built specifically for it. Every page you are reading - the homepage, this case study, the service pages, the blog, the FAQ - is assembled in a bespoke admin from reusable sections, with the design system driving the theme rather than a fixed template.

It is not a WordPress install, and it is not a page of hard-coded markup. It is a small, purpose-built application that treats content as structured data.

Why we built it rather than installed it

An agency site has a specific shape: services, projects, long-form articles, FAQs written for two different audiences, and a contact funnel that has to be triaged. Off-the-shelf CMSs bend that shape into generic "posts and pages", and the result is a site that is technically editable but practically never edited.

So we modelled the site's own vocabulary instead: services, projects, articles, FAQs, testimonials, team members and categories - then gave each one an editing screen that matches how the team actually talks about it.

The content model

Every page is a document made of ordered sections. A section is a typed block with its own fields - a hero, a ticker, a two-audience split, a service grid, a portfolio list, an FAQ group, a closing call to action.

Because the blocks are typed rather than free-form HTML:

• the design cannot drift: a section only has the controls its design allows;
• content can be reordered, hidden or removed without touching code;
• the same block renders consistently on every page that uses it;
• structured data stays structured, so it can be queried, filtered and reused.

The blog, portfolio and FAQ all read from their own tables. Publishing a case study creates a real entry with its own URL, metadata and category - not a line in a WYSIWYG field.

A page builder, not a template

The homepage, the About page and the service detail pages all use the same builder. Changing the order of the homepage is a drag-free list operation in the admin, not a deploy. A section can be hidden while it is being rewritten and switched back on when it is ready.

Each page also carries its own SEO record - title, description, social image and an indexing flag - so a page can be tuned without a developer and without a site-wide rebuild.

Design tokens, one source of truth

Colour, typography and corner radius are stored as design tokens, not scattered through stylesheets. The theme editor writes those tokens once; the public site, the admin and every component read from them.

That means a palette change is a two-minute admin task, and a new page cannot accidentally introduce a shade that does not exist.

Publishing without a deploy

An editor can publish an article, reorder the homepage, add a testimonial or update the FAQ in the browser. There is no build step between the decision and the live page, and no queue of "content tweaks" waiting for the next release.

The same applies to the contact funnel: enquiries arrive in an inbox inside the CMS where they can be read, tagged, archived and answered without leaving the tool.

What it took

The build is a single application - no plugin marketplace, no page-builder add-ons, no theme subscription. The work was in the modelling: deciding what a service is, what a project is, which fields a section needs, and where editors should never be given a free-text box.

That constraint is the point. A CMS is not valuable because it lets you edit everything - it is valuable because it makes the right edits easy and the wrong ones impossible.