Re: [community-group] Standardizing the Handoff - Conceptual (#220)

# Advancing the Design Token Contract Discussion

Thank you for your valuable insights on the Design Token Contract. Let's refine our thoughts to further progress the conversation:

## Token Naming Convention:

- Establish a clear and consistent system for naming, such as category-property-value (e.g., color-background-primary).
- Consider adopting a more comprehensive taxonomy like the CTI+ model, which includes Domain, Category, Type, Item, SubItem, Variant, and Context, with additional metadata tags for subbrands/subthemes and modes.
- Strive for alignment within the community to ensure a defined 'schema' that maps tokens to code output effectively.

## Token Values:

- Foster a shared understanding of units (px, rem, vh, etc.) and color formats (hex, rgb, hsb, hsl, etc.) to avoid confusion and ensure accurate design execution across platforms.

## Token Structure:

- Explore grouping tokens by category (e.g., colors, typography, spacing) for intuitive organization.
- Consider accommodating multi-brand scenarios by including variants for different brands (e.g., brandA-color-background-primary, brandB-color-background-primary) to ensure scalability, maintainability, and brand uniqueness.
- Evaluate potential structures based on their implications for usability and management.

## Token Modification Rules:

- Establish clear guidelines on who can modify or add tokens and under what circumstances to maintain consistency and prevent conflicts.

## Token Usage Guidelines:

- Provide clear instructions on how to use tokens in different contexts, serving as a user manual for design tokens and facilitating effective utilization.

Let's keep in mind that the Design Token Contract aims to improve collaboration, not enforce a hierarchy between designers and developers. By working in tandem and making multi-disciplinary decisions together as a team, we can harness the strengths of both roles. The Design Token Contract serves as a tool for better communication, bridging the gap between design and code.

While it's crucial to avoid dictating a specific naming convention, we should encourage the creation of tailored conventions for each project, product, or hand-off. A base naming convention can be established, which can then be built upon or modified to suit specific needs.

As we navigate the path towards standardization, let's also examine the deviations in Figma Variables' implementation and their alignment with the evolving Design Token Contract. This will ensure that we stay informed and incorporate relevant advancements.

---

## Exploring Figma Variables and their Alignment with the Design Token Contract

I would like to delve into the topic of Figma Variables and their relevance to the Design Token Contract. While Figma Variables offer promising features, it is essential to evaluate their alignment with our ongoing efforts to standardize design tokenization.

Figma Variables, currently in beta, introduce some variations in their implementation. As we examine their specifications and the direction Figma is heading, we should consider their potential impact on the broader design token ecosystem. By understanding these deviations, we can ensure that our discussions and recommendations remain informed and adaptable to evolving industry practices.

As the Design Token Contract gains traction, it is crucial to consider the compatibility and interoperability of design tools and platforms. While Figma is widely adopted within the design community, we should assess how its variable implementation aligns with the principles and goals of the Design Token Contract. This evaluation will enable us to determine the best practices for incorporating Figma Variables into our design token workflows.

By addressing the Figma Variables issue within our conversations, we demonstrate a comprehensive understanding of the design token landscape and a commitment to fostering collaboration and standardization. Let's continue exploring this topic together, sharing insights and findings that can help shape the future of design tokenization.

Thank you for your contributions, and I look forward to engaging in further discussions.

– Mark


-- 
GitHub Notification of comment by ipaintcode
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/220#issuecomment-1642478751 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 July 2023 17:29:21 UTC