Custom Software & AI Development
Guardrails instead of a style guide — three conference sites live in four months
The National Association of Home Builders was launching conference websites on a legacy CMS that let content managers change fonts and colors on any page — so every event site drifted a little further from the brand. We replaced it with a platform where typography and core styling are locked into the CSS and everything else is theirs. Three conference sites have gone live since June 2026, and other departments are now asking for it.
3
Conference sites launched since June 2026
The problem
What they were dealing with
A conference website is not one website. It is a new one for every event, built quickly, usually by whoever on the events team has the time that week.
The legacy CMS handled that badly, and in a specific way: it was awkward to work in, and at the same time far too permissive. Content managers could change fonts and colors directly on a page — so they did. Not out of carelessness, but because the system offered it and a deadline was coming. Across a portfolio of event sites that produces steady brand drift, and no amount of recirculating the style guide corrects a system that invites the opposite.
The two faults compounded each other. A CMS that is hard to use pushes people toward the shortcut; a CMS with no guardrails makes the shortcut expensive. Brand consistency had become something people were asked to remember rather than something the platform could be relied on to produce.
Constraints
What made it hard, and what we did about it
- Challenge
- Content managers could alter fonts and colors on any page, so event sites drifted away from the brand
- What we did
- Core typography and styling moved into the CSS, where the page editor cannot reach them — a constraint the system enforces rather than a guideline somebody has to apply
- Result
- Brand consistency across event sites is now a property of the platform rather than an outcome anybody has to check for
- Challenge
- The legacy system was unintuitive, which was the reason people reached for the shortcuts in the first place
- What we did
- Everything that should belong to the events team — content, structure, imagery, the shape of a site — rebuilt to be fast and obvious to work in
- Result
- The team launches a conference site themselves, on their own schedule, without it becoming a project
- Challenge
- Event details already lived in the systems the events are actually run on
- What we did
- Connected to those systems by API rather than rebuilt alongside them
- Result
- Information is maintained in one place instead of being entered a second time for the website
How it ran
The approach
The useful question was not how to stop people changing the fonts. It was which decisions should belong to a content manager at all, and which should have been settled once, centrally, and then put out of reach.
Results
What it produced
3
Conference sites launched since June 2026
Stood up by the association's own team on the new platform
Three conference sites have gone live on the platform since it launched in June 2026, each one stood up by the association's own team rather than by us.
The more telling result is internal demand. Other departments have asked to move their own events onto it, without anybody mandating that they should. A platform that spreads on its own is usually one that removed friction rather than moving it somewhere less visible.
And the problem it was built for has stopped being a problem anybody manages. Brand consistency across event sites is now enforced by the system rather than checked for afterwards, which is the only version of it that survives a deadline.
What the client gained
Beyond the numbers
Consistency that does not depend on discipline
Typography and core styling live in the CSS, out of reach of the page editor. Staying on brand stopped being something anybody has to remember, police, or discover was missed after launch.
A new event site without a project
The events team stands one up themselves. Launching a conference site stopped being work that has to be scheduled with somebody else first.
Responsive without a separate pass
Every site the platform produces is fully responsive as built, so mobile is not a late check against a deadline that has already arrived.
One record of the event
Connected by API to the systems the events are already run on, so the same details are not maintained twice in two places that will eventually disagree.
Adoption nobody had to drive
Other departments have asked to move their own events onto the platform — which is the kind of spread that only happens when something removed real friction rather than relocating it.
Reference
Filed under
- Sector
Related reading
The thinking behind this
More work
Other case studies
Something similar on your side?
Tell us what you run today and we will tell you what we would look at first.