/*
	Theme Name: Fairfield Golf Club
	Theme URI: https://fairfieldgolfclub.co.uk/
	Description: A hardened, modernised fork of HTML5 Blank, restructured for building bespoke pages out of individually editable ACF blocks.
	Version: 1.0.0
	Author: Dave Mahon
	Requires PHP: 8.0
	Requires at least: 6.4
	Text Domain: html5blank
	License: MIT
	License URI: https://opensource.org/licenses/mit-license.php
*/

/*------------------------------------*\
    MAIN
\*------------------------------------*/

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

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

body {
	margin: 0;
	font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
	line-height: 1.5;
	color: #1a1a1a;
}

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

a {
	color: inherit;
}

.wrapper {
	margin: 0 auto;
}

/* Visually hidden but available to assistive tech — used on the mobile menu button. */
.screen-reader-text {
	position: absolute;
	width: 1px;
	height: 1px;
	padding: 0;
	margin: -1px;
	overflow: hidden;
	clip: rect(0, 0, 0, 0);
	white-space: nowrap;
	border: 0;
}

/*------------------------------------*\
    HEADER / PRIMARY NAVIGATION

    Structure: .site-header > .site-header__inner > logo, .site-nav
    (centered — the "Primary Menu" location), .site-header__actions
    (right-aligned — the separate "Header CTA Button" location, plus the
    mobile toggle). Both menus render via Fairfield_Nav_Walker in
    inc/nav-walker.php. Dropdowns come from child pages or manually
    nested items in the menu editor — no extra setup needed. Icons on
    dropdown links are optional (ACF "Icon" field on the menu item).

    The logo swaps to the crest-only mark below 480px, where there isn't
    room for the full wordmark next to the menu button (or earlier, via
    .site-header--compact-logo — see below).

    Mobile/compact nav is content-aware, not a fixed viewport breakpoint:
    the inline script right after </header> measures whether the logo +
    links + CTA actually fit the header at their natural width and toggles
    .site-header--compact-nav accordingly (re-checked on resize and once
    webfonts finish loading, since that can change link widths). This is
    deliberate — a fixed px breakpoint drifts out of sync the moment menu
    labels change length. .site-header--compact-nav carries what a
    max-width media query would; there's no separate no-JS fallback since
    the hamburger/dropdown interactions already require JS regardless.
\*------------------------------------*/

.site-header {
	--nav-navy: #051a40;
	--nav-blue: #093589;
	--nav-gold: #ca9f3e;
	--nav-cream: #f5f0e8;
	--nav-pad-y: 20px;

	position: sticky;
	top: 0;
	z-index: 1000;
	background-color: var(--nav-navy);
}

/* Applied briefly by the inline script (see below </header>) while it
   toggles .site-header--compact-nav during a resize, so the mobile panel's
   open/close transition doesn't replay and flash on screen for content
   that was never actually opened — only genuine hamburger clicks should
   animate. */
.site-header--no-transition,
.site-header--no-transition * {
	transition: none !important;
}

.site-header__inner {
	display: grid;
	grid-template-columns: minmax(190px, 1fr) auto minmax(190px, 1fr);
	align-items: stretch;
	gap: 1.5rem;
	max-width: 1400px;
	margin: 0 auto;
	padding: var(--nav-pad-y) 32px;
}

.site-header__logo {
	display: flex;
	align-items: center;
	grid-column: 1;
	justify-self: start;
	flex-shrink: 0;
	line-height: 0;
}

.site-header__logo-img {
	height: 40px;
	width: auto;
}

.site-header__logo-img--icon {
	display: none;
}

/* Same content-aware approach as .site-header--compact-nav below, checked
   separately: once the link list has moved into the dropdown, the row only
   has to fit the logo + CTA/hamburger — but a long wordmark could still be
   too wide for a very narrow phone, so that combination gets its own check. */
.site-header--compact-logo .site-header__logo-img--full {
	display: none;
}

.site-header--compact-logo .site-header__logo-img--icon {
	display: block;
}

@media (max-width: 480px) {
	.site-header__logo-img--full {
		display: none;
	}
	.site-header__logo-img--icon {
		display: block;
	}
}

.site-nav {
	display: flex;
	align-items: stretch;
	grid-column: 2;
	justify-self: center;
}

.site-header__actions {
	grid-column: 3;
	justify-self: end;
	display: flex;
	align-items: center;
	gap: 20px;
}

/*
 * Mobile menu toggle (hamburger) — hidden on desktop.
 *
 * Built from an inline SVG + <line> elements, not three plain <span>s
 * laid out via flex + background-color: on at least one real iPhone
 * (both Safari and Chrome — same WebKit engine underneath on iOS, so this
 * pointed at a rendering issue rather than a browser-specific one) the
 * span version rendered completely blank — no bars at all, despite the
 * button itself being present, correctly sized and clickable, and every
 * computed style checked out fine in desktop Chrome. Never fully root-
 * caused on that specific device; switching to real vector strokes
 * sidesteps whatever combination of flex-stretch + zero-width span +
 * background-color WebKit was mishandling, since a stroked SVG line
 * doesn't depend on any of that to have a visible width in the first
 * place.
 */
.site-nav__toggle-menu {
	display: none;
	align-items: center;
	justify-content: center;
	width: 32px;
	height: 32px;
	padding: 0;
	background: none;
	border: 0;
	cursor: pointer;
	flex-shrink: 0;
}

.site-nav__toggle-icon {
	width: 32px;
	height: 32px;
	overflow: visible;
}

.site-nav__toggle-bar {
	stroke: var(--nav-cream);
	stroke-width: 2;
	transition: transform 0.2s ease, opacity 0.2s ease;
	transform-box: fill-box;
	transform-origin: center;
}

.site-header--menu-open .site-nav__toggle-bar:nth-child(1) {
	transform: translateY(6px) rotate(45deg);
}
.site-header--menu-open .site-nav__toggle-bar:nth-child(2) {
	opacity: 0;
}
.site-header--menu-open .site-nav__toggle-bar:nth-child(3) {
	transform: translateY(-6px) rotate(-45deg);
}

.site-nav__menu {
	display: flex;
	align-items: stretch;
	gap: 32px;
	margin: 0;
	padding: 0;
	list-style: none;
}

.site-nav__item {
	position: relative;
	display: flex;
	align-items: center;
}

/* Highlights the trigger for its full height — flush with the header's own
   top/bottom edge, matching the Figma hover state — not just a padded box
   around the text. .site-nav__item is stretched (via the align-items:stretch
   chain above) to the height of the tallest header content, so top/bottom:0
   already reaches that; the calc() then bleeds the remaining --nav-pad-y so
   it reaches the header's true outer edge too. pointer-events:none keeps it
   out of hit-testing, and pixel bleed on left/right just widens the box a
   little beyond the caret/label. Because it's position:absolute, it paints
   above the (non-positioned) link/caret by default — .site-nav__link and
   .site-nav__toggle-submenu carry position:relative + z-index:1 so the text
   stays on top instead of being hidden behind the highlight on hover. */
.site-nav__item--has-children::before {
	content: "";
	position: absolute;
	top: calc(-1 * var(--nav-pad-y));
	bottom: calc(-1 * var(--nav-pad-y));
	left: -16px;
	right: -16px;
	pointer-events: none;
	transition: background-color 0.15s ease;
}

.site-nav__item--has-children:hover::before,
.site-nav__item--has-children:focus-within::before,
.site-nav__item--has-children.is-open::before {
	background-color: var(--nav-blue);
}

/* Invisible hit-area bridging the gap between the trigger and .site-nav__submenu
   below, so moving the pointer down into the dropdown doesn't cross a dead
   zone and lose :hover along the way. Both this height and the submenu's
   "top" (below) are anchored to --nav-pad-y + the same fixed buffer, rather
   than a percentage of the trigger's own height — the trigger is now
   stretched to the header's full height (see .site-nav__item above), so a
   percentage here would no longer land where it used to. Deliberately only
   as wide as the trigger itself (not the wider submenu below) — a fixed
   300px bridge here previously bled sideways under neighbouring nav items
   (e.g. hovering below "Contact" was opening "Facilities"'s dropdown). The
   submenu's own min-width still lets it visually extend further than the
   trigger; this bridge only needs to cover a straight line down from it. */
.site-nav__item--has-children::after {
	content: "";
	position: absolute;
	top: 100%;
	left: 0;
	right: 0;
	height: calc(var(--nav-pad-y) + 12px);
}

.site-nav__link,
.site-nav__submenu-link {
	display: inline-flex;
	align-items: center;
	gap: 8px;
	text-decoration: none;
	color: var(--nav-cream);
	font-family: "Source Sans 3", -apple-system, BlinkMacSystemFont, sans-serif;
}

.site-nav__link {
	position: relative;
	z-index: 1;
	padding-bottom: 3px;
	font-size: 0.78rem;
	line-height: 1.5;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	opacity: 0.82;
	border-bottom: 1px solid transparent;
	transition: opacity 0.15s ease, border-color 0.15s ease;
	/* Without this, a top-level label (not .site-nav__submenu-link, which
	   is fine wrapping inside its dropdown) is free to wrap onto a second
	   line once #site-nav-menu's grid column gets squeezed — which quietly
	   "solves" the width shortage by wrapping text instead of overflowing,
	   so navMenu.scrollWidth in the header's own inline content-aware script
	   never exceeds its clientWidth and .site-header--compact-nav never
	   gets toggled on. Confirmed directly: adding another nav item (or a
	   long label) shrank the grid's "auto" nav column before it, wrapping
	   "Events & Venue" / "What's on" onto two lines instead of switching to
	   the mobile menu. nowrap forces the link back to its true intrinsic
	   width so that script's measurement is accurate again. */
	white-space: nowrap;
}

.site-nav__link:hover,
.site-nav__link:focus-visible,
.site-nav__item.current-menu-item > .site-nav__link,
.site-nav__item.current-menu-ancestor > .site-nav__link {
	opacity: 1;
	border-bottom-color: var(--nav-gold);
}

.site-nav__caret {
	flex-shrink: 0;
	color: var(--nav-gold);
	transition: transform 0.2s ease;
}

.site-nav__toggle-submenu {
	position: relative;
	z-index: 1;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 4px;
	margin-left: 2px;
	background: none;
	border: 0;
	color: var(--nav-gold);
	cursor: pointer;
}

.site-nav__toggle-submenu .site-nav__caret {
	color: inherit;
}

/*
 * Hover/focus-within opening is desktop-only (the `:not(.site-header
 * --compact-nav)` guard below) — on mobile, opening a dropdown is a
 * deliberate tap on .site-nav__toggle-submenu, tracked purely by the
 * .is-open class (see js/scripts.js). Without that guard, a touch's own
 * transient :hover/:focus-within state (tapping the parent link itself
 * focuses it) also matched these same rules, fighting with .is-open:
 * dropdowns opened unreliably on tap, and — this is the more noticeable
 * symptom — scrolling the open mobile panel drops that transient hover/
 * focus state mid-scroll (mobile browsers clear it once a touch turns
 * into a scroll gesture), instantly closing a dropdown that had only
 * ever opened via :hover/:focus-within rather than a real, stable tap.
 */
.site-header:not(.site-header--compact-nav) .site-nav__item--has-children:hover > .site-nav__submenu,
.site-header:not(.site-header--compact-nav) .site-nav__item--has-children:focus-within > .site-nav__submenu,
.site-nav__item--has-children.is-open > .site-nav__submenu {
	display: block;
}

.site-header:not(.site-header--compact-nav) .site-nav__item--has-children:hover > .site-nav__toggle-submenu .site-nav__caret,
.site-header:not(.site-header--compact-nav) .site-nav__item--has-children:focus-within > .site-nav__toggle-submenu .site-nav__caret,
.site-nav__item--has-children.is-open > .site-nav__toggle-submenu .site-nav__caret {
	transform: rotate(180deg);
}

.site-nav__submenu {
	display: none;
	position: absolute;
	top: calc(100% + var(--nav-pad-y));
	left: -16px;
	z-index: 10;
	min-width: 300px;
	margin: 0;
	padding: 24px 0;
	list-style: none;
	background-color: var(--nav-blue);
	box-shadow: 0 16px 32px rgba(5, 26, 64, 0.25);
}

.site-nav__submenu .site-nav__submenu {
	position: static;
	box-shadow: none;
	padding-left: 20px;
}

.site-nav__submenu-item {
	display: block;
}

.site-nav__submenu-link {
	width: 100%;
	padding: 10px 28px;
	font-size: 0.7rem;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: #fff;
}

.site-nav__icon {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	flex-shrink: 0;
	width: 18px;
	height: 18px;
}

.site-nav__icon img {
	width: 100%;
	height: 100%;
	object-fit: contain;
}

/* "Book a Tee Time" — the "Header CTA Button" menu location (see header.php).
   Every link in that menu renders as this gold button. */
.site-nav__cta-menu {
	display: flex;
	align-items: center;
	gap: 12px;
	margin: 0;
	padding: 0;
	list-style: none;
}

.site-nav__cta-menu .site-nav__link {
	padding: 9px 20px;
	background-color: var(--nav-gold);
	border-bottom: 0;
	opacity: 1;
	color: var(--nav-navy);
	font-family: "DM Mono", "SFMono-Regular", Menlo, monospace;
	font-size: 0.72rem;
	letter-spacing: 0.14em;
}

.site-nav__cta-menu .site-nav__link:hover,
.site-nav__cta-menu .site-nav__link:focus-visible {
	background-color: #dbb659;
}

/* Back-compat: still supported if "nav-cta" is applied to an item inside the
   main Primary Menu instead of using the separate CTA menu location. */
.site-nav__item.nav-cta {
	margin-left: 8px;
}

.site-nav__item.nav-cta > .site-nav__link {
	padding: 9px 20px;
	background-color: var(--nav-gold);
	border-bottom: 0;
	opacity: 1;
	color: var(--nav-navy);
	font-family: "DM Mono", "SFMono-Regular", Menlo, monospace;
	font-size: 0.72rem;
	letter-spacing: 0.14em;
}

.site-nav__item.nav-cta > .site-nav__link:hover,
.site-nav__item.nav-cta > .site-nav__link:focus-visible {
	background-color: #dbb659;
}

/*
 * Compact nav — applied via .site-header--compact-nav, added/removed by the
 * inline script after </header> based on measured content width (see the
 * comment at the top of this section). The 480px media query below is only
 * a no-JS floor.
 */
.site-header--compact-nav .site-header__inner {
	position: relative;
	z-index: 1;
	display: flex;
	justify-content: space-between;
}

.site-header--compact-nav .site-nav__toggle-menu {
	display: flex;
}

.site-header--compact-nav .site-header__actions {
	gap: 12px;
}

.site-header--compact-nav .site-nav__cta-menu .site-nav__link {
	width: auto;
	padding: 8px 14px;
	font-size: 0.65rem;
}

.site-header--compact-nav .site-nav {
	display: block;
	grid-column: auto;
	justify-self: auto;
	position: absolute;
	top: 100%;
	left: 0;
	right: 0;
	max-height: calc(100vh - 100%);
	overflow-y: auto;
	background-color: var(--nav-navy);
	border-top: 1px solid rgba(202, 159, 62, 0.2);
	visibility: hidden;
	opacity: 0;
	transform: translateY(-6px);
	transition: opacity 0.2s ease, transform 0.2s ease, visibility 0s linear 0.2s;
}

.site-header--compact-nav.site-header--menu-open .site-nav {
	visibility: visible;
	opacity: 1;
	transform: translateY(0);
	transition: opacity 0.2s ease, transform 0.2s ease;
}

/* Backdrop behind the open mobile menu — dims the page beneath it and gives
   a large, obvious "tap here to close" target. Page scroll is locked to
   match (see .no-scroll, toggled in js/scripts.js alongside this class) —
   otherwise the dimmed page would still scroll behind the fixed panel,
   which reads as broken rather than intentional. Sits inside .site-header
   (z-index: 1000) so it renders above the page without needing its own
   very high z-index. It comes after .site-header__inner in source order
   though, so without an explicit stacking order it would paint over the
   inner's own contents (logo, hamburger) — z-index: 0 here plus
   .site-header__inner's own z-index: 1 (above) keeps those on top and
   clickable; .site-nav is positioned separately and paints above both. */
.site-header__backdrop {
	position: fixed;
	z-index: 0;
	inset: 0;
	background-color: rgba(0, 0, 0, 0.5);
	visibility: hidden;
	opacity: 0;
	transition: opacity 0.2s ease, visibility 0s linear 0.2s;
}

.site-header--compact-nav.site-header--menu-open .site-header__backdrop {
	visibility: visible;
	opacity: 1;
	transition: opacity 0.2s ease;
}

html.no-scroll,
body.no-scroll {
	overflow: hidden;
}

.site-header--compact-nav .site-nav__menu {
	flex-direction: column;
	align-items: stretch;
	gap: 0;
	padding: 8px 0 28px;
}

.site-header--compact-nav .site-nav__item {
	display: block;
	border-bottom: 1px solid rgba(202, 159, 62, 0.15);
}

.site-header--compact-nav .site-nav__item--has-children {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
}

.site-header--compact-nav .site-nav__item--has-children::before,
.site-header--compact-nav .site-nav__item--has-children::after {
	content: none;
}

.site-header--compact-nav .site-nav__link,
.site-header--compact-nav .site-nav__submenu-link {
	width: 100%;
	padding: 18px 28px;
	font-size: 0.85rem;
	letter-spacing: 0.12em;
}

.site-header--compact-nav .site-nav__item--has-children > .site-nav__link {
	width: auto;
	flex: 1 1 auto;
}

.site-header--compact-nav .site-nav__item--has-children > .site-nav__toggle-submenu {
	padding: 18px 28px;
	margin-left: 0;
}

.site-header--compact-nav .site-nav__item--has-children > .site-nav__submenu {
	flex-basis: 100%;
}

.site-header--compact-nav .site-nav__item--has-children.is-open > .site-nav__submenu {
	display: block;
}

.site-header--compact-nav .site-nav__submenu {
	position: static;
	width: calc(100% - 28px);
	margin-left: 28px;
	min-width: 0;
	box-shadow: none;
	padding: 4px 0 10px;
	background-color: var(--nav-blue);
	border-left: 2px solid var(--nav-gold);
}

.site-header--compact-nav .site-nav__submenu-link {
	padding: 12px 20px;
	font-size: 0.78rem;
}

.site-header--compact-nav .site-nav__icon {
	width: 20px;
	height: 20px;
}

.site-header--compact-nav .site-nav__item.nav-cta {
	margin: 16px 28px 0;
	border-bottom: 0;
}

.site-header--compact-nav .site-nav__item.nav-cta > .site-nav__link {
	width: 100%;
	justify-content: center;
	padding: 14px 20px;
}

/* No dedicated no-JS fallback here: the hamburger's open/close and the
   dropdown toggles are already JS-driven (js/scripts.js), same as before
   this change — a no-JS visit couldn't use the mobile menu either way. */
/*


/*------------------------------------*\
    FOOTER
\*------------------------------------*/

.site-footer {
	--footer-navy: #051a40;
	--footer-gold: #ca9f3e;
	background-color: var(--footer-navy);
	border-top: 1px solid rgba(196, 164, 107, 0.15);
}

.site-footer__inner {
	display: grid;
	grid-template-columns: 1.4fr 1fr 1fr;
	column-gap: 3rem;
	row-gap: 2.5rem;
	max-width: 1400px;
	margin: 0 auto;
	padding: 4rem 2rem;
}

.site-footer__logo {
	display: inline-flex;
	line-height: 0;
}

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

.site-footer__address,
.site-footer__contact-details {
	margin: 0;
	font-family: "Source Sans 3", -apple-system, BlinkMacSystemFont, sans-serif;
	font-size: 0.85rem;
	line-height: 1.7;
	color: #fff;
}

.site-footer__address {
	display: block;
	margin-top: 1.25rem;
}

a.site-footer__address--link {
	text-decoration: none;
}

a.site-footer__address--link:hover,
a.site-footer__address--link:focus-visible {
	text-decoration: underline;
}

.site-footer__contact-details {
	margin-top: 1.25rem;
}

.site-footer__contact-details a {
	color: #fff;
	text-decoration: none;
}

.site-footer__contact-details a:hover,
.site-footer__contact-details a:focus-visible {
	text-decoration: underline;
}

.site-footer__label {
	margin: 0;
	font-family: "DM Mono", "SFMono-Regular", Menlo, monospace;
	font-size: 0.62rem;
	letter-spacing: 0.2em;
	text-transform: uppercase;
	color: var(--footer-gold);
}

.site-footer__label--connect {
	margin-top: 1.4rem;
}

.site-footer__menu {
	display: flex;
	flex-direction: column;
	gap: 0.5rem;
	margin: 1rem 0 0;
	padding: 0;
	list-style: none;
}

.site-footer__menu a,
.site-footer__contact-link {
	font-family: "Source Sans 3", -apple-system, BlinkMacSystemFont, sans-serif;
	font-size: 0.85rem;
	color: #fff;
	text-decoration: none;
}

.site-footer__contact-link {
	display: inline-block;
	margin-top: 0.6rem;
}

.site-footer__menu a:hover,
.site-footer__menu a:focus-visible,
.site-footer__contact-link:hover,
.site-footer__contact-link:focus-visible {
	color: var(--footer-gold);
}

.site-footer__social {
	display: flex;
	align-items: center;
	gap: 0.75rem;
	margin-top: 1rem;
}

.site-footer__social-link {
	display: inline-flex;
	color: #fff;
	transition: color 0.2s ease;
}

.site-footer__social-link:hover,
.site-footer__social-link:focus-visible {
	color: var(--footer-gold);
}

.site-footer__bottom {
	border-top: 1px solid rgba(196, 164, 107, 0.12);
	padding: 1.25rem 2rem;
	display: flex;
}

.site-footer__copyright {
	max-width: 1152px;
	margin: 0 auto;
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 0.4rem 0.75rem;
	font-family: "DM Mono", "SFMono-Regular", Menlo, monospace;
	font-size: 0.6rem;
	letter-spacing: 0.12em;
	color: rgba(255, 255, 255, 0.8);
}

.site-footer__legal-link {
	color: rgba(255, 255, 255, 0.8);
	text-decoration: underline;
	text-underline-offset: 2px;
}

.site-footer__legal-link:hover,
.site-footer__legal-link:focus-visible {
	color: var(--footer-gold);
}

@media (max-width: 800px) {
	.site-footer__inner {
		grid-template-columns: 1fr 1fr;
	}

	.site-footer__brand {
		grid-column: 1 / -1;
	}
}

@media (max-width: 560px) {
	.site-footer__inner {
		grid-template-columns: 1fr;
		padding: 3rem 1.25rem;
	}

	.site-footer__bottom {
		padding: 1.25rem 1.25rem;
	}
}

/*------------------------------------*\
    PLAIN CONTENT PAGES
\*------------------------------------*/

/*
 * A generic reading-column treatment for plain text pages (Terms &
 * Conditions, Privacy & Cookies Policy, and any future page like them)
 * built from core paragraph/heading/list/table blocks rather than this
 * theme's own ACF blocks — page.php has no wrapping width/padding of its
 * own (every other page gets that from its own blocks' __inner divs), so
 * without this, a plain content page's text runs edge-to-edge at the full
 * viewport width. Applied via a className on the wrapping core Group
 * block, not a new custom block, since this is just typography/spacing,
 * not a reusable editable component.
 */
.legal-page {
	max-width: 46rem;
	margin: 0 auto;
	padding: 4rem 2rem 6rem;
	font-family: "Source Sans 3", -apple-system, BlinkMacSystemFont, sans-serif;
	font-size: 1rem;
	line-height: 1.75;
	color: #1e2419;
}

.legal-page > *:first-child {
	margin-top: 0;
}

.legal-page h2 {
	margin: 2.5rem 0 1rem;
	font-family: "Lora", Georgia, serif;
	font-weight: 600;
	font-size: 1.4rem;
	color: #051a40;
}

.legal-page p {
	margin: 0 0 1.25rem;
}

.legal-page ul {
	margin: 0 0 1.25rem;
	padding-left: 1.4em;
}

.legal-page li {
	margin-bottom: 0.5rem;
}

.legal-page a {
	color: #051a40;
	text-decoration: underline;
}

.legal-page table {
	width: 100%;
	border-collapse: collapse;
	margin: 0 0 1.5rem;
	font-size: 0.92rem;
}

.legal-page th,
.legal-page td {
	padding: 0.65rem 0.9rem;
	border: 1px solid #e8dfc8;
	text-align: left;
	vertical-align: top;
}

.legal-page thead th {
	background-color: #f0ece2;
	font-family: "DM Mono", "SFMono-Regular", Menlo, monospace;
	font-size: 0.7rem;
	letter-spacing: 0.06em;
	text-transform: uppercase;
}

@media (max-width: 640px) {
	.legal-page {
		padding: 2.5rem 1.25rem 4rem;
	}

	.legal-page table {
		display: block;
		overflow-x: auto;
	}
}

/*------------------------------------*\
    BLOCKS
\*------------------------------------*/

/* Individual block styles live alongside each block in /blocks/{block-name}/style.css
   and are enqueued automatically — this file is for global/site-wide styles only. */