Design Tokens: To Infinity and Beyond

A presentation at Design Tokens: To Infinity and Beyond in September 2020 in by Louis Chenais

Slide 1

Slide 1

Design Tokens: to infinity and beyond

Slide 2

Slide 2

Bonjour 👋 Co-founder & Front-End Developer • W3C Design Tokens Community Group Member • Author of “Design Tokens for Dummies” Previously Front-End Developer @ SportEasy, 5emeGauche & Ultranoir @chuckn0risk • louis@specifyapp.com

Slide 3

Slide 3

Summary

  1. Design tokens kézako? 2. What is a Design API? 3. Why do we need a standard? 4. Future of design tokens 5. Demo of a Design API

Slide 4

Slide 4

Design Tokens kézako?

Slide 5

Slide 5

🤔 What are design tokens? What business issue do we want to address?

Slide 6

Slide 6

Slide 7

Slide 7

Slide 8

Slide 8

“Design tokens are cross platform variables that define key design data” — Sarah Federman | @sarah_federman

Slide 9

Slide 9

Slide 10

Slide 10

Slide 11

Slide 11

Slide 12

Slide 12

Design tokens allow product teams to better collaborate and ensure brand consistency across any platform.

Slide 13

Slide 13

🙏 Thanks to the Salesforce team for providing this categorization

Slide 14

Slide 14

Design tokens should be named differently according to their context of usage.

Slide 15

Slide 15

Design option Design decisions

Slide 16

Slide 16

Design options Design decisions Text style text-body-large Text style button-text-default Color purple-500 Color background-button-primary-default Spacing base-space-3 Spacing button-side-padding

Slide 17

Slide 17

background-button-primary-default button-text-default button-side-padding

Slide 18

Slide 18

Slide 19

Slide 19

“Design tokens are useful for describing core design values, but their full power emerges when used to describe the specs of UI components.” — Cristiano Rastelli | @areaweb

Slide 20

Slide 20

What is a Design API ?

Slide 21

Slide 21

Current situation 🤕 Crafting cohesive user experiences across several platforms is a real challenge.

Slide 22

Slide 22

“A design system isn’t a project. It’s a product, serving products.” — Nathan Curtis | @nathancurtis

Slide 23

Slide 23

Design tokens

Slide 24

Slide 24

Design system Design tokens

Slide 25

Slide 25

Accessibility team 👩 Design team Design System Marketing team Engineering team

Slide 26

Slide 26

Tool #2 Design API Tool #3 Tool #2

Slide 27

Slide 27

Design APIs are the logical evolution of design systems.

Slide 28

Slide 28

“An interoperable, guessable design API is the foundation of a fully networked design system, […]. It’s the next step in the evolution of design systems.” — Matthew Ström | A design API in practice

Slide 29

Slide 29

Why do we need a standard?

Slide 30

Slide 30

As an organization’s brand identity must be used and applied as easily as possible, its design tokens must be able to transit freely from one tool to another.

Slide 31

Slide 31

Colors, icons and images from Figma to Pitch.

Slide 32

Slide 32

Images from Dropbox to Github.

Slide 33

Slide 33

Updating design tokens in Figma will create a ticket in Jira.

Slide 34

Slide 34

Locales from Excel to Webflow.

Slide 35

Slide 35

Our market direly needs a design tokens standard widely spread so that design decision can transit freely across an organization tools ecosystem.

Slide 36

Slide 36

“Systems should support how creators work.” — Danny Banks | An Introduction to Multi-Platform Design Systems

Slide 37

Slide 37

Design Tokens W3C Community Group to the rescue!

Slide 38

Slide 38

DTCG | @designtokens

  1. Created in 2019 par Kaelig DeloumeauPrigent & Jina Anne to gather the design tokens community 2. The need for a standard is now stronger than ever: a call for editors is made in February 2020 3. In June 2020 all editors are found and officially spread across different design tokens modules

Slide 39

Slide 39

Objective #1 Provide a standard for design tokens. It will alIow tool creators and tool consumers to have quality design that scales thanks to design APIs. Lead by Kaelig Deloumeau-Prigent (UX Developer @ Shopify).

Slide 40

Slide 40

Objective #2 Manage the design tokens community and promote design tokens best practices. Lead by Jina Anne (Design System Lead @ Asana).

Slide 41

Slide 41

Design Tokens Community Group modules: Colors Spacing Animation Format …

Slide 42

Slide 42

The future of design tokens

Slide 43

Slide 43

🏆 Universal interoperability

Slide 44

Slide 44

Slide 45

Slide 45

Universal interoperability for design tokens: ability to define and maintain design tokens from any tool.

Slide 46

Slide 46

Slide 47

Slide 47

This would allow us to: • Edit all design tokens directly from a simple YAML/JSON file • See, edit and use all design tokens from a design tool • Use design tokens from apps like Google Docs/MS Word and create templates or themes from them • Use design tokens from a CMS or a third-part system like Webflow/Squarespace/Wordpress/Shopify

Slide 48

Slide 48

Shaper | @hihayk

Slide 49

Slide 49

🌓 The multi-brand use case

Slide 50

Slide 50

Card Grid Component for Themeable Design System | @brad_frost

Slide 51

Slide 51

A unique Card component is applied to three different brands : Verywell.com, TheSpruce.com, and TheBalance.com. https://bradfrost.com/blog/post/creating-themeable-design-systems/

Slide 52

Slide 52

🚀 Beyond digital products

Slide 53

Slide 53

👏 Thanks to @AdamSedwick, @calebwilliams12 and @vlh for their thorough research on the subject.

Slide 54

Slide 54

Demo of a design API

Slide 55

Slide 55

🙏 Shoukran @chuckn0risk • louis@specifyapp.com