Brand system · 2026-08-23
The brand travels with the library.
A package-owned Opus brand system removed the fragile dependency on an application's public folder.
Brand assets are part of the product surface too. This release made them portable, deliberate, and as easy to use as any other component.
One canonical brand
OpusBrand introduced icon, wordmark, and full-lockup variants backed by assets that belong to the published package.
No hidden consumer setup
Applications no longer need to carry a copied public asset just to render the shared brand correctly.
A small change with wide reach
Shared headers and footers moved to the canonical component, making every consumer more consistent while reducing local maintenance.