aboutsummaryrefslogtreecommitdiff
path: root/todo.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-09 13:29:58 -0500
committerCraig Jennings <c@cjennings.net>2026-06-09 13:29:58 -0500
commit392f45f4dd35d1b0c48210752546ab484436eac0 (patch)
treee9e05abe78d832209398cc99f2807fc624e1b065 /todo.org
parent14f1a1c631306ded5f1f345b80c54bfa1bd9bc7e (diff)
downloaddotemacs-392f45f4dd35d1b0c48210752546ab484436eac0.tar.gz
dotemacs-392f45f4dd35d1b0c48210752546ab484436eac0.zip
docs(theme-studio): separate Design Rules from Fidelity Rules
Diffstat (limited to 'todo.org')
-rw-r--r--todo.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/todo.org b/todo.org
index 48df7579..4956d315 100644
--- a/todo.org
+++ b/todo.org
@@ -50,7 +50,7 @@ Investigation start: the two-color contrast cells are =paintUI= (UI faces, app.j
The mode-line box (3D released-button bevel) in the live buffer preview renders slimmer than the bevel Emacs actually draws. Make them match. The bevel comes from =boxCss= in app.js (~line 307), currently =inset 1px 1px 0 #ffffff33,inset -1px -1px 0 #00000066= for the released style — a 1px inset with faint translucent highlight/shadow. Emacs's released-button box is wider/stronger (it shades the highlight and shadow from the actual background color, not a flat translucent white/black). Fix: widen the bevel and derive the highlight/shadow from the box's background so it reads like Emacs. Verify side-by-side against a real Emacs mode-line.
** TODO [#C] theme-studio face-consistency check :feature:theme-studio:
-Two related checks, both surfacing structural-attribute (weight/slant/underline/box/overline/height) issues; color is the theme's design and out of scope.
+Rule taxonomy captured in [[file:docs/design/theme-studio-face-rules.org][docs/design/theme-studio-face-rules.org]] (Design Rules vs Fidelity Rules). The two checks below map to those two rule kinds. Both surface structural-attribute (weight/slant/underline/box/overline/height) issues; color is the theme's design and out of scope.
1. Theme cross-cutting consistency (primary, per Craig 2026-06-09): the theme has deliberate cross-cutting rules — e.g. headings/titles are bold, links are underlined, errors/warnings/success are bold. Flag where the theme BREAKS ITS OWN rule (a heading that isn't bold, a link that isn't underlined). The designer declares the rules; the check finds the violators. This is the "tell me where I broke the rule" guardrail.