

Multi-brand design systems solve an architecture problem and a documentation problem simultaneously. The architecture problem — how to express multiple visual identities through a single token system — is covered in Article 07 — Multi-brand, multi-product and white-label token architecture. The documentation problem is what this article addresses: once your multi-brand token system is built, how do you present it in zeroheight in a way that's navigable, governable, and useful to the teams consuming it?
The choices you make here affect who can find what, how quickly new brand teams get up to speed, and how much overhead the system team carries as the number of brands grows.
The most fundamental documentation question for a multi-brand system is whether each brand gets its own styleguide or whether everything lives in a single shared styleguide.
There's no universal answer, but the decision criteria are fairly clear.
A separate styleguide per brand is the right choice when:
A shared styleguide works best when:
In practice, many organizations end up with a hybrid: a shared system-level styleguide covering the shared foundation, plus brand-specific styleguides for the identity and usage guidelines that are unique to each brand. The shared styleguide is the source of truth for "how this system works"; the brand styleguides are the source of truth for "how this brand uses it."
Whether you're using multiple styleguides or one, brand-specific tokens need to be surfaced correctly in the Tokens Manager.
The cleanest approach follows the token architecture from Article 07: brand tokens live in brand-specific collections that override the shared semantic layer. In zeroheight, all of these collections — shared and brand-specific alike — are consolidated into a single token set in the Tokens Manager, with Collections used to organize them. In the Tokens Manager you'll see something like:
Token set
Collections
00 Primitives (shared)
01 Semantic (shared)
02 Brand A: Color
02 Brand B: Color
02 Brand C: Color
This structure makes it clear which tokens are shared and which are brand-specific, while keeping everything in one place. When Brand B's primary color changes, the update is isolated to Brand B's collection. The shared collections are untouched.
For documentation purposes, brand-specific collections can be surfaced on the appropriate pages of the styleguide using the Design Tokens block. A Brand A color palette page shows Brand A's tokens; a Brand B page shows Brand B's. Neither leaks into the other.
One of the most useful things a multi-brand styleguide can do is show the same component in multiple brand contexts simultaneously. This demonstrates the power of the token system (the same component code, different visual output) and gives consuming teams a reference for what the component should look like in their brand.
In zeroheight, this is achieved by embedding component documentation with brand-specific token modes applied. Design frames can be embedded with different modes active, showing the component in Brand A and Brand B side by side on the same page.
A few patterns that work well:
Side-by-side brand comparison. Show the same component (a button, a card, a form input) in two or three brand contexts next to each other. This is particularly effective for shared component documentation in a single multi-brand styleguide, where the audience includes teams from multiple brands.
Brand-specific component pages. In a multi-styleguide setup, each brand's styleguide shows components in that brand's context only. The shared system styleguide can still show multi-brand comparisons to illustrate how the system works.
Mode-switching in embedded previews. If you're using zeroheight's live component previews, embedding components with different token modes active gives readers a real-time sense of how the component responds to brand switching.
The key discipline: use semantic token references in your components consistently. A component that bypasses the semantic layer and references a primitive directly will look the same regardless of which brand mode is applied, defeating the purpose of the multi-brand demonstration.
More brands means more documentation to maintain, more contributors to coordinate, and more opportunities for things to drift out of sync. Governance structures that work for a single-brand system need to scale.
zeroheight's permission model allows you to control who can view and edit each styleguide. In a multi-styleguide setup, this means each brand styleguide can be managed by its own team, with the system team maintaining admin access across all of them for cross-brand governance.
Useful permission patterns for multi-brand setups:
One of the maintenance challenges in a multi-styleguide setup is keeping shared content (system-level principles, shared component documentation, contribution guidelines) in sync across all styleguides. Updating the same content in five separate styleguides manually is error-prone and time-consuming.
A few approaches to managing this:
The right structure depends significantly on how many brands you're managing.
At this scale, a single shared styleguide with brand-specific sections is often the most practical approach. The overhead of maintaining separate styleguides outweighs the navigational benefit, and the audience for each brand's documentation is small enough that cross-brand content isn't significantly disruptive.
Structure the shared styleguide with a clear top-level section for each brand, and a shared system section covering the foundation. Brand-specific collections are surfaced in the relevant section via Design Tokens blocks.
Here the case for separate styleguides strengthens. Navigation in a single styleguide becomes genuinely complex at this scale, and the likelihood that brand teams have distinct audiences and governance needs increases.
A hybrid works well: a system styleguide covering the shared foundation and the multi-brand architecture, plus individual brand styleguides for each brand's specific implementation. The system styleguide acts as the hub; brand styleguides are the spokes.
At this scale, the documentation challenge becomes a platform problem. Manually maintaining twenty separate styleguides, even with good governance, doesn't scale. The most viable approach is generating brand styleguide sections programmatically from the token system, using zeroheight's API to push brand-specific content rather than maintaining it by hand.
For white-label setups where partner brands are the audience, the token exposure model covered in Article 07 determines what each partner can customize. Their styleguide access reflects the scope of their customization — they see only the tokens they control, not the locked system-level values.
Article 20 — Token governance workflows in zeroheight closes out the guide with the zeroheight-specific governance tools: analytics for measuring token adoption, changelog setup, access controls for contribution workflows, and how to integrate zeroheight into the token release pipeline.
