Azalea
Azalea

Azalea

The tokens, components and guidance shared by every Averoa surface — Hana, Sage, Ivy and Root. One brand, defined once.

Why it exists

Not theory — this is what the four repos actually looked like before it.

identical globals.css

Byte-for-byte the same file in Ivy, Root and Sage.

the same logo component

Re-cutting the artwork once meant three commits in three repos.

2

answers to one question

“Needs a human” was red in Ivy and amber in Root. Both were the only one — in their own repo.

Both themes, always

Every component is checked in light and dark side by side. A component can look right in the theme you happen to be in and be unreadable in the other — and you will not catch that by toggling from memory.

light

SUCCESSNEEDS APPROVALDEADv1

dark

SUCCESSNEEDS APPROVALDEADv1

Start here

The one rule worth remembering

Solid fills are reserved for “a person must act.” Everything else is a subtle tint. That is what makes a wall of a hundred rows readable at a glance — colour tells you severity, fill tells you whether it is your problem.

Fill rule

QUEUEDRUNNINGSUCCESSRETRYINGFAILED← informational · needs you →NEEDS APPROVALDEAD