Free Design Token Naming Guide + Builder (https://lnkd.in/dFuXAh76), a wonderful resources for naming design tokens — from learning how they work and how to name them well to configuring your own naming structure with components, categories, states and roles.
Naming guide:https://lnkd.in/dAWFHf6B
Naming builder: https://lnkd.in/dfqASZB3
Naming things is hard. The right name is the one that’s well-understood and used by the team, but also doesn’t raise questions and confusion in team meetings. So much time is wasted speaking about the very same thing but in different dialects — the designer’s dialect, the developer’s dialect, the product manager’s dialect. That’s what often causes frustration and confusion.
Whenever I have a choice, I always aim for boring, explicit names that teams understand in the same way. No abstract metaphors or ambiguous labels. And a way to do that is to get together and speak through the different ways of how we call things, and choose one specific name that works for everyone.
And then get into habit of naming it, repeatedly over time. The goal isn’t to be consistent with the definitions for the sake of it. But rather to align intentions — and use the same language when making and discussing design decisions. –
Useful Bookmarks for Naming Things:
Naming buttons → https://lnkd.in/eZTum8SK
Naming classes →
Naming commands → https://lnkd.in/eZTum8SK
Naming colors →
Naming design tokens → https://lnkd.in/ehk8MCsr
Naming features → https://lnkd.in/d5pFBcHF
Naming icons →
Naming layers →
Naming variables → https://lnkd.in/exaWHg9K
Naming products →
Naming UI components → https://lnkd.in/eJe8HDEK
Naming variables → https://lnkd.in/dE8k22PD
UI terminology → https://lnkd.in/d29wjzY6
I’ve also put together “How To Name Things” (https://lnkd.in/d8taSqSk), a little post with practical tools, references and time-savers I always keep in my bookmarks — to choose names for UI components, colors, layers, design tokens and everything-in-between.