<aside> 💡
Property names define how components are configured within the design system. A consistent naming convention improves discoverability, reduces ambiguity, and creates a predictable API for both designers and developers.
These guidelines apply to all component properties, including Variant Properties, Boolean Properties, and Text Properties.
</aside>
Having a cheat-sheet for easy and quick reference goes a long way in developing a good habit of naming properties properly.
These are the core variations of a component, mostly involving the biggest visual differences. They refer to the core set of related components within a single component set.
Boolean properties cater to cases where the features are binary i.e. a simple on/off or true/false.
Text Properties define the textual content displayed within a component. Unlike Variant or Boolean properties, Text Properties are editable strings that communicate information, actions, or context to users.
Use PascalCase for all Text Property names.
Node properties allow components to swap or embed subcomponents dynamically. This makes components more flexible by supporting custom content, badges, or nested elements without creating multiple variants.