@uncinq/component-tokens 1.10.0 → 1.10.1

package/docs/customizing.md

@@ -3,6 +3,7 @@ isIndex: false
 title: Customizing
 description: How to override a component token, which layer to reach for, and when a new token is warranted.
 weight: 2
+icon: sliders
 ---
 
 ## CSS override

package/docs/dtcg.md

@@ -3,6 +3,7 @@ isIndex: false
 title: DTCG format
 description: The Design Tokens Community Group JSON format as used for component tokens, including group-level types.
 weight: 4
+icon: braces
 ---
 
 

package/docs/naming.md

@@ -3,6 +3,7 @@ isIndex: false
 title: Naming
 description: The component token naming grammar, the rules behind it, and why colors invert the usual property order.
 weight: 1
+icon: tag
 ---
 
 Every component token follows one pattern:

package/docs/reference.md

@@ -3,6 +3,7 @@ isIndex: false
 title: Reference
 description: Every token for all 26 components, generated from the JSON sources so it can never drift from the shipped CSS.
 weight: 3
+icon: table
 ---
 
 Every table below is generated at build time from `dist/tokens.json`, which Style Dictionary produces from the same JSON sources as the CSS. Nothing here is written by hand, so a token cannot appear in the reference without existing in the package, or change value without the page changing with it.

package/docs/style-dictionary.md

@@ -3,6 +3,7 @@ isIndex: false
 title: Style Dictionary
 description: How component token JSON is compiled to CSS, and how cross-package references to design-tokens are resolved.
 weight: 5
+icon: gear
 ---
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uncinq/component-tokens",
-  "version": "1.10.0",
+  "version": "1.10.1",
   "description": "Framework-agnostic CSS design tokens — component layers.",
   "license": "MIT",
   "repository": {