flâneur

tao of figma

taooffigma.com · 492 words · saved by 1 readers

Components, their properties, and their values should have a consistent naming convention. For example: Naming convention should also apply to: Top-down order of component properties should match the reading direction of the component. Use boolean properties for toggling the visibility of component layers. This will reduce the component size and make it much more manageable. All component layers should have names. While semantic names are best, it it's okay to have something as simple as "container" or even "frame" (just not "Frame 1453583"). Placing components inside (unnamed) frames can make it more difficult to use the component, because it creates additional nesting in the Assets panel. Of course, you should still use this feature intentionally :) Don't use an instance of a component to create another variant of that component. This creates a poor experience for everyone who maintains and uses the library. Place the most commonly used variant in the top left corner of the component

Have a naming convention. Components, their properties, and their values should have a consistent naming convention. For example: Component names are uppercase, with spaces between words. Property names are capitalized. Property values are lowercase. Naming convention should also apply to: Hidden components. For example, you can choose to use a dot as prefix, keep words lowercase, and separate them with dashes. Deprecated components. For example, you can add "DEPRECATED" before component name. Put properties in a logical order. Top-down order of component properties should match the…

saved by

related reading