Draft: feat(DesignTokens): sync design tokens with Figma using REST API
What does this MR do?
- Add sync to Figma scripts for design tokens
- Add Figma extension properties to design tokens
Validating locally
- Create a
.env
file in the root of the project withFIGMA_ACCESS_TOKEN
andFIGMA_FILE_KEY
values e.g.FIGMA_ACCESS_TOKEN=example-figma-access-token-123 FIGMA_FILE_KEY=example-figma-file-id
- Get temp Figma API key by visiting https://www.figma.com/developers/api#access-tokens and pressing button to get temp (24hour) API key
- Set Figma file key from any Figma file by using the share URL and copying the file ID e.g.
https://www.figma.com/file/abc123-figma-file-id/...
file id isabc123-figma-file-id
- Run
yarn tokens:sync-to-figma
to push JSON tokens to Figma file
Screenshots or screen recordings
Integration merge requests
-
GitLab: mr_url -
CustomersDot: mr_url -
Status Page: mr_url
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"
toaria-expanded="true"
when an accordion is expanded. -
Color combinations have sufficient contrast.
Closes #2526 (closed)