Change Details

We should figure out what is holding us back from publishing the design tokens package, address those things, and then publish it, so that it can be used outside of Codex (or in code using Codex, including in MediaWiki). == Necessary steps 1. Style Dictionary size transformers to ensure: - Accessibility (relative sizes where needed) - Themeability (provide simple way to change sizing units) - Developer experience (don't have to care about sizing in their Vue code) 2. Decide if missing font family category is a blocker for publishing first version 3. Removing option tokens from token output https://gerrit.wikimedia.org/r/c/design/codex/+/848519 – see above 4. Publish npm package; from here on teams like Growth can import and use the tokens in their extensions [5. Provide package to be consumed within WikimediaUI Base] [6. Provide package alongside mediawiki.skin.variables, so teams don't have to import separately anymore] == Acceptance criteria [] Publish 'codex-design-tokens' package to npm

== Background We should figure out what is holding us back from publishing the design tokens package, address those things, and then publish it, so that it can be used outside of Codex (or in code using Codex, including in MediaWiki). == Necessary steps 1. Style Dictionary size transformers to ensure: https://gerrit.wikimedia.org/r/c/design/codex/+/850407 - Accessibility (relative sizes where needed) - Themeability (provide simple way to change sizing units) - Developer experience (don't have to care about sizing in their Vue code) 2. Decide if missing font family category is a blocker for publishing first version 3. Removing option tokens from token output https://gerrit.wikimedia.org/r/c/design/codex/+/848519 and T309050 – see above, which relies on font-family tokens 4. Publish npm package; from here on teams like Growth can import and use the tokens in their extensions [5. Provide package to be consumed within WikimediaUI Base T318016] [6. Provide package alongside mediawiki.skin.variables, so teams don't have to import separately anymore] == Acceptance criteria [] Publish 'codex-design-tokens' package to npm

== Background We should figure out what is holding us back from publishing the design tokens package, address those things, and then publish it, so that it can be used outside of Codex (or in code using Codex, including in MediaWiki). == Necessary steps 1. Style Dictionary size transformers to ensure: https://gerrit.wikimedia.org/r/c/design/codex/+/850407 - Accessibility (relative sizes where needed) - Themeability (provide simple way to change sizing units) - Developer experience (don't have to care about sizing in their Vue code) 2. Decide if missing font family category is a blocker for publishing first version 3. Removing option tokens from token output https://gerrit.wikimedia.org/r/c/design/codex/+/848519 and T309050 – see abovee, which relies on font-family tokens 4. Publish npm package; from here on teams like Growth can import and use the tokens in their extensions [5. Provide package to be consumed within WikimediaUI Base T318016] [6. Provide package alongside mediawiki.skin.variables, so teams don't have to import separately anymore] == Acceptance criteria [] Publish 'codex-design-tokens' package to npm