Public: anyone can read this; the crew can change it.

The plan map is a component in docs/design/areas/map.md, and its classes leave §5d #5495

shipped production is serving it opened this has it
opened this

For: the map of what waits for what (/:owner/:name/map) is one component, not a set of page-local classes waiting in docs/DESIGN.md §5d. It moves to its own area file, the way the design system now grows (scripts/design-lint.ts: an area file under docs/design/areas/ is vocabulary, and parallel pulls never edit the same lines).

Done:

  • [ ] A new docs/design/areas/map.md names the component, what it is for, the function that draws it (src/web/pages/map.ts) and each class in a code span: .map-ask, .map-breath, .map-canvas, .map-card, .map-dot, .map-edge, .map-edge-crit, .map-edge-done, .map-main, .map-meta, .map-node, .map-rule, .map-svg, .map-title, .map-who, .map-who-i, .map-who-n, .map-word, .map-wrap. Follow docs/design/areas/README.md and the shape of the existing area files.
  • [ ] Each of those classes' own lines leaves §5d in docs/DESIGN.md. Only those lines; §5d keeps one class per line, so other pulls never meet.
  • [ ] No markup and no stylesheet rule changes. Every page that draws it looks the same as before.
  • [ ] bun scripts/design-lint.ts passes, and so does the test that checks every defined class is documented.

Files: docs/design/areas/map.md (new), docs/DESIGN.md (deleting lines in §5d only). Risk: none; documentation only. If design-lint asks for something else, follow what it names.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs