Naming Conventions for Components
Learn how clear, consistent naming of components and their props makes a component library discoverable, predictable, and maintainable.
Why Names Matter
The hardest problems in component libraries are not technical - they are naming. A poorly named component is hard to find, easy to misuse, and painful to rename later.
Good names act as documentation and reduce the questions teammates ask.
Be Descriptive, Not Clever
Name components by what they are or do, not by clever metaphors.
- Good:
UserAvatar,PrimaryButton - Avoid:
Blob,Sparkle,Thingy
A new teammate should guess the purpose from the name alone.
All lessons in this course
- Atomic Design Methodology
- Component Anatomy & Structure
- Choosing Tech Stack Components
- Naming Conventions for Components