/* =============================================================================
   Direction C · Group house style, teal
   Same skeleton and layout as Direction B (the cork-co.com / corkwills.com system),
   restyled so red appears ONLY in the logo: teal buttons with navy text, navy/teal
   heading rules, navy text instead of black, navy footer (as corkwills), and a
   stronger left-weighted hero overlay so the white headline always passes AA.
   ============================================================================= */


:root {
  --navy:    #1D3557;
  --teal:    #A8DADC;
  --neutral: #F1FAEE;
  --grey:    #EEF1F5;   /* a tint of navy. Was #F3F4F6, a Tailwind grey carried
                           over from corkwills and not in the brand palette;
                           guidelines p.8 allow tints of the brand colours. */
  --ink:     #1D3557;   /* navy text: calmer than the sister sites' black */
  --muted:   #4A5D79;   /* navy tint, 6.6:1 on white */

  /* roles */
  --accent:          var(--teal);   /* heading rules on dark; see overrides for light */
  --btn-primary-bg:  var(--teal);
  --btn-primary-ink: var(--navy);  /* navy on teal = 8.1:1 */
  --btn-primary-hov: #8FCFD2;
  --btn-secondary-bg:  var(--navy);
  --btn-secondary-ink: #FFFFFF;
  --btn-secondary-hov: #28466F;
  --footer-bg:   var(--navy);
  --watermark:   rgba(29, 53, 87, .06);
  --watermark-dark: rgba(255, 255, 255, .05);
  --hero-overlay: linear-gradient(90deg, rgba(29,53,87,.88) 0%, rgba(29,53,87,.8) 50%, rgba(29,53,87,.38) 100%);
  --card-overlay: rgba(29, 53, 87, .72);
  --focus: #457B9D;

  /* The *-Fallback families are declared in fonts.css with the webfont's own
     vertical metrics, so a page that renders in the fallback has the same line
     boxes as one that does not. The generic names stay behind them. */
  --f-head: "Cormorant Garamond", "Cormorant Fallback", Georgia, "Times New Roman", serif;
  --f-body: "Roboto", "Roboto Fallback", system-ui, -apple-system, "Segoe UI", Arial, sans-serif;
  --container: 77.5rem;
  --pad: clamp(1.25rem, 4vw, 2.5rem);
}

*, *::before, *::after { box-sizing: border-box; }
html { -webkit-text-size-adjust: 100%; scroll-behavior: smooth; }
@media (prefers-reduced-motion: reduce) { html { scroll-behavior: auto; } * { transition: none !important; } }
body { margin: 0; font: 400 1rem/1.6 var(--f-body); color: var(--ink); background: #fff; }
img { max-width: 100%; height: auto; display: block; }
a { color: inherit; }
h1, h2, h3 { font-family: var(--f-head); font-weight: 500; line-height: 1.15; margin: 0 0 1rem; color: var(--ink); }
/* Cormorant defaults to old-style figures ("01" reads as "oI"): use lining numerals */
h1, h2, h3, .step-n, .img-card-title, .cta-strip-title, .credential strong, .footer-h { font-variant-numeric: lining-nums; }
h2 { font-size: clamp(2rem, 1.4rem + 2.2vw, 3rem); }
h3 { font-size: clamp(1.4rem, 1.2rem + .6vw, 1.75rem); font-weight: 600; }
p { margin: 0 0 1rem; }
:focus-visible { outline: 3px solid var(--focus); outline-offset: 3px; }
.band :focus-visible, .cta-strip :focus-visible, .site-footer :focus-visible, .contact-panel :focus-visible, .hero :focus-visible, .img-card:focus-visible { outline-color: var(--teal); }
.container { max-width: var(--container); margin-inline: auto; padding-inline: var(--pad); position: relative; z-index: 1; }
.narrow { max-width: 56rem; }
.center { text-align: center; }
.skip { position: absolute; left: -999px; top: 0; z-index: 100; background: var(--navy); color: #fff; padding: .6rem 1rem; }
.skip:focus { left: 1rem; top: 1rem; }

/* ---- review banner (not part of the design) ---- */
.review-banner { background: #FBF7D5; color: #3b3f14; font-size: .85rem; text-align: center; padding: .45rem var(--pad); border-bottom: 1px dashed #B9AE45; }
.review-banner a { color: #3b3f14; font-weight: 500; margin-inline: .1rem; }
.review-banner a[aria-current] { font-weight: 700; text-decoration: none; background: #3b3f14; color: #FBF7D5; padding: 0 .35rem; border-radius: 3px; }

/* ---- buttons: rounded (pill) on request, uppercase as on the sister sites; one variable to adjust ---- */
:root { --btn-radius: 999px; }
/* text-align:center and text-wrap:balance matter once a label wraps, which the
   hero's "Book your no-obligation Financial Clarity Session" does at several
   widths. Without them the second line was left-aligned and short, so the pill
   looked lopsided. balance evens the lines; center keeps them symmetrical
   inside the pill. Browsers without text-wrap:balance simply get centred text,
   which is already the bigger part of the fix. */
.btn { display: inline-block; font: 700 1rem/1.2 var(--f-body); text-transform: uppercase; letter-spacing: .01em; text-decoration: none; padding: .95rem 1.6rem; border: 0; border-radius: var(--btn-radius); cursor: pointer; transition: background-color .15s; text-align: center; text-wrap: balance; }
.btn--primary { background: var(--btn-primary-bg); color: var(--btn-primary-ink); }
.btn--primary:hover { background: var(--btn-primary-hov); }
.btn--secondary { background: var(--btn-secondary-bg); color: var(--btn-secondary-ink); }
.btn--secondary:hover { background: var(--btn-secondary-hov); }
.btn--lg { padding: 1.2rem 2.2rem; font-size: 1.05rem; }

/* ---- short heading rule ---- */
.rule { display: block; width: 5rem; height: 1px; background: var(--navy); margin: 0 0 1.4rem; }
.center .rule { margin-inline: auto; }
.rule--accent { background: var(--accent); }

/* ---- header ---- */
.nav-toggle { position: absolute; opacity: 0; pointer-events: none; }
.site-header { background: #fff; border-bottom: 1px solid rgba(29,53,87,.12); position: relative; z-index: 20; }
.header-inner { display: flex; align-items: center; gap: 2rem; min-height: 5.6rem; padding-block: .9rem; }
.brand { display: inline-flex; flex-direction: column; gap: .3rem; text-decoration: none; }
/* 200px floor, not 160: cork-co.com and corkwills.com both render their logo
   at 230px on a phone and this one sat at 160, which read as a smaller firm
   rather than a quieter one. 200 is most of the way there without matching
   them outright. The middle term only overtakes the floor around 470px wide,
   so this changes phones and leaves the desktop lockup at 236px untouched. */
.brand img { width: clamp(200px, 14vw + 40px, 236px); }
/* The strapline is locked up with the wordmark and should measure the same
   width as it, so text-align-last justifies that one line out to the logo's
   edge. That makes the TYPE SIZE the thing that controls the word gaps: too
   small and justify makes up the difference in whitespace, which is what read
   as three separate words rather than a strapline. The clamp tracks the logo's
   own clamp so the text lands a few pixels short of the mark at every width -
   justify then has two or three pixels to do rather than forty-five - and both
   edges of the lockup line up. Bigger again and the strapline overhangs the
   logo, which is the same raggedness the other way round. */
.brand-strap { font: 700 clamp(.9rem, .924vw + .165rem, .974rem)/1.2 var(--f-body);
               color: var(--navy); text-align: justify; text-align-last: justify; }
/* One band is left where the lockup gets squeezed and the strapline has to
   come down with it or it wraps. The size is justified to the logo's width, so
   it cannot be left to a viewport clamp alone: the flex row can make the logo
   narrower than its CSS width and the text does not know. Under 21.5rem the
   row runs out of room beside the burger and the logo gives up 15-35px.
   There used to be a second band, 54-66rem, where the horizontal nav competed
   for the same space; raising the burger breakpoint to 68rem removed that
   squeeze itself, so the step-down is gone rather than kept as a patch.
   Swept every 2px from 290 to 1458: the strapline holds one line from 292 up. */
@media (max-width: 21.5rem) { .brand-strap { font-size: .68rem; } }

.main-nav { margin-left: auto; display: flex; gap: .4rem 1.3rem; flex-wrap: wrap; justify-content: flex-end; }
.main-nav a { font-weight: 500; text-decoration: none; color: var(--ink); padding-block: .3rem; border-bottom: 2px solid transparent; }
.main-nav a:hover { border-bottom-color: var(--accent); }
.burger { display: none; margin-left: auto; cursor: pointer; padding: .7rem; }
.burger span, .burger span::before, .burger span::after { display: block; width: 26px; height: 2px; background: var(--navy); position: relative; content: ""; }
.burger span::before { position: absolute; top: -8px; } .burger span::after { position: absolute; top: 8px; }
#nav:focus-visible ~ .site-header .burger { outline: 3px solid var(--focus); }
/* 68rem, not 56. The horizontal nav needs 1065px before anything has to
   wrap: 717px of nav, a 236px lockup, the 32px gap between them and 2x40px of
   padding. Below that the row ran out of room and flex squeezed the LOGO
   instead - so between 896px and about 1044px the lockup shrank, the
   justified strapline no longer fitted the narrower logo, and the whole
   thing changed size as you rotated the phone. The burger now takes over
   before the row can ever wrap, which is what removes the squeeze rather
   than compensating for it. Measured, and swept every 2px to confirm. */
@media (max-width: 68rem) {
  .burger { display: block; }
  .main-nav { display: none; position: absolute; top: 100%; left: 0; right: 0; background: #fff; flex-direction: column; gap: 0; padding: .5rem var(--pad) 1.25rem; box-shadow: 0 12px 24px rgba(0,0,0,.12); }
  .main-nav a { padding: .85rem 0; border-bottom: 1px solid rgba(29,53,87,.12); }
  #nav:checked ~ .site-header .main-nav { display: flex; }
}

/* ---- hero: full-bleed photo under a navy overlay ---- */
.hero { position: relative; min-height: clamp(34rem, 60vw, 46.875rem); display: flex; align-items: center; background: var(--navy); overflow: hidden; color: #fff; }
.hero-bg { position: absolute; inset: 0; width: 100%; height: 100%; object-fit: cover; object-position: 60% 40%; }
.hero-overlay { position: absolute; inset: 0; background: var(--hero-overlay); }
/* Asymmetric on purpose: .hero is a centring flex container, so a heavier
   bottom pad lifts the whole block off centre rather than squashing it. */
.hero-content { padding-block: 3rem 6rem; max-width: var(--container); width: 100%; }
.hero h1 { color: #fff; font-weight: 600; font-size: clamp(2.5rem, 1.6rem + 3.4vw, 3.75rem); max-width: 42rem; margin-bottom: 1rem; }
.hero-sub { font-size: clamp(1.05rem, 1rem + .3vw, 1.25rem); max-width: 38rem; margin-bottom: 1.6rem; }
.hero-fine { font-size: .9rem; margin-top: 1.1rem; opacity: .95; }

/* ---- sections ---- */
.section { padding-block: clamp(3.5rem, 2.5rem + 4vw, 5.5rem); position: relative; overflow: hidden; }
.section--tint { background: var(--neutral); }
.section--grey { background: var(--grey); }
.head { max-width: 50rem; margin: 0 auto clamp(2rem, 4vw, 3rem); }
.watermark::before { content: "&"; position: absolute; left: -.5rem; bottom: -2.25rem; font: 400 clamp(10rem, 18vw, 17rem)/1 var(--f-head); color: var(--watermark); pointer-events: none; z-index: 0; }
.watermark--dark::before { color: var(--watermark-dark); }
.intro p { max-width: 50rem; margin-inline: auto; }

.proof { list-style: none; padding: 0; margin: 1.75rem auto 2rem; display: flex; flex-wrap: wrap; justify-content: center; gap: .5rem 0; }
.proof li { font: 700 .82rem/1.2 var(--f-body); letter-spacing: .12em; text-transform: uppercase; color: var(--navy); padding: .2rem 1.1rem; border-left: 1px solid var(--navy); }
.proof li:first-child { border-left: 0; }
@media (max-width: 40rem) { .proof { flex-direction: column; align-items: center; gap: .4rem; } .proof li { border-left: 0; padding: .1rem 0; } }

/* life stages */
/* Five cards, so the row count matters. auto-fit gave 4+1 between 960 and
   1100px - one card alone beside a 700px hole - and left every orphan row hard
   against the left edge. Two changes:
     1. flex, not grid, with justify-content:center, so a short last row centres
        instead of stranding itself. Grid cannot do this: 1fr columns always
        fill, and fixed columns leave the same gap.
     2. explicit counts that skip four. Five divides tidily as 5, 3+2, 2+2+1 and
        1; the 4+1 band is the one that looked broken, so the layout jumps
        straight from five across to three.
   No filler cards: an empty card is a tab stop and a screen-reader
   announcement for nothing, and a decorative one looks clickable. */
.stages { display: flex; flex-wrap: wrap; justify-content: center; gap: 1.25rem; }
.stages > * { flex: 0 1 calc((100% - 5rem) / 5); }                 /* 5 across */
@media (max-width: 75rem) { .stages > * { flex-basis: calc((100% - 2.5rem) / 3); } }
@media (max-width: 48rem) { .stages > * { flex-basis: calc((100% - 1.25rem) / 2); } }
@media (max-width: 30rem) { .stages > * { flex-basis: 100%; } }
.stage { display: block; background: #fff; padding: 1.75rem 1.5rem; text-decoration: none; color: var(--ink); border-top: 3px solid var(--navy); transition: box-shadow .15s, transform .15s; }
.stage:hover { box-shadow: 0 10px 24px rgba(29,53,87,.12); transform: translateY(-2px); }
.stage-age { display: block; font: 700 .78rem/1.2 var(--f-body); letter-spacing: .1em; text-transform: uppercase; color: var(--navy); margin-bottom: .6rem; }
.stage h3 { margin-bottom: .6rem; }
.stage p { margin: 0; font-size: .95rem; }

/* split sections */
.split { display: grid; grid-template-columns: 1fr 1fr; gap: clamp(2rem, 6vw, 6rem); align-items: center; }
.split-media { margin: 0; }
/* The two founders side by side. The originals are a square studio headshot and
   a tall seated portrait; tools/make-headshots.py crops both to 4:5 so they
   read as a pair rather than two unrelated pictures. */
/* The two founders. .split-media img forces aspect-ratio 6/5, which squashed
   both portraits into landscape letterboxes, so this restores 4:5. It has to
   name both classes: at equal specificity the 6/5 rule below wins on order,
   which is exactly what happened the first time this was written. The pair is
   deliberately NOT stretched to the text's full height: that made a near-1:2
   slot which cropped Stefan to one shoulder. tools/make-headshots.py matches
   them on subject scale instead, which is what actually made them read as a
   pair. */
.portraits { display: grid; grid-template-columns: 1fr 1fr; gap: 1rem; }
.split-media.portraits img { width: 100%; aspect-ratio: 4 / 5; object-fit: cover; display: block; }
.portraits figcaption { grid-column: 1 / -1; font-size: .9rem; color: var(--muted);
                        margin-top: .6rem; }
.split-media img { width: 100%; aspect-ratio: 6 / 5; object-fit: cover; }
.split-text h2 { margin-bottom: 1.25rem; }
/* "More about us" sits centred in its column while the text above it stays
   ranged left. Scoped to a direct child so it cannot catch buttons nested in
   anything else that lands in a split. */
.split-text > .btn { display: block; width: fit-content; margin-inline: auto; }
.lead-bold { font-weight: 700; }
@media (max-width: 52rem) { .split { grid-template-columns: 1fr; } }
.credential { display: flex; gap: 1rem; align-items: center; background: #fff; border-left: 3px solid var(--navy); padding: .9rem 1.1rem; margin: 1.5rem 0 .4rem; }
.credential img { width: 4.5rem; height: 4.5rem; border-radius: 50%; object-fit: cover; flex-shrink: 0; }
.credential p { margin: 0; font-size: .95rem; }
.credential strong { font: 600 1.3rem/1.2 var(--f-head); }

/* services: image cards with navy overlay (corkwills "How We Can Help") */
.cards { display: grid; gap: 1.25rem; grid-template-columns: repeat(auto-fit, minmax(min(100%, 19rem), 1fr)); }
.img-card { position: relative; display: block; min-height: 22rem; overflow: hidden; text-decoration: none; color: #fff; background: var(--navy); }
.img-card img { position: absolute; inset: 0; width: 100%; height: 100%; object-fit: cover; transition: transform .4s; }
.img-card-body { position: absolute; inset: 0; background: var(--card-overlay); display: flex; flex-direction: column; justify-content: center; align-items: center; text-align: center; padding: 2rem 1.75rem; gap: .75rem; transition: background-color .2s; }
.img-card-title { font: 600 clamp(1.6rem, 1.4rem + .6vw, 2rem)/1.15 var(--f-head); }
.img-card-text { font-size: .98rem; line-height: 1.55; }
.img-card-link { font-weight: 700; text-transform: uppercase; font-size: .85rem; letter-spacing: .06em; border-bottom: 1px solid currentColor; }
.img-card:hover img { transform: scale(1.04); }
.img-card:hover .img-card-body { background: rgba(29,53,87,.82); }

/* steps */
.steps { list-style: none; margin: 0; padding: 0; display: grid; gap: 2.25rem 2.5rem; grid-template-columns: repeat(auto-fit, minmax(min(100%, 18rem), 1fr)); }
.steps li { border-top: 1px solid rgba(29,53,87,.22); padding-top: 1.25rem; }
.step-n { display: block; font: 600 2.6rem/1 var(--f-head); color: var(--accent); margin-bottom: .6rem; }
.steps h3 { font-size: 1.5rem; margin-bottom: .45rem; }
.steps p { margin: 0; }

/* navy band */
.band { background: var(--navy); color: #fff; padding-block: clamp(3rem, 2rem + 3vw, 4rem); position: relative; overflow: hidden; }
.band h2 { color: #fff; }
.band .split-media img { aspect-ratio: 6 / 5; }

/* insights */
/* .posts/.post, Schema B's photo-topped article card, is gone: the Insights
   index builds its own feature and cards below. .post-meta and .post-more stay
   - the feature card still uses both. */
.post-meta { font: 700 .78rem/1.2 var(--f-body); letter-spacing: .1em; text-transform: uppercase; color: var(--navy); margin-bottom: .6rem; }
.post-more { margin-top: auto; font-weight: 700; text-transform: uppercase; font-size: .85rem; letter-spacing: .06em; color: var(--navy); }
.post-more::after { content: " →"; }

/* reviews placeholder */
.stars { color: var(--accent); font-size: 1.3rem; letter-spacing: .15em; margin-bottom: .75rem; }

/* CTA strip (corkwills "Book a meeting…") */
/* 10px more room above the button. As padding, not margin: a margin showed a
   white strip of page background between the content and the band. */
.cta-strip { background: var(--navy); color: #fff; padding-top: 10px; }
.cta-strip-inner { display: flex; flex-wrap: wrap; align-items: center; justify-content: space-between; gap: 1.25rem 2rem; padding-block: 2.1rem; }
.cta-strip-title { font: 500 clamp(1.5rem, 1.2rem + 1.2vw, 2.1rem)/1.2 var(--f-head); margin: 0; }

/* contact ("Let's Get Started") */
.contact-grid { display: grid; grid-template-columns: minmax(0, .85fr) minmax(0, 1.15fr); gap: 2.5rem; align-items: start; }
@media (max-width: 56rem) { .contact-grid { grid-template-columns: 1fr; } .contact-panel { order: 2; margin-top: 0 !important; } }
.contact-panel { background: var(--navy); color: #fff; padding: clamp(1.75rem, 4vw, 2.75rem); margin-top: 2.4rem; }
.contact-panel dl { margin: 0; display: grid; gap: 1.4rem; }
.contact-panel dt { font-weight: 700; text-transform: uppercase; font-size: .92rem; padding-bottom: .45rem; margin-bottom: .55rem; border-bottom: 1px solid rgba(255,255,255,.35); display: flex; gap: .6rem; align-items: center; }
.contact-panel dd { margin: 0; }
.contact-panel a { color: #fff; font-weight: 500; }
.ico { color: var(--teal); font-size: 1.1rem; width: 1.2rem; text-align: center; }
.highlight { font-size: clamp(2.2rem, 1.6rem + 2vw, 3rem); margin-bottom: 1.75rem; }
.highlight span { background: linear-gradient(transparent 58%, var(--teal) 58%, var(--teal) 92%, transparent 92%); padding: 0 .4rem 0 .1rem; }
.contact-form label { display: block; font-weight: 700; font-size: .85rem; text-transform: uppercase; margin-bottom: 1rem; }
.contact-form input, .contact-form select, .contact-form textarea { display: block; width: 100%; margin-top: .35rem; font: 400 1rem/1.4 var(--f-body); color: var(--ink); border: 1px solid #6B7280; border-radius: 0; padding: .7rem .75rem; background: #fff; text-transform: none; }
.contact-form input:focus-visible, .contact-form select:focus-visible, .contact-form textarea:focus-visible { outline: 3px solid var(--focus); outline-offset: 0; border-color: var(--navy); }
.field-row { display: grid; grid-template-columns: repeat(3, 1fr); gap: 0 1rem; }
@media (max-width: 40rem) { .field-row { grid-template-columns: 1fr; } }
.form-note { font-size: .85rem; color: var(--muted); }
.form-note a { color: var(--navy); }
.form-actions { text-align: right; }

/* footer */
/* NOTE: padding-block here is DEAD. .site-footer is declared three times in this
   file and the Schema E block near the end wins — search "[3b]" for the rule that
   actually sets the footer's padding. */
.site-footer { background: var(--footer-bg); color: #fff; font-size: .9rem; padding-block: 3rem 1.5rem; }
.site-footer a { color: #fff; text-decoration: none; }
.site-footer a:hover { text-decoration: underline; }
.footer-cols { display: grid; grid-template-columns: 1.4fr 1fr; gap: 2rem; }
@media (max-width: 40rem) { .footer-cols { grid-template-columns: 1fr; } }
.footer-h { color: #fff; font: 600 1.35rem/1.2 var(--f-head); margin-bottom: 1rem; }
.footer-links { list-style: none; margin: 0; padding: 0; display: grid; gap: .35rem; }
.footer-links--2col { grid-template-columns: repeat(2, max-content); gap: .35rem 3rem; }
@media (max-width: 30rem) { .footer-links--2col { grid-template-columns: 1fr; } }
.here { opacity: .85; }
.legal { margin-top: 2.25rem; font-size: .78rem; line-height: 1.55; }
.legal p { margin-bottom: .55rem; }
.footer-bottom { border-top: 1px solid rgba(255,255,255,.3); margin-top: 1.5rem; padding-top: 1.1rem; display: flex; flex-wrap: wrap; justify-content: space-between; gap: .5rem 2rem; font-size: .78rem; text-transform: uppercase; font-weight: 700; }
.footer-bottom p { margin: 0; }

/* ---- C overrides: no red anywhere outside the logo ---- */
.rule--accent { background: var(--navy); }                     /* on light sections */
.hero .rule--accent { background: var(--teal); height: 2px; }  /* on the navy hero */
.main-nav a:hover { border-bottom-color: var(--teal); }
.step-n { color: var(--navy); }
.steps li { border-top-color: var(--teal); border-top-width: 2px; }
.stage { border-top-color: var(--teal); border-top-width: 4px; }
.stars { color: var(--teal); }
.btn--primary:focus-visible { outline-color: var(--navy); }
.band .btn--primary:focus-visible, .cta-strip .btn--primary:focus-visible, .hero .btn--primary:focus-visible { outline-color: #fff; }
.site-footer { border-top: 4px solid var(--teal); }
.footer-h { color: var(--teal); }
.credential { border-left-color: var(--teal); border-left-width: 4px; }
.hero-fine { max-width: 34rem; }
@media (max-width: 52rem) { .hero-overlay { background: rgba(29,53,87,.78); } }

/* Review notes hidden for client viewing (10 Sep 2026). Delete this rule to show them again. */
.tbc, 
/* =============================================================================
   CORK & CO WEALTH — additions to the Schema B base.
   Each block is separately revertible. Nothing above this line was restyled.
   ============================================================================= */

/* --- [2] HERO: Schema E's two-column grid inside Schema B's photo hero ------
   B keeps .hero / .hero-bg / .hero-overlay untouched; only the content inside
   .hero-content is re-laid-out, and E's framed figure is imported.           */
:root {
  --on-dark-muted: rgba(255,255,255,.86);
  --hair-dark: rgba(168,218,220,.35);
}
.hero-grid { display: grid; grid-template-columns: 1.15fr .85fr; gap: clamp(2rem, 5vw, 5rem); align-items: center; }
.hero-grid > div { min-width: 0; }
.hero .hero-sub { color: #fff; }
.hero-grid p { max-width: 34rem; }
.hero-actions { display: flex; flex-wrap: wrap; gap: 1rem 1.5rem; align-items: center; margin-top: 1.9rem; }
.hero-actions .more { color: #fff; font-weight: 500; text-decoration: none; border-bottom: 1px solid currentColor; padding-bottom: .1em; }
.hero-actions .more:hover { border-bottom-width: 2px; }
/* Framed photo kept for inner pages; the hero no longer uses it. */
.frame { margin: 0; justify-self: end; width: 100%; max-width: 26rem;
         padding: var(--frame-inset, .85rem); border: 1px solid var(--teal);
         background: rgba(29,53,87,.55); backdrop-filter: blur(2px); }
.frame img { display: block; width: 100%; aspect-ratio: 4 / 5; object-fit: cover;
             object-position: var(--focus-x, 50%) var(--focus-y, 50%); }
.frame-crop { overflow: hidden; }
.frame-crop img { transform: scale(var(--zoom, 1)); transform-origin: var(--zoom-origin, 50% 50%); }
@media (max-width: 54rem) {
  .hero-grid { grid-template-columns: 1fr; }
  .frame { justify-self: start; max-width: 22rem; --frame-inset: .65rem; }
}

/* --- [3] FOOTER .legal — Schema E's block, as supplied by the client 27 Oct ---
   E's own sizing is kept here at the client's request. The in-page .risk blocks
   stay at 1rem. NOTE: approved CW-WEB-10 also lists pension-age, tax-treatment and
   protection-terms paragraphs in the footer; the client chose to omit them.      */
.contact-panel h2 { color: #fff; }
.legal { border-top: 1px solid var(--hair-dark); margin-top: 2.25rem;
         padding-block: 1.75rem 2.25rem; color: rgba(255,255,255,.88);
         font-size: .9rem; line-height: 1.6; }
.legal p { margin-bottom: .7rem; max-width: 86ch; }
.legal-grid { display: grid; grid-template-columns: repeat(3, 1fr); gap: 1.25rem 2.5rem; }
.legal-grid h3 { font: 500 .8rem/1.3 var(--f-body); letter-spacing: .18em; text-transform: uppercase;
                 color: var(--teal); margin: 0 0 .85rem; }
.legal-grid p { max-width: 44ch; text-align: justify; hyphens: auto; }
.legal-grid > div > :last-child { margin-bottom: 0; }
.legal-links { display: flex; flex-wrap: wrap; gap: .4rem 1.3rem; margin-top: 1.75rem;
               padding-top: 1.25rem; border-top: 1px solid rgba(168,218,220,.22); }
/* The build credit sits at the far end of the legal row, the way soyc.co.uk
   carries it. margin-inline-start:auto only bites while the row is on one line;
   once it wraps, the rule below centres the whole row and the credit with it. */
.legal-links .fcredit { margin-inline-start: auto; }
/* Column titles are centred at every width. */
.legal-grid h3 { text-align: center; }

/* Once the footer stops being a wide multi-column row, centre the columns and
   their contents rather than leaving an orphan stranded against the left edge.
   Bullets lose their markers when centred — a centred bullet list reads badly. */
@media (max-width: 60rem) {
  .legal-grid { grid-template-columns: 1fr 1fr; justify-items: center; }
  .legal-grid p { max-width: 46ch; margin-inline: auto; }
  .legal-links { justify-content: center; }
  .legal-links .fcredit { margin-inline-start: 0; }
  .ftr-cols { justify-items: center; text-align: center; }
  .ftr-cols .ftr-logo { margin-inline: auto; }
  .ftr-cols .social { justify-content: center; }
  .family { text-align: center; }
  /* The label's leading rule is a left-hand marker: it reads as the start of a
     line of text. Centred, it becomes a dash floating off the front of
     "The Cork & Co family" with nothing to anchor it, so it goes with the
     alignment it belongs to. The label keeps its letter-spaced teal caps. */
  .family > .label { justify-content: center; }
  .family > .label::before { display: none; }
}
@media (max-width: 44rem) { .legal-grid { grid-template-columns: 1fr; gap: 1.5rem; } }

/* A page that does not scroll is ~15px wider than one that does, which moves
   every centred container sideways when you switch tabs. Reserve the gutter
   whether or not it is needed. Chrome 94+, Firefox 97+, Safari 18.2+. */
html { scrollbar-gutter: stable; }

/* --- [4] PAGE HERO: photo banner, after soyc's .phead ----------------------
   --bg / --bg-md / --bg-sm are written by the image chooser (?swap=1).        */
/* NOT a flex container. It was `display:flex; align-items:flex-end`, which caused
   two separate problems:
     vertically, the block was pinned to the bottom, so a lede of one line versus
     five put the crumbs and headline at a different height on nearly every page;
     horizontally, .container became a FLEX ITEM, so it shrank to fit its text and
     its `margin-inline:auto` then centred that shrunken box — giving six different
     left edges at 1280px, which is the one you could actually see.
   Plain block layout fixes both: the container is full width again, so max-width
   and auto margins behave normally, and content flows from the top. */
.phead { position: relative; min-height: clamp(16rem, 26vw, 22rem);
         overflow: hidden; color: #fff; background: var(--navy); }
.phead-bg { position: absolute; left: 0; right: 0; top: -16%; height: 132%; z-index: 0;
            background-image: var(--bg); background-size: cover;
            background-position: var(--bgpos, center 45%);
            /* pulls a warm photograph back toward the navy so every banner
               reads the same whichever picture ends up in the slot */
            filter: saturate(.78); }
.phead::after { content: ""; position: absolute; inset: 0; z-index: 1;
                background: linear-gradient(180deg, rgba(29,53,87,.52) 0%, rgba(29,53,87,.9) 100%); }
.phead .container { position: relative; z-index: 2;
                    padding-block: clamp(2.75rem, 2rem + 3vw, 4.25rem) clamp(2.25rem, 2rem + 2vw, 3.5rem); }
/* RESERVED SLOTS. Each element holds space for the longest text any page puts
   in it, so the element after it always starts at the same offset and the whole
   block lands in the same place on every page — ctrl-tab between two tabs and
   "Home" does not move. The banner's own height then matches across pages as a
   consequence, with no hard-coded height to go stale.
   Reserved space, not absolute positioning: if a future string overruns its slot
   it pushes down rather than being silently clipped, and clipping an approved
   headline or a risk warning is a compliance problem, not a cosmetic one.
   Line counts come from measuring the real copy at each breakpoint; the lede
   needs FOUR lines at >=1500px where it needs three at 1280, because its
   font-size grows with clamp() while max-width stays at 46rem. */
/* Inner-page headings follow Schema E, which is the same device the hero uses:
   a short statement with the second half in italic teal. Scaled up from 32px to
   sit closer to the hero's 60px without outshouting it - the home page should
   still be the loudest. min-height stays in em, so the two reserved lines scale
   with the type and every banner keeps the same height. */
.phead h1 { color: #fff; margin-bottom: .5rem; line-height: 1.15; font-weight: 600;
            /* 2.5rem floor: the 2rem one produced 32px on a phone against
               cork-co's 40 and corkwills' 48. 40px is cork-co's figure, the
               more restrained of the two. Above ~470px the middle term takes
               over and nothing changes. */
            font-size: clamp(2.5rem, 1.35rem + 2.1vw, 3rem); max-width: 42rem;
            min-height: calc(2 * 1.15em); }
.phead h1 em { color: var(--teal); font-style: italic; font-weight: 400; }
/* THE INSIGHTS STRIP. Everything under Insights - the index and all nine
   articles - opens on a shallow photo strip saying "Insights" rather than a
   banner the height of a screen. An article's own title is the first thing in
   the body column below, so the banner does not say it first and the white
   section is not headless. These are deliberately the one exception to the
   equal-height reserves above: they match each other, not the other ten pages.
   .phead-label is the same words on an article, where the h1 belongs to the
   title; it is styled with the h1 so the two pages look identical. */
.phead--strip { min-height: clamp(9rem, 13vw, 11rem); }
.phead--strip .container { padding-block: clamp(1.75rem, 1.25rem + 1.5vw, 2.5rem); }
.phead--strip .crumbs { margin-bottom: .75rem; }
.phead--strip h1, .phead-label { color: #fff; margin: 0; line-height: 1.15;
  font: 500 clamp(1.6rem, 1.25rem + 1.1vw, 2.2rem)/1.15 var(--f-head); }
/* Both classes named on purpose: the 479px block further down reserves three
   lines for .phead h1 at equal specificity and comes later, so a single class
   would lose and the strip would grow a reserve it has no use for. */
.phead.phead--strip h1 { min-height: 0; }
/* The article's title, at the top of the body column. Sized between a page
   statement and the index's feature card. */
.prose > h1 { font-size: clamp(1.9rem, 1.4rem + 1.6vw, 2.6rem); font-weight: 500;
              max-width: 24ch; margin: 0 0 1.5rem; }
.phead .lede { font-size: clamp(1.05rem, 1rem + .35vw, 1.3rem); max-width: 46rem;
               margin: 0; color: #fff; line-height: 1.5;
               min-height: calc(4 * 1.5em); }
.phead .rule--accent { background: var(--teal); height: 2px; }
/* Line counts are set by the longest lede on the site, which is Our Services.
   Reserving less makes that one page taller than the rest; reserving more only
   adds empty space. At 375px the resulting banner is ~460px, which is no taller
   than the tallest banner was before any of this. */
@media (max-width: 1499px) { .phead .lede { min-height: calc(4 * 1.5em); } }
@media (max-width: 767px)  { .phead .lede { min-height: calc(6 * 1.5em); } }
@media (max-width: 479px)  { .phead h1    { min-height: calc(3 * 1.15em); }
                             .phead .lede { min-height: calc(7 * 1.5em); }
                           }
/* gradient-only variant for any page that should carry no photograph */
.phead--plain { background: linear-gradient(135deg, var(--navy) 0%, #24406A 100%); }
/* Legal pages, watermark treatment. Same ampersand the rest of the site uses as
   a section device (.watermark), scaled to fill the banner and kept very faint so
   it furnishes the space without becoming decoration on a page of plain facts.
   Right-hand side, so it never sits under the crumbs, heading or lede. */
.phead--mark::before { content: "&"; position: absolute; right: clamp(1rem, 5vw, 5rem);
  top: 50%; transform: translateY(-50%); line-height: .8;
  font: 400 clamp(11rem, 26vw, 24rem)/0.8 var(--f-head);
  color: rgba(255,255,255,.055); pointer-events: none; z-index: 0; }
/* Sized for a 22rem banner; on the strip it would be taller than the band it
   sits in, so it is scaled to the smaller block. */
.phead--strip.phead--mark::before { font-size: clamp(6rem, 12vw, 9rem); }
.phead--plain .phead-bg, .phead--plain::after { display: none; }
/* Two declarations per step: the plain url() is the floor, and the image-set()
   after it takes the WebP where image-set() is understood.
   [style*="--bgw"] is not decoration. An undefined custom property inside
   var() makes the whole declaration INVALID AT COMPUTED-VALUE TIME, which
   resolves to unset - it does not fall back to the declaration above. Any
   .phead-bg without the WebP variables (the Grav demo's own templates write
   only --bg) would therefore have had no background at all. The attribute
   selector makes the image-set rule apply only where bg_vars() has supplied
   the whole set. */
.phead-bg[style*="--bgw"] { background-image: image-set(var(--bgw) type("image/webp"),
                                                        var(--bg)  type("image/jpeg")); }
@media (max-width: 1200px) {
  .phead-bg { background-image: var(--bg-md, var(--bg)); }
  .phead-bg[style*="--bgw"] { background-image: image-set(var(--bgw-md, var(--bgw)) type("image/webp"),
                                                          var(--bg-md,  var(--bg))  type("image/jpeg")); }
}
@media (max-width: 560px) {
  /* PORTRAIT FOCAL POINT. At 412x810 a 3:2 landscape is scaled until its
     HEIGHT fills the box, so about two thirds of its width is thrown away and
     you see a narrow vertical slice. Which slice is the only thing still under
     our control, and "center" is usually the sky. --bgpos-sm is set per banner
     in build.py's BANNER map; without one the banner keeps --bgpos. */
  .phead-bg { background-position: var(--bgpos-sm, var(--bgpos, center 45%)); }
  /* The hero is an <img> with object-fit, not a background, so it needs the
     same treatment separately. At 60% 40% the church tower sat small and low;
     70% 75% fills the frame with it. */
  .hero-bg { object-position: 70% 75%; }
  .phead-bg { background-image: var(--bg-sm, var(--bg-md, var(--bg))); }
  .phead-bg[style*="--bgw"] { background-image: image-set(var(--bgw-sm, var(--bgw)) type("image/webp"),
                                                          var(--bg-sm,  var(--bg))  type("image/jpeg")); }
}
.crumbs { font-size: .9rem; line-height: 1.4; margin-bottom: .9rem; color: rgba(255,255,255,.85); }
/* Below ~375px the longest topic - "Planning in your 30s and 40s" - wraps the
   trail onto a second line and made those two article banners 23px taller than
   the rest. Reserved on every phead, not just the long ones, so they all stay
   the same height whether the trail wraps or not. */
@media (max-width: 479px) { .phead .crumbs { min-height: calc(2 * 1.4em); } }
.crumbs a { color: #fff; }
.crumbs span { margin-inline: .45em; }

/* --- [compliance] RISK WARNINGS --------------------------------------------
   Body size, body colour, beside the benefit. Never shrink, never collapse.   */
.risk { border-left: 3px solid var(--teal); padding: .1rem 0 .1rem 1.1rem;
        margin: 1.5rem 0; font-size: 1rem; color: var(--ink); }
.risk p { margin-bottom: .6rem; }
.risk p:last-child { margin-bottom: 0; }
.band .risk, .hero .risk { color: #fff; }
.hero .risk { margin-top: 1.5rem; max-width: 48rem; }

/* --- FAQ accordion (questions only — never a risk warning) ------------------ */
.faq { border-top: 1px solid rgba(29,53,87,.22); }
.faq details { border-bottom: 1px solid rgba(29,53,87,.22); }
.faq summary { cursor: pointer; list-style: none; display: flex; justify-content: space-between;
               gap: 1rem; align-items: center; padding: 1.15rem 0;
               font: 600 clamp(1.15rem, 1.05rem + .4vw, 1.4rem)/1.35 var(--f-head); }
.faq summary::-webkit-details-marker { display: none; }
.faq summary::after { content: "+"; flex: none; width: 2rem; height: 2rem; border-radius: 50%;
                      background: var(--neutral); display: grid; place-items: center;
                      font: 400 1.35rem/1 var(--f-body); color: var(--navy); }
.faq details[open] summary::after { content: "\2212"; background: var(--teal); }
.faq summary:hover { color: var(--focus); }
.faq .answer { padding: 0 3rem 1.35rem 0; }
.faq .answer > :last-child { margin-bottom: 0; }

/* --- Long-form prose (complaints, privacy, articles) ------------------------ */
.prose { max-width: 46rem; }
.prose h2 { font-size: clamp(1.5rem, 1.3rem + .8vw, 2rem); margin-top: 2.25rem; }
.prose h3 { margin-top: 1.75rem; }
.prose ul, .prose ol { padding-left: 1.3rem; }
.prose li { margin-bottom: .45rem; }
.prose a { color: #2F5F7D; }
.prose a.btn--primary { color: var(--btn-primary-ink); }
.prose .doc-version { font-size: .9rem; letter-spacing: .04em; text-transform: uppercase;
                      color: #5A6B7B; margin: 0 0 1.5rem; }
.prose h3 { font-size: 1.15rem; color: var(--navy); }
.prose .nowrap { white-space: nowrap; }

/* [9] PROSE COLUMNS START WHERE EVERYTHING ELSE STARTS -----------------------
   .narrow and .prose set a max-width on the CONTAINER, which .container then
   centres. On FAQs that put the accordion 172px to the right of the headline
   above it, and the page read as misaligned. Keep the container on the normal
   track so its edge matches the header and the banner, and limit the measure on
   its children instead — same comfortable line length, left-aligned.
   .center is the opt-out, for the homepage intro that is centred by design. */
.container.narrow:not(.center) { max-width: var(--container); }
.container.narrow:not(.center) > * { max-width: 56rem; margin-inline: auto; }
.container.prose:not(.center) { max-width: var(--container); }
.container.prose:not(.center) > * { max-width: 46rem; }

/* [5] INSIGHTS ---------------------------------------------------------------
   The index's cards are at [10]; what is left here belongs to the article
   pages. */
.post-more { padding-top: .2rem; }
.prose .back-to { margin-top: 2.5rem; padding-top: 1.25rem; border-top: 1px solid var(--line, #DDE3E9); }
.prose .back-to a { font-weight: 700; }

/* [6] LIFE STAGES: alternating photo/text rows ------------------------------
   Was five full-width bands of text in a narrow container, which left the page
   feeling empty. Each stage is now a half-and-half row, the picture swapping
   sides down the page. Collapses to photo-above-text in one column. */
.stage-row { display: grid; grid-template-columns: 1fr 1fr; gap: clamp(1.75rem, 1rem + 3vw, 3.5rem);
             align-items: center; }
.stage-row--flip .stage-shot { order: 2; }
.stage-shot { margin: 0; }
.stage-shot img { display: block; width: 100%; aspect-ratio: 4 / 3; object-fit: cover; }
.stage-copy > :last-child { margin-bottom: 0; }
.stage-copy h2 { margin-bottom: .75rem; }
@media (max-width: 860px) {
  .stage-row { grid-template-columns: 1fr; gap: 1.5rem; }
  .stage-row--flip .stage-shot { order: 0; }   /* photo always leads when stacked */
  .stage-shot img { aspect-ratio: 16 / 9; }
}

/* [7] CTA STRIP: a slim rail rather than a band ---------------------------- */
.cta-strip-inner { padding-block: .5rem; }
/* The strip is a slim rail now, but .btn--lg still carried 1.2rem of vertical
   padding, so the button was 59px of a 75px bar and the rail read as a button in
   a box. Slimmed HERE rather than on .btn--lg, which is on 17 buttons across the
   site including the contact page's main booking call to action and the hero —
   shrinking those too would drop the primary conversion action below a
   comfortable touch target on a phone. */
.cta-strip .btn--lg { padding-block: .6rem; }
/* Once the strip wraps, the button sits at its natural width and stops short of
   the right edge, so it no longer lines up with the footer column above it.
   Full width closes that and is the usual mobile call-to-action anyway. */
@media (max-width: 767px) {
  .cta-strip-inner { gap: .9rem; }
  .cta-strip-inner .btn { width: 100%; text-align: center; }
}

/* [8] INSIGHTS INDEX: chips, a lead article, then a compact list ------------
   Replaces nine equal cards, which gave every article the same weight and made
   the page shout. Shaped after the soyc news page, without the photographs. */
/* INSIGHTS INDEX ------------------------------------------------------------
   No photographs here, deliberately: a two-person firm writing occasionally
   should not have to source an image per article, and a stale stock picture is
   worse than none. So the hierarchy is all type and space - a feature that is
   allowed to be large, then eight cards that are plainly secondary.

   Eight is the number that matters. It divides by four and by two, so no
   breakpoint strands a single card the way the five life-stage cards did; and
   the layout is centred flex rather than grid for the same reason as .stages,
   since 1fr columns always fill and a short last row cannot centre. */
/* Both the feature and the cards are the house card surface: white, a teal top
   rule, real padding and a small lift on hover - the same treatment .stage uses
   on Life stages. The first attempt bounded them with a single hairline on
   white, which left them reading as columns of loose text rather than as cards,
   which was the whole complaint. They sit on .section--tint for the same
   reason: a white card needs something to be white against. */
.post-feature, .post-card { background: #fff; border-top: 4px solid var(--teal);
  transition: box-shadow .15s, transform .15s; }
.post-feature:hover, .post-card:hover { box-shadow: 0 10px 24px rgba(29,53,87,.12);
  transform: translateY(-2px); }
.post-feature { display: block; text-decoration: none; color: var(--ink);
  margin-bottom: 2rem; }
.post-feature h2 { font-size: clamp(1.9rem, 1.4rem + 1.9vw, 2.9rem); line-height: 1.12;
  margin: 0 0 .9rem; max-width: 24ch; }
.post-feature p { font-size: clamp(1.05rem, 1rem + .3vw, 1.2rem); max-width: 62ch;
  margin-bottom: 1.1rem; }
.post-feature:hover h2, .post-card:hover h3 { text-decoration: underline;
  text-decoration-thickness: 1px; text-underline-offset: .12em; }

/* The index holds the same measure as an article: 46rem, which is what
   .container.prose gives the body of every piece under Insights. Four cards
   across a full-width container made the index a different shape from
   everything it links to. Two across inside that measure also divides eight
   exactly, so there is no short last row to centre or leave hanging. */
.post-feature, .post-cards { max-width: 46rem; margin-inline: auto; }
.post-cards { display: flex; flex-wrap: wrap; justify-content: center; gap: 1.75rem; }
.post-card { flex: 0 1 calc((100% - 1.75rem) / 2); display: flex; flex-direction: column;
  text-decoration: none; color: var(--ink); }
.post-card h3 { font-size: 1.22rem; line-height: 1.25; margin: 0 0 .5rem; }
.post-card p { font-size: .96rem; margin: 0 0 1rem; color: var(--muted); }
/* THE PADDING LIVES ON .post-body, NOT ON THE CARD, so that a thumbnail can
   run to the card's edge instead of sitting in a frame of white. A card with
   no photograph must look exactly as it did before this existed, which is why
   the two values below are the ones the cards themselves used to carry - the
   index will be a mixture of illustrated and plain articles for as long as it
   takes the client to photograph nine subjects, and the plain ones are not a
   degraded state. .post-card is the flex column, so .post-body has to grow for
   "margin-top: auto" on .post-when to still push the date to the bottom. */
.post-feature .post-body { padding: 1.75rem 1.9rem 2rem; }
.post-card .post-body { padding: 1.6rem 1.5rem 1.4rem;
  display: flex; flex-direction: column; flex: 1; }
/* The thumbnail sits under the teal rule and spans the card. A fixed ratio
   rather than the photograph's own: the cards are a grid and a row of
   different heights is worse than a crop. 16/9 on a card, wider on the
   feature, which is a banner-shaped slot rather than a thumbnail. */
.post-thumb { display: block; width: 100%; object-fit: cover; aspect-ratio: 16 / 9; }
.post-feature .post-thumb { aspect-ratio: 5 / 2; }
.post-feature picture, .post-card picture { display: block; }

/* A photograph halfway down the article. It runs the full width of the prose
   column rather than being inset, because at 46rem an inset picture is small
   enough to look like an afterthought. No caption: the pictures are Thame and
   the office, they illustrate rather than inform, and a caption on each would
   be nine more pieces of copy for New Leaf to approve. */
.post-figure { margin: 2.2rem 0; }
.post-figure img { display: block; width: 100%; height: auto; aspect-ratio: 3 / 2;
  object-fit: cover; }

.post-when { margin-top: auto; font: 600 .8rem/1.2 var(--f-body); color: #5A6B7B; }
.post-feature .post-when { display: block; margin-top: .9rem; }
@media (max-width: 38rem) { .post-card { flex-basis: 100%; } }

/* --- SITEMAP (the human one) ------------------------------------------------
   Four or five short lists side by side, which is the same shape the footer
   uses, so the page reads as the footer's long form rather than as a new
   device. auto-fit means the column count follows the width with no
   breakpoints, and the Insights column - the only long one - is allowed to run
   on rather than being balanced against the others. */
/* CSS columns, not grid. Grid rows are as tall as their tallest cell, and the
   Insights column is ten items against the others' two to six - so "The firm"
   ended level with it and "Legal" began a screen further down, with a hole in
   between. Columns pack instead: each group stays whole (break-inside) and the
   short ones stack up behind the long one. */
.sitemap-cols { columns: 2 15rem; column-gap: 2.5rem;
  max-width: 46rem; margin-inline: auto; }
/* Let a long group flow across the column break instead of being kept whole:
   Insights is ten items against Help's two, and keeping it intact left one
   column half empty. The heading never ends up stranded at the foot of a
   column, and no single link is split. */
.sitemap-cols > div { margin-bottom: 2.25rem; }
.sitemap-cols h2 { break-after: avoid; }
.sitemap-cols li { break-inside: avoid; }
.sitemap-cols h2 { font: 700 .78rem/1.2 var(--f-body); letter-spacing: .1em;
  text-transform: uppercase; color: var(--navy); margin: 0 0 .9rem;
  padding-bottom: .6rem; border-bottom: 1px solid var(--rule); }
.sitemap-cols ul { list-style: none; margin: 0; padding: 0; }
.sitemap-cols li { margin-bottom: .55rem; }
.sitemap-cols a { color: var(--ink); text-decoration: none; }
.sitemap-cols a:hover { text-decoration: underline; text-underline-offset: .15em; }

/* --- [2b] HERO CREDENTIALS: Schema E's letterhead row, inside Schema B's hero --- */
.credentials { border-top: 1px solid var(--hair-dark); margin-top: clamp(2rem, 4vw, 3.25rem); }
.credentials ul { list-style: none; margin: 0; padding: 0; display: grid; grid-template-columns: repeat(3, 1fr); }
.credentials li { padding: 1.6rem 1.5rem 1.8rem; border-left: 1px solid var(--hair-dark); }
.credentials li:first-child { border-left: 0; padding-left: 0; }
.credentials .k { display: block; font: 500 .8rem/1.3 var(--f-body); letter-spacing: .2em;
                  text-transform: uppercase; color: var(--teal); margin-bottom: .45rem; }
.credentials .v { display: block; color: var(--on-dark-muted); line-height: 1.5; }
@media (max-width: 40rem) {
  .credentials ul { grid-template-columns: 1fr; }
  .credentials li { border-left: 0; padding-left: 0; padding-block: 1.1rem; }
  .credentials li + li { border-top: 1px solid var(--hair-dark); }
}
.label { display: flex; align-items: center; gap: .8rem; font: 500 .8rem/1.3 var(--f-body);
         letter-spacing: .2em; text-transform: uppercase; color: var(--teal); margin: 0 0 1.1rem; }
.label::before { content: ""; width: 2.25rem; height: 1px; background: var(--teal); flex: none; }
.hero .lede { font-family: var(--f-head); font-size: clamp(1.4rem, 1.2rem + .8vw, 1.85rem);
              line-height: 1.35; color: #fff; margin-bottom: 1rem; }

/* --- [3b] FOOTER: Schema E's structure, carrying the approved CW-WEB-10 text ----
   E's own .legal sizing (.85rem, rgba white) is NOT copied — see [3].            */
/* Top padding tightened (was clamp(2.75rem, 2rem + 3vw, 4rem) = 64px at 1280).
   The CTA strip above is navy too and is now a slim rail, so the old value left
   a wide empty band between the button and "The Cork & Co family". ~39px at
   1280. THIS is the declaration that governs the footer's padding. */
.site-footer { border-top: 0; padding-block: clamp(1.75rem, 1.25rem + 1.5vw, 2.75rem) 2rem; }
.family { border-bottom: 1px solid var(--hair-dark); padding-bottom: 2rem; margin-bottom: 2.25rem; }
.family > .label { color: var(--teal); }
/* Content-width columns, pushed to the outer edges, rather than three equal
   thirds. With 1fr tracks each line of text floated inside a 374px column and
   stopped ~100px short of it, so the right-hand column's text did not line up
   with the call-to-action button directly above it. Sizing each column to its
   own text makes the first flush left and the last flush right by construction,
   however the wording changes. */
.family ul { list-style: none; margin: 0; padding: 0; display: grid; gap: 1.25rem 2rem;
             grid-template-columns: repeat(3, auto); justify-content: space-between; }
.family a, .family .here { text-decoration: none; display: block; opacity: 1; }
.family a:hover .n { text-decoration: underline; }
.family .n { display: block; font: 600 1.25rem/1.25 var(--f-head); color: var(--teal); margin-bottom: .2rem; }
.family .d { display: block; color: var(--on-dark-muted); }
.ext::after { content: " \2197"; font-size: .85em; }
/* Wealth links to this site's own home page, so a plain right arrow rather
   than the north-east one that means "leaves the site". */
.int::after { content: " \2192"; font-size: .85em; }
@media (max-width: 52rem) { .family ul { grid-template-columns: 1fr; gap: 1rem; } }

.ftr-cols { display: grid; grid-template-columns: 1.4fr 1fr 1fr 1fr; gap: 2rem; }
.ftr-cols h2 { font: 500 .8rem/1.3 var(--f-body); letter-spacing: .18em; text-transform: uppercase;
               color: var(--teal); margin-bottom: .9rem; }
.ftr-cols ul { list-style: none; margin: 0; padding: 0; display: grid; gap: .55rem; }
.ftr-cols a { text-decoration: none; }
.ftr-cols a:hover { text-decoration: underline; }
.ftr-logo { width: 185px; margin-bottom: 1.1rem; }
.ftr-cols .social, .social { display: flex; gap: .65rem; margin-top: 1.25rem; list-style: none; padding: 0; }
.social a { width: 2.5rem; height: 2.5rem; border-radius: 50%; display: grid; place-items: center;
            color: var(--teal); box-shadow: inset 0 0 0 1px rgba(168,218,220,.55); }
.social a:hover { background: var(--teal); color: var(--navy); }
/* An account that does not exist yet: shown so the row reads correctly and
   can be discussed, but deliberately not a link. */
.social .pending { width: 2.5rem; height: 2.5rem; border-radius: 50%; display: grid;
                   place-items: center; border: 1px dashed var(--hair-dark);
                   opacity: .45; cursor: default; }
.social svg { display: block; }
@media (max-width: 60rem) { .ftr-cols { grid-template-columns: 1fr 1fr; } }
@media (max-width: 44rem) { .ftr-cols { grid-template-columns: 1fr; gap: 1.75rem; } }

/* no age range on some stages — hide the empty label rather than printing a filler */
.stage-age:empty { display: none; }

/* --- Cookie banner (CW-WEB-09) ---------------------------------------------
   Schema B has no .cookie rules, so without these the h2 inherits the 48px
   Cormorant display size. Keep this block below everything else. */
.cookie { position: fixed; inset: auto 0 0 0; z-index: 60; background: #fff;
          border-top: 2px solid var(--navy); box-shadow: 0 -8px 28px rgba(29,53,87,.14);
          padding: 1.25rem 0; }
.cookie[hidden] { display: none; }
.cookie-inner { display: flex; flex-wrap: wrap; gap: 1rem 2rem; align-items: center; justify-content: space-between; }
.cookie h2 { font: 700 1rem/1.3 var(--f-body); margin: 0 0 .4rem; color: var(--ink); }
.cookie p { margin: 0; max-width: 60ch; }
.cookie-actions { display: flex; flex-wrap: wrap; gap: .75rem; align-items: center; }
.cookie .btn { padding: .7rem 1.4rem; }

/* --- Short-footer variant (proposed to New Leaf, not yet approved) ----------
   Used when build.py runs with FOOTER_MODE=short. Topic risk warnings move to
   the pages they relate to; the footer keeps regulatory status + what we do not
   regulate, at body size, close to Schema E's proportions. */
.legal-band--short .container > p { font-size: 1rem; line-height: 1.6; color: rgba(255,255,255,.9);
                                    max-width: 78ch; margin-bottom: .8rem; }
.legal-band--short .legal-links { margin-top: 1.25rem; font-size: .95rem; }

/* --- Header nav button -----------------------------------------------------
   Schema B's .main-nav is a flex row at its default align-items:stretch, so the
   pill stretched to the row height and its label sat off-centre. Centre the row
   and make the button centre its own label on both axes. */
.main-nav { align-items: center; }
.main-nav .btn { display: inline-flex; align-items: center; justify-content: center;
                 text-align: center; padding: .72rem 1.5rem; line-height: 1.2; }

/* --- Hero: teal italic accent + first-screen height -------------------------
   The <em> colour and the .label rule are Schema E's; both carried over here.

   Header + hero together fill exactly one viewport, so the next section starts
   just below the fold (soyc does the same). --hdr-h is the single source of
   truth: .header-inner uses it and the hero subtracts it, so changing the header
   height keeps the two in step. svh (small viewport height) is the mobile-safe
   unit — 100vh overshoots on phones because it ignores the browser chrome.
   The max() floor stops the hero collapsing on very short windows.            */
:root { --hdr-h: 5.7rem; }   /* fallback only; main.js measures the real header */
.header-inner { min-height: 5.6rem; }
/* The sister sites carry a 117px bar on a phone against this site's 91. 6.5rem
   is most of the way there and gives the larger logo room. It has to sit AFTER
   the line above, not beside the base rule at the top of the file: that one is
   a second declaration of the same property at equal specificity, so whichever
   comes last wins and a media query up there is simply ignored.
   --hdr-h is measured at runtime by assets/main.js, so the hero and the
   banners follow without a second constant to keep in step. */
@media (max-width: 54rem) { .header-inner { min-height: 6.5rem; } }
.hero h1 em { color: var(--teal); font-style: italic; font-weight: 400; }

/* Hero vertical rhythm scales with viewport HEIGHT, not just width, so the
   header+hero block lands on one screen across laptop sizes instead of
   overflowing. Content always wins: on very short windows the hero grows
   rather than clipping anything. */
.hero .hero-content { --hero-pad: clamp(1.1rem, 3vh, 3rem); padding-block: var(--hero-pad); }
/* Header + headline block = exactly one screen; the credentials row begins at the
   fold, so it reads as a cue to scroll rather than competing for first-screen space. */
.hero-grid {
  min-height: max(26rem, calc(100vh  - var(--hdr-h) - var(--hero-pad)));
  min-height: max(26rem, calc(100svh - var(--hdr-h) - var(--hero-pad)));
  align-content: center;
}
.hero h1 { margin-bottom: clamp(.4rem, 1.2vh, 1rem); }
.hero .lede { margin-bottom: clamp(.5rem, 1.4vh, 1rem); }
.hero-actions { margin-top: clamp(1rem, 2.6vh, 1.9rem); }
.credentials { margin-top: clamp(1.1rem, 3vh, 3.25rem); }
.credentials li { padding-block: clamp(.8rem, 2.2vh, 1.6rem) clamp(.9rem, 2.4vh, 1.8rem); }

/* PHONES AND SMALL TABLETS: trim the gap ABOVE the headline, and only that.
   The grid keeps its screen-high box and the credentials row keeps its place
   at the foot of it - the first attempt removed the reserved height outright,
   which closed every gap at once and made the hero read as busy.
   The box keeps its FULL screen, because that is what holds the credentials
   row at the fold - the rule the block above is built on. What changes is
   where the headline sits inside it: centring put ~290px of navy above the
   eyebrow, so below 54rem the block is aligned to the top behind a deliberate
   inset instead. The slack that used to sit above now falls below the pill,
   which is the scroll cue doing its job rather than a gap to close.
   Shrinking the box was tried first and rejected: it trimmed the gap above
   but lifted the credentials row into the first screen, which breaks the
   rule. */
@media (max-width: 54rem) {
  .hero-grid { align-content: start; padding-top: clamp(2.25rem, 13vh, 6rem); }
}

/* INNER-PAGE BANNERS, phones and tablets: the hero's rule applied to the rest
   of the site - header + banner = one screen, and what follows begins just
   below the fold.
   64rem, not the hero's 54rem, so an iPad Pro in portrait is included; above
   that the 424px banner is the composition desktop is built on.
   :not(.phead--strip) keeps the Insights index, the nine articles and the
   sitemap on their shallow strip. Those are deliberately thin, and a
   screen-high photograph in front of an article would undo the point of them.
   Top-aligned, not centred. Centring put 338px of empty banner above the
   breadcrumbs on an iPad portrait and 364px on a 10.9 - the taller the device
   the worse it got, because the slack grows with the screen while the text
   does not. The inset is the hero's, so the two agree. */
@media (max-width: 64rem) {
  .phead:not(.phead--strip) {
    min-height: calc(100vh  - var(--hdr-h));
    min-height: calc(100svh - var(--hdr-h));
    display: flex; align-items: flex-start;
  }
  .phead:not(.phead--strip) .container {
    width: 100%;
    padding-block: clamp(2.5rem, 12vh, 6.5rem) clamp(2.25rem, 2rem + 2vw, 3.5rem);
  }
}

/* Each article's "Important information", as the batch submitted to New Leaf
   carries it. Set apart from the article and quieter than it, but at body size
   - CW-WEB-10 requires warnings at body size on all devices, and this block is
   the article's own set. It is NOT the .risk treatment: a risk warning sits
   beside the benefit it qualifies, this is the standing notice at the foot. */
.article-info { margin-top: 2.5rem; padding-top: 1.5rem;
                border-top: 2px solid rgba(29,53,87,.22); }
.article-info h2 { font: 700 .78rem/1.2 var(--f-body); letter-spacing: .1em;
                   text-transform: uppercase; color: var(--navy); margin: 0 0 .9rem; }
.article-info p { font-size: 1rem; line-height: 1.55; color: var(--muted);
                  margin-bottom: .8rem; }
.article-info p:last-child { margin-bottom: 0; }

/* [9b] BRAND-COMPLIANCE TRIALS ----------------------------------------------
   Four findings from docs/04-brand-and-copy-audit.md, each built as something
   you can switch on in ?swap=1 and look at, rather than decide from a written
   description. All four are OFF by default: the selectors need an attribute on
   <body> that only the chooser writes, so a normal page load is untouched.
   A winner gets baked in as a constant in build.py, the way FOOTER_VARIANT and
   LEGAL_BANNER already are, and this block then loses that variant.          */

/* B-1 was trialled and REJECTED 30 Oct: Georgia was seen against Cormorant
   and the logotype face was preferred. The site keeps Cormorant Garamond and
   the departure from guidelines p.10 stands as a recorded decision, not an
   oversight. Nothing to toggle.                                            */

/* B-2, accepted 30 Oct in this scope and no wider. Guidelines p.10 ask for
   Roboto Light as body copy; Light was refused for body text, which is too
   hard to read at 16px, and accepted in the BANNER and the FOOTER. The
   footer's legal paragraphs are the exception inside the exception: they stay
   at 400, because they are already at 12px and are the one block a regulator
   reads. Roboto is a variable font, so Light costs no extra download. */
.hero,
.phead,
.site-footer { font-weight: 300; }
.hero .lede,
.phead .lede,
.crumbs,
.site-footer p,
.site-footer li,
.site-footer a { font-weight: 300; }
.legal,
.legal p,
.legal li { font-weight: 400; }

/* B-4, accepted 30 Oct. The watermark was a Cormorant "&", which guidelines
   p.5 forbids by name ("NEVER replace the ampersand with another font"). It
   is now the real mark, taken from the logo. */
/* Background image, not a CSS mask. A mask would be one file instead of two
   and would take its colour from --watermark, but it is also one more thing
   that can quietly render nothing - and it does exactly that in the headless
   browser used to check this, so it could be neither screenshotted nor
   verified. Two solid SVGs and an opacity are duller and certain. The opacity
   values are the alpha the glyph had: .06 navy on light, .055 white on dark. */
.watermark::before,
.phead--mark::before {
  content: "";
  display: block;
  width: clamp(10rem, 18vw, 17rem);
  aspect-ratio: 111.71 / 98.3;          /* the glyph's own bounding box */
  content: url("ampersand-navy.svg");   /* a replaced element, not a painted box */
  opacity: .06;
}
.watermark--dark::before,
.phead--mark::before {
  content: url("ampersand-light.svg");
  opacity: .055;
}
/* SIZED ON INK, NOT ON NOMINAL WIDTH. A type glyph is mostly empty em box,
   so the two cannot simply share a width. Measured at 1280: the Cormorant
   glyph covers 19,447px of ink and the brand mark matches that at 280px
   against the glyph's 332.8px box - 0.84x. Opacity is therefore unchanged
   from the glyph's, .06 navy on light and .055 white on dark. */
.watermark::before { width: clamp(8.4rem, 15vw, 14.3rem); }
.phead--mark::before { width: clamp(9.25rem, 22vw, 20rem); }
.phead--strip.phead--mark::before { width: clamp(5rem, 10vw, 7.5rem); }

/* B-5 is DONE, not a trial: accepted 30 Oct as indistinguishable from the
   Tailwind greys it replaced, so the tints are simply in the rules now - the
   --grey token at the top of the file, the header hairline, the .main-nav
   dividers, .steps and .faq. Nothing here to toggle.
   One correction to docs/04 found while testing: that audit says four greys
   were in use. It is three. #6B7280 is on .contact-form, and that class
   appears on NO page - the contact page links out to Fillout rather than
   carrying a form - so it is dead CSS, not a visible breach. It is left
   where it is rather than changed, because changing a rule nothing renders
   only makes the next person wonder what it affected.                      */
/* [10] FOOTER VARIANTS -------------------------------------------------------
   Three presentations of the SAME markup, so nothing about the approved wording
   or its order changes — only how it is laid out. Cycle them with ?swap=1 and
   bake the choice in with FOOTER_VARIANT in build.py.

     columns   three named groups side by side (default). Came out of looking at
               ten real New Leaf AR footers: named groups in columns is the
               pattern across that cohort.
     longform  full-width stacked paragraphs, headings dropped, same type size.
               The cork-co.com shape, kept at a size the approval is happy with.
     compact   as longform but smaller, which is what cork-co.com actually runs.
               SEE THE WARNING BELOW BEFORE CHOOSING THIS ONE.
   ------------------------------------------------------------------------- */

/* --- longform: one column, no group headings ------------------------------ */
body[data-footer="longform"] .legal-grid,
body[data-footer="compact"]  .legal-grid { display: block; }
body[data-footer="longform"] .legal-grid h3,
body[data-footer="compact"]  .legal-grid h3 { display: none; }
body[data-footer="longform"] .legal-grid p,
body[data-footer="compact"]  .legal-grid p { max-width: none; text-align: left;
                                             hyphens: none; margin-bottom: .45rem; }
body[data-footer="longform"] .legal-grid > div,
body[data-footer="compact"]  .legal-grid > div { margin-bottom: .45rem; }

/* --- compact: cork-co.com's actual scale ---------------------------------- *
   COMPLIANCE WARNING. The approval's format table says risk warnings display at
   body-text size on all devices, with no carve-out. The columns and longform
   variants run at .9rem (14.4px) and the client accepted that on 27 Oct 2026.
   This variant is 12px, which is 75% of body text, and it puts the FCA risk
   warnings there too. Do not ship it without putting it to Kim Luckhurst first. */
body[data-footer="compact"] .legal { font-size: 12px; }
body[data-footer="compact"] .legal-grid p { margin-bottom: .35rem; }

/* The chooser's own banner, so nobody forgets which variant they are looking at.
   Gated on the attribute EXISTING: once a variant is baked into build.py the body
   still carries data-footer but swap.js is not there to set the note, and
   content: attr(...) on a missing attribute is an empty string - which still
   renders the block and left a stray 16px gap above the legal text. */
body[data-footer] .legal[data-footer-note]::before {
  content: attr(data-footer-note); display: block; margin-bottom: 1rem;
  font: 700 .7rem/1.4 var(--f-body); letter-spacing: .08em; text-transform: uppercase;
  color: var(--teal); }

/* [11] DESIGN OPTIONS --------------------------------------------------------
   Alternatives to look at with ?swap=1 and bake in with the constants at the top
   of build.py. Both lockups sit in the markup; CSS decides which one shows, so
   switching is instant and needs no rebuild.
   ------------------------------------------------------------------------- */

/* --- header lockup: landscape (default) or the stacked portrait mark ------ */
.brand .logo-v { display: none; }
body[data-brand="portrait"] .brand .logo-h { display: none; }
body[data-brand="portrait"] .brand .logo-v { display: block;
    width: clamp(104px, 8vw + 28px, 140px); }
/* The strapline is cut to the stacked mark's width, which is much narrower, so
   justifying "Independent Financial Planning" across it would tear it apart. */
body[data-brand="portrait"] .brand-strap { text-align-last: auto; text-align: center;
    font-size: clamp(.6rem, .45vw + .32rem, .72rem); }

/* --- footer lockup -------------------------------------------------------- */
.ftr-logo.logo-v { display: none; }
body[data-footerlogo="portrait"] .ftr-logo.logo-h { display: none; }
body[data-footerlogo="portrait"] .ftr-logo.logo-v { display: block; width: 120px; }

/* --- sticky menu ---------------------------------------------------------- *
   .site-header is already position:relative with z-index 20, so sticky only
   needs the offset. The hero measures the real header height into --hdr-h at
   runtime (assets/main.js), which keeps working because the header still
   occupies its space in the flow. */
body[data-menu="sticky"] .site-header { position: sticky; top: 0; }
@media (prefers-reduced-motion: no-preference) {
  body[data-menu="sticky"] { scroll-behavior: smooth; }
}
/* An in-page #anchor would otherwise land underneath the sticky bar. */
body[data-menu="sticky"] :target { scroll-margin-top: 6rem; }

/* [12] COOKIE BANNER (CW-WEB-09) + COOKIE TABLE - 17 Nov 2026 ---------------
   Grav only: the static copy never emits the banner markup. Body size and
   ink, not small grey type - it carries approved wording. Both choices share
   .btn--secondary so Accept and Reject are equally prominent (ICO). It sits
   off the bottom edge and never covers more than its own box; nothing on the
   page is blocked while it waits for an answer. */
.cw-cookie { position: fixed; left: 16px; right: 16px; bottom: 16px; z-index: 9999;
  max-width: 42rem; margin-inline: auto; padding: 1.1rem 1.3rem 1.2rem;
  background: #fff; color: var(--ink); font-size: 1rem; line-height: 1.5;
  border: 1px solid rgba(29, 53, 87, .18); border-radius: 14px;
  box-shadow: 0 10px 30px rgba(29, 53, 87, .18); }
.cw-cookie[hidden], [data-cw-cookie-settings][hidden] { display: none; }
.cw-cookie p { margin: 0; }
.cw-cookie .cw-cookie-h { font-weight: 700; margin-bottom: .3rem; }
.cw-cookie-actions { display: flex; flex-wrap: wrap; align-items: center; gap: .6rem 1rem; margin-top: 1rem; }
.cw-cookie-actions .btn { padding: .75rem 1.25rem; font-size: .9rem; }
.cw-cookie-actions a { color: var(--navy); text-decoration: underline; text-underline-offset: .15em; }
@media (max-width: 479px) {
  .cw-cookie { left: 8px; right: 8px; bottom: 8px; padding: 1rem; }
  .cw-cookie-actions .btn { flex: 1 1 100%; }
}
.cookie-table { width: 100%; border-collapse: collapse; margin: 1rem 0 1.5rem; font-size: 1rem; }
.cookie-table th, .cookie-table td { text-align: left; vertical-align: top; padding: .6rem .75rem; border-bottom: 1px solid rgba(29, 53, 87, .15); }
.cookie-table th { font-weight: 700; }
@media (max-width: 599px) {
  .cookie-table thead { display: none; }
  .cookie-table tr { display: block; padding: .6rem 0; border-bottom: 1px solid rgba(29, 53, 87, .15); }
  .cookie-table td { display: block; border: 0; padding: .15rem 0; }
  .cookie-table td:first-child { font-weight: 700; }
}
