Why it existed

Nobody asked me to build this. My job was subscription and monetization.

But teams kept rebuilding the same components slightly differently, and it was worse than ordinary inconsistency because we publish in Devanagari and Gujarati. Those scripts have different line heights and character widths, so a component that was technically consistent across both still looked wrong in one of them. Every designer was solving that problem alone, under deadline.

What I built

• Tokens for colour, type and spacing, with light and dark themes

• Type scales per script, so Devanagari and Gujarati each render correctly rather than sharing one compromise

• Component variants covering the real states teams needed, not the ideal set

• Documentation written for people shipping that week

The biggest single win was collapsing roughly ten article-card variants into one component.

How I rolled it out

I did not mandate it. I went team to team and helped people adopt it, because a system people are forced into gets worked around.

I also set one governance rule: a component has to ship in a real product before it enters the system. No designing in the abstract.

Results

• Teams stopped rebuilding basics

• Handoff time and UI errors both dropped

• Our products started looking like one product, which for a news brand is trust

What I took from it

Consistency is a tool, not the goal. A component that follows every rule and still feels wrong in one script is not consistent, it is just uniform.