==== Background/Goal
Create and publish an initial version of the Design System Tokens Catalog
===== User stories
- As a designer, I can easily locate what tokens have been created/codified.
- As a developer, I can easily locate which tokens are available. Also which ones are deprecated and their replacements.
===== Considerations
- Tokens available in the Design System should be easy to find by any type of user
- We have multiple documents related to tokens that need to be organized and centralized
- current list of baseline tokens here: {T295991}
===== Requirements
[] There is a single source of truth for Design System Design Tokens
- The Tokens Catalog MUST include the following:
[] A full list of all tokens that already exist in the Design System
[] Links back to relevant visual style guides
[] Overall Design System Status: Not Started, In Design/Scoping, Ready for Development, In Development, Product Sign-Off, Done, Blocked
[] Design Sign-Off: Not started, In progress, Done (all DST designers agree and are in alignment)
[] PHAB Implementation Epic Link (if available)
[] There is a single source of truth for each user story (aka artifact)
[] All source of truth documents/artifacts are available via Design System Portal/Wiki
===== Acceptance criteria
[] There is a single source of truth for each user story (aka document)
[] All documentation should link back to a central Design System Portal
[] Documents should be:
[] easy to read (limited jargon)
[] clear to follow (written as steps, checklists, visual diagrams, etc.)
[] Access to documents should NOT be restricted for viewing by target users (aka remove or update permissions as necessary)
===== Test scenarios
[N/A]
===== Open questions
- How do we mitigate the confusion between existing standards set by other systems (such as OOUI) vs our visual style design standards? Should we document what is different between them?