docs(brand): canonical terracotta #C05734 + scope the dark-first rule to product surfaces #99
No reviewers
Labels
No labels
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Toilville/toilville-design!99
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/toilville-web-palette-tokens"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Re-opens the content of #98, which got merged into #97's branch instead of
mainand had its source branch deleted. #97 is now inmain, so this targetsmaindirectly and adds only the two terracotta commits.Why
brand.primaryhad two values in circulation. Canonical DTCG says#C05734;CLAUDE.md, the toilville-fse theme, the design-sync conventions and a pile ofgenerator fallbacks still said
#CC5C37.It is not cosmetic — white text passes on
#C05734(4.51:1) and fails on#CC5C37(4.07:1). The two website design files we just reviewed disagreewith each other for exactly this reason.
Corrected
CLAUDE.md— the<frontend_aesthetics>colour table + the skin.css exampleREADME.md— the canonical ANSI 256 mapping table.design-sync/conventions.toilville.md,.design-sync/remote-stage/tokens/colors.cssudg/products/wp-themes/toilville-fse/theme.json—primary,color-1,color-7udg/products/rituals/bbs-style.yml— the mapping commentudg/icon-registry/ICON_ISSUES_GITHUB.mdudg/generators/templates/extra.css— everyvar(--accent, …)fallback. Thisfile already mixed both hexes line-to-line, so it is now uniform.
Left alone on purpose
Brand/specs/rituals/rituals-color-theme-light.md— the Rituals sidebar-bggenuinely is
#CC5C37, a distinct token frombrand.primary. Not drift.docs/reviews/theme-alignment-strategy.md— historical record of this exactdrift; rewriting it would erase the finding.
The ANSI
166mapping is hardcoded config, not derived from the hex, so themapping is unaffected. (Neither hex is actually the nearest ANSI index — 166 is
a curated terminal choice.)
Also: scoping the dark-first rule
The approved toilville.com design is light-first, which
CLAUDE.mdlisted as ananti-pattern. Now scoped: product surfaces stay dark-cocoa-first;
marketing surfaces (toilville.com,
deck.landing) are light-first bydesign, with dark still available from the token layer's
prefers-color-schemeblock.Verification
just check— fully greenpython -m pytest generator/tests/— 161 passeddist/*/artifact.html(extra.css is a generator template)https://claude.ai/code/session_01Kbzfscp4w5enUrZxMnDt78
`brand.primary` had two values in circulation. Canonical DTCG says #C05734; CLAUDE.md, the toilville-fse theme, the design-sync conventions and several generator fallbacks still said #CC5C37. It is not cosmetic — white text passes on #C05734 (4.51:1) and fails on #CC5C37 (4.07:1). Corrected: CLAUDE.md, README.md (ANSI table), .design-sync/{conventions, remote-stage}, udg/products/wp-themes/toilville-fse/theme.json, rituals bbs-style.yml, udg/icon-registry/ICON_ISSUES_GITHUB.md, and every --accent fallback in udg/generators/templates/extra.css (which already mixed both). Left alone on purpose: Brand/specs/rituals/rituals-color-theme-light.md — sidebar-bg genuinely is #CC5C37, a distinct token from brand.primary docs/reviews/theme-alignment-strategy.md — historical record of this drift Also scopes the <frontend_aesthetics> dark-first rule: product surfaces stay dark-cocoa-first, marketing surfaces (toilville.com, deck.landing) are light-first by design. Claude-Session: https://claude.ai/code/session_01Kbzfscp4w5enUrZxMnDt78