/*
Theme Name: Fisher Labs
Theme URI: https://fisherlabs.eu
Author: Fisher Labs
Author URI: https://fisherlabs.eu
Description: Custom theme for the Fisher Labs platform. Renders content and configuration supplied by the Fisher Labs Core plugin - no business content or navigation labels are hardcoded here.
Requires at least: 6.5
Tested up to: 6.5
Requires PHP: 8.1
Version: 0.2.0
License: GNU General Public License v2 or later
License URI: LICENSE
Text Domain: fisher-labs
Domain Path: /languages

Fisher Labs requires the Fisher Labs Core plugin to be active.
*/

/*
 * Full visual redesign (requested directly - "style it properly to be
 * a world standard website"): a real design-token system, light/dark
 * mode, full-height/full-width homepage sections with Lenis-driven
 * momentum scroll and GSAP ScrollTrigger reveal choreography (see
 * assets/js/theme-interactions.js), and a hero slider. --fl-accent/--fl-dark/--fl-radius/
 * --fl-font-heading/--fl-font-body are overridden per-site by
 * Settings_Theme via fl_theme_style_tag() (inline <style> in <head>,
 * printed after this file loads) - the values below are this file's
 * own defaults/fallbacks, not hardcoded final values. Mobile-first; no
 * CSS framework, no page builder - matching spec rules 9/11. No
 * user-facing text lives here (spec rule 37) - only structure/style.
 */

:root {
	/* Brand tokens - admin-overridable (Settings_Theme). */
	--fl-accent: #0e686c;
	--fl-accent-fg: #ffffff;
	/* --accent (not --fl-accent) is Azurio's own native token
	 * (main.min.css's own :root) - a real, separate variable, not the
	 * same one under a different name. A dozen of Azurio's own
	 * components read it directly (.btn-default-accent, .bg-color-accent,
	 * .tag-bg.accent, the cursor dot/trail progress bar...) and every one
	 * of them was still rendering Azurio's own default blue (#002bba)
	 * throughout the site regardless of the --fl-accent fix above -
	 * "all buttons that are bluish throughout", reported directly, was
	 * this, not a leftover spot the first fix missed. Re-declared here
	 * (this stylesheet loads after main.min.css, so a plain re-
	 * declaration wins) and again in fl_theme_style_tag() below so the
	 * one admin-configured Accent Color drives both tokens identically. */
	--accent: #0e686c;
	--fl-dark: #0b1120;
	--fl-radius: 10px;
	--fl-radius-lg: 16px;
	--fl-font-heading: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
	--fl-font-body: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;

	/* Light palette - permanent default for internal (non-homepage) pages,
	 * not tied to Azurio's own color-scheme attribute (which is "light"
	 * everywhere now anyway - see header.php - so this block would agree
	 * with it regardless; kept unconditional rather than keyed to
	 * [color-scheme] mainly so it can't be knocked out of sync by a
	 * future change to that attribute). Only the footer goes dark on
	 * internal pages (requested directly - "I wanted only the footer in
	 * the internal pages to be dark"), via .fl-footer-dark further down,
	 * which is a scoped token override independent of this block. */
	--fl-bg: #ffffff;
	--fl-bg-alt: #f5f7fb;
	--fl-bg-raised: #ffffff;
	--fl-fg: #12162a;
	--fl-fg-muted: #5b6178;
	--fl-border: #e4e7f0;
	--fl-shadow: 0 1px 2px rgba(18, 22, 42, 0.04), 0 8px 24px rgba(18, 22, 42, 0.06);
	--fl-shadow-lg: 0 20px 60px rgba(18, 22, 42, 0.14);
	--fl-accent-soft: color-mix(in srgb, var(--fl-accent) 12%, transparent);
	--fl-header-bg: rgba(255, 255, 255, 0.82);

	--fl-max: 1180px;
	--fl-space: clamp(3rem, 7vw, 6rem);
}

* {
	box-sizing: border-box;
}

html {
	scroll-behavior: smooth;
}

body {
	font-family: var(--fl-font-body);
	line-height: 1.6;
	margin: 0;
	color: var(--fl-fg);
	background: var(--fl-bg);
	-webkit-font-smoothing: antialiased;
	transition: background-color 0.2s ease, color 0.2s ease;
}

h1, h2, h3, h4, h5, h6 {
	font-family: var(--fl-font-heading);
	line-height: 1.2;
	letter-spacing: -0.02em;
}

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

a {
	color: var(--fl-accent);
}

.fl-container {
	max-width: var(--fl-max);
	margin: 0 auto;
	padding: 0 1.5rem;
}

.screen-reader-text {
	border: 0;
	clip: rect(1px, 1px, 1px, 1px);
	clip-path: inset(50%);
	height: 1px;
	margin: -1px;
	overflow: hidden;
	padding: 0;
	position: absolute !important;
	width: 1px;
	word-wrap: normal !important;
}

.skip-link.screen-reader-text:focus {
	position: fixed !important;
	clip: auto !important;
	clip-path: none !important;
	width: auto !important;
	height: auto !important;
	top: 0.5rem;
	left: 0.5rem;
	z-index: 1000;
	background: var(--fl-accent);
	color: var(--fl-accent-fg);
	padding: 0.6rem 1rem;
	border-radius: var(--fl-radius);
}

/* ---------------------------------------------------------------
 * Header / nav / language switcher / dark mode toggle
 * --------------------------------------------------------------- */

.fl-site-header {
	position: sticky;
	top: 0;
	z-index: 40;
	background: var(--fl-header-bg);
	backdrop-filter: blur(12px);
	-webkit-backdrop-filter: blur(12px);
	border-bottom: 1px solid var(--fl-border);
}

/* The vendor's own #header.mxd-header (main.min.css) is only
 * z-index:1 - a tie with several in-page hero blocks that are also
 * z-index:1 (.fl-project-hero__inner, .fl-hero-slide-inner, etc). A
 * tied z-index is broken by DOM order, and those hero blocks render
 * after <header> in markup, so they painted over it - specifically
 * swallowing clicks on the language-switcher dropdown, which opens
 * downward past the header's own bottom edge into the hero area below.
 * Confirmed live with a headless-browser click trace on an archive page
 * ("Français" link unclickable - elementFromPoint at its coordinates
 * resolved to .fl-project-hero__inner, not the link) after the language
 * switcher gained French/German/Spanish entries and this became
 * reachable; reported directly. #header.mxd-header (specificity 1,1,0)
 * beats the vendor's own .mxd-header (0,1,0) without needing
 * !important.
 *
 * Briefly raised past .mxd-loader/.mxd-page-transition (z-index 1000/999)
 * to fix "the logo does not display" on a fresh/bookmarked load - reverted
 * back to 10 ("it's the same thing, now a bit worse", reported directly
 * right after): raising the whole header made every child visible as
 * soon as ITS OWN asset was ready, not together, and under the same
 * slow-connection conditions that motivated the fix in the first place,
 * the language-switcher's pill/chevron (pure CSS, instant) painted a
 * full 1-2s before the logo image did - a half-rendered, disconnected
 * control floating over an otherwise still-black screen, which read
 * worse than the original gap. The real fix for the original report
 * lives in .mxd-page-transition itself now (header.php + this file's
 * own .mxd-page-transition__brand rule, a few hundred lines down) -
 * it shows the same branding .mxd-loader already does, so the screen
 * is never actually blank, without touching header stacking at all. */
#header.mxd-header {
	z-index: 10;
}

.fl-site-header-inner {
	display: flex;
	align-items: center;
	gap: 1.5rem;
	padding: 0.9rem 1.5rem;
}

.fl-site-brand {
	display: inline-flex;
	align-items: center;
	text-decoration: none;
	color: var(--fl-fg);
	font-weight: 800;
	font-family: var(--fl-font-heading);
	font-size: 1.2rem;
	letter-spacing: -0.02em;
	margin-right: auto;
}

.fl-site-brand img,
.fl-site-brand .custom-logo {
	max-height: 36px;
	width: auto;
}

.fl-logo-dark {
	display: none;
}

.fl-nav-toggle {
	display: none;
	background: none;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	color: var(--fl-fg);
	padding: 0.5rem;
	cursor: pointer;
	margin-left: auto;
}

.fl-nav-toggle svg {
	width: 22px;
	height: 22px;
}

.fl-site-header-collapse {
	display: flex;
	align-items: center;
	gap: 2rem;
	margin-left: auto;
}

.fl-primary-menu {
	list-style: none;
	display: flex;
	flex-wrap: wrap;
	gap: 1.75rem;
	margin: 0;
	padding: 0;
}

.fl-primary-menu a {
	text-decoration: none;
	color: var(--fl-fg);
	font-weight: 600;
	font-size: 0.94rem;
	transition: color 0.15s ease;
}

.fl-primary-menu a:hover {
	color: var(--fl-accent);
}

.fl-header-controls {
	display: flex;
	align-items: center;
	gap: 1rem;
}

/* Superseded by the scoped, complete .fl-language-*
 * rules further down (the language switcher's markup changed from a
 * native <select> to a custom button+dropdown - see fl_language_switcher()
 * in functions.php), kept here only as a comment for history. */

.fl-theme-toggle {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 2.1rem;
	height: 2.1rem;
	border-radius: 999px;
	border: 1px solid var(--fl-border);
	background: var(--fl-bg-alt);
	color: var(--fl-fg);
	cursor: pointer;
	padding: 0;
}

.fl-theme-toggle svg {
	width: 18px;
	height: 18px;
}

.fl-icon-moon {
	display: none;
}

:root[data-fl-theme="dark"] .fl-icon-sun {
	display: none;
}
:root[data-fl-theme="dark"] .fl-icon-moon {
	display: block;
}
@media (prefers-color-scheme: dark) {
	:root:not([data-fl-theme="light"]) .fl-icon-sun { display: none; }
	:root:not([data-fl-theme="light"]) .fl-icon-moon { display: block; }
}

/* ---------------------------------------------------------------
 * Buttons
 * --------------------------------------------------------------- */

.fl-button {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	gap: 0.8rem;
	padding: 1.3rem 2.4rem;
	border-radius: var(--fl-radius);
	border: 1px solid var(--fl-border);
	text-decoration: none;
	color: var(--fl-fg);
	font-weight: 600;
	font-size: 1.5rem;
	line-height: 1.2;
	background: var(--fl-bg-raised);
	cursor: pointer;
	transition: transform 0.15s ease, box-shadow 0.15s ease, background-color 0.15s ease, border-color 0.15s ease;
}

.fl-button:hover {
	transform: translateY(-1px);
	box-shadow: var(--fl-shadow);
	text-decoration: none;
}

.fl-button-primary {
	background: var(--fl-accent);
	border-color: var(--fl-accent);
	color: var(--fl-accent-fg);
}

.fl-button-primary:hover {
	color: var(--fl-accent-fg);
	filter: brightness(1.08);
}

/* Log In / Sign Up (or My Account, logged in) inside the full-screen
 * nav menu (header.php, .mxd-menu__left) - the one menu surface used
 * on every page at every width, requested directly as their placement
 * rather than fighting the header bar's own limited space. */
.fl-menu-account {
	display: flex;
	flex-wrap: wrap;
	gap: 1.2rem;
	margin-top: 2.4rem;
}

/* Two render sites, one per breakpoint (fl_menu_account_buttons(),
 * functions.php) - stacked under the real site nav "appear[ed] okay" on
 * mobile but "ridiculous" on desktop, where it needed to sit above the
 * contact/address info on the right instead - reported directly. Below
 * 768px the mobile copy (inside .mxd-menu__left) shows and the desktop
 * one (inside .mxd-menu__right) hides; the reverse at 768px+. Same
 * breakpoint every other piece of header-chrome responsive sizing in
 * this file already uses. */
.fl-menu-account--desktop {
	display: none;
}

@media only screen and (min-width: 768px) {
	.fl-menu-account--mobile {
		display: none;
	}

	.fl-menu-account--desktop {
		display: flex;
		flex-wrap: nowrap;
		gap: 0.8rem;
		margin-top: 0;
		margin-bottom: 3.2rem;
	}

	/* .mxd-menu__right (main.min.css) is only 33% of the menu overlay's
	 * width, so two full .fl-button-lg buttons ("Log In"/"Sign Up") wrapped
	 * onto separate lines there instead of sitting side by side - reported
	 * directly. flex-wrap:nowrap above keeps them on one line; clamp()
	 * here shrinks their own padding/font-size fluidly with that column's
	 * actual width (driven by viewport width, same as the column itself)
	 * so they scale down just enough to both fit instead of overflowing or
	 * wrapping their own text mid-word. */
	.fl-menu-account--desktop .fl-button {
		padding: clamp(0.9rem, 0.6vw + 0.6rem, 1.5rem) clamp(1.2rem, 1.6vw + 0.6rem, 2.8rem);
		font-size: clamp(1.2rem, 0.4vw + 1rem, 1.6rem);
		white-space: nowrap;
	}
}

/* ---------------------------------------------------------------
 * Full-height, full-width homepage sections
 * --------------------------------------------------------------- */

/*
 * Native CSS scroll-snap was the first pass here, before Lenis entered
 * the picture - the two don't combine well (Lenis replaces the
 * browser's own scroll handling with a JS-driven one; native
 * scroll-snap fighting a second system for control of scroll position
 * is a well-known bad combination, not a hypothetical one). Dropped in
 * favour of what real sites built this way actually do: generous
 * min-height sections, Lenis's own momentum easing, and the
 * scroll-triggered reveal choreography below doing the work of making
 * each section feel like its own moment - not a hard, forced snap.
 */
@media (min-width: 900px) {
	.fl-scroll-sections .fl-section {
		min-height: 100vh;
		display: flex;
		align-items: center;
	}

	.fl-scroll-sections .fl-section > .fl-container,
	.fl-scroll-sections .fl-hero-slides {
		width: 100%;
	}
}

.fl-section {
	padding: var(--fl-space) 0;
	position: relative;
}

.fl-section:nth-of-type(even) {
	background: var(--fl-bg-alt);
}

.fl-section-heading {
	font-size: clamp(1.75rem, 3.2vw, 2.5rem);
	margin: 0 0 0.6rem;
	font-weight: 800;
}

.fl-section-subheading {
	color: var(--fl-fg-muted);
	margin: 0 0 2.5rem;
	max-width: 60ch;
	font-size: 1.05rem;
}

/* ---------------------------------------------------------------
 * Hero + slider
 * --------------------------------------------------------------- */

.fl-hero {
	padding: 0;
	overflow: hidden;
}

.fl-hero-slides {
	position: relative;
}

.fl-hero-slide {
	display: none;
	padding: clamp(4rem, 12vw, 8rem) 0;
	background-size: cover;
	background-position: center;
	position: relative;
}

.fl-hero-slide-active {
	display: block;
	animation: fl-fade-in 0.5s ease;
}

.fl-hero-slide[style*="--fl-hero-image"]::before {
	content: "";
	position: absolute;
	inset: 0;
	background-image: var(--fl-hero-image);
	background-size: cover;
	background-position: center;
	opacity: 0.16;
	z-index: 0;
}

:root[data-fl-theme="dark"] .fl-hero-slide[style*="--fl-hero-image"]::before {
	opacity: 0.28;
}

.fl-hero-slide-inner {
	position: relative;
	z-index: 1;
	text-align: center;
}

.fl-hero h1 {
	font-size: clamp(2.25rem, 5.5vw, 3.75rem);
	margin: 0 0 1.1rem;
	font-weight: 800;
}

.fl-hero-subtitle {
	color: var(--fl-fg-muted);
	font-size: clamp(1.05rem, 2vw, 1.3rem);
	max-width: 60ch;
	margin: 0 auto 2.2rem;
}

.fl-hero-dots {
	position: absolute;
	bottom: 1.5rem;
	left: 50%;
	transform: translateX(-50%);
	display: flex;
	gap: 0.5rem;
	z-index: 2;
}

.fl-hero-dot {
	width: 8px;
	height: 8px;
	border-radius: 999px;
	border: none;
	background: var(--fl-border);
	cursor: pointer;
	padding: 0;
}

.fl-hero-dot-active {
	background: var(--fl-accent);
	width: 22px;
}

.fl-hero-arrow {
	position: absolute;
	top: 50%;
	transform: translateY(-50%);
	width: 2.5rem;
	height: 2.5rem;
	border-radius: 999px;
	border: 1px solid var(--fl-border);
	background: var(--fl-bg-raised);
	color: var(--fl-fg);
	display: none;
	align-items: center;
	justify-content: center;
	cursor: pointer;
	z-index: 2;
}

.fl-hero-arrow svg {
	width: 18px;
	height: 18px;
}

.fl-hero-arrow-prev {
	left: 1.5rem;
}

.fl-hero-arrow-next {
	right: 1.5rem;
}

@media (min-width: 700px) {
	.fl-hero-arrow {
		display: flex;
	}
}

@keyframes fl-fade-in {
	from { opacity: 0; transform: translateY(6px); }
	to { opacity: 1; transform: translateY(0); }
}

.fl-stats-grid {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
	gap: 1.5rem;
	text-align: center;
}

.fl-stat {
	font-size: clamp(1.75rem, 3.4vw, 2.5rem);
	font-weight: 800;
	margin: 0;
	font-family: var(--fl-font-heading);
}

.fl-cta {
	text-align: center;
}

/* ---------------------------------------------------------------
 * Card grid (services/products/projects/demos/testimonials)
 * --------------------------------------------------------------- */

.fl-card-grid {
	display: grid;
	/* Wider minimum than before (was 280px) - larger cards, fewer per
	   row, at the user's own direction ("the cards should be...
	   larger and occupy more width"). At --fl-max (1180px) this seats
	   2 up, occasionally 3 on very wide viewports, never the 4+ cramped
	   columns the old 280px minimum allowed. */
	grid-template-columns: repeat(auto-fit, minmax(400px, 1fr));
	gap: 2rem;
}

.fl-card {
	display: flex;
	flex-direction: column;
	gap: 0.85rem;
	padding: 2rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	text-decoration: none;
	color: inherit;
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
	transition: transform 0.18s ease, box-shadow 0.18s ease, border-color 0.18s ease;
}

.fl-card:hover {
	transform: translateY(-4px);
	border-color: var(--fl-accent);
	box-shadow: var(--fl-shadow-lg);
	text-decoration: none;
}

.fl-card-image {
	margin: -2rem -2rem 0.5rem;
	overflow: hidden;
	border-radius: var(--fl-radius-lg) var(--fl-radius-lg) 0 0;
	aspect-ratio: 4 / 3;
}

.fl-card-image img {
	border-radius: 0;
	transition: transform 0.3s ease;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.fl-card:hover .fl-card-image img {
	transform: scale(1.05);
}

.fl-card-title {
	font-weight: 700;
	font-family: var(--fl-font-heading);
	font-size: 1.2rem;
}

.fl-card-excerpt {
	color: var(--fl-fg-muted);
	font-size: 0.96rem;
	line-height: 1.55;
}

/* ---------------------------------------------------------------
 * Archive / single
 * --------------------------------------------------------------- */

.fl-generic-archive {
	padding: 3rem 0;
}

.fl-archive-header,
.fl-single-header {
	padding: var(--fl-space) 1.5rem 2rem;
	max-width: var(--fl-max);
	margin: 0 auto;
}

.fl-archive-header h1,
.fl-single-header h1 {
	font-size: clamp(1.9rem, 4vw, 2.75rem);
	font-weight: 800;
}

.fl-single {
	max-width: 70ch;
	margin: 0 auto;
	padding: 0 1.5rem 4rem;
}

.fl-single.fl-single-product,
.fl-single.fl-single-demo {
	max-width: 80ch;
}

.fl-single-lead {
	color: var(--fl-fg-muted);
	font-size: 1.15rem;
}

.fl-single-meta {
	color: var(--fl-fg-muted);
	font-size: 0.9rem;
}

.fl-product-section {
	margin-top: 2rem;
}

/* ---------------------------------------------------------------
 * Pricing plans + calculator
 * --------------------------------------------------------------- */

.fl-pricing-grid {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(260px, 1fr));
	gap: 1.5rem;
	align-items: start;
}

.fl-pricing-card {
	display: flex;
	flex-direction: column;
	gap: 0.85rem;
	padding: 2rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
	transition: transform 0.18s ease, box-shadow 0.18s ease;
}

.fl-pricing-card:hover {
	transform: translateY(-3px);
	box-shadow: var(--fl-shadow-lg);
}

.fl-pricing-card-featured {
	border-color: var(--fl-accent);
	box-shadow: 0 0 0 2px var(--fl-accent), var(--fl-shadow-lg);
	position: relative;
}

.fl-pricing-card-featured::before {
	content: "★";
	position: absolute;
	top: -0.75rem;
	right: 1.5rem;
	background: var(--fl-accent);
	color: var(--fl-accent-fg);
	font-size: 0.7rem;
	padding: 0.3rem 0.6rem;
	border-radius: 999px;
}

.fl-pricing-card-name {
	margin: 0;
	font-weight: 800;
}

.fl-pricing-card-price {
	font-size: 2.25rem;
	font-weight: 800;
	margin: 0;
	font-family: var(--fl-font-heading);
}

.fl-pricing-card-period {
	font-size: 1rem;
	font-weight: 400;
	color: var(--fl-fg-muted);
}

.fl-pricing-card-description {
	color: var(--fl-fg-muted);
	margin: 0;
}

.fl-pricing-card-features {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 0.55rem;
}

.fl-pricing-card-features li {
	padding-left: 1.6em;
	position: relative;
}

.fl-pricing-card-features li::before {
	content: "";
	position: absolute;
	left: 0;
	top: 0.45em;
	width: 0.6em;
	height: 0.6em;
	border-radius: 50%;
	background: var(--fl-accent-soft);
	border: 2px solid var(--fl-accent);
}

.fl-single-price {
	font-size: 1.75rem;
	font-weight: 800;
	margin: 0.25rem 0;
	font-family: var(--fl-font-heading);
}

.fl-calculator {
	margin-top: 2rem;
	padding: 1.75rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	background: var(--fl-bg-alt);
}

.fl-calculator-row {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1rem;
	margin-bottom: 1rem;
}

.fl-calculator-row input,
.fl-calculator-row select {
	padding: 0.45rem 0.7rem;
	border: 1px solid var(--fl-border);
	border-radius: calc(var(--fl-radius) - 2px);
	background: var(--fl-bg-raised);
	color: var(--fl-fg);
}

.fl-calculator-addons {
	border: none;
	padding: 0;
	margin: 0 0 1rem;
}

.fl-calculator-addon {
	display: flex;
	align-items: center;
	gap: 0.5rem;
	margin-bottom: 0.5rem;
}

.fl-calculator-addon-price {
	color: var(--fl-fg-muted);
	font-size: 0.875rem;
}

.fl-calculator-result {
	font-size: 1.3rem;
	font-weight: 700;
	margin: 0;
	border-top: 1px solid var(--fl-border);
	padding-top: 1rem;
}

/* ---------------------------------------------------------------
 * Configurable pricing builder (Pricing\Pricing_Form)
 * NOTE: this theme sets html { font-size: 62.5% } so 1rem = 10px -
 * every size below is on that scale (1.6rem = 16px body text).
 * --------------------------------------------------------------- */

.fl-pricing-builder {
	color: var(--fl-fg);
}

/* Two columns on desktop: the configuration card on the left, a sticky
 * estimate card on the right. custom_quote has no aside -> single column. */
.fl-pricing-builder__grid {
	display: grid;
	grid-template-columns: 1fr;
	gap: 2.4rem;
	align-items: start;
}

@media (min-width: 980px) {
	.fl-pricing-builder.has-aside .fl-pricing-builder__grid {
		grid-template-columns: minmax(0, 1fr) 36rem;
		gap: 3rem;
	}
}

.fl-pricing-builder__main {
	padding: 3.6rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
}

@media (max-width: 600px) {
	.fl-pricing-builder__main {
		padding: 2.4rem 2rem;
	}
}

.fl-pricing-builder__head {
	margin-bottom: 3rem;
	padding-bottom: 2rem;
	border-bottom: 1px solid var(--fl-border);
}

.fl-pricing-builder__head .fl-section-heading {
	margin: 0;
	font-size: 2.6rem;
	line-height: 1.15;
}

.fl-pricing-builder__intro {
	color: var(--fl-fg-muted);
	font-size: 1.55rem;
	line-height: 1.55;
	margin: 1rem 0 0;
	max-width: 60ch;
}

.fl-pricing-builder__body {
	display: flex;
	flex-direction: column;
	gap: 3rem;
	font-size: 1.4rem;
}

/* Sliders read better full-width (a range track needs the room), so they
 * keep the wider auto-fit grid on their own. */
.fl-pb-sliders {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(22rem, 1fr));
	gap: 1rem;
	align-items: start;
}

/* Feature/add-on/configurator-option selection cards: flexbox rather
 * than grid so a last row of 1-2 items stretches to fill the row instead
 * of sitting narrow and left-aligned (grid items don't do this without
 * extra markup; flex-grow gives it for free). min-width caps it at 3 per
 * row on desktop and wraps to fewer as the column narrows - was
 * unintentionally fitting up to 4 per row before, reported directly. */
.fl-pb-group__grid,
.fl-pb-config {
	display: flex;
	flex-wrap: wrap;
	gap: 1rem;
	align-items: stretch;
}

.fl-pb-group__grid > *,
.fl-pb-config > * {
	flex: 1 1 calc(33.333% - 0.667rem);
	min-width: 18rem;
}

.fl-pb-config > [hidden],
.fl-pb-group__grid > [hidden] {
	display: none;
}

/* A configurator field with a longer control (a select of long option
 * labels) can opt to span the full row. */
.fl-pb-field--wide {
	flex-basis: 100%;
}

/* -------- Sticky estimate card (right column) --------------------- */
.fl-pricing-builder__aside {
	position: relative;
}

@media (min-width: 980px) {
	.fl-pricing-builder__aside {
		position: sticky;
		top: 9rem;
	}
}

.fl-pricing-builder__estimate-card {
	padding: 3rem;
	border: 1.5px solid var(--fl-accent);
	border-radius: var(--fl-radius-lg);
	background: color-mix(in srgb, var(--fl-accent) 6%, var(--fl-bg-raised));
	box-shadow: var(--fl-shadow-lg);
}

.fl-pb-group {
	border: none;
	padding: 0;
	margin: 0;
}

.fl-pb-group legend {
	font-family: var(--fl-font-heading);
	font-size: 1.35rem;
	font-weight: 800;
	text-transform: uppercase;
	letter-spacing: 0.08em;
	color: var(--fl-fg-muted);
	margin-bottom: 1.2rem;
	padding: 0;
	width: 100%;
}

.fl-pb-list {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 0.9rem;
}

.fl-pb-item {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1.5rem;
	padding: 1.2rem 0;
	border-bottom: 1px solid var(--fl-border);
	font-size: 1.55rem;
}

.fl-pb-item:last-child {
	border-bottom: none;
}

.fl-pb-item__tag {
	font-size: 1.2rem;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: 0.06em;
	color: var(--fl-accent);
}

.fl-pb-item__price,
.fl-pb-option__price {
	color: var(--fl-fg-muted);
	font-size: 1.3rem;
	font-weight: 600;
	font-variant-numeric: tabular-nums;
	white-space: nowrap;
}

/* -------- Toggle rows: tappable cards with a real custom checkbox ----- */
.fl-pb-option {
	display: flex;
	align-items: center;
	gap: 1.1rem;
	padding: 1.2rem 1.4rem;
	flex-wrap: wrap;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	background: var(--fl-bg-alt);
	cursor: pointer;
	transition: border-color 0.15s ease, background-color 0.15s ease, box-shadow 0.15s ease;
}

.fl-pb-option:hover {
	border-color: color-mix(in srgb, var(--fl-accent) 55%, var(--fl-border));
}

.fl-pb-option:has(input:checked) {
	border-color: var(--fl-accent);
	background: color-mix(in srgb, var(--fl-accent) 8%, var(--fl-bg-raised));
	box-shadow: 0 0 0 1px var(--fl-accent) inset;
}

/* Custom checkbox: hide the native control, draw our own box. */
.fl-pb-option input[type="checkbox"] {
	appearance: none;
	-webkit-appearance: none;
	flex: none;
	width: 1.9rem;
	height: 1.9rem;
	margin: 0;
	border: 1.5px solid var(--fl-border);
	border-radius: 0.5rem;
	background: var(--fl-bg-raised);
	cursor: pointer;
	transition: background-color 0.12s ease, border-color 0.12s ease;
	display: grid;
	place-content: center;
}

.fl-pb-option input[type="checkbox"]::before {
	content: "";
	width: 1rem;
	height: 1rem;
	transform: scale(0);
	transition: transform 0.12s ease;
	background: var(--fl-accent-fg, #fff);
	clip-path: polygon(14% 44%, 0 60%, 40% 100%, 100% 18%, 86% 4%, 40% 72%);
}

.fl-pb-option input[type="checkbox"]:checked {
	background: var(--fl-accent);
	border-color: var(--fl-accent);
}

.fl-pb-option input[type="checkbox"]:checked::before {
	transform: scale(1);
}

.fl-pb-option input[type="checkbox"]:focus-visible {
	outline: 2px solid var(--fl-accent);
	outline-offset: 2px;
}

.fl-pb-option__label {
	flex: 1;
	min-width: 8rem;
	font-weight: 600;
	font-size: 1.4rem;
	line-height: 1.35;
}

.fl-pb-option.is-included {
	color: var(--fl-fg-muted);
	cursor: default;
	background: var(--fl-bg-alt);
	border-style: dashed;
}

.fl-pb-option.is-included input[type="checkbox"] {
	opacity: 0.55;
}

.fl-pb-option__hint,
.fl-pb-slider__hint,
.fl-pb-field__hint {
	flex-basis: 100%;
	margin: 0.4rem 0 0;
	font-size: 1.25rem;
	line-height: 1.45;
	color: var(--fl-fg-muted);
}

/* -------- Sliders (each is a compact card in the grid) -------------- */
.fl-pb-slider {
	display: flex;
	flex-direction: column;
	gap: 0.8rem;
	padding: 1.4rem 1.6rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	background: var(--fl-bg-alt);
}

.fl-pb-slider__label {
	display: flex;
	align-items: baseline;
	gap: 0.7rem;
	font-weight: 600;
	font-size: 1.4rem;
}

.fl-pb-slider__name {
	flex: 1;
}

.fl-pb-slider__value {
	font-family: var(--fl-font-heading);
	font-size: 1.7rem;
	font-weight: 800;
	color: var(--fl-accent);
	font-variant-numeric: tabular-nums;
}

.fl-pb-slider__unit {
	color: var(--fl-fg-muted);
	font-weight: 400;
	font-size: 1.25rem;
}

/* Track wrapper carries the value bubble; --pb-frac (0-1) is set by JS. */
.fl-pb-slider__track {
	position: relative;
	padding-top: 3rem;
}

.fl-pb-slider__bubble {
	position: absolute;
	top: 0;
	left: calc(1.1rem + var(--pb-frac, 0) * (100% - 2.2rem));
	transform: translateX(-50%);
	padding: 0.3rem 0.9rem;
	border-radius: 999px;
	background: var(--fl-accent);
	color: var(--fl-accent-fg, #fff);
	font-family: var(--fl-font-heading);
	font-weight: 800;
	font-size: 1.25rem;
	line-height: 1;
	white-space: nowrap;
	pointer-events: none;
}

.fl-pb-slider__bubble::after {
	content: "";
	position: absolute;
	left: 50%;
	bottom: -0.5rem;
	transform: translateX(-50%);
	border: 0.5rem solid transparent;
	border-top-color: var(--fl-accent);
	border-bottom: 0;
}

.fl-pb-slider input[type="range"] {
	-webkit-appearance: none;
	appearance: none;
	width: 100%;
	height: 0.7rem;
	margin: 0;
	border-radius: 999px;
	background: linear-gradient(
		to right,
		var(--fl-accent) 0,
		var(--fl-accent) calc(var(--pb-frac, 0) * 100%),
		var(--fl-border) calc(var(--pb-frac, 0) * 100%),
		var(--fl-border) 100%
	);
	cursor: pointer;
}

.fl-pb-slider input[type="range"]::-webkit-slider-runnable-track {
	height: 0.7rem;
	border-radius: 999px;
	background: transparent;
}

.fl-pb-slider input[type="range"]::-moz-range-track {
	height: 0.7rem;
	border-radius: 999px;
	background: var(--fl-border);
}

.fl-pb-slider input[type="range"]::-moz-range-progress {
	height: 0.7rem;
	border-radius: 999px;
	background: var(--fl-accent);
}

.fl-pb-slider input[type="range"]::-webkit-slider-thumb {
	-webkit-appearance: none;
	appearance: none;
	width: 2rem;
	height: 2rem;
	margin-top: -0.65rem;
	border-radius: 50%;
	background: #fff;
	border: 0.4rem solid var(--fl-accent);
	box-shadow: 0 2px 6px rgba(0, 0, 0, 0.22);
	cursor: grab;
	transition: transform 0.1s ease;
}

.fl-pb-slider input[type="range"]::-moz-range-thumb {
	width: 2rem;
	height: 2rem;
	border-radius: 50%;
	background: #fff;
	border: 0.4rem solid var(--fl-accent);
	box-shadow: 0 2px 6px rgba(0, 0, 0, 0.22);
	cursor: grab;
}

.fl-pb-slider input[type="range"]:active::-webkit-slider-thumb {
	transform: scale(1.12);
	cursor: grabbing;
}

.fl-pb-slider input[type="range"]:focus-visible {
	outline: none;
}

.fl-pb-slider input[type="range"]:focus-visible::-webkit-slider-thumb {
	box-shadow: 0 0 0 4px color-mix(in srgb, var(--fl-accent) 30%, transparent), 0 2px 8px rgba(0, 0, 0, 0.25);
}

.fl-pb-slider__minmax {
	display: flex;
	justify-content: space-between;
	font-size: 1.15rem;
	color: var(--fl-fg-muted);
	font-variant-numeric: tabular-nums;
	margin-top: 0.2rem;
}

/* -------- Configurator fields (each a compact card in the grid) ---- */
.fl-pb-field {
	display: flex;
	flex-direction: column;
	gap: 0.9rem;
	padding: 1.3rem 1.5rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	background: var(--fl-bg-alt);
}

.fl-pb-field__label {
	font-family: var(--fl-font-heading);
	font-weight: 800;
	font-size: 1.4rem;
}

.fl-pb-field__row {
	display: flex;
	align-items: center;
	gap: 1rem;
	flex-wrap: wrap;
}

/* Custom-styled select: kill the native chrome, draw our own chevron. */
.fl-pb-field select {
	appearance: none;
	-webkit-appearance: none;
	width: 100%;
	padding: 1rem 3.4rem 1rem 1.2rem;
	border: 1.5px solid var(--fl-border);
	border-radius: var(--fl-radius);
	background-color: var(--fl-bg-raised);
	background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='14' height='14' viewBox='0 0 24 24' fill='none' stroke='%23888' stroke-width='2.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E");
	background-repeat: no-repeat;
	background-position: right 1.2rem center;
	color: var(--fl-fg);
	font-size: 1.35rem;
	font-weight: 600;
	cursor: pointer;
	transition: border-color 0.12s ease, box-shadow 0.12s ease;
}

.fl-pb-field select:hover {
	border-color: color-mix(in srgb, var(--fl-accent) 55%, var(--fl-border));
}

.fl-pb-field select:focus-visible {
	outline: none;
	border-color: var(--fl-accent);
	box-shadow: 0 0 0 3px color-mix(in srgb, var(--fl-accent) 22%, transparent);
}

.fl-pb-field select option {
	background: var(--fl-bg-raised);
	color: var(--fl-fg);
}

/* Stepper: −/＋ buttons around a plain number field. */
.fl-pb-stepper {
	display: inline-flex;
	align-items: stretch;
	border: 1.5px solid var(--fl-border);
	border-radius: var(--fl-radius);
	overflow: hidden;
	background: var(--fl-bg-raised);
}

.fl-pb-stepper button {
	width: 3.6rem;
	padding: 0.8rem 0;
	border: none;
	background: var(--fl-bg-alt);
	color: var(--fl-fg);
	font-size: 1.7rem;
	line-height: 1;
	font-weight: 700;
	cursor: pointer;
	transition: background-color 0.12s ease, color 0.12s ease;
}

.fl-pb-stepper button:hover {
	background: var(--fl-accent);
	color: var(--fl-accent-fg, #fff);
}

.fl-pb-stepper button:disabled {
	opacity: 0.35;
	cursor: not-allowed;
}

.fl-pb-stepper input[type="number"] {
	width: 4.6rem;
	border: none;
	border-left: 1.5px solid var(--fl-border);
	border-right: 1.5px solid var(--fl-border);
	background: transparent;
	color: var(--fl-fg);
	font-size: 1.4rem;
	font-weight: 700;
	text-align: center;
	-moz-appearance: textfield;
	appearance: textfield;
}

.fl-pb-stepper input[type="number"]::-webkit-outer-spin-button,
.fl-pb-stepper input[type="number"]::-webkit-inner-spin-button {
	-webkit-appearance: none;
	margin: 0;
}

.fl-pb-field__unit {
	color: var(--fl-fg-muted);
	font-size: 1.25rem;
	font-variant-numeric: tabular-nums;
}

/* No-JS fallback still renders a bare range/select/number - style those
 * minimally so the fallback doesn't look broken either. */
.fl-pb-slider [type="range"]:not([class]),
[data-fl-pricing-fallback] select,
[data-fl-pricing-fallback] input[type="number"] {
	accent-color: var(--fl-accent);
}

.fl-pricing-builder__estimate {
	display: flex;
	flex-direction: column;
	gap: 0.4rem;
}

.fl-pricing-builder__estimate-label {
	font-size: 1.2rem;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: 0.1em;
	color: var(--fl-fg-muted);
}

.fl-pricing-builder__estimate-value {
	font-family: var(--fl-font-heading);
	font-size: 3.6rem;
	line-height: 1.05;
	font-weight: 800;
	color: var(--fl-accent);
	font-variant-numeric: tabular-nums;
}

.fl-pricing-builder__note {
	margin: 1.6rem 0 0;
	font-size: 1.3rem;
	line-height: 1.5;
	color: var(--fl-fg-muted);
}

.fl-pricing-builder__actions {
	display: flex;
	flex-direction: column;
	gap: 1rem;
	margin-top: 2rem;
}

.fl-pricing-builder__actions .fl-button,
.fl-pricing-builder__order {
	width: 100%;
}

.fl-pricing-builder__order {
	display: flex;
}

.fl-pricing-builder__order .fl-button {
	width: 100%;
}

/* Enquiry panel - a full-width card that opens under the two columns:
 * the live configuration summary on the left, the contact form on the
 * right (mirrors the checkout layout). */
.fl-pricing-builder__enquiry {
	margin-top: 2.4rem;
	padding: 3.2rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
}

.fl-pricing-builder__enquiry-grid {
	display: grid;
	grid-template-columns: 1fr;
	gap: 2.4rem;
	margin-top: 2rem;
}

@media (min-width: 860px) {
	.fl-pricing-builder__enquiry-grid {
		grid-template-columns: 28rem minmax(0, 1fr);
		gap: 3rem;
	}
}

.fl-pricing-builder__enquiry[hidden] {
	display: none;
}

.fl-pricing-builder__enquiry-title {
	margin: 0 0 0.6rem;
	font-size: 2.2rem;
}

.fl-pricing-builder__enquiry-lead {
	margin: 0 0 2rem;
	font-size: 1.5rem;
	color: var(--fl-fg-muted);
}

.fl-pricing-builder__summary {
	padding: 2rem 2.2rem;
	border-radius: var(--fl-radius-lg);
	background: color-mix(in srgb, var(--fl-accent) 6%, var(--fl-bg-raised));
	border: 1px solid var(--fl-border);
	height: 100%;
}

.fl-pricing-builder__summary-label {
	display: block;
	font-size: 1.2rem;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: 0.08em;
	color: var(--fl-fg-muted);
	margin-bottom: 1.2rem;
}

.fl-pricing-builder__summary-body ul {
	margin: 0;
	padding: 0;
	list-style: none;
	font-size: 1.4rem;
	line-height: 1.5;
	display: flex;
	flex-direction: column;
	gap: 0.9rem;
}

.fl-pricing-builder__summary-body li {
	padding-left: 1.8rem;
	position: relative;
}

.fl-pricing-builder__summary-body li::before {
	content: "";
	position: absolute;
	left: 0;
	top: 0.5em;
	width: 0.7rem;
	height: 0.7rem;
	border-radius: 50%;
	background: var(--fl-accent);
}

.fl-pricing-builder__summary-total {
	margin: 1.6rem 0 0;
	padding-top: 1.4rem;
	border-top: 1px solid var(--fl-border);
	font-weight: 800;
	font-size: 1.6rem;
	color: var(--fl-accent);
}

.fl-pb-quote {
	max-width: 48rem;
	font-size: 1.6rem;
}

/* Bigger buttons for the builder (and a shared large modifier). */
.fl-button-lg {
	padding: 1.5rem 2.8rem;
	font-size: 1.6rem;
	border-radius: var(--fl-radius);
}

/* Homepage "Pricing Builder" cards (template-parts/pricing-builder-card.php) */

.fl-pb-card__icon {
	display: block;
	width: 48px;
	height: 48px;
	object-fit: contain;
	margin-bottom: 0.75rem;
}

.fl-pb-card__price {
	display: flex;
	flex-direction: column;
	gap: 0.15rem;
	line-height: 1.15;
}

.fl-pb-card__from-label {
	font-size: 0.7rem;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: 0.08em;
	color: var(--fl-fg-muted);
}

/* Bumped from 1.9rem (requested directly, part of the pricing-card
 * redesign pass - see .pricing-data__num's own comment for the same
 * "the price is the headline" reasoning) - still its own smaller size
 * than a definite price (.pricing-data__num, 4rem), since this is an
 * "estimated from" figure, not a final one. */
.fl-pb-card__amount {
	font-family: var(--fl-font-heading);
	font-size: 2.8rem;
	font-weight: 800;
	font-variant-numeric: tabular-nums;
	color: var(--fl-fg);
}

/* ---------------------------------------------------------------
 * FAQ accordion (native <details>, no JS needed)
 * --------------------------------------------------------------- */

.fl-faq-list {
	display: flex;
	flex-direction: column;
	gap: 0.85rem;
	max-width: 70ch;
}

.fl-faq-item {
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	padding: 1.1rem 1.3rem;
	background: var(--fl-bg-raised);
	transition: border-color 0.15s ease;
}

.fl-faq-item:hover {
	border-color: var(--fl-accent);
}

.fl-faq-item summary {
	cursor: pointer;
	font-weight: 700;
}

.fl-faq-answer {
	margin-top: 0.85rem;
	color: var(--fl-fg-muted);
}

/* ---------------------------------------------------------------
 * Forms
 * --------------------------------------------------------------- */

.fl-contact-form {
	max-width: 40rem;
	display: flex;
	flex-direction: column;
	gap: 1.1rem;
}

.fl-contact-form label {
	display: block;
	font-weight: 600;
	margin-bottom: 0.4rem;
}

.fl-contact-form input,
.fl-contact-form textarea,
.fl-single input[type="text"],
.fl-single input[type="email"],
.fl-single input[type="tel"],
.fl-single input[type="number"],
.fl-single select,
.fl-single textarea {
	width: 100%;
	padding: 0.7rem 0.9rem;
	border: 1px solid var(--fl-border);
	border-radius: calc(var(--fl-radius) - 2px);
	font: inherit;
	background: var(--fl-bg-raised);
	color: var(--fl-fg);
}

.fl-contact-form input:focus,
.fl-contact-form textarea:focus,
.fl-single input:focus,
.fl-single select:focus,
.fl-single textarea:focus {
	outline: none;
	border-color: var(--fl-accent);
	box-shadow: 0 0 0 3px var(--fl-accent-soft);
}

.fl-contact-form button {
	border: none;
	cursor: pointer;
	font: inherit;
}

.fl-honeypot {
	position: absolute;
	left: -9999px;
}

.fl-form-notice {
	padding: 0.9rem 1.2rem;
	border-radius: var(--fl-radius);
	margin-bottom: 1.5rem;
	max-width: 40rem;
}

.fl-form-notice-success {
	background: color-mix(in srgb, #1a7a4c 14%, var(--fl-bg-raised));
	color: #1a7a4c;
}

.fl-form-notice-error {
	background: color-mix(in srgb, #b3261e 14%, var(--fl-bg-raised));
	color: #b3261e;
}

/* ---------------------------------------------------------------
 * Checkout
 * --------------------------------------------------------------- */

.fl-order-summary {
	width: 100%;
	max-width: 40rem;
	border-collapse: collapse;
	margin-bottom: 1.5rem;
}

.fl-order-summary td {
	padding: 0.7rem 0;
	border-bottom: 1px solid var(--fl-border);
}

.fl-order-summary td:last-child {
	text-align: right;
}

.fl-order-summary-total td {
	font-weight: 700;
	border-bottom: none;
	font-size: 1.15rem;
}

/* -------- Checkout page order form (template-checkout.php) --------
 * Order details card on the left, customer form on the right - 1rem =
 * 10px on this theme, same scale as the pricing builder. */
.fl-checkout-grid {
	display: grid;
	grid-template-columns: 1fr;
	gap: 2.4rem;
	align-items: start;
}

@media (min-width: 980px) {
	.fl-checkout-grid {
		grid-template-columns: 38rem minmax(0, 1fr);
		gap: 3rem;
	}
}

.fl-checkout-order,
.fl-checkout-customer {
	padding: 3rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
}

@media (min-width: 980px) {
	.fl-checkout-order {
		position: sticky;
		top: 9rem;
	}
}

.fl-checkout-order .fl-section-heading,
.fl-checkout-customer .fl-section-heading {
	margin: 0 0 2rem;
	font-size: 2rem;
}

.fl-checkout-lines {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
}

.fl-checkout-line {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1.2rem;
	padding: 1.1rem 0;
	border-bottom: 1px solid var(--fl-border);
	font-size: 1.4rem;
}

.fl-checkout-line__label {
	flex: 1;
}

.fl-checkout-line__right {
	display: flex;
	align-items: center;
	gap: 0.8rem;
	flex: none;
}

.fl-checkout-line__price {
	font-weight: 600;
	font-variant-numeric: tabular-nums;
	white-space: nowrap;
}

.fl-checkout-line--discount .fl-checkout-line__label,
.fl-checkout-line--discount .fl-checkout-line__price {
	color: var(--fl-accent);
}

.fl-checkout-line__remove {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 2rem;
	height: 2rem;
	border-radius: 50%;
	color: var(--fl-fg-muted);
	text-decoration: none;
	font-size: 1.5rem;
	line-height: 1;
	transition: background-color 0.12s ease, color 0.12s ease;
}

.fl-checkout-line__remove:hover,
.fl-checkout-line__remove:focus-visible {
	background: var(--fl-error-bg, color-mix(in srgb, #b3261e 14%, transparent));
	color: #b3261e;
}

.fl-checkout-coupon {
	display: flex;
	gap: 0.8rem;
	margin-top: 1.8rem;
}

.fl-checkout-coupon input[type="text"] {
	flex: 1;
	padding: 1rem 1.2rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius);
	background: var(--fl-bg-alt);
	color: var(--fl-fg);
	font-size: 1.35rem;
}

.fl-checkout-coupon input[type="text"]:focus-visible {
	outline: none;
	border-color: var(--fl-accent);
	box-shadow: 0 0 0 3px color-mix(in srgb, var(--fl-accent) 22%, transparent);
}

.fl-checkout-coupon .fl-button {
	padding: 1rem 1.8rem;
	font-size: 1.35rem;
}

.fl-checkout-coupon__error {
	margin: 0.8rem 0 0;
	font-size: 1.3rem;
	color: #b3261e;
}

.fl-checkout-total {
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	margin-top: 2rem;
	padding-top: 1.8rem;
	border-top: 1.5px solid var(--fl-border);
	font-size: 1.4rem;
}

.fl-checkout-total strong {
	font-family: var(--fl-font-heading);
	font-size: 2.8rem;
	font-weight: 800;
	color: var(--fl-accent);
}

/* Exactly two columns, never more - reported directly ("some rows have 4
 * fields. there should be a maximum of two fields in a row"). The previous
 * repeat(auto-fit, minmax(20rem, 1fr)) packed in 3-4 columns whenever the
 * customer column was wide enough. Collapses to one column on narrow
 * viewports so two inputs never get cramped side by side. */
.fl-checkout-form__grid {
	display: grid;
	grid-template-columns: repeat(2, minmax(0, 1fr));
	gap: 1.4rem 2rem;
	margin-bottom: 2.4rem;
}

@media only screen and (max-width: 640px) {
	.fl-checkout-form__grid {
		grid-template-columns: 1fr;
	}
}

.fl-form-row--wide {
	grid-column: 1 / -1;
}

.fl-checkout-form .fl-form-row {
	padding: 0;
}

/* .fl-checkout-form.fl-form (not just .fl-checkout-form) - the form
 * element actually carries both classes ("fl-form fl-checkout-form"),
 * and the generic .fl-form select rule further down (sitewide - contact/
 * account/checkout/booking/consulting) sets its own height/line-height/
 * padding/font-size sized for its own <input>s. Equal-specificity same-
 * property declarations resolve by source order, and that rule comes
 * later in the file, so its `height: 5.8rem; line-height: 5.8rem;`
 * (correct for a text input, where a line-height taller than the visible
 * box just overflows symmetrically and invisibly) was winning here too -
 * a <select>'s closed-state text doesn't get the same treatment, so the
 * oversized line-height rendered the option text cropped at the bottom
 * of the shorter, padding-constrained box. The extra class makes this
 * rule unambiguously more specific, and it now states its own
 * line-height explicitly rather than depending on which one currently
 * wins. */
.fl-checkout-form.fl-form select {
	appearance: none;
	-webkit-appearance: none;
	width: 100%;
	padding: 1.2rem 3.6rem 1.2rem 0.2rem;
	border: none;
	border-bottom: 1px solid var(--st-medium);
	background-color: transparent;
	background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' viewBox='0 0 24 24' fill='none' stroke='%23888' stroke-width='2.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E");
	background-repeat: no-repeat;
	background-position: right 0.2rem center;
	color: var(--t-bright);
	font: normal 400 1.5rem var(--_font-accent, inherit);
	line-height: 1.5;
	height: auto;
}

.fl-checkout-consent {
	margin: 0.4rem 0 2.4rem;
	padding: 1.8rem 2rem;
	border-radius: var(--fl-radius);
	background: var(--fl-bg-alt);
	border: 1px solid var(--fl-border);
}

.fl-checkout-consent__row {
	/* !important - .fl-form label (this is a <label>, inside a .fl-form)
	 * sets display:block at higher specificity (0,2,0 vs this rule's
	 * 0,1,0) and silently won, stacking the checkbox above the text
	 * instead of beside it - confirmed via the live computed style
	 * (display:block, not flex), not a guess. Same root cause fixes
	 * .fl-auth-remember below. */
	display: flex !important;
	align-items: flex-start;
	gap: 1rem;
	font-size: 1.35rem;
	line-height: 1.5;
}

.fl-checkout-consent__row + .fl-checkout-consent__row {
	margin-top: 1.2rem;
}

.fl-checkout-consent__row input[type="checkbox"] {
	flex: none;
	width: 1.8rem;
	height: 1.8rem;
	margin-top: 0.1rem;
	accent-color: var(--fl-accent);
}

.fl-checkout-consent__note {
	margin: 1.4rem 0 0;
	padding-top: 1.2rem;
	border-top: 1px solid var(--fl-border);
	font-size: 1.2rem;
	line-height: 1.5;
	color: var(--fl-fg-muted);
}

.fl-checkout-payment-note {
	font-size: 1.35rem;
	margin: 0 0 1.6rem;
}

.fl-checkout-actions {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 1.2rem;
}

.fl-checkout-submit {
	width: 100%;
	justify-content: center;
}

.fl-checkout-cancel {
	width: 100%;
	justify-content: center;
}

/* ---------------------------------------------------------------
 * Auth gate (checkout's account requirement + the account page's own
 * logged-out view - template-parts/checkout-auth-gate.php)
 * --------------------------------------------------------------- */
.fl-auth-google {
	display: flex;
	align-items: center;
	justify-content: center;
	gap: 0.9rem;
	width: 100%;
	padding: 1.1rem 1.6rem;
	border: 1px solid var(--fl-border, rgba(18, 18, 18, 0.16));
	border-radius: var(--fl-radius, 10px);
	background: var(--fl-bg, #fff);
	color: var(--fl-fg, #121212);
	font-size: 1.4rem;
	font-weight: 700;
	text-decoration: none;
	transition: border-color 0.2s ease, background-color 0.2s ease;
}

.fl-auth-google:hover {
	border-color: var(--fl-accent);
	background: var(--fl-accent-soft, color-mix(in srgb, var(--fl-accent) 8%, transparent));
}

.fl-auth-divider {
	display: flex;
	align-items: center;
	gap: 1rem;
	margin: 1.6rem 0;
	color: var(--fl-fg-muted, #7d7f89);
	font-size: 1.2rem;
	text-transform: uppercase;
	letter-spacing: 0.04rem;
}

.fl-auth-divider::before,
.fl-auth-divider::after {
	content: '';
	flex: 1;
	height: 1px;
	background: var(--fl-border, rgba(18, 18, 18, 0.16));
}

.fl-auth-columns {
	display: grid;
	grid-template-columns: 1fr;
	gap: 2.4rem;
}

@media only screen and (min-width: 768px) {
	.fl-auth-columns {
		grid-template-columns: 1fr 1fr;
	}
}

.fl-auth-column h3 {
	font-size: 1.8rem;
	margin: 0 0 1.4rem;
}

.fl-auth-column__note {
	margin-top: 1rem;
	font-size: 1.3rem;
}

.fl-auth-remember {
	/* !important - same .fl-form label specificity fight as
	 * .fl-checkout-consent__row above. */
	display: flex !important;
	align-items: center;
	gap: 0.8rem;
	margin: 0 0 1.6rem;
	font-size: 1.35rem;
	cursor: pointer;
}

/* Same treatment as .fl-checkout-consent__row's own checkbox - a plain
 * native <input type="checkbox"> with no sizing of its own renders at
 * the browser's default, unstyled size, which reads as far too large
 * next to every other custom-styled control on this form (reported
 * directly). */
.fl-auth-remember input[type="checkbox"] {
	flex: none;
	width: 1.8rem;
	height: 1.8rem;
	margin: 0;
	accent-color: var(--fl-accent);
}

/* Dedicated Log In / Sign Up pages (template-login.php/template-signup.php,
 * mode:'login'/'signup') - a single centred card instead of the checkout
 * gate's full-width two-column layout, reported directly as looking
 * unfinished next to it ("should be more professionally styled"). The
 * standard single-form auth-page treatment: a bounded card with its own
 * surface/border/shadow, sitting on the page's own background, rather
 * than a form floating directly in the page container at full width. */
.fl-auth-gate--single {
	max-width: 46rem;
	margin: 0 auto;
	padding: 3.2rem;
	border: 1px solid var(--fl-border);
	border-radius: calc(var(--fl-radius) * 2);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
}

@media only screen and (max-width: 575px) {
	.fl-auth-gate--single {
		padding: 2.4rem 1.8rem;
	}
}

.fl-auth-gate--single .fl-auth-columns {
	grid-template-columns: 1fr;
}

.fl-auth-gate__intro {
	margin: 0 0 2.4rem;
	color: var(--fl-fg-muted);
	font-size: 1.5rem;
}

.fl-auth-gate--single .fl-auth-column {
	max-width: none;
}

.fl-auth-column__switch {
	margin-top: 2rem;
	padding-top: 2rem;
	border-top: 1px solid var(--fl-border);
	font-size: 1.35rem;
	text-align: center;
}

.fl-auth-column__switch a {
	color: var(--fl-accent);
	font-weight: 700;
	text-decoration: none;
}

.fl-auth-column__switch a:hover {
	text-decoration: underline;
}

/* ---------------------------------------------------------------
 * Booking
 * --------------------------------------------------------------- */

/* The "Book this consultation" CTA card on a consultation detail page
 * (single-fl_consultation_type.php) - a bounded, centred card with its
 * own surface, the same treatment as the dedicated Log In / Sign Up
 * pages (.fl-auth-gate--single above). */
.fl-consultation-book {
	max-width: 52rem;
	margin: 0 auto;
	padding: 3.2rem;
	border: 1px solid var(--fl-border);
	border-radius: calc(var(--fl-radius) * 2);
	background: var(--fl-bg-raised);
	box-shadow: var(--fl-shadow);
	text-align: center;
}

@media only screen and (max-width: 575px) {
	.fl-consultation-book {
		padding: 2.4rem 1.8rem;
	}
}

.fl-consultation-book .fl-section-heading {
	margin-top: 0;
}

.fl-consultation-book .fl-prose {
	margin-bottom: 2rem;
}

/* --- retired: the in-site availability slot picker (Booking\Availability_Manager
 * was removed this session); .fl-slot-* left only for any historical
 * markup and harmless as dead rules. --- */
.fl-slot-days {
	display: flex;
	flex-direction: column;
	gap: 1.5rem;
}

.fl-slot-day h3 {
	margin: 0 0 0.5rem;
	font-size: 1rem;
}

.fl-slot-list {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5rem;
}

.fl-slot {
	padding: 0.55rem 1rem;
}

/* ---------------------------------------------------------------
 * Client Portal
 * --------------------------------------------------------------- */

.fl-portal-section {
	margin-bottom: 2.5rem;
}

.fl-portal-section h2 {
	font-size: 1.2rem;
	border-bottom: 1px solid var(--fl-border);
	padding-bottom: 0.6rem;
}

.fl-portal-list {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 0.6rem;
}

.fl-portal-list li {
	padding: 0.6rem 0;
	border-bottom: 1px solid var(--fl-border);
}

.fl-inline-form {
	display: inline;
}

.fl-button-link {
	background: none;
	border: none;
	padding: 0;
	margin-left: 0.5rem;
	color: var(--fl-accent);
	text-decoration: underline;
	cursor: pointer;
	font: inherit;
}

/* ---------------------------------------------------------------
 * Footer
 * --------------------------------------------------------------- */

.fl-site-footer {
	padding: 3.5rem 0 2.5rem;
	border-top: 1px solid var(--fl-border);
	color: var(--fl-fg-muted);
	font-size: 0.92rem;
	background: var(--fl-bg-alt);
}

.fl-site-footer nav ul {
	list-style: none;
	display: flex;
	flex-wrap: wrap;
	gap: 1rem;
	margin: 0 0 1rem;
	padding: 0;
}

.fl-footer-columns {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
	gap: 2rem;
	margin-bottom: 2.5rem;
	padding-bottom: 2.5rem;
	border-bottom: 1px solid var(--fl-border);
}

.fl-footer-widget-title {
	font-size: 0.98rem;
	margin: 0 0 0.85rem;
	color: var(--fl-fg);
	font-weight: 700;
}

.fl-footer-bottom {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 1rem;
}

.fl-footer-social {
	display: flex;
	flex-wrap: wrap;
	gap: 1.25rem;
}

.fl-footer-social a {
	color: var(--fl-fg-muted);
	text-decoration: none;
	font-weight: 600;
}

.fl-footer-social a:hover {
	color: var(--fl-accent);
}

.fl-footer-newsletter {
	flex-basis: 100%;
	order: 3;
}

.fl-footer-newsletter-form {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5rem;
}

.fl-footer-newsletter-form input[type="email"] {
	padding: 0.6rem 0.9rem;
	border: 1px solid var(--fl-border);
	border-radius: calc(var(--fl-radius) - 2px);
	background: var(--fl-bg-raised);
	color: var(--fl-fg);
	flex: 1;
	min-width: 200px;
}

.fl-footer-copyright {
	flex-basis: 100%;
	order: 4;
	margin: 1.5rem 0 0;
}

/* Mobile-only floating "back to top" (footer.php's #fl-mobile-totop,
 * mobile-back-to-top.js toggles .is-visible on scroll) - "on the right,
 * not close to the footer, mostly in the middle of the page... a very
 * narrow button with 3 arrows that looks like [an] animation", reported
 * directly. Fixed at mid-viewport height rather than a bottom corner (the
 * requested placement, and it also keeps clear of any bottom-fixed
 * chatbot launcher - FLAI_Frontend's widget defaults to bottom-right).
 * display:none above 768px - the footer's own "Back to Top" link was
 * removed entirely (reported directly), so desktop has no back-to-top
 * affordance now. */
.fl-mobile-totop {
	display: none;
	position: fixed;
	top: 50%;
	right: 1.4rem;
	transform: translateY(-50%) translateX(0.6rem);
	z-index: 40;
	width: 3.4rem;
	height: 5.4rem;
	padding: 0;
	border: 1px solid var(--fl-border);
	border-radius: 999px;
	background: var(--fl-bg-raised);
	color: var(--fl-fg-muted);
	cursor: pointer;
	align-items: center;
	justify-content: center;
	flex-direction: column;
	gap: 0.1rem;
	opacity: 0;
	pointer-events: none;
	transition: opacity 0.3s ease, transform 0.3s ease, color 0.2s ease;
}

@media only screen and (max-width: 767px) {
	.fl-mobile-totop {
		display: flex;
	}
}

.fl-mobile-totop.is-visible {
	opacity: 1;
	pointer-events: auto;
	transform: translateY(-50%) translateX(0);
}

.fl-mobile-totop:hover,
.fl-mobile-totop:focus-visible {
	color: var(--fl-fg);
}

.fl-mobile-totop:active {
	transform: translateY(-50%) scale(0.94);
}

/* Three clean stroked SVG chevrons (rounded caps/joins), stacked and
 * animated with a staggered rise/fade so they read as one continuous
 * upward motion - "make the carets... more professional", reported
 * directly, replacing the earlier CSS-drawn two-bar chevrons whose
 * vertex seam looked rough. */
.fl-mobile-totop__caret {
	display: block;
	width: 1.4rem;
	height: auto;
	animation: fl-totop-caret 1.5s cubic-bezier(0.25, 0.46, 0.45, 0.94) infinite;
}

.fl-mobile-totop__caret:nth-child(1) {
	animation-delay: 0.36s;
	opacity: 0.35;
}

.fl-mobile-totop__caret:nth-child(2) {
	animation-delay: 0.18s;
	opacity: 0.6;
}

.fl-mobile-totop__caret:nth-child(3) {
	animation-delay: 0s;
}

@keyframes fl-totop-caret {
	0%,
	100% {
		opacity: 0.3;
		transform: translateY(0.35rem);
	}
	45% {
		opacity: 1;
		transform: translateY(0);
	}
	70% {
		opacity: 0.55;
		transform: translateY(-0.2rem);
	}
}

@media (prefers-reduced-motion: reduce) {
	.fl-mobile-totop__caret {
		animation: none;
		opacity: 1;
		transform: none;
	}
}

/* ---------------------------------------------------------------
 * Small screens
 * --------------------------------------------------------------- */

@media (max-width: 899px) {
	.fl-nav-toggle {
		display: inline-flex;
		align-items: center;
		justify-content: center;
	}

	.fl-site-header-collapse {
		display: none;
		flex-direction: column;
		align-items: flex-start;
		gap: 1.25rem;
		position: absolute;
		top: 100%;
		left: 0;
		right: 0;
		background: var(--fl-bg);
		border-bottom: 1px solid var(--fl-border);
		padding: 1.25rem 1.5rem 1.75rem;
		box-shadow: var(--fl-shadow-lg);
	}

	.fl-site-header-collapse.fl-nav-open {
		display: flex;
	}

	.fl-primary-menu {
		flex-direction: column;
		gap: 0.9rem;
	}

	.fl-header-controls {
		width: 100%;
		justify-content: space-between;
	}
}

@media (max-width: 600px) {
	.fl-card-grid {
		grid-template-columns: 1fr;
	}

	.fl-hero-arrow {
		display: none;
	}
}

/* ---------------------------------------------------------------
 * Preloader
 * --------------------------------------------------------------- */

body.fl-loading {
	overflow: hidden;
}

.fl-preloader {
	position: fixed;
	inset: 0;
	z-index: 9999;
	background: var(--fl-dark);
	display: flex;
	align-items: center;
	justify-content: center;
}

.fl-preloader-text {
	font-family: var(--fl-font-heading);
	font-size: clamp(1.5rem, 4vw, 2.5rem);
	font-weight: 700;
	letter-spacing: 0.04em;
	color: #f2f4fb;
	text-transform: uppercase;
	display: inline-block;
	overflow: hidden;
}

/* ---------------------------------------------------------------
 * Header scroll morph
 * --------------------------------------------------------------- */

.fl-site-header {
	transition: background-color 0.3s ease, box-shadow 0.3s ease, border-color 0.3s ease;
}

.fl-site-header-scrolled {
	box-shadow: var(--fl-shadow);
	border-bottom-color: transparent;
}

/* ---------------------------------------------------------------
 * Scroll-reveal masks (GSAP SplitText targets)
 * --------------------------------------------------------------- */

[data-reveal-text] {
	overflow: hidden;
}

.fl-split-line {
	overflow: hidden;
	display: block;
}

/* ---------------------------------------------------------------
 * Section badges ("01 [ Services ]")
 * --------------------------------------------------------------- */

.fl-section-badge {
	display: inline-flex;
	align-items: baseline;
	gap: 0.6rem;
	font-family: var(--fl-font-heading);
	font-size: 0.8rem;
	font-weight: 700;
	letter-spacing: 0.12em;
	text-transform: uppercase;
	color: var(--fl-accent);
	margin-bottom: 1.25rem;
}

.fl-section-badge-number {
	color: var(--fl-fg-muted);
	font-weight: 500;
}

/* ---------------------------------------------------------------
 * Hero: eyebrow, watermark, canvas, scroll cue
 * --------------------------------------------------------------- */

.fl-hero {
	position: relative;
}

.fl-hero-canvas {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	z-index: 0;
	pointer-events: none;
}

.fl-hero-watermark {
	position: absolute;
	top: 50%;
	left: 50%;
	transform: translate(-50%, -50%);
	font-family: var(--fl-font-heading);
	font-size: clamp(6rem, 22vw, 16rem);
	font-weight: 800;
	color: var(--fl-fg);
	opacity: 0.04;
	white-space: nowrap;
	pointer-events: none;
	z-index: 0;
	letter-spacing: -0.03em;
}

.fl-hero-eyebrow {
	text-transform: uppercase;
	letter-spacing: 0.14em;
	font-size: 0.8rem;
	font-weight: 700;
	color: var(--fl-accent);
	margin: 0 0 1rem;
}

.fl-hero-scroll-cue {
	position: absolute;
	bottom: 2rem;
	left: 50%;
	transform: translateX(-50%);
	width: 1px;
	height: 48px;
	overflow: hidden;
	z-index: 2;
}

.fl-hero-scroll-cue-line {
	display: block;
	width: 100%;
	height: 100%;
	background: linear-gradient(to bottom, transparent, var(--fl-accent) 50%, transparent);
	animation: fl-scroll-cue 1.8s ease-in-out infinite;
}

@keyframes fl-scroll-cue {
	0% { transform: translateY(-100%); }
	100% { transform: translateY(100%); }
}

@media (prefers-reduced-motion: reduce) {
	.fl-hero-scroll-cue-line { animation: none; }
}

/* ---------------------------------------------------------------
 * Glassmorphic cards + card hover arrow
 * --------------------------------------------------------------- */

.fl-card,
.fl-pricing-card,
.fl-calculator {
	backdrop-filter: blur(16px);
	-webkit-backdrop-filter: blur(16px);
}

/* Plain opaque cards - background/border just follow --fl-bg-raised/
 * --fl-border, which the [color-scheme] blocks above already repaint
 * per page type (light on the homepage, dark on internal pages), so
 * there's nothing further to condition here. */
.fl-card,
.fl-pricing-card,
.fl-calculator,
.fl-faq-item {
	background: var(--fl-bg-raised);
	border-color: var(--fl-border);
}

.fl-card {
	position: relative;
}

.fl-card-arrow {
	position: absolute;
	top: 1.25rem;
	right: 1.25rem;
	width: 2rem;
	height: 2rem;
	border-radius: 999px;
	background: var(--fl-accent-soft);
	color: var(--fl-accent);
	display: flex;
	align-items: center;
	justify-content: center;
	opacity: 0;
	transform: translate(-6px, 6px);
	transition: opacity 0.25s ease, transform 0.25s ease;
}

.fl-card-arrow svg {
	width: 16px;
	height: 16px;
}

.fl-card:hover .fl-card-arrow {
	opacity: 1;
	transform: translate(0, 0);
}

/* ---------------------------------------------------------------
 * Nav link hover fill + button arrow micro-interaction
 * --------------------------------------------------------------- */

.fl-primary-menu a {
	position: relative;
	padding-bottom: 2px;
}

.fl-primary-menu a::after {
	content: "";
	position: absolute;
	left: 0;
	bottom: -2px;
	width: 100%;
	height: 1px;
	background: currentColor;
	transform: scaleX(0);
	transform-origin: right;
	transition: transform 0.35s cubic-bezier(0.65, 0, 0.35, 1);
}

.fl-primary-menu a:hover::after {
	transform: scaleX(1);
	transform-origin: left;
}

[data-magnetic] {
	will-change: transform;
}

/* ---------------------------------------------------------------
 * Azurio chrome overrides (loads after main.min.css - see
 * fl_enqueue_assets()) - only the handful of rules main.min.css has no
 * equivalent for (a real logo upload, the language switcher) or where
 * Azurio's own default was tuned for far shorter copy than this site's
 * real admin-authored text (the hero outro line).
 * --------------------------------------------------------------- */

/* Logo: light/dark swap, keyed to Azurio's own color-scheme attribute -
 * "light" everywhere now (see header.php), so by default this shows the
 * light-mode (dark-colored) variant sitewide, which is correct for
 * every page's header text being dark now. Only matters once a
 * dark-mode logo variant is actually uploaded - see fl_azurio_logo_svg()
 * in functions.php, which only prints .fl-logo-dark at all when one is. */
:root:not([color-scheme="dark"]) .fl-logo-dark {
	display: none;
}

:root[color-scheme="dark"] .fl-logo-light {
	display: none;
}

/* The homepage header is the one exception (.mxd-header-permanent,
 * header.php) - it sits over the always-dark hero and stays white
 * regardless of the page's own light color-scheme, so its logo needs
 * the dark-mode (light-colored) variant instead of the sitewide
 * default, matching the same rule that keeps its text white. Needs the
 * ":root" prefix (not just ".mxd-header-permanent .fl-logo-light") to
 * actually win: the sitewide rules two blocks up are
 * ":root:not([color-scheme=dark]) .fl-logo-dark" (3 class/attribute
 * selectors) - a plain ".mxd-header-permanent .fl-logo-dark" (2) loses
 * to that on specificity regardless of source order, confirmed live (a
 * real logo pair showed the wrong, dark-on-dark variant on the
 * homepage until this was added). */
:root .mxd-header-permanent .fl-logo-light {
	display: none;
}

:root .mxd-header-permanent .fl-logo-dark {
	display: inline-flex;
}

/* fl-logo-solo: only one logo variant uploaded, no dark-mode counterpart
 * to swap to (fl_azurio_logo_svg(), functions.php) - a light pill behind
 * it on the homepage header specifically, the one place a plain image
 * can't otherwise be guaranteed to read against the always-dark hero
 * regardless of its own colors. Not applied on internal pages: their
 * header sits on a light body already, where an unmodified logo is
 * exactly as legible as it would be anywhere else on the page. */
:root .mxd-header-permanent .fl-logo-solo {
	background-color: rgba(255, 255, 255, 0.92);
	border-radius: 6px;
	padding: 0.4rem 0.6rem;
}

/* Language switcher (fl_language_switcher() in functions.php) - a real
 * button + dropdown panel now, not a native <select> (a second pass on
 * this - "the dropdown is awkward" - since a <select>'s own popup panel
 * can't be styled in any browser, which was the actual awkwardness no
 * amount of styling the closed control could fix). Styled with Azurio's
 * "permanent" tokens (--nl-white etc.) rather than the adaptive --t-x or
 * currentColor tokens main.min.css uses elsewhere - it renders in the
 * header (over the always-dark hero) and in the .mxd-menu overlay (also
 * always dark), so a fixed light-on-dark palette suits both. These rules
 * were global-ized (dropped the .mxd-header__controls prefix) when the
 * second instance was added to the menu - requested directly.
 *
 * Opens on :hover/:focus-within by default (works with zero JS, and
 * that includes keyboard - tabbing onto a link inside it satisfies
 * :focus-within); assets/js/language-switcher.js layers a click-to-
 * toggle .is-open class on top for touch, where hover doesn't apply. */
.fl-language-switcher {
	display: flex;
	align-items: center;
	position: relative;
}

/* Menu-overlay instance (header.php's .menu-language wrapper). Two
 * copies: --mobile at the top of .mxd-menu__left (above the nav),
 * --desktop in .mxd-menu__right above the contact info - same
 * mobile/desktop split the account buttons use, and the same 768px
 * breakpoint. The .mxd-menu overlay is always dark regardless of page
 * type, so this always wants the light-on-dark ("permanent" white)
 * treatment - it must beat the body:not(.home) dark-on-light override
 * further down (right for the header on an internal page, wrong inside
 * the always-dark overlay), hence the .mxd-menu .menu-language prefix.
 * Dropdown opens down-left so it stays inside its column. */
.menu-language--desktop {
	display: none;
	/* Tight to the contact info below - .menu-contact's own padding-top
	 * already supplies the gap; reported directly ("too much space
	 * between the switcher and the email"). */
	margin-bottom: 0.6rem;
}

.menu-language--mobile {
	margin-bottom: 0;
}

/* Mobile-only row pairing the language switcher with the Log In/Sign Up
 * buttons (header.php, .mxd-menu__left) - both used to be full-width
 * blocks stacked one under the other, with the buttons ending up below
 * the entire nav list ("the login and signup button is beneath the menu
 * items", requested directly to sit in the switcher's own row instead).
 * Empty/collapses to nothing at 768px+: both children are display:none
 * there (their own rules below/.fl-menu-account--mobile), so this never
 * shows on desktop, where .mxd-menu__right's separate copies already do
 * their own thing unchanged. flex-wrap:wrap is a safety net on very
 * narrow phones, not the intended layout - .fl-button padding/font-size
 * are trimmed below specifically in this row so the two buttons and the
 * switcher fit one line at ordinary phone widths. */
.mxd-menu__top-row {
	display: flex;
	align-items: center;
	justify-content: space-between;
	flex-wrap: wrap;
	gap: 1rem 1.2rem;
	margin-bottom: 2.4rem;
}

.mxd-menu__top-row .fl-menu-account--mobile {
	margin-top: 0;
}

.mxd-menu__top-row .fl-menu-account--mobile .fl-button {
	padding: 1rem 1.6rem;
	font-size: 1.3rem;
	white-space: nowrap;
}

@media only screen and (min-width: 768px) {
	.menu-language--mobile {
		display: none;
	}

	.menu-language--desktop {
		display: flex;
	}

	/* Trim the vendor's own oversized gap below the switcher/account
	 * buttons - part of the same "too much space" report. */
	.mxd-menu__right .menu-contact {
		padding-top: 2rem;
	}
}

.mxd-menu .menu-language .fl-language-select {
	background-color: rgba(255, 255, 255, 0.08);
	border-color: rgba(255, 255, 255, 0.28);
	color: var(--nl-white, #fff);
}

.mxd-menu .menu-language .fl-language-switcher:focus-within .fl-language-select,
.mxd-menu .menu-language .fl-language-switcher.is-open .fl-language-select {
	background-color: rgba(255, 255, 255, 0.16);
	border-color: rgba(255, 255, 255, 0.55);
}

@media (hover: hover) and (pointer: fine) {
	.mxd-menu .menu-language .fl-language-switcher:hover .fl-language-select {
		background-color: rgba(255, 255, 255, 0.16);
		border-color: rgba(255, 255, 255, 0.55);
	}
}

.mxd-menu .menu-language .fl-language-dropdown {
	right: auto;
	left: 0;
	background-color: var(--nl-black, #0f0f0f);
	border-color: rgba(255, 255, 255, 0.16);
	box-shadow: 0 20px 48px rgba(0, 0, 0, 0.45);
}

.mxd-menu .menu-language .fl-language-dropdown__link {
	color: rgba(255, 255, 255, 0.75);
}

.mxd-menu .menu-language .fl-language-dropdown__link:hover,
.mxd-menu .menu-language .fl-language-dropdown__link:focus-visible,
.mxd-menu .menu-language .fl-language-dropdown__link.is-current {
	color: var(--nl-white, #fff);
	background-color: rgba(255, 255, 255, 0.1);
}

.fl-language-select {
	display: flex;
	align-items: center;
	gap: 0.9rem;
	background-color: rgba(255, 255, 255, 0.08);
	border: 1px solid rgba(255, 255, 255, 0.28);
	border-radius: 100px;
	box-shadow: 0 1px 0 rgba(255, 255, 255, 0.04) inset;
	color: var(--nl-white, #fff);
	cursor: pointer;
	font: normal 600 1.3rem/1.6 var(--_font-accent, inherit);
	letter-spacing: 0.06rem;
	padding: 0.85rem 1.6rem;
	text-transform: uppercase;
	transition: border-color var(--_animspeed-medium, 0.3s), background-color var(--_animspeed-medium, 0.3s);
}

.fl-language-select__icon {
	width: 1.4rem;
	height: 1.4rem;
	flex: 0 0 auto;
}

.fl-language-select__chevron {
	width: 1.1rem;
	height: 1.1rem;
	flex: 0 0 auto;
	transition: transform var(--_animspeed-medium, 0.3s);
}

.fl-language-switcher:focus-within .fl-language-select,
.fl-language-switcher.is-open .fl-language-select {
	background-color: rgba(255, 255, 255, 0.16);
	border-color: rgba(255, 255, 255, 0.55);
}

.fl-language-switcher:focus-within .fl-language-select__chevron,
.fl-language-switcher.is-open .fl-language-select__chevron {
	transform: rotate(180deg);
}

/* :hover split out from the :focus-within/.is-open rules above (and the
 * dropdown-visibility one further down) and gated to real pointer
 * devices only - iOS Safari simulates a "sticky hover" on tap that only
 * clears when a *different* element is next touched, never by tapping
 * the same one again. With a bare :hover in the mix, tapping the
 * switcher button a second time correctly removed the JS is-open class
 * (language-switcher.js) but the phantom :hover state kept matching
 * regardless, so the panel never actually closed except by tapping
 * elsewhere (reported directly - confirmed it wasn't a focus issue,
 * since iOS Safari doesn't even focus plain <button> elements on tap in
 * the first place, a separate well-known WebKit behavior). (hover:hover)
 * and (pointer:fine) together are the standard way to ask "does a real
 * mouse/trackpad exist", true on desktop, false on touchscreens -
 * leaving the JS click-to-toggle as the only mechanism there, which is
 * exactly what it was already built for. */
@media (hover: hover) and (pointer: fine) {
	.fl-language-switcher:hover .fl-language-select {
		background-color: rgba(255, 255, 255, 0.16);
		border-color: rgba(255, 255, 255, 0.55);
	}

	.fl-language-switcher:hover .fl-language-select__chevron {
		transform: rotate(180deg);
	}
}

.fl-language-select:focus-visible {
	border-color: var(--nl-white, #fff);
	outline: none;
}

/* The panel itself: absolutely positioned, actually drops downward below
 * the button (requested directly), hidden via opacity/visibility rather
 * than display so the CSS-only :hover/:focus-within trigger keeps
 * working and the transform can animate. */
.fl-language-dropdown {
	position: absolute;
	top: calc(100% + 0.8rem);
	right: 0;
	z-index: 20;
	min-width: 100%;
	margin: 0;
	padding: 0.6rem;
	list-style: none;
	background-color: var(--nl-black, #0f0f0f);
	border: 1px solid rgba(255, 255, 255, 0.16);
	border-radius: 1.2rem;
	box-shadow: 0 20px 48px rgba(0, 0, 0, 0.45);
	opacity: 0;
	visibility: hidden;
	transform: translateY(-6px);
	transition: opacity var(--_animspeed-medium, 0.3s), transform var(--_animspeed-medium, 0.3s), visibility var(--_animspeed-medium, 0.3s);
	/* main.min.css has a bare, unscoped "ul{display:flex;flex-direction:
	 * column}" reset (several copies, different breakpoints) with no
	 * equivalent specificity override anywhere in this file for this
	 * list specifically - explicit here so this panel's layout doesn't
	 * depend on which of those happens to be in scope. */
	display: block;
}

/* main.min.css also has a bare, unscoped "li{display:inline-flex}" reset
 * - with no width/height of its own, each <li role="option"> became a
 * flex container wrapping another flex container
 * (.fl-language-dropdown__link) that itself has a hidden flex child
 * (the label span, display:none on mobile) - exactly the kind of nested
 * flex-with-a-hidden-child shape real-device WebKit has known sizing
 * quirks around (reported directly: the flag "shrinked" inside a much
 * larger tile on a real phone, not reproduced in either Chrome or a
 * desktop WebKit build). Pinning the <li> to a plain block box removes
 * that nested-flex shape entirely rather than trying to out-guess which
 * specific quirk is responsible. */
.fl-language-dropdown li {
	display: block;
	margin: 0;
	padding: 0;
}

.fl-language-dropdown__link {
	width: 100%;
}

.fl-language-switcher:focus-within .fl-language-dropdown,
.fl-language-switcher.is-open .fl-language-dropdown {
	opacity: 1;
	visibility: visible;
	transform: translateY(0);
}

@media (hover: hover) and (pointer: fine) {
	.fl-language-switcher:hover .fl-language-dropdown {
		opacity: 1;
		visibility: visible;
		transform: translateY(0);
	}
}

.fl-language-dropdown__link {
	display: block;
	border-radius: 0.7rem;
	padding: 0.9rem 1.2rem;
	color: rgba(255, 255, 255, 0.75);
	font: normal 600 1.3rem/1.4 var(--_font-accent, inherit);
	letter-spacing: 0.04rem;
	text-transform: uppercase;
	text-decoration: none;
	white-space: nowrap;
	transition: background-color var(--_animspeed-fast, 0.15s), color var(--_animspeed-fast, 0.15s);
}

.fl-language-dropdown__link:hover,
.fl-language-dropdown__link:focus-visible {
	background-color: rgba(255, 255, 255, 0.1);
	color: var(--nl-white, #fff);
	outline: none;
}

.fl-language-dropdown__link.is-current {
	color: var(--nl-white, #fff);
	background-color: rgba(255, 255, 255, 0.06);
}

.fl-language-dropdown__link {
	display: flex;
	align-items: center;
	gap: 0.9rem;
}

/* Flag icons (fl_flag_svg(), functions.php) - shown everywhere now,
 * desktop included (requested directly - "the globe icon should be
 * replaced with the flag icons... in the desktop or larger screens";
 * mobile already showed flags from an earlier request, this just makes
 * the two consistent instead of desktop being the one screen size still
 * showing the plain globe). The generic globe glyph is hidden
 * unconditionally below rather than only past a breakpoint - CSS-only
 * swap (matches the switcher's own "needs no JS to function"
 * philosophy above), both render server-side and CSS just decides which
 * one paints. The dropdown link's aria-label keeps the full language
 * name available to assistive tech regardless. */
.fl-language-select__icon {
	display: none;
}

.fl-language-select__flag,
.fl-language-dropdown__flag {
	display: block;
	width: 2rem;
	height: 1.5rem;
	flex: 0 0 auto;
	object-fit: cover;
	border-radius: 0.3rem;
}

@media (max-width: 768px) {
	/* The text label still only fits comfortably next to a flag on a
	 * wider header bar - mobile keeps collapsing to flag + chevron only,
	 * same reasoning/values as before this round. */
	.fl-language-select__current,
	.fl-language-dropdown__label {
		display: none;
	}

	.fl-language-select {
		gap: 0.6rem;
		padding: 0.7rem 1.1rem;
	}

	/* Dropdown flag: grow to fill the link's own width instead of
	 * staying pinned at 2rem - confirmed directly, by screenshot, that
	 * the link itself (.fl-language-dropdown__link, min-width:100%
	 * chains up from the panel to the trigger button) is wider than a
	 * single fixed-width flag + its now-hidden label needs, leaving a
	 * visibly empty gap next to the flag inside each tile. "I want the
	 * img to be able to occupy similar width occupied as the a tag" -
	 * flex:1 1 auto (not 0 0 auto) plus width:auto lets it grow into
	 * exactly that leftover space; object-fit:cover (base rule above)
	 * keeps the flag artwork filling the resulting box cleanly at
	 * whatever width that ends up being, cropping rather than
	 * distorting. Scoped to this breakpoint specifically - reported
	 * directly that applying it unconditionally also puffed the flag
	 * out wider than normal on desktop, where the label is still
	 * visible and the flag isn't meant to be the only thing filling the
	 * tile's width. The trigger's own flag (.fl-language-select__flag)
	 * is untouched everywhere - only ever reported on the dropdown's
	 * tiles, not the trigger pill. */
	.fl-language-dropdown__flag {
		width: auto;
		flex: 1 1 auto;
	}
}

/* Preloader images: main.min.css sizes/crops these for full-bleed
 * sample photos (object-fit:cover) - swapped for the tech-stack icon
 * set (requested directly), so they get object-fit:contain and some
 * breathing room plus a faint tile background instead, or a small
 * transparent-background SVG gets stretched and cropped illegibly. */
.mxd-loader__images img {
	object-fit: contain;
	box-sizing: border-box;
	padding: 4.5rem;
	background-color: rgba(255, 255, 255, 0.06);
}

/* Header: transparent everywhere (requested directly - "the header
 * remains transparent"), matching Azurio's own design (.mxd-header is
 * position:absolute with no background of its own). Its own text/icon
 * color needs no override any more: color-scheme is "light" sitewide
 * (header.php), so .mxd-logo/.mxd-header__link's adaptive --t-bright
 * already resolves dark on every page - except the homepage, which
 * sits over the always-dark hero and stays white via
 * .mxd-header-permanent's own hardcoded color, unrelated to
 * color-scheme. (An earlier pass scoped a --t-bright override to
 * body:not(.home) here, back when color-scheme was "dark" sitewide and
 * only the header was carved out light - that's now backwards: light is
 * the sitewide default and only the footer is carved out dark, see
 * .fl-footer-dark further down - so this rule became redundant and was
 * removed rather than left dead.) */
.mxd-header {
	background-color: transparent;
}

/* Safari-only: reported the header (logo/controls, both .loading-fade)
 * sometimes stays invisible on page load until the cursor moves - a
 * known WebKit bug where an element only gets promoted to its own
 * compositor layer *during* a GSAP opacity tween (app.min.js's
 * pageAppearance(), which animates .loading-fade/.loading-item from
 * opacity:0) and Safari occasionally fails to paint that layer until
 * something else forces a repaint (a mousemove, in this case). Forcing
 * the layer to exist *before* the animation starts - via a no-op 3D
 * transform - is the standard fix: it makes the promotion happen at
 * page load instead of mid-tween, so there's nothing left for Safari to
 * miss painting. Harmless on other browsers (already-composited layers
 * ignore this). Scoped to the elements this was reported on (header)
 * plus the .loading-fade/.loading-item/.loading-split classes generally,
 * since every inner page's headline block uses the same reveal. */
.mxd-header,
.mxd-header__logo,
.mxd-header__controls,
.loading-fade,
.loading-item,
.loading-split {
	-webkit-transform: translateZ(0);
	transform: translateZ(0);
	-webkit-backface-visibility: hidden;
	backface-visibility: hidden;
}

/* Same Safari fix, footer links this time: reported unclickable until
 * their .mxd-scramble text-rotate reveal finishes ("except maybe the
 * text have finished its rotating effect") - consistent with the same
 * compositor-layer-created-mid-animation cause as the header above,
 * just triggered by ScrollTrigger-on-scroll-into-view here instead of
 * page load, which is why it's the footer that gets reported (usually
 * off-screen and still animating in when a fast-scrolling Safari user
 * reaches for it) rather than the always-early-visible header nav. */
.footer-nav-v01__item,
.mxd-scramble,
.anim-uni-slide-down,
.anim-uni-slide-up {
	-webkit-transform: translateZ(0);
	transform: translateZ(0);
	-webkit-backface-visibility: hidden;
	backface-visibility: hidden;
}

/* Root cause, found by inspecting the live computed styles directly
 * (reported: setting the background-color to white in DevTools made it
 * render BLACK, and vice versa - a dead giveaway): main.min.css puts
 * "mix-blend-mode: difference" on .mxd-menu__contain (the hamburger's
 * own fixed-position wrapper, a sibling of <header> - not a descendant
 * of .mxd-header, so a selector scoped under ".mxd-header" would never
 * have matched it either way), unconditionally, on every page. That's
 * a deliberate homepage trick - the hamburger floats over a video/image
 * hero there and needs to auto-contrast against whatever scrolls
 * beneath it. On internal pages the header is a plain solid-white bar,
 * where that same blend mode does the opposite of what's wanted: the
 * rendered color becomes the *difference* between the line's own
 * background-color and white behind it, so a dark #121212 line
 * (255-18=237 per channel) displays as near-white, and - confirmed
 * directly - a white line displays as black. No background-color value
 * could ever have fixed this; the blend mode itself had to go. */
body:not(.home) .mxd-menu__contain {
	mix-blend-mode: normal !important;
}

body:not(.home) .mxd-menu__hamburger:not(.active) .hamburger__line {
	/* Hardcoded to the "permanent" white token in main.min.css rather
	 * than the adaptive one .mxd-logo/.mxd-header__link/
	 * .mxd-color-switcher use, so it needs its own override rather than
	 * following --t-bright.
	 *
	 * :not(.active) - the open/X state needs to stay the vendor's own
	 * unconditional white on every page (the full-screen menu overlay
	 * behind it never changes with page type) - confirmed live as a
	 * real bug once mix-blend-mode was still "difference": opening the
	 * menu left the X the same dark color as the closed hamburger,
	 * illegible against the overlay's own always-dark backdrop. */
	background-color: var(--t-bright--light, #121212) !important;
}

/* Language switcher on internal pages: built with fixed white/permanent
 * colors (see its own doc comment further down), on purpose, so it
 * looks the same everywhere regardless of a page's own color-scheme -
 * fine on the homepage, which needs exactly that (white, over the
 * always-dark hero), but wrong on internal pages, which are light
 * throughout and need this dark-on-light treatment instead. Scoped to
 * internal pages only; the homepage keeps the component's own default. */
body:not(.home) .fl-language-select {
	background-color: rgba(0, 0, 0, 0.05);
	border-color: rgba(0, 0, 0, 0.18);
	color: var(--t-bright--light, #121212);
}

body:not(.home) .fl-language-switcher:focus-within .fl-language-select,
body:not(.home) .fl-language-switcher.is-open .fl-language-select {
	background-color: rgba(0, 0, 0, 0.09);
	border-color: rgba(0, 0, 0, 0.35);
}

@media (hover: hover) and (pointer: fine) {
	body:not(.home) .fl-language-switcher:hover .fl-language-select {
		background-color: rgba(0, 0, 0, 0.09);
		border-color: rgba(0, 0, 0, 0.35);
	}
}

body:not(.home) .fl-language-select:focus-visible {
	border-color: var(--t-bright--light, #121212);
}

body:not(.home) .fl-language-dropdown {
	background-color: #ffffff;
	border-color: rgba(0, 0, 0, 0.12);
	box-shadow: 0 20px 48px rgba(0, 0, 0, 0.16);
}

body:not(.home) .fl-language-dropdown__link {
	color: rgba(0, 0, 0, 0.7);
}

body:not(.home) .fl-language-dropdown__link:hover,
body:not(.home) .fl-language-dropdown__link:focus-visible {
	background-color: rgba(0, 0, 0, 0.06);
	color: #000000;
}

body:not(.home) .fl-language-dropdown__link.is-current {
	color: #000000;
	background-color: rgba(0, 0, 0, 0.04);
}

/* ---------------------------------------------------------------
 * Browser-language suggestion bar (template-parts/language-suggestion.php
 * + assets/js/language-suggestion.js). Bottom-anchored, non-blocking,
 * shown at most once. 1rem = 10px on this theme.
 * --------------------------------------------------------------- */

.fl-lang-suggest {
	position: fixed;
	left: 0;
	right: 0;
	bottom: 0;
	z-index: 9000;
	background: var(--fl-dark, #0f0f0f);
	color: #fff;
	transform: translateY(100%);
	transition: transform 0.25s ease;
	box-shadow: 0 -8px 30px rgba(0, 0, 0, 0.25);
}

.fl-lang-suggest.is-visible {
	transform: translateY(0);
}

.fl-lang-suggest[hidden] {
	display: none;
}

.fl-lang-suggest__inner {
	max-width: 96rem;
	margin: 0 auto;
	padding: 1.4rem 2rem;
	display: flex;
	align-items: center;
	gap: 1.4rem;
	flex-wrap: wrap;
}

/* Icon+text wrapper (template-parts/language-suggestion.php) -
 * display:contents on desktop means it generates no box of its own,
 * so .fl-lang-suggest__icon/__text remain plain direct flex children
 * of .fl-lang-suggest__inner exactly as before this wrapper existed;
 * only the mobile breakpoint below turns it into a real flex box, to
 * center its own content. */
.fl-lang-suggest__message {
	display: contents;
}

.fl-lang-suggest__icon {
	width: 2.2rem;
	height: 2.2rem;
	flex: none;
	opacity: 0.85;
}

.fl-lang-suggest__text {
	margin: 0;
	flex: 1 1 20rem;
	font-size: 1.5rem;
	line-height: 1.4;
}

.fl-lang-suggest__accept {
	flex: none;
	display: inline-flex;
	align-items: center;
	padding: 0.9rem 1.8rem;
	border-radius: var(--fl-radius, 8px);
	background: var(--fl-accent, #0e686c);
	color: var(--fl-accent-fg, #fff);
	font-size: 1.4rem;
	font-weight: 700;
	text-decoration: none;
	transition: filter 0.15s ease;
}

.fl-lang-suggest__accept:hover,
.fl-lang-suggest__accept:focus-visible {
	filter: brightness(1.12);
	color: var(--fl-accent-fg, #fff);
	text-decoration: none;
}

.fl-lang-suggest__dismiss {
	flex: none;
	width: 3.2rem;
	height: 3.2rem;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: none;
	background: transparent;
	color: rgba(255, 255, 255, 0.7);
	cursor: pointer;
	border-radius: 50%;
}

.fl-lang-suggest__dismiss svg {
	width: 1.6rem;
	height: 1.6rem;
}

.fl-lang-suggest__dismiss:hover,
.fl-lang-suggest__dismiss:focus-visible {
	background: rgba(255, 255, 255, 0.12);
	color: #fff;
}

@media (max-width: 600px) {
	.fl-lang-suggest__inner {
		padding: 1.2rem 1.4rem;
		gap: 1rem;
	}

	.fl-lang-suggest__accept {
		flex: 1 1 100%;
		justify-content: center;
		order: 3;
	}

	/* Moved to the start of the row (left) instead of its default
	 * trailing position (right) - reported directly ("the x button on
	 * the right in mobile is not very visible, especially due to the
	 * fact that the chatbot image is there"): the dismiss button's
	 * natural right-edge position sits right where the Converso AI
	 * widget launcher floats (bottom-right corner), fighting it for
	 * visibility/tap space. Desktop is untouched ("well placed and
	 * very beautiful") - this order override only applies inside this
	 * mobile breakpoint. */
	.fl-lang-suggest__dismiss {
		order: -1;
	}

	/* Left-aligned (not centered - reverted per direct follow-up:
	 * "i no longer really want it on the middle, rather on the left"),
	 * with a deliberate gap from the dismiss button so the two don't
	 * read as one tap target ("add a marginal space from the X button
	 * so it doesn't seem too attached"). */
	.fl-lang-suggest__message {
		display: flex;
		align-items: center;
		gap: 1rem;
		flex: 1 1 auto;
		min-width: 0;
		margin-left: 1.2rem;
	}
}

/* Hero: an explicit dark background under the video/cover layers -
 * neither has one of its own in main.min.css, so anything that isn't
 * fully painted yet (video still buffering its first frame, a
 * compositing frame dropped during the pinned-scroll animation) would
 * otherwise show the page's own light-mode background (--base, a cream
 * near-white) through the gap - jarring against an intentionally dark
 * hero. Belt-and-suspenders fix for the "white flash while scrolling
 * through the hero" report. */
.mxd-hero-section,
.mxd-hero-02 {
	background-color: var(--base-opp, #0f0f0f);
}

/* Hero outro line: main.min.css sizes .mxd-hero-02__outro p for a short
 * 5-6 word tagline (up to 9.5rem/-0.24rem tracking) - this site's real
 * copy (Homepage > Hero > Subtitle) is a full sentence, so it gets its
 * own scale instead of overflowing the hero, set to the font's boldest
 * weight for more presence. Sized to match the hero title exactly now
 * (requested directly - "make the hero subtitle font size to be same as
 * the hero title size"). The title's *real* rendered size isn't just
 * h1.medium's own three breakpoints (6/8.5/12rem) - a more specific
 * ".mxd-hero-02__intro h1" rule (main.min.css) steps it through a fourth
 * value in between, 9.5rem at 1200px, only reaching 12rem at 1600px+ -
 * confirmed live (getComputedStyle at 1440px width read 9.5rem, not
 * 12rem, the first time this was matched to the wrong three-value
 * scale). This mirrors that same four-value schedule exactly instead:
 * 6/8.5/9.5/12rem. */
.mxd-hero-02__outro p {
	font-size: 6rem;
	font-weight: 800;
	letter-spacing: normal;
}

@media only screen and (min-width: 768px) {
	.mxd-hero-02__outro p {
		font-size: 8.5rem;
	}
}

@media only screen and (min-width: 1200px) {
	.mxd-hero-02__outro p {
		font-size: 9.5rem;
	}
}

@media only screen and (min-width: 1600px) {
	.mxd-hero-02__outro p {
		font-size: 12rem;
	}
}

/* CEO strip (requested directly) - a thin strip under the Strategy/
 * Design/Development process-point cards: a circular CEO photo with a
 * quote to its right. Not part of Azurio's own component set, so it's
 * custom CSS rather than an existing .mxd-* class - built from the same
 * tokens the process-point cards right above it already use
 * (--pt-t-accent-*, via the .accent/.t-accent classes) so it reads as
 * part of the same blue section, not a bolted-on block. The photo is
 * sized well past a typical small avatar specifically so a circular
 * portrait actually reads as one at this width, per "height visible
 * enough to make the CEO image display properly in the circle". */
.fl-ceo-strip {
	display: flex;
	align-items: center;
	gap: 2.4rem;
	/* Pushed down well past the 3 process-point cards above it, rather
	 * than sitting immediately under them (requested directly - "bring
	 * the ceo area closer to the end of the about section, instead of
	 * just right below the 3 cards area"). It's already the last block
	 * in this section, so there's nothing to reorder past - the fix is
	 * distance: enough top margin that it reads as its own closing
	 * element near the section's bottom edge, not an extension of the
	 * cards' own grid. */
	margin-top: 9rem;
	/* Was a flat "border-top" divider line - removed (requested
	 * directly). In its place, the strip reads as its own raised card
	 * instead ("make the beginning of the ceo area to feel like it has
	 * some shadow elevation") - padding + a faint translucent panel +
	 * box-shadow, rather than just a shadow with nothing to cast it on
	 * (a shadow alone on a flush-full-width strip wouldn't read as
	 * "elevated" - it needs an actual edge to lift off the section's
	 * flat teal background from). */
	padding: 2.4rem 2.8rem;
	background: rgba(255, 255, 255, 0.06);
	border-radius: var(--fl-radius-lg, 16px);
	box-shadow: 0 20px 50px rgba(0, 0, 0, 0.25), 0 4px 14px rgba(0, 0, 0, 0.18);
}

@media only screen and (max-width: 767px) {
	.fl-ceo-strip {
		flex-direction: column;
		align-items: flex-start;
		text-align: left;
	}
}

.fl-ceo-strip__photo {
	flex: 0 0 auto;
	width: 8rem;
	height: 8rem;
	border-radius: 50%;
	overflow: hidden;
}

@media only screen and (min-width: 768px) {
	.fl-ceo-strip__photo {
		width: 11rem;
		height: 11rem;
	}
}

.fl-ceo-strip__photo img {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.fl-ceo-strip__quote {
	flex: 1 1 auto;
	min-width: 0;
}

.fl-ceo-strip__text {
	font: normal 500 1.8rem/1.4 var(--_font-default, inherit);
	color: var(--pt-t-accent-bright, #fff);
	margin: 0 0 0.8rem;
}

@media only screen and (min-width: 768px) {
	.fl-ceo-strip__text {
		font-size: 2.2rem;
	}
}

.fl-ceo-strip__author {
	font: normal 600 1.3rem/1.6 var(--_font-accent, inherit);
	letter-spacing: 0.05rem;
	text-transform: uppercase;
	margin: 0;
}

.fl-ceo-strip__author span {
	display: block;
	font-weight: 400;
	letter-spacing: normal;
	text-transform: none;
	margin-top: 0.2rem;
}

/* Standalone CEO-strip section (template-parts/ceo-strip.php, used on
 * the project archive page and anywhere else this gets dropped) - own
 * compact top/bottom padding rather than main.min.css's 14-20rem
 * responsive default-section scale, which is sized for a full content
 * section, not a single thin strip. --fl-accent directly, not
 * .bg-color-accent (see the file's own doc comment on why). The strip's
 * own margin-top: 9rem (above) exists to distance it from the process-
 * point cards immediately above it *inside* the homepage's #about
 * section - meaningless here where this section's own padding-top
 * already provides that clearance, so it's zeroed only in this context. */
.fl-ceo-strip-section {
	padding-top: 6rem;
	padding-bottom: 6rem;
	background-color: var(--fl-accent);
}

.fl-ceo-strip-section .fl-ceo-strip {
	margin-top: 0;
}

/* Pricing: main.min.css gives pricing cards zero column gap (Bootstrap's
 * .row.g-0) and no clearance between the section heading and the first
 * card's "Most Popular" tag (which deliberately floats above the card by
 * -1.6rem - fine only when the heading block above has its own bottom
 * margin, which our centered heading variant here doesn't). Padding
 * lives on the item (not a row gap) so it stays inside each column's own
 * width instead of pushing the 3-column row wider than 100%. */
.mxd-pricing-table {
	margin-top: 5.5rem;
}

.mxd-pricing-table__item {
	box-sizing: border-box;
	padding: 0 1.5rem;
}

/* Pricing card redesign (template-parts/pricing-card.php) - requested
 * directly ("how can we redesign the solution pricing cards to look
 * more professional"). The vendor card (main.min.css) is a flat,
 * borderless, shadowless block (background-color: var(--base-tint),
 * nothing else) with an inverted hierarchy - the plan NAME renders at
 * 4-5rem bold (.pricing-header__title, main.min.css) while the PRICE
 * itself carries no font-size of its own - confirmed directly, not a
 * guess. This gives it an actual card (border/shadow/radius, lift on
 * hover), fixes that hierarchy so the price reads as the headline, and
 * turns the CTA into a solid accent button (was plain outline) - same
 * treatment .fl-detail-cta .btn already established elsewhere on the
 * site for a "this is the one action" button. */
.mxd-pricing-table__inner {
	border: 1px solid var(--fl-border, #e4e7f0);
	border-radius: var(--fl-radius-lg, 16px);
	box-shadow: var(--fl-shadow, 0 1px 2px rgba(18, 22, 42, 0.04), 0 8px 24px rgba(18, 22, 42, 0.06));
	transition: transform var(--_animspeed-medium, 0.3s), box-shadow var(--_animspeed-medium, 0.3s);
}

.no-touch .mxd-pricing-table__inner:hover {
	transform: translateY(-0.4rem);
	box-shadow: var(--fl-shadow-lg, 0 20px 60px rgba(18, 22, 42, 0.14));
}

/* The featured plan stands out on its own merits (border/shadow/scale),
 * not just the badge above it - fl-pricing-featured, set conditionally
 * in pricing-card.php (fl_plan_featured meta). */
.fl-pricing-featured {
	border-color: var(--fl-accent, #0e686c);
	box-shadow: 0 20px 50px color-mix(in srgb, var(--fl-accent, #0e686c) 20%, transparent);
}

@media only screen and (min-width: 1200px) {
	.fl-pricing-featured {
		transform: scale(1.04);
	}

	.no-touch .fl-pricing-featured:hover {
		transform: scale(1.04) translateY(-0.4rem);
	}
}

/* "Most Popular" badge - a real chip (same pill/border/soft-fill
 * treatment .fl-badge established elsewhere) instead of the vendor's
 * plain accent-text tag. Kept straddling the card's own top edge
 * (negative top, the vendor's own original positioning) rather than
 * moved fully inside it - "the badge overlaps the card text", reported
 * directly: the card's own header content starts right at its top
 * padding, so a badge positioned *inside* that area (a previous pass
 * here moved it to top: 1.6rem) has nothing to have moved out of the
 * way there and sits on top of the plan name/icon instead. Sitting
 * above the card entirely avoids that regardless of what the card's own
 * top padding happens to be. */
.mxd-pricing-table__tag {
	top: -1.4rem;
	left: 2.4rem;
}

.mxd-pricing-table__tag .tag {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	padding: 0.6rem 1.4rem;
	border-radius: 100px;
	background: var(--fl-accent, #0e686c);
	color: #ffffff;
}

/* Plan name de-emphasised (was the largest, boldest text on the card -
 * see this rule's own doc comment above); price promoted to the
 * card's actual headline. */
.pricing-header__title {
	margin-bottom: 0.6rem;
	font-size: 1.6rem;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: 0.04rem;
	color: var(--fl-fg-muted, #5b6178);
}

.pricing-data__num {
	font-size: 4rem;
	font-weight: 800;
	color: var(--fl-fg, #12162a);
}

.pricing-data__period {
	color: var(--fl-fg-muted, #5b6178);
}

/* Checklist - accent-tinted checkmarks instead of the vendor's muted
 * grey, and a plain accent-coloured caption instead of a bare heading. */
.pricing-plan__caption {
	color: var(--fl-fg-muted, #5b6178);
}

.mxd-check-list li svg {
	fill: var(--fl-accent, #0e686c);
}

/* Primary CTA - solid accent pill instead of the vendor's plain outline
 * button, so it reads as the one clear action on the card. */
.pricing-data__btnholder .btn.btn-default-outline {
	border-color: var(--fl-accent, #0e686c);
	background-color: var(--fl-accent, #0e686c);
	color: #ffffff;
}

.pricing-data__btnholder .btn.btn-default-outline i {
	background-color: rgba(255, 255, 255, 0.18);
}

.pricing-data__btnholder .btn.btn-default-outline i svg {
	fill: #ffffff;
}

.no-touch .pricing-data__btnholder .btn.btn-default-outline:hover {
	background-color: color-mix(in srgb, var(--fl-accent, #0e686c) 85%, black);
	border-color: color-mix(in srgb, var(--fl-accent, #0e686c) 85%, black);
}

/* Product page's own tier picker (template-parts/product-pricing-tiers.php)
 * - scoped to #fl-pricing-tiers rather than the bare .pricing-data__header/
 * .fl-section-heading classes, which pricing-card.php and every other
 * section heading on the site also use - these rules must not change any
 * of those. "Choose your plan" larger and centered, and each card's own
 * icon (requested directly): a small one beside the plan name, and a
 * large, low-opacity watermark version of the same glyph behind the
 * card's content. */
#fl-pricing-tiers {
	/* The "View pricing" button (detail-gallery-specs.php) jumps straight
	 * here via location.hash - without this, the browser's native anchor
	 * scroll lands the section flush against the very top of the
	 * viewport, slicing the heading's own ascenders off (confirmed live,
	 * screenshotted). A fixed header (position:absolute, not sticky -
	 * see header.php) isn't in play here, this is purely visual
	 * breathing room. */
	scroll-margin-top: 2.5rem;
}

#fl-pricing-tiers .fl-section-heading {
	font-size: clamp(2.2rem, 4vw, 3.2rem);
	text-align: center;
	max-width: 36ch;
	margin-left: auto;
	margin-right: auto;
}

#fl-pricing-tiers .mxd-pricing-table__inner {
	overflow: hidden;
}

#fl-pricing-tiers .mxd-pricing-table__data,
#fl-pricing-tiers .mxd-pricing-table__plan,
#fl-pricing-tiers .mxd-pricing-table__tag {
	position: relative;
	z-index: 1;
}

#fl-pricing-tiers .fl-pricing-tier-icon-bg {
	position: absolute;
	top: 50%;
	left: 50%;
	transform: translate(-50%, -50%);
	font-size: 13rem;
	line-height: 1;
	color: var(--fl-accent, #0e686c);
	opacity: 0.06;
	pointer-events: none;
	z-index: 0;
}

#fl-pricing-tiers .pricing-data__header {
	flex-direction: row;
	align-items: center;
	justify-content: space-between;
	gap: 1rem;
}

#fl-pricing-tiers .fl-pricing-tier-icon {
	flex-shrink: 0;
	font-size: 1.8rem;
	color: var(--fl-accent, #0e686c);
}

/* "View All Solutions" beneath the pricing cards (template-parts/
 * homepage/pricing.php) - requested directly. */
.fl-view-all-cta {
	margin-top: 4rem;
	text-align: center;
}

/* Testimonials grid: same zero-column-gap gap (Bootstrap's .row.g-0) as
 * the pricing cards above - same fix, item-level padding rather than a
 * row gap. */
.fl-testimonial-col {
	box-sizing: border-box;
	padding: 0 1.5rem;
}

/* Vertical gap between wrapped rows - main.min.css's own
 * ".mxd-testimonials-card{margin-top:3rem}" (and the 768px+/1200px+
 * variants of it) never actually applies: a later, unscoped
 * ".mxd-testimonials-card{margin:0}" rule further down the same
 * stylesheet (base styling for its OWN slider/carousel variant of this
 * component, ".mxd-testimonials-card.slider-card" - this site doesn't
 * use it) wins on source order at every width, zeroing it back out for
 * the plain grid variant too. Confirmed live (computed margin-top: 0px
 * on every card) - reported directly as "no padding between them in
 * mobile", where col-12 stacks every card in its own row so a missing
 * *vertical* gap is fully exposed (at 2-up/3-up widths any missing gap
 * is masked whenever there's exactly one row). Set here on the column,
 * not the card, so it doesn't need to out-specify that vendor rule at
 * all; :not(:last-child) so the grid's very last card doesn't add
 * trailing space before the section's own bottom padding. */
.fl-testimonial-col:not(:last-child) {
	margin-bottom: 3rem;
}

/* Testimonial cards - a flat rectangle in the same tint as the section
 * background (main.min.css gives them only padding/margin, no border,
 * radius or shadow), so on a real render they barely read as separate
 * cards at all next to the vivid Featured Projects showcase just above
 * them on the homepage ("make the... homepage [testimonials] section
 * more professional" audit, screenshotted live). Same elevated-card
 * treatment already established sitewide (.mxd-pricing-table__inner,
 * .fl-list-row, ...) - border + radius + shadow, hover lift on
 * non-touch. Unscoped (not just .fl-force-light's homepage instance) so
 * archive-fl_testimonial.php's own dark-mode grid of the same cards
 * gets it too - these --fl-* tokens are already the fixed, non-theme-
 * aware values every other card component on the site uses regardless
 * of light/dark section. */
.mxd-testimonials-card {
	border: 1px solid var(--fl-border, #e4e7f0);
	border-radius: var(--fl-radius-lg, 16px);
	box-shadow: var(--fl-shadow, 0 1px 2px rgba(18, 22, 42, 0.04), 0 8px 24px rgba(18, 22, 42, 0.06));
	transition: transform var(--_animspeed-medium, 0.3s), box-shadow var(--_animspeed-medium, 0.3s);
}

.no-touch .mxd-testimonials-card:hover {
	transform: translateY(-0.4rem);
	box-shadow: var(--fl-shadow-lg, 0 20px 60px rgba(18, 22, 42, 0.14));
}

/* Demos panel (requested directly): a slightly tinted, padded panel so
 * the demos block under the tech-logo grid reads as its own area - the
 * panel's own top padding is what creates the small gap between the two
 * blocks, rather than a separate margin rule. */
.fl-demos-panel {
	background-color: var(--base-tint);
	border-radius: var(--fl-radius-lg, 16px);
	margin-top: 3rem;
	padding: 4rem 3rem 1rem;
}

@media only screen and (min-width: 768px) {
	.fl-demos-panel {
		padding: 5rem 4rem 2rem;
	}
}

/* Footer full-width mark: sized in main.min.css as 28cqw of the
 * container's width assuming a short single word ("Azurio"). "Fisher
 * Labs" is longer, so at that scale it overflowed its container and
 * "Labs" was clipped off-screen entirely - scaled down to fit. */
.mxd-footer__fw-mark .fw-mark__content {
	font-size: 14cqw;
}

/* Footer Privacy Policy / Terms links (footer.php, beneath the VAT number)
 * - inherit main.min.css's own .footer-data a styling (uppercase, accent
 * font, muted colour, hover to bright); this just spaces the two apart and
 * keeps them right-aligned with the rest of that column. */
.footer-data--legal {
	display: flex;
	flex-wrap: wrap;
	justify-content: flex-end;
	gap: 0.6rem 1.6rem;
	margin-top: 0.4rem;
}

/* THE fix for "some links have a kind of scrolling effect before the
 * ability for it to be clicked especially in safari" (reported directly).
 * .mxd-page-transition (header.php) is a full-screen fixed black curtain
 * at z-index:999 that app.min.js's mxdPageTransition() slides up and off
 * over 0.7s on every page load (and back down on navigate-away). loader.min.css
 * gives it will-change:transform but NO pointer-events:none - so for that
 * 0.7s it still intercepts clicks over whatever it's currently covering,
 * and in Safari the will-change compositing layer keeps it hit-testable
 * even after it has visually slid away. It's a purely decorative overlay
 * with no interactive content, so it should never catch a pointer. */
.mxd-page-transition {
	pointer-events: none;
}

/* Brand text (header.php) for the curtain itself - reported directly
 * ("the logo does not display" on a fresh/bookmarked load, then "the
 * language switcher icons appear over the preloader" once the header
 * was raised to fix it instead). This curtain outlasts .mxd-loader on
 * a slow connection (confirmed directly: .mxd-loader already
 * display:none while this was still sitting at its untransformed,
 * fully-covering position), so without this the screen goes genuinely
 * blank for that stretch. Matches .mxd-loader's own text styling
 * (loader.min.css) for visual continuity between the two.
 *
 * position:absolute;top:0 (not the plain flow span this started as):
 * .mxd-page-transition itself is display:flex;align-items:center;
 * justify-content:center (loader.min.css), so a plain span inside it
 * rendered dead-center of the screen - .mxd-loader's own equivalent
 * text (.mxd-loader__top, same file) is pinned to the top instead, and
 * for however briefly the two can be visible at once (one fading as
 * the other takes over), having this one centered instead read as the
 * brand appearing twice in two different spots (reported directly:
 * "previously fisher labs appear at the top, now it also seem to
 * appear in the middle"). Matching .mxd-loader__top's own
 * position/top/padding exactly keeps it in the one place regardless of
 * which layer is actually showing it at a given moment. */
.mxd-page-transition__brand {
	position: absolute;
	top: 0;
	left: 0;
	width: 100%;
	padding: 3rem;
	text-align: center;
	font: normal 600 1.4rem/1.6 "JetBrains Mono", sans-serif;
	text-transform: uppercase;
	letter-spacing: 0.05rem;
	color: #e3e3f0;
}

/* Secondary: keep a link clickable while its own GSAP scroll-scrubbed
 * "slide" reveal is still catching up (scrub:1's ~1s lag, and every
 * scroll re-trigger). app.min.js animates only the link's inner <span>
 * (yPercent), but the <a> is inline-flex + overflow:hidden with a
 * lingering identity transform, so Safari hit-tests that clipped box
 * instead of the link. The <a> box never moves - dropping its own clip
 * (its masking parent, .footer-nav-v01__item / .footer-data, still clips
 * the visible reveal) and giving it a stacking context restores the hit
 * area. */
a.anim-uni-slide-down,
a.anim-uni-slide-up,
a.mxd-socials-line__link {
	overflow: visible;
	position: relative;
	z-index: 1;
}

/* fl-force-light: locks one section to its light/"day mode" palette,
 * originally added (requested directly) to keep testimonials light while
 * the rest of the site defaulted dark. The homepage as a whole is now
 * fixed "day"/light itself (color-scheme="light", set per page type in
 * header.php, no visitor toggle), so on testimonials specifically this
 * is redundant - the section would already resolve light without it -
 * but harmless to leave applied. Kept (rather than stripped from
 * testimonials.php) as a documented escape hatch: main.min.css's whole
 * light/dark system is just these custom properties resolving to a
 * --light or --dark suffixed value depending on color-scheme (see
 * main.min.css's own :root/[color-scheme] blocks), so redeclaring the
 * same property names here, scoped to a section, is how to pin any one
 * section to light regardless of the page's own fixed mode. */
.fl-force-light {
	--base: var(--base--light);
	--base-rgb: var(--base-rgb--light);
	--base-tint: var(--base-tint--light);
	--base-tint-rgb: var(--base-tint-rgb--light);
	--base-bright: var(--base-bright--light);
	--base-bright-rgb: var(--base-bright-rgb--light);
	--accent: var(--accent--light);
	--highlight: var(--highlight--light);
	--base-opp: var(--base-opp--light);
	--base-opp-rgb: var(--base-opp-rgb--light);
	--t-bright: var(--t-bright--light);
	--t-medium: var(--t-medium--light);
	--t-muted: var(--t-muted--light);
	--t-muted-extra: var(--t-muted-extra--light);
	--t-opp-bright: var(--t-opp-bright--light);
	--t-opp-medium: var(--t-opp-medium--light);
	--t-opp-muted: var(--t-opp-muted--light);
	--t-opp-muted-extra: var(--t-opp-muted-extra--light);
	--st-muted: var(--st-muted--light);
	--st-medium: var(--st-medium--light);
	--st-bright: var(--st-bright--light);
	background-color: var(--base);
	color: var(--t-medium);
}

/* fl-footer-dark: the inverse of fl-force-light above, same technique -
 * pins the footer to the *dark* palette on every page except the
 * homepage (whose footer is light, matching its own light body -
 * clarified directly: "the homepage footer has to have the light
 * background"), even though color-scheme is "light" sitewide now
 * (header.php - the homepage and internal pages share one light
 * body/header treatment, only their footers differ). Scoped to
 * body:not(.home) .mxd-footer rather than a class on the markup itself,
 * since footer.php is one shared template for every page - no per-page
 * branching needed there. */
body:not(.home) .mxd-footer {
	--base: var(--base--dark);
	--base-rgb: var(--base-rgb--dark);
	--base-tint: var(--base-tint--dark);
	--base-tint-rgb: var(--base-tint-rgb--dark);
	--base-bright: var(--base-bright--dark);
	--base-bright-rgb: var(--base-bright-rgb--dark);
	--accent: var(--accent--dark);
	--highlight: var(--highlight--dark);
	--base-opp: var(--base-opp--dark);
	--base-opp-rgb: var(--base-opp-rgb--dark);
	--t-bright: var(--t-bright--dark);
	--t-medium: var(--t-medium--dark);
	--t-muted: var(--t-muted--dark);
	--t-muted-extra: var(--t-muted-extra--dark);
	--t-opp-bright: var(--t-opp-bright--dark);
	--t-opp-medium: var(--t-opp-medium--dark);
	--t-opp-muted: var(--t-opp-muted--dark);
	--t-opp-muted-extra: var(--t-opp-muted-extra--dark);
	--st-muted: var(--st-muted--dark);
	--st-medium: var(--st-medium--dark);
	--st-bright: var(--st-bright--dark);
}

/* The footer's own logo (if a real one is uploaded) needs the same
 * light-colored variant the homepage header uses, for the same reason -
 * see the .mxd-header-permanent rule above. */
body:not(.home) .mxd-footer .fl-logo-light {
	display: none;
}

body:not(.home) .mxd-footer .fl-logo-dark {
	display: inline-flex;
}

/* Cursor-follow hover preview (data-cursor-image - services list,
 * blog/demo grids): main.min.css sizes this at 36rem (360px) square.
 * Halved and made circular (requested directly, called out on the
 * services list specifically but this is the one shared component
 * behind every data-cursor-image hover on the site, so the change is
 * sitewide). clip-path's own "round 50%" already approximates a circle
 * during the reveal animation; border-radius is a plain-static backstop
 * for whatever state that animation leaves it in. */
#mxd-cursor__image {
	width: 18rem;
	height: 18rem;
	border-radius: 50%;
}

/* Hero cover image on mobile: object-fit:cover centers by default -
 * shifted left instead (requested directly) so the subject leans left
 * rather than sitting dead-center on narrow screens. Desktop/tablet
 * keep Azurio's own centered default. */
@media only screen and (max-width: 767px) {
	.mxd-hero-02__cover-img img {
		object-position: left center;
	}
}

/* Technology grid on mobile: Azurio's own .col-lg-4 only reaches 3-up at
 * 992px, so mobile was 1 logo per row - forced to 3-up here instead
 * (requested directly), with each item's caption hidden since there's no
 * room left to keep it legible at a third of the width. */
@media only screen and (max-width: 991px) {
	.mxd-clients__item {
		flex: 0 0 33.3333%;
		width: 33.3333%;
		max-width: 33.3333%;
	}

	.mxd-clients__descr {
		display: none;
	}
}

/* Demo card hover (requested directly - see technology.php's own doc
 * comment on why this replaces .mxd-img-anim): a plain zoom + dark
 * overlay, all CSS, no JS and no second image needed. The overlay
 * used to carry its own "View Demo" text button; now that the real
 * View Demo action lives in the card footer as a proper button
 * (requested directly), this is just a "preview" affordance, not a
 * second competing call to action. */
.fl-demo-media {
	display: block;
}

.fl-demo-media__img {
	transition: transform 0.5s ease;
}

.fl-demo-media:hover .fl-demo-media__img {
	transform: scale(1.08);
}

.fl-demo-media__overlay {
	position: absolute;
	inset: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	background: linear-gradient(0deg, rgba(0, 0, 0, 0.55) 0%, rgba(0, 0, 0, 0) 55%);
	opacity: 0;
	transition: opacity 0.35s ease;
}

.fl-demo-media:hover .fl-demo-media__overlay {
	opacity: 1;
}

.fl-demo-media__badge {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 5.2rem;
	height: 5.2rem;
	border-radius: 50%;
	background: var(--fl-accent, #0e686c);
	color: #fff;
	font-size: 2rem;
	transform: scale(0.8);
	transition: transform 0.35s ease;
}

.fl-demo-media:hover .fl-demo-media__badge {
	transform: scale(1);
}

/* Demo card restyle (requested directly - "the cards do not look
 * premium and the tags look awkwardly stacked"). Two separate vendor
 * defaults were the actual cause: .mxd-project-item has no card chrome
 * at all (no border/background/shadow - a bare image + flush caption,
 * meant for the site's more editorial lists), and .mxd-project-item__tags
 * is flex-direction:column + align-items:flex-end, stacking up to 4
 * tags as separate right-aligned lines next to the title instead of
 * wrapping horizontally. Scoped to .fl-demo-cards (demos.php only) -
 * grid-card.php's other callers (case study/demo archive pages) keep
 * the original flush look. */
.fl-demo-cards .mxd-projects-grid__gallery {
	gap: 2.4rem;
	/* stretch (not the vendor's own flex-start) - requested directly
	 * ("the view demo button should be in the card footer"): lets
	 * margin-top:auto on .fl-demo-card__footer below pin the button to
	 * the bottom of every card in a row, even when a neighbouring
	 * card's title/tags run to a different height. */
	align-items: stretch;
}

/* Each card is .col-12.col-md-6.col-xl-4 (demos.php), Bootstrap's own
 * percentage-width grid columns - but .mxd-projects-grid__gallery above
 * also sets gap:2.4rem on top of that, extra spacing those percentages
 * were never reduced to account for. 3 columns at exactly 33.333% plus
 * 2 full 2.4rem gaps between them simply doesn't fit in 100% width, so
 * the third card wrapped onto its own row at EVERY width - confirmed
 * directly, by measuring real rendered positions: still only 2-up even
 * at 1280px, well past the 1200px xl breakpoint col-xl-4 itself needs
 * (reported directly: "the 3rd in the row seem to show in the next
 * line"; this is why - it was never about the breakpoint, the gap math
 * just didn't add up at any width 3-up was ever supposed to apply).
 * calc(100% - gaps) / columns is the standard fix for exactly this
 * combination (percentage flex-basis + an explicit gap) - 2-up from md
 * (768px, matching the original col-md-6), 3-up from xl (1200px,
 * matching the original col-xl-4), both now actually fitting. */
@media only screen and (min-width: 768px) and (max-width: 1199.98px) {
	.fl-demo-cards .mxd-project-item {
		flex: 0 0 calc(50% - 1.2rem);
		width: calc(50% - 1.2rem);
		max-width: calc(50% - 1.2rem);
	}
}

@media only screen and (min-width: 1200px) {
	.fl-demo-cards .mxd-project-item {
		flex: 0 0 calc(33.3333% - 1.6rem);
		width: calc(33.3333% - 1.6rem);
		max-width: calc(33.3333% - 1.6rem);
	}
}

.fl-demo-cards .mxd-project-item {
	gap: 0;
	padding: 0;
	margin-bottom: 0;
	height: 100%;
	background: var(--fl-bg-raised, #fff);
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg);
	/* Resting shadow (requested directly - "the demo cards should have
	 * some kind of shadows... that makes it land better on the white
	 * background") - a border alone reads flat against a plain white
	 * section background; --fl-shadow is the same soft, sitewide "raised
	 * surface" shadow this design system's own token set already
	 * defines, so it stays consistent with every other card-like
	 * component rather than a one-off value. The stronger --fl-shadow-lg
	 * still takes over on hover, below. */
	box-shadow: var(--fl-shadow);
	overflow: hidden;
	transition: transform 0.3s ease, box-shadow 0.3s ease, border-color 0.3s ease;
}

.fl-demo-cards .mxd-project-item:hover {
	transform: translateY(-6px);
	box-shadow: var(--fl-shadow-lg);
	border-color: transparent;
}

.fl-demo-cards .mxd-project-item__caption {
	flex: 1 1 auto;
	flex-direction: column;
	align-items: flex-start;
	gap: 1.2rem;
	padding: 2rem;
}

.fl-demo-cards .fl-demo-card__footer {
	margin-top: auto;
	width: 100%;
}

.fl-demo-cards .fl-demo-card__cta {
	display: flex;
	align-items: center;
	justify-content: center;
	gap: 0.8rem;
	width: 100%;
	padding: 1.2rem 1.6rem;
	border-radius: var(--fl-radius);
	background: var(--fl-accent, #0e686c);
	color: #fff;
	font: normal 600 1.3rem/1.6 var(--_font-accent, inherit);
	letter-spacing: 0.04rem;
	text-transform: uppercase;
	text-decoration: none;
	transition: opacity 0.25s ease;
}

.fl-demo-cards .fl-demo-card__cta i {
	font-size: 1.6rem;
}

.fl-demo-cards .fl-demo-card__cta:hover {
	opacity: 0.85;
	color: #fff;
}

.fl-demo-cards .mxd-project-item__tags {
	flex-direction: row;
	flex-wrap: wrap;
	align-items: center;
	padding-top: 0;
	gap: 0.6rem;
}

.fl-demo-cards .mxd-project-item__tags .tag {
	display: inline-flex;
	align-items: center;
	padding: 0.5rem 1.2rem;
	border-radius: 100px;
	background: var(--fl-bg-alt);
	color: var(--fl-fg-muted);
	font-size: 1.1rem;
}

/* Testimonials subheading: sat flush against the card grid right below
 * it (requested directly - "too close to the testimonial cards"). Own
 * class rather than touching .pricing-header__descr's own rule, since
 * that class is shared with the Pricing section, where this gap wasn't
 * a complaint. */
.fl-testimonials-subheading {
	margin-bottom: 2.4rem;
}

/* ---------------------------------------------------------------
 * Inner pages (archives, singles, static templates) - phase 2 of the
 * Azurio migration, deliberately deferred at the start of the project
 * ("homepage + chrome first"). Every inner page now opens with
 * template-parts/inner-headline.php and (mostly) closes with
 * template-parts/cta-marquee.php; what's here is what those shared
 * partials, and the per-type content between them, need beyond what
 * main.min.css already covers on its own.
 * --------------------------------------------------------------- */

/* Grid card image, forced square (template-parts/grid-card.php) - reported
 * directly ("the cards of the images has to be equal dimensions... limit
 * the display into a square"). main.min.css's own .mxd-project-item__media
 * has no aspect-ratio/fixed-dimension rule at all, so cards were only ever
 * as uniform as their source images happened to be. aspect-ratio+object-fit
 * is the belt to add_image_size( 'fl_card_square', ... )'s braces (functions.php):
 * the registered crop is right for every *new* upload, this covers images
 * uploaded before that size existed (no crop generated for those until
 * regenerated) and any non-square image a URL/API ever feeds in regardless. */
.mxd-project-item__media {
	aspect-ratio: 1 / 1;
	display: block;
}

.mxd-project-item__media img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	transition: transform 0.6s cubic-bezier(0.16, 1, 0.3, 1);
}

.mxd-project-item__media:hover img {
	transform: scale(1.06);
}

/* Grid section wrapper - main.min.css styles .mxd-project-item itself
 * but not the Bootstrap-style .row it sits in on a bare grid (no
 * sticky/pinned scroll choreography here, just a plain wrap), so cards
 * had no gutter between rows without this. */
.fl-grid-row {
	row-gap: 3.2rem;
}

/* Inner-headline title overflow (template-parts/inner-headline.php) -
 * main.min.css's own h1.large is white-space:nowrap by design, tuned
 * for the reference template's own always-short titles ("Works",
 * "Pricing", "Azurio"...). This same block is shared by every CPT
 * single page too, where the title is an admin-entered service/project/
 * product name of unpredictable length ("SEO e Marketing Digitale" ran
 * straight off the right edge of the viewport at that font-size with
 * nowrap) - letting it wrap is the fix that holds regardless of how
 * long a name someone enters, rather than trying to bound the length. */
.inner-headline__title h1.large {
	white-space: normal;
	overflow-wrap: break-word;
}

/* Service single pages (single-fl_service.php) - the shared inner-page
 * rhythm (main.min.css) is tuned for the reference template's short,
 * standalone marketing pages; on a service detail page - long admin
 * title, then a spec split, "What this includes" and the calculator all
 * meant to read as one flow - the 9-15rem title and 11-20rem section
 * paddings read as unprofessional dead space (reported directly). Scoped
 * to the body class so no other page changes. */
.single-fl_service .inner-headline__content.has-large-title {
	padding-top: 4rem;
}

.single-fl_service .inner-headline__title h1.large {
	font-size: 4.4rem;
	line-height: 1.12;
	letter-spacing: -0.02em;
}

.single-fl_service .inner-headline.margin-bottom-subtitle {
	margin-bottom: 4rem;
}

.single-fl_service .mxd-section.padding-top-subtitle {
	padding-top: 3rem;
}

.single-fl_service .mxd-section.padding-bottom-default {
	padding-bottom: 5rem;
}

@media only screen and (min-width: 1200px) {
	.single-fl_service .inner-headline__content.has-large-title {
		padding-top: 5rem;
	}

	.single-fl_service .inner-headline__title h1.large {
		font-size: 5.6rem;
	}

	.single-fl_service .mxd-section.padding-top-subtitle {
		padding-top: 4rem;
	}

	.single-fl_service .mxd-section.padding-bottom-default {
		padding-bottom: 6rem;
	}
}

/* Form fields (.fl-form - contact/account/checkout/booking/consulting) -
 * main.min.css styles bare <textarea> (underline, transparent bg,
 * adaptive color) but has no equivalent rule for <input> at all, text
 * or otherwise - every reference page's own contact form apparently
 * leans on a third-party form-backend's injected styling for that half
 * of the same form, which isn't part of what was licensed/copied here.
 * Mirrors the textarea treatment exactly so text inputs read as the
 * same component, not a mismatched fallback. */
.fl-form input[type="text"],
.fl-form input[type="email"],
.fl-form input[type="tel"],
.fl-form input[type="number"],
.fl-form input[type="password"],
.fl-form input[type="url"],
.fl-form select {
	position: relative;
	display: block;
	width: 100%;
	border: none;
	border-bottom: 1px solid var(--st-medium);
	outline: 0;
	margin: 0;
	padding: 1.2rem 0.2rem;
	background-color: transparent;
	font: normal 400 2rem var(--_font-accent, inherit);
	height: 5.8rem;
	line-height: 5.8rem;
	color: var(--t-bright);
	border-radius: 0;
	-webkit-appearance: none;
	appearance: none;
}

.fl-form input[type="text"]:focus,
.fl-form input[type="email"]:focus,
.fl-form input[type="tel"]:focus,
.fl-form input[type="number"]:focus,
.fl-form input[type="password"]:focus,
.fl-form input[type="url"]:focus,
.fl-form select:focus {
	border-bottom: 1px solid var(--st-bright);
}

.fl-form input::placeholder,
.fl-form textarea::placeholder {
	color: var(--t-muted);
	opacity: 1;
}

.fl-form label {
	display: block;
	font: normal 600 1.3rem/1.6 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.02rem;
	color: var(--t-muted);
	margin-bottom: 0.4rem;
}

.fl-form .fl-form-row {
	margin-bottom: 0;
	padding: 1.6rem 1.5rem;
}

.fl-form-notice {
	padding: 1.6rem 2rem;
	border-radius: var(--fl-radius, 10px);
	font-size: 1.5rem;
	margin-bottom: 2.4rem;
}

.fl-form-notice-success {
	background-color: color-mix(in srgb, #1a7a4c 14%, transparent);
	color: #1a7a4c;
}

.fl-form-notice-error {
	background-color: color-mix(in srgb, #b3261e 14%, transparent);
	color: #b3261e;
}

/* Honeypot field - visually hidden, still in the tab/DOM flow for bots
 * to fill (that's the point), so display:none/visibility:hidden (which
 * some screen readers and most bots skip identically) isn't used. */
.fl-honeypot {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip: rect(0 0 0 0);
	white-space: nowrap;
}

/* About/Process section background - requested directly as a specific
 * hex value, scoped to #about only rather than redefining --accent
 * itself (which .bg-color-accent reads from): that same token also
 * colors other things sitewide (pricing's "Most Popular" badge,
 * buttons, the case-study/project testimonial blockquote background),
 * none of which this request was about - overriding just the
 * background-color declaration here leaves --accent, and everything
 * else that reads it, untouched. */
#about.bg-color-accent {
	background-color: #0e686c;
}

/* Detail page hero image - main.min.css has nothing for a plain single
 * cover photo (every reference page either has no such image or wraps
 * one in a much heavier parallax-divider setup this doesn't need). */
.fl-detail-cover img {
	width: 100%;
	max-height: 56rem;
	object-fit: cover;
	border-radius: var(--fl-radius-lg, 16px);
}

/* Split List detail pages (single-fl_service.php, single-fl_project.php
 * etc.) - Azurio's own .mxd-block-split/.split-info__item come from
 * project-details.html and are fully styled already; this is only the
 * prose typography for the long-form body copy (challenge/solution/
 * description) they wrap, which has no equivalent anywhere in
 * main.min.css since no reference page runs raw admin-authored HTML
 * through wpautop() like this. Kept close to the surrounding
 * manifest/t-medium type scale rather than introducing a new one. */
.fl-prose {
	max-width: 68ch;
}

.fl-prose p {
	font-size: 1.7rem;
	line-height: 1.6;
	color: var(--t-medium);
	margin: 0 0 1.6rem;
}

.fl-prose p:last-child {
	margin-bottom: 0;
}

.fl-prose ul,
.fl-prose ol {
	margin: 0 0 1.6rem;
	padding-left: 2rem;
	color: var(--t-medium);
}

.fl-prose li {
	font-size: 1.7rem;
	line-height: 1.6;
	margin-bottom: 0.6rem;
}

/* Detail-page spec sheet (Client/Industry/Price/etc.) - split-info__item
 * is a single row on its own in the reference template; stacking
 * several needs a touch of vertical rhythm between them that the
 * component doesn't supply by itself. */
.fl-spec-list .split-info__item + .split-info__item {
	margin-top: 0.4rem;
}

/* Project Details list (Client/Industry/Technology/Website) - reported
 * directly ("for the client details info list, reduce the text and
 * the padding of each line"): the vendor's own split-info__item/
 * __details values (2rem/2.4rem text, 2.9-5.5rem vertical padding per
 * row) are sized for a short reference-template list, not a compact
 * spec sheet sitting beside prose paragraphs. Scoped to
 * .single-fl_project - other pages using the same .fl-spec-list
 * component keep the vendor's own sizing. */
.single-fl_project .fl-spec-list .split-info__item {
	padding: 1.4rem 0.2rem 1.6rem;
}

.single-fl_project .fl-spec-list .split-info__details p {
	font-size: 1.7rem;
}

@media only screen and (min-width: 1200px) {
	.single-fl_project .fl-spec-list .split-info__item {
		padding: 1.8rem 0.2rem 2rem;
	}

	.single-fl_project .fl-spec-list .split-info__details p {
		font-size: 1.8rem;
	}
}

/* Pagination (WordPress core's own the_posts_pagination() markup,
 * .nav-links/.page-numbers) - had no styling anywhere in main.min.css
 * (no reference page needs it, they're all static demo content) or in
 * the old .fl-* system, so links rendered as bare underlined text. */
.fl-pagination .nav-links {
	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	gap: 0.8rem;
}

.fl-pagination .page-numbers {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	min-width: 4.4rem;
	height: 4.4rem;
	padding: 0 1rem;
	border: 1px solid var(--st-muted, rgba(18, 18, 18, 0.16));
	border-radius: 100px;
	font: normal 600 1.4rem/1 var(--_font-accent, inherit);
	color: var(--t-bright);
	text-decoration: none;
	transition: background-color 0.25s ease, color 0.25s ease, border-color 0.25s ease;
}

.fl-pagination a.page-numbers:hover {
	background-color: var(--t-bright);
	color: var(--base);
	border-color: var(--t-bright);
}

.fl-pagination .page-numbers.current {
	background-color: var(--t-bright);
	color: var(--base);
	border-color: var(--t-bright);
}

.fl-pagination .page-numbers.dots {
	border-color: transparent;
}

/* Feature/requirement lists (services, products) rendered as Azurio's
 * own tag pills rather than a plain bulleted list, consistent with how
 * tags read everywhere else on these pages. Wraps plain .tag spans
 * (same markup used for the meta/technology tags elsewhere), not a
 * <ul> - nothing here needs list semantics. */
.fl-tag-list {
	display: flex;
	flex-wrap: wrap;
	gap: 0.8rem;
	margin: 0 0 1.6rem;
}

/* Service page Features (detail-features-specs.php) - real badge chips
 * (background + border + rounded corners), not the vendor .tag class
 * above, which is genuinely just styled text with no chip shape of its
 * own - confirmed by reading main.min.css directly, not a rendering
 * bug. "the tags... has to appear somewhat like badges", requested
 * directly once the plain-text version was seen live. */
.fl-badge-list {
	display: flex;
	flex-wrap: wrap;
	gap: 0.8rem;
	margin: 1.6rem 0 0;
}

/* Primary purchase button under the spec list on product / service pages.
 * A real <button> (in its own tiny GET form) on the product page now -
 * requested directly ("the buy now should be an actual button, not a
 * link") - see detail-gallery-specs.php's own doc comment; .fl-detail-cta
 * is a class, not an element selector, so this still matches regardless
 * of whether it's a <div> (service/pricing-plan/consultation-type,
 * detail-features-specs.php) or a <form> (product). */
.fl-detail-cta {
	margin-top: 2.4rem;
}

.fl-spec-list + .fl-detail-cta {
	margin-top: 2rem;
}

/* The CTA's own markup classes (btn-anim/btn-default/btn-additional) turn
 * out to carry no actual styling anywhere in the vendor bundle or this
 * stylesheet (checked directly - not one rule for any of the three,
 * plain or compound) - only bare .btn's full reset (no border/background/
 * padding of its own) applies, so this has only ever rendered as plain
 * caption text and an arrow, not a button - "the buy now link should
 * appear like a button", confirmed live. Same solid-pill treatment
 * .fl-featured-product__btn already uses on the homepage, adapted for a
 * light background instead of that section's dark teal one. */
.fl-detail-cta .btn {
	gap: 1rem;
	padding: 1.5rem 3rem;
	border-radius: 100px;
	background-color: var(--fl-accent);
	color: var(--fl-accent-fg, #ffffff);
	font: normal 700 1.3rem/1 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.06rem;
	transition: transform var(--_animspeed-medium, 0.3s), box-shadow var(--_animspeed-medium, 0.3s), background-color var(--_animspeed-medium, 0.3s);
}

.fl-detail-cta .btn:hover,
.fl-detail-cta .btn:focus-visible {
	background-color: var(--fl-accent);
	transform: translateY(-2px);
	box-shadow: 0 12px 24px rgba(14, 104, 108, 0.28);
}

/* Product page info columns (template-parts/detail-info-columns.php) -
 * "About this product" / Documentation / FAQ stacked on the left,
 * Requirements / Changelog / License on the right (requested directly).
 * A light divider between stacked topics in the same column - without
 * one, back-to-back headings read as one continuous piece rather than
 * distinct topics, since normal reading rhythm has no page-break to mark
 * the change. */
.fl-detail-info-block + .fl-detail-info-block {
	margin-top: 3.2rem;
	padding-top: 3.2rem;
	border-top: 1px solid var(--fl-border);
}

/* Overview section's top padding, product page only - requested directly
 * ("reduce the padding-top of the subtitle area to 2rem"). .padding-top-
 * subtitle (main.min.css) is a shared Azurio preset (13.4-19.4rem across
 * breakpoints) that detail-overview.php also uses for single-fl_service.php -
 * scoped to .single-fl_product (WordPress's own singular-CPT body class)
 * so the service page's spacing is untouched. */
.single-fl_product .padding-top-subtitle {
	padding-top: 2rem;
}

.fl-badge {
	display: inline-flex;
	align-items: center;
	padding: 0.6rem 1.4rem;
	border-radius: 100px;
	border: 1px solid var(--fl-border);
	background: var(--fl-accent-soft, color-mix(in srgb, var(--fl-accent) 12%, transparent));
	color: var(--fl-accent);
	font: normal 600 1.2rem/1.4 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.03rem;
}

/* Featured Projects showcase - small "eyebrow" label directly above each
 * project's own title (homepage_featured_projects_heading; requested
 * directly, moved here from a section-level heading - "place it right
 * on top [of] each mxd-showcase-clip__title"). .fl-showcase-title-wrap
 * carries .mxd-showcase-clip__title's own class too, so it keeps that
 * class's exact responsive width/alignment (main.min.css) - this only
 * stacks its two children (eyebrow, title text) into a column instead
 * of .mxd-showcase-clip__title's own row-flex default, which would
 * otherwise place the eyebrow beside the title instead of above it. */
.fl-showcase-title-wrap {
	flex-direction: column;
	gap: 0.6rem;
}

.fl-showcase-title-wrap .fl-showcase-eyebrow {
	/* Specificity note: main.min.css has its own
	 * ".mxd-showcase-clip__title span{color:var(--t-medium)}" (a class +
	 * element selector), which this span - nested inside a div that also
	 * carries the .mxd-showcase-clip__title class - would otherwise
	 * match too. A bare ".fl-showcase-eyebrow" (one class) loses to that
	 * on specificity regardless of source order; scoping it under its
	 * own wrapper class here (two classes) wins outright instead of
	 * relying on load order, confirmed live (the color rendered as
	 * --t-medium's grey, not this one, before this was scoped). */
	display: block;
	font: normal 600 1.4rem/1.4 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.04rem;
	color: #c9c9c9;
}

.fl-showcase-title-wrap .fl-showcase-title-text {
	/* Same specificity issue as .fl-showcase-eyebrow above - without this
	 * scoping the actual title text (also a <span> here, for the same
	 * reason) would pick up main.min.css's ".mxd-showcase-clip__title
	 * span{color:var(--t-medium)}" too, dimming it instead of the solid
	 * white ".permanent" was supposed to guarantee. */
	display: block;
	color: inherit;
}

/* Featured Projects showcase - background photo placeholder + fade-in
 * (paired with assets/js/showcase-bg-fade.js and the smaller image size
 * featured_projects.php now requests) - reported directly: "sometimes
 * the background image takes time to load, and it looks awkward when
 * scrolling early". The theme accent color fills .mxd-showcase-clip__trigger
 * behind the image the whole time, so there's never a blank/white flash
 * even on a slow load; the photo itself starts invisible and fades in
 * once showcase-bg-fade.js confirms it has actually finished loading. */
.mxd-showcase-clip__trigger {
	background-color: var(--fl-accent, #0e686c);
}

.mxd-showcase-clip__bg {
	opacity: 0;
	transition: opacity 0.6s ease;
}

.mxd-showcase-clip__bg.fl-loaded {
	opacity: 1;
}

/* Header logo - main.min.css sizes .mxd-logo__image (the header bar
 * specifically, not .menu-logo__image in the full-screen nav overlay,
 * which is untouched) at 3.6rem/4rem - felt too small (requested
 * directly), bumped about 30% on both of its own breakpoints so it
 * stays the same size relative to itself at mobile vs desktop, just
 * larger throughout: 3.6/4rem -> 4.6/5.2rem. width:auto (main.min.css)
 * keeps it proportional either way. */
/* .mxd-header__logo prefix (not a bare .mxd-logo__image) so this still
 * wins on a WooCommerce page: woocommerce.css ships
 * `.woocommerce-page img { height: auto }` (0,1,1) which would otherwise
 * outspecify a bare `.mxd-logo__image { height }` (0,1,0) and shrink an
 * SVG logo to its 1px intrinsic height. */
.mxd-header__logo .mxd-logo__image {
	width: auto;
	height: 4.6rem;
}

@media only screen and (min-width: 768px) {
	.mxd-header__logo .mxd-logo__image {
		height: 5.2rem;
	}
}

/* Root cause of "the language dropdown flags look shrunk/cropped below
 * ~445px, fine above it": confirmed directly, by measuring real rendered
 * rects, that it was never the dropdown's own CSS at all. .mxd-header's
 * content (this logo at 4.6rem height -> 223.72px wide, plus
 * .mxd-header__controls at 116px) totals ~340px - wider than .mxd-
 * header's own box at any phone width (245-315px, since flex items
 * don't shrink below their content size by default) - so the controls
 * block, switcher included, simply renders ~80px to the right of where
 * the header logically ends. .mxd-menu__contain (the hamburger) sits
 * independently at a fixed right:3rem with its own z-index:12 and
 * mix-blend-mode:difference - confirmed it starts physically overlapping
 * .fl-language-select once the viewport drops below ~430px (not yet at
 * 430px, overlapping at 390px and below), which lines up with "less than
 * 445px" almost exactly. mix-blend-mode is a paint-only effect invisible
 * to any computed-style/geometry check, which is why the flag's own box
 * always measured correctly while still looking visually wrong - the
 * hamburger was compositing on top of it, color-inverting whatever of
 * the switcher/dropdown fell underneath. The logo - not the hamburger
 * (whose own right:3rem position is what the header's margins were
 * already sized to clear, by design) or the Say Hello icon (already a
 * fixed, small 36px) - is what's actually oversized for the room phones
 * have: shrinking it here is enough on its own to pull the controls
 * block clear of the hamburger at every phone width, confirmed directly
 * (re-measured down to 320px, zero overlap with this in place). */
@media only screen and (max-width: 429px) {
	.mxd-header__logo .mxd-logo__image {
		height: 3.6rem;
	}
}

/* .t-accent - requested directly ("change the light blue color found in
 * t-accent to white"): main.min.css's own ".t-accent{color:var(--pt-t-
 * accent-medium)}" resolves to #A7B2E3, a light blue/lavender. Not
 * touching that variable itself - it's also read by a couple of
 * Azurio's own components this site doesn't use (.socials-list__*) -
 * overriding the class directly is the narrower, safer change. Used in
 * three places, all in the About/Process section: the process-point
 * descriptions, the CEO quote's author line, and (via the nested-span
 * rule main.min.css also defines) that same author line's role/title
 * span specifically - both had to be covered, or the span would still
 * win on higher specificity and stay light blue while the rest of the
 * line went white.
 *
 * A plain ".t-accent" lost outright, though: main.min.css also has a
 * more specific "p.t-accent{color:var(--pt-t-accent-medium)}" (every
 * real usage here is a <p>), which a single-class selector can't beat
 * regardless of source order - confirmed live (computed color was still
 * the old light blue). ".t-accent.t-accent" repeats the class to force
 * higher specificity without needing to know or guess the host tag. */
.t-accent.t-accent,
.t-accent.t-accent span {
	color: #ffffff;
}

/* Single project page hero (template-parts/detail-banner.php) -
 * full-width background image with the breadcrumb/title/subtitle/tags
 * overlaid on top in white, not a separate image block stacked below a
 * plain-text title area (requested directly, after an earlier pass put
 * this same treatment on the archive instead of here - "you are
 * supposed to do the banner design inside the project page itself, not
 * on the project archive"). */
.fl-project-hero {
	position: relative;
	overflow: hidden;
	/* min-height 12rem -> 20rem (requested directly, more visual weight
	 * than the minimum worked out to). margin-top halved (9rem -> 4.5rem
	 * / 10rem -> 5rem) from the previous round's own header-clearance
	 * value, once that round's fix was confirmed actually working -
	 * this was reported as feeling like more clearance than wanted once
	 * seen live, not a re-diagnosis of the padding-vs-margin mechanism
	 * itself. */
	min-height: 20rem;
	margin-top: 4.5rem;
	margin-bottom: 3rem;
	padding-top: 4rem;
	padding-bottom: 4rem;
	display: flex;
	align-items: center;
}

@media only screen and (min-width: 768px) {
	.fl-project-hero {
		margin-top: 5rem;
		margin-bottom: 4rem;
	}
}

.fl-project-hero__media {
	position: absolute;
	inset: 0;
	background-color: var(--base-opp, #0f0f0f);
}

.fl-project-hero__media img {
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.fl-project-hero__overlay {
	position: absolute;
	inset: 0;
	background: linear-gradient(0deg, rgba(0, 0, 0, 0.75) 0%, rgba(0, 0, 0, 0.15) 65%);
}

.fl-project-hero__inner {
	position: relative;
	z-index: 1;
	width: 100%;
	padding-top: 3rem;
	padding-bottom: 3rem;
}

/* .grid-l-container (main.min.css, this element's other class) is
 * deliberately padding:0 below the 768px breakpoint; every other
 * section on the site puts its actual content in a child carrying
 * .mxd-grid-item (padding:0 3rem) to compensate, which is exactly what
 * was missing here - the breadcrumb/title sat flush against the screen
 * edge on mobile, reported directly. Needs the compound selector, not
 * just .fl-project-hero__inner alone: .mxd-container.grid-l-container
 * is two classes (0,2,0), which otherwise beats a lone
 * .fl-project-hero__inner (0,1,0) regardless of source order - confirmed
 * live, the first attempt at this exact fix silently lost that
 * specificity fight at mobile widths. Nothing needed at 768px+ -
 * .grid-l-container's own padding there is already the same 3rem this
 * is matching. */
.fl-project-hero__inner.grid-l-container {
	padding-left: 3rem;
	padding-right: 3rem;
}

@media only screen and (min-width: 768px) {
	.fl-project-hero__inner {
		padding-top: 4rem;
		padding-bottom: 4rem;
	}
}

.fl-project-hero__crumbs {
	margin-bottom: 1.5rem;
	font: normal 600 1.3rem/1.4 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.02rem;
	color: rgba(255, 255, 255, 0.7);
}

.fl-project-hero__crumbs a {
	color: rgba(255, 255, 255, 0.7);
	text-decoration: underline;
}

/* One restrained size for every detail-page / archive hero title. The
 * portfolio-scale 6rem was reported as too large ("some of the titles
 * are too large"); this matches the service page's own already-approved
 * smaller treatment, applied everywhere for consistency. */
.fl-project-hero__title {
	margin: 0 0 1.2rem;
	color: #ffffff;
	font-size: 3.4rem;
	line-height: 1.12;
	letter-spacing: -0.06rem;
}

@media only screen and (min-width: 768px) {
	.fl-project-hero__title {
		font-size: 4.6rem;
	}
}

.fl-project-hero__subtitle {
	max-width: 60ch;
	margin: 0 0 1.5rem;
	color: rgba(255, 255, 255, 0.85);
	font-size: 1.7rem;
	line-height: 1.5;
}

.fl-project-hero__tags {
	display: flex;
	flex-wrap: wrap;
	gap: 0.6rem;
}

.fl-project-hero__cta {
	margin-top: 1.8rem;
}

/* Compact section-break spacing - see detail-split.php/prose-section.php's
 * own doc comments. A flat value rather than main.min.css's own
 * responsive 4-tier scale: this is a modest paragraph/section-level gap,
 * not a full page-section break that needs to grow with viewport width
 * the way padding-bottom-default's 14/17/18/20rem does. */
.fl-padding-bottom-compact {
	padding-bottom: 5rem;
}

/* Project "showcase" image (fl_showcase_image_id - Catalog > Portfolio
 * Projects > Showcase Image, the same optional foreground image field
 * built for the homepage clip showcase) shown inline in the single
 * page's own content area too now, like a featured image (requested
 * directly). Deliberately not full-bleed like the hero above it - a
 * normal content-width image break reads as "here's a closer look",
 * not a second hero. Lives in detail-split.php's left column, under the
 * Challenge/Overview paragraph, not as its own full-width section
 * (refined - "it should be on the left underneath challenges") - so
 * it's capped at that column's own width (half the page on desktop,
 * .fl-project-showcase-img--inline) rather than the wider standalone
 * treatment. */
.fl-project-showcase-img img {
	width: 100%;
	max-height: 56rem;
	object-fit: cover;
	border-radius: var(--fl-radius-lg, 16px);
}

.fl-project-showcase-img--inline {
	margin-top: 2.4rem;
}

/* object-fit:contain (not cover) - reported directly ("the showcase
 * image is still cropped, I want to be able to see the full height of
 * the image, even if you get to make the dimension compact"): cover
 * was filling the fixed box by cropping whatever didn't fit; contain
 * always shows the whole image, letterboxing rather than cropping if
 * its aspect ratio doesn't fill max-height exactly. */
.fl-project-showcase-img--inline img {
	max-height: 34rem;
	object-fit: contain;
}

/* Challenge + Solution, stacked in the same left column now (detail-split.php's
 * manifest_secondary - "on the same row as the problems and solutions",
 * requested directly). .mxd-block-split__manifest's own gap (vendor CSS)
 * only spaces elements *inside* one manifest block, not between the two
 * separate blocks this adds - without this, the Solution heading would
 * sit flush against the Challenge paragraph above it. */
.fl-section-heading--secondary {
	margin-top: 3rem;
}

/* Challenge text (single-fl_project.php's row 1) - reported directly
 * ("reduce the challenge info text font"): the vendor's .manifest-s
 * lead-paragraph size (4.4rem) is meant for a short hero tagline, not
 * a full paragraph of case-study copy, and reads oversized next to the
 * showcase image beside it. Scoped to this one usage (the project
 * page's non-prose manifest block) rather than redefining
 * .manifest.manifest-s itself, which other pages still use at full size.
 * Nudged back up twice afterwards ("increase... a little", then "to
 * like 3.2 rem") - 2.4rem and then 2.8rem both still read a bit small
 * next to the image. */
.single-fl_project .mxd-block-split__manifest .manifest.manifest-s {
	font-size: 3.2rem;
}

/* Challenge row's section spacing (the first .mxd-section on the
 * project page, right after the hero) - reported directly ("too much
 * space above and beneath it"). padding-top-subtitle is main.min.css's
 * own subtitle-overlap spacing (13.4-19.4rem, meant to sit under a
 * large hero title), scoped down the same way .single-fl_service
 * already does for its own opening section. Kept scoped to
 * .single-fl_project (detail-banner.php's .fl-project-hero wrapper is
 * shared by several other single templates) and to the adjacent
 * sibling of the hero specifically, so the Solution/Results row below
 * it - and every other compact detail-split section sitewide - keeps
 * its normal spacing. */
.single-fl_project .fl-project-hero + .mxd-section.padding-top-subtitle {
	padding-top: 3rem;
	padding-bottom: 2rem;
}

@media only screen and (min-width: 1200px) {
	.single-fl_project .fl-project-hero + .mxd-section.padding-top-subtitle {
		padding-top: 4rem;
		padding-bottom: 2.5rem;
	}
}

/* Solution/Results row (row 2) - immediately follows row 1 above via a
 * second chained adjacent-sibling (both rows share the exact same
 * .mxd-section.padding-top-subtitle wrapper, so this is the only way
 * to reach row 2 specifically without a class of its own). Row 2's
 * own padding-top-subtitle was still the full vendor default
 * (13.4-19.4rem) even after row 1's own spacing was tightened above,
 * so the gap between the two rows was still huge - reported directly
 * ("reduce the space between the challenge row section and the
 * section beneath"). */
.single-fl_project .fl-project-hero + .mxd-section.padding-top-subtitle + .mxd-section.padding-top-subtitle {
	padding-top: 1.5rem;
}

@media only screen and (min-width: 1200px) {
	.single-fl_project .fl-project-hero + .mxd-section.padding-top-subtitle + .mxd-section.padding-top-subtitle {
		padding-top: 2rem;
	}
}

/* Testimonial section (single-fl_project.php/single-fl_case_study.php) -
 * same #0e686c requested for the About section's .bg-color-accent,
 * applied here the same way (scoped background-color override, not a
 * redefinition of --accent itself - see the #about rule's own doc
 * comment for why). White text isn't automatic just because the
 * section is dark: .manifest reads the adaptive --t-bright token, which
 * resolves dark on this page (color-scheme is "light" sitewide except
 * the homepage/footer) unless told otherwise, so that's forced white
 * here too. */
.fl-testimonial-accent {
	background-color: #0e686c;
}

.fl-testimonial-accent blockquote {
	color: #ffffff;
}

/* ---------------------------------------------------------------
 * Homepage - Featured Product spotlight (template-parts/homepage/
 * featured_products.php) - showcases exactly one product.
 *
 * Third pass on this (requested directly - a reference product-ad
 * screenshot: solid colour banner, product photo floating directly on
 * it with no card/shadow/rotation, bold headline + short subtitle +
 * one solid pill button, "the bg color to be greenish like the ceo
 * area... the product image can be png or svg... the box in this image
 * represent the product image"). The earlier blob-plus-rotated-card
 * treatment assumed a rectangular photo to crop and mount; a
 * transparent PNG/SVG cutout instead just needs to float on the same
 * solid colour the rest of the banner uses, uncropped - see
 * .fl-featured-product__image's object-fit:contain and the complete
 * absence of any background/border/shadow on it.
 *
 * #0e686c is the same accent colour already used for the homepage CEO
 * strip (.fl-testimonial-accent, this file) - reused directly here
 * rather than a second hardcoded value, so the two "solid accent-
 * coloured panel" moments on this page stay in sync if that colour
 * ever changes.
 * --------------------------------------------------------------- */

/* Full-bleed, edge to edge - the same "colour lives on the outer
 * .mxd-section itself" pattern #about.bg-color-accent already uses.
 * Compact top/bottom padding (not padding-top-default/-bottom-default's
 * 14-20rem scale, meant for a normal content section) - this is a
 * short colour-block CTA, not a full section, sitting between
 * Technology and Pricing. */
.fl-featured-product-section {
	background: linear-gradient(135deg, #12888d 0%, #0e686c 55%, #0a4f52 100%);
	padding-top: 4rem;
	padding-bottom: 4rem;
}

@media only screen and (min-width: 768px) {
	.fl-featured-product-section {
		padding-top: 6rem;
		padding-bottom: 6rem;
	}
}

.fl-featured-product {
	display: flex;
	flex-direction: column-reverse;
	align-items: center;
	gap: 3rem;
}

@media only screen and (min-width: 992px) {
	.fl-featured-product {
		flex-direction: row;
		gap: 5rem;
	}
}

.fl-featured-product__visual {
	flex: 0 0 auto;
	width: 100%;
	max-width: 34rem;
	display: flex;
	align-items: center;
	justify-content: center;
}

@media only screen and (min-width: 992px) {
	.fl-featured-product__visual {
		width: 42%;
		max-width: none;
	}
}

/* No background, border, shadow or rotation on purpose - a transparent
 * PNG/SVG product cutout needs to sit directly on the section's own
 * colour, exactly like the reference. object-fit:contain (not cover)
 * so the whole product shows uncropped regardless of its own image's
 * aspect ratio. */
.fl-featured-product__image {
	width: 100%;
	max-height: 32rem;
	object-fit: contain;
}

.fl-featured-product__content {
	flex: 1 1 auto;
	width: 100%;
	text-align: center;
}

@media only screen and (min-width: 992px) {
	.fl-featured-product__content {
		width: 58%;
		text-align: left;
	}
}

.fl-featured-product__eyebrow {
	display: inline-block;
	margin-bottom: 1.2rem;
	color: rgba(255, 255, 255, 0.75);
	font: normal 700 1.3rem/1 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.12rem;
}

.fl-featured-product__name {
	margin: 0 0 1.2rem;
	color: #ffffff;
	font-size: 3.4rem;
	line-height: 1.15;
	letter-spacing: -0.06rem;
}

@media only screen and (min-width: 768px) {
	.fl-featured-product__name {
		font-size: 4.6rem;
	}
}

.fl-featured-product__tagline {
	max-width: 52ch;
	margin: 0 auto 2.2rem;
	color: rgba(255, 255, 255, 0.85);
	font-size: 1.7rem;
	line-height: 1.55;
}

@media only screen and (min-width: 992px) {
	.fl-featured-product__tagline {
		margin: 0 0 2.2rem;
	}
}

.fl-featured-product__price {
	display: flex;
	align-items: baseline;
	justify-content: center;
	gap: 1rem;
	margin-bottom: 2.4rem;
}

@media only screen and (min-width: 992px) {
	.fl-featured-product__price {
		justify-content: flex-start;
	}
}

.fl-featured-product__price-was {
	color: rgba(255, 255, 255, 0.6);
	font-size: 1.6rem;
	text-decoration: line-through;
}

.fl-featured-product__price-now {
	color: #ffffff;
	font: normal 700 2.6rem/1 var(--_font-default, inherit);
}

.fl-featured-product__cta {
	display: inline-block;
}

/* A solid, fully-rounded pill (not this theme's usual outlined/icon
 * .btn treatment) - matching the reference's own button style
 * specifically, and reading clearly as "the one action" against a
 * solid-colour banner the way an outlined button wouldn't. */
.fl-featured-product__btn {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	padding: 1.6rem 3.2rem;
	border-radius: 100px;
	background-color: #ffffff;
	color: #0e686c;
	font: normal 700 1.3rem/1 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.06rem;
	text-decoration: none;
	transition: transform var(--_animspeed-medium, 0.3s), box-shadow var(--_animspeed-medium, 0.3s);
}

.fl-featured-product__btn:hover,
.fl-featured-product__btn:focus-visible {
	transform: translateY(-2px);
	box-shadow: 0 12px 24px rgba(0, 0, 0, 0.18);
}

/* Featured-product SLIDER (template-parts/homepage/featured_products.php)
 * - only present when more than one product is ticked Featured; a single
 * one still renders the plain .fl-featured-product above with no
 * wrapper at all. Swiper's own pagination re-themed to white/translucent-
 * white (not --fl-accent's teal, which would nearly disappear against
 * this section's own teal-to-dark-teal gradient) - the same rgba(255,
 * 255, 255, *) language the eyebrow/tagline/price-was already use here.
 * No nav arrows (autoplay + dots is enough chrome for a compact CTA
 * section); content-sliders.js initialises it. */
.fl-featured-product-slider__swiper {
	--swiper-pagination-color: #ffffff;
	--swiper-pagination-bullet-inactive-color: #ffffff;
	--swiper-pagination-bullet-inactive-opacity: 0.35;
	padding-bottom: 3.6rem;
}

.fl-featured-product-slider__swiper .swiper-pagination {
	bottom: 0;
}

/* Product screenshots slider (template-parts/product-gallery.php, single-
 * fl_product.php) - a light neutral stage (not white, so a screenshot
 * with a white/transparent background still reads as a distinct panel)
 * with object-fit:contain, so varied screenshot aspect ratios never crop
 * UI chrome out of frame. Pagination/nav re-themed to --fl-accent (this
 * section sits on plain white/light background, unlike the spotlight
 * slider above it). */
.fl-product-gallery__swiper {
	--swiper-theme-color: var(--fl-accent);
	max-width: 84rem;
	margin: 0 auto;
	border-radius: var(--fl-radius-lg, 1.6rem);
	overflow: hidden;
}

.fl-product-gallery__swiper .swiper-wrapper {
	align-items: stretch;
}

.fl-product-gallery__swiper .swiper-slide {
	aspect-ratio: 16 / 10;
	background: var(--fl-bg-alt, #f5f7fb);
	display: flex;
	align-items: center;
	justify-content: center;
}

.fl-product-gallery__image {
	width: 100%;
	height: 100%;
	object-fit: contain;
	display: block;
}

.fl-product-gallery__swiper .swiper-pagination-bullet {
	background: var(--fl-fg-muted, #5b6178);
	opacity: 0.5;
}

.fl-product-gallery__swiper .swiper-pagination-bullet-active {
	opacity: 1;
}

/* Expand-to-fullscreen button, top-right corner of the gallery -
 * requested directly ("the slider of the screenshot should be expandable
 * in a full screen modal"). A whole slide is also clickable (cursor
 * hints at it) - see content-sliders.js. */
.fl-product-gallery {
	position: relative;
}

.fl-product-gallery__expand {
	position: absolute;
	top: 1.2rem;
	right: 1.2rem;
	z-index: 2;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 4rem;
	height: 4rem;
	border: none;
	border-radius: 50%;
	background: rgba(18, 22, 42, 0.55);
	color: #ffffff;
	font-size: 1.8rem;
	line-height: 1;
	cursor: pointer;
	transition: background-color var(--_animspeed-medium, 0.3s);
}

.fl-product-gallery__expand:hover,
.fl-product-gallery__expand:focus-visible {
	background: rgba(18, 22, 42, 0.8);
}

.fl-product-gallery__swiper .swiper-slide {
	cursor: zoom-in;
}

/* Full-screen lightbox (template-parts/product-gallery.php's own doc
 * comment explains why it's relocated to <body> by content-sliders.js
 * before use - position:fixed here would otherwise be scoped to
 * whichever transformed ancestor it happened to still be inside).
 * z-index above the WP admin bar (99999) too, so an admin testing this
 * gets a genuinely full-screen view, not one with the toolbar cutting
 * into it. */
.fl-lightbox {
	position: fixed;
	inset: 0;
	z-index: 999999;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 2.4rem;
}

.fl-lightbox[hidden] {
	display: none;
}

.fl-lightbox__backdrop {
	position: absolute;
	inset: 0;
	background: rgba(6, 8, 16, 0.92);
}

.fl-lightbox__close {
	position: absolute;
	top: 2rem;
	right: 2rem;
	/* Above .fl-lightbox__dialog (z-index: 1, and later in the DOM) -
	 * equal z-index falls back to DOM order, so the dialog (width/
	 * height: 100%, covering the same top-right corner) was painting
	 * over this button and eating its clicks - visible, but nothing to
	 * click ("the close button... does not close"). */
	z-index: 2;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 4.4rem;
	height: 4.4rem;
	border: none;
	border-radius: 50%;
	background: rgba(255, 255, 255, 0.1);
	color: #ffffff;
	font-size: 2rem;
	line-height: 1;
	cursor: pointer;
	transition: background-color var(--_animspeed-medium, 0.3s);
}

.fl-lightbox__close:hover,
.fl-lightbox__close:focus-visible {
	background: rgba(255, 255, 255, 0.2);
}

.fl-lightbox__dialog {
	position: relative;
	z-index: 1;
	width: 100%;
	height: 100%;
	max-width: 140rem;
}

.fl-lightbox__swiper {
	--swiper-theme-color: #ffffff;
	width: 100%;
	height: 100%;
}

.fl-lightbox__swiper .swiper-slide {
	display: flex;
	align-items: center;
	justify-content: center;
}

.fl-lightbox__image {
	max-width: 100%;
	max-height: 100%;
	width: auto;
	height: auto;
	object-fit: contain;
}

/* Body-scroll lock while the lightbox is open (content-sliders.js toggles
 * this on <html>, not <body> - some mobile browsers only honour an
 * overflow lock on the root element). */
html.fl-lightbox-open {
	overflow: hidden;
}

/* Product page hero (template-parts/product-hero.php). Third pass -
 * "dont get it twisted. i want the title area to still have the general
 * title featured background, however, in the product page, i want the
 * product image to display on the right of the title section as it
 * currently does": .fl-project-hero is added alongside .fl-product-hero
 * on the same element, reusing detail-banner.php's own full-bleed
 * background-photo + dark-overlay + sizing wholesale (its CSS, further
 * up this file) rather than a parallel copy - so does .fl-project-hero__
 * inner on the text wrapper (also reused directly, not renamed), which
 * is what actually puts the title above the overlay (position:relative;
 * z-index:1) - a plain differently-named wrapper class here would have
 * had neither and sat *underneath* the background image instead
 * (positioned elements paint above non-positioned ones regardless of
 * source order). On top of that shared background, the (still capped at
 * 14rem, still object-fit:contain so it's always fully visible) product
 * image keeps floating over the column's top-right corner exactly as
 * the second pass built it - now simply layered above the photo instead
 * of the plain page background. The title column itself still uses the
 * same container/row/column markup as detail-overview.php's manifest
 * paragraph beneath it (col-12 inside the same mxd-container.grid-l-
 * container) - restoring the background didn't reopen the earlier
 * "title area width should match the subtitle beneath it" issue, since
 * that's a column-width concern independent of what's painted behind it. */
.fl-product-hero__col {
	position: relative;
	margin-bottom: 0;
}

.fl-product-hero__crumbs {
	margin-bottom: 1.5rem;
	font: normal 600 1.3rem/1.4 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.02rem;
	color: rgba(255, 255, 255, 0.7);
}

.fl-product-hero__crumbs a {
	color: rgba(255, 255, 255, 0.7);
	text-decoration: underline;
}

.fl-product-hero__title {
	max-width: 75%;
	margin: 0;
	color: #ffffff;
	font-size: 3.4rem;
	line-height: 1.12;
	letter-spacing: -0.06rem;
}

@media only screen and (min-width: 768px) {
	.fl-product-hero__title {
		font-size: 4.6rem;
	}
}

/* Stacked below the title on narrow screens (there's no spare corner to
 * float it in without overlapping the title once it wraps to more than
 * one line) - absolutely positioned only from 768px, where a short
 * product title reliably leaves the top-right corner clear. */
.fl-product-hero__media {
	margin-top: 1.5rem;
}

/* A definite height (not max-height) - "i no longer see the product
 * image" after capping it. This SVG's own root element sets
 * width="100%" height="100%" (a percentage, not a usable intrinsic
 * size) and the <img> tag itself carries no width/height attributes, so
 * with only max-height/width:auto to go on it's a replaced element with
 * a known aspect ratio but no intrinsic size to scale from - browsers
 * don't agree on that case, and rendering it at zero height is a real
 * possible outcome, not just a theoretical one. height:14rem is
 * unambiguous; width:auto still scales from the image's real aspect
 * ratio exactly as before. */
.fl-product-hero__image {
	display: block;
	height: 14rem;
	width: auto;
	max-width: 100%;
	object-fit: contain;
}

@media only screen and (min-width: 768px) {
	/* Centred between the section's own top and bottom edge (requested
	 * directly), not pinned to the top of the title column - top: 50% +
	 * translateY(-50%) against .fl-product-hero__col (its containing
	 * block). The column's own vertical centre already coincides with
	 * the section's: .fl-project-hero centres .fl-project-hero__inner
	 * within itself (align-items: center), that wrapper's padding is
	 * equal top/bottom, and .fl-product-hero__col carries no padding or
	 * margin of its own beneath it - centring against the column is the
	 * same point as centring against the section, without needing to
	 * restructure the markup to position against the section directly
	 * (which would also lose this same right edge lining up with the
	 * title's own container). */
	.fl-product-hero__media {
		position: absolute;
		top: 50%;
		right: 0;
		margin-top: 0;
		transform: translateY(-50%);
	}
}

/* Newsletter signup (template-parts/newsletter-signup.php) - homepage
 * only now, inside this section specifically (moved out of the footer,
 * where it rendered on every page looking unstyled and out of place -
 * reported directly). Styled against this section's own green gradient
 * background, not a generic light-theme form - white/translucent-white
 * throughout, same white-pill button language as
 * .fl-featured-product__btn above it rather than the accent-coloured
 * .fl-button-primary, which would all but disappear against a
 * background this close to --fl-accent itself. */
/* Elevated card instead of a hard divider line above it (removed,
 * requested directly) - a soft shadow reads as "this sits above/in
 * front of the section" without a literal rule cutting across the
 * page. */
/* Width matches .fl-hero-domain-overlay's own width formula exactly -
 * requested directly ("make the 'Stay in the loop' section subscribe
 * form card same width as the hero domain checker card width"). This
 * card had no width rule of its own before, so it stretched to whatever
 * its wrapping section happened to be (much wider than the hero card). */
.fl-newsletter-signup {
	width: min(860px, calc(100% - 4rem));
	margin: 3.2rem auto 0;
	padding: 3.2rem;
	background: rgba(255, 255, 255, 0.05);
	border-radius: 2rem;
	box-shadow: 0 30px 70px rgba(0, 0, 0, 0.45);
}

.fl-newsletter-signup__heading {
	margin: 0 0 0.4rem;
	color: #ffffff;
	font-weight: 700;
	font-size: 1.6rem;
}

.fl-newsletter-signup__subheading {
	margin: 0 0 1.4rem;
	color: rgba(255, 255, 255, 0.8);
	font-size: 1.35rem;
}

/* Width/button treatment now matches .fl-hero-domain-overlay's own form
 * exactly - requested directly ("make the input form width and button
 * style similar"). max-width:42rem (420px) previously left this form
 * floating narrower than the card it now sits in (widened to 860px in
 * the same pass as the card itself) - same "form floating narrower than
 * its card" gap the hero's own form had before that was freed. column-
 * gap:0 (not the shorthand gap, which would also zero the wrap-to-a-new-
 * line spacing the error message needs) merges input+button into one
 * continuous attached pill instead of two separate pills with a space
 * between them, exactly like the hero's search row. */
.fl-newsletter-signup__form {
	display: flex;
	flex-wrap: wrap;
	row-gap: 0.8rem;
	column-gap: 0;
	max-width: none;
}

.fl-newsletter-signup__form input[type="email"] {
	flex: 1 1 20rem;
	min-width: 0;
	box-sizing: border-box;
	height: 5.6rem;
	padding: 0 1.6rem;
	line-height: 5.6rem;
	border: 1px solid rgba(255, 255, 255, 0.35);
	border-radius: 100px 0 0 100px;
	background: rgba(255, 255, 255, 0.1);
	color: #ffffff;
}

/* main.min.css's own `form input:required:valid { color: var(--t-bright) }`
 * (and its :focus:required:invalid sibling) is more specific than the base
 * rule above and, since --t-bright follows the SITE's light/dark mode not
 * this dark section's own bg-color-opposite, resolves to near-black on a
 * light-mode site - so a valid email typed in went invisible against the
 * dark CTA panel (reported directly: "the entered text [should] be white").
 * These match the vendor's own pseudo-class selectors to win on source
 * order and keep the text white in every state. */
.fl-newsletter-signup__form input[type="email"]:focus,
.fl-newsletter-signup__form input[type="email"]:required:valid,
.fl-newsletter-signup__form input[type="email"]:focus:required:invalid {
	color: #ffffff;
}

.fl-newsletter-signup__form input[type="email"]::placeholder {
	color: rgba(255, 255, 255, 0.65);
}

/* Placeholder clears the moment the field is focused (reported directly:
 * "clicking the email address form... I want the placeholder to
 * disappear") rather than only once the visitor starts typing. */
.fl-newsletter-signup__form input[type="email"]:focus::placeholder {
	color: transparent;
}

/* Inverted from white-fill/teal-text to accent-fill/white-text, and
 * attached flat against the input's own flat right edge - same button
 * treatment .fl-hero-domain-overlay's own button uses (requested
 * directly: "button style similar" to the hero's). */
.fl-newsletter-signup__form .fl-button {
	border-radius: 0 100px 100px 0;
	background-color: var(--fl-accent, #0e686c);
	color: #ffffff;
	border: none;
	font: normal 700 1.3rem/1 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.06rem;
	box-sizing: border-box;
	height: 5.6rem;
	padding: 0 2.4rem;
}

.fl-newsletter-signup__form .fl-button:hover {
	background-color: #0a5559;
}

.fl-newsletter-signup__message {
	margin: 0;
	color: #ffffff;
}

.fl-newsletter-signup__error {
	flex-basis: 100%;
	font-size: 1.2rem;
	color: #ffd7d4;
}

/* Mobile: the email input's 20rem (320px) flex-basis plus the button's
 * own padding regularly add up to more than this card's inner width
 * once its 3.2rem horizontal padding is subtracted from a phone
 * viewport, so flex-wrap pushes the button onto its own line below the
 * input (reported directly - "the button shifts downwards... perhaps
 * due to the width of the card"). The hero's own domain-checker card
 * (.fl-hero-domain-overlay, above) stays on one line at the same
 * widths because it tightens its own card padding and field sizing on
 * mobile the same way - mirroring that here instead of just this
 * form's own rules, since the card's padding is as much a factor as the
 * input's basis. */
@media (max-width: 767px) {
	.fl-newsletter-signup {
		padding: 2rem;
	}

	.fl-newsletter-signup__form input[type="email"] {
		flex-basis: 12rem;
		height: 5rem;
		padding: 0 1.3rem;
		line-height: 5rem;
		font-size: 1.5rem;
	}

	.fl-newsletter-signup__form .fl-button {
		height: 5rem;
		padding: 0 1.6rem;
		font-size: 1.2rem;
	}
}

/* ---------------------------------------------------------------
 * Hero slider + domain checker overlay (requested directly - "no
 * longer a downward slider, instead a regular slider without any caret
 * or dots"; "I prefer the domain checker to be on the hero... a fixed
 * transparent card that appears on each hero regardless of the
 * sliding"). Replaces the earlier scroll-triggered position:sticky
 * title/subtitle mechanism entirely - see hero.php/hero-slider.js.
 * New classes throughout, not touching .mxd-hero-section/.mxd-hero-02
 * themselves, so nothing else that also uses those classes is affected.
 * --------------------------------------------------------------- */

/* z-index:0 (on top of the position:relative it already had) deliberately
 * turns this into its own stacking context - reported directly: "I no
 * longer see the logo and some header items". Root cause: main.min.css's
 * <header> is "position:absolute;z-index:1" but nothing between it and
 * the document root establishes a stacking context of its own, so every
 * z-index used inside the hero (the slide cover image's z-index:1, the
 * domain overlay's z-index:6, ...) was being compared DIRECTLY against
 * the header's z-index:1 in that same shared (root) context - and on an
 * exact tie, the element later in the DOM wins regardless of the numbers
 * involved, which is the hero (it renders after <header>). Confirmed live
 * (curled the rendered page - the header markup/logo <img> was present
 * and correctly classed, only the paint order was wrong). Giving the
 * whole section an explicit z-index seals every descendant z-index inside
 * one atomic layer that then sits at "0" in the root context - always
 * below the header's "1" - so nothing added inside the hero can ever
 * re-cover the header again, no matter what z-index it uses. */
.fl-hero-section {
	position: relative;
	z-index: 0;
}

/* Vendor's own dark tint over the whole hero (video + slides alike) -
 * main.min.css: ".mxd-hero-02__cover{background-color:rgba(0,0,0,.4);
 * mix-blend-mode:multiply}", a plain sibling div in .mxd-hero-02__background
 * (hero.php). Separate from, and in addition to, the per-slide cover
 * image's own opacity - this one sits over literally everything.
 * Removed entirely - requested directly ("remove the color overlay on
 * the hero entirely"). */
.fl-hero-section .mxd-hero-02__cover {
	background-color: transparent;
	mix-blend-mode: normal;
}

/* fl-hero-02-* (not fl-hero-*) throughout this block - see the doc
 * comment in template-parts/homepage/hero.php on why these are prefixed
 * this way. */
/* position:absolute + inset:0 (not position:relative + width/height:100%)
 * - reported directly: "the fixed background... occupies full
 * dimensions, however, the slide... seems to be an overlay that is
 * boxed... I want each slide to be a full hero not an overlay." Root
 * cause: .mxd-hero-02 (vendor CSS) has "padding:2rem". The shared video
 * background (.mxd-hero-02__background) is itself position:absolute,
 * so it's sized against .mxd-hero-02's *padding box* and ignores that
 * padding entirely - full-bleed edge to edge. This slider was still a
 * normal-flow child, so it sat inside .mxd-hero-02's *content box*
 * instead - inset by that same 2rem on every side, reading as a boxed
 * overlay floating over the full-bleed video rather than a full hero
 * slide in its own right. Matching the background's own positioning
 * (absolute, inset:0) makes every slide's cover image - and the slide
 * as a whole - genuinely full-bleed, exactly like the video beneath it. */
.fl-hero-02-slider {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
}

.fl-hero-02-slide {
	position: relative;
	display: flex;
	align-items: flex-start;
	justify-content: center;
	width: 100%;
	height: 100%;
	/* align-items:center (dead-center of the full hero height) put the
	 * title/subtitle right on top of where the domain card also needed
	 * to sit, pushing the whole cluster down toward the bottom third -
	 * reported directly: "it is too low towards the base of the hero."
	 * A clamped top offset instead - well below the header, comfortably
	 * above the domain card's own "bottom" position further down.
	 * Nudged slightly back down again from that first pass - requested
	 * directly ("shift the hero title, subtitle and the domain card a
	 * bit downwards"). */
	padding-top: clamp(10.5rem, 25vh, 17.5rem);
	box-sizing: border-box;
	text-align: center;
}

/* Single-slide sites (no .swiper class added by hero.php - see its own
 * PHP) still need the slide to actually occupy the hero rather than
 * relying on Swiper's own slide sizing, which never initialises. */
.fl-hero-02-slider:not(.swiper) .fl-hero-02-slide {
	position: absolute;
	inset: 0;
}

.fl-hero-02-slide__cover {
	position: absolute;
	inset: 0;
	z-index: 1;
}

.fl-hero-02-slide__cover img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	/* 0.35 (against .mxd-hero-02's own dark background-color showing
	 * through the rest) read as a heavy dark overlay on the image -
	 * reported directly ("make the overlay lighter a bit"). Bumped
	 * moderately, not removed - the title/subtitle still need to stay
	 * legible over whatever photo is showing. */
	opacity: 0.55;
}

.fl-hero-02-slide__content {
	position: relative;
	z-index: 2;
	max-width: 900px;
	padding: 0 2rem;
}

/* Explicit font-size/weight/color (not just the vendor's own .medium
 * class) - reported directly: "the hero title is too large in the first,
 * and very little in the second." Root cause: main.min.css only ever
 * sizes ".medium" via a "h1.medium{font-size:...}" tag-qualified
 * selector, never a bare ".medium{...}" - so it silently did nothing for
 * slides 2-4, which use a <p> (only slide 1 is a real <h1>, kept singular
 * for SEO). Slide 1 therefore rendered at the vendor's own hero-scale
 * (8.5-12rem) while slides 2-4 fell all the way back to a plain
 * paragraph's font-size - hence "huge" vs "very little." One explicit,
 * tag-independent rule here now governs every slide's title identically,
 * clamped well below that 8.5-12rem vendor scale (already read as
 * dominant even at slide 1's size) but still a bold hero statement. */
.fl-hero-02-slide__title {
	display: block;
	margin: 0;
	font-family: var(--_font-default, inherit);
	font-weight: 600;
	font-size: clamp(3rem, 6vw, 6.5rem);
	/* 1.1 (not the "g" in "grow"/"business" was reported cropped - a
	 * line-height that tight left no room for descenders inside the
	 * per-line masks (.fl-split-line, style.css) GSAP's SplitText wraps
	 * around slide 1's h1 for its data-reveal-text slide-up animation -
	 * both that wrapper and [data-reveal-text] itself are overflow:
	 * hidden, so anything a line-box doesn't have room for gets clipped,
	 * not just visually tight. */
	line-height: 1.22;
	letter-spacing: -0.02em;
	color: var(--nl-white, #fff);
	will-change: opacity, transform;
}

.fl-hero-02-slide__subtitle {
	display: block;
	margin: 1.2rem 0 0;
	font-size: clamp(1.5rem, 1.6vw, 1.8rem);
	font-style: italic;
	line-height: 1.4;
	color: rgba(255, 255, 255, 0.82);
	will-change: opacity, transform;
}

/* The domain checker overlay - a fixed, translucent "glass" card that
 * stays in place regardless of which slide is showing (it sits outside
 * .fl-hero-slider entirely, in its own stacking layer). Reuses the
 * compact widget as-is (template-parts/domain-checker.php) - only this
 * wrapper is hero-specific. */
/* Sized up twice now ("even larger than this", requested directly), and
 * its vertical position has moved twice too - up from 14% to 22% to 30%
 * ("shift the card higher"), then nudged back down slightly to 26%
 * ("shift... the domain card a bit downwards", requested directly).
 * border-radius reverted from a full 999px pill back to a more modest
 * curve ("revert only the card's border radius to be less curved than
 * it currently is", requested directly) - .fl-domain-entry__input/__btn
 * below keep their own 999px pill shape, only the outer card's own
 * radius changed. */
.fl-hero-domain-overlay {
	position: absolute;
	left: 50%;
	bottom: 26%;
	transform: translateX(-50%);
	z-index: 6;
	width: min(860px, calc(100% - 4rem));
	padding: 2.8rem 3.8rem;
	border-radius: 2.8rem;
	background: rgba(11, 17, 32, 0.38);
	backdrop-filter: blur(14px);
	-webkit-backdrop-filter: blur(14px);
	border: 1px solid rgba(255, 255, 255, 0.14);
}

/* bottom:26% is a percentage of the hero's own height, with no idea how
 * tall .fl-hero-02-slide__title/__subtitle actually render above it -
 * fine on a tall viewport, but confirmed directly (measuring real
 * rendered rects, not just guessing) that it overlaps the subtitle text
 * the moment the window gets short: a longer translation that wraps to
 * 3 lines (Italian's "Traduzione di siti web, risolta...") already
 * overlaps by ~4px at a plain 1440x900 window, and by over 160px at
 * 1320x676 - reported directly as "the hero title and sometimes its
 * subtitles encroach into the search card", worse on a wider desktop
 * monitor than a laptop simply because desktop browser windows commonly
 * run shorter relative to their width. min-width:1024px keeps mobile's
 * own separate positioning (top:58%/bottom:auto, further down) untouched
 * - this only covers the desktop layout that uses bottom:26% at all.
 *
 * bottom:13% (this rule's first pass) cleared the title but immediately
 * overlapped .fl-hero-icon-marquee instead (reported directly right
 * after - "the search card now overlaps the scrolling icons") - that
 * marquee sits at its own fixed bottom:8%/height:9rem, independent of
 * this card, so pushing the card further down to clear the title just
 * walked it straight into the marquee below. bottom:24% plus a smaller
 * padding (frees more of the card's own height) threads both gaps at
 * once - confirmed directly against both a 900px and a 676px window. */
@media (min-width: 1024px) and (max-height: 950px) {
	.fl-hero-02-slide__title {
		font-size: clamp(3rem, 5vw, 5rem);
	}

	.fl-hero-domain-overlay {
		bottom: 24%;
		padding: 2rem 3.8rem;
	}

	.fl-hero-domain-overlay__intro {
		margin-bottom: 1rem;
	}
}

/* Past a point there just isn't enough room between a 3-line title and
 * the icon marquee for the card's full content regardless of its
 * position - confirmed directly (a plain 1320x676 window still overlaps
 * the title by ~18px even with the above tier's smaller card). The
 * reassurance line is the least essential part of the card's own copy
 * (the main intro sentence and the actual input/button carry the real
 * content), so it's what gives here first. */
@media (min-width: 1024px) and (max-height: 760px) {
	.fl-hero-domain-overlay {
		padding: 1.4rem 3.8rem;
	}

	.fl-hero-domain-overlay__intro {
		margin-bottom: 0.6rem;
	}

	.fl-hero-domain-overlay__intro-note {
		display: none;
	}
}

/* Intro copy above the input row - requested directly ("Search a domain
 * or describe your project - we'll guide you from there. No obligation,
 * no reservation."). Same white/light treatment as the widget's own
 * .fl-domain-entry__alt link below the form - this text also sits
 * directly on the dark glass card, not inside the light input/button
 * "cards" themselves. */
.fl-hero-domain-overlay__intro {
	margin-bottom: 1.6rem;
	text-align: center;
}

.fl-hero-domain-overlay__intro-text {
	margin: 0;
	font-size: 1.7rem;
	font-weight: 600;
	line-height: 1.4;
	/* Light yellow - requested directly. */
	color: #fef08a;
}

.fl-hero-domain-overlay__intro-note {
	margin: 0.4rem 0 0;
	font-size: 1.3rem;
	color: rgba(255, 255, 255, 0.7);
}

/* The shared widget's own .fl-domain-entry caps at max-width:560px
 * (right for its other, narrower placements) - freed here so the form
 * actually fills this wider card instead of floating narrower inside it
 * ("also applies to the form", requested directly). */
.fl-hero-domain-overlay .fl-domain-entry {
	max-width: none;
}

/* Button merged INTO the input as one continuous pill instead of two
 * separate pill controls with a gap between them - requested directly:
 * "I do not want the button to be outside the input field. I want it to
 * be inside such that the left part of it has no radius and is straight
 * while... the right [end] seem[s] to look like the right end of the
 * input field." No gap, no wrap - the two share one outer silhouette:
 * input rounded on its outer (left) end only, button rounded on its
 * outer (right) end only, flat/straight where they meet in the middle.
 * A fixed, equal height on both (rather than trusting padding+line-height
 * to match between an <input> and a <button>) is what actually keeps
 * that shared seam pixel-flush. */
.fl-hero-domain-overlay .fl-domain-entry__search {
	gap: 0;
	flex-wrap: nowrap;
}

.fl-hero-domain-overlay .fl-domain-entry__input {
	background: rgba(255, 255, 255, 0.96);
	border: none;
	border-radius: 999px 0 0 999px;
	box-sizing: border-box;
	height: 6.4rem;
	padding: 0 2.4rem;
	/* line-height matching height - an <input> isn't a flex container for
	 * its own text like .fl-button is (align-items:center there), so with
	 * padding:0 vertically it needs this to actually center the text in
	 * the fixed height rather than sitting top-aligned. */
	line-height: 6.4rem;
	font-size: 1.7rem;
	flex: 1 1 auto;
	min-width: 0;
}

/* Inverted from the first pass (white fill, accent text) - requested
 * directly ("the button color should be inversed with its text"): solid
 * accent fill with white text. */
.fl-hero-domain-overlay .fl-domain-entry__btn {
	background: var(--fl-accent, #0e686c);
	color: #fff;
	border: none;
	border-radius: 0 999px 999px 0;
	box-sizing: border-box;
	height: 6.4rem;
	padding: 0 3rem;
	font-size: 1.6rem;
	font-weight: 700;
	flex: 0 0 auto;
}

.fl-hero-domain-overlay .fl-domain-entry__btn:hover {
	background: #0a5559;
}

/* Solid near-white (not the base widget's rgba(255,255,255,.85)) -
 * reported directly: "the domain checker support texts outside of the
 * cards has to be white or lighter texts that contrasts against the
 * darker background." The input and button are their own light "cards"
 * (opaque white backgrounds, dark text - already legible); this link is
 * the one piece of widget text sitting directly on the dark glass card
 * itself, so it gets the strongest, most deliberately legible treatment
 * rather than a softened alpha. */
.fl-hero-domain-overlay .fl-domain-entry__alt {
	color: #f5f7fa;
	font-weight: 600;
}

.fl-hero-domain-overlay .fl-domain-entry__alt:hover {
	color: #fff;
}

/* Tech-icon marquee - replaces the old 3D "zoom in" scatter rail
 * (assets/js/hero-icons-autoplay.js's retired initHeroIcons(), see its
 * own comment) with a continuous right-to-left strip underneath the
 * domain card - requested directly. Animation itself (translateX loop +
 * per-item scale based on distance from center) is assets/js/hero-icon-
 * marquee.js; this is purely the static layout it animates within.
 * Edge-to-edge (not width-matched to the card) - a marquee reads as
 * content entering/exiting the viewport, which only makes sense running
 * the hero's full width. overflow:hidden crops the doubled item list
 * down to one visible window; the mask-image fade (not just the scale
 * shrinking toward the edges) keeps entries/exits soft rather than a
 * hard clip line. */
/* Visible width matches .fl-hero-domain-overlay's own width formula
 * exactly (not edge-to-edge) - requested directly ("the beginning and
 * end of the scroll area should be the width of the checker card above
 * it"). The JS reads this element's actual clientWidth at runtime
 * (hero-icon-marquee.js's measure()), so narrowing it here is the whole
 * fix - nothing to change on the JS side for this part. */
.fl-hero-icon-marquee {
	position: absolute;
	left: 50%;
	bottom: 8%;
	transform: translateX(-50%);
	z-index: 4;
	width: min(860px, calc(100% - 4rem));
	height: 9rem;
	overflow: hidden;
	-webkit-mask-image: linear-gradient(90deg, transparent 0, #000 12%, #000 88%, transparent 100%);
	mask-image: linear-gradient(90deg, transparent 0, #000 12%, #000 88%, transparent 100%);
}

.fl-hero-icon-marquee__track {
	display: flex;
	align-items: center;
	width: max-content;
	will-change: transform;
}

.fl-hero-icon-marquee__item {
	display: flex;
	flex: 0 0 auto;
	align-items: center;
	justify-content: center;
	width: 9rem;
	height: 9rem;
	margin-right: 2.4rem;
	will-change: transform;
}

.fl-hero-icon-marquee__item img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	border-radius: var(--fl-radius-lg, 16px);
}

/* Tech-stack default set (no admin photo upload - see hero.php): plain
 * logos, not full-bleed photos - object-fit:contain and no rounded photo
 * frame, same reasoning as the old rail's own tech-tile treatment.
 * Recolored to a flat light gray, not each icon's own brand colors
 * (requested directly: "the logo should be light grayish instead of its
 * actual colors"). These are external-file <img> SVGs (self-hosted
 * Simple Icons, fl_tech_stack()), not inline <svg> markup, so a CSS
 * fill/color override has nothing to attach to - brightness(0) first
 * crushes every icon to solid black regardless of its original hue,
 * invert(1) flips that to solid white, then opacity(...) settles it at a
 * muted light gray rather than stark white against the dark hero. */
.fl-hero-icon-marquee__item--tech img {
	width: 60%;
	height: 60%;
	object-fit: contain;
	border-radius: 0;
	filter: brightness(0) invert(1) opacity(0.55) drop-shadow(0 4px 10px rgba(0, 0, 0, 0.45));
}

/* Social links + "Scroll to explore" removed from the hero everywhere
 * (originally mobile-only - a phone render had this row competing with
 * the language-suggestion banner and AI chat launcher for the same
 * bottom strip - now reported unwanted on desktop too, so the hide is
 * unconditional). main.min.css gives .mxd-hero-02__dataline
 * "justify-content:space-between", which would otherwise leave a
 * stretched gap where .mxd-hero-02__socials used to sit - display:none
 * on the dataline's own children removes that gap along with them. */
.mxd-hero-02__socials,
.mxd-hero-02__controls {
	display: none;
}

@media (max-width: 767px) {
	/* Vertically centered instead of anchored near the base - requested
	 * directly ("in the mobile view, move the checker card to the
	 * middle"). bottom:auto is needed alongside top:50% - with both
	 * top and bottom set (non-auto) on an absolutely positioned element
	 * with height:auto, the browser stretches it to fill the gap between
	 * them instead of sizing to its own content.
	 *
	 * top:58% (not 50%) - dead center overlapped the hero title's last
	 * line above it (confirmed live: "FISHER LABS" tagline text was
	 * hidden behind the card's own top edge), so nudged down a bit
	 * ("move the checker card a bit downward in mobile", requested
	 * directly) - still comfortably clear of the socials row/scroll cue
	 * further down. */
	.fl-hero-domain-overlay {
		top: 58%;
		bottom: auto;
		transform: translate(-50%, -50%);
		padding: 1.8rem 1.6rem;
		border-radius: 2.8rem;
	}

	.fl-hero-domain-overlay .fl-domain-entry__input {
		height: 5.2rem;
		padding: 0 1.6rem;
		line-height: 5.2rem;
		font-size: 1.5rem;
	}

	.fl-hero-domain-overlay .fl-domain-entry__btn {
		height: 5.2rem;
		padding: 0 1.8rem;
		font-size: 1.4rem;
	}

	.fl-hero-icon-marquee {
		bottom: 6%;
		height: 6.4rem;
	}

	.fl-hero-icon-marquee__item {
		width: 6.4rem;
		height: 6.4rem;
		margin-right: 1.6rem;
	}

	/* Fixed height - the real bug behind "sections beneath jump when the
	 * slider transitions" (reported directly, after the removals above
	 * still hadn't fixed it). Root cause: main.min.css declares height
	 * TWICE - "height:100svh;height:calc(var(--vh) * 100)" - and with two
	 * valid declarations of the same property, the LAST one wins outright
	 * on every modern browser, not "svh where supported, JS fallback
	 * otherwise" as the pattern implies. So --vh (app.min.js, only
	 * recalculated on resize/orientationchange - confirmed reading that
	 * function directly) is what actually sizes the hero: a pixel value
	 * frozen from window.innerHeight at whatever moment it last fired,
	 * which on a real phone is however tall the viewport was WITH the
	 * address bar showing. The hero box then stays pinned at that stale
	 * height while the browser's own address bar collapses during normal
	 * scroll/interaction (never a 'resize' event) and the actual viewport
	 * grows - everything else on the page reflows against the real,
	 * current viewport, so the mismatch surfaces as the content below the
	 * hero visibly shifting. 100svh (small viewport height) exists
	 * specifically to stay correct through exactly that address-bar
	 * show/hide, no JS needed - reversing the order here so it's declared
	 * LAST makes it the one that actually wins, instead of the stale JS
	 * fallback. */
	.mxd-hero-02 {
		height: calc(var(--vh, 1vh) * 100);
		height: 100svh;
	}

	/* Mobile menu item text - main.min.css's own base size for
	 * .main-menu__caption (the nav overlay's actual item label, per
	 * FL_Azurio_Menu_Walker in functions.php) is 3.4rem/34px, sized for
	 * the 1600px+ desktop overlay it was designed around; every
	 * intermediate breakpoint just repeats that same 3.4rem, so a phone
	 * gets the same size as a small laptop - reported directly as "too
	 * large" on mobile. */
	.main-menu__caption {
		font-size: 2.6rem;
	}
}

/* ---------------------------------------------------------------
 * Header hamburger / menu logo contrast (requested directly)
 * ---------------------------------------------------------------
 * The hamburger's own internal-pages contrast fix already existed
 * (body:not(.home) .hamburger__line, further up this file) from
 * earlier work - just missing the :not(.active) scoping that keeps it
 * from also darkening the open/X state, fixed there directly rather
 * than duplicated here. */

/* The menu overlay's own logo (.mxd-menu__logo) is a separate DOM
 * subtree from the header's (.mxd-header__logo) - Azurio's light/dark
 * logo swap rules only ever targeted .mxd-header-permanent, so this
 * element was never covered by them and always showed the light-mode
 * (dark-colored) logo variant, illegible against the overlay's own
 * always-dark backdrop on every page, not just internal ones. Forced to
 * the dark-mode (light-colored) variant unconditionally instead - the
 * overlay's background never changes with page type, so neither should
 * its logo. Same :root-prefix specificity trick already proven for the
 * homepage header's own logo above (style.css, .mxd-header-permanent
 * .fl-logo-light/.fl-logo-dark) - needed to beat main.min.css's own
 * :root:not([color-scheme=dark]) .fl-logo-dark{display:none} rule. */
:root .mxd-menu__logo .fl-logo-light {
	display: none;
}

:root .mxd-menu__logo .fl-logo-dark {
	display: inline-flex;
}

/* fl-logo-solo (only one logo variant uploaded, no dark-mode
 * counterpart to swap to) gets the same light-pill treatment the
 * homepage header already uses for the same reason (style.css,
 * .mxd-header-permanent .fl-logo-solo) - a plain dark-colored logo
 * would be just as illegible against the overlay's always-dark backdrop
 * as it would be against the homepage's dark hero, on any page. */
:root .mxd-menu__logo .fl-logo-solo {
	background-color: rgba(255, 255, 255, 0.92);
	border-radius: 6px;
	padding: 0.4rem 0.6rem;
}

/* ---------------------------------------------------------------
 * Autoplay video "play" glyph (requested directly - "it does not
 * really autoplay on safari browsers... i do not want to display the
 * play icon regardless").
 *
 * Several WebKit-prefixed pseudo-elements were tried first
 * (::-webkit-media-controls-start-playback-button, -overlay-play-
 * button, -overlay-enclosure, and the whole -media-controls tree) and
 * NONE of them actually hid it - confirmed directly with a real WebKit
 * render (Playwright's own webkit engine, not just Chromium, which
 * doesn't reproduce this at all since its autoplay policy is more
 * lenient). Chromium and WebKit both use the -webkit- prefix for their
 * own vendor pseudo-elements (Chromium/Blink being a WebKit fork
 * historically) but don't necessarily define the *same* names under
 * it, so there's no reliable name to target here at all.
 *
 * The actual fix - video-autoplay-safari.js - sidesteps that entirely:
 * once a video is confirmed still paused after a real .play() attempt
 * (autoplay genuinely blocked - a visitor's own Safari "Never Auto-
 * Play" setting or Low Power Mode, neither of which any page-side code
 * can override), it covers the video with this plain, ordinary
 * .fl-video-poster-cover div - the video's own poster image, at a
 * higher z-index - so there's no native video surface exposed for
 * WebKit to draw *any* icon onto, regardless of what it's internally
 * called or which build defines what. Undoes itself automatically if
 * the video does start playing later. */
.fl-video-poster-cover {
	position: absolute;
	inset: 0;
	background-size: cover;
	background-position: center;
	opacity: 0;
	transition: opacity 0.3s ease;
	z-index: 1;
}


/* ---------------------------------------------------------------
 * "Proof" section - shared layout + side nav for the Case Studies,
 * Testimonials and FAQ archives (template-parts/proof-nav.php).
 * --------------------------------------------------------------- */

/* NOTE: this theme sets html { font-size: 62.5% }, so 1rem = 10px. */

.fl-proof-layout {
	display: grid;
	grid-template-columns: 240px minmax(0, 1fr);
	gap: 6rem;
	align-items: start;
	margin: 0;
}

/* .grid-l-container (this layout's parent, on the case-study/testimonial/
 * FAQ archives) has no side padding of its own below 768px - every other
 * section in the theme compensates with a .mxd-grid-item child
 * (padding: 0 3rem); this layout never got one, so the sidebar nav and
 * the card grid both sat flush against the screen edge on mobile
 * ("some cards and sections in mobile seem to edge to edge without any
 * good padding clearance", requested directly). Fixed here once for all
 * three archives that share this layout, rather than three separate
 * template edits. */
@media only screen and (max-width: 767px) {
	.fl-proof-layout {
		padding: 0 3rem;
	}
}

.fl-proof-content { min-width: 0; }
.fl-proof-content > .row { margin-left: 0; margin-right: 0; }

@media (min-width: 992px) {
	.fl-proof-nav { position: sticky; top: 11rem; }
}

.fl-proof-nav__label {
	margin: 0 0 1.6rem;
	font-size: 1.15rem;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--t-muted, #7d7f89);
}

.fl-proof-nav__list {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
}

.fl-proof-nav__list li { margin: 0; }

.fl-proof-nav__link {
	display: block;
	padding: 1.1rem 0;
	font-size: 1.8rem;
	line-height: 1.3;
	font-weight: 500;
	color: var(--t-medium, #575960);
	border-left: 2px solid transparent;
	transition: color 0.18s ease, border-color 0.18s ease, padding-left 0.18s ease;
}

.fl-proof-nav__link:hover,
.fl-proof-nav__link:focus-visible {
	color: var(--t-bright, #121212);
}

.fl-proof-nav__link.is-active {
	color: var(--accent, #0e686c);
	border-left-color: var(--accent, #0e686c);
	padding-left: 1.4rem;
	font-weight: 600;
}

@media (max-width: 991px) {
	.fl-proof-layout {
		grid-template-columns: 1fr;
		gap: 3rem;
	}
	.fl-proof-nav { position: static; }
	.fl-proof-nav__label { margin-bottom: 0.8rem; }
	.fl-proof-nav__list {
		flex-direction: row;
		flex-wrap: wrap;
		gap: 0 0.8rem;
		border-bottom: 1px solid var(--t-muted-extra, rgba(128, 128, 128, 0.3));
	}
	.fl-proof-nav__link {
		padding: 1.3rem 1.6rem;
		border-left: none;
		border-bottom: 2px solid transparent;
	}
	.fl-proof-nav__link.is-active {
		padding-left: 1.6rem;
		border-left: none;
		border-bottom-color: var(--accent, #0e686c);
	}
}

/* FAQ archive - a labelled group of accordions per category. */
.fl-faq-group + .fl-faq-group {
	margin-top: 5.5rem;
}

/* Testimonials archive - two-up cards inside the content column. */
.fl-proof-content .fl-testimonial-col {
	margin-bottom: 2.4rem;
}

/* ---------------------------------------------------------------
 * 404 - page not found (404.php). AI-robot Lottie + an animated
 * magnifying glass "scanning" it. Theme root is font-size:62.5%
 * (1rem = 10px).
 * --------------------------------------------------------------- */

.fl-404 { padding-top: 4rem; }

.fl-404__inner {
	max-width: 62rem;
	margin: 0 auto;
	text-align: center;
	display: flex;
	flex-direction: column;
	align-items: center;
}

.fl-404__visual {
	position: relative;
	width: 100%;
	max-width: 26rem;
	/* Reserve the robot's own portrait footprint (682x902) so the layout
	 * never jumps or collapses while the Lottie loads. */
	aspect-ratio: 682 / 902;
	margin-bottom: 0.5rem;
}

.fl-404__lottie {
	width: 100%;
	height: 100%;
}
.fl-404__lottie svg { display: block; width: 100%; height: 100%; }

/* Magnifying glass sweeping over the robot's "face". */
.fl-404__scanner {
	position: absolute;
	right: 6%;
	top: 14%;
	width: 8rem;
	height: 8rem;
	color: var(--accent, #0e686c);
	animation: fl-404-sweep 5s ease-in-out infinite;
}

.fl-404__scanner svg {
	width: 100%;
	height: 100%;
	filter: drop-shadow(0 0.4rem 1.2rem rgba(0, 0, 0, 0.25));
}

.fl-404__scanner::before {
	content: "";
	position: absolute;
	left: 8%;
	top: 8%;
	width: 58%;
	height: 58%;
	border-radius: 50%;
	background: currentColor;
	opacity: 0.16;
	animation: fl-404-pulse 2s ease-out infinite;
}

@keyframes fl-404-sweep {
	0%   { transform: translate(-1.6rem, -0.6rem) rotate(-10deg); }
	25%  { transform: translate(1.1rem, -1.4rem) rotate(7deg); }
	50%  { transform: translate(1.7rem, 1rem) rotate(12deg); }
	75%  { transform: translate(-0.7rem, 1.5rem) rotate(-5deg); }
	100% { transform: translate(-1.6rem, -0.6rem) rotate(-10deg); }
}

@keyframes fl-404-pulse {
	0%   { transform: scale(0.6); opacity: 0.28; }
	70%  { transform: scale(1.5); opacity: 0; }
	100% { transform: scale(1.5); opacity: 0; }
}

@media (prefers-reduced-motion: reduce) {
	.fl-404__scanner { animation: none; transform: rotate(6deg); }
	.fl-404__scanner::before { animation: none; }
}

.fl-404__code {
	margin: 0;
	font: normal 700 1.4rem/1 var(--_font-accent, monospace);
	letter-spacing: 0.5rem;
	text-transform: uppercase;
	color: var(--accent, #0e686c);
}

.fl-404__title {
	margin: 1rem 0 0;
	font-size: 3.4rem;
	line-height: 1.15;
	letter-spacing: -0.06rem;
	color: var(--t-bright, #121212);
}

@media (min-width: 768px) {
	.fl-404__title { font-size: 4.4rem; }
}

.fl-404__text {
	margin: 1.4rem 0 0;
	max-width: 46ch;
	font-size: 1.7rem;
	line-height: 1.6;
	color: var(--t-medium, #575960);
}

.fl-404__search {
	display: flex;
	width: 100%;
	max-width: 42rem;
	margin: 3rem 0 0;
	border: 1px solid var(--t-muted-extra, rgba(128, 128, 128, 0.3));
	border-radius: 100px;
	overflow: hidden;
	background: var(--base-bright, #fff);
}

.fl-404__search input[type="search"] {
	flex: 1;
	min-width: 0;
	border: 0;
	background: transparent;
	padding: 1.3rem 2rem;
	font-size: 1.6rem;
	color: var(--t-bright, #121212);
}
.fl-404__search input[type="search"]:focus { outline: none; }

.fl-404__search button {
	border: 0;
	cursor: pointer;
	background: var(--accent, #0e686c);
	color: #fff;
	padding: 0 2.4rem;
	font: normal 600 1.3rem/1 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.05rem;
	transition: filter 0.15s ease;
}
.fl-404__search button:hover { filter: brightness(1.1); }

.fl-404__links {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 1.6rem;
	margin-top: 3rem;
}

.fl-404__link-plain {
	font-size: 1.5rem;
	color: var(--t-medium, #575960);
	text-decoration: underline;
	text-underline-offset: 0.3rem;
}
.fl-404__link-plain:hover { color: var(--t-bright, #121212); }

/* ---------------------------------------------------------------
 * Legal / company pages (template-legal.php) - long-form documents
 * inside .fl-prose, plus a "last updated" line. Uses the shared
 * .fl-proof-* side-nav layout.
 * --------------------------------------------------------------- */

.fl-prose--doc h2 {
	margin: 4rem 0 1.4rem;
	font-size: 2.4rem;
	line-height: 1.25;
	font-weight: 700;
	color: var(--t-bright, #121212);
}
.fl-prose--doc > h2:first-child { margin-top: 0; }

.fl-prose--doc h3 {
	margin: 2.8rem 0 1rem;
	font-size: 1.9rem;
	line-height: 1.3;
	font-weight: 700;
	color: var(--t-bright, #121212);
}

.fl-prose--doc h2 + h3 { margin-top: 1.4rem; }

.fl-prose--doc a {
	color: var(--accent, #0e686c);
	text-decoration: underline;
	text-underline-offset: 0.2rem;
}

.fl-doc-updated {
	margin: 4rem 0 0;
	padding-top: 2rem;
	border-top: 1px solid var(--t-muted-extra, rgba(128, 128, 128, 0.3));
	font-size: 1.4rem;
	color: var(--t-muted, #7d7f89);
}

/* ---------------------------------------------------------------------
 * Portfolio archive - sticky CEO sidebar + a "blog list" of projects
 * (archive-fl_project.php, template-parts/portfolio-sidebar.php,
 * template-parts/project-row.php) - requested directly ("make the [CEO]
 * section to be a fixed left sidebar with a good design, then make the
 * projects to be like a blog list on the right that is scrollable, such
 * that each project card has its image on the left and info on the
 * right, each on a row").
 *
 * .fl-list-row (below) - image left, info right - was .fl-project-row
 * until this second pass, when it became the services list's row shape
 * too (services archive + the homepage's Featured Services section -
 * requested directly, "i prefer the list to appear like the project
 * page list in the services page, as well as the services list in the
 * homepage") and needed a name that isn't project-specific. .fl-list is
 * the plain wrapper for a row list with no sidebar (services); the
 * portfolio archive keeps its own .fl-portfolio-list (identical rules,
 * kept separate since it's a documented part of that specific sidebar
 * layout, not because the CSS actually differs).
 * ------------------------------------------------------------------- */
.fl-portfolio-layout {
	display: flex;
	flex-direction: column;
	align-items: flex-start;
	gap: 3.2rem;
}

@media only screen and (min-width: 992px) {
	.fl-portfolio-layout {
		flex-direction: row;
		gap: 4.8rem;
	}
}

/* Sidebar stacks above the list on mobile/tablet, plain and non-sticky -
 * "fixed" only makes sense once there's a tall list beside it to scroll
 * past; below 992px the list is short enough (and the sidebar tall
 * enough) that a sticky sidebar would mostly just sit there anyway,
 * while opting out avoids it ever overlapping the footer on a short
 * project list. */
.fl-portfolio-sidebar {
	width: 100%;
	flex: 0 0 auto;
}

@media only screen and (min-width: 992px) {
	.fl-portfolio-sidebar {
		width: 32rem;
		position: sticky;
		top: 4rem;
	}
}

.fl-portfolio-sidebar__card {
	padding: 3.2rem 2.8rem;
	border-radius: var(--fl-radius-lg, 16px);
	background: linear-gradient(160deg, #12888d 0%, #0e686c 60%, #0a4f52 100%);
	text-align: center;
	box-shadow: 0 20px 50px rgba(0, 0, 0, 0.18);
}

.fl-portfolio-sidebar__photo {
	width: 9.6rem;
	height: 9.6rem;
	margin: 0 auto 2.2rem;
	border-radius: 50%;
	overflow: hidden;
	border: 3px solid rgba(255, 255, 255, 0.25);
}

.fl-portfolio-sidebar__photo img {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

.fl-portfolio-sidebar__quote {
	margin: 0 0 2rem;
	color: #ffffff;
	font-size: 1.6rem;
	line-height: 1.55;
}

.fl-portfolio-sidebar__name {
	margin: 0;
	color: #ffffff;
	font: normal 700 1.3rem/1.4 var(--_font-accent, inherit);
	text-transform: uppercase;
	letter-spacing: 0.04rem;
}

.fl-portfolio-sidebar__title {
	margin: 0.3rem 0 0;
	color: rgba(255, 255, 255, 0.7);
	font-size: 1.3rem;
}

.fl-portfolio-list,
.fl-list {
	flex: 1 1 auto;
	min-width: 0;
	width: 100%;
}

/* Live Demos divider - continues straight on inside .fl-portfolio-list
 * itself now (archive-fl_project.php), not a separate full-width
 * section - reported directly ("it should not continue under a full
 * width section. it should look like a continuation of the project
 * list but the demarcator is only the Live demos title"). Reduced from
 * the vendor's own hero-scale h2 (also reported directly, "the font
 * size should be reduced") to a size closer to - just a step above -
 * the row titles it's introducing (.fl-list-row__title, 1.9/2.4rem),
 * so it reads as a heading inside the list rather than a new page
 * section. */
.fl-portfolio-list__divider {
	margin: 3.2rem 0 0.4rem;
	font-size: 2.2rem;
	font-weight: 700;
	line-height: 1.2;
	letter-spacing: -0.02rem;
	color: var(--fl-fg, #12162a);
}

@media only screen and (min-width: 768px) {
	.fl-portfolio-list__divider {
		font-size: 2.6rem;
	}
}

/* The Client Projects heading (archive-fl_project.php) reuses this
 * exact divider style, but it's the very first thing in the list -
 * the 3.2rem top margin above makes sense breaking two row groups
 * apart, not here, where the section's own padding already provides
 * that space. */
.fl-portfolio-list__divider--first {
	margin-top: 0;
}

.fl-list-row {
	display: flex;
	align-items: center;
	gap: 2rem;
	padding: 2.4rem 0;
	border-bottom: 1px solid var(--fl-border);
	text-decoration: none;
	transition: opacity var(--_animspeed-medium, 0.3s);
}

.fl-list-row:first-child {
	border-top: 1px solid var(--fl-border);
}

.fl-list-row:hover,
.fl-list-row:focus-visible {
	opacity: 0.82;
}

.fl-list-row__media {
	flex: 0 0 auto;
	width: 9rem;
	height: 9rem;
	border-radius: var(--fl-radius, 10px);
	overflow: hidden;
}

@media only screen and (min-width: 576px) {
	.fl-list-row__media {
		width: 12rem;
		height: 12rem;
	}
}

@media only screen and (min-width: 992px) {
	.fl-list-row__media {
		width: 14rem;
		height: 14rem;
	}
}

.fl-list-row__media img {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
	transition: transform var(--_animspeed-medium, 0.4s);
}

.fl-list-row:hover .fl-list-row__media img {
	transform: scale(1.06);
}

.fl-list-row__content {
	flex: 1 1 auto;
	min-width: 0;
}

.fl-list-row__title {
	margin: 0 0 0.6rem;
	color: var(--fl-fg);
	font-size: 1.9rem;
	line-height: 1.2;
}

@media only screen and (min-width: 768px) {
	.fl-list-row__title {
		font-size: 2.4rem;
	}
}

.fl-list-row__blurb {
	display: -webkit-box;
	max-width: 60ch;
	margin: 0 0 1.2rem;
	overflow: hidden;
	color: var(--fl-fg-muted);
	font-size: 1.4rem;
	line-height: 1.5;
	-webkit-line-clamp: 2;
	-webkit-box-orient: vertical;
}

.fl-list-row__tags {
	display: flex;
	flex-wrap: wrap;
	gap: 0.6rem;
}

/* The vendor .tag class (main.min.css) is genuinely just styled text -
 * no background/border/shape of its own (the same gap .fl-badge was
 * built to close elsewhere on the site) - "make the tags look more like
 * tags", requested directly. Real chip styling, scoped to this
 * component only - every other .tag sitewide (project hero) is
 * untouched. transform: none cancels .tag's own translateY nudge - a
 * baseline-alignment compensation for plain text that isn't needed once
 * it's a padded chip. */
.fl-list-row__tags .tag {
	display: inline-flex;
	align-items: center;
	padding: 0.4rem 1.1rem;
	border-radius: 100px;
	border: 1px solid var(--fl-border);
	background: var(--fl-accent-soft, color-mix(in srgb, var(--fl-accent) 12%, transparent));
	color: var(--fl-accent);
	transform: none;
}

.fl-list-row__arrow {
	display: none;
	flex: 0 0 auto;
	align-items: center;
	justify-content: center;
	width: 4rem;
	height: 4rem;
	border: 1px solid var(--fl-border);
	border-radius: 50%;
	color: var(--fl-fg);
	font-size: 1.6rem;
	transition: background-color var(--_animspeed-medium, 0.3s), border-color var(--_animspeed-medium, 0.3s), color var(--_animspeed-medium, 0.3s), transform var(--_animspeed-medium, 0.3s);
}

@media only screen and (min-width: 768px) {
	.fl-list-row__arrow {
		display: flex;
	}
}

.fl-list-row:hover .fl-list-row__arrow {
	background: var(--fl-accent);
	border-color: var(--fl-accent);
	color: #ffffff;
	transform: rotate(45deg);
}

/* Two-per-row grid modifier (services archive + the homepage's Featured
 * Services section) - requested directly ("the list cards have to be
 * two in a row and if a row must contain only the last or one card, it
 * has to be full width"). Each .fl-list-row becomes a bordered card
 * (the plain list's shared top/bottom divider lines don't make sense
 * once items sit side by side) rather than changing its own internal
 * image-left/text-right shape, which already reads fine at half width.
 *
 * The odd-one-out rule is pure CSS, no PHP item count needed: the last
 * child is only ever at an *odd* position (1st, 3rd, 5th...) when the
 * total count is odd - exactly when it would otherwise be alone in its
 * row - so :last-child:nth-child(odd) alone identifies it. */
.fl-list--grid {
	display: grid;
	grid-template-columns: 1fr;
	gap: 2rem;
}

@media only screen and (min-width: 768px) {
	.fl-list--grid {
		grid-template-columns: repeat(2, 1fr);
		column-gap: 2.8rem;
	}
}

.fl-list--grid .fl-list-row,
.fl-list--grid .fl-list-row:first-child {
	align-items: flex-start;
	margin: 0;
	padding: 2rem;
	border: 1px solid var(--fl-border);
	border-radius: var(--fl-radius-lg, 16px);
}

.fl-list--grid .fl-list-row:last-child:nth-child(odd) {
	grid-column: 1 / -1;
}

/**
 * Compact entry-point widget (template-parts/domain-checker.php,
 * assets/js/domain-checker.js) - deliberately just an input + button +
 * one secondary link now (the full check/result/enquiry experience
 * moved to the Project Builder funnel page below). Own scoped classes,
 * same reasoning as .fl-featured-product* above.
 */
.fl-domain-entry {
	max-width: 560px;
	margin: 0 auto;
	text-align: center;
}

.fl-domain-entry__search {
	display: flex;
	gap: 0.75rem;
	flex-wrap: wrap;
	justify-content: center;
}

.fl-domain-entry__input {
	flex: 1 1 260px;
	padding: 1.1rem 1.4rem;
	border: 1px solid var(--fl-border, #e2e2e2);
	border-radius: 999px;
	font-size: 1.6rem;
}

.fl-domain-entry__btn {
	white-space: nowrap;
}

.fl-domain-entry__alt {
	display: inline-block;
	margin-top: 1.2rem;
	font-size: 1.4rem;
	color: var(--fl-muted, #777);
	text-decoration: none;
}

.fl-domain-entry__alt:hover {
	color: var(--fl-accent, #0e686c);
}

/**
 * Homepage "Tell us what you're building" CTA (template-parts/homepage/
 * domain_checker.php) - full-bleed accent banner, same gradient/padding
 * pattern as .fl-featured-product-section below so the two CTA moments
 * on this homepage read as one design language. .fl-domain-entry* rules
 * above stay the shared widget's own light-background default (used
 * elsewhere via [fl_domain_checker]); everything under .fl-domain-cta
 * here overrides it for light-on-dark only in this one placement.
 */
.fl-domain-cta-section {
	background: linear-gradient(135deg, #12888d 0%, #0e686c 55%, #0a4f52 100%);
	padding-top: 6rem;
	padding-bottom: 6rem;
}

.fl-domain-cta {
	max-width: 720px;
	margin: 0 auto;
	text-align: center;
	color: #fff;
}

.fl-domain-cta__icon {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 56px;
	height: 56px;
	border-radius: 50%;
	background: rgba(255, 255, 255, 0.14);
	margin-bottom: 1.6rem;
}

.fl-domain-cta__icon svg {
	width: 28px;
	height: 28px;
}

.fl-domain-cta__title {
	color: #fff;
	font-size: clamp(2.8rem, 4vw, 4.2rem);
	margin-bottom: 1.2rem;
}

.fl-domain-cta__sub {
	color: rgba(255, 255, 255, 0.82);
	font-size: 1.7rem;
	max-width: 520px;
	margin: 0 auto 3.2rem;
}

.fl-domain-cta__widget {
	margin-bottom: 2rem;
}

.fl-domain-cta .fl-domain-entry__input {
	background: rgba(255, 255, 255, 0.96);
	border: none;
	font-size: 1.7rem;
	padding: 1.3rem 1.8rem;
}

.fl-domain-cta .fl-domain-entry__btn {
	background: #fff;
	color: var(--fl-accent, #0e686c);
	border: none;
	font-weight: 700;
	padding: 0 2.2rem;
}

.fl-domain-cta .fl-domain-entry__btn:hover {
	background: rgba(255, 255, 255, 0.9);
}

.fl-domain-cta .fl-domain-entry__alt {
	color: rgba(255, 255, 255, 0.82);
}

.fl-domain-cta .fl-domain-entry__alt:hover {
	color: #fff;
}

.fl-domain-cta__trust {
	display: flex;
	justify-content: center;
	flex-wrap: wrap;
	gap: 0.6rem 2rem;
	list-style: none;
	margin: 0;
	padding: 0;
	font-size: 1.3rem;
	color: rgba(255, 255, 255, 0.75);
}

.fl-domain-cta__trust li {
	position: relative;
	padding-left: 1.6rem;
}

.fl-domain-cta__trust li::before {
	content: '';
	position: absolute;
	left: 0;
	top: 0.5em;
	width: 8px;
	height: 8px;
	border-radius: 50%;
	background: rgba(255, 255, 255, 0.6);
}

@media (max-width: 600px) {
	.fl-domain-cta-section {
		padding-top: 4rem;
		padding-bottom: 4rem;
	}
}

/* Azurio's own .mxd-container.grid-l-container (this section's wrapper,
 * domain-cta-banner.php) zeroes its horizontal padding below 768px by
 * design - meant for edge-to-edge grid/carousel layouts elsewhere on
 * the site (the portfolio list, case-study grids) that want full-bleed
 * content on mobile. This section is a centered max-width:720px text +
 * form block, not a grid, so inheriting that zero padding instead left
 * its text and the domain-checker field flush against the viewport
 * edges on mobile (reported directly). Restoring plain .mxd-container's
 * own 3rem gutter here, scoped to this one section, rather than
 * touching grid-l-container's shared mobile default other layouts
 * still want. */
@media (max-width: 767px) {
	.fl-domain-cta-section .mxd-container {
		padding: 0 2rem;
	}
}

/**
 * Project Builder funnel (template-project-builder.php,
 * assets/js/project-builder.js). Redesigned toward a modern registrar/
 * SaaS-wizard look (Hostinger/Namecheap-style: numbered connected
 * stepper, icon-led choice cards with a confirming checkmark state,
 * chip-styled domain results, a proper priced summary card) - the
 * earlier plain-button version read as unfinished. Still Fisher Labs'
 * own accent/tokens throughout, not a copy of either brand's palette.
 * Progressive disclosure over a two-column layout (main step content +
 * a persistent summary panel) on desktop, collapsing to a single column
 * with a sticky compact summary bar on mobile.
 */
.fl-funnel-section {
	padding-top: 4rem;
	padding-bottom: 6rem;
}

.fl-funnel {
	max-width: 980px;
	margin: 0 auto;
}

/* ---------- Stepper ---------- */

.fl-funnel__progress {
	display: flex;
	align-items: flex-start;
	margin-bottom: 3.2rem;
	overflow-x: auto;
	padding-bottom: 0.4rem;
}

.fl-funnel__progress-item {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 0.6rem;
	flex-shrink: 0;
	min-width: 64px;
}

.fl-funnel__progress-dot {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 32px;
	height: 32px;
	border-radius: 50%;
	border: 2px solid var(--fl-border, #e4e7f0);
	color: var(--fl-muted, #777);
	font-size: 1.3rem;
	font-weight: 700;
	background: var(--fl-bg, #fff);
	transition: all 0.25s ease;
}

.fl-funnel__progress-dot svg {
	width: 15px;
	height: 15px;
}

.fl-funnel__progress-item.is-active .fl-funnel__progress-dot {
	border-color: var(--fl-accent, #0e686c);
	color: var(--fl-accent, #0e686c);
	box-shadow: 0 0 0 4px color-mix(in srgb, var(--fl-accent, #0e686c) 14%, transparent);
}

.fl-funnel__progress-item.is-done .fl-funnel__progress-dot {
	background: var(--fl-accent, #0e686c);
	border-color: var(--fl-accent, #0e686c);
	color: #fff;
}

.fl-funnel__progress-label {
	font-size: 1.15rem;
	color: var(--fl-muted, #777);
	white-space: nowrap;
	font-weight: 500;
}

.fl-funnel__progress-item.is-active .fl-funnel__progress-label {
	color: var(--fl-dark, #0b1120);
	font-weight: 700;
}

.fl-funnel__progress-connector {
	flex: 1 1 24px;
	min-width: 24px;
	height: 2px;
	background: var(--fl-border, #e4e7f0);
	margin-top: 15px;
	transition: background 0.25s ease;
}

.fl-funnel__progress-connector.is-done {
	background: var(--fl-accent, #0e686c);
}

/* ---------- Layout ---------- */

.fl-funnel__layout {
	display: grid;
	grid-template-columns: 1fr 320px;
	gap: 3.2rem;
	align-items: start;
}

/* .fl-funnel__side is the grid cell itself (template-project-builder.php)
 * - stretched to the FULL row height (align-items:start on the grid
 * above would otherwise shrink it to its own short content, leaving
 * .fl-funnel__side-sticky below almost no room to actually stick while
 * scrolling through a much taller .fl-funnel__main - confirmed live,
 * see that wrapper's own doc comment, both here and in the PHP template,
 * for the full "continue button feels hidden on scroll" investigation). */
.fl-funnel__side {
	align-self: stretch;
}

/* The sticky unit itself: summary card + its desktop Continue button,
 * moving together as one card rather than the card alone (previously
 * .fl-funnel__summary was the sticky element on its own, with the button
 * a separate sibling below it - once the card visually "stuck" partway
 * down a tall step, the button - still positioned by normal flow
 * relative to the card's un-stuck position - ended up scrolled far out
 * of reach, reported directly as "hidden underneath the sticky summary
 * card"). Owns the card's own visual chrome (radius/shadow/overflow) so
 * .fl-funnel__summary and the continue slot beneath it read as one
 * seamless box - see each of their own rules just below for how the
 * button renders as a green action built into the card's own bottom
 * edge ("a green button on the card itself", requested directly). */
.fl-funnel__side-sticky {
	position: sticky;
	top: 2rem;
	display: flex;
	flex-direction: column;
	border-radius: var(--fl-radius-lg, 16px);
	box-shadow: var(--fl-shadow, 0 1px 2px rgba(18, 22, 42, 0.04), 0 8px 24px rgba(18, 22, 42, 0.06));
	overflow: hidden;
}

/* Continue/submit button mount points - requested directly ("the
 * continue button should on desktop be underneath the your project card
 * on the right and be on the right of the back button in mobile").
 * Exactly one of the two is ever visible; assets/js/project-builder.js's
 * placeContinueButton() fills both unconditionally and lets this media
 * query decide which one shows, so it never has to branch on viewport
 * itself or re-run on resize. */
.fl-funnel__continue-slot--mobile {
	display: none;
}

@media (max-width: 980px) {
	.fl-funnel__layout {
		grid-template-columns: 1fr;
	}

	.fl-funnel__side {
		display: none;
	}

	.fl-funnel__continue-slot--mobile {
		display: block;
		flex: 1 1 auto;
	}
}

.fl-funnel__step {
	opacity: 0;
	transform: translateY(10px);
}

.fl-funnel__step.is-entering {
	animation: fl-funnel-step-in 0.38s ease forwards;
}

@keyframes fl-funnel-step-in {
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

.fl-funnel__step-eyebrow {
	display: block;
	font-size: 1.2rem;
	font-weight: 700;
	letter-spacing: 0.06em;
	text-transform: uppercase;
	color: var(--fl-accent, #0e686c);
	margin-bottom: 0.6rem;
}

.fl-funnel__step-title {
	margin-top: 0;
	margin-bottom: 0.6rem;
	font-size: 2.6rem;
}

.fl-funnel__step-sub {
	color: var(--fl-muted, #777);
	margin-bottom: 2.4rem;
	font-size: 1.5rem;
}

/* ---------- Choice cards ---------- */

.fl-funnel__options-grid,
.fl-funnel__cards-grid {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(230px, 1fr));
	gap: 1.2rem;
	margin-bottom: 1.6rem;
}

.fl-funnel__options-grid--compact,
.fl-funnel__cards-grid--compact {
	grid-template-columns: repeat(auto-fill, minmax(180px, 1fr));
}

/* A recommended/"often paired" service card that expands in place to
   show its own options once toggled on (e.g. Web Translation has real
   configurable options of its own, not just a flat base price). Spans
   the full grid row rather than sitting inside one grid cell, so its
   expanded panel doesn't squeeze against a neighbouring card. */
.fl-funnel__recommended-item {
	grid-column: 1 / -1;
	display: flex;
	flex-direction: column;
	gap: 0.8rem;
}

.fl-funnel__recommended-item .fl-funnel__card {
	max-width: 320px;
}

.fl-funnel__recommended-body {
	padding: 1.4rem 1.6rem;
	border-radius: var(--fl-radius, 10px);
	background: var(--fl-bg-alt, #f5f7fb);
}

.fl-funnel__recommended-body:empty {
	display: none;
}

.fl-funnel__card {
	position: relative;
	display: flex;
	align-items: center;
	gap: 1.2rem;
	text-align: left;
	padding: 1.6rem 1.8rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius-lg, 16px);
	background: var(--fl-bg, #fff);
	cursor: pointer;
	transition: border-color 0.18s ease, box-shadow 0.18s ease, transform 0.18s ease;
}

.fl-funnel__card:hover {
	border-color: var(--fl-accent, #0e686c);
	box-shadow: 0 8px 24px rgba(11, 17, 32, 0.06);
	transform: translateY(-2px);
}

.fl-funnel__card.is-selected {
	border-color: var(--fl-accent, #0e686c);
	background: color-mix(in srgb, var(--fl-accent, #0e686c) 5%, transparent);
	box-shadow: 0 0 0 3px color-mix(in srgb, var(--fl-accent, #0e686c) 12%, transparent);
}

.fl-funnel__card.is-confirming {
	transform: scale(0.98);
}

.fl-funnel__card--compact {
	padding: 1.2rem 1.4rem;
	gap: 0.8rem;
}

.fl-funnel__card-icon {
	flex-shrink: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 42px;
	height: 42px;
	border-radius: 12px;
	background: color-mix(in srgb, var(--fl-accent, #0e686c) 10%, transparent);
	color: var(--fl-accent, #0e686c);
}

.fl-funnel__card-icon svg {
	width: 22px;
	height: 22px;
}

.fl-funnel__card-body {
	display: flex;
	flex-direction: column;
	gap: 0.2rem;
	min-width: 0;
}

.fl-funnel__card-title {
	font-weight: 700;
	font-size: 1.5rem;
	line-height: 1.3;
}

.fl-funnel__card-sub {
	font-size: 1.3rem;
	color: var(--fl-muted, #777);
}

.fl-funnel__card-pill {
	margin-left: auto;
	flex-shrink: 0;
	font-size: 1.05rem;
	font-weight: 600;
	padding: 0.3rem 0.8rem;
	border-radius: 999px;
	background: var(--fl-bg-alt, #f5f7fb);
	color: var(--fl-muted, #777);
}

.fl-funnel__card-check {
	position: absolute;
	top: -8px;
	right: -8px;
	width: 24px;
	height: 24px;
	border-radius: 50%;
	background: var(--fl-accent, #0e686c);
	color: #fff;
	display: flex;
	align-items: center;
	justify-content: center;
	opacity: 0;
	transform: scale(0.5);
	transition: all 0.2s ease;
	box-shadow: 0 2px 6px rgba(11, 17, 32, 0.2);
}

.fl-funnel__card-check svg {
	width: 13px;
	height: 13px;
}

.fl-funnel__card.is-selected .fl-funnel__card-check {
	opacity: 1;
	transform: scale(1);
}

.fl-funnel__skeleton {
	height: 78px;
	border-radius: var(--fl-radius-lg, 16px);
	background: linear-gradient(90deg, var(--fl-bg-alt, #f5f7fb) 25%, #eef1f7 37%, var(--fl-bg-alt, #f5f7fb) 63%);
	background-size: 400% 100%;
	animation: fl-funnel-shimmer 1.4s ease infinite;
}

@keyframes fl-funnel-shimmer {
	0% { background-position: 100% 50%; }
	100% { background-position: 0 50%; }
}

.fl-funnel__skip {
	background: none;
	border: none;
	color: var(--fl-muted, #777);
	cursor: pointer;
	font-size: 1.35rem;
	display: inline-flex;
	align-items: center;
	gap: 0.4rem;
	padding: 0.4rem 0;
}

.fl-funnel__skip:hover {
	color: var(--fl-accent, #0e686c);
}

.fl-funnel__recommend-label {
	display: flex;
	align-items: center;
	gap: 0.6rem;
	font-size: 1.3rem;
	font-weight: 700;
	color: var(--fl-accent, #0e686c);
	margin: 0.4rem 0 1rem;
}

.fl-funnel__recommend-label svg {
	width: 16px;
	height: 16px;
}

/* "What's included" - the service's own base features (Pricing_Engine's
   item.included=true rows), shown as a static checklist rather than a
   togglable checkbox: the price already counts these unconditionally,
   so a checkbox would falsely imply they can be turned off. */
.fl-funnel__included-label {
	font-size: 1.3rem;
	font-weight: 700;
	color: var(--fl-muted, #777);
	margin: 0.4rem 0 1rem;
	text-transform: uppercase;
	letter-spacing: 0.04em;
}

.fl-funnel__included-list {
	list-style: none;
	margin: 0 0 2.4rem;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 0.7rem;
}

.fl-funnel__included-list li {
	display: flex;
	align-items: center;
	gap: 0.9rem;
	font-size: 1.4rem;
}

.fl-funnel__included-list svg {
	flex-shrink: 0;
	width: 18px;
	height: 18px;
	padding: 3px;
	border-radius: 50%;
	background: color-mix(in srgb, var(--fl-accent, #0e686c) 12%, transparent);
	color: var(--fl-accent, #0e686c);
}

/* ---------- Pricing controls (add-ons/options step) ---------- */

.fl-funnel__pricing-controls {
	display: flex;
	flex-direction: column;
	gap: 0.8rem;
	margin-bottom: 1.6rem;
}

.fl-funnel__check-row {
	display: flex;
	align-items: center;
	gap: 1rem;
	padding: 1.2rem 1.4rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	cursor: pointer;
	transition: border-color 0.15s ease;
}

.fl-funnel__check-row:hover {
	border-color: var(--fl-accent, #0e686c);
}

.fl-funnel__check-row input[type='checkbox'] {
	position: absolute;
	opacity: 0;
	width: 0;
	height: 0;
}

.fl-funnel__check-visual {
	flex-shrink: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 22px;
	height: 22px;
	border-radius: 6px;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	color: #fff;
	transition: all 0.15s ease;
}

.fl-funnel__check-visual svg {
	width: 13px;
	height: 13px;
	opacity: 0;
	transition: opacity 0.15s ease;
}

.fl-funnel__check-row input:checked + .fl-funnel__check-visual {
	background: var(--fl-accent, #0e686c);
	border-color: var(--fl-accent, #0e686c);
}

.fl-funnel__check-row input:checked + .fl-funnel__check-visual svg {
	opacity: 1;
}

.fl-funnel__check-label {
	flex: 1;
	font-size: 1.4rem;
}

.fl-funnel__check-price {
	flex-shrink: 0;
	font-weight: 700;
	color: var(--fl-accent, #0e686c);
	font-size: 1.3rem;
}

.fl-funnel__slider-row {
	display: flex;
	flex-direction: column;
	gap: 0.5rem;
	padding: 1rem 0;
}

/* Configurator "select" groups (e.g. "Project type") - previously just
 * padding:1rem 0 around a completely unstyled native <select>, which is
 * what actually made it look "too slim and narrow", reported directly
 * with a screenshot. Same bordered-box treatment as .fl-funnel__check-row
 * right above, for visual consistency with the rest of this step. */
.fl-funnel__group-row {
	display: flex;
	flex-direction: column;
	gap: 0.6rem;
	padding: 1.2rem 1.4rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
}

.fl-funnel__group-label {
	font-size: 1.4rem;
	font-weight: 600;
}

/* Custom-styled select: kill the native chrome, draw our own chevron -
 * same pattern as .fl-pb-field select (assets/js/pricing-builder.js's own
 * configurator), ported here for the funnel's identical control - see
 * renderPricingFormControls()'s own doc comment in project-builder.js
 * for why checkbox/stepper groups needed the same treatment. */
.fl-funnel__select {
	appearance: none;
	-webkit-appearance: none;
	width: 100%;
	padding: 1.1rem 3.4rem 1.1rem 1.2rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	background-color: var(--fl-bg-raised, #fff);
	background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='14' height='14' viewBox='0 0 24 24' fill='none' stroke='%23888' stroke-width='2.5' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E");
	background-repeat: no-repeat;
	background-position: right 1.2rem center;
	color: var(--fl-fg);
	font-size: 1.4rem;
	font-weight: 600;
	cursor: pointer;
	transition: border-color 0.12s ease, box-shadow 0.12s ease;
}

.fl-funnel__select:hover {
	border-color: color-mix(in srgb, var(--fl-accent, #0e686c) 55%, var(--fl-border, #e2e2e2));
}

.fl-funnel__select:focus-visible {
	outline: none;
	border-color: var(--fl-accent, #0e686c);
	box-shadow: 0 0 0 3px color-mix(in srgb, var(--fl-accent, #0e686c) 22%, transparent);
}

/* Configurator "stepper" groups (e.g. "Custom Post Types") - previously
 * rendered with NO interactive control at all, just the bare label text
 * ("a non selectable list... it looks confusing", reported directly) -
 * assets/js/project-builder.js's renderPricingFormControls() never built
 * anything for group.control === 'stepper' before. Same bordered-box +
 * -/+ stepper treatment as .fl-pb-field/.fl-pb-stepper (the single-
 * service estimator's own working stepper), ported here rather than
 * reusing those classes directly since the two builders' surrounding
 * layout differs enough to want their own scoped rules. */
.fl-funnel__stepper-row {
	display: flex;
	align-items: center;
	justify-content: space-between;
	flex-wrap: wrap;
	gap: 1rem;
	padding: 1.2rem 1.4rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
}

.fl-funnel__stepper-label {
	font-size: 1.4rem;
	font-weight: 600;
}

.fl-funnel__stepper {
	display: inline-flex;
	align-items: stretch;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	overflow: hidden;
	background: var(--fl-bg-raised, #fff);
}

.fl-funnel__stepper-btn {
	width: 3.6rem;
	padding: 0.8rem 0;
	border: none;
	background: var(--fl-bg-alt, #f5f7fb);
	color: var(--fl-fg);
	font-size: 1.7rem;
	line-height: 1;
	font-weight: 700;
	cursor: pointer;
	transition: background-color 0.12s ease, color 0.12s ease;
}

.fl-funnel__stepper-btn:hover {
	background: var(--fl-accent, #0e686c);
	color: #ffffff;
}

.fl-funnel__stepper-btn:disabled {
	opacity: 0.35;
	cursor: not-allowed;
}

.fl-funnel__stepper-input {
	width: 4.6rem;
	border: none;
	border-left: 1.5px solid var(--fl-border, #e2e2e2);
	border-right: 1.5px solid var(--fl-border, #e2e2e2);
	background: transparent;
	color: var(--fl-fg);
	font-size: 1.4rem;
	font-weight: 700;
	text-align: center;
	-moz-appearance: textfield;
	appearance: textfield;
}

.fl-funnel__stepper-input::-webkit-outer-spin-button,
.fl-funnel__stepper-input::-webkit-inner-spin-button {
	-webkit-appearance: none;
	margin: 0;
}

.fl-funnel__stepper-unit {
	color: var(--fl-muted, #777);
	font-size: 1.25rem;
	font-variant-numeric: tabular-nums;
}

/* ---------- Domain step ---------- */

.fl-funnel__domain-inline {
	display: flex;
	gap: 0.8rem;
	flex-wrap: wrap;
	margin-top: 0.8rem;
}

.fl-funnel__domain-input {
	flex: 1 1 260px;
	padding: 1.1rem 1.4rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: 999px;
	font-size: 1.5rem;
}

.fl-funnel__domain-input:focus {
	outline: none;
	border-color: var(--fl-accent, #0e686c);
}

.fl-funnel__domain-disclaimer {
	margin: 1rem 0 0;
	font-size: 1.25rem;
}

.fl-funnel__domain-results {
	margin-top: 1.6rem;
	display: flex;
	flex-direction: column;
	gap: 0.8rem;
}

.fl-funnel__domain-row {
	display: flex;
	align-items: center;
	gap: 1rem;
	padding: 1.2rem 1.6rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	flex-wrap: wrap;
}

.fl-funnel__domain-row-main {
	display: flex;
	align-items: center;
	gap: 1rem;
	flex: 1 1 200px;
	min-width: 0;
}

.fl-funnel__domain-name {
	font-weight: 700;
	font-size: 1.5rem;
	overflow: hidden;
	text-overflow: ellipsis;
	white-space: nowrap;
}

.fl-funnel__domain-status {
	flex-shrink: 0;
	font-size: 1.1rem;
	font-weight: 700;
	letter-spacing: 0.02em;
	text-transform: uppercase;
	padding: 0.35rem 0.9rem;
	border-radius: 999px;
}

.fl-funnel__domain-row.is-available .fl-funnel__domain-status,
.fl-funnel__domain-row.is-premium .fl-funnel__domain-status {
	background: color-mix(in srgb, #0e9f6e 14%, transparent);
	color: #0e7a52;
}

.fl-funnel__domain-row.is-unavailable .fl-funnel__domain-status,
.fl-funnel__domain-row.is-reserved .fl-funnel__domain-status,
.fl-funnel__domain-row.is-unknown_error .fl-funnel__domain-status {
	background: var(--fl-bg-alt, #f5f7fb);
	color: var(--fl-muted, #777);
}

.fl-funnel__domain-row.is-available,
.fl-funnel__domain-row.is-premium {
	border-color: color-mix(in srgb, var(--fl-accent, #0e686c) 30%, var(--fl-border, #e2e2e2));
}

.fl-funnel__domain-row.is-unavailable,
.fl-funnel__domain-row.is-reserved,
.fl-funnel__domain-row.is-unknown_error {
	opacity: 0.65;
}

.fl-funnel__domain-price {
	font-weight: 700;
	color: var(--fl-dark, #0b1120);
	font-size: 1.4rem;
	flex-shrink: 0;
}

.fl-funnel__domain-pick {
	flex-shrink: 0;
}

/* ---------- Summary (sidebar + review step + mobile bar) ---------- */

.fl-funnel__summary-list {
	display: flex;
	flex-direction: column;
	gap: 0.2rem;
}

.fl-funnel__summary-row {
	display: flex;
	align-items: baseline;
	gap: 0.6rem;
	padding: 0.9rem 0;
	border-bottom: 1px solid var(--fl-border, #e4e7f0);
	font-size: 1.35rem;
}

.fl-funnel__summary-label {
	color: var(--fl-muted, #777);
	flex-shrink: 0;
}

.fl-funnel__summary-value {
	font-weight: 600;
	overflow: hidden;
	text-overflow: ellipsis;
	white-space: nowrap;
}

.fl-funnel__summary-change {
	margin-left: auto;
	flex-shrink: 0;
	background: none;
	border: none;
	color: var(--fl-accent, #0e686c);
	font-size: 1.2rem;
	font-weight: 600;
	cursor: pointer;
	text-decoration: underline;
}

/* Per-item remove (additional services, domain) - requested directly:
 * "there should be the possibility to either remove items... or clear
 * the total price." Only .fl-funnel__summary-change also present (Change
 * on a row with both) gets margin-left:auto - this one takes it instead
 * when Change isn't there (the additional-service rows), so it still
 * sits flush right rather than immediately after the value. */
.fl-funnel__summary-remove {
	flex-shrink: 0;
	width: 2rem;
	height: 2rem;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	margin-left: 0.4rem;
	padding: 0;
	background: none;
	border: none;
	border-radius: 50%;
	color: var(--fl-muted, #777);
	font-size: 1.8rem;
	line-height: 1;
	cursor: pointer;
}

.fl-funnel__summary-row:not(:has(.fl-funnel__summary-change)) .fl-funnel__summary-remove {
	margin-left: auto;
}

.fl-funnel__summary-remove:hover {
	background: rgba(0, 0, 0, 0.06);
	color: #c0392b;
}

/* "Clear the total price" (requested directly) - a deliberately low-key
 * text link below the price, same treatment as .fl-funnel__resume-toggle
 * above it, not a second prominent button competing with the step's own
 * primary "Continue" action. */
.fl-funnel__summary-startover {
	display: block;
	margin-top: 1rem;
	background: none;
	border: none;
	padding: 0;
	color: var(--fl-muted, #777);
	font-size: 1.25rem;
	text-decoration: underline;
	cursor: pointer;
}

.fl-funnel__summary-startover:hover {
	color: #c0392b;
}

/* Themed "start over" confirmation (project-builder.js's showConfirmModal())
 * - replaces a bare window.confirm(), which can't be styled at all and
 * looks like a browser chrome error rather than part of the site
 * (reported directly). Generic enough for any future destructive-action
 * confirm in the funnel, not just this one. Light-card treatment (not
 * the dark full-bleed .fl-lightbox used for the portfolio image viewer,
 * a deliberately different, immersive context) - the funnel lives on
 * light internal pages, so this matches .fl-card's own design language. */
.fl-modal {
	position: fixed;
	inset: 0;
	z-index: 9500;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 2rem;
}

.fl-modal[hidden] {
	display: none;
}

.fl-modal__backdrop {
	position: absolute;
	inset: 0;
	background: rgba(15, 15, 15, 0.55);
}

.fl-modal__dialog {
	position: relative;
	z-index: 1;
	width: 100%;
	max-width: 44rem;
	background: var(--fl-bg-raised, #fff);
	border: 1px solid var(--fl-border, #e4e7f0);
	border-radius: var(--fl-radius-lg, 16px);
	box-shadow: var(--fl-shadow-lg, 0 20px 60px rgba(18, 22, 42, 0.14));
	padding: 3.2rem;
	animation: fl-modal-in 0.18s ease;
}

@keyframes fl-modal-in {
	from { opacity: 0; transform: translateY(8px) scale(0.98); }
	to { opacity: 1; transform: translateY(0) scale(1); }
}

.fl-modal__title {
	margin: 0 0 0.8rem;
	font-size: 2rem;
	font-weight: 700;
	color: var(--fl-fg);
}

.fl-modal__desc {
	margin: 0 0 2.4rem;
	color: var(--fl-fg-muted, #5b6178);
	font-size: 1.5rem;
	line-height: 1.5;
}

.fl-modal__actions {
	display: flex;
	justify-content: flex-end;
	gap: 1.2rem;
}

@media (max-width: 480px) {
	.fl-modal__actions {
		flex-direction: column-reverse;
	}
	.fl-modal__actions .fl-button {
		width: 100%;
	}
}

/* Body-scroll lock while a themed modal is open - same convention
 * .fl-lightbox already uses (toggled on <html>, not <body>). */
html.fl-modal-open {
	overflow: hidden;
}

.fl-funnel__summary-price-row {
	display: flex;
	align-items: center;
	justify-content: space-between;
	padding-top: 1.4rem;
	margin-top: 0.4rem;
}

.fl-funnel__summary-price {
	font-size: 2rem;
	font-weight: 800;
	color: var(--fl-accent, #0e686c);
}

/* Card chrome itself (radius/shadow/sticky) now lives on the shared
 * .fl-funnel__side-sticky wrapper (further up this file) - this is just
 * the padded content area, border-bottom-less so the continue slot
 * right after it (same rule block, next) reads as part of the same card
 * with no seam between them. */
.fl-funnel__summary {
	padding: 2rem;
	background: var(--fl-bg-alt, #f5f7fb);
	border: 1px solid var(--fl-border, #e4e7f0);
	border-bottom: none;
}

/* The desktop Continue button's own dock - same card background/border
 * as .fl-funnel__summary directly above it (no visual seam, no
 * padding-top of its own since the summary's last row already carries
 * enough bottom spacing), rounded off by .fl-funnel__side-sticky's own
 * overflow:hidden. Empty (no button placed yet) collapses to nothing
 * rather than showing a bare empty card footer. */
.fl-funnel__continue-slot--desktop:empty {
	display: none;
}

.fl-funnel__continue-slot--desktop {
	padding: 0 2rem 2rem;
	background: var(--fl-bg-alt, #f5f7fb);
	border: 1px solid var(--fl-border, #e4e7f0);
	border-top: none;
}

/* The green "go" action - deliberately a different colour from the
 * site's own teal accent (--fl-accent), which this card's price already
 * uses right above it - a distinct "continue" cue, requested directly
 * ("the button should be a green button on the card itself"). Scoped to
 * this one dock rather than a new global --fl-* token, since nothing
 * else on the site uses this colour. */
.fl-funnel__continue-slot--desktop .fl-button {
	width: 100%;
	background: #1a9c5e;
	border-color: #1a9c5e;
	color: #ffffff;
}

.fl-funnel__continue-slot--desktop .fl-button:hover {
	background: #16874f;
	border-color: #16874f;
	color: #ffffff;
}

.fl-funnel__summary h3 {
	margin-top: 0;
	font-size: 1.5rem;
}

.fl-funnel__summary-empty {
	color: var(--fl-muted, #777);
	font-size: 1.3rem;
}

/* "Save your progress" - collapsed to a single low-key link by default,
   never competing visually with the step's own primary action. */
.fl-funnel__resume {
	margin-top: 1.6rem;
	padding-top: 1.6rem;
	border-top: 1px solid var(--fl-border, #e4e7f0);
}

.fl-funnel__resume-toggle {
	background: none;
	border: none;
	padding: 0;
	color: var(--fl-muted, #777);
	font-size: 1.25rem;
	text-decoration: underline;
	cursor: pointer;
}

.fl-funnel__resume-toggle:hover {
	color: var(--fl-accent, #0e686c);
}

.fl-funnel__resume-form input {
	width: 100%;
	padding: 0.8rem 1rem;
	margin-bottom: 0.6rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	font-size: 1.3rem;
}

.fl-funnel__resume-note {
	margin: 0.6rem 0 0;
	font-size: 1.15rem;
	color: var(--fl-muted, #777);
}

.fl-funnel__resume-sent {
	color: var(--fl-accent, #0e686c);
	font-weight: 600;
}

.fl-funnel__mobile-bar {
	position: sticky;
	bottom: 0;
	display: none;
	justify-content: space-between;
	align-items: center;
	padding: 1.2rem 2rem;
	border-radius: var(--fl-radius-lg, 16px) var(--fl-radius-lg, 16px) 0 0;
	background: var(--fl-bg, #fff);
	box-shadow: 0 -8px 24px rgba(11, 17, 32, 0.1);
	margin-top: 2rem;
	font-size: 1.5rem;
}

.fl-funnel__mobile-bar strong {
	color: var(--fl-accent, #0e686c);
	font-size: 1.8rem;
}

.fl-funnel__mobile-bar span {
	color: var(--fl-muted, #777);
	font-size: 1.2rem;
}

@media (max-width: 980px) {
	.fl-funnel__mobile-bar:not([hidden]) {
		display: flex;
	}
}

/* ---------- Customer step / nav / thank-you ---------- */

.fl-funnel__customer-form {
	display: grid;
	gap: 1.4rem;
	max-width: 480px;
	margin-bottom: 2rem;
}

.fl-funnel__field label {
	display: block;
	margin-bottom: 0.5rem;
	font-size: 1.3rem;
	font-weight: 600;
}

.fl-funnel__field input,
.fl-funnel__field textarea {
	width: 100%;
	padding: 1.1rem 1.4rem;
	border: 1.5px solid var(--fl-border, #e2e2e2);
	border-radius: var(--fl-radius, 10px);
	font-size: 1.4rem;
}

.fl-funnel__field input:focus,
.fl-funnel__field textarea:focus {
	outline: none;
	border-color: var(--fl-accent, #0e686c);
}

/* Row, not a stack - the mobile "Continue" slot (template-project-
 * builder.php) sits after Back in DOM order, so a plain flex row already
 * puts it on Back's right with zero reordering tricks needed. On desktop
 * the mobile slot is display:none (style.css, .fl-funnel__continue-slot
 * rules further up), so this just shows Back alone as before. */
.fl-funnel__nav {
	display: flex;
	align-items: center;
	gap: 1.2rem;
	margin-top: 2rem;
}

.fl-funnel__nav .fl-funnel__back {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
}

/* [hidden] needs its own rule here, not just the browser's default UA
 * one - the plain .fl-funnel__nav .fl-funnel__back{display:inline-flex}
 * rule above outranks that UA rule on specificity (2 classes beats the
 * UA stylesheet's bare [hidden] selector), so it was winning even when
 * assets/js/project-builder.js set backBtn.hidden = true on step 1 - the
 * button rendered anyway. Reported directly ("the back button is not
 * supposed to be visible on step 1, no?"). */
.fl-funnel__nav .fl-funnel__back[hidden] {
	display: none;
}

.fl-funnel__back svg {
	width: 14px;
	height: 14px;
}

.fl-funnel__continue {
	margin-top: 0.4rem;
}

.fl-funnel__thankyou-icon {
	width: 64px;
	height: 64px;
	border-radius: 50%;
	background: var(--fl-accent, #0e686c);
	color: #fff;
	display: flex;
	align-items: center;
	justify-content: center;
	margin-bottom: 1.6rem;
}

.fl-funnel__thankyou-icon svg {
	width: 30px;
	height: 30px;
}