One brand system across every Vallit surface
Vallit, WTM, and the internal dashboards used to drift. Each surface had its own flavor of indigo, its own type scale, its own notion of what calm-authority looked like in a button. A single shared-ui tokens layer now replaces that drift with one source of truth.
Two files carry it: brand.css for CSS custom properties the runtime reads, and index.ts for the JS constants the build-time code imports. The tokens ship in packages/shared-ui so the marketing app, the operator dashboard, and any future surface pull from the same atoms. Primary accent is #5e6ad2 indigo; type scale favors readable density over hero-page drama; shadow recipes come in three discrete layers rather than the ad-hoc rgba(0,0,0,.N) that had accumulated.
A companion brand-guidelines doc at docs/brand-guidelines.md walks through when the system bends and when it doesn't — B2B tone, language patterns, voice register per audience. It's the file a designer or an agent should read before touching anything that has a headline or a color on it.
This is the substrate the full marketing-landing rebuild sits on. Phase 1 of that rebuild (panel chrome standardization, four-layer tonal system) extends these tokens rather than re-inventing them.
Want this for your team?
We scope, build, and deploy Kian into your stack — usually in four to eight weeks.