Loading…
16
Pro tip: Naming our design system's color tokens took three months of back and forth
We started with 'primary' and 'secondary' but then needed shades for alerts, disabled states, and dark mode, which spiraled into endless debates over names like 'neutral-700' versus 'gray-cool-mid'. It finally got solved when our lead dev made a script to map every old hex code to the new system after a full quarter. Anyone else get stuck for ages on something that seems simple at first?
3 comments
Log in to join the discussion
Log In3 Comments
mitchell.wade7mo ago
Three months seems fast. Naming things is the hardest part of the job, and getting it wrong costs more time later. Eva_rivera probably agrees that rushing it is a bad plan.
10
janahenderson6mo ago
Totally feel this, we got stuck in the same loop. What finally worked for us was locking the core team in a room and banning any name that wasn't a simple number system, like gray-100 through gray-900. We made a strict rule that new shades just got the next number, no fancy names allowed. It felt dumb at first but it stopped all the pointless arguments cold. Now everything just works and no one has to think about it anymore.
3