Comments (2)
Thanks for pointing that out. That text could be worded better, and isn't really aligned with the definitions of "design token" we have in our glossary and format spec respectively:
The single source of truth to name and store a design decision, distributed so teams can use it across design tools and coding languages.
A (Design) Token is an information associated with a name, at minimum a name/value pair.
(TBH, I think that text is just something that predates our gloassary definition, which we forgot to update)
You're quite right - aspects of a design like colors, typography, spacing, etc. are as old as design itself and not something we're trying to invent a new name for. However, I'd argue the act of choosing a specific color/size/whatever, naming that choice within the context of a design system and all the methodologies around naming, organising, theming, etc. that have grown up around that, are more novel.
If we were to update the "indivisible pieces of a design system" line in our technical reports intro to be aligned with the definitions I cited above, would that be better?
from community-group.
Firstly, I want to thank @c1rrus and all contributing members for their insightful discussions and efforts in defining and refining the concept of design tokens. Your work is foundational to advancing our collective understanding and application of design systems.
I've reflected on the definition of design tokens as "indivisible pieces of a design system such as colors, spacing, typography scale." This concept profoundly resonates across various design disciplines, including graphic design, architecture, and broader cultural aesthetic principles rooted in historical movements like the Baroque, Renaissance, and Bauhaus. These movements have enriched our visual and cultural landscapes and established fundamental design principles that influence today's digital design methodologies.
The practice of applying consistent design elements such as colors, spacing, and typography has evolved significantly with the advent of design tokens in digital design frameworks. This evolution marks a transition from traditional to digital, where the formalization and systematization of design elements enable a more structured and scalable approach. This approach enhances design consistency and reusability across platforms and teams, a testament to the innovative spirit that drives our community.
Given @c1rrus's valuable feedback, I support updating our introductory text to align more closely with the glossary and format spec definitions. Acknowledging these design principles' historical and cross-disciplinary roots could further enrich our definition of design tokens. By doing so, we underscore that the innovation of design tokens lies not in the design elements themselves but in the methodologies of naming, organizing, and applying these decisions within contemporary digital ecosystems.
Incorporating a brief mention of the term's origin or its parallels in historical design practices could illuminate the innovative aspects of design tokens. This context bridges the gap between time-honored design principles and the difficulties of digital product development, highlighting the unique value design tokens bring to modern design and development processes.
– Mark
from community-group.
Related Issues (20)
- Consider using type: "$alias" for explicity
- Define how far design tokens are expected to be interoperable. HOT 1
- Remove REM/EM from specification? HOT 25
- Error in Font Weight example in spec?
- Standardizing the Handoff - Conceptual HOT 10
- Extensible Types HOT 2
- grid type HOT 6
- Specification / recommendation for custom types HOT 4
- Token Operations
- The $ property name prefix should be unnecessary with a well-structured schema HOT 10
- [Discussion]: How to transform composite tokens HOT 5
- Transition token documentation issue HOT 1
- Suggestion: colorList type for DataViz HOT 6
- Most recent edition (07/2023) missing from main page on w3c community group HOT 1
- Type: Text alignment HOT 11
- Custom Types / Interpritations HOT 1
- Is there a way to still include boolean and string type functionality? HOT 1
- Be explicit about whether or not empty groups are allowed HOT 5
- Alias $type inheritance? HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from community-group.