/** * Global base styles * ------------------ * Restores the foundation the previous parent theme used to provide and the * current boltpress parent no longer does: global body/heading typography and * a content container for generic pages rendered by the parent templates * (page.php / single.php / archive.php / index.php), e.g. /apie-mus/. * * Without this, inherited text falls back to the browser serif default and * generic-page content (`main.site-main`) runs edge-to-edge with no width * constraint. Pages with their own layout (home, contact, search, WooCommerce) * are excluded so this never double-wraps them. * * Uses the legacy token names (resolved by token-compat.css) with hardcoded * fallbacks matching the design tokens, so it also holds up if the design * system is disabled. Loads after token-compat.css but before component CSS so * components keep overriding it. */ /* ---- Global base typography --------------------------------------- * A FAITHFUL restore of what boltpress 1.0.0's generator emitted for this site * (see the compiled design-tokens.css). Declaration-for-declaration, no additions: * the whole point is that swapping the parent is a pixel no-op. * * In particular there is NO line-height here. 1.0.0 emitted line-height NOWHERE * (zero occurrences in its compiled output), so a `body { line-height: 1.5 }` would * be inherited by every element that doesn't set its own — WooCommerce cart / * my-account / notices, widget and comment text — and reflow them ~15% taller. That * is a redesign, not a bridge. Prose line-height is set on .entry-content below, * where it is scoped and intentional. */ body { font-family: var(--font-family-body, "DM Sans", sans-serif); font-size: var(--font-size-base, 16px); font-weight: var(--font-weight-normal, 400); color: var(--color-text, #777e90); background-color: var(--color-background, #ffffff); } /* Heading scale, per level, matching 1.0.0 exactly. The colour comes from the * PER-LEVEL --color-headings-h1..h6 tokens (not --color-headings-general): all six * are #252a36 today, so it renders identically, but using the general token would * silently swallow any future per-level colour edit made in the admin. * * The load-bearing surfaces are the WooCommerce-default

inside * .woocommerce-billing-fields (form-checkout.php calls * do_action('woocommerce_checkout_billing') and we ship no form-billing.php) and * editor-authored h4/h5/h6 inside .entry-content — without a size they fall to UA * defaults (h3 20px -> 18.72px, h4 18px -> 16px). * * No margin-bottom and no .h1-.h6 class variants: 1.0.0 emitted the former only from * a spacing.md token this site does not have, and the latter have zero usage here. */ h1, h2, h3, h4, h5, h6 { font-family: var(--font-family-heading, "DM Sans", sans-serif); font-weight: var(--font-weight-bold, 700); } h1 { font-size: var(--font-size-3xl, 30px); color: var(--color-headings-h1, #252a36); } h2 { font-size: var(--font-size-2xl, 24px); color: var(--color-headings-h2, #252a36); } h3 { font-size: var(--font-size-xl, 20px); color: var(--color-headings-h3, #252a36); } h4 { font-size: var(--font-size-lg, 18px); color: var(--color-headings-h4, #252a36); } h5 { font-size: var(--font-size-base, 16px); color: var(--color-headings-h5, #252a36); } h6 { font-size: var(--font-size-sm, 14px); color: var(--color-headings-h6, #252a36); } /* LOAD-BEARING. The old parent pinned every paragraph to 16px. Without this, blog * paragraphs inherit .militra-post-content's 19px (single-post.css) — its own `p` * rule sets only margin-bottom — which re-typesets every post. Restored so the * parent upgrade stays a visual no-op. */ p, .wp-block-paragraph { font-size: var(--font-size-base, 16px); } /* Global link colour. The old parent painted every bare ; the new parent emits * only :root vars, so links the child never paints (WooCommerce cart / my-account * body links, notice links, comment and widget links) revert to UA blue. * Specificity 0,0,1 — every component rule, and `.entry-content a` below, still win. */ a, .wp-block-navigation-item__content { color: var(--color-links-initial, #797979); } a:hover, .wp-block-navigation-item__content:hover { color: var(--color-links-hover, #252a36); } /* Brand text-selection highlight. Background ONLY — the old parent never set `color` * here (it had no white colour token), and token-compat.css DOES define --color-white, * so adding `color: var(--color-white)` would be a behaviour change, not a restore. */ ::selection { background-color: var(--color-primary, #ff7544); } /* Global form controls. The old parent supplied these; the new parent supplies nothing. * The load-bearing half is border / radius / font-size / font-family plus the label * rule: without them, WooCommerce login+register on /paskyra/, the review form and the * shipping calculator render as UA-default inset 13px Arial boxes. * * No padding and no label margin-bottom: the old parent emitted neither (spacing.sm / * spacing.xs do not exist in this token set). Copied verbatim so the upgrade is a pixel * no-op. All selectors are 0,0,1 — every child class-scoped rule still wins. */ input[type="text"], input[type="email"], input[type="password"], input[type="url"], input[type="tel"], input[type="number"], input[type="search"], textarea, select { font-size: var(--font-size-base, 16px); font-family: var(--font-family-body, "DM Sans", sans-serif); border-radius: var(--border-radius-md, 15px); border: 1px solid var(--color-border, #000000); width: 100%; box-sizing: border-box; } input[type="text"]:focus, input[type="email"]:focus, input[type="password"]:focus, input[type="url"]:focus, input[type="tel"]:focus, input[type="number"]:focus, input[type="search"]:focus, textarea:focus, select:focus { border-color: var(--color-primary, #ff7544); outline: none; } label { font-weight: var(--font-weight-medium, 500); display: block; } /* ---- Generic-page content layout ---------------------------------- * * Targets parent-template pages only (e.g. /apie-mus/, rendered by the parent's * page.php). Excludes every template that owns its own layout: * .home / .page-template-front-page -> front-page.css (full-bleed) * .search -> search.css * .woocommerce / .woocommerce-page -> shop / category / product CSS * .site-main.contact-page -> contact-page.css * .site-main.militra-blog -> blog-archive.css (own shell + container) * .site-main.militra-single -> single-post.css (own 1360px journal spread) * * The last two exclusions are LOAD-BEARING. The child's own home/index/archive/ * page-naujienos templates emit `class="site-main militra-blog"` and single.php emits * `class="site-main militra-single"` — none of which is a WooCommerce or search body * class, so without these :not()s this rule matches them too. It would then clamp the * journal spread to 1264px (single-post.css explicitly needs 1360px: 704 prose + * 2x240 rail + 2x64 gutter + 2x24 padding), starving the TOC/related rails from ~240px * to ~168px, and would add 48px/24px padding to the blog listing that its own shell * already handles. Both templates would visibly change the moment the bridge came on. */ body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page):not(.militra-blog):not(.militra-single) { max-width: var(--header-width-max, 1264px); margin-left: auto; margin-right: auto; padding: var(--spacing-12, 48px) var(--spacing-8, 24px) var(--spacing-16, 64px); box-sizing: border-box; } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-header { margin-bottom: var(--spacing-6, 18px); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-title { font-size: var(--font-size-4xl, 36px); font-weight: var(--font-weight-bold, 700); color: var(--color-headings-h1, #252a36); margin: 0 0 var(--spacing-4, 16px); line-height: var(--line-height-tight, 1.25); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content { font-size: var(--font-size-base, 16px); line-height: var(--line-height-relaxed, 1.75); color: var(--color-text, #777e90); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content > * { margin-top: 0; margin-bottom: var(--spacing-4, 16px); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content h2 { font-size: var(--font-size-2xl, 24px); margin-top: var(--spacing-8, 24px); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content h3 { font-size: var(--font-size-xl, 20px); margin-top: var(--spacing-6, 18px); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content a { color: var(--color-primary, #ff7544); text-decoration: underline; } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content img { max-width: 100%; height: auto; border-radius: var(--border-radius-md, 15px); } body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content ul, body:not(.home):not(.page-template-front-page):not(.search):not(.woocommerce):not(.woocommerce-page) .site-main:not(.contact-page) .entry-content ol { padding-left: var(--spacing-6, 18px); } /* ---- Button compatibility ---------------------------------------- * * Two changes the boltpress parent made to its button CSS API broke child * buttons: * (a) it renamed its button classes .boltpress-btn-* -> .bp-btn-*, so the * child's .boltpress-btn-primary/secondary CTAs (used as in the hero * and buy-now) lost all appearance and render as default blue links; * (b) its generated design-tokens.css now paints EVERY bare