/* ===================================================================== LEGAL -- the paired sheet for templates/legal.php Story 4 of `_bmad-output/specs/spec-contact-page/SPEC.md` (CAP-6). The plainest stylesheet in this theme, and deliberately so: a centred prose measure, the rhythm a long document needs between its headings, lists and paragraphs, and nothing else. There is no component here, no layout, no breakpoint and no drawing behind it. WHAT THIS SHEET DOES NOT DECIDE. It declares no colour VALUE -- no hex literal appears below. Every colour on this page resolves from a role site-interactive-states.css already decided against the white ground: `--ground-ink` for body text, the four `--state-link-*` roles for the links. If one of those values is wrong it is wrong everywhere and is fixed there, once. THE COLUMN IS LIFTED FROM contact.css:120-128, which lifted it from simple-stack.css:255, and both halves of the reasoning come with it rather than being re-derived here. It is a deliberate third copy and not an extraction: the three sheets load on mutually exclusive pages, so a shared file would be a fourth stylesheet in every bundle to save six lines in each. THERE IS NO PAIRED SCRIPT. functions.php's emitter guards the `js` key with `! empty()`, and the `project` archive has shipped css-only since v1.11.16 -- so a missing script is a supported shape rather than the silently-dropped-handle failure a missing SHEET would be. A legal document has no behaviour; shipping an empty file to satisfy a pattern would be a file to maintain and a request to make for nothing. ===================================================================== */ /* ===================================================================== THE COLUMN `min(760px, 100% - 2 * var(--band-gutter, 15px))` is this codebase's prose measure. 760px is the measure itself; the second term is the gutter, and the `min()` is which of the two is binding at this viewport. A Page with no template takes the full site band as its measure and sets policy text across all of it, which is exactly what makes this file necessary. IT CHANGED FORM AT v1.14.0 AND THE REASON IS THE WHOLE LESSON HERE. It was `max-width: min(760px, var(--container, 760px))` plus `padding: 64px 15px 96px`, which is the same thing ONLY WHILE THE GUTTER IS A CONSTANT. `--band-gutter` now ramps to 56px at 1400, and under the old form a border-box `max-width` of 760 with 56px of padding inside it left a 648px measure -- the gutter eating 15% of a reading column it was never sized against. The gutter belongs OUTSIDE a narrow measure and INSIDE a full-width band; `width: min(measure, 100% - 2 * gutter)` is how you say that in one declaration, and it needs no horizontal padding at all. WHAT IT COMPUTES TO, AND NOTE THE DESKTOP ROW IS A RESTORATION: viewport gutter column was (v1.13.41) 390px 20px 350px 345px -- inset now matches the chrome 600px 24px 552px 570px 1400px 56px 760px 730px -- the full drawn measure, at last THE `--container` TERM WAS DROPPED, NOT LOST. It was there so the column could never outgrow the chrome band above it. `100%` subsumes it: the chrome's content width is `min(viewport, --container) - 2g` and this column is `min(760, viewport - 2g)`, so the column is never the wider of the two at any viewport -- by construction now, rather than by a dial whose mobile tier (748px) happened to sit just below 760. One fewer database value this rule depends on. THE 15px INSIDE THE `var()` IS NOT DECORATION, and the failure it guards is the same one the old fallback guarded, one level out: an unresolved custom property inside `min()` makes the whole function invalid at computed-value time, which drops `width` back to `auto` -- the column would silently go full-bleed, which is the one failure this rule exists to prevent. With the fallback it degrades to a flat 15px inset, i.e. to what shipped through v1.13.41. `box-sizing: border-box` IS RETAINED AND IS NO LONGER LOAD-BEARING HORIZONTALLY -- there is no horizontal padding left for it to govern. It stays for the vertical padding and for the next person who adds a border, and because Neve sets it globally anyway; this rule simply no longer depends on that global for its measure. ===================================================================== */ .legal-page { width: min(760px, 100% - 2 * var(--band-gutter, 15px)); margin: 0 auto; box-sizing: border-box; padding: 64px 0 96px; font-family: var(--font-body); color: var(--ground-ink); } /* ===================================================================== RHYTHM A policy page is a document rather than a composition: its whole visual job is to be scannable down a single column, which is spacing and almost nothing else. NO `font-size` ON ANY HEADING, and the omission is load-bearing. Neve's typography theme_mods bind `--h1fontsize`/`--h2fontsize` and their letter-spacing from an inline