Skip to content

feat(DesignTokens): Create design token table

Scott de Jonge requested to merge 2641-design-tokens-visualisation into main

What does this MR do?

Create design token table storybook story to render compiled /src/tokens/build/json/tokens.json in a visual format with filtering.

Screenshots or screen recordings

Current tokens

Light Dark
localhost_9001__path__story_tokens-all--default__1_ localhost_9001__path__story_tokens-all--default__2_
localhost_9001__path__story_tokens-all--default localhost_9001__path__story_tokens-all--default__3_

Aliased tokens

In future iteration we will be adding constant color tokens to replace gray.500 with color.neutral.500 etc. These will be alised to exisiting text semantic design tokens.

Patch: design-toke-aliases.patch

Light Dark
localhost_9001__path__story_tokens-all--default__4_ localhost_9001__path__story_tokens-all--default__5_

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.

Closes #2641 (closed)

Edited by Scott de Jonge

Merge request reports