Define design tokens’

• structure
• naming convention
• format/language
• management (creation, conversion and update).

Learnings from the prototyping sprint could be handy.

Notes and open questions:

• 2 big issues related to the current token structure: 1. (Possibly temporary) Every time component-level tokens need to be defined, there’s a need to dig deep and connect the dots (i.e. if several components share the same style) to update existing tokens (aliases). 2. Having component-level tokens makes us to have to handle a huge and growing amount of them.
• In case we stick to JSON: Is it worth exploring ways in which to simplify the creation and edition of tokens, to prevent us from having to edit JSON directly? (This exploration was considered as a next step after the prototyping week. See Phab task)