/** * Core layout defaults, neutralised — loaded BEFORE qubi360.css. * * Cascade position is the whole point of this file. Three stylesheets run in order: * * 1. core's global-styles (inline, in ) * 2. this file — undoes the layout defaults the design does not want * 3. qubi360.css — the design, untouched, re-asserts whatever it needs * 4. wp.css — reconciliation that must beat the design * * Everything here is written at (0,1,0), the same weight core uses, so the design * in step 3 wins any tie by loading later. Putting these rules in wp.css instead * would flip that: they would beat the design and flatten its own spacing. */ /* Core ships `:root :where(.is-layout-flow) > * {margin-block-start:24px}`, which applies at every nesting depth. The q- components set their own vertical rhythm through padding, borders and explicit margins, and most of them are flex or grid rows where an injected block margin simply pushes items out of alignment — it was offsetting the header nav, the footer legal row and every .q-tagline. Two forms, because the wrong margin turns up both on a q- container's own children (.q-tagline, .q-nav) and further down inside one (.comment-meta sits in .q-comments and has no q- class of its own, but the design still owns its spacing). Anything the design does want back it states explicitly and later: .q-prose re-asserts `> * + * {margin-top:24px}` from qubi360.css, which is why the article body still spaces correctly. */ /* A third form, for the case the first two miss: the flow container has no q- class and no q- ancestor, but its children are the design's own elements. That is exactly the
wrapper in every template — a plain wp-block-group whose children are the .q-sec bands — so without this core drops 24px of white between every section, which reads as a gap in each tinted and inked band. */ .is-layout-flow:where([class*="q-"]) > *, :where([class*="q-"]) .is-layout-flow > *, .is-layout-flow > :where([class*="q-"]) { margin-block-start: 0; margin-block-end: 0; }