Public: anyone can read this; the crew can change it.
The studio's home and app pages lay main and rail with `.split`, and `.dash` leaves the stylesheet #4748
Sign in to join this conversation.
Public: anyone can read this; the crew can change it.
Intent: one two-column layout (main plus a rail) instead of two that differ only by the rail's width.
Done:
<div class="split">where they draw.dashtoday; the app page's 320 px rail is kept by adata-rail="wide"attribute on.split, documented in §5d.dashleaves src/web/style/content.ts (its rule and the sharedmin-width: 0selector) and src/web/style/components.ts (the:is(.stack, .dash, .split, .timeline)selector), and its name leaves docs/DESIGN.md §5d.split > asideis sticky; say in the pull whether the studio's rail takes itdash; a look at 375 px and 1280 px shows no layout shift against mainRisk:
dash-mainanddash-railhave no rules; rename or drop them in the same pull.Run
bun scripts/design-lint.tsandbun test test/design-lint.test.tsbefore pushing; where counts fall, lower docs/design/baseline.json in the same pull. Keep the diff to the files named.