@skdx/tokens 0.34.0 → 0.35.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 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Theme contract and design tokens for the SkandaDX design system.
|
|
4
4
|
|
|
5
|
-
A SkandaDX theme is a **plain, JSON-serializable object** — no CSS files, no build step required. This package defines what a theme looks like (the `Theme` contract), ships ready-made themes, and provides functions that turn any theme into CSS custom properties (`--skdx-*` variables). It's published as a standalone, general-purpose package: skdx's own framework packages are headless (Phase 1) and don't depend on or apply these tokens themselves today, so `@skdx/tokens` is meant to be consumed independently — by
|
|
5
|
+
A SkandaDX theme is a **plain, JSON-serializable object** — no CSS files, no build step required. This package defines what a theme looks like (the `Theme` contract), ships ready-made themes, and provides functions that turn any theme into CSS custom properties (`--skdx-*` variables). It's published as a standalone, general-purpose package: skdx's own framework packages are headless (Phase 1) and don't depend on or apply these tokens themselves today, so `@skdx/tokens` is meant to be consumed independently — by the docs site, or by any other project that wants the `--skdx-*` variables. Themed components that auto-apply a `Theme` are planned as future (Phase 2) work, not current behavior. Because themes are plain data, they are the natural output format for a visual theme builder: the builder edits a `Theme` object, and this package renders it to CSS.
|
|
6
6
|
|
|
7
7
|
```text
|
|
8
8
|
Theme (colors) ── themeToCss / applyTheme ─┐
|