/* ============================================================================
   BLUME DESIGN SYSTEM v2
   ----------------------------------------------------------------------------
   Loaded AFTER each page's inline <style> block, so it wins on equal specificity.
   Where an inline rule sits inside a media query, the v2 rule is prefixed with
   `body ` to raise specificity and win regardless of source order.

   Scope: Batch 1 only (index, treatments, concerns, results, about, team,
   contact). The other ~280 pages are untouched and keep their inline CSS.

   Added 2026-08-27. Plan: output/website-batch1-design-plan-2026-08-27/
   ============================================================================ */

:root {
  --cream: #FDFBF7;
  --ink:   #1D1D1D;
  --sand:  #EDE7E0;
  --taupe: #676056;
  --bark:  #4A453D;
  --gold:  #C4A87C;
  --line:  rgba(29, 29, 29, 0.15);

  --sp-1: 8px;   --sp-2: 16px;  --sp-3: 24px;  --sp-4: 32px;
  --sp-5: 48px;  --sp-6: 64px;  --sp-7: 96px;  --sp-8: 128px;
}

/* ----------------------------------------------------------------------------
   1. MOTION — near zero, the hud position.
   The old build defaulted every content block to opacity:0 and waited for an
   IntersectionObserver. If JS is slow or fails the page renders blank, on a
   site where 93% of paid traffic is mobile. Content must not depend on JS.
   ---------------------------------------------------------------------------- */
.reveal,
.reveal--delay-1,
.reveal--delay-2,
.reveal--delay-3 {
  opacity: 1 !important;
  transform: none !important;
  transition: none !important;
}

/* Scroll-snap forced a slideshow that fought normal scrolling and trapped
   users on sections taller than the viewport. */
html {
  scroll-snap-type: none !important;
}
body .section,
body .hero,
body .split {
  scroll-snap-align: none !important;
}

@media (prefers-reduced-motion: reduce) {
  * { animation: none !important; transition: none !important; }
}

/* ----------------------------------------------------------------------------
   2. TYPE
   Base was 13.5px / weight 300 / letter-spacing 0.3px, on both desktop and
   mobile. Too small for a 35-55 audience, under the 16px iOS input-zoom
   threshold, and weight 300 at that size renders thin-grey on low-DPI Android.
   ---------------------------------------------------------------------------- */
body {
  font-size: 16px;
  font-weight: 400;
  line-height: 1.7;
  letter-spacing: 0;
}

body h1 {
  font-size: clamp(34px, 5vw, 56px);
  font-weight: 300;
  line-height: 1.15;
  letter-spacing: 0.02em;
}

body h2 {
  font-size: clamp(24px, 2.4vw, 28px);
  font-weight: 300;
  line-height: 1.4;
  letter-spacing: 0.02em;
}

body h3 {
  font-size: 19px;
  font-weight: 500;
  line-height: 1.5;
  letter-spacing: 0.01em;
}

/* Section prose. The old build was wildly inconsistent here: the homepage set
   .split__text to clamp(26px, 2.8vw, 38px) while interior pages used bare <p>
   inheriting the 13.5px base. Same component, 3x size difference between pages.
   One scale now. */
body .split__content p,
body .split__content li,
body .intro p {
  font-size: 19px;
  font-weight: 300;
  line-height: 1.65;
  letter-spacing: 0;
}

/* Split statement text. NOTE the selector: `body .split__content p` (0,1,2)
   out-specifies a bare `body .split__text` (0,1,1), so the plain class rule was
   DEAD on every `<p class="split__text">` and these blocks rendered at the 19px
   body size instead of the statement size. Matching the p explicitly fixes it.
   Size restored to the homepage's original clamp(26px, 2.8vw, 38px) (John,
   2026-08-28: the split sections read too small on desktop and left too much
   empty space). max-width lifted from 500px so the text fills the panel width. */
body .split__content p.split__text,
body p.split__text,
body .split__text {
  font-size: clamp(24px, 2.3vw, 32px);
  max-width: 34ch;
  font-weight: 300;
  line-height: 1.5;
  letter-spacing: 0.02em;
}

/* Eyebrow / label */
body .split__eyebrow,
body .hero__eyebrow,
body .locations__title,
body .footer__col-heading {
  font-size: 13px;
  font-weight: 500;
  line-height: 1.4;
  letter-spacing: 0.08em;
  text-transform: uppercase;
}

/* Nothing on the site drops below 13px. */
body .footer__bottom-links a,
body .footer__social a,
body .footer__trust,
body .breadcrumbs {
  font-size: 13px;
}

/* ----------------------------------------------------------------------------
   3. CTA SYSTEM
   One language sitewide. Wording stays "Book a date with us" (John, 2026-08-27).
   Zero radius: the pill shape was the one soft form in an otherwise hard-edged
   layout, and it read as a generic web button rather than as part of the brand.
   ---------------------------------------------------------------------------- */
body .footer__book-btn,
body .cta-banner__btn,
body .location-card__cta,
body .cta-section__btn {
  border-radius: 0;
  font-size: 15px;
  font-weight: 600;
  letter-spacing: 0.01em;
  box-shadow: none;
  transition: background 200ms ease, color 200ms ease;
}



/* Secondary CTA: circled chevron + label. The circle is one of the three places
   radius is allowed (chevron circles, and nothing else). */
body .split__link,
body .concern-list__link {
  font-size: 15px;
  font-weight: 600;
  letter-spacing: 0.01em;
  text-decoration: none;
}

body .split__link:hover,
body .concern-list__link:hover {
  text-decoration: underline;
  text-underline-offset: 4px;
}

body .circle-arrow {
  border-radius: 50%;
}

/* ----------------------------------------------------------------------------
   4. MATERIAL
   Hairline or flat colour-block change. No shadows, no gradients except hero
   scrims, no radius except chevron circles.
   ---------------------------------------------------------------------------- */
body .location-card,
body .reviews-band,
body .reg-practitioners,
body .faq__item,
body .concern-list__item {
  box-shadow: none;
}

body .reg-practitioners__box,
body .location-card {
  border-radius: 0;
}

/* ----------------------------------------------------------------------------
   5. HERO
   min-height, never fixed height with overflow:hidden (that clipped the
   homepage copy including Kia's AHPRA registration line). Scrim strengthened
   because headlines were colliding with the lit BLUME signage in the photos.
   ---------------------------------------------------------------------------- */
/* The homepage video hero is full-viewport, desktop and mobile. `svh` (smallest
   viewport height) is used so the hero fills the screen without any part sitting
   under the mobile URL bar. This matches the original build; do NOT reduce it.
   Scoped to .hero--video so it cannot affect the compact banner hero on
   contact.html (min-height: 38vh) or the 4:5 aspect-ratio image heroes on the
   other Batch 1 pages. */
body .hero--video {
  min-height: 100vh;
  min-height: 100svh;
  height: auto;
}

body .hero__overlay,
body .hero::after {
  background: linear-gradient(
    to bottom,
    rgba(29, 29, 29, 0.55) 0%,
    rgba(29, 29, 29, 0.28) 38%,
    rgba(29, 29, 29, 0.45) 100%
  );
}

/* ----------------------------------------------------------------------------
   6. LAYOUT SAFETY
   Sections grow to their content. This is the class of bug that clipped the
   homepage; it must not be reintroduced by any future section.

   NOTE: .hero carries BOTH `section` and `hero` classes, so it is excluded here.
   Without the :not() the hero collapses to zero height, because its video is
   absolutely positioned and contributes no intrinsic height. Do not remove.
   Never set `min-height: 0` on a section: it is not needed to prevent clipping
   (height:auto + overflow:visible is sufficient) and it breaks full-bleed heroes.
   ---------------------------------------------------------------------------- */
body .section:not(.hero),
body .split {
  height: auto;
  overflow: visible;
}

body .reviews-band {
  background: var(--ink);
}

/* ----------------------------------------------------------------------------
   7. PROOF LEDGER (P1) — the legal occupant of the review-panel slot.
   AHPRA guardrail 8: the rating and review COUNT are permitted as plain text
   only. No widget, no quotes, no link to or display of the reviews themselves.
   ---------------------------------------------------------------------------- */
.proof-ledger {
  background: var(--cream);
  padding: var(--sp-7) var(--sp-4);
}

.proof-ledger__inner {
  max-width: 1040px;
  margin: 0 auto;
  display: grid;
  grid-template-columns: repeat(4, 1fr);
  gap: 0;
}

.proof-ledger__item {
  padding: var(--sp-3) var(--sp-3) var(--sp-3) 0;
  border-right: 1px solid var(--line);
}

.proof-ledger__item:last-child {
  border-right: 0;
}

.proof-ledger__num {
  display: block;
  font-size: 48px;
  font-weight: 300;
  line-height: 1.1;
  letter-spacing: 0;
  color: var(--ink);
}

.proof-ledger__label {
  display: block;
  margin-top: var(--sp-1);
  font-size: 13px;
  font-weight: 500;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--taupe);
}

@media (max-width: 860px) {
  .proof-ledger__inner { grid-template-columns: repeat(2, 1fr); }
  .proof-ledger__item:nth-child(2n) { border-right: 0; }
  .proof-ledger__item:nth-child(-n+2) { border-bottom: 1px solid var(--line); }
  .proof-ledger__num { font-size: 38px; }
}

/* ----------------------------------------------------------------------------
   8. MOBILE
   93.2% of Google Ads spend and 94% of impressions. Treat as the primary case.
   ---------------------------------------------------------------------------- */
@media (max-width: 768px) {
  body { font-size: 16px; }

  body .split__content p,
  body .split__content li,
  body .intro p { font-size: 17px; }

  /* Must match the desktop rule's specificity (0,2,2) or it is dead. Mobile
     keeps a restrained statement size; the desktop clamp would floor at 26px
     here, which is too large for a 390px column. */
  body .split__content p.split__text,
  body p.split__text,
  body .split__text { font-size: 22px; max-width: 100%; }

  /* Tap targets */
  body .footer__book-btn,
  body .cta-banner__btn,
  body .location-card__cta { min-height: 48px; }
}

/* ----------------------------------------------------------------------------
   9. REGISTRATION LEDGER (P2 archetype) - practitioners as a designed object.
   Name + AHPRA reg stay in one row (B6: reg line adjacent to every name).
   ---------------------------------------------------------------------------- */
.reg-ledger {
  background: var(--cream);
  border-top: 1px solid var(--line);
  padding: var(--sp-7) var(--sp-4);
}
.reg-ledger__inner {
  max-width: 1040px;
  margin: 0 auto;
  display: grid;
  grid-template-columns: 5fr 7fr;
  gap: var(--sp-6);
  align-items: start;
}
.reg-ledger__head h2 {
  font-size: 28px;
  font-weight: 300;
  letter-spacing: 0.01em;
  margin: 0 0 var(--sp-2);
  color: var(--ink);
}
.reg-ledger__head p {
  font-size: 16px;
  font-weight: 300;
  line-height: 1.65;
  color: var(--taupe);
  max-width: 36ch;
  margin: 0;
}
.reg-ledger__rows { border-top: 1px solid var(--line); }
.reg-ledger__row {
  display: flex;
  align-items: baseline;
  gap: var(--sp-3);
  padding: var(--sp-3) 0;
  border-bottom: 1px solid var(--line);
}
.reg-ledger__idx {
  font-size: 12px;
  font-weight: 500;
  letter-spacing: 0.12em;
  color: var(--gold);
  min-width: 28px;
}
.reg-ledger__name {
  font-size: 19px;
  font-weight: 400;
  color: var(--ink);
  flex: 1;
}
.reg-ledger__reg {
  font-size: 12px;
  font-weight: 500;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--taupe);
  white-space: nowrap;
}
@media (max-width: 860px) {
  .reg-ledger__inner { grid-template-columns: 1fr; gap: var(--sp-4); }
  .reg-ledger__row { flex-wrap: wrap; row-gap: 4px; }
  .reg-ledger__reg { white-space: normal; width: 100%; padding-left: calc(28px + var(--sp-3)); }
}

/* ---- split photo fix 2026-09-21 (John: 'weird white gaps between each section on desktop')
   Two causes. (1) The photo was an inline <img>, so every half carried a text-baseline strip under it (8px of page
   background). (2) The photo half was a fixed square pinned to the top, so whenever the text half ran taller (About
   story +26px, Team +40px) a cream band showed under the photo. The photo now fills its half, whatever its height.
   Desktop only for (2): phones stack the halves and keep their 4:5 photo. */
body .split__image img { display: block; }
@media (min-width: 769px) {
  body .split { align-items: stretch; }
  body .split > .split__image { align-self: stretch; aspect-ratio: auto; min-height: 50vw; position: relative; overflow: hidden; }
  body .split > .split__image > img { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }
}