@oxide/design-system 3.0.3--canary.148.17951596811.0 → 3.0.3--canary.148.17952915399.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -24,10 +24,7 @@ For more information checkout [auto's docs](https://intuit.github.io/auto/docs).
|
|
|
24
24
|
|
|
25
25
|
To ensure consistency between our designs and implementation we use the
|
|
26
26
|
[Design Tokens Plugin](https://www.figma.com/community/plugin/888356646278934516/Design-Tokens)
|
|
27
|
-
inside of figma to export a [json tokens file](styles/src/tokens.json) to the repo.
|
|
28
|
-
that file is changed the [build-themes](.github/workflows/build-themes.yaml) workflow runs
|
|
29
|
-
to generate theme stylesheets, a tailwind token file, and other artifacts in
|
|
30
|
-
[dist](styles/dist/).
|
|
27
|
+
inside of figma to export a [json tokens file](styles/src/tokens.json) to the repo. The user can then run `npm run build` to generate theme files. This is not automatic, the user should then commit the changes.
|
|
31
28
|
|
|
32
29
|
The design tokens plugin is two way so token changes made in the json file can be synced
|
|
33
30
|
back with figma.
|
package/package.json
CHANGED