/*
 * Custom Silicon Solutions 2026 — main stylesheet
 *
 * Tokens live on :root. Never hardcode a hex value in a template (BUILD-SPEC §3).
 *
 * PRECEDENCE: BUILD-SPEC.md governs code conventions. The design handoff governs
 * everything visual. Where they conflict on look, the handoff wins — so the palette
 * here is the navy/cyan brand pulled from the live site's compiled CSS, not
 * BUILD-SPEC §3's blue/copper draft, and the theme self-hosts Proxima Nova and
 * Roboto rather than using BUILD-SPEC §11's system stack. Self-hosting still
 * satisfies the actual rule behind §11 and §1.1: no third-party origins.
 *
 * CLASS INVENTORY EXTENSIONS to BUILD-SPEC §12. The closed inventory has no classes
 * for the components the expertise pages need. Added here, and only here:
 *   .site-nav__submenu .site-nav__submenu-link .site-nav__toggle
 *   .site-nav--mobile .site-nav__list--mobile
 *   .page-hero__breadcrumb .page-hero__actions .page-hero--media
 *   .subnav .subnav__list .subnav__item .subnav__link .subnav__link--current
 *   .card-grid .card-media .card-media__thumb .card-media__body .card-media__title
 *   .checklist .checklist__item
 *   .split .split--even .split__body .split__media .split__figure
 *   .home-hero .home-hero__media .home-hero__scrim .home-hero__inner
 *   .home-hero__content .home-hero__title .home-hero__lede .home-hero__actions
 *   .related .related__inner .related__label .related__list .related__link
 *   .related__arrow
 *   .ip-blocks .ip-blocks__title .ip-blocks__list .ip-blocks__group
 *   .ip-blocks__summary .ip-blocks__mark .ip-blocks__items
 *   .testimonial .testimonial__figure .testimonial__quote .testimonial__mark
 *   .testimonial__caption .testimonial__name .testimonial__role
 *   .tabs .js-tabs .tabs--numbered .tabs__list .tabs__tab .tabs__num
 *   .tabs__panel .tabs__title .is-tabbed .tk-figure--side .split__figure--contain
 * ---------------------------------------------------------------------------- */

/* ---------------------------------------------------------------- 1. Fonts   */

@font-face {
	font-family: 'ProximaNova-Bold';
	src: url('../fonts/Proxima-Nova-Bold.woff2') format('woff2'),
	     url('../fonts/FontsFree-Net-Proxima-Nova-Bold.otf') format('opentype');
	font-weight: 700;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: 'Roboto';
	src: url('../fonts/Roboto-latin.woff2') format('woff2');
	font-weight: 400 700;
	font-style: normal;
	font-display: swap;
	unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
	               U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193,
	               U+2212, U+2215, U+FEFF, U+FFFD;
}

/* ---------------------------------------------------------------- 2. Tokens  */

:root {
	/* Palette — design handoff README, pulled from the live site's globals. */
	--c-navy: #0e1133;
	--c-navy-deep: #0a0d24;
	--c-cyan: #70ccdb;
	--c-cyan-hover: #4fb9cb;
	--c-cyan-active: #3c9fb0;
	--c-indigo: #4a56a6;
	--c-ink: #282828;
	--c-graphite: #3f434c;
	--c-slate: #4b4f58;
	--c-mist: #f6f7f8;
	--c-band: #eef1f6;
	--c-line: #e0e0e0;
	--c-line-2: #d3d7e0;
	--c-line-3: #e3e6ec;
	--c-line-hover: #c9ced6;
	--c-white: #ffffff;

	/* On-dark alphas */
	--c-on-dark-strong: rgba(255, 255, 255, .92);
	--c-on-dark: rgba(255, 255, 255, .8);
	--c-on-dark-mute: rgba(255, 255, 255, .72);
	--c-on-dark-soft: rgba(255, 255, 255, .6);
	--c-on-dark-faint: rgba(255, 255, 255, .55);
	--c-on-dark-rule: rgba(255, 255, 255, .12);
	--c-on-dark-edge: rgba(255, 255, 255, .18);

	/* Type */
	--f-head: 'ProximaNova-Bold', Helvetica, Arial, sans-serif;
	--f-body: 'Roboto', Helvetica, Arial, sans-serif;
	--fs-h1: 50px;
	--fs-h2: 32px;
	/* Brand book: six sizes only — 50, 32, 21, 18, 17, 15. */
	--fs-h3: 21px;
	--fs-lede: 21px;
	--fs-body: 18px;
	--fs-body-sm: 17px;
	--fs-meta: 15px;


	/* Spacing */
	--sp-1: 4px;
	--sp-2: 8px;
	--sp-3: 12px;
	--sp-4: 16px;
	--sp-5: 22px;
	--sp-6: 32px;
	--sp-7: 44px;
	--sp-8: 56px;
	--sp-9: 76px;
	--sp-10: 88px;

	--container: 1280px;
	--container-narrow: 960px;
	--gutter: 32px;
	--radius: 0;
	--radius-btn: 10px;
	--shadow-card: 0 6px 20px rgba(14, 17, 51, .12);
	--shadow-menu: 0 12px 32px rgba(14, 17, 51, .22);
}

/* ---------------------------------------------------------------- 3. Base    */

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

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

body {
	margin: 0;
	background: var(--c-white);
	color: var(--c-ink);
	font-family: var(--f-body);
	font-size: var(--fs-body);
	line-height: 1.55;
	letter-spacing: .25px;
	-webkit-font-smoothing: antialiased;
	text-wrap: pretty;
}

h1, h2, h3, h4, h5, h6 {
	font-family: var(--f-head);
	font-weight: 700;
	color: var(--c-navy);
}

a { color: var(--c-indigo); }
a:hover { color: var(--c-navy); }

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

:focus-visible {
	outline: 3px solid var(--c-cyan);
	outline-offset: 2px;
}

summary::-webkit-details-marker { display: none; }

@media (prefers-reduced-motion: reduce) {
	*,
	*::before,
	*::after {
		animation-duration: .01ms !important;
		transition-duration: .01ms !important;
		scroll-behavior: auto !important;
	}
}

/* --------------------------------------------------------------- 4. Utility  */

.skip-link {
	position: absolute;
	left: -9999px;
	top: 0;
	z-index: 100;
	padding: 12px 20px;
	background: var(--c-cyan);
	color: var(--c-navy);
	font-weight: 600;
	text-decoration: none;
}

.skip-link:focus {
	left: 0;
}

.screen-reader-text {
	position: absolute !important;
	width: 1px;
	height: 1px;
	padding: 0;
	margin: -1px;
	overflow: hidden;
	clip: rect(0, 0, 0, 0);
	white-space: nowrap;
	border: 0;
}

.is-hidden { display: none !important; }

/* ---------------------------------------------------------------- 5. Layout  */

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

.container--narrow { max-width: var(--container-narrow); }

.section {
	border-top: 1px solid var(--c-line-3);
	background: var(--c-white);
}

/*
 * Core wraps every group block in a .wp-block-group__inner-container, so an
 * editor-authored .container is a grandchild of its .section, and a .card-media
 * is a grandchild of its .card-grid. Two consequences, both handled here:
 * selectors use descendant rather than child combinators, and the wrapper is
 * set to display:contents so it does not swallow grid and flex layout.
 */
.section .container { padding-top: 80px; padding-bottom: 72px; }

.section > .wp-block-group__inner-container,
.container > .wp-block-group__inner-container,
.card-grid > .wp-block-group__inner-container,
.card-media > .wp-block-group__inner-container,
.card-media__body > .wp-block-group__inner-container {
	display: contents;
}

.section--tint { background: var(--c-band); }
.section--mist { background: var(--c-mist); }

.section--dark {
	background: var(--c-navy);
	border-top: 0;
	color: var(--c-white);
}

.section--dark .section__title { color: var(--c-white); }

.section--tight .container { padding-top: 80px; padding-bottom: 40px; }

.section__title {
	margin: 0 0 26px;
	font-size: var(--fs-h2);
	line-height: 1.25;
}

.section__intro {
	margin: 0;
	max-width: 900px;
	font-size: var(--fs-body);
	line-height: 1.75;
	color: var(--c-graphite);
}

.section__body > * + * { margin-top: var(--sp-5); }

/* --------------------------------------------------------------- 6. Buttons  */

.btn {
	display: inline-block;
	padding: 14px 26px;
	min-height: 44px;
	border: 1px solid transparent;
	border-radius: var(--radius-btn);
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	line-height: 1.2;
	text-decoration: none;
	cursor: pointer;
}

.btn--primary {
	background: var(--c-cyan);
	color: var(--c-navy);
}

.btn--primary:hover,
.btn--primary:focus-visible {
	background: var(--c-cyan-hover);
	color: var(--c-navy);
}

.btn--primary:active { background: var(--c-cyan-active); }

.btn--secondary {
	background: transparent;
	border-color: var(--c-indigo);
	color: var(--c-indigo);
}

.btn--secondary:hover,
.btn--secondary:focus-visible { background: var(--c-indigo); color: var(--c-white); }

.btn--on-dark {
	background: transparent;
	border-color: rgba(255, 255, 255, .45);
	color: var(--c-white);
}

.btn--on-dark:hover,
.btn--on-dark:focus-visible {
	border-color: var(--c-cyan);
	color: var(--c-cyan);
}

/* ---------------------------------------------------------- 7. Site header   */

.site-header {
	position: sticky;
	top: 0;
	z-index: 60;
	background: var(--c-navy);
	border-bottom: 1px solid rgba(255, 255, 255, .08);
}

.site-header__inner {
	max-width: var(--container);
	margin: 0 auto;
	padding: 0 var(--gutter);
	min-height: 96px;
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 0 24px;
}

.site-brand {
	display: flex;
	align-items: center;
	flex: none;
}

/*
 * One fluid rule for every screen, rather than a desktop size plus mobile
 * overrides. Separate breakpoint rules are how a mobile fix quietly breaks
 * desktop — there is only one value here, and it scales.
 */
.site-brand__logo {
	display: block;
	height: clamp(46px, 5vw, 68px);
	width: auto;
}

.site-nav { flex: 1; display: flex; justify-content: flex-end; }

.site-nav__list {
	display: flex;
	align-items: center;
	gap: 2px;
	list-style: none;
	margin: 0;
	padding: 0;
	font-size: var(--fs-meta);
	letter-spacing: .25px;
}

.site-nav__item { position: relative; }

.site-nav__link {
	display: flex;
	align-items: center;
	gap: 6px;
	padding: 10px 14px;
	color: var(--c-white);
	text-decoration: none;
}

.site-nav__link:hover,
.site-nav__link:focus-visible { color: var(--c-cyan); }

.site-nav__link--current { color: var(--c-cyan); }

.site-nav__link .site-nav__caret {
	font-size: 10px;
	opacity: .7;
}

/* Dropdowns open on hover AND focus-within, so they work by keyboard with no JS. */
.site-nav__submenu {
	display: none;
	position: absolute;
	top: 100%;
	left: 0;
	width: 266px;
	list-style: none;
	margin: 0;
	padding: 8px 0;
	background: var(--c-white);
	box-shadow: var(--shadow-menu);
}

.site-nav__item:hover > .site-nav__submenu,
.site-nav__item:focus-within > .site-nav__submenu { display: block; }

.site-nav__item--wide > .site-nav__submenu { width: 310px; }
.site-nav__item--mid  > .site-nav__submenu { width: 280px; }
.site-nav__item--end  > .site-nav__submenu { left: auto; right: 0; width: 250px; }

.site-nav__submenu-link {
	display: block;
	padding: 11px 20px;
	color: var(--c-ink);
	text-decoration: none;
	font-size: var(--fs-meta);
}

.site-nav__submenu-link:hover,
.site-nav__submenu-link:focus-visible {
	background: var(--c-mist);
	color: var(--c-indigo);
}

.header-actions { margin-left: 10px; }

.header-actions .btn {
	/*
	 * Centred as a flex box, not by padding alone. The shorter padding here
	 * (10px against the base 14px) leaves the content box smaller than the
	 * 44px min-height the base .btn sets for tap targets, so the line box
	 * settled at the top of the box and the label sat ~6px high. Centring
	 * distributes that slack instead. Box size is unchanged, so nothing in
	 * the header moves.
	 */
	display: inline-flex;
	align-items: center;
	justify-content: center;
	padding: 10px 20px;
	font-size: var(--fs-meta);
}

.nav-toggle {
	display: none;
	align-items: center;
	justify-content: center;
	width: 48px;
	height: 48px;
	background: none;
	border: 1px solid rgba(255, 255, 255, .35);
	color: var(--c-white);
	font-size: 20px;
	cursor: pointer;
}

.nav-toggle:hover {
	border-color: var(--c-cyan);
	color: var(--c-cyan);
	background: rgba(112, 204, 219, .12);
}

.site-nav--mobile { display: none; }

.site-nav__list--mobile {
	flex-direction: column;
	list-style: none;
	margin: 0;
	padding: 8px 0 16px;
	border-top: 1px solid var(--c-on-dark-rule);
	font-size: 17px;
}

.site-nav__list--mobile .site-nav__link {
	display: block;
	padding: 14px var(--gutter);
}

.site-nav__list--mobile .header-actions {
	margin: 0;
	padding: 12px var(--gutter) 0;
}

/* Collapsible section inside the mobile panel. */
.site-nav__group-summary {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 12px;
	padding: 14px var(--gutter);
	list-style: none;
	cursor: pointer;
	color: var(--c-white);
	font-size: 17px;
}

.site-nav__group-summary::-webkit-details-marker { display: none; }
.site-nav__group-summary:hover { color: var(--c-cyan); }

.site-nav__group-mark {
	flex: none;
	color: var(--c-cyan);
	font-size: 20px;
	line-height: 1;
}

.site-nav__group[open] .site-nav__group-mark::after { content: '\2212'; }
.site-nav__group:not([open]) .site-nav__group-mark::after { content: '\002B'; }

.site-nav__group-list {
	list-style: none;
	margin: 0;
	padding: 0 0 8px;
	background: rgba(0, 0, 0, .18);
}

.site-nav__group-list .site-nav__link {
	padding: 12px var(--gutter) 12px calc(var(--gutter) + 14px);
	font-size: 16px;
	color: var(--c-on-dark);
}

.site-nav__group-list .site-nav__link:hover { color: var(--c-cyan); }

@media (max-width: 1039px) {
	.site-nav { display: none; }
	.nav-toggle { display: flex; }
	.site-nav--mobile.is-open { display: block; }
}

/* ------------------------------------------------------------ 8. Page hero   */

.page-hero {
	background-color: var(--c-navy-deep);
	background-position: center;
	background-size: cover;
	color: var(--c-white);
}

.page-hero__inner {
	max-width: var(--container);
	margin: 0 auto;
	padding: 84px var(--gutter) 76px;
}

/*
 * One interior-page hero height for every market and expertise page.
 *
 * The design files disagree (High-Voltage top-aligned and short, Ultra-Low Power
 * a fixed 430px and centered). Neither is copied. An interior hero should
 * introduce the page rather than fill the screen: at 340–420px, the sticky
 * header plus hero still leave real content visible above the fold on a
 * laptop, and the clamp scales it with the viewport instead of pinning one
 * value that looks oversized on a small screen. Phones drop the minimum and let
 * the content set the height. The homepage hero is deliberately taller — that
 * is a different job.
 */
.page-hero--tall .page-hero__inner {
	box-sizing: border-box;
	min-height: clamp(340px, 34vw, 420px);
	display: flex;
	flex-direction: column;
	justify-content: center;
	align-items: flex-start;
}

@media (max-width: 782px) {
	.page-hero--tall .page-hero__inner { min-height: 0; }
}

.page-hero__breadcrumb {
	margin: 0 0 20px;
	font-size: var(--fs-meta);
	letter-spacing: 1.4px;
	text-transform: uppercase;
	color: var(--c-on-dark-soft);
}

.page-hero__breadcrumb a {
	color: var(--c-on-dark-soft);
	text-decoration: none;
}

.page-hero__breadcrumb a:hover { color: var(--c-cyan); }

.page-hero__title {
	margin: 0 0 22px;
	max-width: 900px;
	font-size: var(--fs-h1);
	line-height: 1.1;
	color: var(--c-white);
}

.page-hero__lede {
	margin: 0;
	max-width: 900px;
	font-size: var(--fs-lede);
	line-height: 1.5;
	color: var(--c-on-dark-strong);
}

.page-hero__actions { margin-top: var(--sp-6); }

/* --------------------------------------------------------------- 9. Sub-nav  */

.subnav {
	background: var(--c-mist);
	border-bottom: 1px solid var(--c-line);
}

/*
 * The bar runs to the right edge of the window rather than stopping at the
 * content margin. That is ~160px of extra room on a laptop, which is often the
 * difference between all five tabs fitting and the bar needing to scroll. The
 * left edge still lines up with the content below, so it does not read as
 * misaligned — and the scroll fade now sits at the true screen edge, which is
 * where a swipe naturally starts.
 */
.subnav .container {
	max-width: none;
	padding-right: 0;
	padding-left: max(var(--gutter), calc((100% - var(--container)) / 2 + var(--gutter)));
}

/*
 * One row that scrolls, never a stack. Five long labels ("Precision Analog and
 * Data Converters") need about 1100px to sit side by side, so wrapping kicked
 * in almost as soon as a desktop window was narrowed and the bar became a tall
 * ragged block that pushed the page content down. Scrolling keeps the bar one
 * line high at every width, and the current tab always starts visible.
 */
.subnav__list {
	display: flex;
	flex-wrap: nowrap;
	overflow-x: auto;
	gap: 0;
	list-style: none;
	margin: 0;
	padding: 0;
	font-size: var(--fs-meta);
	scrollbar-width: none;
	-webkit-overflow-scrolling: touch;
}

.subnav__list::-webkit-scrollbar { display: none; }

.subnav__item { flex: none; }

.subnav__link {
	display: block;
	padding: 17px 18px;
	color: var(--c-slate);
	text-decoration: none;
	white-space: nowrap;
}

.subnav__link:hover,
.subnav__link:focus-visible {
	color: var(--c-navy);
	box-shadow: inset 0 -3px 0 var(--c-line-hover);
}

.subnav__link--current {
	color: var(--c-navy);
	font-weight: 700;
	box-shadow: inset 0 -3px 0 var(--c-cyan);
}

/*
 * 9b. Portfolio filter — the sub-nav used as a filter rather than a page nav.
 *
 * Same bar, same look, so the site does not grow a second navigation language.
 * The count after each label tells a visitor how much is behind it before they
 * spend a click, which matters when three of the five hold fewer than ten items.
 */

.subnav__count {
	display: inline-block;
	min-width: 1.6em;
	margin-left: 4px;
	padding: 1px 6px;
	border-radius: 10px;
	background: var(--c-mist);
	font-size: var(--fs-meta);
	font-variant-numeric: tabular-nums;
	color: var(--c-slate);
	text-align: center;
}

.subnav__link--current .subnav__count {
	background: var(--c-cyan);
	color: var(--c-navy);
}

.portfolio-filter__status {
	max-width: var(--container);
	margin: 0 auto;
	padding: 14px var(--gutter) 0;
	font-size: var(--fs-meta);
	color: var(--c-slate);
}

.portfolio-filter__status:empty { padding: 0; }

/*
 * Filtering hides cards and any market section left with nothing in it.
 * Two classes deep so these beat .card-media's own display: flex.
 */
.card-media.is-filtered-out,
.section.is-filtered-out { display: none; }

/* ------------------------------------------------------------ 10. Checklist  */

/*
 * One column, everywhere, capped at a readable measure.
 *
 * Some source designs set these lists in two columns. Two columns are wrong for
 * this content: the eye must travel down the left column then back up to the top
 * of the right, CSS columns flow down-then-across while people read
 * across-then-down, and because the items run from four words to fifteen the
 * columns end up visibly ragged. They also collapse as soon as the window
 * narrows, which reads as inconsistent spacing between pages.
 *
 * The width cap matters as much as the column count — a bullet running the full
 * 1216px is too long a line to track back from comfortably.
 */
.checklist {
	margin: 0;
	padding-left: 0;
	max-width: 820px;
	list-style: none;
	font-size: var(--fs-body-sm);
	line-height: 1.7;
	display: flex;
	flex-direction: column;
	gap: 12px;
}

.checklist li {
	position: relative;
	padding-left: 22px;
}

.checklist li::before {
	content: '';
	position: absolute;
	left: 2px;
	top: .62em;
	width: 5px;
	height: 5px;
	border-radius: 50%;
	background: var(--c-indigo);
}

/*
 * Two-column capability list with an indigo dot marker (Ultra-Low Power).
 * Uses CSS columns rather than grid so items flow top-to-bottom down the first
 * column and continue in the second, matching the design.
 */
/*
 * Kept as a no-op so pages already carrying this class keep working. Every
 * capability list now renders identically -- see .checklist above.
 */
.checklist--cols { columns: auto; }

/*
 * Text-only example list (Precision Analog). These examples are circuit
 * specifications rather than linked case studies, so they get a plain
 * three-column list — putting them in photo cards would imply a page to click
 * through to that does not exist.
 */
.spec-list {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(min(100%, 300px), 1fr));
	gap: clamp(12px, 1.5vw, 20px);
	list-style: none;
	margin: 0;
	padding: 0;
}

.spec-list > .wp-block-group__inner-container { display: contents; }

.spec-list li {
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	border-top: 3px solid var(--c-cyan);
	padding: 18px 20px;
	font-size: var(--fs-body-sm);
	line-height: 1.6;
	color: var(--c-graphite);
}

/* Cyan-ruled fact row: heading left, values right. */
.spec-row {
	border-top: 3px solid var(--c-cyan);
	padding-top: 22px;
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));
	gap: 20px 48px;
	align-items: baseline;
}

.spec-row > .wp-block-group__inner-container { display: contents; }

.spec-row h3 {
	margin: 0;
	font-size: 21px;
	line-height: 1.3;
}

.spec-row p {
	margin: 0;
	font-size: var(--fs-body-sm);
	line-height: 1.7;
}

/* ---------------------------------------------------------- 11. Media cards  */

/*
 * Fluid rather than a fixed three columns. A locked column count made each card
 * 392px wide on a large screen, where the photograph dominated and the title
 * looked lost. Letting the grid fit as many ~260px cards as the row allows gives
 * four across on a wide monitor, three on a laptop and two on a tablet, without
 * a breakpoint for each.
 */
.card-grid {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(min(100%, 224px), 1fr));
	gap: clamp(12px, 1.5vw, 20px);
	list-style: none;
	margin: 0;
	padding: 0;
}

/*
 * A card is a group, not an anchor: the cards are authored in the block editor
 * and core group blocks cannot be links without a plugin. The title carries the
 * single link, the image is decorative, and the whole card lights up on hover or
 * when the title takes focus.
 */
.card-media {
	position: relative;
	display: flex;
	flex-direction: column;
	height: 100%;
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	text-decoration: none;
}

/*
 * The title's link is stretched over the whole card, so the entire card is
 * clickable while the page still contains exactly one link per card — the
 * accessible way to do it. A second real link would make screen readers
 * announce every card twice.
 */
.card-media__title a::after {
	content: '';
	position: absolute;
	inset: 0;
	z-index: 1;
}

/*
 * "Read more" is an affordance the old site had and the handoff design dropped.
 * Generated rather than authored so it does not have to be typed into sixty
 * cards, and it cannot go stale or be edited into something misleading.
 */
.card-media__body::after {
	content: 'Read more \2192';
	margin-top: auto;
	padding-top: 4px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 600;
	color: var(--c-indigo);
}

.card-media:hover .card-media__body::after,
.card-media:focus-within .card-media__body::after { color: var(--c-cyan-active); }

.card-media:hover,
.card-media:focus-within {
	border-color: var(--c-cyan);
	box-shadow: var(--shadow-card);
}

/*
 * These are scoped under .card-media deliberately. Core ships a per-block
 * stylesheet whose `.wp-block-image img { height: auto }` has the same
 * specificity as an unscoped `.card-media__figure img` and loads after the
 * theme, so it would win on source order and the thumbnails would render at
 * their natural aspect ratio instead of the design's fixed 150px band.
 */
.card-media .card-media__figure {
	position: relative;
	margin: 0;
	line-height: 0;
}

/* The design darkens the lower half of each thumbnail. */
.card-media .card-media__figure::after {
	content: '';
	position: absolute;
	inset: 0;
	background: linear-gradient(rgba(14, 17, 51, .1), rgba(14, 17, 51, .45));
	pointer-events: none;
}

/*
 * Sized by proportion, not by a locked pixel height, so the photo always fits
 * its card at any screen width. A fixed height letterboxes the image on narrow
 * screens and crops badly on wide ones.
 */
.card-media .card-media__thumb,
.card-media .card-media__figure img {
	display: block;
	width: 100%;
	height: auto;
	aspect-ratio: 16 / 9;
	object-fit: cover;
	background: var(--c-navy-deep);
}

.card-media__body {
	display: flex;
	flex-direction: column;
	gap: 8px;
	padding: 18px 20px 22px;
}

.card-media__title {
	margin: 0;
	font-size: 19px;
	line-height: 1.25;
	color: var(--c-navy);
}

.card-media__title a {
	color: inherit;
	text-decoration: none;
}

.card-media__title a:hover { color: var(--c-indigo); }

/* Spec line under a card title (Ultra-Low Power examples carry one). */
.card-media__text {
	margin: 0;
	font-size: 16px;
	line-height: 1.5;
	color: var(--c-slate);
}

/*
 * On phones the card turns sideways: photo left, text right. Nine full-width
 * stacked cards is a very long scroll, and a full-width photo at this aspect
 * becomes a letterboxed strip. Sideways roughly halves the scroll and gives
 * long titles and the Ultra-Low Power spec line room to read.
 */
@media (max-width: 520px) {
	.card-grid {
		grid-template-columns: 1fr;
		gap: 10px;
	}

	/*
	 * The minimum matters: High-Voltage's cards carry only a title, so without
	 * it the row collapses to ~47px — cramped, and below a comfortable tap
	 * target. Ultra-Low Power's cards have a spec line and grow past it.
	 */
	.card-media {
		flex-direction: row;
		align-items: stretch;
		min-height: clamp(76px, 21vw, 96px);
	}

	/*
	 * A fixed square, centered — deliberately not stretched to the card's height.
	 * Stretching tied the photo's size to how much text the card happened to
	 * carry, so a card with a long spec line showed a photo twice the size of
	 * its neighbour for no reason a reader could see. Every thumbnail is now
	 * identical, and small, because the text carries the meaning.
	 */
	.card-media .card-media__figure {
		flex: 0 0 clamp(62px, 17vw, 84px);
		aspect-ratio: 1 / 1;
		align-self: center;
		margin-left: 12px;
		overflow: hidden;
	}

	/* Without min-width:0 a flex child refuses to shrink below its content. */
	.card-media__body {
		flex: 1 1 auto;
		min-width: 0;
	}

	/*
	 * Absolute, not height:100%. The figure's height comes from the text beside
	 * it, so it is indefinite as far as the image is concerned — height:100%
	 * against an indefinite parent falls back to the image's intrinsic height
	 * and the card grows to a thousand-odd pixels.
	 */
	.card-media .card-media__thumb,
	.card-media .card-media__figure img {
		position: absolute;
		inset: 0;
		width: 100%;
		height: 100%;
		aspect-ratio: auto;
	}

	.card-media__body {
		justify-content: center;
		gap: 5px;
		padding: 12px 14px;
	}

	.card-media__title { font-size: 16px; }
	.card-media__text { font-size: 14px; line-height: 1.45; }
}

/* ---------------------------------------------------------------- 12. Split  */

.split {
	display: grid;
	grid-template-columns: 1.1fr 1fr;
	gap: var(--sp-8);
	align-items: center;
}

/* Home's splits are even and taller than the expertise page's. */
.split--even { grid-template-columns: 1fr 1fr; gap: 64px; }

.split > .wp-block-group__inner-container,
.split__body > .wp-block-group__inner-container {
	display: contents;
}

.split__body > * + * { margin-top: var(--sp-5); }

.split__media {
	display: block;
	width: 100%;
	height: 360px;
	object-fit: cover;
}

/* Image order is set by block order in the editor — no modifier needed. */
.split .split__figure {
	margin: 0;
	line-height: 0;
}

.split .split__figure img {
	display: block;
	width: 100%;
	height: 420px;
	object-fit: cover;
}

@media (max-width: 860px) {
	.split,
	.split--even { grid-template-columns: 1fr; gap: var(--sp-7); }
	.split__media { height: 280px; }
	.split .split__figure img { height: 280px; }
}

/* ------------------------------------------------------------ 12b. Home hero */

.home-hero {
	position: relative;
	overflow: hidden;
	background: var(--c-navy);
	color: var(--c-white);
}

/*
 * The photograph occupies the right of the hero, not the whole of it.
 *
 * At full width with object-fit: cover the chip rendered at close to its native
 * size and dominated the band — it read as the subject of the page rather than
 * the backdrop to the headline. Constraining the picture to the right 60% and
 * letting it fit rather than fill scales the chip down, and leaves the left of
 * the band as flat navy for the headline to sit on.
 */
.home-hero__media {
	position: absolute;
	top: -1px;
	right: 0;
	left: auto;
	width: 60%;
	height: 100%;
	object-fit: contain;
	object-position: right center;
	opacity: .9;
}

/*
 * Solid navy under the words, fading out across the picture.
 *
 * Fully opaque to 42% so the headline and lede sit on flat colour rather than on
 * a dimmed photograph, then falling away so the chip is not muddied.
 */
.home-hero__scrim {
	position: absolute;
	inset: 0;
	background: linear-gradient(
		to right,
		rgba(14, 17, 51, 1) 0%,
		rgba(14, 17, 51, 1) 42%,
		rgba(14, 17, 51, .82) 54%,
		rgba(14, 17, 51, .4) 72%,
		rgba(14, 17, 51, .1) 100%
	);
}

.home-hero__inner {
	position: relative;
	max-width: var(--container);
	margin: 0 auto;
	padding: 110px var(--gutter) 120px;
}

.home-hero__content { max-width: 600px; }

.home-hero__title {
	margin: 0 0 24px;
	font-size: var(--fs-h1);
	line-height: 1.1;
	color: var(--c-white);
}

.home-hero__lede {
	margin: 0 0 36px;
	font-size: var(--fs-lede);
	line-height: 1.5;
	color: rgba(255, 255, 255, .94);
}

.home-hero__actions {
	display: flex;
	flex-wrap: wrap;
	gap: 16px;
	margin: 0;
}

@media (max-width: 782px) {
	.home-hero__inner { padding: 64px var(--gutter) 72px; }

	/*
	 * On desktop the scrim runs left-to-right, because the headline occupies the
	 * left half and the photograph the right. On a phone the text runs the full
	 * width, so its right-hand end lands on the transparent end of that gradient
	 * — directly over the brightest part of the chip — and the words become hard
	 * to read. Below 782px the scrim becomes a top-to-bottom wash that is dark
	 * everywhere the text actually is, matching how the interior page heroes
	 * already work.
	 */
	.home-hero__scrim {
		background: linear-gradient(
			to bottom,
			rgba(14, 17, 51, .9) 0%,
			rgba(14, 17, 51, .86) 62%,
			rgba(14, 17, 51, .7) 100%
		);
	}

	/* Full width again on a phone: at 60% the chip would be too small to read. */
	.home-hero__media {
		width: 100%;
		object-fit: cover;
		object-position: 62% center;
		opacity: .6;
	}
}

/* --------------------------------------------------------------- 12c. Eyebrow */

.section__eyebrow {
	margin: 0 0 8px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.6px;
	text-transform: uppercase;
	color: var(--c-indigo);
}

.section--dark .section__eyebrow { color: var(--c-cyan); }

/*
 * The arrow is decorative and added in CSS rather than typed into the link text,
 * so screen readers announce "Learn More" and not "Learn More right arrow".
 */
.split__cta { margin: 0; }
.split__cta .btn { padding: 11px 24px; font-size: var(--fs-meta); }
.split__cta .btn::after { content: ' \2192'; }
.section--dark .split__body p { color: var(--c-on-dark-strong); }

/* --------------------------------------------------------------- 12d. Related */

.related {
	border-top: 1px solid var(--c-line-3);
	background: #dfe4ee;
	color: var(--c-ink);
}

.related__inner {
	max-width: var(--container);
	margin: 0 auto;
	padding: 34px var(--gutter);
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	gap: 14px 34px;
}

.related__label {
	margin: 0;
	flex: none;
	font-size: var(--fs-meta);
	letter-spacing: .1em;
	text-transform: uppercase;
	color: #6b7185;
}

.related__list {
	display: flex;
	flex-wrap: wrap;
	gap: 14px 30px;
	list-style: none;
	margin: 0;
	padding: 0;
}

.related__link {
	display: inline-flex;
	align-items: baseline;
	gap: 9px;
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	line-height: 1.3;
	color: var(--c-navy);
	text-decoration: none;
	border-bottom: 1px solid #c9cedb;
	padding-bottom: 3px;
}

.related__link:hover,
.related__link:focus-visible {
	color: var(--c-indigo);
	border-color: var(--c-indigo);
}

.related__arrow {
	color: var(--c-indigo);
	font-size: var(--fs-meta);
}

/* ------------------------------------------------------------ 13. IP blocks  */

.ip-blocks .container { padding-top: 80px; padding-bottom: 88px; }

.ip-blocks__title {
	margin: 0 0 30px;
	text-align: center;
	font-size: var(--fs-h2);
	color: var(--c-white);
}

.ip-blocks__list {
	max-width: var(--container-narrow);
	margin: 0 auto;
	display: flex;
	flex-direction: column;
	gap: 2px;
}

.ip-blocks__group {
	border: 1px solid var(--c-on-dark-edge);
	background: rgba(255, 255, 255, .04);
}

.ip-blocks__summary {
	cursor: pointer;
	list-style: none;
	padding: 16px 22px;
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	color: var(--c-white);
	display: flex;
	justify-content: space-between;
	gap: 16px;
}

.ip-blocks__summary:hover { background: rgba(255, 255, 255, .09); }

.ip-blocks__mark { color: var(--c-cyan); }

.ip-blocks__group[open] .ip-blocks__mark::after { content: '\2212'; } /* minus */
.ip-blocks__group:not([open]) .ip-blocks__mark::after { content: '\002B'; } /* plus */

.ip-blocks__items {
	margin: 0;
	padding: 4px 26px 22px 44px;
	font-size: var(--fs-meta);
	line-height: 1.7;
	color: #d6dae6;
	display: flex;
	flex-direction: column;
	gap: 7px;
}

/* --------------------------------------------------------- 14. Testimonial   */

.testimonial {
	background: var(--c-white);
	border-top: 1px solid var(--c-line);
	color: var(--c-ink);
}

.testimonial .container { padding-top: var(--sp-9); padding-bottom: var(--sp-9); }

.testimonial__figure {
	max-width: 880px;
	margin: 0 auto;
	text-align: center;
}

.testimonial__quote {
	margin: 0;
	font-family: var(--f-head);
	font-size: 22px;
	font-weight: 700;
	line-height: 1.5;
	color: var(--c-navy);
}

.testimonial__mark { color: #2f93a8; }

.testimonial__caption {
	display: flex;
	flex-wrap: wrap;
	align-items: baseline;
	justify-content: center;
	gap: 4px 14px;
	margin-top: 26px;
	padding-top: 20px;
	border-top: 1px solid var(--c-line);
	font-size: 16px;
	color: var(--c-slate);
}

.testimonial__name {
	font-family: var(--f-head);
	font-weight: 700;
	color: var(--c-navy);
}

/* ---------------------------------------------------------- 15. Site footer  */

.site-footer {
	background: var(--c-navy);
	border-top: 1px solid rgba(112, 204, 219, .28);
	color: var(--c-white);
	font-family: var(--f-body);
}

.site-footer__grid {
	max-width: var(--container);
	margin: 0 auto;
	padding: var(--sp-9) var(--gutter) var(--sp-7);
	display: grid;
	/*
	 * The README specifies four columns at 1.2fr 1fr 1fr 1fr. The design file's
	 * auto-fit minmax(250px) needs ~1192px of inner width to seat all four, so it
	 * dropped to three on anything narrower than a 1280px viewport. Explicit
	 * columns at desktop, auto-fit below.
	 */
	grid-template-columns: 1.2fr 1fr 1fr 1fr;
	gap: var(--sp-8) 64px;
}

@media (max-width: 1039px) {
	.site-footer__grid {
		grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
	}
}

.site-footer__logo {
	width: clamp(200px, 20vw, 268px);
	height: auto;
	display: block;
	margin-bottom: 20px;
}

.site-footer__tagline {
	margin: 0;
	font-size: 16px;
	line-height: 1.6;
	color: var(--c-on-dark-mute);
}

.site-footer__heading {
	margin: 0 0 18px;
	font-size: var(--fs-h5);
	color: var(--c-cyan);
}

.site-footer__list {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-direction: column;
	gap: 13px;
	font-size: var(--fs-meta);
	line-height: 1.45;
}

.site-footer__list a {
	color: var(--c-on-dark);
	text-decoration: none;
}

.site-footer__list a:hover,
.site-footer__list a:focus-visible { color: var(--c-cyan); }

.site-footer__col--contact {
	display: flex;
	flex-direction: column;
	gap: 13px;
	font-size: var(--fs-meta);
	line-height: 1.45;
	color: var(--c-on-dark);
}

.site-footer__contact-link {
	align-self: flex-start;
	color: var(--c-white);
	text-decoration: none;
	border-bottom: 1px solid rgba(112, 204, 219, .6);
}

.site-footer__contact-link:hover { color: var(--c-cyan); }

.site-footer__address {
	margin: 0;
	font-style: normal;
	line-height: 1.6;
}

.site-footer__phone {
	align-self: flex-start;
	color: var(--c-on-dark);
	text-decoration: none;
}

.site-footer__phone:hover { color: var(--c-cyan); }

.site-footer__bottom { border-top: 1px solid var(--c-on-dark-rule); }

.site-footer__legal {
	max-width: var(--container);
	margin: 0 auto;
	padding: 22px var(--gutter);
	display: flex;
	justify-content: space-between;
	gap: 16px;
	font-size: var(--fs-meta);
	color: var(--c-on-dark-faint);
}

.site-footer__legal p { margin: 0; }

@media (max-width: 600px) {
	.site-footer__legal { flex-direction: column; gap: 8px; }
}

/* ------------------------------------------------------- 16. Editor content  */

/* Page body content authored as core blocks in the WordPress editor. */
.prose > *:first-child { margin-top: 0; }
.prose > *:last-child { margin-bottom: 0; }

.prose h2 {
	margin: 0 0 26px;
	font-size: var(--fs-h2);
	line-height: 1.25;
}

.prose h3 {
	margin: 0 0 var(--sp-4);
	font-size: var(--fs-h3);
	line-height: 1.3;
}

.prose p {
	margin: 0 0 var(--sp-5);
	font-size: var(--fs-body);
	line-height: 1.75;
	color: var(--c-graphite);
}

.prose ul:not(.card-grid):not(.checklist) {
	margin: 0 0 var(--sp-5);
	padding-left: 22px;
	font-size: var(--fs-body-sm);
	line-height: 1.7;
}

/* ----------------------------------------------------------- 17. Responsive  */

@media (max-width: 1120px) {
	.subnav { position: relative; }
	.subnav::after {
		content: "";
		position: absolute;
		top: 0; right: 0; bottom: 1px;
		width: 40px;
		pointer-events: none;
		background: linear-gradient(to right, rgba(246,247,248,0), var(--c-mist));
	}
}

@media (max-width: 782px) {
	:root {
		--fs-h1: 34px;
		--fs-h2: 26px;
		--fs-h3: 21px;
		--fs-lede: 19px;
		--fs-body: 16px;
		--fs-body-sm: 15px;
		--gutter: 20px;
	}

	.page-hero__inner { padding: 56px var(--gutter) 48px; }
	.section .container { padding-top: 56px; padding-bottom: 48px; }
	.site-header__inner { min-height: 72px; }

	/*
	 * The expertise sub-nav has five long labels. Wrapping turns it into a tall
	 * ragged block that pushes the page content off screen, so on small screens
	 * it becomes a single scrollable strip instead — the current tab stays
	 * visible and the rest are one swipe away.
	 */
	.subnav__list {
		flex-wrap: nowrap;
		overflow-x: auto;
		gap: 0;
		scrollbar-width: none;
		-webkit-overflow-scrolling: touch;
	}

	.subnav__list::-webkit-scrollbar { display: none; }

	/* Without this the strip looks like it ends at the screen edge. */
	.subnav {
		position: relative;
	}

	.subnav::after {
		content: '';
		position: absolute;
		top: 0;
		right: 0;
		bottom: 1px;
		width: 40px;
		pointer-events: none;
		background: linear-gradient(to right, rgba(246, 247, 248, 0), var(--c-mist));
	}

	.subnav__item { flex: none; }

	.subnav__link {
		padding: 15px 14px;
		font-size: var(--fs-meta);
		white-space: nowrap;
	}

	/* 44px of left indent is a lot of a 390px screen. */
	.ip-blocks__items { padding: 4px 18px 18px 32px; }
	.ip-blocks__summary { padding: 14px 16px; font-size: 16px; }
	.ip-blocks .container { padding-top: 56px; padding-bottom: 56px; }
	.ip-blocks__title { margin-bottom: 20px; }

	.testimonial__quote { font-size: 19px; }
	.testimonial .container { padding-top: 48px; padding-bottom: 48px; }

	.card-grid { gap: 16px; }

	.split, .split--even { gap: var(--sp-6); }

	.site-footer__grid { gap: 36px 32px; padding-top: 48px; }
	.related__inner { padding: 24px var(--gutter); gap: 10px 20px; }
}

@media (max-width: 480px) {
	:root {
		--fs-h1: 29px;
		--fs-h2: 23px;
		--fs-lede: 18px;
	}

	.page-hero__inner { padding: 40px var(--gutter) 36px; }
	.home-hero__inner { padding: 48px var(--gutter) 52px; }
	.section .container { padding-top: 44px; padding-bottom: 40px; }

	/* Keep the chip visible behind the headline rather than cropping to sky. */
	.home-hero__media { object-position: 62% center; }

	.split .split__figure img,
	.split__media { height: 220px; }

	.nav-toggle { width: 44px; height: 44px; }

	.ip-blocks__items { padding: 4px 14px 16px 26px; font-size: 14px; }
	.card-media__title { font-size: 17px; }
}

/* ------------------------------------------------------------- 18. Glossary  */

/* A–Z index. Plain anchor links — no script needed to navigate a long page. */
.az {
	display: flex;
	flex-wrap: wrap;
	gap: 6px;
}

.az__link {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	min-width: 42px;
	min-height: 42px;
	padding: 0 10px;
	border: 1px solid var(--c-line-2);
	background: var(--c-white);
	color: var(--c-navy);
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	text-decoration: none;
}

.az__link:hover,
.az__link:focus-visible {
	border-color: var(--c-cyan);
	background: var(--c-cyan);
	color: var(--c-navy);
}

.glossary__letter {
	margin: 0 0 20px;
	font-size: var(--fs-h2);
	line-height: 1;
	color: var(--c-cyan-active);
	border-bottom: 3px solid var(--c-cyan);
	padding-bottom: 10px;
}

/*
 * A definition list, because that is what a glossary is. Two columns on wide
 * screens: term left, definition right, so the eye can run down the terms
 * without reading every definition.
 */
.glossary {
	margin: 0;
	display: grid;
	grid-template-columns: minmax(180px, 260px) minmax(0, 1fr);
	gap: 4px 32px;
	align-items: baseline;
}

.glossary__term {
	margin: 0;
	padding: 12px 0 12px;
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	color: var(--c-navy);
	border-top: 1px solid var(--c-line);
}

.glossary__def {
	margin: 0;
	padding: 12px 0;
	font-size: var(--fs-body-sm);
	line-height: 1.65;
	color: var(--c-graphite);
	border-top: 1px solid var(--c-line);
	max-width: 820px;
}

.glossary__back {
	margin: 26px 0 0;
	font-size: var(--fs-meta);
}

@media (max-width: 700px) {
	/* Stack on phones: a 180px term column leaves too little for the definition. */
	.glossary { grid-template-columns: 1fr; gap: 0; }
	.glossary__term { padding-bottom: 2px; border-top: 1px solid var(--c-line); }
	.glossary__def { padding-top: 0; border-top: 0; padding-bottom: 16px; }
}

/* -------------------------------------------------------------- 19. Contact  */

.contact-layout {
	display: grid;
	grid-template-columns: minmax(0, 1.4fr) minmax(0, 1fr);
	gap: clamp(32px, 5vw, 64px);
	align-items: start;
}

@media (max-width: 860px) {
	.contact-layout { grid-template-columns: 1fr; }
}

.form { display: flex; flex-direction: column; gap: var(--sp-5); max-width: 620px; }

.form__field { display: flex; flex-direction: column; gap: 6px; }

.form__label {
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	color: var(--c-navy);
}

.form__label-note {
	font-family: var(--f-body);
	font-weight: 400;
	color: var(--c-slate);
	font-size: var(--fs-meta);
}

.form__hint { margin: 0; font-size: var(--fs-meta); color: var(--c-slate); }

.form__input,
.form__textarea {
	width: 100%;
	padding: 12px 14px;
	border: 1px solid var(--c-line-2);
	border-radius: 0;
	background: var(--c-white);
	color: var(--c-ink);
	font-family: var(--f-body);
	/* 16px minimum stops iOS zooming the page when a field is focused. */
	font-size: 16px;
	line-height: 1.5;
}

.form__input:focus,
.form__textarea:focus {
	outline: 3px solid var(--c-cyan);
	outline-offset: 1px;
	border-color: var(--c-cyan);
}

.form__textarea { resize: vertical; min-height: 150px; }

.form__actions { margin-top: var(--sp-2); }

/* Hidden from people, left visible to bots. Not display:none — bots skip that. */
.form__honeypot {
	position: absolute;
	left: -9999px;
	width: 1px;
	height: 1px;
	overflow: hidden;
}

.notice { padding: 16px 20px; border-left: 3px solid; margin-bottom: var(--sp-5); }
.notice p { margin: 0 0 6px; }
.notice p:last-child { margin-bottom: 0; }
.notice--success { border-color: var(--c-cyan); background: var(--c-band); }
.notice--error { border-color: #b3261e; background: #fdf3f2; color: #5f1710; }

.contact-info { list-style: none; margin: 0 0 var(--sp-7); padding: 0; display: flex; flex-direction: column; gap: var(--sp-4); }
.contact-info__item { display: flex; flex-direction: column; gap: 2px; }

.contact-info__label {
	font-family: var(--f-mono, var(--f-body));
	font-size: var(--fs-small);
	letter-spacing: .1em;
	text-transform: uppercase;
	color: var(--c-slate);
	margin: 0 0 6px;
}

.contact-info__value { font-size: var(--fs-body-sm); color: var(--c-navy); font-style: normal; }

.contact-note { border-top: 3px solid var(--c-cyan); padding-top: 18px; }
.contact-note h3 { margin: 0 0 12px; font-size: var(--fs-h5); }

/* ---------------------------------------------------------------- 20. About  */

/* Management team: role, name, then bio. */
/*
 * Management team.
 *
 * Three long biographies side by side read as three walls of grey text unless
 * each one is given an edge. Two things fix that:
 *
 * 1. The name comes before the role. With the role first, a long one ("VP of
 *    Marketing and Business Development") wrapped to two lines and pushed that
 *    person's name a line lower than the other two, so the three names — the
 *    thing a reader actually scans for — did not line up.
 * 2. Each person sits on their own white card. The bios are long and of unequal
 *    length; without a surface behind them the columns run into each other and
 *    it is not obvious where one person ends and the next begins.
 */

.team {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(min(100%, 320px), 1fr));
	gap: clamp(20px, 2.4vw, 28px);
	align-items: start;
}

.team > .wp-block-group__inner-container { display: contents; }

/* Hairline as well as the cyan rule: the section behind this is white, so a
   white card with no border is invisible. */
.team__member {
	border: 1px solid var(--c-line-3);
	border-top: 3px solid var(--c-cyan);
	background: var(--c-white);
	padding: 24px clamp(20px, 2vw, 26px) 8px;
	box-shadow: 0 1px 3px rgba(14, 17, 51, .06);
}

.team__member > .wp-block-group__inner-container { display: block; }

.team__name {
	margin: 0 0 6px;
	font-size: var(--fs-h3);
	line-height: 1.25;
}

/*
 * Reserve two lines whatever the role is called. "President and CEO" fits on one
 * line and "VP of Marketing and Business Development" needs two, which pushed
 * that column's divider and opening sentence 29px below the other two.
 */
.team__role {
	margin: 0 0 16px;
	padding-bottom: 16px;
	border-bottom: 1px solid var(--c-line-3);
	font-size: var(--fs-meta);
	font-weight: 700;
	line-height: 1.45;
	min-height: 4.4em;   /* two lines of an uppercase role, so all three cards align */
	letter-spacing: 1.4px;
	text-transform: uppercase;
	color: var(--c-indigo);
}

.team__member p { font-size: var(--fs-body-sm); line-height: 1.7; margin: 0 0 16px; }

/*
 * Partner logos. A grid of evenly-sized cells rather than raw images: the source
 * logos vary wildly in shape and background, and left unconstrained they read as
 * a jumble. Each sits centered in its own bordered cell at a capped height.
 */
.partners {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(min(100%, 240px), 1fr));
	gap: 14px;
	list-style: none;
	margin: 0 0 var(--sp-7);
	padding: 0;
}

.partners > .wp-block-group__inner-container { display: contents; }

/*
 * The cell was 160px wide with 16px of padding, leaving 128px for a logo — and
 * most of these files carry their own generous whitespace margin on top of that,
 * so the mark itself ended up rendering at well under half the cell. A wider
 * cell, tighter padding and a taller cap give a wide wordmark room to actually
 * grow before anything clips it.
 */
.partners__item {
	display: flex;
	align-items: center;
	justify-content: center;
	min-height: 124px;
	padding: 12px 16px;
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
}

/*
 * width: 100%, not auto — and this is the actual reason the logos rendered tiny.
 *
 * WordPress marks these lazy and gives them sizes="auto", which tells the browser
 * to choose a file based on the element's laid-out width. With width: auto the
 * laid-out width depends on which file was chosen, and the choice depends on the
 * laid-out width. That circle settles low: every logo came out 87px wide inside a
 * 193px cell, whatever its source file. Enlarging the cell alone made it worse,
 * because the logo stayed 87px and the empty space around it grew.
 *
 * An explicit width breaks the circle: the cell decides the width, the browser
 * then picks a file that suits it, and max-height stops a tall mark overpowering
 * a wide one.
 */
/*
 * 2026-08-26 — the marks were reported as "really small and some of them very
 * hard to read". Checked before changing anything: the source files are around
 * 1024px wide but were rendering at roughly 125px, so there is ample real
 * resolution to spend. Enlarging these does not soften them.
 */
.partners__item img {
	width: 100%;
	height: auto;
	max-height: 92px;
	object-fit: contain;
}

/* Partners with no logo supplied show their name instead of an empty box. */
.partners__name {
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-meta);
	color: var(--c-slate);
	text-align: center;
	line-height: 1.35;
}

.partners__group { margin: 0 0 12px; font-size: var(--fs-h3); }

/*
 * 2026-08-28 — on phones the auto-fill 240px minimum meant one logo per row,
 * so the section became a huge scroll of oversized cards (reported from a
 * real device). Logo-wall convention: two per row on phones, three-to-five on
 * larger screens. Cells and logo caps shrink with them so the cards stop
 * looking like empty frames — which also fixes the text-only partners
 * (no logo file exists yet) sitting alone in a tall box.
 */
@media (max-width: 699px) {
	.partners { grid-template-columns: repeat(2, 1fr); gap: 10px; }
	.partners__item { min-height: 76px; padding: 10px 12px; }
	.partners__item img { max-height: 56px; }
	.partners__name { font-size: 13px; }
}

/* FAQs — native details, no script. */
.faq { display: flex; flex-direction: column; gap: 2px; max-width: 900px; }
.faq > .wp-block-group__inner-container { display: contents; }

.faq .wp-block-details {
	border: 1px solid var(--c-line);
	background: var(--c-white);
}

.faq .wp-block-details summary {
	cursor: pointer;
	list-style: none;
	padding: 18px 22px;
	font-family: var(--f-head);
	font-weight: 700;
	font-size: var(--fs-body-sm);
	color: var(--c-navy);
	display: flex;
	justify-content: space-between;
	gap: 16px;
	align-items: flex-start;
}

.faq .wp-block-details summary::-webkit-details-marker { display: none; }
.faq .wp-block-details summary:hover { background: var(--c-mist); }

.faq .wp-block-details summary::after {
	content: '\002B';
	flex: none;
	color: var(--c-cyan-active);
	font-size: 22px;
	line-height: 1;
}

.faq .wp-block-details[open] summary::after { content: '\2212'; }

.faq .wp-block-details p {
	margin: 0;
	padding: 0 22px 20px;
	font-size: var(--fs-body-sm);
	line-height: 1.7;
	color: var(--c-graphite);
	max-width: 820px;
}

/* ------------------------------------------- 19. Long-form explainer pages  */

/*
 * Turnkey ASICs is the longest page on the site: seven sections, roughly two
 * thousand words. Three components carry it, and each exists because the content
 * has a shape that a plain run of paragraphs would hide.
 *
 *   .section__body  prose held to a readable measure
 *   .steps          a real sequence — numbered, because the order is the point
 *   .panels         parallel options — a grid, because they are compared, not read
 *
 * Nothing else was added. A long page needs fewer kinds of thing on it, not more.
 */

/* --- Prose ---------------------------------------------------------------- */

/*
 * The container runs to 1280px. Body text at that width is roughly 160
 * characters a line, about twice the length at which people reliably find the
 * start of the next one.
 */
.section__body {
	max-width: 820px;
}

.section__body > .wp-block-group__inner-container { display: contents; }

.section__body p {
	margin: 0 0 var(--sp-5);
	font-size: var(--fs-body);
	line-height: 1.75;
	color: var(--c-graphite);
}

.section__body h3 {
	margin: var(--sp-6) 0 var(--sp-4);
	font-size: var(--fs-h3);
	line-height: 1.3;
}

.section__body > *:first-child { margin-top: 0; }
.section__body > *:last-child { margin-bottom: 0; }

/* --- Steps ---------------------------------------------------------------- */

/*
 * Numbered deliberately. The six phases happen in order, each gated by a review
 * that must pass before the next begins, so the number carries real information
 * rather than decorating the list. A grid rather than a stack: the phases are
 * short and comparable, and stacking them buried the later ones.
 */
.steps {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(min(100%, 340px), 1fr));
	gap: clamp(16px, 2vw, 24px);
	margin-top: var(--sp-8);
	counter-reset: step;
}

.steps > .wp-block-group__inner-container { display: contents; }

.step {
	position: relative;
	counter-increment: step;
	padding: 26px 24px 22px;
	background: rgba(255, 255, 255, .05);
	border: 1px solid var(--c-on-dark-edge);
	border-top: 3px solid var(--c-cyan);
}

.step > .wp-block-group__inner-container { display: block; }

.step::before {
	content: counter(step);
	display: block;
	margin-bottom: 10px;
	font-family: var(--f-head);
	font-size: var(--fs-h3);
	font-variant-numeric: tabular-nums;
	line-height: 1;
	color: var(--c-cyan);
}

.step__title {
	margin: 0 0 12px;
	font-size: var(--fs-h3);
	line-height: 1.25;
	color: var(--c-white);
}

.step p {
	margin: 0 0 14px;
	font-size: var(--fs-body-sm);
	line-height: 1.65;
	color: var(--c-on-dark);
}

/* The gate that closes each phase — the thing a buyer actually wants to find. */
.step__gate {
	margin: 0;
	padding-top: 12px;
	border-top: 1px solid var(--c-on-dark-rule);
	font-size: var(--fs-meta);
	font-weight: 700;
	line-height: 1.5;
	color: var(--c-cyan);
}

/* --- Panels --------------------------------------------------------------- */

/*
 * Parallel options, not a sequence — so no numbers. Five engagement models and
 * three test capability groups are both read by scanning across for the one that
 * applies, which is what a grid supports and a stack of headings does not.
 */
.panels {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(min(100%, 300px), 1fr));
	gap: clamp(16px, 2vw, 24px);
	margin-top: var(--sp-7);
}

.panels > .wp-block-group__inner-container { display: contents; }

.panels--three { grid-template-columns: repeat(auto-fit, minmax(min(100%, 260px), 1fr)); }

.panel {
	padding: 26px 24px 22px;
	background: var(--c-white);
	border: 1px solid var(--c-line-3);
	border-top: 3px solid var(--c-cyan);
}

.panel > .wp-block-group__inner-container { display: block; }

.panel__title {
	margin: 0 0 12px;
	font-size: var(--fs-h3);
	line-height: 1.25;
}

.panel p {
	margin: 0;
	font-size: var(--fs-body-sm);
	line-height: 1.7;
	color: var(--c-graphite);
}

.panel .checklist { margin-top: 0; }
.panel .checklist li { font-size: var(--fs-body-sm); }

/* --- Dark section text ---------------------------------------------------- */

.section--dark .section__eyebrow { color: var(--c-cyan); }
.section--dark .section__intro { color: var(--c-on-dark); }
.section--dark .section__body p { color: var(--c-on-dark); }
.section--dark .section__body h3 { color: var(--c-white); }

/* --- Closing call to action ----------------------------------------------- */

/*
 * A reader who has come two thousand words should not have to scroll back to the
 * hero to act. Centered, because it is the only thing in the band.
 */
.cta-band .container {
	max-width: 760px;
	text-align: center;
}

.cta-band .section__intro { margin: 0 auto; }
.cta-band__actions { margin: var(--sp-6) 0 0; }

/* ----------------------------------------------- 20. ASIC case study pages  */

/*
 * The solution section pairs the explanation with the die layout. Text first on
 * a phone — the layout illustrates the words rather than introducing them, so it
 * should not push the explanation below the fold.
 */
.case-split {
	display: grid;
	grid-template-columns: minmax(0, 1fr);
	gap: clamp(24px, 3vw, 44px);
	align-items: start;
}

.case-split > .wp-block-group__inner-container { display: contents; }

@media (min-width: 861px) {
	.case-split { grid-template-columns: minmax(0, 1fr) 360px; }
}

.case-split .section__body { max-width: none; }

/*
 * The layouts are 500px square. Displayed larger they go soft, so the cell is
 * capped rather than filled, and the white mat keeps a light-on-light layout
 * from bleeding into the tinted section behind it.
 */
.case-layout {
	margin: 0;
	max-width: 360px;
	padding: 14px;
	background: var(--c-white);
	border: 1px solid var(--c-line-3);
}

.case-layout img {
	display: block;
	width: 100%;
	height: auto;
}

.case-layout figcaption {
	margin: 12px 0 0;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.2px;
	text-transform: uppercase;
	color: var(--c-slate);
	text-align: left;
}

/*
 * Spec strip — the headline numbers, directly under the hero.
 *
 * These are not new facts. Every value is lifted from the Key Features list
 * further down the same page; the strip just promotes the three or four an
 * engineer qualifies on, so they are readable without scrolling. Some chips list
 * four features and some list twenty-one, which is the whole reason the strip
 * exists: a reader should not have to parse twenty-one bullets to learn whether
 * the part is even in range.
 */
.specs {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(min(100%, 180px), 1fr));
	gap: 1px;
	margin: 0;
	padding: 0;
	list-style: none;
	background: var(--c-line-3);
	border: 1px solid var(--c-line-3);
}

.specs > .wp-block-group__inner-container { display: contents; }

.spec {
	background: var(--c-white);
	padding: 20px 22px;
}

.spec > .wp-block-group__inner-container { display: block; }

.spec__key {
	margin: 0 0 6px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.3px;
	text-transform: uppercase;
	color: var(--c-slate);
}

.spec__value {
	margin: 0;
	font-family: var(--f-head);
	font-size: var(--fs-h3);
	line-height: 1.2;
	font-variant-numeric: tabular-nums;
	color: var(--c-navy);
}

/* The strip sits tight under the hero rather than as a full section of its own. */
.section--specs .container { padding-top: 32px; padding-bottom: 32px; }

/* --------------------------------------------- 21. Draft copy, clearly marked */

/*
 * Any wording on this site that did NOT come from the current site or the design
 * handoff is marked with .draft. It is CSS's content, not ours to write, and an
 * unmarked suggestion sitting in a finished-looking page is indistinguishable
 * from approved copy — which is exactly how invented wording ends up published.
 *
 * The marker is loud on purpose and the layout underneath is real, so the page
 * can be judged as a design while nobody mistakes the words for signed-off copy.
 *
 * REMOVE BEFORE LAUNCH. A Site Health check counts these and reports while any
 * remain, so this cannot ship unnoticed.
 */
.draft {
	background: #fdf3e0;
	box-shadow: inset 0 -2px 0 #d9a441;
	color: #6b4a12;
	padding: 0 3px;
}

.section--dark .draft {
	background: rgba(217, 164, 65, .18);
	color: #f0d9a8;
}

.draft__tag {
	display: inline-block;
	margin-left: 6px;
	padding: 1px 6px;
	border-radius: 3px;
	background: #d9a441;
	color: #2b1d05;
	font-family: var(--f-body);
	font-size: 10px;
	font-weight: 700;
	letter-spacing: 1px;
	text-transform: uppercase;
	vertical-align: middle;
	white-space: nowrap;
}

/* A whole block of draft copy rather than a phrase. */
.draft-block {
	border: 2px dashed #d9a441;
	background: #fdf3e0;
	padding: 16px 18px;
	margin: 0 0 var(--sp-5);
}

.section--dark .draft-block {
	background: rgba(217, 164, 65, .12);
	border-color: rgba(217, 164, 65, .55);
}

.draft-block > *:last-child { margin-bottom: 0; }

.draft-block__note {
	margin: 0 0 10px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1px;
	text-transform: uppercase;
	color: #8a5714;
}

.section--dark .draft-block__note { color: #e8c88a; }

/* ------------------------------------------ 22. Build notes, out of the way  */

/*
 * Notes about unfinished work sit beside the page, never inside it.
 *
 * They began as amber boxes in the content, which broke the design of the very
 * pages they commented on — impossible to judge a layout through a wall of
 * annotation. Now the page renders exactly as it will on launch day, and a small
 * counter in the corner opens the notes in a panel. Nothing in the layout moves.
 *
 * Everything here disappears the moment the notes are removed from the content,
 * and Site Health reports while any remain.
 */

.sitenote { display: none; }

.notes-toggle {
	position: fixed;
	right: 18px;
	bottom: 18px;
	z-index: 90;
	display: inline-flex;
	align-items: center;
	gap: 8px;
	padding: 11px 16px;
	border: 1px solid var(--c-on-dark-edge);
	border-radius: 22px;
	background: var(--c-navy);
	color: var(--c-white);
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	line-height: 1;
	cursor: pointer;
	box-shadow: 0 6px 20px rgba(14, 17, 51, .28);
}

.notes-toggle:hover { background: var(--c-navy-deep); }

.notes-toggle__count {
	display: inline-grid;
	place-items: center;
	min-width: 20px;
	height: 20px;
	padding: 0 5px;
	border-radius: 10px;
	background: #d9a441;
	color: #2b1d05;
	font-variant-numeric: tabular-nums;
}

/* [hidden] alone loses to display:flex below, so it is restated here. */
.notes-panel[hidden] { display: none; }

.notes-panel {
	position: fixed;
	top: 0;
	right: 0;
	bottom: 0;
	z-index: 95;
	width: min(400px, 92vw);
	display: flex;
	flex-direction: column;
	background: var(--c-white);
	border-left: 1px solid var(--c-line-2);
	box-shadow: -8px 0 28px rgba(14, 17, 51, .18);
	overflow-y: auto;
}

.notes-panel__head {
	position: sticky;
	top: 0;
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 12px;
	padding: 18px 20px;
	background: var(--c-navy);
	color: var(--c-white);
}

.notes-panel__title {
	margin: 0;
	font-family: var(--f-head);
	font-size: var(--fs-h3);
	color: var(--c-white);
}

.notes-panel__close {
	border: 0;
	background: none;
	color: var(--c-white);
	font-size: 26px;
	line-height: 1;
	padding: 0 4px;
	cursor: pointer;
}

.notes-panel__list { padding: 6px 20px 28px; }

.notes-panel__item {
	padding: 18px 0;
	border-bottom: 1px solid var(--c-line-3);
}

.notes-panel__item:last-child { border-bottom: 0; }

.notes-panel__where {
	margin: 0 0 8px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.1px;
	text-transform: uppercase;
	color: #8a5714;
}

.notes-panel__body p,
.notes-panel__body li {
	font-size: var(--fs-body-sm);
	line-height: 1.6;
	color: var(--c-graphite);
}

.notes-panel__body p { margin: 0 0 10px; }
.notes-panel__body ul { margin: 0 0 10px; padding-left: 20px; }
.notes-panel__body > *:last-child { margin-bottom: 0; }

.notes-panel__jump {
	margin-top: 10px;
	padding: 0;
	border: 0;
	background: none;
	color: var(--c-indigo);
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	text-decoration: underline;
	cursor: pointer;
}

/* Briefly mark the section a note refers to. */
.is-note-target {
	outline: 3px solid #d9a441;
	outline-offset: -3px;
}

/*
 * Wording written by Claude rather than taken from CSS's own copy. Quiet by
 * default — a dotted underline only — so it does not shout through the design.
 * The full amber treatment appears only while the notes panel is open.
 */
.draft {
	background: none;
	box-shadow: none;
	color: inherit;
	padding: 0;
	border-bottom: 1px dotted #c79a3f;
}

.draft__tag { display: none; }

.notes-open .draft {
	background: #fdf3e0;
	box-shadow: inset 0 -2px 0 #d9a441;
	color: #6b4a12;
	padding: 0 3px;
	border-bottom: 0;
}

.notes-open .draft__tag { display: inline-block; }

@media print {
	.notes-toggle,
	.notes-panel { display: none !important; }
}

/*
 * Case study columns.
 *
 * Every section on a case study page runs text down the left and something
 * useful down the right. Before this, only the Custom Solution section had a
 * right-hand element, so Application and Key Features left a third of the page
 * empty — and narrowing just those two threw the left edges out of line with the
 * rest of the page, which looked worse than the empty space did.
 */
.spec-panel {
	border: 1px solid var(--c-line-3);
	border-top: 3px solid var(--c-cyan);
	background: var(--c-white);
	padding: 20px 22px 6px;
}

.spec-panel > .wp-block-group__inner-container { display: block; }

.spec-panel__title {
	margin: 0 0 14px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.3px;
	text-transform: uppercase;
	color: var(--c-slate);
}

.spec-panel__row {
	margin: 0 0 14px;
	padding-bottom: 14px;
	border-bottom: 1px solid var(--c-line-3);
}

.spec-panel__row:last-of-type { border-bottom: 0; }

.spec-panel__key {
	display: block;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	color: var(--c-slate);
	margin-bottom: 2px;
}

.spec-panel__value {
	display: block;
	font-family: var(--f-head);
	font-size: var(--fs-h3);
	line-height: 1.25;
	font-variant-numeric: tabular-nums;
	color: var(--c-navy);
}

/* Long feature lists read better in two columns than as one tall stack. */
.checklist--two {
	max-width: none;
	columns: 2;
	column-gap: clamp(28px, 4vw, 56px);
}

.checklist--two li { break-inside: avoid; }

@media (max-width: 720px) {
	.checklist--two { columns: 1; }
}

/*
 * Placeholder buttons.
 *
 * A button cannot carry the inline placeholder marker without the marker
 * swallowing the button, so the button itself is outlined instead. Same signal,
 * same amber, no effect on the layout.
 */
.btn--placeholder {
	position: relative;
	outline: 2px dashed #d9a441;
	outline-offset: 3px;
}

.notes-open .btn--placeholder::after {
	content: "placeholder";
	position: absolute;
	left: 50%;
	top: calc(100% + 8px);
	transform: translateX(-50%);
	padding: 2px 7px;
	border-radius: 3px;
	background: #d9a441;
	color: #2b1d05;
	font-family: var(--f-body);
	font-size: 10px;
	font-weight: 700;
	letter-spacing: 1px;
	text-transform: uppercase;
	white-space: nowrap;
}

/* A second pairing inside the same section needs air above it. */
.case-split--spaced { margin-top: clamp(32px, 4vw, 56px); }

/*
 * Who delivers what, inside a development phase.
 *
 * The Customer / CSS split is the most useful thing on the design flow for a
 * buyer — it says plainly what they have to produce at each stage — so it gets
 * its own label rather than being folded into the paragraph.
 */
.step__who {
	margin: 16px 0 6px;
	font-family: var(--f-body);
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 1.1px;
	text-transform: uppercase;
	color: var(--c-cyan);
}

.step__list {
	margin: 0;
	padding-left: 18px;
	font-size: var(--fs-body-sm);
	line-height: 1.6;
	color: var(--c-on-dark);
}

.step__list li { margin: 0 0 5px; }

/* Phases carry far more detail now, so they need a wider column. */
.steps { grid-template-columns: repeat(auto-fit, minmax(min(100%, 360px), 1fr)); }

/* ------------------------------------------------- 25. Contact split panel  */

/*
 * CLASS INVENTORY EXTENSION (see the header note): .contact-split,
 * .contact-split__info, .contact-split__form, .map-card, .map-card__body,
 * .map-card__note.
 *
 * The supplied Contact_Page deck shows the page as two full-height panels side
 * by side — details on a light ground, form on a dark one. Nothing in the
 * existing inventory does that: .contact-layout is a plain two-column grid with
 * no backgrounds, and giving it backgrounds would change the live contact page.
 * So this is a separate component, additive only. Existing pages are untouched.
 *
 * The deck's palette (grey, red links, Facebook and Twitter marks) is mockup
 * styling, not this site's. The structure is taken from the deck; the colours
 * are the theme's own tint and navy.
 */
.contact-split {
	display: grid;
	grid-template-columns: minmax(0, 1fr) minmax(0, 1.1fr);
	align-items: stretch;
}

@media (max-width: 860px) {
	.contact-split { grid-template-columns: 1fr; }
}

.contact-split__info,
.contact-split__form { padding: clamp(28px, 4vw, 56px); }

.contact-split__info { background: var(--c-mist, var(--c-tint, #eef1f6)); }

.contact-split__form { background: var(--c-navy); color: var(--c-on-dark); }

.contact-split__form .section__title,
.contact-split__form .form__label { color: var(--c-white); }

.contact-split__form .form__hint,
.contact-split__form .form__label-note { color: var(--c-on-dark); }

/*
 * A link out to Google Maps rather than an embedded map. An <iframe> from
 * google.com would be a third-party origin loading before the visitor has
 * agreed to anything, which both BUILD-SPEC 1.1 and the privacy policy would
 * have to account for. A card that links out costs one click and no tracking.
 */
.map-card {
	display: block;
	margin-top: var(--sp-6);
	border: 1px solid var(--c-line-3);
	border-top: 3px solid var(--c-cyan);
	background: var(--c-white);
	text-decoration: none;
}

.map-card__body { padding: 18px 20px; }

.map-card__note {
	display: block;
	margin-top: 6px;
	font-size: var(--fs-small);
	color: var(--c-slate);
}

.map-card:hover { border-color: var(--c-cyan); }

/*
 * Map embed. CLASS INVENTORY EXTENSION: .map-embed.
 *
 * aspect-ratio keeps the frame from collapsing to the iframe default of 150px
 * and holds its height before the frame loads, so nothing below it jumps.
 */
.map-embed {
	margin-top: var(--sp-6);
	aspect-ratio: 4 / 3;
	border: 1px solid var(--c-line-3);
	background: var(--c-line-3);
}

.map-embed iframe {
	display: block;
	width: 100%;
	height: 100%;
	border: 0;
}

.map-card { margin-top: var(--sp-4); }

/*
 * Contact list with icons. CLASS INVENTORY EXTENSION: .contact-info--icons,
 * .contact-info__icon.
 *
 * A modifier rather than a change to .contact-info, so the live contact page
 * and the other review variants keep the plain list. Two rows (label, value)
 * with the icon spanning both, so the glyph aligns to the label's cap height
 * rather than floating between the lines.
 */
.contact-info--icons .contact-info__item {
	display: grid;
	grid-template-columns: 22px minmax(0, 1fr);
	column-gap: 14px;
	align-items: start;
}

.contact-info__icon {
	grid-row: 1 / span 2;
	margin-top: 1px;
	color: var(--c-cyan);
}

.contact-info__icon svg {
	display: block;
	width: 22px;
	height: 22px;
}

.contact-info--icons .contact-info__label { margin-bottom: 2px; }

/*
 * Contact split: explicit placement so the map can be a sibling of the two
 * panels rather than a child of the details panel.
 *
 * Desktop: details top-left, map beneath it, form filling the right column
 * across both rows.
 *
 * Phone: details, then form, then map. The details block is four short lines
 * and a tap-to-call number, so it costs almost no scroll and serves the visitor
 * who only wants to ring. The map is the tall element, so it goes last — the
 * form should not be pushed a screen down by it.
 */
.contact-split__info { grid-column: 1; grid-row: 1; }
.contact-split__map  { grid-column: 1; grid-row: 2; padding: 0 clamp(28px, 4vw, 56px) clamp(28px, 4vw, 56px); background: var(--c-mist, var(--c-tint, #eef1f6)); }
.contact-split__form { grid-column: 2; grid-row: 1 / span 2; }

@media (max-width: 860px) {
	.contact-split__info { grid-column: 1; grid-row: 1; }
	.contact-split__form { grid-column: 1; grid-row: 2; }
	.contact-split__map  { grid-column: 1; grid-row: 3; padding: clamp(28px, 4vw, 56px); }
}

/* The whole address is a link to the map; keep it reading as an address. */
.contact-info__value a { color: inherit; }

/* Required-field marker. CLASS INVENTORY EXTENSION: .form__required. */
.form__required {
	margin-left: 3px;
	color: var(--c-cyan);
	font-weight: 700;
}

/* On the navy panel the cyan asterisk needs to stay legible. */
.contact-split__form .form__required { color: var(--c-cyan); }

/*
 * Consent checkbox. CLASS INVENTORY EXTENSION: .form__consent,
 * .form__consent-label.
 *
 * The checkbox sits on the first line of the sentence rather than centred
 * against a wrapped block, and the whole sentence is inside the label so the
 * tap target is the text, not just the 16px box — which matters on a phone.
 */
.form__consent-label {
	display: grid;
	grid-template-columns: auto minmax(0, 1fr);
	column-gap: 10px;
	align-items: start;
	font-size: var(--fs-body-sm);
	line-height: 1.55;
	cursor: pointer;
}

.form__consent-label input {
	width: 16px;
	height: 16px;
	margin-top: 3px;
}

.contact-split__form .form__consent-label { color: var(--c-on-dark); }
.contact-split__form .form__consent-label a { color: var(--c-cyan); }

/*
 * Photographic hero. CLASS INVENTORY EXTENSION: .home-hero--photo.
 *
 * The base .home-hero was built around the chip render: pinned to the right 60%
 * and object-fit: contain so it sits behind the headline rather than competing
 * with it. A building photograph needs to fill the band and crop, and the band
 * itself should be shorter — on a contact page the form is what the visitor
 * came for, and 230px of hero padding pushes it off the first screen.
 */
.home-hero--photo .home-hero__media {
	width: 100%;
	object-fit: cover;
	object-position: center 42%;
	opacity: 1;
}

/* Fill left-to-right instead of fading out early, so the headline stays legible
   over a photograph rather than over flat navy. */
.home-hero--photo .home-hero__scrim {
	background: linear-gradient(
		to right,
		rgba(14, 17, 51, .92) 0%,
		rgba(14, 17, 51, .78) 38%,
		rgba(14, 17, 51, .45) 68%,
		rgba(14, 17, 51, .28) 100%
	);
}

.home-hero--photo .home-hero__inner { padding: 68px var(--gutter) 76px; }

@media (max-width: 782px) {
	.home-hero--photo .home-hero__inner { padding: 48px var(--gutter) 54px; }
}

/* A location confirmation, not something to explore — 4:3 was needlessly deep. */
.map-embed { aspect-ratio: 16 / 10; }

/*
 * Icon placement, revised.
 *
 * The icon was spanning both rows, which put it beside the LABEL — a pin next
 * to the word "Irvine Headquarters" rather than next to the address itself. The
 * icon belongs with the thing it marks, so the label now runs full width and
 * the icon sits on the value row.
 *
 * align-items: start on the value row keeps the glyph on the first line of a
 * two-line address instead of centring against the block.
 */
.contact-info--icons .contact-info__label {
	grid-column: 1 / -1;
	grid-row: 1;
}

.contact-info__icon {
	grid-column: 1;
	grid-row: 2;
	margin-top: 2px;
}

.contact-info--icons .contact-info__value {
	grid-column: 2;
	grid-row: 2;
}

/* ------------------------------------------- 26. Contact hero, revised      */

/*
 * CLASS INVENTORY EXTENSION: .section--bleed, .nowrap.
 *
 * THE SCRIM. The first version darkened the whole band, which buried the
 * photograph — the building was there the entire time and simply could not be
 * seen. The gradient now goes near-opaque only under the words and clears
 * almost completely by the middle, so the headline stays legible and the
 * building is actually visible.
 *
 * THE CROP. A wide short band cannot show a whole building without either
 * letterboxing or growing very tall. Brightness sampling of the source puts the
 * sky at 0-50% and the building at 50-75%, so the frame is positioned at 58% to
 * sit on the building rather than on sky or on the landscaping below it, and the
 * band is given a minimum height so the roofline is not clipped.
 */
.home-hero--photo .home-hero__scrim {
	background: linear-gradient(
		to right,
		rgba(14, 17, 51, .88) 0%,
		rgba(14, 17, 51, .70) 26%,
		rgba(14, 17, 51, .30) 48%,
		rgba(14, 17, 51, .06) 70%,
		rgba(14, 17, 51, 0) 100%
	);
}

.home-hero--photo .home-hero__media { object-position: center 58%; }

.home-hero--photo { min-height: 440px; display: flex; align-items: center; }

.home-hero--photo .home-hero__inner {
	width: 100%;
	padding: 40px var(--gutter) 44px;
}

@media (max-width: 782px) {
	.home-hero--photo { min-height: 340px; }
	.home-hero--photo .home-hero__inner { padding: 32px var(--gutter) 36px; }

	/* On a phone the band is narrow enough that a left-only scrim leaves the
	   headline over foliage, so darken the whole thing instead. */
	.home-hero--photo .home-hero__scrim {
		background: linear-gradient( to right, rgba(14, 17, 51, .82) 0%, rgba(14, 17, 51, .62) 100% );
	}
}

/* Keeps a proper noun from breaking across lines. */
.nowrap { white-space: nowrap; }

/* A section whose children supply their own full-width grounds. */
.section--bleed { padding-left: 0; padding-right: 0; }

/* ------------------------------- 27. Contact body: one lifted form card     */

/*
 * Previous attempts made BOTH columns panels, so the page carried a single
 * heavy slab with a hard seam down the middle — white on one side, navy on the
 * other, neither belonging to the page behind it. Two competing surfaces, no
 * hierarchy.
 *
 * Only one thing on this page is an action, so only one thing is raised. The
 * form is a navy card lifted on a shadow and pulled up into the base of the
 * hero photograph; the contact details are not a panel at all, they sit
 * directly on the page like ordinary content. The cyan top rule is the same
 * device .panel already uses elsewhere, so the card reads as part of this
 * theme rather than as an import.
 *
 * The page beneath fades from a faint mist at the top into white, which gives
 * the card something to sit on without drawing an edge anywhere.
 */
.contact-split__wrap {
	padding: 0 var(--gutter) clamp(72px, 9vw, 128px);
	background: linear-gradient( to bottom, var(--c-mist, #eef1f6) 0%, var(--c-white) 48% );
}

.contact-split {
	position: relative;
	z-index: 2;
	display: grid;
	grid-template-columns: minmax(0, 1fr) minmax(0, 1.05fr);
	grid-template-rows: auto 1fr;
	column-gap: clamp(32px, 5vw, 72px);
	align-items: start;
	max-width: var(--container);
	margin: 0 auto;
	box-shadow: none;
	overflow: visible;
}

/* Details are page content, not a surface. */
.contact-split__info {
	grid-column: 1;
	grid-row: 1;
	background: none;
	padding: clamp(36px, 4vw, 56px) 0 0;
}

.contact-split__map {
	grid-column: 1;
	grid-row: 2;
	background: none;
	padding: clamp(20px, 2.5vw, 28px) 0 0;
}

/*
 * The one raised element. The negative margin lifts only this card into the
 * photograph — lifting the whole grid would drag the details up over the
 * building, which is the picture's subject.
 */
.contact-split__form {
	grid-column: 2;
	grid-row: 1 / span 2;
	margin-top: clamp(-104px, -7vw, -56px);
	padding: clamp(28px, 3.4vw, 46px);
	background: var(--c-navy);
	color: var(--c-on-dark);
	border-top: 3px solid var(--c-cyan);
	box-shadow: 0 26px 54px rgba(14, 17, 51, .30), 0 2px 8px rgba(14, 17, 51, .14);
}

@media (max-width: 860px) {
	.contact-split { grid-template-columns: 1fr; grid-template-rows: auto auto auto; }
	.contact-split__info { grid-column: 1; grid-row: 1; padding-top: clamp(28px, 6vw, 40px); }
	.contact-split__form { grid-column: 1; grid-row: 2; margin-top: clamp(28px, 6vw, 40px); }
	.contact-split__map  { grid-column: 1; grid-row: 3; }
}

@media (max-width: 600px) {
	/* No room to overlap gracefully once the card is full width. */
	.contact-split__form { margin-top: 28px; }
}

/* Give the map a little more presence now that it is not boxed in. */
.map-embed { aspect-ratio: 16 / 11; border: 0; }

/*
 * The directions link reads as a link, not as another form field. It sat in a
 * bordered box, which made it look like an input in the details column.
 */
.map-card {
	border: 0;
	border-top: 1px solid var(--c-line-3);
	background: none;
	padding-top: 16px;
}

.map-card__body { padding: 0; }
.map-card strong { color: var(--c-indigo); }
.map-card:hover strong { text-decoration: underline; }

/* ----------------------------------- 28. Anchor landing under sticky header */

/*
 * Every in-page link in the navigation — "Why an ASIC?", "Management Team",
 * "IP Blocks" and the rest — landed with its heading hidden.
 *
 * The header is position: sticky, top: 0 and about 97px tall, but nothing set a
 * scroll offset to match. A browser scrolls an anchor target to y=0, which on
 * this site is underneath the header. The heading you asked for ended up behind
 * the menu and the first thing visible was the paragraph after it, so the jump
 * looked like it had missed.
 *
 * The only scroll-padding present came from WordPress's admin bar (32px), which
 * exists solely for signed-in staff — so a signed-out visitor, i.e. every real
 * visitor, got no offset at all.
 *
 * scroll-margin-top on the targets rather than scroll-padding-top on the root:
 * it survives whichever element ends up being the scroll container, and it can
 * be adjusted for the admin bar via the body class, which a rule on <html>
 * cannot.
 */
:root { --css-header-h: 97px; }

@media (max-width: 782px) {
	:root { --css-header-h: 76px; }
}

/* Harmless on elements that are never linked to: scroll-margin only applies
   when something scrolls the element into view. */
[id] { scroll-margin-top: calc( var(--css-header-h) + 24px ); }

/* Signed-in staff also have the 32px WordPress admin bar above the header. */
body.admin-bar [id] { scroll-margin-top: calc( var(--css-header-h) + 24px + 32px ); }

/*
 * 2026-08-26 — the 24px above is not enough for section headings.
 *
 * Every `.section__title` is preceded by a `.section__eyebrow` — the small
 * line reading "The case for custom", "What we do" and so on — which sits 31px
 * above the heading it labels. The id is on the h2, so the browser scrolls the
 * *heading* clear of the header and leaves the eyebrow behind it: measured on
 * /turnkey-asics/#why-an-asic, the eyebrow landed at y=89 against a 97px
 * header, clipped by 8px. That is the "jumps too far and cuts off the header
 * for that section" report — the jump is short, not long.
 *
 * Why it looked fine when tested: signed-in staff get the admin-bar rule above
 * (97+24+32 = 153px), which happens to clear the eyebrow. Signed-out visitors —
 * i.e. every real visitor — got 121px and saw it clipped. Testing while logged
 * into wp-admin hides the bug completely.
 *
 * 56px = the eyebrow's 23px line box + its 8px margin + the same 24px of air
 * the headings already had. Signed-out now matches what staff always saw.
 */
.section__title[id] { scroll-margin-top: calc( var(--css-header-h) + 56px ); }

body.admin-bar .section__title[id] { scroll-margin-top: calc( var(--css-header-h) + 56px + 32px ); }

/* ------------------------------------------------ 29. Download file cards    */
/*
 * 2026-08-27 — the Standard IC downloads rendered as plain bulleted links and
 * read as unfinished. Each file is now a card: icon, name, and a file-type
 * badge split out of the link text (the name alone is the meaningful part;
 * the type is metadata, so it rides in a badge rather than the sentence).
 */
.dl-list {
	list-style: none;
	margin: 10px 0 0;
	padding: 0;
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(310px, 1fr));
	gap: 10px;
}

.dl-list > .wp-block-group__inner-container { display: contents; }

.dl-list li { margin: 0; }

.dl-list a {
	display: flex;
	align-items: center;
	gap: 10px;
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	border-radius: 8px;
	padding: 13px 14px;
	text-decoration: none;
	color: var(--c-indigo);
	font-weight: 600;
	font-size: 15px;
	line-height: 1.3;
}

.dl-list a::before {
	content: "\2913";           /* ⤓ download arrow */
	font-size: 17px;
	color: var(--c-cyan);
	flex: 0 0 auto;
}

.dl-list a:hover,
.dl-list a:focus-visible {
	border-color: var(--c-cyan);
	color: var(--c-navy);
}

.dl-type {
	margin-left: auto;
	flex: 0 0 auto;
	font-size: 10.5px;
	font-weight: 700;
	letter-spacing: .05em;
	background: var(--c-navy);
	color: var(--c-white);
	border-radius: 4px;
	padding: 2px 7px;
}

/*
 * 2026-08-27 — "layout graphic is blurry and cut off" (Jared H2 + D3).
 * Two different root causes, one remedy pattern:
 *  - Home collage: PNG line art had been re-encoded to JPEG (fuzz) and
 *    cover-cropped into a box of the wrong shape (cut off). Now served as a
 *    lossless PNG with contain, so nothing is cropped or smeared.
 *  - HV/ASIC-expertise die image: the source is 500px despite its filename;
 *    cover was UPscaling then cropping it. contain downsizes instead — sharper
 *    and complete.
 */
.split__figure--contain img {
	height: 420px;
	object-fit: contain;
	background: var(--c-white);
}

.split__media--contain {
	object-fit: contain;
	background: var(--c-white);
}

/*
 * 2026-08-27 — Standard IC round 3 (Mimi): downloads back to the old site's
 * chart layout (Type | File name | Action) but in our design language, with
 * type badges color-coded per convention (PDF red, XLS green, ZIP slate).
 * The card grid (.dl-list) is retired on this page; keep the rules above for
 * any other page still using it.
 */
.dl-table { margin: 14px 0 0; }

.dl-table table {
	width: 100%;
	border-collapse: collapse;
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	border-radius: 8px;
	overflow: hidden;
	font-size: 15px;
}

/*
 * Header row is navy with white ProximaNova per the design handoff's chart
 * (handoff wins on look) — the earlier grey small-caps header read as a
 * wireframe next to it.
 */
.dl-table th {
	text-align: left;
	font-family: var(--f-head);
	font-size: 14px;
	font-weight: 700;
	letter-spacing: .03em;
	color: var(--c-white);
	background: var(--c-navy);
	padding: 12px 16px;
	border-bottom: 1px solid var(--c-line-2);
}

/*
 * Cells are slate, not indigo: with the file name now a real link, indigo
 * belongs to the links alone — a page of indigo text made everything look
 * clickable and nothing stand out.
 */
.dl-table td {
	padding: 11px 14px;
	border-bottom: 1px solid var(--c-line);
	vertical-align: middle;
	color: var(--c-slate);
}

.dl-table tbody tr:last-child td { border-bottom: 0; }
.dl-table tbody tr:hover td { background: var(--c-paper, #f6f7fb); }
.dl-table td:first-child { width: 92px; white-space: nowrap; }

.dl-table .dl-type {
	margin-left: 0;
	display: inline-block;
	font-size: 10.5px;
	font-weight: 700;
	letter-spacing: .05em;
	color: var(--c-white);
	border-radius: 4px;
	padding: 3px 8px;
}

.dl-type--pdf { background: #B3261E; }
.dl-type--xls { background: #1E7A46; }
.dl-type--zip { background: #47506E; }
.dl-type--txt { background: #6B7086; }
.dl-type--other { background: var(--c-navy); }

.dl-get {
	font-weight: 600;
	color: var(--c-cyan-active, #0B6F7B);
	text-decoration: none;
}

.dl-get:hover,
.dl-get:focus-visible { text-decoration: underline; color: var(--c-navy); }

/* The golden 555 visual as a content image: native-ish size, centered */
.sic-visual { max-width: 560px; margin: 26px auto 0; }
.sic-visual img { width: 100%; height: auto; border-radius: 10px; }

/*
 * 2026-08-27 — Turnkey rebuild visual layer (Jared's missing-info rejection).
 * All content visible, no tabs; these classes carry the proof band, section
 * imagery, test-floor video/photos and the static testimonial grid.
 */
.tk-markets {
	text-align: center;
	font-size: 14px;
	font-weight: 600;
	letter-spacing: .08em;
	text-transform: uppercase;
	color: var(--c-cyan-active, #0B6F7B);
	margin: 0 0 18px;
}

.tk-stats { display: grid; grid-template-columns: repeat(4, 1fr); gap: 14px; }
.tk-stats > .wp-block-group__inner-container { display: contents; }
.tk-stat {
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	border-radius: 10px;
	padding: 18px 16px;
	text-align: center;
}
.tk-stat__n { font-size: 24px; font-weight: 700; letter-spacing: -.02em; color: var(--c-navy); margin: 0; }
.tk-stat__l { font-size: 12.5px; color: var(--c-indigo); margin: 4px 0 0; }
@media (max-width: 760px) { .tk-stats { grid-template-columns: repeat(2, 1fr); } }

.tk-figure { margin: 22px 0; }
.tk-figure img { width: 100%; height: auto; max-height: 420px; object-fit: cover; border-radius: 10px; }
.tk-figure.size-large img[src*="die-layout"] { object-fit: contain; background: var(--c-white); }

.tk-video { margin: 8px 0 18px; }
.tk-video video { width: 100%; border-radius: 10px; }

.tk-photos { display: grid; grid-template-columns: repeat(3, 1fr); gap: 12px; margin: 0 0 22px; }
.tk-photos > .wp-block-group__inner-container { display: contents; }
.tk-photos figure { margin: 0; }
.tk-photos img { width: 100%; height: 170px; object-fit: cover; border-radius: 8px; }
@media (max-width: 700px) { .tk-photos { grid-template-columns: 1fr; } .tk-photos img { height: auto; } }

.tk-quotes { display: grid; grid-template-columns: repeat(3, 1fr); gap: 14px; }
.tk-quotes > .wp-block-group__inner-container { display: contents; }
.tk-quote {
	background: var(--c-white);
	border: 1px solid var(--c-line-2);
	border-radius: 10px;
	padding: 20px 18px;
	font-size: 14.5px;
	line-height: 1.6;
}
.tk-quote__who { margin-top: 12px; font-size: 12.5px; font-weight: 600; color: var(--c-cyan-active, #0B6F7B); }
@media (max-width: 860px) { .tk-quotes { grid-template-columns: 1fr; } }

/*
 * 2026-08-27 — Standard IC round 4 (Mimi: "fix the damn padding"). The 820px
 * prose measure is right for paragraphs but was strangling the download
 * charts, leaving a void on the right. On this template the body opens up for
 * tables/headings while paragraphs keep their readable measure. File names
 * are links too — same target as the Download action.
 */
body.page-template-template-products .section__body { max-width: 1060px; }
body.page-template-template-products .section__body > p { max-width: 820px; }

.dl-table td { padding: 13px 16px; }
.dl-table th { padding: 11px 16px; }

/*
 * Round 6 (Mimi): one link per file, not two. The Action column is gone; the
 * file name is the download link and carries the arrow. The arrow lives in CSS
 * (::after) so screen readers and search engines read only the file name.
 */
.dl-name {
	color: var(--c-indigo);
	font-weight: 600;
	text-decoration: none;
}
.dl-name:hover,
.dl-name:focus-visible { color: var(--c-navy); text-decoration: underline; }

/* Slightly larger and half a space further out (Mimi round 10) — visible on
   mobile without reading as part of the file name. */
.dl-name::after {
	content: "\2913";           /* ⤓ download arrow */
	display: inline-block;
	margin-left: .5em;
	font-size: 1.2em;
	line-height: 1;
	vertical-align: -.1em;
	color: var(--c-cyan-active, #0B6F7B);
}

/*
 * Round 7 (Mimi: "it looks off"): sizes sat inline after the names, so every
 * row trailed into empty space. They are their own right-aligned column now —
 * Type | File name | Size — which squares the chart up like the old site's.
 */
.dl-table td:last-child,
.dl-table th:last-child {
	width: 90px;
	text-align: right;
	white-space: nowrap;
}

.dl-table td:last-child { font-variant-numeric: tabular-nums; }

/*
 * 2026-08-27 — Standard IC round 5 (Mimi: bulky type, link-the-words, golden
 * award). Eyebrow + shorter H2 per the handoff (the combined "CSS555 — long
 * name" bolded line was the bulk); paragraphs open to the handoff's 1.75
 * leading on this page; the Golden Mousetrap award badge returns to the
 * CSS555 section (it was on the old site but never made the handoff); the
 * Download arrow moves into CSS so the markup stops carrying a ⬇ character.
 */
body.page-template-template-products .section__body p { line-height: 1.75; }

.sic-eyebrow {
	margin: 0 0 6px;
	font-size: var(--fs-meta);
	font-weight: 700;
	letter-spacing: 2px;
	text-transform: uppercase;
	color: var(--c-indigo);
}

.dl-get::before { content: "\2913\00a0"; }

/*
 * Round 9 (Mimi): the badge sits beside the CSS555 heading in the section's
 * empty right half, not under it — it is the first child of the container so
 * the eyebrow, title and copy wrap to its left. Section is white now, so the
 * GIF's white background disappears into it.
 */
/*
 * Round 12 (Mimi): right side after all — badge floats top-right, its top on
 * the CSS555 label row, title and copy to its left. Only CSS555 has an award;
 * the label (eyebrow) treatment itself is on every product section already.
 */
/* Round 13: nudged up a touch (-10px / -6px mobile) so the badge pins to the
   section corner instead of hanging into the paragraph. */
.sic-award {
	float: right;
	width: 150px;
	margin: -10px 0 14px 26px;
}

/* multiply lets the GIF's baked-in white box read as transparent, so the
   badge sits directly on the white or tinted band with no sticker edge. */
.sic-award img { width: 100%; height: auto; mix-blend-mode: multiply; }

@media (max-width: 700px) {
	.sic-award { width: 104px; margin: -6px 0 10px 16px; }
}

/* ------------------------------------------------------- 24. Turnkey tabs    */

/*
 * 2026-08-27 — tabs restored at Mimi's direction, superseding the same-day
 * no-tabs layout (Jared's missing-info rejection). Both concerns hold: the
 * panels and their headings stay in the DOM for crawlers and no-JS readers
 * (tabs.js only toggles [hidden]), while visitors click through the way the
 * old site worked. Styling follows the handoff's tab spec: centered row,
 * 3px cyan underline on the active tab, cyan 01–05 numbers on Design Flow.
 */
.tabs__list {
	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	gap: 8px 34px;
	margin: 0 0 40px;
	border-bottom: 1px solid var(--c-line);
}

.tabs__tab {
	appearance: none;
	background: none;
	border: 0;
	border-bottom: 3px solid transparent;
	margin-bottom: -1px;
	padding: 0 2px 15px;
	cursor: pointer;
	font-family: var(--f-head);
	font-size: var(--fs-body-sm);
	letter-spacing: .2px;
	color: var(--c-slate);
}

.tabs__tab:hover { color: var(--c-navy); }

.tabs__tab[aria-selected="true"] {
	border-bottom-color: var(--c-cyan);
	color: var(--c-navy);
}

.tabs__num {
	margin-right: 9px;
	font-size: var(--fs-meta);
	color: var(--c-cyan-active);
}

.tabs__tab[aria-selected="true"] .tabs__num { color: var(--c-cyan-active); }

.tabs__panel[hidden] { display: none; }

/*
 * Panel prose is centered rather than pinned left — the section titles and the
 * tab row above it are centered, and a left-pinned 820px column inside a
 * 1280px container was reported (correctly) as "so much space on the right".
 */
.tabs__panel {
	max-width: 960px;
	margin: 0 auto;
}

/* The label heading keeps ranking and anchor duty; the button carries the
   visible label once tabs are built. */
.is-tabbed .tabs__title {
	position: absolute;
	width: 1px;
	height: 1px;
	padding: 0;
	margin: -1px;
	overflow: hidden;
	clip: rect(0 0 0 0);
	white-space: nowrap;
	border: 0;
}

.tabs__panel .section__body { max-width: none; }

.tabs__panel .panels,
.tabs__panel .tk-photos,
.step__gate { clear: both; }

/* Small source photos (the 300px design-flow set) sit beside the text instead
   of stretching blurry across the column. */
.tk-figure--side {
	float: right;
	width: min(300px, 42%);
	margin: 4px 0 18px 26px;
}

.tk-figure--side img {
	width: 100%;
	height: auto;
	max-height: none;
	border: 1px solid var(--c-line-2);
	border-radius: 10px;
}

@media (max-width: 700px) {
	.tk-figure--side { float: none; width: 100%; margin: 16px 0; }
}

/* Die-layout art is taller than wide — crop would slice it. */
.split__figure--contain img { object-fit: contain; background: var(--c-white); }

.section--dark .checklist li { color: var(--c-on-dark-strong); }

/* Engagement accordions — handoff spec: hairline boxes on the navy band,
   Full Turnkey open by default (set in the editor, not here). */
.section--dark .wp-block-details {
	border: 1px solid var(--c-on-dark-edge);
	background: rgba(255, 255, 255, .05);
	margin: 0 0 8px;
}

.section--dark .wp-block-details summary {
	cursor: pointer;
	list-style: none;
	padding: 20px 26px;
	font-family: var(--f-head);
	font-size: var(--fs-h3);
	color: var(--c-white);
}

.section--dark .wp-block-details summary::-webkit-details-marker { display: none; }

.section--dark .wp-block-details summary::before {
	content: '\2014';
	margin-right: 16px;
	color: var(--c-cyan);
}

.section--dark .wp-block-details summary:hover { background: rgba(112, 204, 219, .1); }

.section--dark .wp-block-details > *:not(summary) {
	margin: 0 26px 20px 58px;
	color: var(--c-on-dark-strong);
}

.section--dark .wp-block-details .checklist { max-width: none; }

/*
 * 2026-08-27 — Turnkey finalization (Mimi): make the development CYCLE read
 * as a cycle again, and fit the phase steps' full restored text.
 */

/* Phase-gate diagram: horizontal on desktop, vertical under 768px */
.tk-flow-diagram { margin: 6px 0 26px; }
.tk-flow-diagram svg { width: 100%; height: auto; display: block; }
.tk-flow-diagram .tk-svg-v { display: none; max-width: 360px; margin: 0 auto; }
@media (max-width: 767px) {
	.tk-flow-diagram .tk-svg-h { display: none; }
	.tk-flow-diagram .tk-svg-v { display: block; }
}

/* The flow steps carry full paragraphs + deliverables now, so the compact
 * card grid reads as clutter. On this page they stack as one ordered column. */
body.page-template-template-turnkey .steps {
	grid-template-columns: 1fr;
	max-width: 940px;
}
body.page-template-template-turnkey .step__list { columns: 2; column-gap: 28px; }
@media (max-width: 700px) {
	body.page-template-template-turnkey .step__list { columns: 1; }
}
body.page-template-template-turnkey .step__who {
	font-size: 12px;
	font-weight: 700;
	letter-spacing: .08em;
	text-transform: uppercase;
	color: #7FE3EC;
	margin: 14px 0 4px;
}
body.page-template-template-turnkey .step__gate {
	display: inline-block;
	margin-top: 14px;
	padding: 6px 12px;
	border-radius: 20px;
	background: rgba(35, 185, 199, .18);
	border: 1px solid #23B9C7;
	color: #7FE3EC;
	font-size: 13px;
	font-weight: 700;
}

/* The hand-drawn schematic is a B/W sketch; tint it into the brand's navy
 * so it doesn't sit gray against the palette (Mimi's ask). */
.tk-figure--tint img {
	filter: grayscale(1) sepia(1) hue-rotate(175deg) saturate(2.4) brightness(.92);
}

/* Deliverables fold into a native disclosure per phase (Mimi: page too busy).
 * <details> keeps the lists in the DOM, so search engines index them fully —
 * unlike the old site's script-driven tabs. Nothing is lost, just folded. */
.step-more {
	margin: 14px 0 4px;
	border: 1px solid var(--c-on-dark-edge, rgba(255,255,255,.18));
	border-radius: 8px;
	background: rgba(255, 255, 255, .04);
}
.step-more summary {
	cursor: pointer;
	list-style: none;
	padding: 11px 14px;
	font-size: 13.5px;
	font-weight: 700;
	letter-spacing: .04em;
	color: #7FE3EC;
}
.step-more summary::-webkit-details-marker { display: none; }
.step-more summary::before { content: "\25B8\00a0"; }
.step-more[open] summary::before { content: "\25BE\00a0"; }
.step-more[open] summary { border-bottom: 1px solid var(--c-on-dark-edge, rgba(255,255,255,.18)); }
.step-more__body { padding: 4px 16px 14px; }

/*
 * 2026-08-27 — Mimi's mobile pass on Turnkey.
 * 1. The section jump-nav (.subnav) becomes sticky, hiding on scroll-down and
 *    returning on scroll-up (JS adds .subnav--away), so mid-page readers can
 *    always jump without scrolling back to the top. Site-wide: every page
 *    using the component behaves the same.
 * 2. The proof band matches the site's section language: tinted background,
 *    shadowed cards, cyan-accented numbers — not bare white boxes.
 */
.subnav {
	position: sticky;
	top: var(--css-header-h, 64px);
	z-index: 40; /* below .site-header (60) and its menu panel — the jump-nav must never cover the hamburger */
	transition: transform .25s ease;
}
.subnav--away { transform: translateY(calc(-110% - var(--css-header-h, 64px))); }

/*
 * 2026-08-28 — Mimi: the IC Design Expertise and Market Expertise pages keep
 * their jump-nav where it sits, in the flow. Those bars switch between sibling
 * pages rather than jumping around one long page, so there is nothing to return
 * to mid-scroll and a following bar would only cost screen height.
 *
 * relative, not static: the ::after fade edge on narrow screens is positioned
 * against this element. nav.js skips this variant, so .subnav--away is never
 * applied to it and it cannot slide out of the flow.
 */
.subnav--static {
	position: relative;
	top: auto;
	transform: none;
	transition: none;
}

.tk-stat {
	box-shadow: 0 1px 2px rgba(14, 17, 51, .06), 0 6px 18px rgba(14, 17, 51, .07);
	border-top: 3px solid var(--c-cyan);
}
.tk-stat__n { color: var(--c-navy); }
.tk-stats { margin-top: 10px; }

/* Light-section fold (same disclosure pattern as .step-more, light palette).
 * The overview row in the mobile menu gets a subtle emphasis. */
.fold {
	margin: 14px 0;
	border: 1px solid var(--c-line-2);
	border-radius: 8px;
	background: var(--c-white);
}
.fold summary {
	cursor: pointer;
	list-style: none;
	padding: 11px 14px;
	font-size: 13.5px;
	font-weight: 700;
	letter-spacing: .04em;
	color: var(--c-cyan-active, #0B6F7B);
}
.fold summary::-webkit-details-marker { display: none; }
.fold summary::before { content: "\25B8\00a0"; }
.fold[open] summary::before { content: "\25BE\00a0"; }
.fold[open] summary { border-bottom: 1px solid var(--c-line-2); }
.fold__body { padding: 6px 16px 14px; }
.section--dark .fold {
	background: rgba(255, 255, 255, .04);
	border-color: var(--c-on-dark-edge, rgba(255,255,255,.18));
}
.section--dark .fold summary { color: #7FE3EC; }
.section--dark .fold[open] summary { border-bottom-color: var(--c-on-dark-edge, rgba(255,255,255,.18)); }
.panel .fold { margin: 8px 0 0; }

/* .site-nav__link--overview retired 2026-08-27 — replaced by clickable group labels */

/* Reduced-height package/testing panels now that lists fold */

/*
 * 2026-08-27 — mobile menu usability pass (Mimi).
 * Standard pattern: the section LABEL navigates, the +/- mark toggles.
 * The open panel scrolls within the viewport (it couldn't before), and
 * only one section stays open at a time (accordion, via nav.js).
 */
.site-nav__group-summary {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 8px;
}
.site-nav__group-link {
	color: inherit;
	text-decoration: none;
	flex: 1;
	padding: 6px 0;
}
.site-nav__group-mark {
	flex: 0 0 auto;
	min-width: 44px;
	min-height: 44px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	cursor: pointer;
}
.site-nav--mobile.is-open {
	max-height: calc(100dvh - var(--css-header-h, 76px));
	overflow-y: auto;
	-webkit-overflow-scrolling: touch;
	overscroll-behavior: contain;
}

/*
 * 2026-08-27 — Standard IC round 11 (Mimi: "desktop not aligned right, mobile
 * perfect"). Diagnosis: every column WAS aligned; the problem was the table
 * stretching the full 1060px body width, which inflated the File name column
 * to 776px and left ~400px of dead space before the right-aligned Size. On a
 * phone the columns are narrow so the gap never appears — hence "mobile
 * perfect". Capping the chart keeps the three columns visually grouped, and
 * keeps all five download charts identical in width instead of each sizing to
 * its own longest filename.
 */
.dl-table { max-width: 720px; }

/*
 * File names drop from 600 to 500. Every row bold read as a wall of heavy
 * text with nothing standing out; the badges and the cyan arrow already mark
 * these as files and links, so weight is doing no work here. Bold now belongs
 * to the header row alone, which is what makes a chart scannable.
 */
.dl-name { font-weight: 500; }

/*
 * 2026-08-27 — Standard IC round 15. Mimi, and she is right: "EVERYTHING ON
 * SITE SHOULD AUTO ADJUST TO WHATEVER SCREEN."
 *
 * This page had accumulated FOUR competing fixed widths, each added to fix the
 * symptom the previous one caused:
 *     .section__body            820px   (global)
 *     .section__body            1060px  (this template, round 4)
 *     .section__body > p        820px   (this template, round 4)
 *     .dl-table                 720px   (round 11, to close a gap in the chart)
 *     everything                720px   (round 14 — mine, to force alignment)
 * Round 14 did align them, by pinning the whole page to 720px. On a 1440px
 * screen that left the content sitting in the left half with the right half
 * empty, while every other page on the site spans the full 1216px. Picking a
 * number was the mistake; the page should follow the screen.
 *
 * So: no fixed column on this template at all. Every element — eyebrow,
 * heading, prose, download chart and the floated award — takes its width from
 * .container, which is already fluid (100% of the viewport, capped at 1280 and
 * shrinking freely below that). One shared edge at EVERY screen size, because
 * they are all measured from the same parent instead of from five constants.
 */
body.page-template-template-products .sic-eyebrow,
body.page-template-template-products .section__title,
body.page-template-template-products .section__body,
body.page-template-template-products .section__body > p,
body.page-template-template-products .dl-table { max-width: none; }

body.page-template-template-products .sic-award { margin-right: 0; }