feat(css): add --sidebar-* chrome tokens (LC-554 phase 1b) #523
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/LC-554-sidebar-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?
LC-UI-01 phase 1b: introduce
--sidebar-*chrome tokens (CSS only, no visual change)Second slice of LC-554 (epic LC-553). Adds a dedicated
--sidebar-*token family so the room sidebar can get its own dark-navy Blue Harbor identity, following the exact pattern the enclave rail already uses (--rail-*, consumed via raw CSS rules, not Tailwind utilities).What changed
Six tokens defined in all four theme blocks (
:root,[data-theme=dark],hc-light,hc-dark):--sidebar-surface,-elevated,-sunken,-content,-muted,-border.:root: dark-navy chrome#071a2fover the light page - the signature Blue Harbor look. The light sidebar deliberately mirrors the dark theme's navy surfaces.#041326) so it still reads as distinct chrome (same posture as the rail).Why it is safe
w-64sidebar templates still usebg-surface-sunken; unused CSS custom properties render nothing, so this is+39lines of pure additions with zero visual change and no Tailwind rebuild..lc-sidebar { background: var(--sidebar-surface) }rules + template wiring) is LC-560 / LC-UI-07, where the dark sidebar actually lands.🤖 Generated with Claude Code
https://claude.ai/code/session_011jXpZXXwpB36MvTr6JrGXN