- From: Mark Learst via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Aug 2023 22:53:44 +0000
- To: public-design-tokens-log@w3.org
I've been digging into these different options for managing composite design tokens, and here are my two cents. **Option 1**, which decomposes each token into individual variables, offers granular control. This allows for fine-tuned customization but could lead to management complexities, especially when it comes to ensuring the proper combination of these decomposed tokens. **Option 2**encapsulates all attributes into a single object and provides a cohesive approach. It makes it clear which attributes are meant to be used together but may not offer the same level of granularity that might be required in some scenarios. However, the 3rd approach suggested by @ddamato provides a balanced solution. It still allows for granular customization via sub-properties while providing a consolidated output tailored for specific platforms like CSS or Android through token operations. This modular approach not only streamlines the application of design tokens but also enables more efficient cross-platform compatibility. Given the flexibility and scalability inherent in the third approach, it is a compelling solution for managing composite design tokens effectively. -- GitHub Notification of comment by ipaintcode Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/226#issuecomment-1689027956 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 August 2023 22:53:46 UTC