Multi brand video component library: give one brand its own version without forking everyone
Quick answer:A multi brand video component library is one shared set of templates, transitions and graphics used across several brands. When one brand needs a component to behave differently, give it a brand scoped set that links the shared components and holds its own version of the changed one, so no other brand inherits it.
The request was small. One brand in a shared library wanted a transition to move differently from how it moved everywhere else. Two instincts showed up immediately. Pull that transition out of the shared set, or edit it in place. Either one would have hit every other brand using it.
Why is editing a shared video component risky across brands?
Because a shared component is shared on purpose. Every brand linked to it gets every change. Edit it in place for one brand, and the others inherit a transition nobody asked them about. Pull it out of the shared set, and the brands that relied on it lose it, sometimes in projects that are already live.
Inheritance also hides problems. In one theme, an animation appeared to fire twice. The effect already existed through a link to the shared set, and someone had rebuilt it locally on top. The fix was deleting the duplicate, and it looked like an animation bug until someone traced the link.
How should a multi brand video component library handle a brand variant?
Give the brand its own scoped set. That set links every shared component the brand keeps as is, and holds its own version of the one it changes. The shared library stays untouched, and the variant lands only where it was requested.
| Approach | What happens to the requesting brand | What happens to every other brand |
|---|---|---|
| Edit the shared component in place | Gets its variant | Inherits a change nobody approved |
| Remove it from the shared set | Loses the shared version, builds its own | Loses the component, sometimes mid project |
| Brand scoped set linking the shared library | Gets its variant, keeps everything else linked | Unaffected |
This applies to any studio running several identities through one system. We looked at the broader version of that setup inswitching brand identities inside one system.
What does a brand scoped component set cost to maintain?
More than a single shared library. Each scoped set is a place where one brand diverges. Make three brands diverge on three components, and a change to the shared version now needs checking against three local versions. The layer that was meant to let you change things once now asks you to change some things once per brand.
That is a reasonable trade for a genuine brand difference. It is a poor trade for a preference. A useful rule is that a component earns a brand scoped version only when the brand guide requires the difference.
How do you retire or rename a shared video component safely?
Run the old and new versions side by side for a while. Removing or renaming a component in a shared library tends to break the placed instances rather than the whole project, so users find a piece of their video they cannot interact with, and the only recovery is deleting it and adding it back. Ship the replacement alongside the original, let usage move over, and rename or remove at the end.
The same thinking applies to any change that lands on people who did not request it. Our post onchange management for a shared template librarycovers the communication side.
What does this look like for one brand's transition request?
Take the transition request above across a portfolio of four brands.
- The request:Brand B wants its transition to move differently.
- The check:the brand guide for Brand B specifies that motion. It qualifies for a scoped version.
- The build:a Brand B set links every shared component except that transition, and holds its own version of it.
- The result:Brands A, C and D see no change. Brand B gets its transition everywhere it uses the library.
- The record:the divergence is logged, so the next change to the shared transition gets checked against Brand B's version.
If you are starting from the basics of how shared motion rules work, our explainer onwhat a motion design system isis the place to begin.
FAQ
What is a multi brand video component library?
A single set of video templates, transitions and graphics shared across several brands, usually in an in house agency or a company with multiple product brands.
How do you customize a shared video template for one brand?
Create a brand scoped set that links the shared components the brand keeps and holds its own version of the one it changes, rather than editing the shared component.
Why did changing one template affect other brands?
Because every brand linked to a shared component inherits changes to it. Editing it in place changes it everywhere it is used.
How do you remove a component from a shared template library?
Ship the replacement alongside it, let usage move over, then remove or rename the old one. Removing it outright can break instances already placed in projects.