@devexpress/design-tokens-internal 262.14.0 → 262.15.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devexpress/design-tokens-internal",
-  "version": "262.14.0",
+  "version": "262.15.0",
   "description": "",
   "license": "ISC",
   "author": "",

package/tokens/components/README.md

@@ -11,6 +11,9 @@ tokens/components/
 │   │   └── fluent_small.json, fluent_medium.json, fluent_large.json, material_medium.json
 │   └── theme/     ← size-independent tokens, one file per theme
 │       └── fluent.json, material.json
+├── vnext/         ← vNext product tokens (same size/ + theme/ structure)
+│   ├── size/
+│   └── theme/
 ├── blazor/        ← web-specific overrides and extensions (same size/ + theme/ structure)
 │   ├── size/
 │   └── theme/
@@ -19,16 +22,20 @@ tokens/components/
         └── fluent.json
 ```
 
-`core/` and `blazor/` use the **`size/` + `theme/`** structure: `size/` holds tokens whose values depend on the size mode (`small` / `medium` / `large`), `theme/` holds everything else. Available themes are **`fluent`** and **`material`**. `wpf/` still uses the legacy per-component structure with one `fluent.json` per component, until the WPF team switches (see [stability zones](../../docs/stability.md)).
+`core/`, `vnext/`, and `blazor/` use the **`size/` + `theme/`** structure: `size/` holds tokens whose values depend on the size mode (`small` / `medium` / `large`), `theme/` holds everything else. Available themes are **`fluent`** and **`material`**. `wpf/` still uses the legacy per-component structure with one `fluent.json` per component, until the WPF team switches (see [stability zones](../../docs/stability.md)).
 
 ---
 
-## Three-tier hierarchy
+## Folder roles
 
 ### `core/` — Source of truth
 
 Tokens exported directly from the Figma design file. The `size/` and `theme/` subfolders correspond 1:1 to the shared Figma variable collections (Sizing and Theme). These tokens are **platform-agnostic** — they define the visual anatomy of a component (spacing, colors, border-radius, typography) using semantic token aliases. They do **not** contain raw values.
 
+### `vnext/` — vNext product tokens
+
+The vNext product's own copy of the component tokens, exported from the [vNext UI Kit](https://www.figma.com/design/PjqsaIQHxOoRpvkvbGLFkK/vNext-UI-Kit?m=auto) Figma file (see also the [vNext Data Grid Demo](https://www.figma.com/design/26We86Bbh8ghwgFDYduaKv/vNext-Data-Grid-Demo?m=auto)). Same `size/` + `theme/` structure and conventions as `core/`, but maintained independently by the vNext team.
+
 ### `blazor/` — Blazor overrides
 
 Additions or overrides specific to the web platform (React, Angular, Vue, Blazor WebAssembly). Extends `core/` with web-only states or layout differences.