/* ===== tokens.css ===== */
/* ==========================================================================
   AVELaunch Books — design tokens
   Source of truth: WEBSITE_DESIGN (Figma), page "Dekstop"
   Handoff document v1.0, 7 September 2026, sections 6 and 7
   No colour value may be written anywhere outside this file.
   ========================================================================== */

:root {
  /* --- 6.2 Primitive palette ------------------------------------------- */
  --rich-black-1:      #0B1424;  /* body text, inverse surfaces, 3px strokes */
  --rich-black-2:      #E8EDF5;
  --rich-black-3:      #C7D2E3;  /* 1px hairline, vertical grid lines       */
  --rich-black-4:      #93A3BD;
  --rich-black-5:      #5D6C86;  /* secondary text                          */
  --rich-black-6:      #08101D;
  --rich-black-7:      #050A14;

  --space-cadet-1:     #1B2A57;
  --space-cadet-2:     #EEF2FA;
  --space-cadet-3:     #CBD6EC;
  --space-cadet-4:     #9BAED3;
  --space-cadet-5:     #657BA8;
  --space-cadet-6:     #142042;
  --space-cadet-7:     #0D162D;

  --vista-blue-1:      #7C9EC7;  /* brand surface                           */
  --vista-blue-2:      #F3F7FC;  /* spelled "Vista Vlue 2" in the file      */
  --vista-blue-3:      #DCE8F5;
  --vista-blue-4:      #B7CBE3;
  --vista-blue-5:      #93B1D3;

  --columbia-blue-1:   #C2E6F9;
  --columbia-blue-2:   #FCFEFF;
  --columbia-blue-3:   #EEF8FD;
  --columbia-blue-4:   #D9EEF9;
  --columbia-blue-5:   #CBE8FA;

  --amber-1:           #F2BB16;
  --amber-2:           #F9E08A;
  --amber-3:           #F7CD52;
  --amber-4:           #E0A800;  /* accent: buttons, underlines, active     */

  --editorial-white-1: #F8F7F4;
  --editorial-white-2: #FFFFFF;
  --editorial-white-3: #FDFBF8;
  --editorial-white-4: #EEEAE3;  /* page background                         */

  /* --- 6.3 Semantic layer ----------------------------------------------
     Reference map from the file. The layout binds to primitives, exactly
     as the Figma layers do, so this layer stays a dictionary of roles.     */
  --surface-page:       var(--editorial-white-4);
  --surface-brand:      var(--vista-blue-1);
  --surface-accent:     var(--amber-4);
  --surface-inverse:    var(--rich-black-1);
  --content-primary:    var(--rich-black-1);
  --content-secondary:  var(--rich-black-5);
  --content-on-inverse: var(--editorial-white-4);
  --content-accent:     var(--amber-4);
  --content-on-accent:  var(--rich-black-1);
  --content-on-brand:   var(--rich-black-1);
  --border-strong:      var(--rich-black-1);   /* 3px */
  --border-hairline:    var(--rich-black-3);   /* 1px */
  --border-accent:      var(--amber-4);        /* 3px */
  --action-fill:        var(--amber-4);
  --action-fill-hover:  rgba(255, 255, 255, 0); /* no fill on hover        */
  --action-border-hover: var(--amber-4);

  /* --- 4.1 Grid ---------------------------------------------------------
     1440 reference · 12 columns · Stretch · margin 50 · gutter 25
     Working area 1340. Column width is derived, never written down.       */
  --layout-reference: 1440px;
  --layout-margin:    50px;
  --layout-gutter:    25px;
  --layout-content:   1340px;
  --layout-floor:     1200px;   /* lower bound of the desktop layout       */

  /* --- 4.1 Vertical lines ----------------------------------------------
     Seven lines, step 180 of 1440 = 12.5 % of the window.
     THIS IS THE ONLY PLACE THE POSITIONS EXIST. Both layers — the page
     layer under the content and the header layer over its blurred
     background — read them from here. Writing them twice is what makes
     the two layers drift apart at the header edge.                        */
  --line-step:  12.5%;
  --line-width: 1px;
  --line-color: var(--rich-black-3);

  /* --- 8 Effects --------------------------------------------------------
     One effect on the whole site: BACKGROUND_BLUR 50 on the header plate. */
  --header-blur: 25px;
  --header-plate: rgb(238 234 227 / 0.75);
  --header-height: 61px;

  /* --- Motion ----------------------------------------------------------- */
  --t-fast: 150ms;
  --t-base: 300ms;
}

/* ===== base.css ===== */
/* ==========================================================================
   AVELaunch Books — fonts, typography scale, grid, vertical lines, layout
   intent tags. Handoff sections 4, 5, 7, 15.
   ========================================================================== */

/* --- 15.1 Fonts. Served from our own domain, never a third party. -------- */
@font-face {
  font-family: "Mulish";
  font-style: normal;
  font-weight: 200 1000;
  font-display: swap;
  src: url("../fonts/mulish-latin-wght-normal.woff2") format("woff2-variations");
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193,
    U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
  font-family: "Mulish";
  font-style: normal;
  font-weight: 200 1000;
  font-display: swap;
  src: url("../fonts/mulish-latin-ext-wght-normal.woff2") format("woff2-variations");
  unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF,
    U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020,
    U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
  font-family: "Mulish";
  font-style: italic;
  font-weight: 200 1000;
  font-display: swap;
  src: url("../fonts/mulish-latin-wght-italic.woff2") format("woff2-variations");
  unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
    U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193,
    U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
  font-family: "Comforter";
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url("../fonts/comforter-latin-400-normal.woff2") format("woff2");
}

/* --- Reset -------------------------------------------------------------- */
*, *::before, *::after { box-sizing: border-box; }

html { -webkit-text-size-adjust: 100%; }

body {
  margin: 0;
  min-width: var(--layout-floor);
  background: var(--surface-page);
  color: var(--content-primary);
  font-family: "Mulish", "Helvetica Neue", Arial, sans-serif;
  font-weight: 400;
  font-size: 15px;
  line-height: normal;
  -webkit-font-smoothing: antialiased;
}

img, svg, video { display: block; max-width: 100%; }
img { height: auto; }

a { color: inherit; text-decoration: none; }

button, input, textarea, select {
  font: inherit;
  color: inherit;
  margin: 0;
}

h1, h2, h3, h4, p, figure, blockquote, dl, dd { margin: 0; }
ul, ol { margin: 0; padding: 0; list-style: none; }

/* 9. Keyboard focus is visible on every interactive element: white plate,
   3px accent stroke — the decision taken for the form fields, applied site
   wide because the component sets carry no separate focus variant.        */
:focus-visible {
  outline: 3px solid var(--border-accent);
  outline-offset: 2px;
  background-color: var(--editorial-white-2);
}

/* --- 7.3 Heading trim ---------------------------------------------------
   Headings in the file sit on the cap height, not on the line box. Without
   the trim every heading drops a few pixels and the spacing above it reads
   larger than the macket.                                                  */
.u-trim {
  text-box-trim: trim-both;
  text-box-edge: cap alphabetic;
}

/* --- 7.2 Type styles ----------------------------------------------------
   Letter spacing comes from Figma as a percentage of the type size, so it
   is written in em and never converted to pixels. Line height is Auto in
   every style, which is line-height: normal, not 100 %.                    */
.t-heading-accent       { font-family: "Comforter", cursive; font-weight: 400; font-size: 100px; letter-spacing: 0; text-transform: uppercase; }
.t-heading-accent-small { font-family: "Comforter", cursive; font-weight: 400; font-size: 100px; letter-spacing: 0; }
.t-heading              { font-weight: 1000; font-size: 50px; letter-spacing: 0.1em;  text-transform: uppercase; }
.t-heading-wide         { font-weight: 1000; font-size: 50px; letter-spacing: 0.06em; text-transform: uppercase; }
.t-heading-wide-light   { font-weight: 200;  font-size: 50px; letter-spacing: 0.06em; text-transform: uppercase; }
.t-subheading           { font-weight: 400;  font-size: 25px; letter-spacing: 0;      text-transform: uppercase; }
.t-intro                { font-weight: 400;  font-size: 25px; letter-spacing: 0; }
.t-intro-black          { font-weight: 1000; font-size: 25px; letter-spacing: 0;      text-transform: uppercase; }
.t-intro-black-wide     { font-weight: 1000; font-size: 25px; letter-spacing: 0.1em;  text-transform: uppercase; }
.t-base                 { font-weight: 400;  font-size: 15px; letter-spacing: 0; }
.t-base-black           { font-weight: 1000; font-size: 15px; letter-spacing: 0; }
.t-base-italic          { font-weight: 400;  font-size: 15px; font-style: italic; }
.t-base-down-black      { font-weight: 1000; font-size: 15px; text-transform: lowercase; }
.t-base-up              { font-weight: 400;  font-size: 15px; text-transform: uppercase; }
.t-base-up-black        { font-weight: 1000; font-size: 15px; text-transform: uppercase; }
.t-base-up-black-wide   { font-weight: 1000; font-size: 15px; letter-spacing: 0.1em;  text-transform: uppercase; }
.t-label                { font-weight: 400;  font-size: 25px; letter-spacing: 0.1em;  text-transform: uppercase; }
.t-label-wide           { font-weight: 400;  font-size: 25px; letter-spacing: 0.6em;  text-transform: uppercase; }
.t-label-big            { font-weight: 200;  font-size: 100px; text-transform: uppercase; }
.t-label-big-black      { font-weight: 1000; font-size: 100px; text-transform: uppercase; }

.u-secondary { color: var(--content-secondary); }
.u-accent    { color: var(--content-accent); }

/* --- 4.1 / 4.2 Working area ---------------------------------------------
   Above 1440 the working area holds at 1340 and centres; the margins grow.
   Between 1200 and 1440 the margin stays 50, the gutter stays 25, the
   columns narrow. Type sizes do not change.                               */
.container {
  width: min(var(--layout-content), 100% - var(--layout-margin) * 2);
  margin-inline: auto;
}

/* 12-column helper. The column width is derived from the grid, never set. */
.grid12 {
  display: grid;
  grid-template-columns: repeat(12, 1fr);
  gap: var(--layout-gutter);
}

/* --- 5.1 Intent tags ----------------------------------------------------
   Five values cover all thirty-nine hand-composed blocks. Where Auto Layout
   in the file disagrees with the tag, the tag wins.                        */

/* fluid — lives inside the working area and narrows with it. Default. */
.is-fluid { width: 100%; }

/* flow — a row of equal elements that wraps when it stops fitting.
   The gap equals the gutter. The count per row is not fixed.              */
.is-flow {
  display: flex;
  flex-wrap: wrap;
  gap: var(--layout-gutter);
}
.is-flow > * { flex: 1 1 var(--flow-basis, 430px); min-width: 0; }

/* bleed:both — runs the full window width both sides. Text and cards
   inside stay in the working area.                                        */
.is-bleed-both {
  width: 100vw;
  margin-left: calc(50% - 50vw);
}

/* bleed:left / bleed:right — out past one margin only, never both.
   --bleed-stop is the macket coordinate of the edge that stays put,
   expressed as a share of the working area.                               */
.is-bleed-left {
  margin-left: calc(50% - 50vw);
  margin-right: var(--bleed-stop, 0%);
}
.is-bleed-right {
  margin-right: calc(50% - 50vw);
  margin-left: var(--bleed-stop, 0%);
}

/* --- 4.1 Vertical lines -------------------------------------------------
   One component, two placements. Positions are read from --line-step in
   tokens.css and exist nowhere else, so the page layer and the header layer
   cannot drift apart.                                                      */
.gridlines {
  position: absolute;
  inset: 0;
  pointer-events: none;
  z-index: 0;
}
.gridlines i {
  position: absolute;
  top: 0;
  bottom: 0;
  width: var(--line-width);
  background: var(--line-color);
  left: calc(var(--n) * var(--line-step));
}

/* The page layer sits under every section, the full height of the document.
   The header is the one exception: it keeps its own sticky positioning and
   rides above, because it draws its own copy of the lines over its plate. */
/* Bleeding blocks are drawn past the window edge on purpose — an amber band
   that runs off the left, a roller whose next card is cut by the right. The
   page clips them at the window. `clip` and not `hidden`: hidden would make
   this a scroll container and the pinned header would stop pinning. */
.page {
  position: relative;
  overflow-x: clip;
}
.page > .gridlines { z-index: 0; }
.page > *:not(.gridlines):not(.site-header):not(.site-up) { position: relative; z-index: 1; }
.page > .site-header { z-index: 2; }

/* Skip link — visible only once it takes focus. */
.skip-link {
  position: absolute;
  left: var(--layout-margin);
  top: 0;
  z-index: 10;
  transform: translateY(-200%);
  padding: 12px 25px;
  background: var(--editorial-white-2);
  color: var(--content-primary);
  font-weight: 1000;
  font-size: 15px;
  text-transform: uppercase;
  transition: transform var(--t-fast);
}
.skip-link:focus-visible { transform: translateY(0); }

/* --- Vertical rhythm between the blocks ---------------------------------
   The file stacks the screen's blocks on a fixed rhythm, and it is defined
   here once rather than inside each section: a section owns its own height,
   never the air around it.

   Read off the Main screen (1:3): the header's box ends at 111 and the first
   block starts at 180; every neighbouring pair of blocks sits 150 apart; the
   footer sits 100 below the last one.

   150 is only the Main screen's number. Services runs 150 · 100 · 0, How It
   Works runs 100 below its halfway point, and the gap under the header is a
   different number on every screen. So the default lives here and a block
   that departs from it writes its own value once, in the markup, as
   `style="--gap: 100px"` on the <section> — the measured Figma number, next
   to the block it belongs to, still not a margin the section sets on itself.

   The FAQ on Main carries `--gap: 0`: its full-width blue fill is meant to
   start exactly where the founder block above it ends.                      */
:root {
  --block-gap: 150px;
  --block-gap-first: 69px;   /* header box 111 → first block 180 */
  --block-gap-footer: 100px;
}

main > section + section  { margin-top: var(--gap, var(--block-gap)); }
main > section:first-child { margin-top: var(--gap, var(--block-gap-first)); }
.page > .site-footer { margin-top: var(--gap-footer, var(--block-gap-footer)); }

/* --- 13.3 Anchors -------------------------------------------------------
   Smooth scroll that accounts for the pinned header, so the target block
   does not hide underneath it.                                            */
html { scroll-behavior: smooth; }
[id] { scroll-margin-top: calc(var(--header-height) + 50px); }

@media (prefers-reduced-motion: reduce) {
  html { scroll-behavior: auto; }
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}

/* --- Below the 1200 floor ------------------------------------------------
   The design stops at 1200: below that there is no narrower composition to
   fall back to, and `min-width` on its own gave a horizontal scrollbar — the
   headline cut off the left edge, half the hero off the right. A window at
   900 is not a phone; it is a laptop or a half-screen window, and a page you
   have to scroll sideways to read is broken in the only sense that matters.

   So the page keeps its 1200 layout and is scaled down to fit the window.
   Everything stays in proportion and simply reads smaller. This is not a
   narrow layout and it is no substitute for one — it is what the site does
   until a narrow composition is drawn.

   The scale itself cannot be written here: `zoom` needs a plain ratio, and
   no CSS expression turns a viewport width into one — dividing 100vw by 1200
   yields a length, which `zoom` rejects. So it is set by the small inline
   script the build puts at the top of every <body>, and `zoom` rather than
   `transform: scale()` because a transform would make the pinned header and
   the scroll-to-top control position against the transformed box instead of
   the window, and both would come unstuck.                                 */

/* An inline link inside body copy. The site has no underlines anywhere, so
   a link in the middle of a sentence has to be told apart some other way:
   it carries the accent colour and a 1px rule that thickens on hover. */
.u-link-inline {
  color: var(--content-accent);
  border-bottom: 1px solid currentColor;
  transition: border-bottom-width var(--t-fast), color var(--t-fast);
}
.u-link-inline:hover,
.u-link-inline:focus-visible {
  border-bottom-width: 3px;
}

/* ===== header.css ===== */
/* ==========================================================================
   Site header — Figma component set 504:2789, instance 20:1973 on Main.
   Load AFTER css/base.css.

   Full window width, 61px tall, pinned to the top of the window. Three
   layers, bottom to top:

     1. the plate  — Editorial White 4 at 75 % over a background blur
                     (Figma "Rectangle 13", 1440 x 61)
     2. the lines  — the page's own .gridlines component, drawn a second
                     time so the seven lines sit OVER the plate
     3. the logo and the menu

   Geometry: the seven lines and the seven menu cells are the same seven
   positions. They are read from --line-step in tokens.css and appear
   nowhere else, so the page's line layer and the header's cannot drift.
   ========================================================================== */

.site-header {
  position: sticky;
  top: 0;
  z-index: 10;
  height: var(--header-height);
  /* Starts one page margin down; the page's own lines show in that strip. */
  margin-top: var(--layout-margin);
}

/* base.css pins every child of .page with `position: relative` at a higher
   weight than a single class, so the sticky behaviour is restated here at
   matching specificity. Width stays `auto` — the header must measure the
   same box as .page, not 100vw, or the scrollbar would offset its lines by
   a few pixels against the page's. */
.page > .site-header {
  position: sticky;
  z-index: 10;
}

/* --- 1. The plate ------------------------------------------------------- */
.site-header__plate {
  position: absolute;
  inset: 0;
  z-index: 0;
  background: var(--header-plate);
  -webkit-backdrop-filter: blur(var(--header-blur));
  backdrop-filter: blur(var(--header-blur));
}

/* --- 2. The lines -------------------------------------------------------
   The only modifier the shared component needs: it is lifted above the
   plate. The page layer keeps z-index 0 and stays under the content, so
   what shows inside the header is this crisp set at full strength, never
   the page's set dimmed and blurred through the translucent plate.       */
.site-header__lines {
  z-index: 1;
}

/* --- 3. Logo ------------------------------------------------------------ */
.site-header__logo {
  position: absolute;
  z-index: 2;
  left: var(--layout-margin);
  top: 50%;
  transform: translateY(-50%);
}

/* 15px tall, the wordmark's own ratio gives the width (107.45 in the
   macket). Fixed to the window margin, not to a share of the width. */
.site-header__logo img {
  width: auto;
  height: 15px;
}

/* --- 3. Menu ------------------------------------------------------------
   Each cell's line is at --n * --line-step; the label sits one gutter to
   the right of it. The cell width (150 in the macket) is never needed —
   the next cell is placed from the next line, not from this one's edge.  */
.site-header__nav {
  position: absolute;
  inset: 0;
  z-index: 2;
  /* The nav box covers the whole header, including the logo. It is
     transparent but would still take the clicks, so it is made inert and
     only the menu items themselves are given back to the pointer. */
  pointer-events: none;
}

.site-header__item {
  position: absolute;
  top: 0;
  bottom: 0;
  display: flex;
  align-items: center;
  pointer-events: auto;
  left: calc(var(--n) * var(--line-step) + var(--layout-gutter));
}

.site-header__link {
  white-space: nowrap;
  transition: color var(--t-fast);
}

/* Active page. The five variants in the set carry no other difference at
   this height, so one rule covers Main, Services, Process, Results and
   About. Styled off the attribute so the markup cannot drift from it. */
.site-header__link[aria-current="page"],
.site-header__link:hover,
.site-header__link:focus-visible {
  color: var(--content-accent);
}

/* --- 4. The sub-navigation ----------------------------------------------
   Three of the five header variants in the set are 113 tall instead of 61:
   Services (966:7456), Results (521:2698) and About (521:3038). The extra
   52 is a second row of links that hangs under the item that owns it —
   All services / Discovery Sprint under Services, Author Stories / Free
   Resources under Results, Our Team & Story / FAQ / Contact under About.

   Each sub-item sits on the SAME seven positions as the bar above it, one
   gutter right of its line, and the group's plate covers only its own
   columns. The rest of the row is bare: the page shows through it, with
   the seven lines carried down across the full width (Figma "Group 75").

   The block is a child of the <li> that opens it, so :hover and
   :focus-within on that item are the entire interaction — no script, and
   the pointer can travel down into the row without losing the hover
   because it never leaves the <li>'s subtree.

   It is an OVERLAY, not flow: on Services the hero deliberately starts at
   110 and runs up behind the whole header. A page whose first block is
   meant to start below the open row writes that into its own --gap.     */
.site-header__sub {
  position: absolute;
  top: 100%;
  left: 0;
  right: 0;
  height: 52px;
  opacity: 0;
  visibility: hidden;
  transition: opacity var(--t-fast) ease, visibility var(--t-fast);
  /* The nav box above is inert so it cannot swallow clicks meant for the
     page; this row is its own box and takes its own. */
  pointer-events: auto;
}

/* The block is a sibling of the menu, not a child of the item that opens it:
   the item is itself absolutely positioned, so a descendant would be laid
   out against that one narrow cell instead of across the header. :has()
   carries the relationship instead.

   Three states, in this order, and the order is the whole logic:

     1. a page that belongs to a group holds that group's row open;
     2. the moment the pointer or the caret lands on ANY opening item, every
        row closes — otherwise the page's own row and the hovered one draw
        on top of each other in the same 52px strip, which is what the
        header did on all seven section pages;
     3. the row belonging to what is actually being pointed at opens.

   Step 3 also keeps the row open while the pointer is inside it, so
   travelling down from the label into the links does not close it. */

/* 1 — held open by the page */
.site-header[data-subnav="services"] .site-header__sub[data-group="services"],
.site-header[data-subnav="results"]  .site-header__sub[data-group="results"],
.site-header[data-subnav="about"]    .site-header__sub[data-group="about"] {
  opacity: 1;
  visibility: visible;
}

/* 2 — anything being pointed at or tabbed to closes all of them first */
.site-header:has(.site-header__link[data-opens]:hover) .site-header__sub,
.site-header:has(.site-header__link[data-opens]:focus-visible) .site-header__sub,
.site-header:has(.site-header__sub:hover) .site-header__sub,
.site-header:has(.site-header__sub:focus-within) .site-header__sub {
  opacity: 0;
  visibility: hidden;
}

/* 3 — and only the one being pointed at opens */
.site-header:has(.site-header__link[data-opens="services"]:hover) .site-header__sub[data-group="services"],
.site-header:has(.site-header__link[data-opens="services"]:focus-visible) .site-header__sub[data-group="services"],
.site-header:has(.site-header__sub[data-group="services"]:hover) .site-header__sub[data-group="services"],
.site-header:has(.site-header__sub[data-group="services"]:focus-within) .site-header__sub[data-group="services"],
.site-header:has(.site-header__link[data-opens="results"]:hover) .site-header__sub[data-group="results"],
.site-header:has(.site-header__link[data-opens="results"]:focus-visible) .site-header__sub[data-group="results"],
.site-header:has(.site-header__sub[data-group="results"]:hover) .site-header__sub[data-group="results"],
.site-header:has(.site-header__sub[data-group="results"]:focus-within) .site-header__sub[data-group="results"],
.site-header:has(.site-header__link[data-opens="about"]:hover) .site-header__sub[data-group="about"],
.site-header:has(.site-header__link[data-opens="about"]:focus-visible) .site-header__sub[data-group="about"],
.site-header:has(.site-header__sub[data-group="about"]:hover) .site-header__sub[data-group="about"],
.site-header:has(.site-header__sub[data-group="about"]:focus-within) .site-header__sub[data-group="about"] {
  opacity: 1;
  visibility: visible;
}

/* The group's own piece of the plate: from its first line to one past its
   last, so the blur ends on a line and not in the middle of a cell. */
.site-header__sub-plate {
  position: absolute;
  top: 0;
  bottom: 0;
  left: calc(var(--from) * var(--line-step));
  width: calc(var(--span) * var(--line-step) + var(--line-width));
  /* The file gives this the same Editorial White 4 at 75 % as the bar above
     it, but it only ever draws the header over the cream hero. On a live
     page the sticky header travels over the blue and amber bands, and there
     a 75 % plate that covers three columns and not the rest reads as a grey
     smear cut through the headline behind it — the bar gets away with it
     because it spans the full width, this row does not. So the row's own
     plate is opaque: the two links stay legible over anything, and the strip
     reads as a panel that belongs to the menu instead of a smudge. */
  background: var(--surface-page);
}

/* Figma "Line 39": 1px at y 62, i.e. the first pixel of this row, spanning
   exactly the group's columns. */
.site-header__sub-rule {
  position: absolute;
  top: 1px;
  height: var(--line-width);
  left: calc(var(--from) * var(--line-step));
  width: calc(var(--span) * var(--line-step) + var(--line-width));
  background: var(--line-color);
  z-index: 2;
}

/* The seven lines continue down through the whole row, group or not. */
.site-header__sub-lines { z-index: 1; }

.site-header__submenu {
  position: absolute;
  inset: 0;
  z-index: 3;
}

/* Macket: label baseline at y 76 within the 113 header, i.e. 15 into this
   row; same one-gutter offset from the line as the bar above. */
.site-header__subitem {
  position: absolute;
  top: 15px;
  left: calc(var(--n) * var(--line-step) + var(--layout-gutter));
  pointer-events: auto;
}

/* Sentence case, Base Regular — the one place on the site where a menu
   label is not set in capitals. */
.site-header__sublink {
  white-space: nowrap;
  transition: color var(--t-fast);
}

.site-header__sublink[aria-current="page"],
.site-header__sublink:hover,
.site-header__sublink:focus-visible {
  color: var(--content-accent);
}

/* ===== footer.css ===== */
/* ==========================================================================
   Site footer — Figma symbol 152:1464, instance 966:8527.
   Load AFTER css/base.css.

   Full window width, 415 tall in the macket, Vista Blue 1. The fill is
   opaque, so it covers the page's vertical line layer — the macket shows
   no lines inside the footer.

   Vertical rhythm, read off the macket (footer top = 0):

        50  logo, 15 tall
        83  hairline, full working area
        98  tagline          |  50   Company / Services / Contact headings
       134  social icons     |  98   first link of each column
       184  Barcelona office | 289   last link of the Services column
       339  hairline
       354  legal links and copyright
       415  foot

   The right-hand link block starts level with the logo, so the first
   hairline crosses it. That is why the two halves are one grid with fixed
   rows rather than two stacked blocks: the rules span both columns while
   the link block spans the rows above and below the first of them.
   ========================================================================== */

.site-footer {
  background: var(--vista-blue-1);
  padding-block: var(--layout-margin);
  min-height: 415px;
}

.site-footer__grid {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  /* logo band · hairline · body · hairline · bottom bar */
  grid-template-rows: 33px var(--line-width) 255px var(--line-width) auto;
}

/* --- Logo --------------------------------------------------------------- */
.site-footer__logo {
  grid-column: 1;
  grid-row: 1;
  justify-self: start;
}

.site-footer__logo img {
  width: auto;
  height: 15px;
}

/* --- Hairlines ---------------------------------------------------------- */
.site-footer__rule {
  grid-column: 1 / -1;
  margin: 0;
  border: 0;
  height: var(--line-width);
  background: var(--rich-black-1);
}
.site-footer__rule--top    { grid-row: 2; }
.site-footer__rule--bottom { grid-row: 4; }

/* --- Left half: tagline, socials, office -------------------------------- */
.site-footer__brand {
  grid-column: 1;
  grid-row: 3;
}

.site-footer__tagline { margin-top: 14px; }

.site-footer__social {
  display: flex;
  align-items: center;
  gap: var(--layout-gutter);
  margin-top: var(--layout-gutter);
}

.site-footer__office {
  display: block;
  font-style: normal;
  margin-top: var(--layout-gutter);
}
.site-footer__office span { display: block; }

/* --- Right half: three link columns -------------------------------------
   Spans from the logo band down past the first hairline, exactly as in the
   macket. 169 wide each, 50 apart — two gutters.                          */
.site-footer__nav {
  grid-column: 2;
  grid-row: 1 / 4;
  align-self: start;
  display: flex;
  gap: calc(var(--layout-gutter) * 2);
}

.site-footer__col {
  display: flex;
  flex-direction: column;
  gap: 30px;
  width: 169px;
}

.site-footer__list {
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
  align-items: start;
}

/* --- Bottom bar --------------------------------------------------------- */
.site-footer__bottom {
  grid-column: 1 / -1;
  grid-row: 5;
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: var(--layout-gutter);
  margin-top: 14px;
}

.site-footer__legal {
  display: flex;
  flex-wrap: wrap;
  gap: var(--layout-gutter);
}

.site-footer__copy {
  text-align: right;
  white-space: nowrap;
}

/* --- Links -------------------------------------------------------------- */
.site-footer a {
  transition: color var(--t-fast);
}
.site-footer a:hover,
.site-footer a:focus-visible {
  color: var(--content-accent);
}

/* --- The reduced footer — Figma `Footer_min` 917:7587, 1440 x 319 --------
   Used by the two paid-traffic landing pages. Same brand block, same legal
   row, same hairline; the three site-map columns are replaced by "Contact"
   and two ways to reach us, and the second hairline is gone.

   Measured from the symbol: logo 50,50 · rule y 83 · tagline y 98 · social
   y 134 · office y 184 · legal row and copyright y 258. With the 50 page
   padding those become a 33 logo band, the rule, a 160 body and the bottom
   bar — 319 in total.                                                     */
.site-footer--min {
  min-height: 319px;
}

.site-footer--min .site-footer__grid {
  /* logo band · hairline · body · bottom bar */
  grid-template-rows: 33px var(--line-width) 160px auto;
}

/* "Contact" sits on the logo's line, hard right. */
.site-footer--min .site-footer__contact {
  grid-column: 2;
  grid-row: 1;
  justify-self: end;
  align-self: start;
}

/* WhatsApp and the address share the tagline's line, right aligned. */
.site-footer--min .site-footer__reach {
  grid-column: 2;
  grid-row: 3;
  justify-self: end;
  align-self: start;
  display: flex;
  gap: 50px;
  margin-top: 14px;
}

.site-footer--min .site-footer__reach a {
  transition: color var(--t-fast);
}
.site-footer--min .site-footer__reach a:hover,
.site-footer--min .site-footer__reach a:focus-visible {
  color: var(--content-accent);
}

/* The bottom bar moves up one row, since there is no second hairline. */
.site-footer--min .site-footer__bottom {
  grid-row: 4;
}

/* ===== up.css ===== */
/* ==========================================================================
   Scroll-to-top control — `Button_form` 657:4075, macket 50,235 · 61 × 72.
   Load AFTER css/base.css.

   Fixed to the window at the page margin, at the same y the file draws it,
   so it sits in the empty strip left of the first vertical line and clear of
   the header. The label is set on its side reading bottom to top, which is
   what makes the box taller than it is wide.
   ========================================================================== */

.site-up {
  position: fixed;
  left: var(--layout-margin);
  /* The file draws this at y 235 — a static position on a page that does not
     scroll. As a floating control at the same coordinate it sits on top of
     whatever band happens to be passing: the Services list on the homepage
     runs its blue fill from the page margin, and the button covered the first
     row's line. So it keeps the file's x and moves to the foot of the window,
     out of the reading column and where a back-to-top control is looked for. */
  bottom: var(--layout-margin);
  z-index: 11;                      /* over the header's 10 */
  display: inline-flex;
  align-items: center;
  justify-content: center;
  padding: 25px;
  border: 0;
  background: var(--action-fill);
  color: var(--content-on-accent);
  box-shadow: inset 0 0 0 3px var(--action-fill);
  cursor: pointer;
  opacity: 0;
  transition: opacity var(--t-base) ease,
              background-color var(--t-fast) ease,
              box-shadow var(--t-fast) ease;
}

/* `hidden` is removed by the script; `data-shown` is what fades it in, so
   the control is never a dead button and never a flash on load. */
.site-up[data-shown] { opacity: 1; }

.site-up__label {
  writing-mode: vertical-rl;
  transform: rotate(180deg);        /* reads bottom to top, as in the file */
  white-space: nowrap;
}

/* pas → hov on Button_form: the fill empties, the amber stroke stays, and
   the box does not change size because the stroke is drawn inside. */
.site-up:hover,
.site-up:focus-visible {
  background: var(--action-fill-hover);
  box-shadow: inset 0 0 0 3px var(--action-border-hover);
}

/* ===== faq/f1.css ===== */
/* ==========================================================================
   FAQ — block 1, the page opening and its jump row
   Figma: node 657:3581 "Section 1", 1112 x 407, macket x 164.
   1112 is ten columns with their gutters, so the block is 2 / span 10 and
   sits one column in from each side of the working area.

   215 (Frame 167) + 125 + 67 (Frame 168) = 407.
   ========================================================================== */

.s-f1 .s-f1__inner {
  grid-column: 2 / span 10;
  display: flex;
  flex-direction: column;
  gap: 125px;
}

/* --- Heading ------------------------------------------------------------
   85 heading group + 50 + 80 lede = 215. The lede is pulled to the right of
   the block, 543 wide, which is what `items-end` does in the file.        */
.s-f1 .s-f1__intro {
  display: flex;
  flex-direction: column;
  align-items: flex-end;
  gap: 50px;
}

/* The Comforter word lies over the Mulish heading in one grid cell. The
   heading sits 50 down inside the 85-tall group; the accent starts at 0.  */
.s-f1 .s-f1__title {
  display: grid;
  width: 100%;
  font: inherit;
}
.s-f1 .s-f1__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f1 .s-f1__title-main {
  margin-top: 50px;
}
.s-f1 .s-f1__title-accent {
  color: var(--amber-4);
}

.s-f1 .s-f1__lede {
  width: 100%;
  max-width: 543px;
}

/* --- Jump row -----------------------------------------------------------
   Frame 168: 894 x 67 centred in the 1112 block — a 3px Rich black 1 stroke
   with 25 of padding, five Button_text labels spread across it. 67 is
   3 + 25 + cap height 11 + 25 + 3.

   It narrows with the working area rather than wrapping: five labels on one
   rule is the whole point of the device, and 894 still fits at 1200.      */
.s-f1 .s-f1__jump {
  align-self: center;
  width: 100%;
  max-width: 894px;
}
.s-f1 .s-f1__jump-list {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  padding: 25px;
  border: 3px solid var(--border-strong);
}
.s-f1 .s-f1__jump-link {
  display: block;
  white-space: nowrap;
  transition: color var(--t-fast);
}
.s-f1 .s-f1__jump-link:hover,
.s-f1 .s-f1__jump-link:focus-visible {
  color: var(--content-accent);
}

/* ===== faq/f2.css ===== */
/* ==========================================================================
   FAQ — block 2, "The Process"
   Figma: node 657:3909 "Section 2", 917 tall.
   Card component: FAQ_S2_Card, component set 657:3677, whose variants keep
   the homepage's names — `Home_S13_Card_1..n` x `Pas` / `Act`. Every answer
   below is lifted from an `Act` variant; the `Pas` variants carry the question
   only.

   The row geometry is Main's section 13 exactly — 61 collapsed, 25 between
   rows, 25 / 25 / 25 / 50 of trigger padding and a 607 answer column inset 50
   from the left with 228 left empty on the right — so the rules below are
   s13's, renamed. See the report: this is the fifth copy of one accordion and
   it wants a shared partial.

   1112 is ten columns with their gutters (2 / span 10); the 885 list is eight
   (3 / span 8), which centres it inside the heading.
   76 heading + 50 + 491 list = 617.
   ========================================================================== */

/* Full-window Rich black 3 band. 150 top and bottom, as the frame draws it.
   NOT Vista Blue 1: the three banded blocks on this screen are not one
   colour. Sampled off the rendered frame — blocks 2 and 5 are #C7D2E3
   (Rich black 3) and block 4 is #7C9EC7 (Vista Blue 1). Blocks 4 and 5 sit
   flush against each other, which is why block 5 carries `--gap: 0`. */
.s-f2 {
  background: var(--rich-black-3);
  padding-block: 150px;
}

/* The 50 between the heading and the list is the grid's own row gap, not a
   margin on the list: .grid12 already puts 25 between rows, and a margin on
   top of it would silently make the block 25 taller. */
.s-f2 .s-f2__grid {
  row-gap: 50px;
}

.s-f2 .s-f2__title {
  grid-column: 2 / span 10;
  display: grid;
  width: 100%;
  text-align: center;
  font: inherit;
}
.s-f2 .s-f2__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f2 .s-f2__title-accent {
  color: var(--amber-4);
}
/* The heading sits 41 down inside the 76-tall group on this screen — not the
   50 of a Main heading. Measured off 657:3908. */
.s-f2 .s-f2__title-main {
  margin-top: 41px;
}

/* --- Rows ---------------------------------------------------------------
   Collapsed row is 61: 25 + cap height 11 + 25. Gap between rows 25.       */
.s-f2 .s-f2__list {
  grid-column: 3 / span 8;
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f2 .s-f2__item {
  background: var(--editorial-white-4);
}
.s-f2 .s-f2__question {
  font: inherit;
}
.s-f2 .s-f2__trigger {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  width: 100%;
  padding: 25px 25px 25px 50px;
  border: 0;
  background: none;
  text-align: left;
  cursor: pointer;
}
.s-f2 .s-f2__label {
  color: var(--content-primary);
}

/* The chevron is Main_S11_Arrows: a 45-degree rule, 21.213 x 10.607. The file
   the homepage already ships, reused rather than re-exported.              */
.s-f2 .s-f2__chevron {
  flex: 0 0 auto;
  width: 21.213px;
  height: 10.607px;
  transition: transform var(--t-base) ease;
}
.s-f2 .s-f2__item.is-open .s-f2__chevron {
  transform: rotate(180deg);
}

/* --- Panel --------------------------------------------------------------
   Animated on grid-template-rows so the real content height is measured
   instead of guessed with a max-height. visibility keeps the collapsed
   answer out of the accessibility tree once the transition has finished.  */
.s-f2 .s-f2__panel {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows var(--t-base) ease;
}
.s-f2 .s-f2__panel-inner {
  overflow: hidden;
  visibility: hidden;
  transition: visibility 0s linear var(--t-base);
}
.s-f2 .s-f2__item.is-open .s-f2__panel {
  grid-template-rows: 1fr;
}
.s-f2 .s-f2__item.is-open .s-f2__panel-inner {
  visibility: visible;
  transition-delay: 0s;
}

/* Open row: 25 + question + 50 + answer + 50. 25 of the 50 between question
   and answer is the trigger's own bottom padding, which is what keeps the
   collapsed row at 61; the other 25 is here. The answer column is 607 wide —
   228 stays empty on the right, as the Act variants draw it.              */
.s-f2 .s-f2__answer {
  padding: 25px 228px 50px 50px;
  color: var(--content-primary);
}

/* ===== faq/f3.css ===== */
/* ==========================================================================
   FAQ — block 3, "Time & Involvement"
   Figma: node 657:4035 "Section 3", 445 tall.
   Card component: FAQ_S3_Card, component set 657:3914, whose variants keep
   the homepage's names — `Home_S13_Card_1..n` x `Pas` / `Act`. Every answer
   below is lifted from an `Act` variant; the `Pas` variants carry the question
   only.

   The row geometry is Main's section 13 exactly — 61 collapsed, 25 between
   rows, 25 / 25 / 25 / 50 of trigger padding and a 607 answer column inset 50
   from the left with 228 left empty on the right — so the rules below are
   s13's, renamed. See the report: this is the fifth copy of one accordion and
   it wants a shared partial.

   1112 is ten columns with their gutters (2 / span 10); the 885 list is eight
   (3 / span 8), which centres it inside the heading.
   76 heading + 50 + 319 list = 445.
   ========================================================================== */

/* No fill: the page background shows through, so the rows carry Rich black 3
   instead of Editorial white 4. That is the ONLY difference between this
   block and the banded ones. */

/* The 50 between the heading and the list is the grid's own row gap, not a
   margin on the list: .grid12 already puts 25 between rows, and a margin on
   top of it would silently make the block 25 taller. */
.s-f3 .s-f3__grid {
  row-gap: 50px;
}

.s-f3 .s-f3__title {
  grid-column: 2 / span 10;
  display: grid;
  width: 100%;
  text-align: center;
  font: inherit;
}
.s-f3 .s-f3__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f3 .s-f3__title-accent {
  color: var(--amber-4);
}
/* The heading sits 41 down inside the 76-tall group on this screen — not the
   50 of a Main heading. Measured off 657:4035. */
.s-f3 .s-f3__title-main {
  margin-top: 41px;
}

/* --- Rows ---------------------------------------------------------------
   Collapsed row is 61: 25 + cap height 11 + 25. Gap between rows 25.       */
.s-f3 .s-f3__list {
  grid-column: 3 / span 8;
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f3 .s-f3__item {
  background: var(--rich-black-3);
}
.s-f3 .s-f3__question {
  font: inherit;
}
.s-f3 .s-f3__trigger {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  width: 100%;
  padding: 25px 25px 25px 50px;
  border: 0;
  background: none;
  text-align: left;
  cursor: pointer;
}
.s-f3 .s-f3__label {
  color: var(--content-primary);
}

/* The chevron is Main_S11_Arrows: a 45-degree rule, 21.213 x 10.607. The file
   the homepage already ships, reused rather than re-exported.              */
.s-f3 .s-f3__chevron {
  flex: 0 0 auto;
  width: 21.213px;
  height: 10.607px;
  transition: transform var(--t-base) ease;
}
.s-f3 .s-f3__item.is-open .s-f3__chevron {
  transform: rotate(180deg);
}

/* --- Panel --------------------------------------------------------------
   Animated on grid-template-rows so the real content height is measured
   instead of guessed with a max-height. visibility keeps the collapsed
   answer out of the accessibility tree once the transition has finished.  */
.s-f3 .s-f3__panel {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows var(--t-base) ease;
}
.s-f3 .s-f3__panel-inner {
  overflow: hidden;
  visibility: hidden;
  transition: visibility 0s linear var(--t-base);
}
.s-f3 .s-f3__item.is-open .s-f3__panel {
  grid-template-rows: 1fr;
}
.s-f3 .s-f3__item.is-open .s-f3__panel-inner {
  visibility: visible;
  transition-delay: 0s;
}

/* Open row: 25 + question + 50 + answer + 50. 25 of the 50 between question
   and answer is the trigger's own bottom padding, which is what keeps the
   collapsed row at 61; the other 25 is here. The answer column is 607 wide —
   228 stays empty on the right, as the Act variants draw it.              */
.s-f3 .s-f3__answer {
  padding: 25px 228px 50px 50px;
  color: var(--content-primary);
}

/* ===== faq/f4.css ===== */
/* ==========================================================================
   FAQ — block 4, "Pricing details"
   Figma: node 657:4247 "Section 4", 831 tall.
   Card component: FAQ_S4_Card, component set 657:4100, whose variants keep
   the homepage's names — `Home_S13_Card_1..n` x `Pas` / `Act`. Every answer
   below is lifted from an `Act` variant; the `Pas` variants carry the question
   only.

   The row geometry is Main's section 13 exactly — 61 collapsed, 25 between
   rows, 25 / 25 / 25 / 50 of trigger padding and a 607 answer column inset 50
   from the left with 228 left empty on the right — so the rules below are
   s13's, renamed. See the report: this is the fifth copy of one accordion and
   it wants a shared partial.

   1112 is ten columns with their gutters (2 / span 10); the 885 list is eight
   (3 / span 8), which centres it inside the heading.
   76 heading + 50 + 405 list = 531.
   ========================================================================== */

/* Full-window Vista Blue 1 band. 150 top and bottom, as the frame draws it. */
.s-f4 {
  background: var(--vista-blue-1);
  padding-block: 150px;
}

/* The 50 between the heading and the list is the grid's own row gap, not a
   margin on the list: .grid12 already puts 25 between rows, and a margin on
   top of it would silently make the block 25 taller. */
.s-f4 .s-f4__grid {
  row-gap: 50px;
}

.s-f4 .s-f4__title {
  grid-column: 2 / span 10;
  display: grid;
  width: 100%;
  text-align: center;
  font: inherit;
}
.s-f4 .s-f4__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f4 .s-f4__title-accent {
  color: var(--amber-4);
}
/* The heading sits 41 down inside the 76-tall group on this screen — not the
   50 of a Main heading. Measured off 657:4246. */
.s-f4 .s-f4__title-main {
  margin-top: 41px;
}

/* --- Rows ---------------------------------------------------------------
   Collapsed row is 61: 25 + cap height 11 + 25. Gap between rows 25.       */
.s-f4 .s-f4__list {
  grid-column: 3 / span 8;
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f4 .s-f4__item {
  background: var(--editorial-white-4);
}
.s-f4 .s-f4__question {
  font: inherit;
}
.s-f4 .s-f4__trigger {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  width: 100%;
  padding: 25px 25px 25px 50px;
  border: 0;
  background: none;
  text-align: left;
  cursor: pointer;
}
.s-f4 .s-f4__label {
  color: var(--content-primary);
}

/* The chevron is Main_S11_Arrows: a 45-degree rule, 21.213 x 10.607. The file
   the homepage already ships, reused rather than re-exported.              */
.s-f4 .s-f4__chevron {
  flex: 0 0 auto;
  width: 21.213px;
  height: 10.607px;
  transition: transform var(--t-base) ease;
}
.s-f4 .s-f4__item.is-open .s-f4__chevron {
  transform: rotate(180deg);
}

/* --- Panel --------------------------------------------------------------
   Animated on grid-template-rows so the real content height is measured
   instead of guessed with a max-height. visibility keeps the collapsed
   answer out of the accessibility tree once the transition has finished.  */
.s-f4 .s-f4__panel {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows var(--t-base) ease;
}
.s-f4 .s-f4__panel-inner {
  overflow: hidden;
  visibility: hidden;
  transition: visibility 0s linear var(--t-base);
}
.s-f4 .s-f4__item.is-open .s-f4__panel {
  grid-template-rows: 1fr;
}
.s-f4 .s-f4__item.is-open .s-f4__panel-inner {
  visibility: visible;
  transition-delay: 0s;
}

/* Open row: 25 + question + 50 + answer + 50. 25 of the 50 between question
   and answer is the trigger's own bottom padding, which is what keeps the
   collapsed row at 61; the other 25 is here. The answer column is 607 wide —
   228 stays empty on the right, as the Act variants draw it.              */
.s-f4 .s-f4__answer {
  padding: 25px 228px 50px 50px;
  color: var(--content-primary);
}

/* ===== faq/f5.css ===== */
/* ==========================================================================
   FAQ — block 5, "Rights & Confidentiality"
   Figma: node 657:4451 "Section 5", 745 tall.
   Card component: FAQ_S5_Card, component set 657:4329, whose variants keep
   the homepage's names — `Home_S13_Card_1..n` x `Pas` / `Act`. Every answer
   below is lifted from an `Act` variant; the `Pas` variants carry the question
   only.

   The row geometry is Main's section 13 exactly — 61 collapsed, 25 between
   rows, 25 / 25 / 25 / 50 of trigger padding and a 607 answer column inset 50
   from the left with 228 left empty on the right — so the rules below are
   s13's, renamed. See the report: this is the fifth copy of one accordion and
   it wants a shared partial.

   1112 is ten columns with their gutters (2 / span 10); the 885 list is eight
   (3 / span 8), which centres it inside the heading.
   76 heading + 50 + 319 list = 445.
   ========================================================================== */

/* Full-window Rich black 3 band. 150 top and bottom, as the frame draws it.
   NOT Vista Blue 1: the three banded blocks on this screen are not one
   colour. Sampled off the rendered frame — blocks 2 and 5 are #C7D2E3
   (Rich black 3) and block 4 is #7C9EC7 (Vista Blue 1). Blocks 4 and 5 sit
   flush against each other, which is why block 5 carries `--gap: 0`. */
.s-f5 {
  background: var(--rich-black-3);
  padding-block: 150px;
}

/* The 50 between the heading and the list is the grid's own row gap, not a
   margin on the list: .grid12 already puts 25 between rows, and a margin on
   top of it would silently make the block 25 taller. */
.s-f5 .s-f5__grid {
  row-gap: 50px;
}

.s-f5 .s-f5__title {
  grid-column: 2 / span 10;
  display: grid;
  width: 100%;
  text-align: center;
  font: inherit;
}
.s-f5 .s-f5__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f5 .s-f5__title-accent {
  color: var(--amber-4);
}
/* The heading sits 41 down inside the 76-tall group on this screen — not the
   50 of a Main heading. Measured off 657:4450. */
.s-f5 .s-f5__title-main {
  margin-top: 41px;
}

/* --- Rows ---------------------------------------------------------------
   Collapsed row is 61: 25 + cap height 11 + 25. Gap between rows 25.       */
.s-f5 .s-f5__list {
  grid-column: 3 / span 8;
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f5 .s-f5__item {
  background: var(--editorial-white-4);
}
.s-f5 .s-f5__question {
  font: inherit;
}
.s-f5 .s-f5__trigger {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  width: 100%;
  padding: 25px 25px 25px 50px;
  border: 0;
  background: none;
  text-align: left;
  cursor: pointer;
}
.s-f5 .s-f5__label {
  color: var(--content-primary);
}

/* The chevron is Main_S11_Arrows: a 45-degree rule, 21.213 x 10.607. The file
   the homepage already ships, reused rather than re-exported.              */
.s-f5 .s-f5__chevron {
  flex: 0 0 auto;
  width: 21.213px;
  height: 10.607px;
  transition: transform var(--t-base) ease;
}
.s-f5 .s-f5__item.is-open .s-f5__chevron {
  transform: rotate(180deg);
}

/* --- Panel --------------------------------------------------------------
   Animated on grid-template-rows so the real content height is measured
   instead of guessed with a max-height. visibility keeps the collapsed
   answer out of the accessibility tree once the transition has finished.  */
.s-f5 .s-f5__panel {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows var(--t-base) ease;
}
.s-f5 .s-f5__panel-inner {
  overflow: hidden;
  visibility: hidden;
  transition: visibility 0s linear var(--t-base);
}
.s-f5 .s-f5__item.is-open .s-f5__panel {
  grid-template-rows: 1fr;
}
.s-f5 .s-f5__item.is-open .s-f5__panel-inner {
  visibility: visible;
  transition-delay: 0s;
}

/* Open row: 25 + question + 50 + answer + 50. 25 of the 50 between question
   and answer is the trigger's own bottom padding, which is what keeps the
   collapsed row at 61; the other 25 is here. The answer column is 607 wide —
   228 stays empty on the right, as the Act variants draw it.              */
.s-f5 .s-f5__answer {
  padding: 25px 228px 50px 50px;
  color: var(--content-primary);
}

/* ===== faq/f6.css ===== */
/* ==========================================================================
   FAQ — block 6, "After Launch"
   Figma: node 657:4621 "Section 6", 531 tall.
   Card component: FAQ_S6_Card, component set 657:4452, whose variants keep
   the homepage's names — `Home_S13_Card_1..n` x `Pas` / `Act`. Every answer
   below is lifted from an `Act` variant; the `Pas` variants carry the question
   only.

   The row geometry is Main's section 13 exactly — 61 collapsed, 25 between
   rows, 25 / 25 / 25 / 50 of trigger padding and a 607 answer column inset 50
   from the left with 228 left empty on the right — so the rules below are
   s13's, renamed. See the report: this is the fifth copy of one accordion and
   it wants a shared partial.

   1112 is ten columns with their gutters (2 / span 10); the 885 list is eight
   (3 / span 8), which centres it inside the heading.
   76 heading + 50 + 405 list = 531.
   ========================================================================== */

/* No fill: the page background shows through, so the rows carry Rich black 3
   instead of Editorial white 4. That is the ONLY difference between this
   block and the banded ones. */

/* The 50 between the heading and the list is the grid's own row gap, not a
   margin on the list: .grid12 already puts 25 between rows, and a margin on
   top of it would silently make the block 25 taller. */
.s-f6 .s-f6__grid {
  row-gap: 50px;
}

.s-f6 .s-f6__title {
  grid-column: 2 / span 10;
  display: grid;
  width: 100%;
  text-align: center;
  font: inherit;
}
.s-f6 .s-f6__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f6 .s-f6__title-accent {
  color: var(--amber-4);
}
/* The heading sits 41 down inside the 76-tall group on this screen — not the
   50 of a Main heading. Measured off 657:4621. */
.s-f6 .s-f6__title-main {
  margin-top: 41px;
}

/* --- Rows ---------------------------------------------------------------
   Collapsed row is 61: 25 + cap height 11 + 25. Gap between rows 25.       */
.s-f6 .s-f6__list {
  grid-column: 3 / span 8;
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f6 .s-f6__item {
  background: var(--rich-black-3);
}
.s-f6 .s-f6__question {
  font: inherit;
}
.s-f6 .s-f6__trigger {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
  width: 100%;
  padding: 25px 25px 25px 50px;
  border: 0;
  background: none;
  text-align: left;
  cursor: pointer;
}
.s-f6 .s-f6__label {
  color: var(--content-primary);
}

/* The chevron is Main_S11_Arrows: a 45-degree rule, 21.213 x 10.607. The file
   the homepage already ships, reused rather than re-exported.              */
.s-f6 .s-f6__chevron {
  flex: 0 0 auto;
  width: 21.213px;
  height: 10.607px;
  transition: transform var(--t-base) ease;
}
.s-f6 .s-f6__item.is-open .s-f6__chevron {
  transform: rotate(180deg);
}

/* --- Panel --------------------------------------------------------------
   Animated on grid-template-rows so the real content height is measured
   instead of guessed with a max-height. visibility keeps the collapsed
   answer out of the accessibility tree once the transition has finished.  */
.s-f6 .s-f6__panel {
  display: grid;
  grid-template-rows: 0fr;
  transition: grid-template-rows var(--t-base) ease;
}
.s-f6 .s-f6__panel-inner {
  overflow: hidden;
  visibility: hidden;
  transition: visibility 0s linear var(--t-base);
}
.s-f6 .s-f6__item.is-open .s-f6__panel {
  grid-template-rows: 1fr;
}
.s-f6 .s-f6__item.is-open .s-f6__panel-inner {
  visibility: visible;
  transition-delay: 0s;
}

/* Open row: 25 + question + 50 + answer + 50. 25 of the 50 between question
   and answer is the trigger's own bottom padding, which is what keeps the
   collapsed row at 61; the other 25 is here. The answer column is 607 wide —
   228 stays empty on the right, as the Act variants draw it.              */
.s-f6 .s-f6__answer {
  padding: 25px 228px 50px 50px;
  color: var(--content-primary);
}

/* ===== faq/f7.css ===== */
/* ==========================================================================
   FAQ — block 7, "ways to start" and the contact form
   Figma: node 663:4800 "Section 7", 1340 x 661 — the whole working area,
   split six and six: the text column 658 at x 0, the form 657 at x 683.
   Form component: FAQ_S7_Form, instance 663:4810.

   FAQ_S7_Form is Main_S14_Form (Main's section 15) with ONE addition — a
   second, outlined WhatsApp button beside "Send it" — and one copy change:
   the message placeholder reads "Type your message", not "Tell us about your
   book idea". Everything else, down to the 607 inner column and the 44 above
   the status line, is identical. The rules below are s15's, renamed. See the
   report: this form now exists three times and wants a shared partial.

   50 + 506 + 44 + 11 + 50 = 661.
   ========================================================================== */

.s-f7 .s-f7__intro {
  grid-column: 1 / span 6;
  align-self: start;
  display: flex;
  flex-direction: column;
  gap: 75px;
}
.s-f7 .s-f7__form {
  grid-column: 7 / span 6;
}

/* --- Left column --------------------------------------------------------
   85 heading group + 25 + 80 lede = 190, then 75, then the 61 button row. */
.s-f7 .s-f7__head {
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f7 .s-f7__title {
  display: grid;
  width: 100%;
  font: inherit;
}
.s-f7 .s-f7__title > * {
  grid-area: 1 / 1;
  width: 100%;
}
.s-f7 .s-f7__title-main {
  margin-top: 50px;
}
.s-f7 .s-f7__title-accent {
  color: var(--amber-4);
}

.s-f7 .s-f7__actions {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--layout-gutter);
}

/* Button_form, two variants: filled and outlined. Both 61 tall — 25 + cap
   height 11 + 25 — and as wide as their label plus the padding.           */
.s-f7 .s-f7__cta {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  padding: 25px;
  white-space: nowrap;
  color: var(--content-on-accent);
  cursor: pointer;
  transition: background-color var(--t-base), box-shadow var(--t-base);
}
.s-f7 .s-f7__cta--fill {
  background: var(--action-fill);
  box-shadow: inset 0 0 0 3px var(--action-fill);
}
.s-f7 .s-f7__cta--line {
  background: none;
  box-shadow: inset 0 0 0 3px var(--border-strong);
  color: var(--content-primary);
}
.s-f7 .s-f7__cta--fill:hover,
.s-f7 .s-f7__cta--fill:focus-visible {
  background: var(--action-fill-hover);
  box-shadow: inset 0 0 0 3px var(--action-border-hover);
}
.s-f7 .s-f7__cta--line:hover,
.s-f7 .s-f7__cta--line:focus-visible {
  box-shadow: inset 0 0 0 3px var(--action-border-hover);
  color: var(--content-accent);
}

/* --- Form ---------------------------------------------------------------
   50 + 420 fields + 25 + 61 buttons + 44 + 11 status + 50 = 661.          */
.s-f7 .s-f7__form {
  display: flex;
  flex-direction: column;
  padding: 50px 25px;
  background: var(--vista-blue-1);
}
.s-f7 .s-f7__body {
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f7 .s-f7__fields {
  display: flex;
  flex-direction: column;
  gap: var(--layout-gutter);
}
.s-f7 .s-f7__field {
  display: flex;
  flex-direction: column;
  gap: 10px;
}
.s-f7 .s-f7__label {
  color: var(--content-on-brand);
}

/* --- Plates -------------------------------------------------------------
   Main_S14_Form_text_card: Editorial White 4 plate, no border at rest,
   15 of padding all round — 15 + cap height 11 + 15 = 41 for a one-liner. */
.s-f7 .s-f7__plate {
  width: 100%;
  border: 0;
  background: var(--editorial-white-4);
  color: var(--content-primary);
}
.s-f7 .s-f7__input {
  height: 41px;
  padding: 0 15px;
}
.s-f7 .s-f7__textarea {
  height: 225px;
  padding: 15px;
  resize: vertical;
}
.s-f7 .s-f7__plate::placeholder {
  color: var(--vista-blue-1);
  opacity: 1;
}
/* The Act variants draw the focus stroke on the plate edge rather than 2
   outside it, so the offset base.css sets site wide is dropped here.      */
.s-f7 .s-f7__plate:focus-visible {
  outline-offset: 0;
  background-color: var(--editorial-white-2);
}

/* --- The two buttons ----------------------------------------------------
   The row is 607 wide with the pair pushed to its ends, which is how
   FAQ_S7_Form draws it. This is the one thing Main's form does not have.  */
.s-f7 .s-f7__actions-row {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: space-between;
  gap: var(--layout-gutter);
}
.s-f7 .s-f7__submit,
.s-f7 .s-f7__whatsapp {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  padding: 25px;
  border: 0;
  cursor: pointer;
  transition: background-color var(--t-fast) ease, box-shadow var(--t-fast) ease;
}
.s-f7 .s-f7__submit {
  background: var(--action-fill);
  color: var(--content-on-accent);
}
.s-f7 .s-f7__whatsapp {
  background: none;
  box-shadow: inset 0 0 0 3px var(--border-strong);
  color: var(--content-on-brand);
}
/* The label is trimmed to its cap height, so 25 + 11 + 25 gives the 61 of
   the macket. It carries the trim rather than the button, because only a
   flex item is a block container of its own text.                        */
.s-f7 .s-f7__submit-label,
.s-f7 .s-f7__whatsapp-label {
  white-space: nowrap;
}
.s-f7 .s-f7__submit:hover:not([disabled]) {
  background: var(--action-fill-hover);
  box-shadow: inset 0 0 0 3px var(--action-border-hover);
}
.s-f7 .s-f7__whatsapp:hover,
.s-f7 .s-f7__whatsapp:focus-visible {
  box-shadow: inset 0 0 0 3px var(--action-border-hover);
  color: var(--content-accent);
}
/* The Loading variant leaves the button looking exactly as it does at rest,
   so nothing is restyled here — it is only made unusable.                 */
.s-f7 .s-f7__submit[disabled] {
  cursor: progress;
}

/* --- Status line --------------------------------------------------------
   25 of the 44 between the button row and the status line comes from the
   form's own gap, the remaining 19 from here.                             */
.s-f7 .s-f7__status {
  display: flex;
  align-items: flex-start;
  justify-content: space-between;
  gap: var(--layout-gutter);
  margin-top: 44px;
  color: var(--content-on-brand);
}
.s-f7 .s-f7__message {
  text-align: right;
}
.s-f7 .s-f7__hint[hidden],
.s-f7 .s-f7__state[hidden],
.s-f7 .s-f7__message[hidden] {
  display: none;
}