/*
 * The Aditya Blog stylesheet.
 *
 * GENERATED — do not edit this file. It is copied from
 * `preview/preview.css` by `preview/sync-site-css.js`, so that the live
 * site and the writing desk's preview are rendered by the same rules
 * rather than by two that drift.
 *
 * Edit the source, then run:  node preview/sync-site-css.js
 */

/*
 * Static preview stylesheet — "Ink & Paper".
 *
 * Tokens copied from theme/aditya-blog/theme.json; the @font-face rules point
 * at the theme's real self-hosted woff2 files. No WordPress, no PHP — this
 * shows the design system exactly as the theme will render it.
 */

@font-face {
	font-family: "Bricolage Grotesque";
	src: url("../fonts/bricolage.woff2") format("woff2");
	font-weight: 400 800;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: "Source Serif 4";
	src: url("../fonts/source-serif.woff2") format("woff2");
	font-weight: 400 700;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: "Source Serif 4";
	src: url("../fonts/source-serif-italic.woff2") format("woff2");
	font-weight: 400;
	font-style: italic;
	font-display: swap;
}

:root {
	/*
	 * --- Colour -------------------------------------------------------
	 *
	 * Every colour is a ROLE, taken from whichever style is switched on, with
	 * the Ink & Paper value as the fallback.
	 *
	 * The fallback is what makes this work in both places at once. Opened as a
	 * file with no WordPress anywhere near it — the prototype, the writing
	 * desk's preview — the presets do not exist and the fallback applies, so
	 * the design is exactly as drawn. Served by WordPress, the preset wins, and
	 * choosing a different style under Appearance -> Editor -> Styles repaints
	 * the whole site without touching a line of this file.
	 *
	 * Without this indirection a style variation would change theme.json and
	 * change nothing anyone could see, because these hard-coded hexes would
	 * still be sitting on top of it.
	 */
	--paper: var(--wp--preset--color--base, #FAF7F2);
	--paper-deep: var(--wp--preset--color--surface, #F1EADE);
	--ink: var(--wp--preset--color--contrast, #121212);
	--ink-faded: var(--wp--preset--color--muted, #57524A);
	--vermillion: var(--wp--preset--color--primary, #C4260E);
	--vermillion-wash: var(--wp--preset--color--primary-soft, #F7E2DC);
	--rule: var(--wp--preset--color--border, #D6CCBC);
	--marker: var(--wp--preset--color--highlight, #F6E7A8);

	/* --- Type, on the same terms --- */
	/* `--sans` and `--serif` both go through `--wp--custom--*` FIRST, and this
	   is not belt-and-braces — it is the only route there is. WordPress
	   strips `settings.typography.fontFamilies` out of user global styles
	   when a variation is applied, so a variation cannot repoint the `sans`
	   preset. Worse, it fails SILENTLY in a way that looks fine: the
	   variation sets `styles.typography.fontFamily` and WordPress duly
	   writes `body { font-family: <the new face> }` — and then THIS file's
	   own `body { font-family: var(--sans) }` loads after it and wins. The
	   page renders in the old face while every stylesheet involved looks
	   correct. Caught on 2026-09-28 by measuring `getComputedStyle`, not by
	   looking: two geometric sans faces are near enough in a screenshot. */
	--sans: var(--wp--custom--sans, var(--wp--preset--font-family--sans, "Bricolage Grotesque", "Helvetica Neue", Helvetica, Arial, sans-serif));
	/* `--wp--custom--serif` is the escape hatch a variation needs and did not
	   have: WordPress STRIPS settings.typography.fontFamilies out of user global
	   styles when a variation is applied — font families are the Font Library's
	   business at user origin — so a variation cannot repoint the `serif` preset
	   itself. settings.custom DOES survive. A variation whose source has no serif
	   in it at all (Usabilio Live is one) sets this to a sans preset and all six
	   serif passages follow. */
	--serif: var(--wp--custom--serif, var(--wp--preset--font-family--serif, "Source Serif 4", Charter, Georgia, serif));
	--mono: var(--wp--preset--font-family--mono, ui-monospace, SFMono-Regular, Menlo, Consolas, monospace);

	/* The display face. Headings used `--sans` directly until 2026-09-28, which
	   meant a variation could change the body face and the headings followed it
	   whether or not that was wanted — a theme setting its headings in a second
	   family, which is most of them, had no way to say so. Unset, `--display`
	   falls back to `--sans` and nothing changes. */
	--display: var(--wp--custom--display, var(--sans));
	--display-weight: var(--wp--custom--display-weight, 800);
	--display-tracking: var(--wp--custom--display-tracking, -0.035em);
	--display-leading: var(--wp--custom--display-leading, 1.02);

	/* Sizes, measure and spacing go through the presets for the same reason the
	   colours do, and they did NOT until 2026-09-28: a variation could declare a
	   whole type scale in `settings.typography.fontSizes` and this file would
	   quietly keep drawing the old one. Each fallback is the previous hard-coded
	   value, so the default look is unchanged to the pixel. A variation that
	   wants to stay mobile-first writes its sizes as clamp() — a flat px size
	   here is the same size on a phone. */
	--fs-small: var(--wp--preset--font-size--small, 0.8125rem);
	--fs-medium: var(--wp--preset--font-size--medium, clamp(1.0625rem, 1rem + 0.2vw, 1.1875rem));
	--fs-large: var(--wp--preset--font-size--large, clamp(1.1875rem, 1.1rem + 0.35vw, 1.375rem));
	--fs-x-large: var(--wp--preset--font-size--x-large, clamp(1.5rem, 1.15rem + 1.5vw, 2.125rem));
	--fs-xx-large: var(--wp--preset--font-size--xx-large, clamp(2.125rem, 1.4rem + 3vw, 3.25rem));
	--fs-huge: var(--wp--preset--font-size--huge, clamp(2.75rem, 1.2rem + 6.5vw, 5.5rem));

	/* --- Spacing --- */
	--sp-20: var(--wp--preset--spacing--20, clamp(0.75rem, 1.5vw, 1rem));
	--sp-30: var(--wp--preset--spacing--30, clamp(1rem, 2vw, 1.5rem));
	--sp-40: var(--wp--preset--spacing--40, clamp(1.75rem, 3.5vw, 2.5rem));
	--sp-50: var(--wp--preset--spacing--50, clamp(2.5rem, 6vw, 4rem));
	--sp-60: var(--wp--preset--spacing--60, clamp(3.5rem, 9vw, 6.5rem));

	/* The block editor's button radius lives in `styles.elements.button` and
	   only ever reaches `.wp-element-button`. `.btn` is this design's own
	   class and ignored it, so a variation could declare a 28px pill and
	   every button the theme actually draws stayed square. */
	--btn-radius: var(--wp--custom--button-radius, 0);

	/*
	 * The reading measure, in one place.
	 *
	 * `.entry` capped itself at 66ch and the post's hero figure capped itself at
	 * nothing, so a post showed a 1052px picture above 813px of text off the same
	 * left edge — a 239px overhang down the right. Onkar saw it on 2026-09-28.
	 *
	 * It was briefly `50.75rem`, capping the PICTURE down to the text. Onkar's
	 * call was the other way round — *"insted of making image short make the
	 * text more width"* — so both now run the full width of the wrap and the
	 * edges still line up, which was the point.
	 *
	 * **This is wider than the house reading rule.** At 1052px in 18px DM Sans a
	 * line is roughly 105 characters; `CLAUDE.md` asks for 65–75. It is a
	 * deliberate, instructed choice, and one value reverses it: `50.75rem` puts
	 * the measure back at 66 characters and the picture back in step with it.
	 *
	 * Whatever the value, it must NOT be expressed in `ch`. That unit is the
	 * width of a "0" in the ELEMENT'S OWN font, so a single shared `66ch` token
	 * resolved to 813px inside `.entry`, which reads at 18px, and 722px on the
	 * figure, which inherits the 16px body — two widths from one variable, and
	 * it looked almost right, which is the worst kind of wrong.
	 */
	--measure: 100%;

	--content: var(--wp--style--global--content-size, 720px);
	--wide: var(--wp--style--global--wide-size, 1240px);
}

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

body {
	margin: 0;
	background: var(--paper);
	color: var(--ink);
	font-family: var(--sans);
	font-size: var(--fs-medium);
	line-height: 1.6;
	-webkit-font-smoothing: antialiased;
	font-synthesis-weight: none;
}

h1, h2, h3, h4 {
	margin: 0;
	font-family: var(--display);
	font-weight: var(--display-weight);
	line-height: var(--display-leading);
	letter-spacing: var(--display-tracking);
}

h1 { font-size: var(--fs-huge); }
h2 { font-size: var(--fs-xx-large); line-height: 1.05; }
h3 { font-size: var(--fs-x-large); line-height: 1.1; }

p { margin: 0 0 1em; }

a { color: var(--ink); text-decoration: underline; text-underline-offset: 3px; }
a:hover { color: var(--vermillion); }
a:focus-visible { outline: 2px solid var(--vermillion); outline-offset: 3px; }

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

.wrap { max-width: var(--content); margin-inline: auto; padding-inline: var(--sp-30); }
.wrap--wide { max-width: var(--wide); }

/*
 * The masthead meets the page.
 *
 * WordPress gives `.wp-site-blocks > * + *` a `margin-block-start` of
 * `--wp--style--block-gap`, which put **24px between the header template part
 * and `main`**. Nothing here asked for it and nobody could see it: for as long
 * as whatever sat under the bar was white, the gap was white too. The day the
 * hero became a dark video stage it turned into a white stripe across the top
 * of the site — which is how it was finally noticed, on 2026-09-28, rather
 * than by anything in the CSS.
 *
 * The bar is chrome. Content starts directly beneath it, and every template
 * already opens with its own padding, so there is nothing to replace.
 */
.wp-site-blocks > main { margin-block-start: 0; }

/*
 * Same cause, one level down. Inside `.hero-stage` the backdrop and the
 * writing are siblings, so the block gap pushed the hero's text another 24px
 * down its own video. The stage's padding sets that rhythm; the gap is noise.
 */
.hero-stage > * + * { margin-block-start: 0; }

/*
 * A wrap inside a wrap contributes nothing.
 *
 * Measured 2026-09-27: the chips rail on /writing/ started 24px to the right of
 * the page heading, because a pattern that brings its own `.wrap--wide` was
 * dropped inside the template's `.wrap--wide` and paid the 24px gutter twice.
 * It is invisible on its own and unmistakable next to anything that did not
 * nest — which is exactly how a page ends up with three left edges.
 *
 * Stated once here rather than policed in every template: the OUTERMOST wrap
 * owns the measure and the gutter, and anything nested inside it fills what it
 * was given.
 */
.wrap .wrap {
	max-width: none;
	padding-inline: 0;
}

/*
 * ...unless it is inside a dropdown panel, which is the one exception and has
 * to be stated here or the rule above is wrong twice over.
 *
 * A masthead panel is `position: absolute` against the BAR, so although it sits
 * inside `.sections__inner` in the markup, it is not laid out inside it: it
 * spans the whole window. Its inner wrap is therefore a top-level wrap again,
 * and stripping its measure and its gutter — which the rule above did from
 * 14:05 to 15:05 on 2026-09-27 — ran both dropdowns edge to edge with their
 * first link touching the left of the screen. Measured: the panel's inner wrap
 * was L0 R1407 with `max-width: none` and no padding, where it should be
 * L108 R1332 at 1240 wide.
 *
 * The plugin's tools panel is named here too. It is the same mechanism in
 * somebody else's file, and `menu.css` cannot know what this theme does to
 * nested wraps.
 */
.sections__panel .wrap,
.adb-menu__panel .wrap {
	max-width: var(--content);
	margin-inline: auto;
	padding-inline: var(--sp-30);
}

.sections__panel .wrap--wide,
.adb-menu__panel .wrap--wide {
	max-width: var(--wide);
}

.muted { color: var(--ink-faded); }
.small { font-size: var(--fs-small); }

/* Uppercase micro-label: the workhorse of this design. */
.label {
	font-family: var(--sans);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.18em;
	text-transform: uppercase;
	margin: 0;
	color: var(--ink-faded);
}

.label--accent { color: var(--vermillion); }

.rule-thick { border: 0; border-top: 2px solid var(--ink); margin: 0; }
.rule-thin { border: 0; border-top: 1px solid var(--rule); margin: 0; }

/*
 * A note on `--sans` vs `--display`, because this file used to need only one
 * of them. Until 2026-09-28 the theme's sans WAS its display face, so every
 * title below simply said `var(--sans)` and looked right. Under a variation
 * that sets a separate heading family — Usabilio Live does — those titles
 * silently fell back to the BODY face while `h1`-`h4` moved to the display
 * one, leaving two faces doing the same job on the same page. The five that
 * are genuinely headings now say `var(--display)`; everything that is a
 * label, a button, a byline or a table stays on `--sans`, which is what it
 * always meant. The masthead is deliberately untouched.
 */

/* --- Buttons ------------------------------------------------------------- */
.btn {
	display: inline-flex;
	align-items: center;
	min-height: 44px;
	padding: 0.85rem 1.5rem;
	border: 1px solid var(--ink);
	border-radius: var(--btn-radius);
	background: var(--ink);
	color: var(--paper);
	font-family: var(--sans);
	font-size: var(--fs-small);
	font-weight: 700;
	letter-spacing: 0.06em;
	text-transform: uppercase;
	text-decoration: none;
	cursor: pointer;
	transition: background-color 150ms ease, color 150ms ease, border-color 150ms ease;
}

.btn:hover { background: var(--vermillion); border-color: var(--vermillion); color: var(--paper); }

.btn--outline { background: transparent; color: var(--ink); }
.btn--outline:hover { background: var(--ink); border-color: var(--ink); color: var(--paper); }

.btn--small { padding: 0.7rem 1.1rem; font-size: 0.6875rem; letter-spacing: 0.12em; }

.btns { display: flex; flex-wrap: wrap; gap: 0.5rem; }

/* --- Masthead ------------------------------------------------------------ */
.topbar {
	border-bottom: 2px solid var(--ink);
	background: var(--paper);
}

.topbar__inner {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: var(--sp-30);
	flex-wrap: wrap;
	padding-block: 0.75rem;
}

.wordmark {
	font-family: var(--sans);
	font-size: 1.0625rem;
	font-weight: 800;
	letter-spacing: -0.02em;
	text-transform: uppercase;
	text-decoration: none;
	color: var(--ink);
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	min-height: 44px;
}

.wordmark span { color: var(--vermillion); }

.nav { display: flex; align-items: center; gap: var(--sp-30); flex-wrap: wrap; }

.nav a {
	position: relative;
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	text-decoration: none;
	color: var(--ink);
	min-height: 44px;
	display: inline-flex;
	align-items: center;
}

.nav a::after {
	content: "";
	position: absolute;
	left: 0;
	right: 100%;
	bottom: 0.7rem;
	height: 2px;
	background: var(--vermillion);
	transition: right 180ms ease;
}

.nav a:hover::after { right: 0; }
.nav a:hover { color: var(--ink); }

.icon-btn {
	width: 44px;
	height: 44px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid var(--ink);
	border-radius: 0;
	background: transparent;
	color: var(--ink);
	cursor: pointer;
}

.icon-btn:hover { background: var(--ink); color: var(--paper); }

/* --- Sections bar --------------------------------------------------------
 *
 * The category tree, in the masthead. Eight hubs on an ink band, the whole of
 * it behind "All sections"; `inc/sections.php` builds the markup from the
 * taxonomy.
 *
 * Why an INK band and not a third pale row: the masthead already has two light
 * rows (the mark, then the tools strip). A third would read as one 160px slab
 * of cream with links floating in it. The ink band gives the page a spine, and
 * it is the one place on the site where the navigation is the loudest thing —
 * which is exactly right for a directory of fifteen sections.
 *
 * NAMESPACE: `sections*`. Not `nav*` (the masthead's own links), not `adb-nav*`
 * or `adb-menu*` (the plugin's tools bar, which loads on the very same page).
 *
 * Contrast, measured rather than eyeballed: paper #FAF7F2 on ink #121212 is
 * 16.4:1. Vermillion #C4260E on ink is 2.8:1 and therefore NEVER carries text
 * here — it is the underline and the current-section mark only.
 */
.sections {
	position: relative;
	z-index: 50;
	background: var(--ink);
	border-bottom: 2px solid var(--ink);
}

/*
 * It WRAPS. It does not scroll sideways, and that is a correctness decision
 * rather than a taste one.
 *
 * This row used to be `overflow-x: auto`, which reads well on a phone — until
 * a panel opens. A dropdown is `position: absolute` against `.sections`, and
 * `.sections` is OUTSIDE the scroller, but the panel is a descendant of the
 * scrolled content: measured at 700px, the tools panel came out at L1002 W588,
 * i.e. 900px of it off the right of a 667px screen. offsetParent said
 * `nav.sections` the whole time, which is exactly what makes this one hard to
 * see by reading the CSS.
 *
 * So there is no scroller at any width. Between about 1100 and 1240 the row
 * wraps to two lines; below 900 only the two "All …" menus remain (see the
 * media query at the end of this block), which is one short line and the whole
 * tree one tap away.
 */
.sections__inner {
	display: flex;
	align-items: center;
	flex-wrap: wrap;
	row-gap: 0;
	/*
	 * 0.8rem, not `--sp-30`, and not the 1.05rem it was until 2026-09-28.
	 *
	 * This row carries BOTH navigations, so it has always been the tightest
	 * thing on the page. It was measured at 1,245px inside a 1,240px wrap —
	 * five over, clipping "All PDF tools" — and 1.05rem bought it ~25px of
	 * slack. That was slack against a **1,240px** wrap.
	 *
	 * The Usabilio Live variation sets his `wideSize`, which is **1,100px**.
	 * The wrap lost 140px, the 25px of slack went with it, and the toolkit
	 * half wrapped onto a second line — the bar Onkar saw as "2 lined". The
	 * band is one line by design and the design did not change; the box it
	 * lives in got smaller.
	 *
	 * 0.8rem here plus 0.10em of tracking on `.sections__link` gives back
	 * ~58px, so the row fits 1,100px with room rather than by a hair. Measured
	 * after the change: content 1,021px in 1,100px at 1440 / 1366 / 1280,
	 * all one line.
	 */
	column-gap: 0.8rem;
}

.sections__link {
	position: relative;
	display: inline-flex;
	align-items: center;
	gap: 0.35rem;
	min-height: 44px;
	padding-block: 0.25rem;
	font-family: var(--sans);
	font-size: 0.6875rem;
	font-weight: 700;
	/* 0.10em, down from 0.14em on 2026-09-28. DM Sans sets wider than the face
	   this bar was drawn in, and his wide measure is 140px narrower — see the
	   note on `column-gap` above. The two together are what keep the ink band
	   on one line. */
	letter-spacing: 0.10em;
	text-transform: uppercase;
	text-decoration: none;
	color: var(--paper);
	white-space: nowrap;
	cursor: pointer;
}

.sections__link::after {
	content: "";
	position: absolute;
	left: 0;
	right: 100%;
	bottom: 0.55rem;
	height: 2px;
	background: var(--vermillion);
	transition: right 180ms ease;
}

.sections__link:hover::after,
.sections__link.is-here::after,
.sections__item[open] > .sections__link::after { right: 0; }

.sections__link:focus-visible {
	outline: 2px solid var(--paper);
	outline-offset: 2px;
}

.sections__chev { transition: transform 180ms ease; }
.sections__item[open] > .sections__link .sections__chev { transform: rotate(180deg); }

/* The closed state is stated outright rather than inferred from whatever the
   engine does with a <details> internal slot — the tools bar was laid out at
   544px tall while shut for exactly that reason. */
.sections__item > .sections__panel { display: none; }
.sections__item[open] > .sections__panel { display: block; }

/* The browser's own triangle, in two dialects. Without both, Safari keeps it. */
.sections__item > summary {
	list-style: none;
	-webkit-user-select: none;
	user-select: none;
}

.sections__item > summary::-webkit-details-marker { display: none; }
.sections__item > summary::marker { content: ""; }

.sections__panel {
	position: absolute;
	left: 0;
	right: 0;
	top: 100%;
	z-index: 60;
	max-height: min(70vh, 24rem);
	overflow-y: auto;
	padding-block: var(--sp-30) var(--sp-20);
	background: var(--paper);
	border-bottom: 2px solid var(--ink);
	box-shadow: 0 18px 40px -24px rgba(18, 18, 18, 0.45);
	animation: sections-in 140ms ease-out;
}

@keyframes sections-in {
	from { opacity: 0; transform: translateY(-4px); }
	to   { opacity: 1; transform: none; }
}

/* --- The toolkit, at the end of the same bar -----------------------------
 *
 * The masthead was three rows until 2026-09-27; the PDF strip now sits at the
 * right-hand end of this one. The plugin still draws its own links and its own
 * panel — what is here is the slot and the colours, nothing that would have to
 * be kept in step with the tool catalogue.
 *
 * `menu.css` hangs everything off its own custom properties with hard-coded
 * fallbacks, which is exactly what makes this possible: the tokens are
 * redefined for an ink background on the bar, and left alone inside the panel,
 * which is still paper with ink on it.
 */
.sections__split {
	flex: 0 0 auto;
	margin-left: auto;
	width: 1px;
	align-self: stretch;
	background: rgba(250, 247, 242, 0.25);
}

.sections__tools {
	display: flex;
	align-items: center;
	gap: 1rem;
	flex: 0 0 auto;

	/* The plugin's own tokens, restated for a dark row. Without this they are
	   undefined outside `.adb-nav` and every declaration using them is invalid,
	   which reads as "the tools bar lost its styling" rather than as a missing
	   variable. */
	--adb-teal: #12807A;
	--adb-wash: #E4F3F1;
	--adb-deep: #0B4F4A;
	--adb-paper: var(--paper);
	--adb-surface: var(--paper-deep);
	--adb-ink: var(--ink);
	--adb-faded: var(--ink-faded);
	--adb-accent: var(--vermillion);
	--adb-rule: var(--rule);
}

/*
 * The toolkit's panel behaves exactly like the theme's, at every width.
 *
 * `menu.css` turns it into an in-flow accordion below 781px — `position:
 * static`, no background, no shadow — which is right on the pale strip it was
 * designed for and wrong here twice over: on an INK band a transparent panel
 * renders ink text on ink, and as a flex item it took 373px of the row and
 * stood 1,613px tall.
 *
 * So both menus in this masthead are one overlay under the whole bar, at every
 * width. `top: 100%` resolves against `.sections` — the panel's containing
 * block — not against the item that opened it.
 */
.sections__tools .adb-menu__panel {
	position: absolute;
	left: 0;
	right: 0;
	top: 100%;
	/*
	 * 32rem, which is `menu.css`'s own figure, not the 26rem the sections map
	 * uses. The map is fifteen tiles; this is 29 tools in six columns and needs
	 * about 440px. Capping it at 416 did not clip anything visibly — it added a
	 * scrollbar, and the 15px gutter that scrollbar reserves pushed this
	 * panel's content edge to 76px while the sections panel beside it sat at
	 * 84. Eight pixels of disagreement between two menus on one bar.
	 */
	max-height: min(82vh, 32rem);
	overflow-y: auto;
	padding-block: var(--sp-30) var(--sp-20);
	background: var(--paper);
	border-top: 0;
	border-bottom: 2px solid var(--ink);
	box-shadow: 0 18px 40px -24px rgba(18, 18, 18, 0.45);
}

/* On the bar the links are paper; inside the panel the tokens above apply and
   it stays ink on paper. Scoped to a direct child so the panel never inherits
   the inversion. */
.sections__tools > .adb-nav__link,
.sections__tools > .adb-menu > .adb-nav__link {
	color: var(--paper);
}

.sections__tools > .adb-menu > .adb-nav__link:focus-visible,
.sections__tools > .adb-nav__link:focus-visible {
	outline: 2px solid var(--paper);
	outline-offset: 2px;
}

@media (max-width: 1240px) {
	/* Once the row wraps, the toolkit follows the sections onto the next line
	   rather than being pinned to a right-hand edge with a gap in front of it. */
	.sections__split { margin-left: 0; }
}

@media (max-width: 900px) {
	/* Two menus on one line, one at each end. */
	.sections__tools { flex: 0 0 auto; }
}

/* --- One hub's panel: the hub itself, then its children ------------------ */
.sections__body {
	display: grid;
	grid-template-columns: minmax(180px, 15rem) 1fr;
	gap: var(--sp-30) var(--sp-40);
	align-items: start;
}

.sections__all {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	min-height: 44px;
	font-family: var(--sans);
	font-size: 0.75rem;
	font-weight: 700;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	text-decoration: none;
	color: var(--ink);
	border-bottom: 2px solid var(--vermillion);
}

.sections__all:hover { color: var(--vermillion); }
.sections__all svg { transition: transform 160ms ease; }
.sections__all:hover svg { transform: translateX(3px); }

/*
 * The children are a wrapped list, not columns. A hub holds four to six of
 * them; a column layout would leave five columns of one item each and read as
 * five sections rather than one.
 */
.sections__kids {
	list-style: none;
	margin: 0;
	padding: 0;
	display: flex;
	flex-wrap: wrap;
	gap: 0.15rem var(--sp-40);
}

.sections__kids a {
	display: inline-flex;
	align-items: center;
	min-height: 40px;
	font-family: var(--serif);
	font-size: 1rem;
	text-decoration: none;
	color: var(--ink-faded);
	border-bottom: 1px solid transparent;
}

.sections__kids a:hover {
	color: var(--ink);
	border-bottom-color: var(--vermillion);
}

.sections__kids a.is-here {
	color: var(--vermillion);
	border-bottom-color: var(--vermillion);
}

/* --- The map of sections -------------------------------------------------
 *
 * Fifteen tiles, not 93 links. The panel printed the entire tree until
 * 2026-09-27 and stood 672px tall — it covered the page it was supposed to be
 * navigating, and there was nothing in it that said "close me". Children are
 * one hover away on the bar and they open the archive rail besides; this is the
 * map, and a map that does not fit on the screen is not a map.
 */
/*
 * The tiles draw their own borders and overlap by a pixel. Drawing the rules as
 * `gap: 1px` over a rule-coloured background is the same trick the card grid
 * used and it fails the same way: fifteen tiles in a six-column grid leave
 * three empty tracks painting a beige slab the size of three tiles. A short row
 * now simply stops.
 */
.sections__map {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(190px, 1fr));
	gap: 0;
}

.sections__tile {
	display: flex;
	align-items: center;
	gap: 0.65rem;
	min-height: 60px;
	padding: 0.7rem 0.9rem;
	border: 1px solid var(--rule);
	margin: -1px 0 0 -1px;
	background: var(--paper);
	text-decoration: none;
	transition: background-color 150ms ease, color 150ms ease;
}

/*
 * The section's picture.
 *
 * A drawn mark by default and a photograph when the owner has set one — same
 * box either way, so a tile does not change shape the day somebody uploads an
 * image. The mark takes `currentColor`, which is what lets one drawing work on
 * a paper tile, on the ink band and in a vermillion heading.
 */
.sections__tile-art {
	flex: 0 0 auto;
	width: 34px;
	height: 34px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid var(--rule);
	color: var(--vermillion);
	overflow: hidden;
}

.sections__tile-text {
	display: flex;
	flex-direction: column;
	gap: 0.1rem;
	min-width: 0;
}

.sections__photo {
	width: 100%;
	height: 100%;
	object-fit: cover;
	display: block;
}

.sections__tile:hover .sections__tile-art { border-color: var(--paper); color: var(--paper); }

.sections__all .sections__art { color: var(--vermillion); flex: 0 0 auto; }
.sections__all:hover .sections__art { color: inherit; }
.sections__all .sections__photo { width: 22px; height: 22px; border: 1px solid var(--rule); }

.sections__tile-name {
	font-family: var(--sans);
	font-size: 0.75rem;
	font-weight: 800;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	color: var(--ink);
}

.sections__tile-meta {
	font-family: var(--sans);
	font-size: 0.6875rem;
	color: var(--ink-faded);
	font-variant-numeric: tabular-nums;
}

.sections__tile:hover { background: var(--ink); }
.sections__tile:hover .sections__tile-name { color: var(--paper); }
.sections__tile:hover .sections__tile-meta { color: var(--rule); }

.sections__tile.is-here { box-shadow: inset 3px 0 0 var(--vermillion); }
.sections__tile.is-here .sections__tile-name { color: var(--vermillion); }
.sections__tile.is-here:hover .sections__tile-name { color: var(--paper); }

/* --- The way out ---------------------------------------------------------
 *
 * Built by `sections.js`, never by PHP: with the script off there is no panel
 * to be stuck in — clicking the summary again closes it, which is what a
 * <details> does — and a close button that does nothing is worse than none.
 */
.sections__close {
	position: absolute;
	top: 0.5rem;
	right: max(1.25rem, calc((100% - var(--wide)) / 2));
	width: 34px;
	height: 34px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid var(--rule);
	background: var(--paper);
	color: var(--ink-faded);
	cursor: pointer;
	padding: 0;
}

.sections__close:hover { background: var(--ink); border-color: var(--ink); color: var(--paper); }

/* The toolkit's panel is `position: relative` in menu.css, so the control needs
   no repositioning there — but its own padding is different, so it is nudged to
   sit on the same line as the one in the sections panel. */
.adb-menu__panel .sections__close { top: 0.6rem; }
.sections__close:focus-visible { outline: 2px solid var(--vermillion); outline-offset: 2px; }

.sections__foot {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: var(--sp-30);
	flex-wrap: wrap;
	margin-top: var(--sp-30);
	padding-top: var(--sp-20);
	border-top: 1px solid var(--rule);
}

.sections__note {
	margin: 0;
	font-family: var(--sans);
	font-size: 0.75rem;
	color: var(--ink-faded);
}

.sections__more {
	font-family: var(--sans);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	text-decoration: none;
	color: var(--ink);
	border-bottom: 2px solid var(--vermillion);
	min-height: 44px;
	display: inline-flex;
	align-items: center;
}

.sections__more:hover { color: var(--vermillion); }

@media (max-width: 1100px) {
	.sections__map { grid-template-columns: repeat(auto-fill, minmax(160px, 1fr)); }
}

/*
 * Small screens: two menus, not thirteen labels.
 *
 * Thirteen items wrap into five lines of small caps at 390px — 220px of
 * masthead before the article starts. Both "All …" disclosures already hold
 * everything their neighbours point at (the whole 93-term tree, and all 29
 * tools), so below 900px they are the bar and the rest step aside. One line,
 * no scroller, nothing off-screen.
 *
 * The section a reader is currently in is the one exception: it stays, because
 * a masthead that cannot show you where you are is worse than a long one.
 */
@media (max-width: 900px) {
	.sections__item:not(.sections__item--all),
	.sections__tools > .adb-nav__link {
		display: none;
	}

	/* `is-here` is on the summary, not on the disclosure — so the disclosure is
	   selected through it. A hub with no children is a plain link and matches
	   the first rule instead. */
	.sections__item:has( > .sections__link.is-here ) { display: block; }
	a.sections__link.is-here { display: inline-flex; }
	.sections__split { display: none; }
	.sections__inner { justify-content: space-between; }
}

@media (max-width: 780px) {
	/* One column of children rather than a wrapped row: at this width the
	   wrap leaves orphans and the eye loses the column. */
	.sections__body { grid-template-columns: 1fr; }
	.sections__kids { flex-direction: column; gap: 0; }
	.sections__map { grid-template-columns: 1fr 1fr; }
	/* 44px on a phone, where the list is thumbed rather than pointed at. */
	.sections__kids a { min-height: 44px; }
}

/*
 * One column below 520px.
 *
 * A half-width tile at 390px leaves about 120px for the name, and TECHNOLOGY
 * is one word at 0.08em tracking — it cannot wrap, so it ran under the tile
 * beside it and was clipped. Nothing here is truncatable: a section's name is
 * the whole content of the tile.
 */
@media (max-width: 520px) {
	.sections__map { grid-template-columns: 1fr; }
}

@media (prefers-reduced-motion: reduce) {
	.sections__panel { animation: none; }
	.sections__link::after,
	.sections__chev,
	.sections__all svg { transition: none; }
}

/* --- About figure -------------------------------------------------------- */

/*
 * A 3.06:1 band, the proportion the file is actually cut to, so nothing is
 * cropped and nothing letterboxes. `aspect-ratio` is NOT used: the intrinsic
 * width/height on the tag already reserve the box, and adding a ratio here
 * would only start a fight if the picture is ever replaced with another crop.
 */
.about-figure {
	margin: var(--sp-40) auto 0;
}

.about-figure img {
	display: block;
	width: 100%;
	height: auto;
	border: 1px solid var(--rule);
}

/* --- Hero ---------------------------------------------------------------- */

/*
 * The hero's stage — the client's own Pexels footage behind his own words.
 *
 * It is a PLAIN full-width block, not a `100vw` bleed. `main` is unconstrained
 * and the `.wrap` inside does the centring, so there is no `calc(50% - 50vw)`
 * anywhere and therefore no way for the stage to reach past a scrollbar and
 * give the page a horizontal scroll. That bug is the usual price of full-bleed
 * and it is simply not paid here.
 *
 * `isolation: isolate` matters: it gives the stage its own stacking context so
 * the media can sit at `z-index: 0` under content at `z-index: 1` without the
 * masthead, the dropdown panels or anything else on the page being dragged
 * into the comparison.
 */
.hero-stage {
	position: relative;
	isolation: isolate;
	overflow: hidden;
	background: var(--ink);
}

.hero-stage__media {
	position: absolute;
	inset: 0;
	z-index: 0;
	background-size: cover;
	background-position: center;
	background-repeat: no-repeat;
}

.hero-stage__video {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
	/* Decoration. It must never be the reason a line of text is unreadable, so
	   the veil above it does the work and this just fills the frame. */
	pointer-events: none;
}

/*
 * Two gradients, not one. The horizontal pass protects the left-hand column
 * where every word actually sits; the vertical pass keeps the footage from
 * fighting the masthead above it or the rule below it. Both are the palette's
 * own plum, so the hero belongs to the page rather than sitting on top of it.
 */
.hero-stage__veil {
	position: absolute;
	inset: 0;
	background:
		linear-gradient(90deg, rgb(56 20 36 / 94%) 0%, rgb(56 20 36 / 80%) 48%, rgb(56 20 36 / 50%) 100%),
		linear-gradient(180deg, rgb(56 20 36 / 60%) 0%, rgb(56 20 36 / 22%) 42%, rgb(56 20 36 / 72%) 100%);
}

.hero--media {
	position: relative;
	z-index: 1;
	padding-block: var(--sp-60);
	color: var(--paper-deep);
}

.hero--media h1 { color: var(--paper-deep); }

/* The rose is a link colour chosen against white. On the plum it is too close
   to the ground to read, so it is lifted toward the cream — by mixing rather
   than by a second hard-coded hex, so it still follows whatever `primary` a
   variation sets. */
.hero--media h1 em,
.hero--media .label--accent {
	color: #CD90A8;
	color: color-mix(in srgb, var(--vermillion) 55%, var(--paper-deep));
}

.hero--media .hero__meta { border-top-color: rgb(255 248 243 / 28%); }
.hero--media .hero__lede { color: rgb(255 248 243 / 82%); }

/* On the plum the filled button would vanish, so the two swap jobs: the solid
   one goes cream, and the outline borrows the cream for its edge. */
.hero--media .btn {
	background: var(--paper-deep);
	border-color: var(--paper-deep);
	color: var(--ink);
}
.hero--media .btn:hover {
	background: var(--vermillion);
	border-color: var(--vermillion);
	color: var(--paper-deep);
}
.hero--media .btn--outline {
	background: transparent;
	border-color: rgb(255 248 243 / 55%);
	color: var(--paper-deep);
}
.hero--media .btn--outline:hover {
	background: var(--paper-deep);
	border-color: var(--paper-deep);
	color: var(--ink);
}

/* Motion is decoration here and nobody has to sit through it. The poster stays
   as the background, so the hero looks composed rather than broken. */
@media (prefers-reduced-motion: reduce) {
	.hero-stage__video { display: none; }
}

.hero { padding-block: var(--sp-60) var(--sp-50); }

.hero h1 { max-width: 16ch; }
.hero h1 em { font-style: normal; color: var(--vermillion); }

.hero__meta {
	display: grid;
	grid-template-columns: 1fr minmax(260px, 34%);
	gap: var(--sp-40);
	align-items: end;
	margin-top: var(--sp-40);
	padding-top: var(--sp-30);
	border-top: 1px solid var(--rule);
}

.hero__lede {
	font-family: var(--serif);
	font-size: var(--fs-large);
	line-height: 1.5;
	color: var(--ink-faded);
	margin: 0;
	max-width: 46ch;
}

/* --- Lead article -------------------------------------------------------- */
.lead {
	display: grid;
	grid-template-columns: 4.5rem 1fr minmax(240px, 32%);
	gap: var(--sp-40);
	padding-block: var(--sp-50);
	border-top: 2px solid var(--ink);
}

.lead__index,
.row__index {
	font-family: var(--sans);
	font-size: 0.75rem;
	font-weight: 700;
	letter-spacing: 0.1em;
	color: var(--vermillion);
	padding-top: 0.5rem;
}

.lead h2 { margin-block: 0.5rem 0.75rem; max-width: 18ch; }

.lead__excerpt {
	font-family: var(--serif);
	font-size: var(--fs-large);
	line-height: 1.55;
	color: var(--ink-faded);
	max-width: 52ch;
}

.thumb {
	aspect-ratio: 4 / 3;
	background: var(--paper-deep);
	border: 1px solid var(--ink);
	display: grid;
	place-items: center;
	color: var(--ink-faded);
	font-size: 0.6875rem;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	text-align: center;
	padding: var(--sp-20);
}

.thumb--wide { aspect-ratio: 21 / 9; }

/*
 * A real picture in a slot shaped for the placeholder.
 *
 * `.thumb` and `.thumb--wide` describe an empty BOX — a ratio, a background,
 * centred small caps. WordPress puts that same class on the <img> once a
 * featured image exists, so the ratio applied to the picture itself and,
 * with no object-fit to say otherwise, stretched it to fit: every circle in
 * the first plate came out an oval on the article page. The box rules and the
 * picture rules have to be different rules.
 */
img.thumb,
img.thumb--wide,
.lead__figure img,
.thumb img {
	display: block;
	width: 100%;
	height: 100%;
	padding: 0;
	object-fit: cover;
	background: var(--paper);
	border: 1px solid var(--ink);
}

.lead__figure img {
	aspect-ratio: 4 / 3;
}

img.thumb--wide {
	aspect-ratio: 21 / 9;
}

/*
 * The post's hero picture is the same width as the writing under it.
 *
 * It sits in its own `wrap wrap--wide`, so it filled all 1052px while `.entry`
 * stopped at the 66ch measure — the picture overhung the text by 239px on the
 * right and by nothing on the left, which reads as a mistake rather than as a
 * wide image. Capping the PICTURE rather than its wrap keeps the wrap's
 * padding and centring identical to every other row, and a block element caps
 * from its start edge, so the two line up on the left without any extra rule.
 */
.article-figure img,
.article-figure .thumb {
	max-width: var(--measure);
}

.meta-line {
	display: flex;
	flex-wrap: wrap;
	gap: 0.75rem;
	align-items: center;
	font-size: 0.6875rem;
	font-weight: 600;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--ink-faded);
	font-variant-numeric: tabular-nums;
}

.meta-line .sep { color: var(--rule); }

/* --- The index (replaces the card grid) ---------------------------------- */
.section-head {
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	gap: var(--sp-30);
	padding-bottom: 0.6rem;
	border-bottom: 2px solid var(--ink);
	margin-top: var(--sp-60);
}

.index { border-top: 0; }

.row {
	display: grid;
	grid-template-columns: 4.5rem 1fr minmax(200px, 26%);
	gap: var(--sp-40);
	padding-block: var(--sp-30);
	border-bottom: 1px solid var(--rule);
	align-items: start;
	text-decoration: none;
	color: inherit;
	transition: background-color 120ms ease, padding 120ms ease;
}

.row:hover {
	background: var(--ink);
	color: var(--paper);
	padding-inline: var(--sp-20);
}

.row:hover .row__index,
.row:hover .row__cat { color: var(--paper); }

.row:hover .row__excerpt,
.row:hover .row__meta { color: var(--rule); }

.row__title {
	font-family: var(--display);
	font-size: var(--fs-x-large);
	font-weight: 800;
	line-height: 1.05;
	letter-spacing: -0.03em;
	margin: 0.15rem 0 0.4rem;
	max-width: 24ch;
}

.row__cat {
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	color: var(--vermillion);
}

.row__excerpt {
	font-family: var(--serif);
	font-size: 1rem;
	line-height: 1.5;
	color: var(--ink-faded);
	margin: 0;
	max-width: 58ch;
}

.row__meta {
	font-size: 0.6875rem;
	font-weight: 600;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--ink-faded);
	text-align: right;
	font-variant-numeric: tabular-nums;
	padding-top: 0.35rem;
}

/* --- The dense index: everything, by month -------------------------------
 *
 * The front page's rows are display type with a running number, because six of
 * them is a shortlist and a shortlist is worth counting. The page that lists
 * EVERYTHING is a different object: at that size fifteen rows were 3,000px of
 * identical slabs under a wall of category chips (Onkar, 2026-09-27: "its
 * inside is too messy"). Same row, read at reading size, grouped by the month
 * it was published in.
 */
.index__month {
	font-family: var(--sans);
	font-size: var(--fs-small);
	font-weight: 800;
	letter-spacing: 0.16em;
	text-transform: uppercase;
	color: var(--ink-faded);
	margin: var(--sp-40) 0 0;
	padding-bottom: 0.4rem;
	border-bottom: 2px solid var(--ink);
}

.index__month:first-child { margin-top: 0; }

.row--dense {
	grid-template-columns: 1fr minmax(120px, 16%);
	gap: var(--sp-30);
	padding-block: var(--sp-20);
}

.row--dense .row__title {
	font-size: var(--fs-large);
	line-height: 1.2;
	letter-spacing: -0.015em;
	margin: 0.1rem 0 0;
	/*
	 * 24ch is the display measure and it belongs to the big rows: at reading
	 * size it is about 330px, which broke every title into three lines inside a
	 * 1,000px column and left the row looking like a column of scraps.
	 */
	max-width: 60ch;
}

.row--dense .row__cat { font-size: 0.625rem; }

.row--dense .row__meta { padding-top: 0.2rem; }

@media (max-width: 600px) {
	/* The date moves under the title rather than squeezing it to nothing. */
	.row--dense { grid-template-columns: 1fr; gap: 0.35rem; }
	.row--dense .row__meta { text-align: left; }
	.row--dense .row__meta br { display: none; }
}

/* --- Ink band ------------------------------------------------------------ */
.band {
	background: var(--ink);
	color: var(--paper);
	padding: var(--sp-60) var(--sp-40);
	margin-top: var(--sp-60);
	text-align: center;
}

.band h2 { color: var(--paper); max-width: 22ch; margin-inline: auto; }
.band p { color: #B8B0A4; font-size: var(--fs-small); margin-top: var(--sp-20); }
.band .btns { justify-content: center; margin-top: var(--sp-30); }
.band .btn { background: var(--paper); color: var(--ink); border-color: var(--paper); }
.band .btn:hover { background: var(--vermillion); border-color: var(--vermillion); color: var(--paper); }
.band .btn--outline { background: transparent; color: var(--paper); }
.band .btn--outline:hover { background: var(--paper); color: var(--ink); border-color: var(--paper); }

/* --- Article ------------------------------------------------------------- */
.article-head { padding-block: var(--sp-50) var(--sp-30); }
.article-head h1 { font-size: var(--fs-xx-large); letter-spacing: -0.04em; max-width: 20ch; }

.article-head .hero__lede { margin-top: var(--sp-30); }

.article-meta {
	display: flex;
	flex-wrap: wrap;
	gap: 0.75rem;
	align-items: center;
	margin-top: var(--sp-30);
	padding-block: 0.75rem;
	border-top: 1px solid var(--rule);
	border-bottom: 2px solid var(--ink);
	font-size: 0.6875rem;
	font-weight: 600;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--ink-faded);
	font-variant-numeric: tabular-nums;
}

/*
 * Flex, not grid — and that is a bug fix, not a preference.
 *
 * This was a two-column grid with a companion rule meant to collapse it on a
 * post with no table of contents:
 *
 *     .article-body:has( > aside:not(:has(*)) ) { grid-template-columns: minmax(0, 1fr); }
 *
 * **That selector is invalid.** `:has()` may not be nested inside another
 * `:has()`, so the browser discarded the whole rule. Its neighbour below is
 * legal — a `:has()` inside a TOP-LEVEL `:not()` is allowed — so that one ran.
 *
 * The result, on every post without a TOC: the aside was hidden, the grid kept
 * BOTH tracks, and the article fell into the 24% sidebar column. Measured on
 * 2026-09-28 at 1440: the body rendered 252px wide with 735px of empty page
 * beside it. Onkar found it by opening a post; nothing in CSS reported it,
 * because an invalid selector is not an error, it is silence — the collapse
 * this comment block used to promise had never once been applied.
 *
 * Flex needs no `:has()` for the collapse at all: a `display: none` aside
 * simply stops taking part and the entry grows into the space. `.entry` keeps
 * its own 66ch cap, so a full-width row still sets at a readable measure.
 */
.article-body {
	display: flex;
	align-items: flex-start;
	gap: var(--sp-50);
	margin-top: var(--sp-50);
}

.article-body > aside {
	flex: 0 1 24%;
	min-width: 200px;
}

.article-body > .entry {
	flex: 1 1 0;
	min-width: 0;
}

/* Legal, and still wanted: an aside holding only the template's whitespace is
   not `:empty`, so `:has(*)` — which tests for ELEMENT children — is the test
   that works. */
.article-body > aside:not(:has(*)) { display: none; }

.entry {
	font-family: var(--serif);
	font-size: var(--fs-large);
	line-height: 1.7;
	max-width: var(--measure);
}

.entry > h2 {
	font-family: var(--display);
	border-top: 1px solid var(--ink);
	padding-top: var(--sp-20);
	margin-top: var(--sp-50);
	margin-bottom: var(--sp-20);
	scroll-margin-top: 2.5rem;
}

.entry > h3 {
	font-family: var(--display);
	margin-top: var(--sp-40);
	margin-bottom: var(--sp-20);
	scroll-margin-top: 2.5rem;
}

.entry > p:first-of-type::first-letter {
	font-family: var(--display);
	font-weight: 800;
	font-size: 3.6em;
	line-height: 0.78;
	float: left;
	margin: 0.08em 0.12em 0 0;
	color: var(--vermillion);
}

.entry em { font-style: italic; }

/* --- TOC ----------------------------------------------------------------- */
.adb-toc {
	border-top: 2px solid var(--ink);
	padding-top: var(--sp-20);
	font-family: var(--sans);
	font-size: var(--fs-small);
}

.adb-toc__title {
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.18em;
	text-transform: uppercase;
	color: var(--ink-faded);
	margin: 0 0 0.5rem;
}

.adb-toc ol { list-style: none; margin: 0; padding: 0; counter-reset: adb-toc; }
.adb-toc li { margin: 0; counter-increment: adb-toc; }

.adb-toc a {
	display: flex;
	align-items: center;
	gap: 0.6rem;
	min-height: 44px;
	padding-block: 0.35rem;
	color: var(--ink-faded);
	text-decoration: none;
	line-height: 1.35;
	border-bottom: 1px solid var(--rule);
}

.adb-toc a::before {
	content: counter(adb-toc, decimal-leading-zero);
	font-size: 0.6875rem;
	font-weight: 700;
	color: var(--rule);
	flex: none;
}

.adb-toc li.is-h3 a { padding-inline-start: 1.6rem; }

.adb-toc a:hover,
.adb-toc a.is-active { color: var(--ink); }

.adb-toc a:hover::before,
.adb-toc a.is-active::before { color: var(--vermillion); }

.adb-toc a.is-active { font-weight: 600; }

@media (min-width: 1100px) {
	.adb-toc.is-sticky { position: sticky; top: 2.5rem; }
}

/* --- Editorial patterns -------------------------------------------------- */
.takeaways {
	font-family: var(--sans);
	font-size: 1rem;
	border: 1px solid var(--ink);
	box-shadow: 4px 4px 0 0 var(--ink);
	background: var(--paper);
	padding: var(--sp-40);
	margin-block: var(--sp-40);
}

.takeaways .label { margin-bottom: 0.75rem; }

.checklist { list-style: none; padding-inline-start: 0; margin: 0; }

.checklist li {
	position: relative;
	padding-inline-start: 1.6rem;
	margin-block: 0.6rem;
	line-height: 1.5;
}

.checklist li::before {
	content: "";
	position: absolute;
	inset-inline-start: 0;
	top: 0.72em;
	width: 0.7rem;
	height: 2px;
	background: var(--vermillion);
}

.callout {
	font-family: var(--sans);
	font-size: 1rem;
	background: var(--marker);
	border: 1px solid var(--ink);
	padding: var(--sp-30);
	margin-block: var(--sp-40);
}

.callout .label { margin-bottom: 0.4rem; color: var(--ink); }

blockquote.pull {
	font-family: var(--display);
	font-size: var(--fs-x-large);
	font-weight: 800;
	line-height: 1.08;
	letter-spacing: -0.03em;
	border: 0;
	border-top: 2px solid var(--ink);
	border-bottom: 2px solid var(--ink);
	margin: var(--sp-50) 0;
	padding: var(--sp-40) 0;
}

blockquote.pull p { margin: 0; }

blockquote.pull cite {
	display: block;
	margin-top: 0.9rem;
	font-size: 0.6875rem;
	font-weight: 600;
	font-style: normal;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--ink-faded);
}

.entry table {
	width: 100%;
	border-collapse: collapse;
	font-family: var(--sans);
	font-size: var(--fs-small);
	font-variant-numeric: tabular-nums;
	margin-block: var(--sp-40);
}

.entry :is(th, td) {
	padding: 0.7rem 0.9rem;
	border: 0;
	border-bottom: 1px solid var(--rule);
	text-align: left;
	vertical-align: top;
}

.entry thead th {
	border-bottom: 2px solid var(--ink);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.14em;
	text-transform: uppercase;
}

.entry code {
	font-family: var(--mono);
	font-size: 0.88em;
	background: var(--paper-deep);
	border: 1px solid var(--rule);
	padding: 0.1em 0.35em;
}

/* --- Share + author ------------------------------------------------------ */
.share {
	margin-top: var(--sp-50);
	padding-top: var(--sp-20);
	border-top: 2px solid var(--ink);
}

.share .label { margin-bottom: 0.75rem; }

.author-card {
	display: grid;
	grid-template-columns: 80px 1fr;
	gap: var(--sp-30);
	border: 1px solid var(--ink);
	box-shadow: 6px 6px 0 0 var(--vermillion);
	background: var(--paper);
	padding: var(--sp-40);
	margin-top: var(--sp-60);
}

.avatar {
	width: 80px;
	height: 80px;
	border: 1px solid var(--ink);
	background: var(--vermillion-wash);
	display: grid;
	place-items: center;
	font-family: var(--sans);
	font-weight: 800;
	font-size: 2rem;
	color: var(--vermillion);
}

/* --- Footer -------------------------------------------------------------- */
.site-footer {
	border-top: 2px solid var(--ink);
	margin-top: var(--sp-60);
	padding-block: var(--sp-50);
	background: var(--paper-deep);
}

.footer-cols {
	display: grid;
	grid-template-columns: 42% 1fr 1fr;
	gap: var(--sp-50);
}

.footer-links { display: flex; flex-direction: column; }

.footer-links a {
	font-size: 0.75rem;
	font-weight: 600;
	letter-spacing: 0.12em;
	text-transform: uppercase;
	min-height: 44px;
	display: inline-flex;
	align-items: center;
	text-decoration: none;
	border-bottom: 1px solid var(--rule);
}

.footer-links a:hover { color: var(--vermillion); }

.footer-bottom {
	display: flex;
	flex-wrap: wrap;
	justify-content: space-between;
	gap: var(--sp-20);
	border-top: 1px solid var(--rule);
	margin-top: var(--sp-40);
	padding-top: var(--sp-30);
	color: var(--ink-faded);
	font-size: 0.6875rem;
	font-weight: 600;
	letter-spacing: 0.12em;
	text-transform: uppercase;
}

/* --- Preview-only banner ------------------------------------------------- */


/* --- Responsive ---------------------------------------------------------- */
@media (max-width: 1024px) {
	.lead { grid-template-columns: 3rem 1fr; }
	.lead__figure { grid-column: 1 / -1; }
	.hero__meta { grid-template-columns: 1fr; }
}

@media (max-width: 781px) {
	.article-body { flex-direction: column; }
	.article-body > aside { flex: 0 0 auto; min-width: 0; width: 100%; }
	.adb-toc.is-sticky { position: static; }
	.row { grid-template-columns: 2.5rem 1fr; }
	.row__meta { grid-column: 2; text-align: left; padding-top: 0.5rem; }
	.footer-cols { grid-template-columns: 1fr; }
	.lead { grid-template-columns: 1fr; }
	.lead__index { padding-top: 0; }
}

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

html { scroll-behavior: smooth; }

/* ==========================================================================
   Components added when every link was wired up
   ========================================================================== */

/* Links that should not look like links (titles, wordmarks in cards). */
a.plain { color: inherit; text-decoration: none; }
a.plain:hover { color: var(--vermillion); }

.lead__figure { display: block; text-decoration: none; }
.lead__figure .thumb { width: 100%; }

.section-head__title {
	font-size: 1.125rem;
	font-weight: 800;
	letter-spacing: 0.02em;
	text-transform: uppercase;
}

/* --- Preview toolbar ----------------------------------------------------- */





/* --- The head of a section ----------------------------------------------- */
/*
 * The section mark sits ABOVE the heading, not beside it.
 *
 * Beside it, the emblem pushed the eyebrow, the title and the description 88px
 * to the right while the chips rail and the list below them stayed on the page
 * edge — measured, and the most visible misalignment on the site. A 64px mark
 * is a section's badge; it does not get to move the section's name.
 */
.archive-head {
	display: block;
}

/*
 * The emblem is a square with a rule, not a filled block: it sits beside a
 * heading set in the site's heaviest weight and should not compete with it.
 */
.archive-head__art {
	width: 64px;
	height: 64px;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 1px solid var(--rule);
	color: var(--vermillion);
	margin-bottom: var(--sp-20);
}

/*
 * A photograph the owner set gets a band instead. 16:5 is wide enough to read
 * as a banner and short enough that the section's name is still on the first
 * screen of a phone, which is the whole point of a section header.
 */
.archive-head__banner {
	margin-top: var(--sp-30);
	aspect-ratio: 16 / 5;
	overflow: hidden;
	border: 1px solid var(--rule);
}

.archive-head__photo {
	width: 100%;
	height: 100%;
	object-fit: cover;
	display: block;
}

@media (max-width: 600px) {
	.archive-head__art { width: 48px; height: 48px; }
	.archive-head__banner { aspect-ratio: 16 / 7; }
}

/* --- Category chips ------------------------------------------------------ */
.chips { display: flex; flex-wrap: wrap; gap: 0.5rem; }

.chip {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	min-height: 44px;
	padding: 0.5rem 0.9rem;
	border: 1px solid var(--ink);
	background: transparent;
	color: var(--ink);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.12em;
	text-transform: uppercase;
	text-decoration: none;
	transition: background-color 150ms ease, color 150ms ease;
}

.chip span { color: var(--ink-faded); font-variant-numeric: tabular-nums; }

.chip:hover { background: var(--ink); color: var(--paper); }
.chip:hover span { color: var(--rule); }

.chip.is-active { background: var(--ink); color: var(--paper); }
.chip.is-active span { color: var(--rule); }

/*
 * The chip that goes back UP a level. It leads the rail on a child archive, so
 * it is drawn as the section it is rather than as another sibling: vermillion
 * rule under it, and a little arrow before the name.
 */
.chip--up { border-color: var(--vermillion); box-shadow: inset 0 -2px 0 var(--vermillion); }
.chip--up svg { color: var(--vermillion); }
.chip--up:hover { background: var(--vermillion); border-color: var(--vermillion); color: var(--paper); }
.chip--up:hover svg { color: var(--paper); }

/*
 * A section with nothing in it yet. Faded rather than hidden — the tree is what
 * this site says it covers, and a rail that only shows what has been published
 * is a different promise. Still a link, still 44px, still readable: the border
 * softens, the label does not.
 */
.chip--empty { border-color: var(--rule); }
.chip--empty span { color: var(--rule); }

/* --- Pagination ---------------------------------------------------------- */
.pagination {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: var(--sp-20);
	flex-wrap: wrap;
	border-top: 2px solid var(--ink);
	margin-top: var(--sp-40);
	padding-top: var(--sp-20);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.12em;
	text-transform: uppercase;
}

/* --- Forms --------------------------------------------------------------- */
.comment-form label {
	display: block;
	margin: var(--sp-20) 0 0.35rem;
	font-family: var(--sans);
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.14em;
	text-transform: uppercase;
}

.comment-form :is(input, textarea) {
	width: 100%;
	padding: 0.8rem;
	border: 1px solid var(--ink);
	border-radius: 0;
	background: var(--paper);
	color: var(--ink);
	font-family: var(--sans);
	font-size: 0.9375rem;
}

.comment-form :is(input, textarea):focus {
	outline: 2px solid var(--vermillion);
	outline-offset: 1px;
}

.search-row,
.subscribe-row {
	display: flex;
	gap: 0.5rem;
	flex-wrap: wrap;
	margin-top: var(--sp-30);
}

.search-row input,
.subscribe-row input {
	flex: 1 1 16rem;
	min-height: 44px;
	padding: 0.7rem 0.9rem;
	border: 1px solid var(--ink);
	border-radius: 0;
	background: var(--paper);
	color: var(--ink);
	font-family: var(--sans);
	font-size: 0.9375rem;
}

.subscribe-row { justify-content: center; margin-top: var(--sp-30); }
.subscribe-row input { border-color: var(--paper); max-width: 22rem; }

.search-row input:focus,
.subscribe-row input:focus {
	outline: 2px solid var(--vermillion);
	outline-offset: 1px;
}

.btns--stack { flex-direction: column; align-items: stretch; }

/*
 * A stacked button holds whatever the owner's address turns out to be.
 *
 * `Email hello2apsingh@gmail.com` is one unbreakable token as far as the line
 * breaker is concerned, so it ran straight out of the card it sits in and over
 * the vermillion shadow — measured on /contact/ at 1440 the day the real
 * address replaced a short one. An address is data, not a design assumption:
 * the button wraps to it rather than the other way round.
 */
.btns--stack .btn {
	justify-content: center;
	min-width: 0;
	overflow-wrap: anywhere;
	text-align: center;
}

.screen-reader-only {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip-path: inset(50%);
	white-space: nowrap;
}

/* --- Contact layout ------------------------------------------------------ */
.contact-grid {
	display: grid;
	grid-template-columns: minmax(280px, 38%) minmax(0, 1fr);
	gap: var(--sp-50);
	margin-top: var(--sp-40);
}

.contact-direct {
	border: 1px solid var(--ink);
	box-shadow: 6px 6px 0 0 var(--vermillion);
	background: var(--paper);
	padding: var(--sp-40);
	align-self: start;
}

/* --- Comments ------------------------------------------------------------ */
.comments { margin-top: var(--sp-50); }

.comment {
	display: grid;
	grid-template-columns: 48px 1fr;
	gap: var(--sp-30);
	padding-block: var(--sp-30);
	border-bottom: 1px solid var(--rule);
}

.comment__avatar {
	width: 48px;
	height: 48px;
	border: 1px solid var(--ink);
	background: var(--paper-deep);
	display: grid;
	place-items: center;
	font-family: var(--sans);
	font-weight: 800;
	color: var(--ink);
}

.comment__meta {
	font-size: 0.6875rem;
	font-weight: 700;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--ink-faded);
	margin: 0 0 0.35rem;
}

.comment__body {
	font-family: var(--serif);
	font-size: 1.0625rem;
	line-height: 1.6;
	margin: 0 0 0.5rem;
}

.comment a.label { text-decoration: none; }
.comment a.label:hover { color: var(--vermillion); }

/* --- Search highlight ---------------------------------------------------- */
mark {
	background: var(--marker);
	color: var(--ink);
	padding: 0 0.15em;
}

/* --- Responsive additions ------------------------------------------------ */
@media (max-width: 781px) {
	.contact-grid { grid-template-columns: 1fr; }
	.comment { grid-template-columns: 40px 1fr; }
	.comment__avatar { width: 40px; height: 40px; }
}