An interesting look at the early draft proposal for an official design token specification and file format. The pitch is a strong one: standardise design tokens so that every tool can understand them, and display them in the most appropriate way. An IDE could show the underlying code; a design tool like Figma could show visual widgets like colour swatches and type hierarchies. Better still, you have one file that all systems ingest, so a change in one place should flood throughout the system: a designer changes a colour token in Figma, the live code updates.
- Source
- Link to Original 🔗
- Published
- Categories
- Nuts & Bolts, Web Design
- Tags
- design tokens, design system
Explore Other Notes
⬅ Newer
React server components tips
A quick overview of React Server Components and some of the mental models that are useful when thinking about how they might be applied, in …
Older ➡
Josh's custom CSS reset
Josh has added some additional thoughts to Andy's CSS reset. Personally, I like a combination of the two (with a dash of Stephanie's best practices thrown in for good measure), but wanted to capture …
- <!DOCTYPE html> <html> <head> <title></title> </head> <body> <p>An interesting look at the early draft proposal for an official design token specification and file format. The pitch is a strong one: standardise design tokens so that every tool can understand …</p> </body> </html>
- Murray Champernowne
