You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/PLANNING.md
+29-20Lines changed: 29 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,13 +27,15 @@ What we could working on next.
27
27
28
28
Everything we could attempt given sufficient time and resources.
29
29
30
-
### Deterministic sorting (linting)
30
+
### Tokens evolution
31
+
32
+
#### Deterministic sorting (linting)
31
33
32
34
- JS import/export ordering via ESLint autofix
33
35
- JSON key-order enforcement for selected token paths (including top-key conventions like `$schema` / `$type` / `$description` / `default`)
34
36
- Alphabetical sorting
35
37
36
-
### Machine-readable intent
38
+
####Machine-readable intent
37
39
38
40
- Expand token/group `$description` coverage for intent guidance:
39
41
- usage guidance for humans/agents
@@ -43,14 +45,14 @@ Everything we could attempt given sufficient time and resources.
43
45
- stable fields for tooling/agents beyond prose descriptions
44
46
- worked examples where intent is easy to misuse
45
47
46
-
### Design model evolution
48
+
#### Design model evolution
47
49
48
50
- Light/dark inverse surfaces
49
51
-`density` context (class-based in CSS) — current size context grid/spacing is broadly editorial/comfortable in nature, this may be fine, but may want to add a ui/compact mode
50
52
- Border and Transition DTCG Composites
51
53
- Give wireframe theme an actual design
52
54
53
-
### Style Dictionary DTCG 2025.10 gaps
55
+
####Style Dictionary DTCG 2025.10 gaps
54
56
55
57
[Support for DTCG v2025.10](https://github.com/style-dictionary/style-dictionary/issues/1590)
56
58
@@ -59,45 +61,47 @@ Everything we could attempt given sufficient time and resources.
- reduce/remove custom resolver->SD source adaptation where SD can natively consume resolver semantics
61
63
62
-
### Export target evolution
64
+
#### JSON export target
65
+
66
+
Define a stable JSON artifact contract for downstream consumers (including docs) so metadata and token data can be consumed without coupling to internal bridge/build intermediates. Likely `packages/tokens` / `@measured/calibrate-tokens`.
67
+
68
+
Note: pipeline is currently hard-coded to CSS; probably add optional `--formats` in `packages/system/scripts/pipeline/index.mjs` when implementing a second export target.
69
+
70
+
#### Export target evolution
63
71
64
72
1. Penpot
65
73
1. Figma
66
74
1. VS Code token lookup artifact
67
75
1. iOS
68
76
1. Android
69
77
70
-
Note: pipeline is currently hard-coded to CSS; probably add optional `--formats` in `packages/system/scripts/pipeline/index.mjs` when implementing a second export target.
78
+
### Further evolution
71
79
72
-
### Automated checks
80
+
#### Assets package
73
81
74
-
Stylelint/ESLint/axe; token-name lint rules; forbid raw hex/px; PR templates require a11y notes, screenshots, and before/after diffs.
82
+
Decide whether shared fonts/images should ship as a dedicated package and define what is stable asset API vs implementation detail.
75
83
76
-
###JSON export target
84
+
#### Shareable automated checks
77
85
78
-
Define a stable JSON artifact contract for downstream consumers (including docs) so metadata and token data can be consumed without coupling to internal bridge/build intermediates.
86
+
Stylelint/ESLint/axe configs; token-name lint rules; forbid raw hex/px; PR templates require a11y notes, screenshots, and before/after diffs.
79
87
80
-
### Minimal viable publish
88
+
####Minimal viable publish
81
89
82
90
Define the minimum scripts, workflow, and release notes needed to publish initial alpha packages and unblock downstream adoption tasks.
83
91
84
-
### Documentation website (`apps/documentation`)
85
-
86
-
Stand up a docs site that consumes published token/component packages and serves as the canonical reference for usage, contracts, and examples.
92
+
#### Documentation website (`apps/documentation`)
87
93
88
-
### Assets package
89
-
90
-
Decide whether shared fonts/images should ship as a dedicated package and define what is stable asset API vs implementation detail.
94
+
Stand up a docs site that consumes published token/component packages and serves as the canonical reference for usage, contracts, and examples. Deploy to `http://calibrate.msrd.dev`, `apps/storybook` can deploy to `http://calibrate.msrd.dev/storybook/`
91
95
92
-
### CLI bootstrap tool
96
+
####CLI bootstrap tool (`@measured/calibrate`)
93
97
94
98
Scope a `calibrate` bootstrap CLI for fast project scaffolding with sensible defaults for tokens, components, and optional assets.
0 commit comments