Hi Romina, you recommend keeping one component per file for the multi-brand. How do you handle updates? eg an update in the button component would mean opening and updating all component files which contain a button in the layout (button group, modal, card, …). I only did a poc and found that time consuming and difficult to keep the overview which component is included in other components. curious to hear your thoughts or best practices !
1. For DS, which only uses two themes, I keep all the components in one file (as mentioned above).
2. It depends on your tech stack (Figma Variables vs design tokens) and how you push/pull.
3. No matter what, for multi-brand DS, it may seem like a burden initially, but later on, it is much easier to collaborate + file performance is better + versioning +, etc.
4. I still group components (for example, radio button + checkboxes in Form elements, all dropdowns, etc.). So, in the end, it is not "so many" files.
5. It is easier to keep an agnostic library and combine per brand/product and then share it with specific product teams.
You can also send me a DM with more specific questions ;)
Hi Romina, you recommend keeping one component per file for the multi-brand. How do you handle updates? eg an update in the button component would mean opening and updating all component files which contain a button in the layout (button group, modal, card, …). I only did a poc and found that time consuming and difficult to keep the overview which component is included in other components. curious to hear your thoughts or best practices !
Hey Petra.
1. For DS, which only uses two themes, I keep all the components in one file (as mentioned above).
2. It depends on your tech stack (Figma Variables vs design tokens) and how you push/pull.
3. No matter what, for multi-brand DS, it may seem like a burden initially, but later on, it is much easier to collaborate + file performance is better + versioning +, etc.
4. I still group components (for example, radio button + checkboxes in Form elements, all dropdowns, etc.). So, in the end, it is not "so many" files.
5. It is easier to keep an agnostic library and combine per brand/product and then share it with specific product teams.
You can also send me a DM with more specific questions ;)