refactor(frontend): invert the dashboard + H0M3 gutter (#1537)
Follow-up from #1532. Previously `body.dashboard-shell` / `body.home-shell` carried the 1.5em horizontal gutter, and full-width chrome broke out of it with negative margins (`.dashboard-chrome { margin: 0 -1.5em }`, the `#server-warnings { margin: 0 -1.5em }` override). Invert it: `<body>` is now full-bleed, and the padded page content lives in a single inner `.page-content` wrapper that carries the gutter. The server-warnings banner, the sticky tab strip, and the footer then span the full width for free — so the `-1.5em` breakout hacks are gone. - `.page-content { padding: 0 1.5em }` is a shared primitive in common.css (the dashboard + H0M3 both opt in by wrapping their content; FL0W / L0GS / ST4TS / S3TT1NGS stay full-bleed with their own `.<page>-main` padding). - dashboard.html / index.html wrap their content in `.page-content`. - dashboard.css / home.css: drop the body horizontal gutter (keep `padding-bottom` for foot breathing room); `.dashboard-chrome` margin `0 -1.5em 1em` → `0 0 1em`. - common.css: drop the `#server-warnings` breakout override. Behaviour/visual-neutral by intent (content gutter unchanged; chrome + banner already rendered full-width via the old breakout). Worth a gui screenshot-diff to confirm — esp. the now-full-width footer divider. Last fold-in of #1464 step 2.
This commit is contained in:
parent
df3058e311
commit
293e608ca4
5 changed files with 38 additions and 19 deletions
|
|
@ -9,14 +9,15 @@
|
|||
routing model. */
|
||||
|
||||
body.dashboard-shell {
|
||||
/* Full-width layout — no max-width cap so wide screens don't
|
||||
waste real estate on empty side margins. `padding: 0 1.5em
|
||||
1.5em` keeps a small gutter on the left/right so cards don't
|
||||
kiss the viewport edge; `.dashboard-chrome { margin: 0 -1.5em
|
||||
... }` still pulls the chrome bar edge-to-edge through that
|
||||
gutter. */
|
||||
/* Full-bleed body (no horizontal gutter). The 1.5em side gutter lives
|
||||
on the inner `.page-content` wrapper (see common.css), so the sticky
|
||||
chrome bar, the server-warnings banner, and the footer span the full
|
||||
width edge-to-edge with no negative-margin breakout. `padding-bottom`
|
||||
keeps a little breathing room above the viewport edge (overridden to
|
||||
clear the selection bar via `.has-selection` below). No max-width cap
|
||||
— wide screens use the full width rather than empty side margins. */
|
||||
margin: 0;
|
||||
padding: 0 1.5em 1.5em;
|
||||
padding-bottom: 1.5em;
|
||||
}
|
||||
|
||||
.dashboard-chrome {
|
||||
|
|
@ -28,7 +29,7 @@ body.dashboard-shell {
|
|||
backdrop-filter: blur(8px) saturate(120%);
|
||||
border-bottom: 1px solid var(--purple-dim);
|
||||
padding: 0.4em 0 0;
|
||||
margin: 0 -1.5em 1em;
|
||||
margin: 0 0 1em;
|
||||
}
|
||||
/* ← home back-link to the H0M3 hub. Small purple link top-left of the
|
||||
chrome, mirroring the .logs-back treatment the sub-pages use so the
|
||||
|
|
|
|||
Loading…
Reference in a new issue