/*
 * otoposmou-joomla — site stylesheet.
 *
 * ============================================================================
 * 🔴 WHY THIS FILE IS CALLED user.css AND WHY THERE IS NO CHILD TEMPLATE.
 *
 * Baked by the Dockerfile to
 *     /var/www/site/media/templates/site/cassiopeia/css/user.css
 *
 * Stock Cassiopeia already asks for it. Read off the running 6.1.2 image, not
 * researched:
 *     templates/cassiopeia/index.php:82        ->useStyle('template.user')
 *     templates/cassiopeia/joomla.asset.json:43  "name": "template.user",
 *                                                "uri": "user.css", "weight": 500
 * Weight 500 puts it AFTER template.css, so it wins specificity ties without a
 * single `!important`. Joomla omits a missing asset silently, which is why nothing
 * referenced it before this file existed.
 *
 * That makes a Cassiopeia CHILD TEMPLATE unnecessary, and a child template is not
 * free here: it needs a new #__template_styles row, an extension:discover pass in
 * scripts/install.sh, and the `home` flag moved off `cassiopeia` — three pieces of
 * database state to keep in step, on a site whose Global Configuration → Save is
 * broken by design (docs/09 decision #4). A child template that is registered but
 * not `home=1` renders NOTHING and looks exactly like a CSS bug. ⚠️ One already
 * exists unused in the image — `cassiopeia_extended`, style id 12, home=0 — which is
 * Joomla's own stock example, not project-authored. Do not mistake it for ours.
 *
 * ⚠️ BEFORE THIS FILE, `.otm-missing-image` HAD NO CSS AT ALL. Verified four ways:
 * zero .css files in the repo, `grep -rl otm-missing --include=*.css` over the
 * docroot returned nothing, all 13 stylesheets the worst-case article loads greped
 * clean, and the screenshot. The placeholder was the loudest element on the page
 * partly because nobody had ever styled it — it was rendering at full body-text size
 * with UA-default `figure { margin: 1em 40px }`.
 * ============================================================================
 */

/* ---------------------------------------------------------------------------
 * The lost photographs of the 2004-2020 archive.
 *
 * Emitted by import/lib/sanitise.php (the marker) and plugins/system/otmarchive
 * (the row and the note). MEASURED: 2,768 markers across 1,577 of 1,821 articles;
 * the worst article carries 34.
 *
 * 🔴 THE WHOLE JOB OF THIS BLOCK IS TO MAKE A REPEATED ELEMENT SCANNABLE RATHER THAN
 * READABLE. One marker should be legible; thirty-four in a column should read as an
 * index — something the eye counts and moves past — and never compete with the
 * organisation's own words. Hence: small, one line, muted, no link colour, and a
 * dashed border that says "a thing is absent here" without drawing a box the size of
 * a photograph.
 * ------------------------------------------------------------------------- */

/*
 * 🔴 THERE IS NO `white-space: nowrap` HERE ANY MORE, AND PUTTING IT BACK BREAKS THE
 *    ONE ARTICLE THE CAPTIONED VARIANT EXISTS FOR. MEASURED at 390 px on article 830
 *    (legacy 1019, the single article whose source carried a real caption): its chip
 *    is 428 px of unbreakable text, `documentElement.scrollWidth` 444 against
 *    `innerWidth` 386, so the WHOLE PAGE scrolled sideways and the caption clipped
 *    mid-word at the viewport edge. nowrap is right for a 17-character label and
 *    wrong for the same class carrying arbitrary text, and the class cannot tell the
 *    two apart — import/lib/sanitise.php's otm_placeholder_captioned() emits the same
 *    `otm-missing-image`.
 *
 *    `display: inline-block` + `max-width: 100%` gives BOTH behaviours with no second
 *    class and no stored-body change, because an inline-block is an ATOMIC INLINE:
 *    its shrink-to-fit width is min(max-content, containing block), never the space
 *    left on the current line. So the 17-character label always takes its max-content
 *    width and never splits — a chip that does not fit moves to the next line whole,
 *    which is the property the nowrap was there to buy — while the 428 px captioned
 *    chip is clamped to the column and wraps INSIDE its own box.
 *
 * ⚠️ `max-width` is load-bearing, not belt-and-braces: Joomla sets
 *    `box-sizing: border-box` globally, so 100% has to include the padding and the
 *    1 px border or the chip overflows by 18 px and the page scrolls again — by less,
 *    which is worse, because it is no longer obvious in a screenshot.
 */
.otm-missing-image {
	display: inline-block;
	max-width: 100%;
	padding: 0.05em 0.5em;
	border: 1px dashed #c3c8ce;
	border-radius: 3px;
	background: #f7f8f9;
	color: #6b7280;
	font-size: 0.8em;
	line-height: 1.6;
	overflow-wrap: break-word;
	vertical-align: baseline;
	text-decoration: none;
}

/*
 * A marker still inside a live `<a>`. plugins/system/otmarchive unwraps the anchor
 * only where the destination is established as dead, so anything still linked here
 * goes somewhere real — 22 YouTube, 3 Google Photos, and 5 links to articles on this
 * very site. It has to look clickable, because it is.
 *
 * ⚠️ `a` is matched loosely on purpose: the anchor may carry target, rel and title.
 */
a .otm-missing-image {
	border-style: solid;
	border-color: #b6c6dd;
	color: #2a4c7d;
}

a:hover .otm-missing-image,
a:focus .otm-missing-image {
	border-color: #2a4c7d;
	background: #eef3fa;
}

/*
 * The anchor's own underline, which lands on NOTHING. Several of the 2008 anchors are
 * written `<a …><img …> </a>` — a trailing space INSIDE the link — and once the image
 * became a chip with `text-decoration: none`, that space was the only thing left for
 * the underline to draw on: a stray 8 px dash floating between chips (visible on
 * article 1804, and only in a screenshot). The chip keeps its solid border and link
 * colour, so nothing is lost as an affordance.
 */
.otm-missing-row a {
	text-decoration: none;
}

/*
 * ---------------------------------------------------------------------------
 * 🔴 A RUN OF LOST PHOTOGRAPHS IS ONE RULED LINE THAT STATES ITS COUNT, NOT A GRID.
 *
 * This block used to design the opposite, in as many words: "a gallery of lost
 * photographs … the chips wrap like the thumbnails they replaced". On article 403 —
 * the front-page lead, the first article anyone opens — that rendered 34 identical
 * empty boxes in 6 wrapped rows, at 1280px and at 390px alike. A gallery of absences
 * is a memorial; it says nothing 34 times, in the position where the volunteers' own
 * words should be.
 *
 * plugins/system/otmarchive now collapses any run of two or more (see its RUN_MIN,
 * with the measured distribution) into `<p class="otm-missing-run">`. Article 403 is
 * now two single chips and four lines: 3, 4, 5 and 19.
 *
 * The line is DASHED, like the chip's own border, because it means the same thing —
 * something is absent here — and it is set in the same muted grey at the same small
 * size, so it reads as a caption of the text rather than as an interruption of it.
 * ------------------------------------------------------------------------- */
.otm-missing-run {
	display: flex;
	align-items: center;
	gap: 0.6em;
	flex-wrap: wrap;
	margin: 1.1em 0;
	color: #6b7280;
	font-size: 0.8em;
	line-height: 1.5;
}

/* The rule itself: a flexible hairline that finishes the line out to the measure.
   ⚠️ On the ::after and never as a border on the paragraph — a border-bottom under the
   whole box draws under the wrapped chips too, and reads as a table rule. */
.otm-missing-run::after {
	content: "";
	flex: 1 1 40px;
	border-top: 1px dashed #c3c8ce;
}

.otm-missing-run b {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-weight: 700;
	color: #4b5563;
}

/*
 * What is LEFT after the collapse, and it is deliberately still a chip.
 *
 * Two shapes reach this rule: the 2,224 paragraphs that hold exactly one lost
 * photograph — one absence in one place is not a grid, and a whole ruled sentence
 * would be louder than the chip it replaced — and the 33 runs whose markers all still
 * carry a LIVE link, which the collapse never swallows because a link is the last
 * thing at that position a reader can follow. `line-height` rather than `margin`
 * between wrapped lines, so the rare multi-chip row stays compact.
 */
.otm-missing-row {
	margin: 0.5em 0;
	line-height: 2.1;
}

/* Two rows that survived as neighbours (different parents, a list between them) should
   still read as one group rather than two paragraphs. */
.otm-missing-row + .otm-missing-row {
	margin-top: -0.25em;
}

/*
 * ---------------------------------------------------------------------------
 * PHONE WIDTHS.
 *
 * ⚠️ THIS BLOCK USED TO BE THE MITIGATION AND IS NOW ONLY A DETAIL. 390 px was the
 * width where the "scannable index" property was lost — article 403's 19-chip row
 * rendered as 10 stacked rows of 2 identical chips, 336 px tall — and the honest thing
 * a stylesheet could do was shrink the chip and buy back 80 px of it. The arithmetic
 * behind that is unchanged and is the reason CSS was never going to be the answer: a
 * 17-character chip is ~131 px here against a ~340 px column, three across needs a
 * ~9.8 px font, and flex, grid and `auto-fill` only reach three-across by wrapping the
 * label to two lines inside each chip, which costs the same height and reads worse.
 *
 * That run is now ONE LINE at every width (`.otm-missing-run`, above), so what is left
 * to shrink is the single chip and the rare live-link row.
 *
 * ⚠️ The note is deliberately NOT shrunk. It is one sentence per article and it is the
 * thing that has to stay readable when everything around it is an 11 px label.
 * ------------------------------------------------------------------------- */
@media (max-width: 480px) {
	.otm-missing-image {
		padding: 0.05em 0.35em;
		font-size: 0.72em;
	}

	.otm-missing-row {
		line-height: 1.6;
	}
}

/*
 * The one honest sentence, once per article, above the body.
 *
 * Quieter than the article and louder than a chip: that ordering is the entire
 * design. It is information the reader needs once, not a warning.
 */
.otm-missing-note {
	margin: 0 0 1.25em;
	padding: 0.5em 0 0.5em 0.9em;
	border-left: 3px solid #d7dce2;
	color: #5b6470;
	font-size: 0.875em;
	font-style: italic;
	line-height: 1.5;
}

/*
 * The articles whose TEXT did not survive either (import.php). Same family, same
 * volume — it had no styling before this file either.
 *
 * ⚠️ MEASURED in the live database: **1** article carries this note today (legacy 18,
 * the only source record with a literally empty `html`). It is styled anyway because
 * the guard that emits it is a permanent rule, not a one-off — a data refresh that
 * drops a body would produce more, and an unstyled notice would then be the loudest
 * thing on that page. This comment used to say 43, which is the count of source
 * articles that are markup-or-placeholder ONLY (docs/03 §6) — a different set, and
 * 42 of them have a placeholder and therefore never reach this branch.
 */
.otm-empty-body {
	color: #5b6470;
	font-size: 0.875em;
	font-style: italic;
}

/* ---------------------------------------------------------------------------
 * The archive's video embeds — import/lib/sanitise.php's otm_youtube_iframe().
 * A 16:9 box that scales, because the source markup carried fixed pixel widths that
 * S8 removes and nothing then constrains the iframe at all.
 *
 * 🔴 `display: block` IS LOAD-BEARING, NOT TIDINESS. Pipeline 2.3.0 changed the
 * wrapper from `<figure>` to `<span>` because 12 of the 28 embeds are stored inside a
 * `<p>` or an `<a>`, where a `<figure>` is illegal and every browser was ejecting it
 * to block level. A span is phrasing content and therefore INLINE by default: without
 * this line the wrapper has no box, `margin` and `max-width` are ignored on it, and
 * the iframe below inherits its width from a zero-height inline parent. The symptom
 * is a video that renders as a sliver or collapses entirely — a CSS bug that looks
 * like a broken embed.
 * ------------------------------------------------------------------------- */

.otm-video {
	display: block;
	margin: 1em 0;
	max-width: 100%;
}

.otm-video iframe {
	display: block;
	width: 100%;
	aspect-ratio: 16 / 9;
	height: auto;
	border: 0;
}

/* ===========================================================================
 * ΜΕΤΩΠΑ — the site design.
 *
 * Everything above this line is the 2004–2020 archive's lost-photograph
 * treatment and predates the design; everything below is «Μέτωπα». They share a
 * file because Cassiopeia declares exactly ONE user stylesheet
 * (joomla.asset.json:74, `template.user` → user.css, weight 500, loaded after
 * template.css) and that is the whole styling mechanism on this site: no child
 * template, no #__template_styles row, no !important.
 *
 * 🔴 THREE RULES THIS FILE DOES NOT BREAK, EACH ALREADY PAID FOR ONCE:
 *
 * 1. NO `100vw`, ANYWHERE — AND THAT IS THE RULE, NOT "no viewport unit". The
 *    design is five full-bleed bands. `width:100vw; margin-left:calc(50% - 50vw)`
 *    is the obvious way to build one and it is a trap: 100vw INCLUDES the
 *    scrollbar, so every band overflows by ~15px and the page scrolls sideways —
 *    invisible in a screenshot, because the overflow is off-canvas. Cassiopeia's
 *    own `.full-width` (`grid-column: full-start / full-end`) does the same job
 *    with a grid line, and index.php puts it on `.container-component`.
 *
 *    ⚠️ THIS PARAGRAPH USED TO CLAIM "there is no viewport unit anywhere in this
 *    file", AND IT WAS FALSE IN A WAY ANYONE CAN CHECK IN ONE GREP: `vw` appears
 *    **28** times in declarations here, plus one `min(72vh, 640px)`. Every one of
 *    them is inside a `clamp()` between two px bounds — gaps, paddings, font sizes
 *    and the two search fields — so none can grow past its ceiling and none is a
 *    full-bleed width or a negative margin, which is the thing that overflows. A
 *    doc that is wrong in a checkable way is worse than no doc: the next person
 *    greps, finds 28 hits, and stops believing the rest of the file.
 *
 *    THE ASSERTION IS A RANGE, NOT A WIDTH: `documentElement.scrollWidth <=
 *    innerWidth` at **320 / 360 / 390 / 768 / 1280**. It used to be run at 390 and
 *    up, and 320 was the width that failed — the masthead brand, for a completely
 *    unrelated reason (see `.otm-brand`).
 *
 * 2. SPECIFICITY, NOT WEIGHT. Loading after template.css only wins TIES.
 *    Cassiopeia sets font-family on `body` and on the heading elements, so a
 *    selector here has to match at equal or greater specificity or the page comes
 *    out looking almost right — which is the worst outcome available.
 *
 * 3. GREEK UPPERCASE HAPPENS HERE AND NOWHERE ELSE. Every eyebrow and band
 *    heading is `text-transform: uppercase` under `<html lang="el-gr">`, which
 *    applies Unicode's Greek tailoring and correctly DROPS the tonos:
 *    «Χωρίς μεσάζοντες» → ΧΩΡΙΣ ΜΕΣΑΖΟΝΤΕΣ. The PHP equivalent does not:
 *    measured in this container, `mb_strtoupper('Χωρίς μεσάζοντες')` returns
 *    **ΧΩΡΊΣ ΜΕΣΆΖΟΝΤΕΣ** — misspelled Greek, in the largest type on the page,
 *    raising nothing. Never move this into PHP.
 * ======================================================================== */

/* ---------------------------------------------------------------------------
 * THE TYPE SYSTEM — three faces, one family, ZERO NEW BYTES.
 *
 * All three already ship inside the image at media/vendor/roboto-fontface, and
 * the licence is read out of the binaries' own name table (ID 13): Apache 2.0.
 * No CDN, no new asset, nothing for the CSP to allow.
 *
 * 🔴 COVERAGE MEASURED PER FACE AGAINST THE REAL CORPUS. The figure that used to
 * stand here — "10 of the 229 missing", quoted once for all three faces —
 * contradicted itself in the next sentence by naming the tenth as `→`, "which is
 * not in the corpus at all". Re-measured by reading each binary's own `cmap` and
 * the corpus out of the live database (tags stripped, entities decoded); the
 * per-face split is the part that matters, and it is why one character got past
 * two earlier counts. docs/10 §6f has the method and the full reconciliation.
 *
 *                              cmap  glyphs   pre-import   post-import (this DB)
 *   Roboto-Regular/Medium/Bold   896   1294   10 missing      3 missing
 *   Roboto-Condensed-Bold        896   1294   10 missing      3 missing
 *   Roboto-Slab-Bold             881   1052   11 missing      4 missing → now 3
 *
 * That reconciles the older reports too: "896 glyphs" and "1294 glyphs" were both
 * right, about different columns of the same file (cmap codepoints vs numGlyphs).
 *
 * Seven of the pre-import misses are import damage or canonical equivalents and are
 * normalised at import (S2b, pipeline 2.5.0, in import/lib/sanitise.php). The tenth
 * is `U+1F5BC 🖼`, the emoji in the archive extractor's placeholder, which S4
 * removes. 🔴 THE ELEVENTH IS WHY THE FIGURE HAS TO BE PER FACE: ROBOTO SLAB — the
 * NUMERALS face this design leans on — LACKS `U+2010 HYPHEN`, WHICH IS IN THE
 * CORPUS (article 1389, «40% ‐ 80%»). It is normalised to `-` at S2b as of 2.5.0.
 *
 * What is left is three genuine POLYTONIC Greek letters in two real quotations,
 * deliberately left to system fallback rather than silently monotonised — the same
 * three in all three faces.
 *
 * 🔴 AND ONE DESIGN CONSTRAINT, WHICH IS A SEPARATE FACT AND WAS THE SOURCE OF THE
 * CONTRADICTION: `→` (U+2192) IS NOT IN ANY WEIGHT OF ROBOTO, and it is not in the
 * corpus either. Neither is ↗, ⟶, ⇢, ▸, ▶, ►, ❯ or ≫ — measured, all of them. The
 * design's «Διαβάστε τη δράση →» would have rendered from whatever font the
 * browser fell back to, at a different weight and a different baseline from the
 * words beside it. Every forward affordance on this site therefore uses `›`
 * (U+203A), which Roboto has and which sits in the same register as the «»
 * the Greek text uses constantly.
 * ------------------------------------------------------------------------- */

@font-face {
	font-family: "OTM Sans";
	src: url("../../../../vendor/roboto-fontface/fonts/roboto/Roboto-Regular.woff2") format("woff2");
	font-weight: 400;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: "OTM Sans";
	src: url("../../../../vendor/roboto-fontface/fonts/roboto/Roboto-Medium.woff2") format("woff2");
	font-weight: 500;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: "OTM Sans";
	src: url("../../../../vendor/roboto-fontface/fonts/roboto/Roboto-Bold.woff2") format("woff2");
	font-weight: 700;
	font-style: normal;
	font-display: swap;
}

@font-face {
	font-family: "OTM Display";
	src: url("../../../../vendor/roboto-fontface/fonts/roboto-condensed/Roboto-Condensed-Bold.woff2") format("woff2");
	font-weight: 700;
	font-style: normal;
	font-display: swap;
}

/*
 * The numerals get their OWN face, and that is the load-bearing typographic
 * decision of the whole design rather than a flourish. This archive has no
 * photographs — not 87% missing, 100% — so what a photograph would have done on a
 * card is done by the date and the read count. Set in the body face they read as
 * mouse-print metadata; set in a slab at a larger size with tabular figures they
 * are graphic material, and a column of them lines up.
 */
@font-face {
	font-family: "OTM Slab";
	src: url("../../../../vendor/roboto-fontface/fonts/roboto-slab/Roboto-Slab-Bold.woff2") format("woff2");
	font-weight: 700;
	font-style: normal;
	font-display: swap;
}

/* ---------------------------------------------------------------------------
 * THE PALETTE. Four colours, no gradients, no rounded cards, no accent bars.
 *
 * RED is sampled from otoposmou.gr itself — a pixel histogram of the live site
 * returns a dominant brick-red cluster at (144,12,0)–(168,24,0). It is the
 * organisation's own colour, and it means NOW.
 *
 * SLATE is the archive register. Two colours doing semantic work is the entire
 * system: a mixed listing tells you at a glance which items are current.
 *
 * 🔴 THE CURRENT/ARCHIVE BOUNDARY IS RELATIVE, NOT A YEAR. See
 * OTM_CURRENT_MONTHS in otm/lib.php. Written as "before 2019 is slate" it
 * inverts itself the first time the volunteers publish: the archive goes wholly
 * slate, the front page wholly red, and the distinction stops carrying any
 * information at all.
 * ------------------------------------------------------------------------- */

:root {
	--otm-ink: #14171a;
	--otm-red: #a81c10;
	--otm-red-d: #84130a;
	--otm-slate: #2c5058;
	--otm-ground: #f1efe9;
	--otm-rule: #d8d4cb;
	--otm-rule-dark: #2f353b;
	--otm-muted: #5b6470;
	--otm-paper: #fff;
	--otm-wrap: 1280px;
	--otm-gut: clamp(16px, 4vw, 40px);
}

/*
 * ⚠️ `body` and not `:root` — Cassiopeia sets font-family ON BODY, so a rule on
 * :root loses to it at every element and the page renders in the stock stack
 * while looking deliberate. Same reason the heading rule below names the
 * elements rather than relying on inheritance.
 */
body.site {
	font-family: "OTM Sans", system-ui, -apple-system, "Segoe UI", sans-serif;
	color: var(--otm-ink);
	background: var(--otm-paper);
	font-size: 17px;
	line-height: 1.55;
	-webkit-font-smoothing: antialiased;
}

body.site h1,
body.site h2,
body.site h3,
body.site h4,
body.site .otm-navlink,
body.site .otm-eyebrow {
	font-family: "OTM Display", "Arial Narrow", system-ui, sans-serif;
	font-weight: 700;
	letter-spacing: 0;
	line-height: 1.08;
}

body.site a {
	color: inherit;
	text-decoration: none;
}

body.site a:hover,
body.site a:focus {
	color: var(--otm-red);
	text-decoration: underline;
	text-underline-offset: 3px;
}

/* ---------------------------------------------------------------------------
 * THE BAND / WRAP PAIR. This is the only layout primitive in the design.
 *
 * `.otm-band` paints edge to edge; `.otm-wrap` holds the content to a measure and
 * pads it. `.otm-wrap` is a MAX-WIDTH and a padding — never a width — so it can
 * never be the thing that overflows.
 * ------------------------------------------------------------------------- */

.otm-wrap {
	max-width: var(--otm-wrap);
	margin-inline: auto;
	padding-inline: var(--otm-gut);
	box-sizing: border-box;
}

.otm-band {
	padding-block: clamp(28px, 5vw, 64px);
}

/*
 * 🔴 Cassiopeia's `.grid-child` carries `padding: 2.5rem .5em`, which would inset
 * every band by 8px and put a white gutter down both sides of the ink block — a
 * defect that reads as "the full-bleed did not work" rather than as padding.
 */
.site-grid > .container-component.full-width {
	padding: 0;
	max-width: none;
}

.site-grid {
	margin-bottom: 0;
	row-gap: 0;
}

/* ⚠️ Clipped rather than pushed to `left: -9999px`. In an RTL context a negative
   inline offset extends the scroll box, which is the same overflow class as the
   pager above — and it is a rule that is easy to copy into a site that is RTL. */
.otm-skip {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip-path: inset(50%);
	white-space: nowrap;
}

.otm-skip:focus {
	inset-inline-start: 8px;
	top: 8px;
	width: auto;
	height: auto;
	clip-path: none;
	z-index: 50;
	background: var(--otm-red);
	color: #fff;
	padding: 8px 14px;
}

/* --------------------------------------------------------------- MASTHEAD */

.otm-header {
	background: var(--otm-paper);
	border-bottom: 2px solid var(--otm-ink);
}

.otm-masthead-in {
	display: flex;
	align-items: center;
	gap: clamp(12px, 2vw, 28px);
	padding-block: 14px;
	flex-wrap: wrap;
}

/*
 * 🔴 `flex: 0 1 auto`, AND THE `1` IS THE WHOLE FIX FOR A SITEWIDE 320px OVERFLOW.
 *
 * MEASURED at 320px on /, /diodia-13 and /draseis: `documentElement.scrollWidth` 325
 * against `innerWidth` 320. The offender was this element — with `flex-shrink: 0` the
 * brand holds its MAX-CONTENT width, and its widest child is the tagline «Εθελοντική
 * Ομάδα Δράσης Ν. Πιερίας» at 233px, which puts the box's right edge at 325 inside a
 * 304px content column. Allowing it to shrink lets the tagline wrap to a second line
 * at that one width and changes nothing at any other.
 *
 * ⚠️ `min-width: 0` on both this and `.otm-word` is not belt-and-braces. A flex item's
 * automatic minimum size is its MIN-CONTENT width, so `flex-shrink: 1` alone stops at
 * the longest unbreakable word and the page still overflows — by less, which is worse,
 * because 3px is invisible in a screenshot in a way 5px at least is not.
 *
 * ⚠️ AND THE ASSERTION IS NOW A RANGE, NOT A WIDTH. 360/390/600/768/1024/1280 were all
 * clean while this was broken: the previous check ran at exactly the widths the design
 * was drawn at, so the one width nobody drew at was the one that failed.
 */
.otm-brand {
	display: flex;
	align-items: center;
	gap: 12px;
	flex: 0 1 auto;
	min-width: 0;
}

body.site .otm-brand:hover {
	text-decoration: none;
	color: inherit;
}

/*
 * PLACEHOLDER. The client's mark is blocked (CLAUDE.md), so the site ships a
 * two-letter type block that says so on its own face, in 6px caps, and says it
 * again in the footer's legal line. A stock icon or a drawn logo here would be a
 * proposal nobody made.
 */
.otm-mark {
	display: block;
	background: var(--otm-red);
	color: #fff;
	font-family: "OTM Display", sans-serif;
	font-size: 20px;
	line-height: 1;
	padding: 9px 8px 4px;
	text-align: center;
	letter-spacing: 0.02em;
}

.otm-mark em {
	display: block;
	font-family: "OTM Sans", sans-serif;
	font-style: normal;
	font-weight: 500;
	font-size: 5.5px;
	letter-spacing: 0.14em;
	margin-top: 3px;
	opacity: 0.8;
}

.otm-word {
	display: block;
	min-width: 0;   /* see .otm-brand — without this the shrink stops at min-content */
	font-family: "OTM Display", sans-serif;
	font-size: clamp(20px, 2.6vw, 27px);
	text-transform: uppercase;
	line-height: 1.05;
}

.otm-tagline {
	display: block;
	font-family: "OTM Sans", sans-serif;
	font-weight: 400;
	font-size: 11.5px;
	letter-spacing: 0.06em;
	text-transform: none;
	color: var(--otm-muted);
	margin-top: 3px;
}

/* ------------------------------------------------------------------- NAV */

.otm-nav {
	display: flex;
	align-items: center;
	gap: clamp(10px, 1.8vw, 26px);
	margin-inline-start: auto;
	flex-wrap: wrap;
	/* Shrinks before it wraps to a second row. Without this the nav holds its
	   max-content width, the search field is pushed onto its own line, and the
	   masthead grows a 60px empty band that reads as a layout bug. */
	min-width: 0;
	justify-content: flex-end;
}

body.site .otm-navlink {
	font-size: 13.5px;
	letter-spacing: 0.05em;
	text-transform: uppercase;
	padding-block: 6px;
	border-bottom: 4px solid transparent;
	cursor: pointer;
	white-space: nowrap;
}

body.site .otm-navlink:hover,
body.site .otm-navlink:focus,
body.site .otm-navlink.is-active {
	color: var(--otm-ink);
	border-bottom-color: var(--otm-red);
	text-decoration: none;
}

/* ------------------------------------------------- THE ΔΡΑΣΕΙΣ MEGA-PANEL
 *
 * 🔴 A `<details>` ELEMENT AND NOT ONE LINE OF JAVASCRIPT. It opens on click and
 * on Enter, is focusable, is announced as a disclosure, and works with scripting
 * off — so the "forty campaigns in four groups" promise holds unconditionally
 * instead of holding only while a script runs. This object is what replaces the
 * 45-item sidebar tree, and unlike the tree it is on every page and every row
 * carries how much work is in it and which years it ran.
 * ----------------------------------------------------------------------- */

/*
 * ⚠️ THE PANEL IS POSITIONED AGAINST THE MASTHEAD, NOT AGAINST ITS OWN SUMMARY.
 * `position: relative` on `.otm-mega` plus `left: 50%; transform: translateX(-50%)`
 * centres a 1280px panel on the SUMMARY — which sits wherever the nav item happens
 * to be — so at 1280px the first column («Ο τόπος», the largest group) was clipped
 * off the left edge of the page. Anchoring to the masthead and letting the panel's
 * own `.otm-wrap` do the centring is the fix, and it also means the panel keeps its
 * columns aligned with the rest of the page.
 */
.otm-masthead {
	position: relative;
}

.otm-mega > summary {
	list-style: none;
	display: inline-block;
}

.otm-mega > summary::-webkit-details-marker {
	display: none;
}

.otm-mega[open] > summary {
	border-bottom-color: var(--otm-red);
}

.otm-mega-body {
	position: absolute;
	/* ⚠️ Insets, not a width. `width: 100vw` here would be the scrollbar bug in the
	   one place it is most tempting; `inset-inline: 0` against the masthead gives the
	   page's own width by construction and can never exceed it. */
	inset-inline: 0;
	top: 100%;
	background: var(--otm-ink);
	color: #fff;
	z-index: 30;
	box-shadow: 0 18px 40px rgba(0, 0, 0, 0.28);
	border-top: 2px solid var(--otm-red);
	/* ⚠️ At 390px the four groups stack into one column ~1,500px tall. An absolutely
	   positioned box does not grow the document, so without this the last fifteen
	   campaigns are simply unreachable — the panel LOOKS complete in a screenshot and
	   is not. `vh` is safe here in a way `vw` never is: the scrollbar is horizontal
	   nowhere. No effect at 1280px, where the panel is ~520px tall. */
	max-height: min(72vh, 640px);
	overflow-y: auto;
	overscroll-behavior: contain;
}

.otm-mega-grid {
	display: grid;
	grid-template-columns: repeat(4, minmax(0, 1fr));
	gap: 0 clamp(16px, 2vw, 32px);
	padding-block: 26px 30px;
}

body.site .otm-mega-col h3 {
	font-size: 13px;
	letter-spacing: 0.09em;
	text-transform: uppercase;
	color: var(--otm-red);
	padding-bottom: 8px;
	margin: 0 0 10px;
	border-bottom: 1px solid var(--otm-rule-dark);
}

.otm-mega-col.is-spare h3 {
	color: #8a939c;
	font-size: 11.5px;
}

.otm-mega-hint {
	font-size: 11.5px;
	color: #8a939c;
	margin: -4px 0 8px;
}

.otm-mega-col ul {
	list-style: none;
	margin: 0;
	padding: 0;
}

.otm-mega-col li {
	padding-block: 4px 6px;
}

.otm-mega-col a {
	display: flex;
	justify-content: space-between;
	align-items: baseline;
	gap: 8px;
	color: #fff;
	font-size: 14px;
	line-height: 1.25;
}

body.site .otm-mega-col a:hover,
body.site .otm-mega-col a:focus {
	color: #fff;
	text-decoration: none;
}

body.site .otm-mega-col a:hover .otm-mega-name,
body.site .otm-mega-col a:focus .otm-mega-name {
	text-decoration: underline;
	text-underline-offset: 3px;
}

.otm-mega-n {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 12px;
	color: #97a0a8;
	flex: 0 0 auto;
}

/*
 * 🔴 THE PANEL'S OWN LINK TO /draseis. A `<summary>` is a disclosure control, not a
 * link, so before this line the header item «Οι δράσεις μας» led NOWHERE — the page
 * behind it had zero inbound links anywhere on the site and existed only for someone
 * typing the URL. Ruled off from the forty rows above it so it reads as the way out of
 * the panel rather than as a forty-first campaign.
 */
.otm-mega-foot {
	border-top: 1px solid var(--otm-rule-dark);
	padding-block: 12px 16px;
}

.otm-mega-foot a {
	font-family: "OTM Display", sans-serif;
	text-transform: uppercase;
	letter-spacing: 0.07em;
	font-size: 12.5px;
	color: #fff;
}

/* --------------------------------------------------------- THE SPAN BAR
 *
 * A campaign's years drawn on a shared 2004→2020 axis. Percentages only — the
 * bar cannot overflow its column because it has no length of its own.
 */
.otm-span {
	display: block;
	position: relative;
	height: 5px;
	margin-top: 4px;
	background: rgba(0, 0, 0, 0.08);
}

.otm-span i {
	position: absolute;
	top: 0;
	bottom: 0;
	background: var(--otm-red);
}

.otm-mega-col .otm-span {
	background: rgba(255, 255, 255, 0.12);
}

.otm-mega-col .otm-span i {
	background: #6d8f98;
}

/* ---------------------------------------------------------------- SEARCH */

.otm-search {
	flex: 0 0 auto;
}

.otm-search .mod-finder,
.otm-search form {
	margin: 0;
}

.otm-search input[type="text"] {
	border: 1px solid var(--otm-rule);
	border-radius: 0;
	padding: 7px 10px;
	font-size: 13.5px;
	width: clamp(150px, 18vw, 230px);
	background: var(--otm-ground);
}

.otm-search .btn,
.otm-search button {
	border-radius: 0;
	background: var(--otm-ink);
	border-color: var(--otm-ink);
	color: #fff;
}

/* ------------------------------------------------------- THE ACTION STRIP
 *
 * The red band under the masthead. Their live site has this element today as a
 * baked JPEG that nobody can edit; here it is ONE mod_custom in position
 * `banner`, i.e. the object a volunteer opens in Περιεχόμενο → Ενότητες
 * ιστοτόπου. Its CONTENT is blocked on the client, so what ships is the strip
 * plus a line that says so — never an invented call to action, never a link to a
 * page that does not exist.
 */
.otm-band-action {
	background: var(--otm-red);
	color: #fff;
	padding-block: 14px;
}

.otm-band-action p {
	margin: 0;
	font-size: 15px;
}

.otm-band-action a {
	color: #fff;
	text-decoration: underline;
}

.otm-placeholder {
	font-style: italic;
	opacity: 0.92;
}

/* ----------------------------------------------------------- BREADCRUMBS */

.otm-crumbs {
	border-bottom: 1px solid var(--otm-rule);
	background: var(--otm-paper);
}

/* «Βρίσκεστε εδώ: Αρχική» on the front page is a crumb trail with one crumb,
   pointing at the page it is on. The module stays published for every other view. */
body.site.view-featured .otm-crumbs {
	display: none;
}

.otm-crumbs .breadcrumb {
	margin: 0;
	padding: 9px 0;
	background: none;
	font-size: 11px;
	letter-spacing: 0.07em;
	text-transform: uppercase;
	color: var(--otm-muted);
	flex-wrap: wrap;
}

.otm-crumbs .breadcrumb a {
	color: var(--otm-muted);
}

/* ------------------------------------------------------------- LEAD BLOCK
 *
 * The hero, and it is made of type and numbers because there is nothing else:
 * ZERO of the 1,821 archive articles carries an image. The same block accepts a
 * background photograph later through one class, with no structural change.
 */
.otm-band-lead {
	background: var(--otm-ink);
	color: #fff;
}

.otm-lead {
	display: grid;
	grid-template-columns: minmax(0, 1fr) 300px;
	gap: clamp(20px, 4vw, 56px);
	align-items: start;
}

body.site .otm-eyebrow,
body.site .otm-kicker > span,
body.site .otm-kicker > a {
	display: inline-block;
	font-family: "OTM Display", sans-serif;
	font-size: 12.5px;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--otm-red);
	border-top: 3px solid var(--otm-red);
	padding-top: 7px;
	margin-bottom: 12px;
}

.otm-band-lead .otm-eyebrow {
	color: #ff6a58;
	border-top-color: var(--otm-red);
}

body.site .otm-lead-title {
	font-size: clamp(34px, 4.55vw, 60px);
	margin: 0 0 16px;
	max-width: 20ch;
}

body.site .otm-lead-title a {
	color: #fff;
}

.otm-lead-stand {
	font-size: clamp(16px, 1.5vw, 19px);
	line-height: 1.5;
	color: #cfd4d9;
	max-width: 56ch;
	margin: 0 0 18px;
}

.otm-lead-meta {
	display: flex;
	align-items: baseline;
	gap: 16px;
	flex-wrap: wrap;
	margin: 0;
}

.otm-datum,
.otm-reads,
.otm-reg-n,
.otm-reg-years,
.otm-row-reads {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-weight: 700;
}

.otm-band-lead .otm-datum,
.otm-band-lead .otm-reads {
	font-size: 13px;
	color: #97a0a8;
}

/*
 * ⚠️ `display: inline-block` and a real padding, because on an INLINE element the
 * 2px rule sits on the text baseline — which in a condensed uppercase face lands
 * through the descenders and reads as a strikethrough. Visible only in the
 * screenshot of the article page's «ΟΛΗ Η ΔΡΑΣΗ ›», where it made the link look
 * disabled.
 */
body.site .otm-more {
	display: inline-block;
	font-family: "OTM Display", sans-serif;
	text-transform: uppercase;
	letter-spacing: 0.07em;
	font-size: 13px;
	color: #fff;
	border-bottom: 2px solid var(--otm-red);
	padding-bottom: 5px;
	text-decoration: none;
}

body.site .otm-more:hover,
body.site .otm-more:focus {
	border-bottom-color: var(--otm-ink);
	text-decoration: none;
}

.otm-band-more .otm-more:hover,
.otm-band-more .otm-more:focus {
	color: var(--otm-red);
	border-bottom-color: var(--otm-red);
}

/*
 * THE LEDGER — the numbers that stand in for the photograph. Every figure is
 * queried, never typed: an earlier draft carried «42 δράσεις» (three of which
 * are not campaigns) and «22 χρόνια» (against an archive that starts in 2004),
 * and a hero made of figures fails at its own thesis on one wrong figure.
 */
.otm-ledger {
	border-inline-start: 1px solid #2f353b;
	padding-inline-start: clamp(16px, 2vw, 30px);
}

.otm-ledger p {
	margin: 0 0 16px;
}

.otm-ledger b {
	display: block;
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 34px;
	line-height: 1.05;
}

.otm-ledger span {
	display: block;
	font-size: 12px;
	letter-spacing: 0.09em;
	text-transform: uppercase;
	color: #97a0a8;
	margin-top: 2px;
}

/* -------------------------------------------------------- BAND HEADINGS */

body.site .otm-bandhead {
	font-size: clamp(17px, 2vw, 22px);
	letter-spacing: 0.06em;
	text-transform: uppercase;
	margin: 0 0 20px;
	padding-bottom: 10px;
	border-bottom: 2px solid var(--otm-ink);
}

body.site .otm-bandhead small {
	font-family: "OTM Slab", Georgia, serif;
	font-size: 14px;
	color: var(--otm-muted);
	margin-inline-start: 8px;
}

body.site .otm-subhead {
	font-size: 13px;
	letter-spacing: 0.09em;
	text-transform: uppercase;
	margin: 34px 0 12px;
}

/* ------------------------------------------------------------- THE CARDS
 *
 * A ruled table, not floating boxes: one shared ground, 1px rules between cells.
 * Three type sizes in one block do the work that photo-crop variation does on a
 * site that has photographs — a text grid at one size is a list, a text grid at
 * three sizes is a front page.
 *
 * 🔴 THE PHOTOGRAPH SLOT IS ZERO-HEIGHT WHEN THERE IS NO PHOTOGRAPH, and the
 * rows do NOT stretch to their tallest sibling. An earlier version of this design
 * put a hatched "the photograph was not preserved" frame in the card; its own
 * screenshot showed one card carrying the frame and its two neighbours carrying
 * 200px of dead white space. Since zero archive articles have an image, that
 * frame would render on the front page's most valuable object every single time.
 * Either a real <img> or nothing at all.
 */
/*
 * ⚠️ TWELVE COLUMNS, NOT THREE. The block is one ruled table whose first row is
 * 6|3|3 and whose second is 3|3|3|3 — the scale contrast that does the work a
 * photo grid gets from crop variation. A `2fr 1fr 1fr` grid cannot express that:
 * seven cards land 3+3+1 and the last row is a single card two thirds empty.
 * `grid-auto-rows: min-content` is what stops a row stretching every card to the
 * height of its tallest sibling, which is the other half of the same defect.
 */
.otm-cards {
	display: grid;
	gap: 1px;
	background: var(--otm-rule);
	border-block: 1px solid var(--otm-rule);
	grid-template-columns: repeat(12, minmax(0, 1fr));
	grid-auto-rows: min-content;
}

.otm-cards > .otm-card {
	grid-column: span 3;
}

.otm-cards > .otm-card.is-big {
	grid-column: span 6;
}

/*
 * ⚠️ EVERY CARD GRID IS THE SAME TWELVE COLUMNS, and only the SPANS differ. Mixing
 * `grid-template-columns` per variant with `grid-column: span N` on the children is
 * the defect this replaced: at 390px the template collapsed to one column while the
 * spans stayed at 3 and 6, so the browser manufactured implicit columns and every
 * card grew ~400px of empty space below its text. Visible in the 390px screenshot as
 * two cards per viewport; invisible to every element count, which found seven.
 */
.otm-cards-3 > .otm-card {
	grid-column: span 4;
}

.otm-cards-4 > .otm-card {
	grid-column: span 3;
}

.otm-card {
	background: var(--otm-paper);
	padding: 0 clamp(12px, 1.4vw, 20px) 18px;
	display: flex;
	flex-direction: column;
}

.otm-card:hover {
	background: var(--otm-ground);
}

/* The card's coloured band. This is what supplies the repeating colour rhythm a
   photo grid gets from its pictures — blocks at consistent positions, which is
   the actual perceptual job the photographs were doing. */
.otm-band-tag {
	display: flex;
	justify-content: space-between;
	align-items: baseline;
	gap: 8px;
	margin: 0 clamp(-20px, -1.4vw, -12px) 14px;
	padding: 6px clamp(12px, 1.4vw, 20px) 5px;
	background: var(--otm-slate);
	color: #fff;
	font-family: "OTM Display", sans-serif;
	font-size: 11.5px;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	min-height: 24px;
}

.otm-band-tag.is-now {
	background: var(--otm-red);
}

.otm-band-tag b {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 12px;
	flex: 0 0 auto;
}

.otm-shot {
	margin: 0 0 12px;
}

.otm-shot img {
	display: block;
	width: 100%;
	height: auto;
}

body.site .otm-card h3 {
	font-size: 18.5px;
	margin: 0 0 8px;
}

body.site .otm-card.is-mid h3 {
	font-size: 22px;
}

body.site .otm-card.is-big h3 {
	font-size: clamp(24px, 2.6vw, 35px);
}

.otm-card-ex {
	font-size: 14px;
	line-height: 1.5;
	color: #3d444b;
	margin: 0 0 12px;
}

.otm-card.is-big .otm-card-ex {
	font-size: 16px;
}

.otm-card-meta {
	margin: auto 0 0;
	display: flex;
	gap: 12px;
	flex-wrap: wrap;
	font-size: 12px;
	color: var(--otm-muted);
	padding-top: 8px;
	border-top: 1px solid var(--otm-rule);
}

/* --------------------------------------------------------- THE REGISTER
 *
 * 40 links drawn as a chart. Every row carries the two facts that let a reader
 * triage instantly: how much work is in it, and when it happened.
 *
 * ⚠️ CSS MULTI-COLUMN, NOT GRID. Columns fill top-to-bottom, so the single
 * count-descending ranking reads 1–14 down column one, 15–28 down column two. A
 * 3-column GRID distributes the same rows ROW-first and produces three
 * independent-looking descents, and no rule then tells a reader which column a
 * name is in — they have to scan all three.
 */
.otm-band-register {
	background: var(--otm-ground);
}

.otm-band-register.is-spare {
	background: var(--otm-paper);
}

.otm-register {
	columns: 3;
	column-gap: clamp(20px, 3vw, 44px);
	list-style: none;
	margin: 0;
	padding: 0;
}

.otm-register li {
	break-inside: avoid;
	padding: 7px 0 8px;
	border-bottom: 1px solid var(--otm-rule);
	font-size: 14px;
}

.otm-register li a {
	display: flex;
	justify-content: space-between;
	align-items: baseline;
	gap: 10px;
}

.otm-reg-name {
	font-family: "OTM Display", sans-serif;
	color: var(--otm-slate);
}

/* ⚠️ There is deliberately no `li.is-top` rank rule here. See the long note in
   html/com_content/featured/default.php: a top-twelve colour cliff lands on the
   column-2/3 boundary at 1280px and reads as an unstyled third column. */

.otm-reg-n {
	font-size: 12.5px;
	color: var(--otm-muted);
	flex: 0 0 auto;
}

.otm-reg-years {
	display: block;
	font-size: 10.5px;
	color: var(--otm-muted);
	margin-top: 3px;
}

/*
 * ⚠️ ONE LINE OF WORDS, NOT A DRAWN AXIS, and the screenshot is why. A 2004 … 2020
 * scale printed across the foot of the band reads as the axis for the WHOLE band —
 * but each of the three columns carries its own 2004→2020 track, so the labels line
 * up with nothing in columns two and three. Every row already prints its own year
 * range in figures beside the bar; what was missing was the sentence saying what the
 * bar is.
 */
.otm-axis {
	margin: 14px 0 0;
	font-size: 11.5px;
	color: var(--otm-muted);
}

/* ----------------------------------------------------------- THE ARCHIVE
 *
 * The search box is PROMOTED here, not deleted: it was a 200px sidebar module and
 * it is now a field in the masthead on every page plus a full-width field at the
 * head of this band. com_finder ships a Greek tokeniser and stemmer and the
 * import builds 56,514 stems — which is the honest answer for a 1,821-item long
 * tail, because nobody navigates 1,821 items by menu.
 */
.otm-band-archive {
	background: var(--otm-slate);
	color: #fff;
}

.otm-band-archive .otm-bandhead {
	border-bottom-color: rgba(255, 255, 255, 0.35);
}

.otm-bigsearch {
	display: flex;
	gap: 0;
	margin: 0;
	max-width: 720px;
}

.otm-bigsearch input[type="text"] {
	flex: 1 1 auto;
	min-width: 0;
	border: 0;
	padding: 14px 16px;
	font-size: 16px;
	font-family: inherit;
	background: #fff;
	color: var(--otm-ink);
}

.otm-bigsearch button {
	flex: 0 0 auto;
	border: 0;
	background: var(--otm-red);
	color: #fff;
	font-family: "OTM Display", sans-serif;
	text-transform: uppercase;
	letter-spacing: 0.08em;
	font-size: 13px;
	padding: 0 20px;
	cursor: pointer;
}

.otm-mostread {
	list-style: none;
	margin: 0;
	padding: 0;
	counter-reset: otm;
	columns: 3;
	column-gap: clamp(20px, 3vw, 44px);
}

.otm-mostread li {
	break-inside: avoid;
	counter-increment: otm;
	display: flex;
	justify-content: space-between;
	align-items: baseline;
	gap: 12px;
	padding: 8px 0;
	border-bottom: 1px solid rgba(255, 255, 255, 0.18);
	font-size: 14px;
	line-height: 1.3;
}

.otm-mostread li::before {
	content: counter(otm);
	font-family: "OTM Slab", Georgia, serif;
	font-size: 12px;
	color: #9fb8bd;
	flex: 0 0 1.6em;
}

.otm-mostread a {
	flex: 1 1 auto;
	color: #fff;
}

.otm-band-archive .otm-reads {
	font-size: 12.5px;
	color: #9fb8bd;
	flex: 0 0 auto;
}

/* --------------------------------------------------------- SECTION PAGES */

.otm-band-sectionhead {
	background: var(--otm-paper);
	padding-bottom: clamp(18px, 3vw, 32px);
}

.otm-kicker {
	display: flex;
	align-items: baseline;
	gap: 14px;
	flex-wrap: wrap;
	margin: 0 0 6px;
	font-size: 12px;
	color: var(--otm-muted);
}

.otm-kicker b {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	color: var(--otm-ink);
}

.otm-kicker > span:not(:first-child) {
	border: 0;
	padding: 0;
	margin: 0;
	color: var(--otm-muted);
	font-family: "OTM Sans", sans-serif;
	letter-spacing: 0;
	text-transform: none;
	font-size: 12px;
}

body.site .otm-section-title {
	font-size: clamp(32px, 5.4vw, 64px);
	margin: 0 0 14px;
	max-width: 22ch;
}

.otm-section-desc {
	max-width: 62ch;
	color: #3d444b;
	font-size: 16px;
}

.otm-rail {
	display: flex;
	gap: clamp(20px, 4vw, 60px);
	margin: 22px 0 0;
	padding-top: 16px;
	border-top: 1px solid var(--otm-rule);
	flex-wrap: wrap;
}

.otm-rail dt {
	font-size: 11px;
	letter-spacing: 0.09em;
	text-transform: uppercase;
	color: var(--otm-muted);
	font-weight: 400;
}

.otm-rail dd {
	margin: 2px 0 0;
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 28px;
	line-height: 1.1;
}

/* Counted filter chips — the second taxonomy level doing real navigational work
   instead of sitting in a tree. */
.otm-band-chips {
	background: var(--otm-ground);
	padding-block: 16px;
}

.otm-chips {
	display: flex;
	flex-wrap: wrap;
	gap: 8px;
}

.otm-chip {
	display: inline-flex;
	align-items: baseline;
	gap: 7px;
	max-width: 100%;
	border: 1px solid var(--otm-rule);
	background: var(--otm-paper);
	padding: 5px 10px;
	font-size: 13px;
	line-height: 1.3;
}

.otm-chip b {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 11px;
	color: var(--otm-muted);
	font-weight: 700;
}

body.site .otm-chip:hover,
body.site .otm-chip:focus,
.otm-chip.is-active {
	background: var(--otm-ink);
	border-color: var(--otm-ink);
	color: #fff;
	text-decoration: none;
}

.otm-chip.is-active b,
body.site .otm-chip:hover b {
	color: #b9c1c8;
}

/* THE DENSE INDEX — the answer to a 191-item campaign. A card grid that deep is a
   wall; a bare list is what the site has today. */
.otm-index {
	list-style: none;
	margin: 26px 0 0;
	padding: 0;
	border-top: 1px solid var(--otm-rule);
}

.otm-row {
	display: grid;
	grid-template-columns: 92px minmax(0, 1fr) 150px 78px;
	gap: 0 16px;
	align-items: baseline;
	padding: 12px 0;
	border-bottom: 1px solid var(--otm-rule);
}

.otm-row:hover {
	background: var(--otm-ground);
}

.otm-row .otm-datum {
	font-size: 12.5px;
	color: var(--otm-muted);
}

.otm-row-main a {
	font-family: "OTM Display", sans-serif;
	font-size: 17px;
	line-height: 1.2;
	display: block;
}

.otm-row-ex {
	display: block;
	font-size: 13px;
	color: var(--otm-muted);
	margin-top: 3px;
	line-height: 1.45;
}

/*
 * ⚠️ THE RED IN THIS COLUMN NAMES WHAT THE PAGE HAS NOT ALREADY SAID, and the two
 * pages that use it therefore fill it from different levels of the tree — on purpose,
 * and stated here because it is exactly the kind of thing that reads as a bug.
 *
 *   campaign page  → the CHILD sub-section («ΑΙΓΙΝΙΟ»), and only when it differs from
 *                    the page's own category. The `<h1>` above it already says ΔΙΟΔΙΑ.
 *   search results → the CAMPAIGN («ΔΙΟΔΙΑ»). There is no context on a search page, so
 *                    the child would name a sub-section of nothing.
 *
 * 🔴 NOT the same question as the card's `.otm-band-tag`, which is the CAMPAIGN
 * everywhere without exception — that element is the design's one eyebrow and it read
 * «ΑΙΓΙΝΙΟ» on section pages until it was fixed. See category/blog.php.
 */
.otm-row-cat {
	font-size: 11px;
	letter-spacing: 0.06em;
	text-transform: uppercase;
	color: var(--otm-red);
	line-height: 1.3;
}

.otm-row-reads {
	font-size: 12.5px;
	color: var(--otm-muted);
	text-align: end;
}

/*
 * 🔴 THE PAGER IS THE ONE THING ON THIS SITE THAT OVERFLOWED 390px, AND ONLY A
 * MEASUREMENT FOUND IT. «Διόδια» is 10 pages, so Joomla emits first/prev + ten
 * numbers + next/last in a `ul.pagination` that core styles `display: flex` with NO
 * `flex-wrap` — 473px of buttons inside a 358px column. `documentElement.scrollWidth`
 * read **505** against an `innerWidth` of 390, and the screenshot showed nothing at
 * all, because a horizontal overflow is off-canvas. This is exactly the defect class
 * docs/08 §4 exists for, and it is why every band is asserted rather than looked at.
 *
 * ⚠️ The fix is `flex-wrap`, NOT `overflow-x: auto` on the wrapper. A scroll
 * container would still be 473px wide, would still need a horizontal drag on a
 * phone, and would hide pages 5–10 behind a gesture nobody is told about.
 */
.otm-pager {
	margin-top: 24px;
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 12px;
}

.otm-pager .pagination {
	flex-wrap: wrap;
	row-gap: 4px;
	margin-bottom: 0;
}

.otm-pager .pagination__wrapper {
	max-width: 100%;
}

.otm-pager-count {
	margin: 0;
	font-family: "OTM Slab", Georgia, serif;
	font-size: 12px;
	color: var(--otm-muted);
}

.otm-band-siblings {
	background: var(--otm-ground);
}

.otm-band-siblings .otm-register {
	columns: 4;
}

/* ------------------------------------------------------------- ARTICLES */

.otm-measure {
	max-width: calc(41em + 2 * var(--otm-gut));
}

.otm-band-articlehead {
	padding-bottom: 0;
}

body.site .otm-article-title {
	font-size: clamp(32px, 4.4vw, 54px);
	margin: 0 0 18px;
}

.otm-metabar {
	display: flex;
	flex-wrap: wrap;
	gap: 6px 18px;
	align-items: baseline;
	margin: 0;
	padding: 10px 0;
	border-block: 1px solid var(--otm-rule);
	font-size: 12.5px;
	color: var(--otm-muted);
}

.otm-fromarchive {
	margin-inline-start: auto;
	font-size: 11px;
	letter-spacing: 0.07em;
	text-transform: uppercase;
	color: var(--otm-slate);
}

.otm-band-articlebody {
	padding-top: clamp(20px, 3vw, 34px);
}

.otm-prose {
	font-size: 18px;
	line-height: 1.65;
}

.otm-prose p {
	margin: 0 0 1.1em;
}

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

.otm-band-more {
	background: var(--otm-ground);
}

.otm-more-all {
	margin: 18px 0 0;
	display: flex;
	align-items: baseline;
	gap: 14px;
	flex-wrap: wrap;
}

/* What is behind the link, said in words, so «όλες οι 40 δράσεις ›» is not a leap of
   faith after a list that stops at 18. */
.otm-more-note {
	font-size: 12px;
	color: var(--otm-muted);
}

/*
 * ============================================================================
 * 🔴 «ΔΙΑΒΑΣΤΕ ΤΗ ΔΡΑΣΗ ›» ON A PALE GROUND — ONE RULE, EVERY PALE BAND, AND THE
 *    LIST IS THE POINT.
 *
 * The base `body.site .otm-more` paints this link WHITE, because the first place it
 * appeared was the ink lead block. On any pale band it then renders present,
 * focusable, correctly linked and INVISIBLE — a defect that no element count and no
 * link check can see, and which shipped once already (docs/10) and again on the
 * search page's empty state while this file was being edited.
 *
 * 🔴 `body.site` IS LOAD-BEARING ON EVERY LINE BELOW — THIS FILE'S OWN RULE 2.
 * `.otm-band-more .otm-more` is (0,2,0) and the base rule is (0,2,1), so the bare
 * version loses and the link stays white. Loading after template.css only wins TIES.
 *
 * ⚠️ ONE GROUPED SELECTOR RATHER THAN ONE BLOCK PER BAND. Three copies of the same
 * two declarations is three places to remember when the fourth pale band is built,
 * and the failure mode of forgetting is invisible ink — so a new band is added to
 * THIS list and nowhere else.
 * ============================================================================
 */
body.site .otm-band-more .otm-more,
body.site .otm-band-register .otm-more,
body.site .otm-finder .otm-more {
	color: var(--otm-ink);
}

body.site .otm-band-register .otm-more:hover,
body.site .otm-band-register .otm-more:focus,
body.site .otm-finder .otm-more:hover,
body.site .otm-finder .otm-more:focus {
	color: var(--otm-red);
	border-bottom-color: var(--otm-red);
}

.otm-empty {
	color: var(--otm-muted);
}

/* ------------------------------------------------- «ΤΟ ΑΡΧΕΙΟ» — THE SEARCH PAGE
 *
 * ⚠️ THIS BLOCK USED TO BE A REPAIR JOB AND IS NOW A HANDFUL OF DETAILS. com_finder
 * was the one view on the site with no override, so this file was reaching in from
 * outside to hide a `<cite>` full of URLs, un-button an advanced-search toggle and
 * give a Bootstrap form a gutter — and the page still read as a CMS screen because
 * markup, not styling, was what said «Είδος: Άρθρο» under every hit.
 *
 * templates/cassiopeia/html/com_finder/search/ now renders the page in the site's own
 * bands and the site's own dense index, so what is left here is: the field on its
 * slate ground, the highlight, and the search-specific behaviour of the shared row.
 * ------------------------------------------------------------------------- */

/* The field band is tighter than a content band — it holds one object, and the stock
   `.otm-band` rhythm made a 300px slate box with a single input floating in it. */
.otm-band-finder {
	padding-block: clamp(18px, 2.4vw, 30px);
}

/*
 * The search-term highlight. Core ships mark.js's own `mark { background: #ff0 }` from
 * the UA stylesheet — a browser-yellow marker pen through Greek body text, forty times
 * a page, which is the loudest thing on the page and belongs to no palette here. The
 * archive's own ground plus a red underline says "this is the word you asked for" in
 * the site's two colours.
 */
.otm-finder mark {
	background: #f7e9e6;
	color: inherit;
	box-shadow: inset 0 -2px 0 rgba(168, 28, 16, 0.45);
	padding: 0 1px;
}

/* The suggested / explained line above the results — one muted sentence, the same
   register as the register band's axis note. */
.otm-finder .com-finder__explained {
	margin: 0 0 18px;
}

.otm-finder .com-finder__empty .otm-empty {
	font-size: 17px;
	margin: 0 0 6px;
}

/*
 * 🔴 AWESOMPLETE WRAPS THE INPUT AT RUNTIME, AND THAT COLLAPSED THE SEARCH FIELD.
 *
 * The autosuggest script inserts a `<div class="awesomplete">` AROUND the input after
 * the page loads, so the flex item on this row stops being the input — which carries
 * `flex: 1 1 auto` — and becomes the wrapper, which does not. The field then shrinks
 * to the input's default ~20-character size: on the screenshot, «Αναζήτηση σε 1.821
 * δημοσι» clipped mid-word inside a 720px form with 480px of empty slate beside it.
 * Invisible in the markup, because the markup is correct until JavaScript runs.
 */
.otm-bigsearch .awesomplete {
	flex: 1 1 auto;
	min-width: 0;
	display: flex;
}

.otm-bigsearch .awesomplete > input {
	width: 100%;
}

/*
 * The autosuggest list. `awesomplete` ships its own rounded, shadowed dropdown; these
 * four lines put it on the design's square, ruled ground so the one interactive
 * flourish on the site does not look borrowed.
 */
.otm-finder .awesomplete > ul {
	border-radius: 0;
	border: 1px solid var(--otm-rule);
	box-shadow: 0 12px 28px rgba(0, 0, 0, 0.16);
	font-size: 15px;
}

.otm-finder .awesomplete > ul > li[aria-selected="true"] {
	background: var(--otm-ground);
	color: var(--otm-ink);
}

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

.otm-footer {
	background: var(--otm-ink);
	color: #b9c1c8;
	padding-block: clamp(30px, 4vw, 52px) 24px;
	font-size: 13.5px;
}

.otm-footer-in {
	display: grid;
	grid-template-columns: 1.2fr 2fr 1fr;
	gap: clamp(20px, 3vw, 44px);
}

.otm-footer a {
	color: #fff;
}

body.site .otm-footer h2 {
	font-size: 12px;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	color: var(--otm-red);
	margin: 0 0 10px;
	padding-bottom: 8px;
	border-bottom: 1px solid var(--otm-rule-dark);
}

.otm-footer-name {
	font-family: "OTM Display", sans-serif;
	font-size: 22px;
	color: #fff;
	margin: 0 0 6px;
}

.otm-footer p {
	margin: 0 0 3px;
}

.otm-footer ul {
	list-style: none;
	margin: 0;
	padding: 0;
}

.otm-footer-index ul {
	columns: 2;
	column-gap: 26px;
}

.otm-footer li {
	padding: 3px 0;
	display: flex;
	justify-content: space-between;
	gap: 10px;
	break-inside: avoid;
}

.otm-footer li span {
	font-family: "OTM Slab", Georgia, serif;
	font-variant-numeric: tabular-nums;
	font-size: 11px;
	color: #6d777f;
}

.otm-legal {
	margin-top: 28px;
	padding-top: 16px;
	border-top: 1px solid var(--otm-rule-dark);
	font-size: 11.5px;
	color: #838d95;
}

.otm-legal p {
	margin: 0 0 4px;
}

.otm-legal strong {
	color: #fff;
}

/* ===========================================================================
 * NARROW WIDTHS.
 *
 * 🔴 390px IS THE TARGET AND `documentElement.scrollWidth === innerWidth` IS THE
 * TEST. Not "it looks fine in the screenshot": a horizontal overflow is
 * off-canvas and therefore INVISIBLE in a screenshot, which is how the archive
 * chip's `white-space: nowrap` reached production once already (docs/10 §2 #15 —
 * scrollWidth 444 against innerWidth 386, on one article, found only by asking
 * the browser).
 * ======================================================================== */

@media (max-width: 1100px) {
	.otm-mega-grid {
		grid-template-columns: repeat(2, minmax(0, 1fr));
		row-gap: 18px;
	}

	.otm-register,
	.otm-mostread {
		columns: 2;
	}

	.otm-band-siblings .otm-register {
		columns: 2;
	}

	.otm-footer-in {
		grid-template-columns: 1fr 1fr;
	}
}

@media (max-width: 820px) {
	.otm-lead {
		grid-template-columns: minmax(0, 1fr);
	}

	.otm-ledger {
		border-inline-start: 0;
		border-top: 1px solid #2f353b;
		padding-inline-start: 0;
		padding-top: 18px;
		display: flex;
		gap: clamp(18px, 5vw, 40px);
		flex-wrap: wrap;
	}

	.otm-ledger b {
		font-size: 26px;
	}

	.otm-cards > .otm-card,
	.otm-cards > .otm-card.is-big,
	.otm-cards-3 > .otm-card,
	.otm-cards-4 > .otm-card {
		grid-column: span 6;
	}

	body.site .otm-card.is-big h3,
	body.site .otm-card.is-mid h3 {
		font-size: 19px;
	}

	/*
	 * The nav wraps onto its own line rather than collapsing behind a control.
	 * Five short Greek labels fit two rows at 390px, and a burger would hide the
	 * ΔΡΑΣΕΙΣ panel behind a second tap for nothing.
	 */
	.otm-masthead-in {
		row-gap: 10px;
	}

	.otm-nav {
		margin-inline-start: 0;
		order: 3;
		width: 100%;
		gap: 14px;
		/*
		 * ⚠️ Overrides the desktop `flex-end`, which is correct up there (the nav
		 * sits between the masthead and the search field) and wrong here. Once the
		 * nav is its own full-width row it wraps, and at 390px five labels break
		 * 4 + 1 — with flex-end that last label hangs alone off the RIGHT edge while
		 * the row above starts at the left, which reads as a stray element rather
		 * than a second row. Screenshotted at 390: it is the one thing on the phone
		 * masthead that looks unfinished.
		 */
		justify-content: flex-start;
	}

	.otm-search {
		/*
		 * Grows into the masthead's free width instead of hugging the right edge,
		 * where `flex: 0 0 auto` left a ~150px dead gap beside a 150px field.
		 *
		 * ⚠️ `margin-inline-start: auto` is REMOVED, not kept alongside the grow.
		 * An auto margin on the main axis absorbs ALL positive free space before
		 * flex-grow is distributed, so the two together are not "right-aligned and
		 * growing" — the margin wins and the grow is dead. Measured: the field
		 * stayed at its 156px basis with 200px of empty masthead beside it.
		 *
		 * The basis is what picks the row: 200px cannot sit beside the wordmark at
		 * 390px so search takes its own full-width row, while at 768px it shares
		 * row one with the wordmark and grows into what is left.
		 */
		flex: 1 1 200px;
	}

	/*
	 * 🔴 The same runtime wrapper that collapsed the archive band's field — see the
	 * awesomplete note above — collapses this one, and it is why `width: 100%` on
	 * the input alone did nothing: awesomplete inserts a plain `<div>` between the
	 * form and the input, the div shrink-wraps, and 100% of a shrink-wrapped parent
	 * is the input's own default size. Measured: `.otm-search` grew to 358px while
	 * the input stayed at 156px inside it. The wrapper has to be told to fill too.
	 */
	.otm-search .mod-finder,
	.otm-search form,
	.otm-search .awesomplete {
		display: block;
		width: 100%;
	}

	.otm-search input[type="text"] {
		width: 100%;
		/* Cassiopeia caps `.form-control` at 200px; measured, this is what held the
		   field to 200px at 768px even once every wrapper above it filled the row. */
		max-width: none;
	}

	/*
	 * ⚠️ THE PANEL STAYS A DROPDOWN AT PHONE WIDTHS. Rendering it in flow instead
	 * (`position: static`) puts a 1,500px block INSIDE a wrapping flex row, and the
	 * screenshot showed the result: «Τώρα» stranded half-way down the page beside the
	 * panel and the remaining three nav links pushed below it. Anchored to the
	 * masthead it behaves like every other disclosure on a phone, and the max-height
	 * above is what makes it scrollable rather than truncated.
	 */
	.otm-mega-grid {
		padding-block: 18px 22px;
	}

	/*
	 * The dense index stops being a table. Four columns at 390px is 60px each,
	 * which wraps every title to five lines.
	 */
	.otm-row {
		grid-template-columns: minmax(0, 1fr) auto;
		gap: 2px 12px;
	}

	.otm-row .otm-datum {
		order: 1;
	}

	.otm-row-reads {
		order: 2;
		text-align: end;
	}

	.otm-row-main {
		order: 4;
		grid-column: 1 / -1;
	}

	.otm-row-cat {
		order: 3;
		grid-column: 1 / -1;
	}
}

@media (max-width: 560px) {
	body.site {
		font-size: 16px;
	}

	.otm-mega-grid,
	.otm-footer-in {
		grid-template-columns: minmax(0, 1fr);
	}

	.otm-register,
	.otm-mostread,
	.otm-footer-index ul,
	.otm-band-siblings .otm-register {
		columns: 1;
	}

	.otm-cards > .otm-card,
	.otm-cards > .otm-card.is-big,
	.otm-cards-3 > .otm-card,
	.otm-cards-4 > .otm-card {
		grid-column: span 12;
	}

	.otm-rail {
		gap: 18px 28px;
	}

	.otm-rail dd {
		font-size: 22px;
	}

	.otm-bigsearch {
		flex-wrap: wrap;
	}

	.otm-bigsearch button {
		width: 100%;
		padding: 12px 0;
	}

	/*
	 * ⚠️ This used to be `width: clamp(120px, 40vw, 200px)`, which is where the
	 * 156px field at 390px came from — 40vw of 390 is 156 exactly. It dated from
	 * when the field shared a row with the wordmark and had to be kept small; it
	 * now has a row of its own, so it fills it like the archive band's does.
	 */
	.otm-search input[type="text"] {
		width: 100%;
	}
}
