Commit graph

1 commit

Author SHA1 Message Date
Tom Huang
56aa985b1a
feat(design-systems): integrate kami as editorial paper system + deck starter (#226)
* feat(design-systems): integrate kami as editorial paper system + deck starter

- Add design-systems/kami/DESIGN.md adapting kami's tokens, ten invariants,
  and type/color/component rules into the OD DESIGN.md spec. Lands under a
  new "Editorial & Print" category in the picker.
- Add templates/kami-deck.html: a kami-flavored variant of deck-framework.html
  (parchment canvas, ink-blue accent, single-weight serif) with five demo
  slides — cover, agenda, metric row, two-column body+pull-quote, closing —
  so it doubles as a worked example for slide and prototype work.
- Update design-systems/README.md and README.md to list and credit kami
  (MIT, tw93/kami).
- Update apps/web/src/i18n/content.ts so the i18n coverage test passes:
  add the German summary for 'kami' and the 'Editorial & Print' category.

* docs(design-systems/kami): address PR #226 review notes

Five P3 polish edits from @lefarcen's review (LGTM, non-blocking):

1. Add a "When to swap the stack" subsection in §3 spelling out how the
   three CJK font stacks combine: set the dominant-language stack on
   :root, scope per-section overrides for mixed-language artifacts,
   never chain all three families inside one font-family declaration.

2. Reframe the brand as "kami / 紙 / 纸" so the system reads as
   co-designed across EN, zh-CN, and ja from the start, not Japan-centric
   with i18n bolted on. Title and §1 lede updated.

3. Reconcile the pt → px ratios into one table at the top of §3
   "Hierarchy": print pt × ~1.33 for page artifacts, × 1.6 for slide
   macro tokens, × 0.6 for slide micro tokens. Drop the duplicate
   ratio bullets from §5 "Slides".

4. Keep the soft tag-brush gradient exception but make it real: add
   the .tag.brush CSS + an inline <span class="tag brush"> example
   in §4, and surface it once on slide 04 of the kami deck so agents
   see exactly when the carve-out applies.

5. Add a "Tabular-nums contexts" subsection in §3 enumerating every
   place numbers should opt into tabular-nums (metrics, footers,
   section numbers, dates, financial tables, KPI grids, version
   numbers, side-by-side comparisons) — and the rule for when not to
   (single numbers in running prose).
2026-05-02 11:00:56 +08:00