/* About page (/lt/apie/, /en/about/) — native-layout port (DB pages 6 / 7).
   apglebk.css and blocks.css are NOT edited (other agents work in them in
   parallel); the one rule this port needs lives here.

   Three sections paint a background that differs from the page background
   (#FAF7F5) and so must become bleed sections (`align:full` on a section with
   `layout:{"type":"constrained"}`, per apglebk.css's own comment at the
   `.wp-block-post-content.is-layout-constrained` rule: "a section that bleeds
   is alignfull; core negates the padding for it. If its copy must sit on the
   rail, give THAT group a constrained inner layout"):
     apg-section-10858258 (apie-roles,    #EAEFFE)
     apg-section-76b75b09 (apie-values,   #E6ECE5)
     apg-section-0d6ab989 (apie-contacts, #FFFFFF)

   Each of those classes sets its vertical rhythm with a `padding: Xrem 0`
   SHORTHAND, which explicitly zeroes padding-left/right. Once the section is
   alignfull + has-global-padding, that explicit 0 has the same (0,1,0)
   specificity as core's `.has-global-padding { padding-left/right: var(...) }`
   rule and, being the theme's own stylesheet, wins the cascade tie — so the
   gutter that is supposed to put these sections' copy back on the rail never
   applied: measured at 402px viewport the rail child came out 402px wide
   (0..402) instead of 320px (41..361), reflowing text and shrinking
   apie-values/apie-contacts by 66px/45px versus the pre-port page.

   This is the same shape of fix already applied to home.css's `.ap-banner`
   and kept as a documented pattern in the "18. Paremkite" section of
   apglebk.css itself ("write vertical padding as longhands so the shorthand
   does not reset that gutter to 0") — restate top/bottom as longhand, and
   restate left/right explicitly as the same root-padding variable
   has-global-padding would have supplied, since blocks.css's own
   `apg-section-*` rule (unedited, still present, loaded before this file)
   also writes left/right:0 via its own shorthand and would otherwise still
   win the cascade tie against `.has-global-padding` for those two
   properties even though this file no longer competes on them itself. */
.apg-section-10858258 {
    padding-top: 5rem;
    padding-bottom: 5rem;
    padding-left: var(--wp--style--root--padding-left);
    padding-right: var(--wp--style--root--padding-right);
}
.apg-section-76b75b09 {
    padding-top: 5.5rem;
    padding-bottom: 5.5rem;
    padding-left: var(--wp--style--root--padding-left);
    padding-right: var(--wp--style--root--padding-right);
}
.apg-section-0d6ab989 {
    padding-top: 6rem;
    padding-bottom: 5rem;
    padding-left: var(--wp--style--root--padding-left);
    padding-right: var(--wp--style--root--padding-right);
}

/* Mobile: the About hero is a rounded rail card like every other hero
   (owner's call, 5 Sep 2026); copy at gutter + 1rem. */
@media (max-width: 640px) {
    .apie-hero .apg-div-8110b68c { padding-left: 1rem; padding-right: 1rem; }
}

/* The hero wrapper / grid are wp:groups and carried core's default 36px group
   padding, so the painted card started at y=137 while every other page's
   first block starts at 101 (24px under the header). */
.apie-hero .apg-div-456ddcc6,
.apie-hero .apg-div-8233f316 { padding-top: 0; padding-bottom: 0; }
@media (max-width: 640px) {
    /* band and photo touch, as in the Figma frame */
    .apie-hero .apg-div-8233f316 { gap: 0; }
}