Does component naming really matter?
Monday · November 13, 2023
While working on Lyearn’s Design System, we often find ourselves debating the perfect name for a component. This dilemma deepens when we research other design systems and discover that every team uses different names—whether it’s "Pill," "Chips," "Badges," "Tags," or "Tokens."
Screenshot: A Slack thread on naming a pill-like component
Here’s the truth: If your team agrees on a name like "Potato" and everyone understands it, that’s all that matters. Consistency and clarity in naming are important, but the name itself is secondary.
What truly impacts our work is how well we document our components. Thorough and clear documentation ensures that a component is easily understood and used, no matter its name.