I’m looking at soon cleaning up our component libraries and weighing a couple structural options, i.e. how many component libraries should we have? Very curious for input and opinions on these options:
1. A separate library file for each component. For ease of use, we think we’d have to bring these all into a single kit library file where we wrap each component in an outer component wrapper and then publish those. This way designers can subscribe to a single library.
Pros: makes using Figma branches very light and clean on component files
Cons: most of these library files will all have to subscribe to each other in order to compose larger components from atomic ones. Updates might involve lots of nested published updates.
Question: Does this impact memory/performance in a similar way to having hundreds of variants in a component?
2. One big component library. This might now be possible with variables and greatly reduced variant matrices?
Pros: composition of nested atomic components and updates like that happen automatically
Cons: branching usually gets messy with multiple designers working on a single library
Question: Any other concerns or gotchas here?
3. A handful of libraries grouped by component category. e.g. Controls, Containers, Inputs, Messaging, etc.
Pros: branching should still be clean as update efforts are usually limited to a single component category.
Cons: libraries will still have to subscribe to each other but at least the numbers are lower than Option 1.
