/*
 * Interior page template — hero, breadcrumbs, and the reading rhythm for
 * page content.
 *
 * The homepage is built from full-bleed section blocks and does not use most of
 * this; these rules are for pages whose body is ordinary editor content. The
 * one deliberate exception is the post card at the bottom of this file, which
 * the homepage News band and the Internships stories band share.
 */

/* ---------- page hero ---------- */

.vim-page-hero {
	position: relative;
	isolation: isolate;
	background-color: var(--teal-900);
	background-size: cover;
	/* Essential once the parallax script starts moving the position: the
	   default `repeat` tiles the photograph the moment it is nudged. */
	background-repeat: no-repeat;
	/*
	 * Framed above centre (Tom, 2026-08-24: the heroes "sit too high in the
	 * viewing window"). With `cover`, centring crops equally top and bottom,
	 * which on these photographs cut people's heads off — the subjects sit in
	 * the upper third. Biasing the window upward keeps faces in shot.
	 */
	background-position: center 28%;
	/*
	 * Taller than the original clamp(3rem, 6vw, 5.5rem) so more of the
	 * photograph is visible behind the title (Tom, 2026-08-24).
	 *
	 * The padding alone now carries the height: the breadcrumb is absolutely
	 * positioned, so unlike the first pass it contributes nothing to the box.
	 * Raising the clamp again keeps the hero at ~345px on a desktop viewport.
	 */
	padding: clamp(5rem, 11.5vw, 10.5rem) 2rem;
}

@media (max-width: 767px) {
	.vim-page-hero {
		padding-inline: 1.25rem;
	}
}

/*
 * Parallax is real motion now, driven by assets/parallax.js, not
 * `background-attachment: fixed` (Tom, 2026-08-24: "a true parallax where the
 * image passes more slowly behind the title").
 *
 * The background stays attached to the ELEMENT, which is what makes
 * `_vim_hero_focus` mean the same thing on every screen. `fixed` positioned it
 * against the viewport instead, so the visible slice moved with screen height
 * and the top ~15% of every photograph was permanently hidden behind the
 * header — that is what kept cutting faces off on some screens and not others.
 *
 * The script only nudges background-position-y, so with JavaScript off, a
 * frozen tab, or reduced motion the hero simply keeps its authored framing.
 */
.vim-page-hero--image {
	will-change: background-position;
}

/* Only images need darkening — the flat teal fallback is already dark enough
   for white text at 11.48:1, and an overlay would only muddy it. */
.vim-page-hero--image::before {
	content: "";
	position: absolute;
	inset: 0;
	background-color: color-mix(in srgb, var(--ink) 58%, transparent);
	z-index: -1;
}

.vim-page-hero__inner {
	max-width: var(--gb-container-width);
	margin-inline: auto;
	display: flex;
	flex-direction: column;
	align-items: center;
	row-gap: 1.25rem;
	text-align: center;
}

/*
 * The hero and its breadcrumb are siblings inside this wrapper — see
 * vim_render_page_hero() in inc/interior.php for why the crumb is not a child
 * of the section.
 *
 * The wrapper is only ever the positioning context; it adds no height of its
 * own, because on desktop the crumb inside it is out of flow.
 */
.vim-page-hero-wrap {
	position: relative;
}

/*
 * The breadcrumb sits at the true bottom-left of the hero (Tom, 2026-08-24):
 * flush to the section's bottom edge, not floated up inside its padding, with
 * its left edge on the content measure.
 *
 * It is taken out of the flow and pinned, because the hero's vertical padding
 * is what centres the title — anything left in that flow sits inside the
 * padding by definition.
 *
 * It stays FIRST in the markup, so a screen reader still meets the breadcrumb
 * before the page's h1, which is the conventional reading order.
 *
 * The horizontal padding is the trick that lines it up: whichever is larger of
 * the page gutter, or half the space left over once the content measure is
 * taken out. That puts the box exactly on the measure's left edge on wide
 * screens and keeps a sensible gutter on narrow ones.
 */
.vim-page-hero-wrap .vim-breadcrumbs {
	position: absolute;
	/* 10px clear of the bottom edge rather than flush against it — Tom's call. */
	inset: auto 0 10px 0;
	padding-inline: max(2rem, (100% - var(--gb-container-width)) / 2);
	background: none;
	/*
	 * 🚨 Required, and its absence is invisible to every measurement.
	 *
	 * .vim-page-hero is `position: relative` with `z-index: auto`, so it paints
	 * in the same layer as this absolutely positioned box — and it comes LATER
	 * in tree order, so it wins and covers the crumb completely. While the crumb
	 * was a CHILD of the section it sat inside that element's own stacking
	 * context and painted over its background; as a preceding SIBLING it does
	 * not, and the breadcrumb vanished from every desktop page on 2026-08-26.
	 *
	 * The geometry stays correct throughout — position, offsets and size all
	 * measure exactly as before — so computed style cannot detect this. Check it
	 * with document.elementFromPoint() over the crumb, or with a screenshot.
	 */
	z-index: 1;
}

/* The dark box hugs the crumbs rather than spanning the measure. */
.vim-page-hero-wrap .vim-breadcrumbs ol {
	width: max-content;
	max-width: 100%;
	justify-content: flex-start;
	background-color: var(--teal-900);
	padding: 0.5rem 0.9rem;
}

/*
 * A page with no featured image falls back to a flat --teal-900 band, and a
 * --teal-900 box on it would be invisible. --ink is the next step down the
 * same family, so the box still reads as a box.
 */
.vim-page-hero-wrap:not(.vim-page-hero-wrap--image) .vim-breadcrumbs ol {
	background-color: var(--ink);
}

/*
 * Mobile: the crumb comes out of the hero and sits below it (Tom, 2026-08-26).
 *
 * On a phone the hero is only ~196px tall against ~345px on a desktop, so a
 * 42px dark pill pinned to its bottom edge crowded the h1 and left the band
 * looking stuffed. Below the band it has room, and the page gets a clear
 * hero → breadcrumb → content rhythm.
 *
 * column-reverse, not a DOM change: the crumb is still first in the markup for
 * a screen reader, and is shown second. That is the same reading-order /
 * visual-order split the absolute positioning above already depends on.
 */
@media (max-width: 767px) {

	.vim-page-hero-wrap {
		display: flex;
		flex-direction: column-reverse;
	}

	/*
	 * Back into the flow. `inset: auto` alone is not enough — `position` has to
	 * be reset too, or the box stays out of flow and the wrapper collapses onto
	 * the hero with the crumb painted over the content below it.
	 */
	.vim-page-hero-wrap .vim-breadcrumbs {
		position: static;
		inset: auto;
		/* Matches .vim-section's mobile gutter, so the crumb's left edge lines
		   up with the first line of body copy underneath it. */
		padding: 0.9rem 1.25rem;
	}

	/*
	 * No pill down here. The box existed to hold white text off a photograph;
	 * on the page background it would be a dark slab floating above the
	 * content, and the white text inside it is the only reason it was needed.
	 */
	.vim-page-hero-wrap .vim-breadcrumbs ol,
	.vim-page-hero-wrap:not(.vim-page-hero-wrap--image) .vim-breadcrumbs ol {
		background-color: transparent;
		padding: 0;
		width: auto;
	}

	/*
	 * --ink rather than the white above: this row now sits on whatever the page
	 * background is, which is --white or --sand. Both give --ink well over 15:1,
	 * and the same value works on either without a second rule.
	 */
	.vim-page-hero-wrap .vim-breadcrumbs li,
	.vim-page-hero-wrap .vim-breadcrumbs a {
		color: var(--ink);
	}

	.vim-page-hero-wrap .vim-breadcrumbs a:hover,
	.vim-page-hero-wrap .vim-breadcrumbs a:focus {
		color: var(--teal-700);
	}
}

.vim-page-hero__title {
	color: var(--white);
	margin: 0;
}

/* ---------- breadcrumbs ---------- */

.vim-breadcrumbs ol {
	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	align-items: center;
	gap: 0.35rem 0.6rem;
	margin: 0;
	padding: 0;
	list-style: none;
	font-size: 1rem;
}

.vim-breadcrumbs li {
	display: flex;
	align-items: center;
	color: var(--white);
}

/* Separator drawn in CSS so it is never read out by a screen reader. */
.vim-breadcrumbs li + li::before {
	content: "";
	display: inline-block;
	width: 0.4rem;
	height: 0.4rem;
	margin-right: 0.6rem;
	border-top: 2px solid currentColor;
	border-right: 2px solid currentColor;
	transform: rotate(45deg);
	opacity: 0.65;
}

.vim-breadcrumbs a {
	color: var(--white);
	text-decoration: underline;
	text-underline-offset: 0.2em;
}

.vim-breadcrumbs a:hover,
.vim-breadcrumbs a:focus {
	color: var(--accent);
}

.vim-breadcrumbs [aria-current="page"] {
	opacity: 0.85;
}

/* ---------- interior content sections ---------- */

/*
 * One pattern shared by every interior page, so eleven pages do not each carry
 * their own copy of the same rules. Blocks reference these classes and keep
 * their own `css` attributes empty.
 */

.vim-section {
	padding-block: clamp(2.75rem, 5vw, 4.5rem);
	padding-inline: 2rem;
}

@media (max-width: 767px) {
	.vim-section {
		padding-inline: 1.25rem;
	}
}

/*
 * Two consecutive bands of the SAME colour should not pay the boundary twice.
 *
 * Between a white band and a sand one, the colour change marks the join, so a
 * full pad on each side reads correctly. Between two sand bands — /volunteer/
 * runs "You Have Questions?" straight into "Volunteer application" — there is
 * no colour change, so the two pads simply stack into ~144px of empty sand and
 * the pair reads as one band with a hole in the middle rather than as two
 * sections.
 *
 * Dropping the second band's top pad leaves one full gap at the join, which
 * matches the rhythm inside a section. Written as a same-class adjacency so it
 * holds anywhere the condition arises, rather than being patched per page.
 */
.vim-section--sand + .vim-section--sand,
.vim-section--teal + .vim-section--teal,
.vim-section:not(.vim-section--sand):not(.vim-section--teal)
	+ .vim-section:not(.vim-section--sand):not(.vim-section--teal) {
	padding-top: 0;
}

/* Alternating bands so a long page of prose does not read as one slab. */
.vim-section--sand {
	background-color: var(--sand);
}

.vim-section--teal {
	background-color: var(--teal-900);
}

.vim-section--teal :is(h2, h3, h4, p, li) {
	color: var(--white);
}

.vim-section__inner {
	max-width: var(--gb-container-width);
	margin-inline: auto;
}

.vim-section__heading {
	color: var(--teal-900);
	margin-bottom: 1rem;
}

.vim-section__subheading {
	color: var(--teal-900);
	margin-bottom: 0.5rem;
}

/* ---------------------------------------------------------------------------
 * Accordion
 *
 * One component, two uses: long forms behind a labelled toggle, and FAQ
 * sections (Tom, 2026-08-24 — "FAQs should live inside of accordions", "long
 * forms into a GP accordion, labelled", "accordions should be full width").
 *
 * It lives here rather than in forms.css because forms.css is only enqueued
 * when Forminator is active, and an FAQ has nothing to do with Forminator.
 * Form-specific rules — the field measure inside a panel, the stray empty
 * paragraphs wpautop leaves around a shortcode — stay in forms.css keyed to
 * `.vim-form-accordion`.
 *
 * The toggle is a full-width bar rather than a button pill because it opens a
 * panel rather than performing an action; it must not read as a submit button.
 *
 * GenerateBlocks Pro's runtime sets aria-expanded and adds
 * `.gb-accordion__item-open`. Nothing here should try to control open state.
 * ------------------------------------------------------------------------- */

.vim-accordion {
	margin-block: 1.5rem;
}

.vim-accordion .gb-accordion__item {
	border: 1px solid color-mix(in srgb, var(--teal-900) 28%, transparent);
	border-radius: 0.25rem;
	background-color: var(--white);
}

.vim-accordion .gb-accordion__item + .gb-accordion__item {
	margin-top: 0.5rem;
}

.vim-accordion .gb-accordion__toggle {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1rem;
	width: 100%;
	background-color: var(--sand);
	color: var(--teal-900);
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	font-weight: 800;
	text-align: left;
	border: 0;
	border-radius: 0.25rem;
	padding: 0.9rem 1.1rem;
	cursor: pointer;
}

.vim-accordion .gb-accordion__toggle:is(:hover, :focus) {
	background-color: color-mix(in srgb, var(--sand) 70%, var(--teal-900));
	color: var(--white);
}

.vim-accordion .gb-accordion__toggle:focus-visible {
	outline: 3px solid var(--accent);
	outline-offset: -3px;
}

/* Square off the bottom corners once the panel beneath is showing. */
.vim-accordion .gb-accordion__item-open .gb-accordion__toggle {
	border-bottom-left-radius: 0;
	border-bottom-right-radius: 0;
}

.vim-accordion .gb-accordion__toggle-icon svg {
	width: 1.15rem;
	height: 1.15rem;
	display: block;
}

.vim-accordion .gb-accordion__content > * {
	padding: 1.25rem 1.1rem 1.5rem;
}

/*
 * An FAQ answer is running prose, so it keeps a reading measure even though the
 * panel around it runs the full width of the band.
 */
.vim-accordion .gb-accordion__content .vim-section__copy,
.vim-accordion .gb-accordion__content .vim-list {
	max-width: 70ch;
}

/* ---------------------------------------------------------------------------
 * Get Involved — section icons
 *
 * The same treatment as the homepage stat band: a white line icon centred in a
 * flat coloured circle, taking the homepage's colour order (plum, teal-700,
 * green-600, teal-500) even though this page has four icons and the band has
 * five (Tom, 2026-08-24).
 *
 * Smaller than the band's 156px because these sit above a heading rather than
 * carrying a headline figure of their own.
 *
 * The icons are aria-hidden in the markup — each one is immediately followed by
 * a heading saying the same word, so alt text would announce every section
 * twice.
 * ------------------------------------------------------------------------- */

.vim-involve__icon {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 112px;
	height: 112px;
	aspect-ratio: 1;
	border-radius: 50%;
	margin-bottom: 1.5rem;
}

@media (max-width: 767px) {

	.vim-involve__icon {
		width: 88px;
		height: 88px;
	}
}

/*
 * The supplied files carry no fill of their own, so the icon takes this one.
 * Percentage sizing keeps the optical weight matched across four artboards
 * drawn at different viewBox scales.
 */
.vim-involve__icon svg {
	width: 52%;
	height: 52%;
	fill: var(--white);
}

.vim-involve__icon--0 {
	background-color: var(--plum);
}

.vim-involve__icon--1 {
	background-color: var(--teal-700);
}

.vim-involve__icon--2 {
	background-color: var(--green-600);
}

.vim-involve__icon--3 {
	background-color: var(--teal-500);
}

/*
 * Bottom-align the button in every Get Involved box, so the four calls to
 * action sit on one line across each row of the 2-up grid instead of floating
 * wherever their copy happens to end. Measured before: 26px apart in row 1.
 *
 * 🚨 This works only because the Donate box's three policy links were moved
 * ABOVE its button (2026-08-25), making the button the last child of all four
 * boxes. While the links came last, no amount of auto margin could align the
 * buttons — box 4's button sat one links-height higher than its neighbour's by
 * construction, and pinning the links to the bottom instead just moved the
 * mismatch. **If those links are ever moved back below the button, this rule
 * silently stops aligning that box.**
 *
 * Row 2 happened to be aligned already, by coincidence: box 3's spare space
 * equalled box 4's links height. Any copy edit would have broken it.
 *
 * ⚠️ The spare height goes into the COPY (`flex-grow: 1`), not into an auto
 * margin on the button. `margin-top: auto` on the button would work for boxes
 * that end with one, but in the Donate box it would open the free space
 * BETWEEN the links and the button and strand the fine print in mid-air — and
 * putting an auto margin on both splits the free space in two and does it
 * twice. Growing the copy pushes the links-and-button group down together.
 */
/*
 * 🚨 The copy does NOT grow, and the button is NOT pinned to the bottom.
 *
 * Earlier on 2026-08-25 it was: `flex-grow: 1` on the copy pushed each button
 * down so the four aligned across a row. Tom then asked for the opposite —
 * *"keep the content with the text and center the content vertically in the
 * box"* — because bottom-pinning opened a visible hole between a short box's
 * copy and its button.
 *
 * The centring itself lives in each box's own `styles` (justifyContent), not
 * here, so the client can change it in the editor. **Do not reintroduce
 * `flex-grow` here to "fix" the button alignment** — the two cannot both be
 * true, and centring is the one that was asked for.
 */

/*
 * 🚨 Spacing inside a box is the flex `row-gap` ALONE (Tom, 2026-08-25:
 * "tighten up the spacing between header content and button").
 *
 * The box is a flex column with `row-gap: 1.25rem` in its block styles, but
 * every child also arrived carrying its own `margin-bottom` — 24px on the icon,
 * 16px on the heading, 20px on the copy. Those do not collapse in a flex
 * container, they ADD to the gap, so the real spacing was 44 / 36 / 40px and
 * uneven with it. Measured, not guessed.
 *
 * Zeroing the margins here leaves one number in charge, in the block's own
 * styles where the client can change it. **Do not "fix" tight spacing by
 * putting a margin back on a child** — it will silently double again.
 */
.vim-involve__box > .vim-involve__icon,
.vim-involve__box > .vim-section__heading,
.vim-involve__box > .vim-section__copy,
.vim-involve__box > .vim-policy-links {
	margin-bottom: 0;
}

/*
 * Box headings step down from --fs-display (28-38px) to --fs-heading (22-26px)
 * (Tom, 2026-08-25: "reduce the header size on those boxes as well").
 *
 * ⚠️ Size only — the elements stay `h2`. The homepage outline depends on the
 * level, not the size, and dropping these to h3 would put an h3 before the
 * page's first h2. Same reasoning as the four-column band on the front page,
 * which is 28px by explicit CSS while remaining h2.
 */
.vim-involve__box .vim-section__heading {
	font-size: var(--fs-heading, 1.625rem);
}

/*
 * The policy links under the Donations box — Code of Ethics, Donor Bill of
 * Rights, Privacy Policy.
 *
 * They were `.gbp-button--secondary`, which stacked three outlined buttons under
 * the Donate button and made the box read as four equal calls to action. They
 * are secondary reference links, so they are small text links now (Tom,
 * 2026-08-25). Centring lives on the row block's own styles, not here.
 *
 * ⚠️ This rule is required, not cosmetic: the site's prose-link rule is
 * `.entry-content a:not([class*="gb-"])`, which deliberately skips block-built
 * links so it cannot underline buttons. These anchors carry `gb-text`, so
 * without something here they would render with no underline and no link colour
 * at all.
 */
.vim-policy-links a {
	font-size: 16px;
	color: var(--teal-700);
	text-decoration: underline;
	text-underline-offset: 0.15em;
}

.vim-policy-links a:hover,
.vim-policy-links a:focus {
	color: var(--accent-dark);
}

/*
 * Body copy fills its container (Tom, 2026-08-24: text "seems to be constrained
 * … not filling the page").
 *
 * It previously carried max-width: 70ch, a reading measure. That is why a
 * full-width section's paragraph stopped around 810px while the grid beneath it
 * ran the full 1400px, which reads as a hard wrap rather than a choice. Inside
 * the two-column media rows nothing changes — the column already sets the width.
 */
.vim-section__copy {
	color: var(--body);
	margin-bottom: 1.25rem;
}

.vim-section__copy:last-child {
	margin-bottom: 0;
}

/* Media + text pairs, as on Our Services. */
/*
 * ⚠️ The alternating rows' GRID is not defined here.
 *
 * It lives in each row block's own `styles` object, so GenerateBlocks renders
 * real grid controls in the editor and the client can change the column split,
 * the gap or which side the image sits on (Tom, 2026-08-24: "be sure when you
 * do these alternating image layouts that we are using a GP container with a GB
 * grid within it"). Defining it here as well would give the row two sources of
 * truth, and the one in the stylesheet would be invisible to whoever is editing.
 *
 * The mirroring works the same way: the reversed rows carry `order: 2` on the
 * figure block above 861px, rather than a `.vim-media--reverse` class.
 *
 * What stays here is the image's appearance, which is not layout.
 */

.vim-media img {
	width: 100%;
	height: 100%;
	max-height: 420px;
	object-fit: cover;
	display: block;
	border-radius: 0.25rem;
}

.vim-subsection + .vim-subsection {
	margin-top: 2rem;
}

.vim-list {
	color: var(--body);
	padding-left: 1.35em;
	margin-bottom: 1.25rem;
}

.vim-list li + li {
	margin-top: 0.5em;
}

/*
 * Tighter list indent on phones (Tom, 2026-10-27: "Decrease the indent of the
 * bullet lists on mobile").
 *
 * GeneratePress gives every ul/ol `margin: 0 0 1.5em 3em` in main.min.css, and
 * nothing here overrode the 3em, so a list sat ~3em + 1.35em in from the copy
 * above it — about 78px on a 390px screen. Below 768px the margin goes and the
 * bullet hangs in a 1.25em padding instead, so the text lines up close to the
 * paragraph edge. Desktop is untouched.
 *
 * Written as the complement of (min-width: 768px), like hero.css, so a
 * fractional viewport such as 767.5px cannot fall between two queries.
 */
@media not all and (min-width: 768px) {
	.vim-list,
	.entry-content > :is(ul, ol),
	.vim-accordion .gb-accordion__content :is(ul, ol) {
		margin-left: 0;
		padding-left: 1.25em;
	}

	.vim-list :is(ul, ol),
	.entry-content li > :is(ul, ol) {
		margin-left: 1em;
	}
}

/*
 * Data tables — currently the income / FPL chart on Eligibility.
 *
 * A core/table block, because this is real tabular data and GenerateBlocks'
 * element tagName enum has no `table`. Row headers carry scope="row" so the
 * family size is announced with each figure rather than read as a bare number.
 */

.vim-table {
	max-width: 34rem;
	margin-inline: 0;
}

/*
 * The cap above exists to stop four short numeric columns stretching across the
 * full 1400px measure. Inside the Eligibility page's two-column layout the
 * chart is already constrained by its own grid column, so the cap does nothing
 * but leave a ragged gap down the right-hand edge.
 */
.gb-element-vimelgchart .vim-table {
	max-width: none;
}

.vim-table table {
	width: 100%;
	border-collapse: collapse;
}

.vim-table th,
.vim-table td {
	padding: 0.6rem 0.9rem;
	text-align: left;
	border: 1px solid color-mix(in srgb, var(--teal-900) 22%, transparent);
}

.vim-table thead th {
	background-color: var(--teal-900);
	color: var(--white);
	font-weight: 800;
}

.vim-table tbody th {
	background-color: var(--sand);
	font-weight: 800;
	width: 9rem;
}

.vim-table figcaption {
	margin-top: 0.6rem;
	font-size: var(--fs-small, 0.875rem);
	color: var(--body-alt);
}

/*
 * Staff directory cards.
 *
 * ⚠️ The grid is NOT here — it is on the container block's `styles`, three
 * across with the last row centred, so it is editable in the block editor. See
 * the note on the alternating rows above; same rule, same reason.
 *
 * What stays here is the appearance of a card.
 */

.vim-staff__member img {
	width: 100%;
	aspect-ratio: 1;
	object-fit: cover;
	object-position: top center;
	display: block;
	border-radius: 0.25rem;
	margin-bottom: 1rem;
}

/* Someone with no photo still gets a card the same shape as the others. */
.vim-staff__placeholder {
	width: 100%;
	aspect-ratio: 1;
	border-radius: 0.25rem;
	margin-bottom: 1rem;
	background-color: color-mix(in srgb, var(--teal-900) 12%, transparent);
}

.vim-staff__name {
	color: var(--teal-900);
	font-size: var(--fs-lead, 1.25rem);
	font-weight: 800;
	margin-bottom: 0.15rem;
}

.vim-staff__role {
	color: var(--muted);
	margin-bottom: 0.5rem;
}

.vim-staff__contact {
	color: var(--body);
	font-size: 1rem;
	margin-bottom: 0;
}

.vim-staff__contact a {
	color: var(--teal-700);
	text-decoration: underline;
}

/* A boxed aside, e.g. "What to Bring to Screening Appointment". */
.vim-callout {
	background-color: var(--white);
	border-left: 5px solid var(--accent);
	padding: clamp(1.5rem, 3vw, 2.25rem);
	border-radius: 0.25rem;
}

/* ---------- post card ---------- */

/*
 * Shared by the homepage News band and the Internships success-stories band.
 *
 * These rules used to live in the homepage section's own `css` attribute, which
 * GenerateBlocks writes into uploads/generateblocks/style-39740.css — a
 * per-page file. That made them unavailable to any other page, so the second
 * band would have needed a duplicate set under a different class name. One
 * definition here instead; the homepage block's copy was removed in the same
 * change so there is no second source of truth.
 */
.vim-news-card {
	background-color: var(--white);
	display: flex;
	flex-direction: column;
	height: 100%;
	overflow: hidden;
}

/*
 * Fixed 300px band. min- and max-height are both set, not just height: the
 * image is a flex item in a column card, so a bare height is still a shrinkable
 * basis — a card whose title wraps to three lines would squash its own image
 * and break alignment across the row. object-fit keeps the crop centred.
 */
.vim-news-card img {
	width: 100%;
	height: 300px;
	min-height: 300px;
	max-height: 300px;
	object-fit: cover;
	display: block;
}

.vim-news-card__body {
	padding: 1.75rem;
	display: flex;
	flex-direction: column;
	row-gap: 0.65rem;
}

.vim-news-card__title {
	font-size: var(--fs-heading, 1.75rem);
	font-weight: 600;
	line-height: 1.25;
	margin-bottom: 0;
	color: var(--muted);
}

/*
 * Card titles carry no underline at rest; the underline is the hover
 * affordance (Tom, 2026-08-25: "underline on hover for link titles").
 *
 * 🚨 Specificity, and why the previous version of this rule never did anything.
 * The prose-link rule further down this file is
 * `.entry-content a:not([class*="gb-"])`, which scores (0,2,1) — `:not()` takes
 * the specificity of its argument, and `[class*="gb-"]` is an attribute
 * selector. The old selector here was `.vim-news-card__title a`, only (0,1,1),
 * so it LOST: every card title on the site — the homepage News band included —
 * rendered underlined and in the prose link colour, and had done since the
 * component was written. Scoping to `.entry-content` and repeating the `:not()`
 * takes this to (0,3,1), which wins outright rather than depending on source
 * order.
 *
 * The card-title anchors are generated by the query loop and carry no class of
 * their own, which is exactly why the prose rule catches them at all.
 *
 * ⚠️ The original rule also set `color: var(--muted)` at rest. That has never
 * applied, so adopting it now would change every card title on the site from
 * the teal link colour to a warm grey — a bigger change than was asked for. The
 * rest colour is deliberately left alone; only the hover darkens.
 */
.entry-content .vim-news-card__title a:not([class*="gb-"]) {
	text-decoration: none;
}

.entry-content .vim-news-card__title a:not([class*="gb-"]):hover,
.entry-content .vim-news-card__title a:not([class*="gb-"]):focus {
	color: var(--teal-900);
	text-decoration: underline;
}

.vim-news-card__date {
	font-style: italic;
	color: var(--teal-700);
	font-size: var(--fs-body, 1.125rem);
	margin-bottom: 0;
}

.vim-news-card__excerpt {
	color: var(--body);
	font-size: var(--fs-body, 1.125rem);
	line-height: 1.55;
	margin-bottom: 0;
}

/* ---------------------------------------------------------------------------
 * Donate page tabs
 *
 * GenerateBlocks Pro's tabs block, styled as a row of buttons (Tom,
 * 2026-08-25: "I'd like to use GP button tabs with personal donation as the
 * default … but in the style of the new site"). The live vim-clinic.org donate
 * page is tabbed, so this restores that shape.
 *
 * ⚠️ The plugin's own CSS does the SHOWING AND HIDING — `.gb-tabs__item`
 * is `display:none` until it gains `.gb-tabs__item-open`. Nothing here may set
 * `display` on a panel, or a closed tab becomes visible and every panel stacks.
 *
 * The current button is marked with `.gb-block-is-current`, added by the
 * plugin's PHP at render and moved by its JS on click. Do not invent a class
 * for it.
 * ------------------------------------------------------------------------- */

.vim-tabs__menu {
	display: flex;
	flex-wrap: wrap;
	gap: 0.6rem;
	margin-bottom: 2.5rem;
}

/*
 * 🚨 There is deliberately NO reading-measure cap on tab panels or on
 * `.vim-prose`.
 *
 * One was added on 2026-08-25 — 68ch, because /donate/'s paragraphs ran the
 * full 1400px and one was 395 characters on a single line — and Tom removed it
 * the same day: *"also make it all 100% width on that page"*. The class hooks
 * are left in the markup so a cap can be reinstated in one rule if that is ever
 * wanted, but **do not reintroduce it as a "fix" for long lines** — it is a
 * decision that has already been made the other way.
 */

/*
 * These are real `<button>` elements, so the browser's own control styling has
 * to be reset before anything else lands — font, colour and background do not
 * inherit into a button.
 */
.vim-tabs__menu .vim-tab {
	appearance: none;
	border: 1px solid color-mix(in srgb, var(--teal-900) 30%, transparent);
	border-radius: 2rem;
	background-color: transparent;
	padding: 0.65rem 1.4rem;
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	font-weight: 800;
	line-height: 1.2;
	color: var(--teal-900);
	cursor: pointer;
	transition: background-color 0.15s ease, color 0.15s ease;
}

.vim-tabs__menu .vim-tab:is(:hover, :focus-visible) {
	background-color: var(--sand);
}

.vim-tabs__menu .vim-tab:focus-visible {
	outline: 3px solid var(--accent);
	outline-offset: 2px;
}

/*
 * The open tab: --ink on --accent, 7.52:1. White on the accent is 2.09:1 and
 * fails, so the text darkens and never the teal — settled site-wide.
 *
 * ⚠️ Colour is not the only signal. The plugin also sets `aria-selected` on
 * these buttons, so the current tab is announced as well as seen.
 */
.vim-tabs__menu .vim-tab.gb-block-is-current {
	background-color: var(--accent);
	border-color: var(--accent);
	color: var(--ink);
}

/*
 * On a sand band the resting tabs would otherwise sit on their own colour, so
 * the hover fill flips to white to stay visible.
 */
.vim-section--sand .vim-tabs__menu .vim-tab:is(:hover, :focus-visible) {
	background-color: var(--white);
}

/* ---------------------------------------------------------------------------
 * Category filter — News / Events / Success Stories
 *
 * Sits above the grid on the blog home and on every category archive. Tom's
 * 2026-08-25 restructure made category the meaningful split, and this is how a
 * reader reaches the three feeds: the blog home is "News and Events" and the
 * archives are its children at /news-and-events/<slug>/.
 * ------------------------------------------------------------------------- */

.vim-cat-filter {
	margin-bottom: 2.5rem;
}

.vim-cat-filter ul {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5rem;
	list-style: none;
	margin: 0;
	padding: 0;
}

/*
 * 🚨 These selectors must NOT be scoped to `.entry-content`, and that is the
 * opposite of every other link rule in this file.
 *
 * The competing prose rule is `.entry-content a:not([class*="gb-"])` at
 * (0,2,1), so elsewhere the trick is to scope INTO `.entry-content` and win.
 * Here it backfires: the filter renders inside a GeneratePress Element on the
 * blog home and the archives, where there is **no `.entry-content` wrapper at
 * all** — so a scoped rule matches nothing and the chips rendered as bare
 * teal-700 text.
 *
 * `.vim-cat-filter ul li a:not(…)` reaches (0,2,3) on element count alone,
 * which beats the prose rule wherever that rule does apply, and still works
 * where it does not.
 */
.vim-cat-filter ul li a:not([class*="gb-"]) {
	display: inline-block;
	padding: 0.5rem 1.1rem;
	border: 1px solid color-mix(in srgb, var(--teal-900) 30%, transparent);
	border-radius: 2rem;
	font-size: var(--fs-small, 0.875rem);
	font-weight: 800;
	letter-spacing: 0.03em;
	text-transform: uppercase;
	color: var(--teal-900);
	text-decoration: none;
	background-color: transparent;
}

.vim-cat-filter ul li a:not([class*="gb-"]):is(:hover, :focus) {
	background-color: var(--sand);
	color: var(--teal-900);
	text-decoration: none;
}

/*
 * The current filter is --ink on --accent: 7.52:1. White on the accent is
 * 2.09:1 and fails — the text darkens, never the teal.
 *
 * ⚠️ Colour is not the only signal. The current item also carries
 * `aria-current="page"`, so it is announced as well as seen.
 */
.vim-cat-filter ul li a.is-current:not([class*="gb-"]) {
	background-color: var(--accent);
	border-color: var(--accent);
	color: var(--ink);
}

/* ---------------------------------------------------------------------------
 * Search results
 *
 * Elements 46654 (hero) and 46649 (loop). The hero is now just
 * [vim_page_hero], so search gets the same flat --teal-900 band, centred title
 * and padding as every other page.
 *
 * The starter's results were a bare column of linked titles with an arrow —
 * no date, no excerpt, and no way to tell a page from a patient story. A
 * result you cannot judge without clicking is barely a result.
 * ------------------------------------------------------------------------- */

.vim-search-results {
	max-width: 46rem;
	margin-inline: auto;
}

.vim-search-result + .vim-search-result {
	margin-top: 2rem;
	padding-top: 2rem;
	border-top: 1px solid color-mix(in srgb, var(--teal-900) 15%, transparent);
}

.vim-search-result__title {
	font-size: var(--fs-heading, 1.625rem);
	line-height: 1.25;
	margin-bottom: 0.4rem;
	color: var(--teal-900);
}

/*
 * ⚠️ Scoped past `.entry-content a:not([class*="gb-"])`, which scores (0,2,1)
 * because :not() takes the specificity of its argument and `[class*=]` is an
 * attribute selector. An unscoped rule here ties at best and loses on source
 * order — the same trap that left every news card title underlined for weeks.
 *
 * The loop generates these anchors and they carry no class, so `:not()` is
 * satisfied and the rule has to out-score it rather than dodge it.
 */
.entry-content .vim-search-result__title a:not([class*="gb-"]) {
	color: var(--teal-900);
	text-decoration: none;
}

.entry-content .vim-search-result__title a:not([class*="gb-"]):is(:hover, :focus) {
	color: var(--accent-dark);
	text-decoration: underline;
}

/*
 * There is deliberately no `__meta` rule. Search returns pages as well as
 * posts, and a page's publish date here is a build artefact — every one reads
 * "August 23, 2026", the day the local build created them. A date line was
 * built, seen to state something false, and removed.
 */
.vim-search-result__excerpt {
	color: var(--body);
	line-height: 1.55;
	margin-bottom: 0;
}

/*
 * The core/search block on the empty-results page. Left to itself it renders a
 * browser-default input and a near-black button, which is the one control on
 * the page a visitor who found nothing actually needs to use.
 *
 * Scoped to `.vim-no-results` on purpose: the header's search is
 * GeneratePress's own modal, styled elsewhere, and a bare `.wp-block-search`
 * rule would reach into it.
 */
.vim-no-results .wp-block-search__label {
	font-weight: 800;
	color: var(--teal-900);
	margin-bottom: 0.5rem;
}

.vim-no-results .wp-block-search__input {
	border: 1px solid color-mix(in srgb, var(--teal-900) 35%, transparent);
	border-radius: 0.25rem 0 0 0.25rem;
	padding: 0.7rem 0.9rem;
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	color: var(--body);
	background-color: var(--white);
}

.vim-no-results .wp-block-search__input:focus-visible {
	outline: 3px solid var(--accent);
	outline-offset: -1px;
}

/*
 * Matches the primary button: --ink on --accent, which is 7.52:1. White on the
 * accent is 2.09:1 and fails — the text darkens, never the teal. That decision
 * is settled site-wide; do not re-lighten this.
 */
.vim-no-results .wp-block-search__button {
	background-color: var(--accent);
	color: var(--ink);
	border: 0;
	border-radius: 0 0.25rem 0.25rem 0;
	padding: 0.7rem 1.4rem;
	font-family: inherit;
	font-size: var(--fs-body, 1rem);
	font-weight: 800;
	cursor: pointer;
}

.vim-no-results .wp-block-search__button:is(:hover, :focus) {
	background-color: var(--accent-dark);
}

.vim-no-results .vim-list {
	margin-top: 1.75rem;
}

/* ---------------------------------------------------------------------------
 * Single post
 *
 * Element 29810. The hero, breadcrumbs and h1 all come from [vim_page_hero],
 * the same one the interior pages use — posts were added to
 * vim_should_render_page_hero() on 2026-08-25 rather than given a second hero.
 *
 * ⚠️ The article's MEASURE lives in the block's own `styles` (46rem), not here,
 * so the client can change it in the editor. What is here is appearance.
 * ------------------------------------------------------------------------- */

.vim-post__meta {
	font-style: italic;
	color: var(--teal-700);
	font-size: var(--fs-body, 1rem);
	margin-bottom: 2rem;
	padding-bottom: 1.25rem;
	border-bottom: 1px solid color-mix(in srgb, var(--teal-900) 15%, transparent);
}

/* The band that holds the cards. The grid goes on the looper itself — anything
   inside a looper repeats once per post, so a grid div in there would yield N
   one-column grids instead of one N-column grid. */
.vim-story-grid {
	display: grid;
	grid-template-columns: repeat(3, 1fr);
	gap: 1.5rem;
}

@media (max-width: 1023px) {
	.vim-story-grid {
		grid-template-columns: repeat(2, 1fr);
	}
}

@media (max-width: 639px) {
	.vim-story-grid {
		grid-template-columns: 1fr;
	}
}

/* ---------- grantor logo wall ---------- */

/*
 * Logos supplement the grantor name list, they do not replace it: not every
 * funder has supplied one, and a pure logo wall would leave those unnamed and
 * invisible to search and screen readers. Each logo carries its organisation
 * name as alt text.
 *
 * The tiles are white cards because the supplied files have mixed backgrounds
 * (white, light blue, transparent) — without a card they read as ragged boxes
 * on the sand band.
 */
/*
 * Five across, with any short final row centred (Tom, 2026-08-25).
 *
 * Flex rather than grid: a grid's last row always starts at column 1, so eleven
 * logos in five columns would leave a lone item hard against the left edge.
 * Flex with `justify-content: center` and a fixed basis centres the remainder
 * for free. Same technique as the staff directory.
 *
 * The gap is a custom property because the basis has to subtract it four times;
 * repeating the clamp() inside the calc() would drift if either were edited.
 */
.vim-logo-wall {
	--logo-gap: clamp(1.5rem, 3vw, 2.5rem);

	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	gap: var(--logo-gap);
	list-style: none;
	margin: 0 0 2.5rem;
	padding: 0;
}

.vim-logo-wall li {
	flex: 0 1 calc((100% - 4 * var(--logo-gap)) / 5);
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 0.7rem;
	text-align: center;
}

@media (max-width: 1024px) {

	.vim-logo-wall li {
		flex-basis: calc((100% - 2 * var(--logo-gap)) / 3);
	}
}

@media (max-width: 640px) {

	.vim-logo-wall li {
		flex-basis: calc((100% - var(--logo-gap)) / 2);
	}
}

/*
 * `mix-blend-mode: multiply` drops the white box out of each logo (Tom: "multiply
 * logos on background to remove white boxes"). Most of these are JPEGs with a
 * baked-in white field, which is why they previously needed a white tile behind
 * them to look deliberate.
 *
 * ⚠️ Multiply only disappears WHITE. It works here because the band is --sand;
 * on a dark band it would darken the logos into mud. If this component is ever
 * used on --teal-900, the logos need transparent PNGs instead.
 *
 * A fixed height rather than max-height so every logo occupies the same band and
 * the captions below them line up across the row.
 */
/*
 * ⚠️ Scoped to .entry-content deliberately. The reading-rhythm block further
 * down this file sets `.entry-content :is(img, video) { height: auto }`, which
 * scores (0,1,1) — `:is()` takes the specificity of its strongest argument, a
 * type selector. A bare `.vim-logo-wall img` ties it at (0,1,1) and LOSES on
 * source order, so the fixed band silently did nothing and the wall rendered
 * ragged, logos running from 42px to 268px tall.
 */
.entry-content .vim-logo-wall img {
	width: auto;
	max-width: 100%;
	height: 90px;
	object-fit: contain;
	display: block;
	mix-blend-mode: multiply;
}

/*
 * All eleven current logos survive multiply — checked by compositing each onto
 * --sand and measuring the difference, rather than by eye, because they lazy-load
 * and an early screenshot makes them look missing when they are merely late.
 *
 * ⚠️ Rotary District 5110 is the one to watch: its logo carries a solid pale-BLUE
 * field, and multiply only erases white. That tile stays visible and cannot be
 * blended away — it needs a transparent replacement file to match the others.
 */

.vim-logo-wall__name {
	margin: 0;
	font-size: 0.875rem;
	line-height: 1.35;
	color: var(--body);
}

/*
 * The grantors with no logo. A centred comma-separated run rather than a second
 * bulleted column, so they read as part of the same acknowledgement rather than
 * as a lesser list (Tom, 2026-08-25).
 */
/*
 * Grantors with no logo — a tile of medium centred text in the same wall
 * (Tom, 2026-08-25: "for missing logos you can use medium sized centered text
 * as in the example"). The 2022 composite did exactly this for N.B. Giustina,
 * Newburn and the Coeta and Donald Barker Foundation.
 *
 * ⚠️ These tiles carry the name ONCE. A logo tile is image + caption, so
 * giving a text tile both a name and a caption would print it twice.
 *
 * The 90px height is the logo band's height, so a text tile's baseline block
 * occupies the same slot as its neighbours' artwork and the captions below
 * still line up across a row.
 *
 * `.vim-grantor-names` — the comma-separated run this replaces — was removed in
 * the same pass. It only ever existed because twelve grantors had no logo; with
 * the names in the wall there is nothing left for it to hold, and as a
 * single-name paragraph it read as a stray caption for the logo above it.
 */
.vim-logo-wall__text {
	display: flex;
	align-items: center;
	justify-content: center;
	min-height: 90px;
	margin: 0;
	font-size: 1.0625rem; /* 17 — a step up from the 14px captions, so a text
	                       * tile reads as artwork in its own right rather than
	                       * as a caption with its picture missing */
	font-weight: 700;
	line-height: 1.3;
	color: var(--teal-900);
	text-align: center;
	text-wrap: balance;
}

/* ---------------------------------------------------------------------------
 * Contact page
 *
 * Restructured 2026-08-25 (Tom: "three-column top section, hours table, map
 * and address", and "this needs to look like a good doctor's website contact
 * page"). Three detail cards over a band pairing the hours table with the map,
 * then the email form.
 *
 * ⚠️ Every GRID on this page lives in its own block's `styles` object, not
 * here — the three-up row, the hours/map pair and the card interiors. That is
 * the house rule (Tom, 2026-08-24): the client has to be able to change a
 * column split from the editor. What lives here is APPEARANCE only.
 *
 * The previous version put the four-column grid in `.vim-contact` with the
 * block carrying `"styles":[]`, which is the same dead-block defect that left
 * /board-of-directors/, /volunteer/ and /about/ silently unstaggered.
 * ------------------------------------------------------------------------- */

/*
 * Intro paragraph. Left at the section's own alignment, but capped at a
 * reading measure — across the full 1400px container a three-line paragraph
 * became one very long line and read like a legal notice.
 */
.vim-lede {
	max-width: 68ch;
	font-size: var(--fs-lead, 1.1875rem);
	color: var(--body);
}

/* ---------- the three detail cards ---------- */

/*
 * Sand cards on a white band, matching the Get Involved boxes so the site has
 * one card treatment rather than two. The hairline is what keeps them from
 * reading as flat blocks of colour once they sit side by side.
 */
/*
 * No border (Tom, 2026-08-25: "remove the border from the boxes on that same
 * page"). The sand fill is what separates a card from the white band behind it,
 * and the hairline on top of that was doing the job twice.
 *
 * ⚠️ The hours card and the map lost theirs in the same pass. Leaving those two
 * outlined while the cards above them were not would have read as a mistake
 * rather than a choice — they are all boxes on one page.
 */
.vim-contact-card {
	background-color: var(--sand);
	border-radius: 12px;
}

.vim-contact-card .vim-section__copy:last-child {
	margin-bottom: 0;
}

/*
 * Card headings are DIRECTORY LABELS, not section headings (Tom, 2026-08-25:
 * "the headers should not be the normal size or whatever it needs to be
 * directory like").
 *
 * `.vim-section__subheading` inherits GeneratePress's h3, which is
 * --fs-heading at 26px. Three of those stacked across a row shouted louder
 * than the address and the phone numbers underneath, which are the content a
 * visitor came for. At 15px uppercase over a rule they read as the column
 * headings of a directory and let the data below them carry the weight.
 *
 * The class beats GP's `h3 { font-size: ... }` on specificity (0,1,0) vs
 * (0,0,1), so no !important is needed — but it does have to stay a class rule;
 * moving this to a bare element selector would silently lose.
 */
.vim-directory-label {
	font-size: 0.9375rem; /* 15 */
	font-weight: 800;
	line-height: 1.3;
	text-transform: uppercase;
	letter-spacing: 0.085em;
	color: var(--teal-900);
	margin: 0 0 1.1rem;
	padding-bottom: 0.7rem;
	border-bottom: 2px solid var(--accent);
}

/*
 * Icon in a flat coloured circle — the same treatment as the homepage stat
 * band and the Get Involved boxes, at a smaller diameter because these sit
 * above a heading rather than carrying a section on their own.
 *
 * These three icons are drawn as STROKES, unlike the supplied Get Involved
 * artwork which is filled paths. Hence the separate rule: setting `fill` on
 * these would flood each shape solid.
 */
.vim-contact-card__icon {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 60px;
	height: 60px;
	aspect-ratio: 1;
	border-radius: 50%;
	margin-bottom: 1.25rem;
}

.vim-contact-card__icon svg {
	display: block;
	width: 28px;
	height: 28px;
	fill: none;
	stroke: var(--white);
	stroke-width: 1.75;
	stroke-linecap: round;
	stroke-linejoin: round;
}

.vim-contact-card__icon--0 {
	background-color: var(--plum);
}

.vim-contact-card__icon--1 {
	background-color: var(--teal-700);
}

.vim-contact-card__icon--2 {
	background-color: var(--green-600);
}

/*
 * The address itself. `<address>` is not in GenerateBlocks' tagName enum, so
 * this is a paragraph; the semantics are carried by the heading above it.
 */
.vim-contact-card__address {
	font-size: var(--fs-lead, 1.1875rem);
	font-weight: 700;
	color: var(--teal-900);
	line-height: 1.55;
	margin-bottom: 1.25rem;
}

/*
 * The phone directory (Tom, 2026-08-25: "it should have better phone number
 * listing ... it needs to be directory like").
 *
 * Was a bulleted list reading "Appointments and Eligibility: 541-685-1800" —
 * one undifferentiated run of body text per line, with the number, the thing a
 * visitor is actually scanning for, buried at the end behind a colon and
 * set in the same size and weight as the label.
 *
 * Now each entry is a row: a small uppercase label over the number, the number
 * set large in teal, and a hairline between entries. The eye runs down a
 * column of numbers instead of reading four sentences.
 *
 * ⚠️ Label ABOVE the number rather than beside it, deliberately. A
 * label-left / number-right directory row is the more conventional shape, but
 * these sit in a card roughly a third of the container wide and the longest
 * label — "Patient Assistance Program Fax" — wraps to two lines at that
 * measure, which leaves the number floating against a ragged label. Stacked,
 * every row is the same shape whatever the label length.
 */
.vim-phones {
	list-style: none;
	margin: 0;
	padding: 0;
}

.vim-phones li {
	padding-block: 0.75rem;
}

.vim-phones li:first-child {
	padding-top: 0;
}

.vim-phones li:last-child {
	padding-bottom: 0;
}

.vim-phones li + li {
	border-top: 1px solid color-mix(in srgb, var(--teal-900) 12%, transparent);
}

.vim-phones__label {
	display: block;
	font-size: 0.8125rem; /* 13 */
	font-weight: 700;
	line-height: 1.35;
	text-transform: uppercase;
	letter-spacing: 0.07em;
	color: var(--muted);
	margin-bottom: 0.2rem;
}

/*
 * Scoped past `.entry-content a:not([class*="gb-"])`, which scores (0,2,1)
 * because :not() takes the specificity of its argument and `[class*=]` is an
 * attribute selector. An unscoped `.vim-phones a` would tie at best and lose
 * on source order — the same trap that left every news card title underlined
 * in the prose link colour for weeks.
 */
.entry-content .vim-phones a:not([class*="gb-"]) {
	display: inline-block;
	font-size: 1.25rem; /* 20 */
	font-weight: 800;
	line-height: 1.2;
	font-variant-numeric: tabular-nums;
	color: var(--teal-900);
	text-decoration: none;
}

.entry-content .vim-phones a:not([class*="gb-"]):is(:hover, :focus) {
	color: var(--accent-dark);
	text-decoration: underline;
}

/*
 * A fax number is NOT a link (Tom, 2026-08-25). As a `tel:` link, tapping
 * "Clinic Fax" on a phone dials a fax machine — an unpleasant surprise, and on
 * a clinic site the sort of thing a patient does while already anxious.
 *
 * Matching the linked numbers' size, weight and tabular figures keeps the
 * column even, so the distinction is in the behaviour, not in the rhythm.
 */
.vim-phones__number {
	display: inline-block;
	font-size: 1.25rem; /* 20 — same as the linked numbers */
	font-weight: 800;
	line-height: 1.2;
	font-variant-numeric: tabular-nums;
	color: var(--teal-900);
}

/* ---------- hours ---------- */

/*
 * The hours sit in a white card on the sand band, so the table reads as a
 * posted notice rather than as loose text — which is how a clinic's opening
 * hours are read.
 */
.vim-hours-card {
	background-color: var(--white);
	border-radius: 12px;
}

/*
 * Opening hours as a description list — each day is the term and its hours are
 * the description, which is what a <dl> is for. Grid pairs them on one row
 * without wrapping every pair in its own div.
 *
 * ⚠️ The grid stays here rather than moving to the block's styles: the pairing
 * of a dt with its dd is the MEANING of a description list, not a layout
 * choice, and a client who changed it to one column would break the table
 * rather than restyle it. The card's padding and the hours/map split are both
 * on their blocks, which is where the editable decisions are.
 */
.vim-hours {
	display: grid;
	grid-template-columns: max-content 1fr;
	gap: 0 1.25rem;
	margin: 0;
	color: var(--body);
}

.vim-hours dt {
	font-weight: 800;
	color: var(--teal-900);
}

/*
 * Rule between days rather than under every cell — the separator has to span
 * the pair, and a grid has no row element to hang a border on, so each of the
 * two cells draws its own half of the same line.
 */
.vim-hours dt,
.vim-hours dd {
	padding-block: 0.7rem;
}

.vim-hours dt:not(:first-of-type),
.vim-hours dd:not(:first-of-type) {
	border-top: 1px solid color-mix(in srgb, var(--teal-900) 12%, transparent);
}

.vim-hours dd {
	margin: 0;
}

/* The closed day is information, not an offer — it should not read as loud as the open ones. */
.vim-hours .vim-hours__closed {
	color: var(--muted);
}

/* ---------- map ---------- */

/*
 * Map. The ratio lives on the wrapper so the iframe can fill it absolutely and
 * never letterbox or push the page sideways on a phone.
 *
 * `--vim-map-ratio` so the two-up band can flatten it: beside the hours card
 * the map is roughly half the width it used to be, and at 16/9 the pair came
 * out badly mismatched in height.
 */
.vim-map {
	position: relative;
	aspect-ratio: var(--vim-map-ratio, 16 / 9);
	border-radius: 12px;
	overflow: hidden;
}

/*
 * In the hours/map band the map is a stretched grid item, so it takes its
 * height from the hours card beside it rather than from a ratio. A ratio there
 * would fight the grid: at 16/9 across that column the map came out ~250px
 * taller than the card it is meant to sit level with.
 *
 * The min-height is what stops it collapsing if the card beside it is ever
 * shortened, and the ratio comes back once the band stacks to one column.
 */
.vim-map--fill {
	aspect-ratio: auto;
	height: 100%;
	min-height: 340px;
}

/*
 * 🚨 `min-height` MUST be released when the band stacks, and the reason is not
 * obvious: with a definite height and `aspect-ratio` set, the browser derives
 * the WIDTH from the height. At 375px the 340px floor plus a 4/3 ratio sized
 * the map to 453px and pushed 98px of horizontal overflow onto the page — a
 * map wider than the phone it was on. The floor only ever existed to stop the
 * map collapsing beside a short hours card, which cannot happen once the two
 * are stacked.
 */
@media (max-width: 900px) {
	.vim-map--fill {
		aspect-ratio: 16 / 9;
		height: auto;
		min-height: 0;
	}
}

/* Belt and braces: nothing here may ever be wider than the column it sits in. */
.vim-map {
	max-width: 100%;
}

@media (max-width: 600px) {
	.vim-map,
	.vim-map--fill {
		aspect-ratio: 4 / 3;
	}
}

.vim-map iframe {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	border: 0;
	display: block;
}

/*
 * Callout on a white band. `.vim-callout` is white, which is invisible against
 * the white "Email Us" section — the accent rule alone was doing all the work.
 * A modifier rather than a change to the component, which is still on sand
 * elsewhere and correct there.
 */
.vim-callout--sand {
	background-color: var(--sand);
}

/*
 * The emergency line above the contact form. Every clinic contact page carries
 * one, and it has to outrank the paragraph under it without being alarming —
 * so it is set larger and in --teal-900 rather than in a red that the palette
 * does not contain.
 *
 * ⚠️ NOT sized off --fs-lead: this line must not shrink when the type scale is
 * retuned, because it is the one sentence on the page that has to be read
 * first.
 */
.vim-callout__urgent {
	font-size: 1.125rem; /* 18 */
	font-weight: 800;
	color: var(--teal-900);
	margin-bottom: 0.75rem;
}

/* ---------- reading rhythm ---------- */

/*
 * These rules are for ORDINARY EDITOR CONTENT — paragraphs, lists and links
 * typed into the editor. They must not touch GenerateBlocks output, which
 * carries its own styling.
 *
 * Two regressions taught this the hard way: a blanket `.entry-content > * + *`
 * margin injected white gaps between the homepage's full-bleed bands, and a
 * blanket `.entry-content a` underlined every button on the site. GeneratePress
 * already applies bottom margins through the typography settings, so the
 * spacing rules were redundant as well as harmful — they are gone, and
 * everything else excludes `.gb-*`.
 */
/*
 * ⚠️ No reading measure here either.
 *
 * These selectors used to cap prose at 70ch. Removed on 2026-08-24 with the
 * body copy, so editor content fills its container the same way block content
 * does — a page that mixes the two should not have two different text widths.
 */

.entry-content > :is(ul, ol) {
	padding-left: 1.35em;
}

.entry-content > :is(ul, ol) li + li {
	margin-top: 0.5em;
}

/* Links in prose get underlines; block-built links style themselves. */
.entry-content a:not([class*="gb-"]) {
	color: var(--teal-700);
	text-decoration: underline;
	text-underline-offset: 0.15em;
}

.entry-content a:not([class*="gb-"]):hover,
.entry-content a:not([class*="gb-"]):focus {
	color: var(--accent-dark);
}

.entry-content > blockquote {
	margin-inline: 0;
	padding: 0.25rem 0 0.25rem 1.5rem;
	border-left: 4px solid var(--accent);
	font-size: var(--fs-lead, 1.25rem);
	color: var(--teal-900);
}

.entry-content :is(img, video) {
	max-width: 100%;
	height: auto;
}

.entry-content > table {
	width: 100%;
	border-collapse: collapse;
}

.entry-content > table :is(th, td) {
	padding: 0.7rem 1rem;
	border: 1px solid color-mix(in srgb, var(--teal-900) 22%, transparent);
	text-align: left;
}

.entry-content > table th {
	background-color: var(--sand);
	font-weight: 800;
}

/*
 * No extra padding on .content-area.
 *
 * This used to add clamp(2.5rem, 5vw, 4.5rem) top and bottom "for breathing
 * room", but GeneratePress's own .site-content already supplies 128px on any
 * contained page — so the rule was stacking a third layer of space under the
 * hero, on top of the theme's and the band's. Band-built pages now render
 * full-width (see vim_full_width_for_banded_pages in inc/interior.php) and get
 * their rhythm from .vim-section; pages of ordinary prose keep the theme's
 * 128px, which is enough on its own.
 */
