How a Digital Brand Stays Itself Since 2001: Lessons From The Chapel | Digital Marmalade [Skip to main content](#main-content) The web looked completely different in 2001. Flash introductions. Fixed-width layouts designed for monitors most people no longer own. No smartphones, no social media, no expectation that a website would work on anything other than a desktop browser sitting on a desk. Digital Marmalade has worked with The Chapel since that year. The Chapel is one of the UK's most respected hairdressing brands — award-winning, built around a strong aesthetic identity, and now operating across multiple salons. Over that time, we've redesigned and rebuilt their digital presence through several generations of the web. The technology changed completely each time. The brand didn't — and keeping those two things in balance is a more interesting problem than it might sound. What brand continuity actually means online ------------------------------------------- A luxury brand has a character. The Chapel's is built around a strong visual identity, a particular quality of imagery, a tone that feels confident without being cold. None of that is intrinsic to any specific technology. But it has to survive translation into whatever the current medium requires — a 2001 desktop site, a 2012 responsive redesign, a 2024 build that has to perform on a phone with a patchy 4G connection while still looking beautiful on a large screen. The risk in any redesign is that changes made for good technical or commercial reasons quietly erode the qualities that made the brand work in the first place. A faster-loading image that's been compressed too hard. A layout that's more mobile-friendly but loses the sense of space the desktop version had. A type choice that's more legible on small screens but doesn't carry the same weight. None of these feel like big decisions individually. Across a series of them, they can add up to a brand that's drifted somewhere its audience no longer recognises. What makes a long relationship work ----------------------------------- The thing that protects against drift, more than any design system or brand guideline document, is accumulated understanding. After working with a client for more than twenty years, you carry knowledge that isn't written down anywhere — what choices they regretted, which direction a previous redesign pushed them that turned out to be wrong, what their clients respond to that isn't obvious from the brief alone. This matters because every redesign starts from a position of genuine knowledge rather than a fresh interpretation. The risk in bringing in a new agency for each rebuild is that each team starts from what they can see — the existing site, the brand guidelines, perhaps a mood board — and makes reasonable decisions that turn out to miss something that would have been obvious to someone who'd been in the room for the previous three versions. What changes, and what shouldn't -------------------------------- The practical lesson from a relationship that spans this many iterations of the web is that the things worth protecting are usually not the things that feel most in need of updating. A bold photographic style, a consistent tone of voice, a particular sense of restraint in how much content the page carries — these are worth fighting to preserve through a rebuild, because they're usually why the brand works. The things that should change are the ones that are getting in the way of those qualities being experienced properly: a layout that no longer reads well on the devices people are actually using, a CMS that makes content maintenance painful, a performance issue that's making the site feel less premium than it should. Knowing which category a given element falls into is easier when you've seen it across multiple iterations. The Chapel's current digital presence reflects decisions made over a long time, by a team that understands what the brand is trying to be — and that continuity is part of what a long-term agency relationship is actually for. If you're thinking about a digital redesign and want to talk through how to protect what's working while updating what isn't, [get in touch](../../contact). [ Back to news ](/news) October 2026 ### [ What Building Software for Regulated Industries Actually Requires ](https://www.digitalmarmalade.co.uk/news/what-building-software-for-regulated-industries-actually-requires) Read more September 2026 ### [ Why We Built Our Own CMS ](https://www.digitalmarmalade.co.uk/news/why-we-built-our-own-cms) Read more September 2026 ### [ Designing Digital Products for Children: What Changes ](https://www.digitalmarmalade.co.uk/news/designing-digital-products-for-children-what-changes) Read more Allow cookies