/** * Адвокат Бургас — the bridge layer. * * Three stylesheets ship, in this order: * * 1. assets/fonts/fonts.css @font-face, self-hosted, Cyrillic first * 2. assets/css/advokatburgas-tokens.css every --advb-* custom property * 3. assets/css/advokatburgas.css the 20 design-system components * 4. this file WordPress block output → those components * * The first three are generated by @inkblot-studio/advokatburgas-ds and are * never edited here — regenerate them from the token repo instead. This file is * the only hand-written CSS in the theme, and it exists for one reason: the * design system describes hand-written markup, while a block theme renders * `.wp-block-*`. Everything below translates between the two. * * The rule that governs every line: no literal colour, size, shadow or duration. * If a value is not a --advb-* token, it does not belong here. Where a block * needs the exact treatment a component already carries, prefer adding the * component class to the block's markup (or via a render_block filter in * inc/design-system.php) over restating the rules. * * Contents * 1 Document 5 Blocks 9 Redesign components * 2 Masthead + nav 6 Article & prose 10 Editor-facing niceties * 3 Drawer 7 Query loops 11 Print * 4 Footer 8 Contact + form */ /* ========================================================= 1 document */ /* * Nothing here sets `overflow-x: hidden` on the body. * * It is the usual reflex for a stray horizontal scrollbar, and it costs more * than it fixes: it makes the scroll container, which breaks * `position: sticky` on the masthead and stops `scroll-margin` working for the * skip link. The right fix is for nothing to overflow in the first place — * every wide thing on this site (tables, the map, the practice grid) is inside * its own container, and `.advb-container` is border-box so its gutter cannot * push it past 100%. */ /* * `wp-site-blocks` is the wrapper WordPress prints around every template. It * gets the root padding from theme.json, which would double up with the gutter * .advb-container already applies. Sections own their own gutters. */ .wp-site-blocks > * { margin-block: 0; } .advb-root .wp-site-blocks { padding-left: 0; padding-right: 0; } /* Restore the constraint that theme.json's root padding used to provide, but only for blocks that opted into a constrained layout. */ .advb-root :where(.is-layout-constrained) > :where(:not(.alignleft):not(.alignright):not(.alignfull)) { max-width: var(--advb-semantic-layout-measure); margin-inline: auto; } .advb-root :where(.is-layout-constrained) > .alignwide { max-width: var(--advb-semantic-layout-content); } /* * Full-width bands sit flush against each other. * * WordPress's flow layout puts `margin-block-start: var(--wp--style--block-gap)` * on every child after the first, which on this site meant a 24px strip of * page background between the hero and the band under it — a white seam across * a design whose sections are supposed to butt together. Each band carries its * own padding; the gap between them is that padding, not a margin. * * Scoped to the section wrappers. Inside an article the flow margins are what * space the paragraphs, and those are left alone. */ .advb-root .entry-content > *, .advb-root #advb-main > * { margin-block: 0; } /* The skip link ships in the component layer; it only needs to be first. */ .advb-skip-link { position: fixed; } /* * Visually hidden, still announced. Core ships this class with the block * library stylesheet, which a block theme may or may not enqueue on a given * page — the nav toggle's label cannot depend on that. */ .advb-root .screen-reader-text { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); white-space: nowrap; border: 0; padding: 0; margin: 0; } /* ==================================================== 2 masthead + nav */ /* * The navigation block renders