rtCamp

Managing multiple brands doesn't require multiple systems.

Here's how Cox Automotive standardized publishing across eight brands while preserving what made each one unique ↓

Most enterprise design systems live in Figma.

They govern colour, type, spacing, and component behaviour, and then the content team publishes a page that ignores half of it because the CMS didn't enforce anything.

The gap isn't the design system. It's the distance between where design decisions are made and where content gets published.

Gutenberg closes that gap. When custom blocks and patterns are built to your design system with role-based permissions controlling what editors can and can't modify, every page is on-brand by default.

Not because someone reviewed it. Because the system is designed to prevent off-brand output.

Cox Automotive's Design Library works exactly this way. A centralised block and pattern repository shared across eight brand websites, with 70–80% of components reused for each new launch.

The design system isn't a PDF, it's the publishing environment itself.

For CMOs and brand custodians managing multiple properties, this is the real value: marketing moves fast, and the brand stays intact.

No bottleneck. No review queue. No "can you check this before I hit publish?” messages.

Editorial independence doesn’t happen because a CMS claims to be “easy to use.”

It happens when the entire publishing workflow is designed around the content team.

Here’s how we helped reduce developer dependency and improve publishing velocity ↓