Page Comparison

Documenting design tokens

Adam Stankiewicz

Reference: https://github.com/openedx/paragon/pull/3186#discussion_r1825568151

Where should such documentation live?

Are there linting rules we can create and/or enable for design tokens?

• Maybe? https://eslint.org/blog/2024/10/eslint-json-markdown-support/

Notes:

• https://github.com/openedx/paragon/blob/alpha/tokens/README.md

• Next steps

  • Adam Stankiewicz to create action items for organizing token properties and discovery for ESLint on JSON tokens.

Next steps related to dimension type:

• Adam Stankiewicz to file style-dictionary GitHub issue to document invalid DTCG format spec with split out value vs. unit:

  • Code Block
    --pgn-size-border-width-unit: 0px; /* Default border width. */ --pgn-size-border-width-value: 1; /* Default border width. */

5 min

Design Tokens Non-Engineering Presentation

Peter Kulko

https://docs.google.com/presentation/d/1FOSbTUTbbzaBoIDYMa5s32in1uFoYWdoQ-GjKk5IRBo/edit?usp=sharing
📄 Paragon Design Tokens Cheat Sheet

https://discuss.openedx.org/t/paragon-design-tokens/14277

https://youtu.be/ZTm43oQkcE0?si=GLcSsR8xON-sBzcC

22/23/Next docs sites

Brian Smith to make an issue for ensuring we have docs site deployments for versions 22, 23, and Next versions.

• One issue for docs sites

• One issue for semantic release/npm

• One issue for generic “cutover” to cover the above 2 and anything else we think of

Should do the docs site and npm/semantic release changes during a WG meeting (sync as opposed to async)