/**
 * OTA News Single styles: the sidebar cards.
 *
 * Sidebar component 2460:14764 ("News / Sidebar") on frame 404:9883. Three
 * cards, stacked 19px apart, each one a white panel with a hairline border, a
 * 14px radius, 24px of padding, an accent eyebrow, and rows separated by
 * hairlines with a trailing arrow badge.
 *
 * WHY THE CARD IS STRUCTURE AND THE REST IS CSS
 *
 * A card in the frame wraps a heading AND the list under it. Elementor draws
 * those as two sibling widgets, and CSS cannot put a border around two
 * siblings. Faking it (top half of the border on the heading, bottom half on
 * the list) survives exactly until an editor drags a widget, so each card is a
 * real inner section in template 2610 carrying `.ota-aside-card`, and this file
 * styles what is inside it. Nothing here knows a widget's element id, so the
 * sidebar can be rearranged without touching this file.
 *
 * THE TOKENS
 *
 * Every colour is a colour theme role, so the sidebar follows whatever theme
 * the section is in, with the frame's own value as the fallback:
 *
 *   card surface   --ota-background   bar/background  white
 *   card border    --ota-divider      bar/divider     rgba(0, 48, 56, 0.2)
 *   eyebrow        --ota-accent       bar/accent      #f04c3a
 *   row text       --ota-text         bar/text        #003038
 *   row meta       --ota-text-muted   (none in frame) #5a6b6e
 *
 * Two deliberate divergences from the frame's raw numbers. The border is the
 * divider role, which resolves to 0.14 alpha sitewide where the frame draws
 * 0.2: the role is what keeps the card consistent with every other hairline on
 * the page, and 0.06 of alpha is not worth breaking that for. And the date's
 * #5a6b6e has no variable behind it in the frame at all, so it is bound to the
 * muted-text role with the hex as the fallback rather than hardcoded.
 *
 * THE SPECIFICITY FIGHTS
 *
 * Two rules have to be outgunned rather than merely written. Elementor prints
 * its own widget CSS at one class for the categories and posts widgets, which a
 * single class here would only tie with, hence the `.ota-aside-card` prefix on
 * everything. And the theme spaces stacked list items from
 * src/scss/modules/_content.scss at one id, three classes and four elements:
 *
 *   main#agendtheme-content .agendtheme-content-inner:not(…) ul:not(…, …)
 *   li + li { margin-top: 0.5rem }
 *
 * which a class cannot reach past on the id. The `#agendtheme-content` rules
 * below restate that at one id and MORE than three classes (five on the
 * categories rows, four on the tags list), doubling widget classes purely for
 * the count where needed. Measure any fix to them on the SECOND row: the theme
 * rule skips the first, so a broken fix reads as cured on row one and leaves
 * the rest sitting low.
 */

.ota-aside-card {
	--oac-surface: var(--ota-background, #fff);
	--oac-line: var(--ota-divider, rgba(0, 48, 56, 0.2));
	--oac-eyebrow: var(--ota-accent, #f04c3a);
	--oac-text: var(--ota-text, #003038);
	--oac-meta: var(--ota-text-muted, #5a6b6e);

	/* 24px of padding and a 14px radius are the frame's own numbers. */
	padding: 24px;
	background-color: var(--oac-surface);
	border: 1px solid var(--oac-line);
	border-radius: var(--ota-radius-md, 14px);
}

/*
 * 19px between cards, and nothing under the last one. Applied as a margin on
 * the card rather than a gap on the column, because the column is an Elementor
 * widget-wrap whose gap an editor can overwrite from the panel.
 */
.ota-aside-card + .ota-aside-card {
	margin-top: 19px;
}

/*
 * A CARD WITH NOTHING IN IT IS NOT A CARD
 *
 * The "On this page" card holds one widget, and the Secondary Nav draws nothing
 * on a post with no top-level Elementor sections to harvest, which is every
 * classic post on the site. The card is a section, so it kept drawing its
 * border, padding and radius around the hole.
 *
 * `:not(:has(.elementor-widget))` is safe to write this broadly because
 * Elementor omits a widget's wrapper entirely when its render() prints nothing:
 * the empty card's `.elementor-widget-wrap` has no children at all, while the
 * category and latest cards always have at least a heading. So this reaches the
 * empty one and cannot reach a populated one. It also means any future card
 * whose contents all fall away disappears with them, rather than needing its own
 * rule.
 */
.ota-aside-card:not(:has(.elementor-widget)) {
	display: none;
}

/*
 * THE EYEBROW
 *
 * 17px bold with 1px of tracking in the accent, which is the same eyebrow
 * treatment the page's section headings already use. Applies to any heading
 * widget in a card, so "Browse by category" and "Latest in this category" both
 * get it without either being named here.
 *
 * The 24.75px line-height in the frame is 1.456 at 17px; it is written as a
 * ratio so a global font-size change carries.
 */
.ota-aside-card .elementor-widget-heading .elementor-heading-title {
	margin: 0;
	font-size: 1.0625rem;
	font-weight: 700;
	line-height: 1.456;
	letter-spacing: 1px;
	color: var(--oac-eyebrow);
}

/* 12px from the eyebrow to the first row, per the frame's card gap. */
.ota-aside-card .elementor-widget-heading {
	margin-bottom: 12px;
}

/*
 * THE ROWS
 *
 * The categories widget and the posts widget draw completely different markup
 * for what the frame draws as one row, so the shared parts are set on both
 * lists at once and each widget's quirks are handled under it.
 */
.ota-aside-card .elementor-widget-wp-widget-categories ul,
.ota-aside-card .elementor-widget-wp-widget-categories ol {
	margin: 0;
	padding: 0;
	list-style: none;
}

/*
 * The stock categories widget prints its own "Categories" title above the
 * list. The frame's card already has an eyebrow saying "Browse by category",
 * so the widget's own title is a duplicate heading, and leaving it visible
 * would also put two headings in the accessibility tree for one list.
 */
.ota-aside-card .elementor-widget-wp-widget-categories :is(h1, h2, h3, h4, h5, h6) {
	display: none;
}

.ota-aside-card .elementor-widget-wp-widget-categories li {
	margin: 0;
	padding: 0;
	border-bottom: 1px solid var(--oac-line);
}

/* See THE SPECIFICITY FIGHTS. Check row two, not row one. */
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item + li.cat-item {
	margin-top: 0;
}

/*
 * A row is the link, not the li: making the link the flex row is what puts the
 * whole width in the hit area, so the arrow at the far end is clickable rather
 * than decorative.
 */
.ota-aside-card .elementor-widget-wp-widget-categories li a {
	position: relative;
	display: block;
	/* Room for the badge, which is positioned rather than laid out: see below. */
	padding-block: 12px;
	padding-right: 40px;
	font-size: 0.9375rem;
	font-weight: 300;
	line-height: 1.65;
	color: var(--oac-text);
	text-decoration: none;
}

/*
 * THE TRAILING ARROW, AND THE RING THAT APPEARS AROUND IT
 *
 * Two pseudo-elements, both absolutely positioned, and the split is forced
 * rather than chosen. `mask-image` clips EVERYTHING the element paints, its
 * border and box-shadow included, so a ring cannot be drawn on the same element
 * that masks the arrow: it gets masked away with it. So `::before` is the glyph
 * and `::after` is the ring around it.
 *
 * Positioned and not laid out, because the row was a flex line and the arrow was
 * a flex item. Absolute keeps the badge pinned to the right edge whatever the
 * label does, which matters once the label goes bold on hover.
 *
 * A mask rather than an <img> because the glyph takes its colour from the row.
 */
.ota-aside-card .elementor-widget-wp-widget-categories li a::before {
	content: "";
	position: absolute;
	top: 50%;
	right: 7px;
	width: 13.5px;
	height: 13.5px;
	transform: translateY(-50%);
	background-color: currentColor;
	-webkit-mask: url("../img/ota-btn-arrow.svg") no-repeat center / contain;
	mask: url("../img/ota-btn-arrow.svg") no-repeat center / contain;
}

/*
 * The ring. Its border is present at rest and merely transparent, so turning it
 * on costs no width and nothing moves. Adding a border on hover instead would
 * grow the box by 3px and nudge the row.
 */
.ota-aside-card .elementor-widget-wp-widget-categories li a::after {
	content: "";
	position: absolute;
	top: 50%;
	right: 0;
	width: 27.75px;
	height: 27.75px;
	transform: translateY(-50%);
	border: 1.5px solid transparent;
	border-radius: 50%;
	transition: border-color 0.2s;
}

/*
 * WHAT WAS ACTUALLY MAKING THE ROWS JUMP, because it was not this file.
 *
 * The theme skins every unclassed link in the content area, and a stock
 * categories widget prints exactly that: `<a href="...">Driving</a>`, no class.
 * From skin-2020:
 *
 *   main#agendtheme-content .agendtheme-content-inner:not(…) a:not([class]):hover
 *     { background: var(--at-color-accent);
 *       border-bottom: 2px solid var(--at-color-accent);
 *       text-decoration: none }
 *
 * So hovering a category put a solid accent block behind the label AND added
 * 2px to the bottom of the row, which pushed every row below it down by two
 * pixels. That is the bounce. Its `text-decoration: none` also outranked the
 * underline this file was asking for, so the underline never appeared either.
 *
 * THE ARITHMETIC, because these selectors look absurd and are not. The theme's
 * hover rule scores one id, four classes (`.agendtheme-content-inner`, both
 * `:not()` arguments, and `:hover`) and two elements. A rule here therefore
 * needs an id just to enter the argument, and then more classes than four:
 *
 *   #agendtheme-content .ota-aside-card .elementor-widget
 *     .elementor-widget-wp-widget-categories li.cat-item a:hover
 *     -> 1 id, 5 classes, 2 elements
 *
 * `.elementor-widget` is doubled onto the widget wrapper purely for the count.
 * Drop any one class and the theme wins again, silently, and only on hover.
 */
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a,
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:hover,
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:focus,
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:active,
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:visited {
	background: none;
	border-bottom: 0;
}

/*
 * The hover the frame draws: the label goes to Medium and picks up an underline,
 * and the ring appears around the arrow. Medium, not bold, because 500 is what
 * the frame uses for the current row (2460:14764) and it is verified not to
 * rewrap the longest category name at the sidebar's width, which bold would risk
 * and would reintroduce the jump this whole block exists to remove.
 */
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:hover,
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item a:focus-visible {
	color: var(--oac-text);
	font-weight: 500;
	text-decoration: underline;
	text-underline-position: from-font;
}

.ota-aside-card .elementor-widget-wp-widget-categories li a:hover::after,
.ota-aside-card .elementor-widget-wp-widget-categories li a:focus-visible::after {
	border-color: currentColor;
}

/*
 * The current category, which WordPress marks for us, given the same treatment.
 * It only appears on a category archive: on a single post nothing in the stock
 * widget knows which of the post's categories is "the" one, so a news article
 * shows no active row. That is a gap against the frame, which draws one, and it
 * needs a widget rather than a rule to close.
 */
#agendtheme-content .ota-aside-card .elementor-widget.elementor-widget-wp-widget-categories li.cat-item.current-cat > a {
	font-weight: 500;
	text-decoration: underline;
	text-underline-position: from-font;
}

.ota-aside-card .elementor-widget-wp-widget-categories li.current-cat > a::after {
	border-color: currentColor;
}

/*
 * THE LATEST-IN-CATEGORY CARD
 *
 * Elementor's Posts widget in its Classic skin. The frame's row is a title and
 * a date and nothing else, so the thumbnail, the excerpt, the Read More link
 * and the comment count all come off. They are switched off in the widget's own
 * panel too; these rules are the belt to that braces, because the panel is
 * template content an editor can flip back on by accident and the frame has no
 * layout for any of them.
 *
 * `.elementor-post-avatar` is not a typo and is not the author's photograph:
 * the Posts widget prints the COMMENT COUNT in a span with that class. Hiding
 * `.elementor-post__comments`, which is what the class list leads you to,
 * silently does nothing, and that is how "19 August 2026 /// No Comments"
 * survived the first pass at this rule. The `///` goes with it, since the
 * separator is a `span + span::before` and stops matching once one span is gone.
 */
.ota-aside-card .elementor-widget-posts .elementor-post__thumbnail__link,
.ota-aside-card .elementor-widget-posts .elementor-post__excerpt,
.ota-aside-card .elementor-widget-posts .elementor-post__read-more,
.ota-aside-card .elementor-widget-posts .elementor-post-avatar {
	display: none;
}

.ota-aside-card .elementor-widget-posts .elementor-posts {
	display: block;
}

.ota-aside-card .elementor-widget-posts article.elementor-post {
	margin: 0;
	padding-block: 12px;
	border-bottom: 1px solid var(--oac-line);
}

.ota-aside-card .elementor-widget-posts .elementor-post__text {
	margin: 0;
	padding: 0;
}

.ota-aside-card .elementor-widget-posts .elementor-post__title {
	margin: 0;
	font-size: 0.9375rem;
	font-weight: 300;
	line-height: 1.65;
}

.ota-aside-card .elementor-widget-posts .elementor-post__title a {
	color: var(--oac-text);
	text-decoration: none;
}

.ota-aside-card .elementor-widget-posts .elementor-post__title a:hover,
.ota-aside-card .elementor-widget-posts .elementor-post__title a:focus-visible {
	text-decoration: underline;
	text-underline-position: from-font;
}

/*
 * The date. 12px over a 19.8px line in the frame, which is 1.65 at 12px, the
 * same ratio the 15px rows use.
 */
.ota-aside-card .elementor-widget-posts .elementor-post__meta-data {
	margin: 0;
	padding: 0;
	border: 0;
	font-size: 0.75rem;
	font-weight: 300;
	line-height: 1.65;
	color: var(--oac-meta);
}

/*
 * THE CARD'S CLOSING BUTTON
 *
 * "View All Categories" and "View All Advocacy" are Button widgets carrying
 * `ota-btn--ghost`, so the badge, the arrow and every colour come from
 * assets/css/ota-buttons.css and none of it is restated here. The frame differs
 * from that component in one way only: the row runs the full width of the card
 * with the label at one end and the badge at the other, where the component
 * centres a `max-content` row. That override is all this block is.
 */
.ota-aside-card .elementor-widget-button .elementor-button {
	display: flex;
	width: 100%;
	justify-content: space-between;
	padding-inline: 0;
}

.ota-aside-card .elementor-widget-button .elementor-button .elementor-button-content-wrapper {
	width: 100%;
	justify-content: space-between;
}

/*
 * The button sits on the last hairline rather than adding one of its own, so
 * the row above it keeps its border and this one has none.
 */
.ota-aside-card .elementor-widget-button {
	margin-top: 0;
}

/*
 * THE STICKY SIDEBAR
 *
 * Moved here out of the column's own Elementor custom CSS, which had
 * `top: 120px` hardcoded. 120 was about right for a guest and wrong for anyone
 * logged in, because the admin bar pushes the fixed header down by another 32.
 * These are the same two variables the jump bar uses, measured onto the page by
 * ota-mega-menu.js, plus 24px of breathing room.
 *
 * `align-self: flex-start` is load-bearing and easy to lose. Elementor's columns
 * are flex items that stretch to the row's height by default, and a sticky
 * element the full height of its container has nowhere to travel, so it silently
 * does nothing.
 *
 * WHAT MAKES THIS WORK AT ALL is that the article column is now the taller of
 * the two. While the resources, author and tags bands sat below the two-column
 * block, the columns ended at the same height and there was no distance to stick
 * over. Sticky is only ever as useful as the difference between the two columns.
 *
 * Worth knowing: `<html>` on this site is a flex container, which makes BODY the
 * scroll container (`overflow-x: hidden` forces the other axis to `auto`). That
 * is fine for sticky, because body's scrollport is the viewport and nothing
 * between here and body clips overflow. An ancestor with its own `overflow` is
 * the usual reason a rule like this appears to be ignored, so check that first.
 */
.ota-news-aside {
	position: sticky;
	top: calc(var(--ota-admin-bar, 0px) + var(--ota-header-height, 0px) + 24px);
	align-self: flex-start;

	/*
	 * NO HEIGHT CAP AND NO INNER SCROLLBAR. Capping the column and letting it
	 * scroll itself does keep every card reachable when the sidebar is taller
	 * than the viewport, but a nested scroll area inside a pinned column reads as
	 * broken, so it is deliberately not done. The trade is accepted instead: on a
	 * short viewport the foot of the sidebar stays below the fold while the column
	 * is pinned. Keep the sidebar short enough to fit and the question does not
	 * arise, which is why the latest card draws three posts rather than six.
	 */
}

/*
 * Below the two-column breakpoint the sidebar is a stack under the article, so
 * pinning it would strand it mid-page.
 */
@media (max-width: 900px) {
	.ota-news-aside {
		position: static;
	}
}

/*
 * AIR UNDER THE HERO
 *
 * The template's first section butted straight up against the hero band, so the
 * first paragraph and the first sidebar card both started on the seam. Frame
 * 404:9883 leaves roughly 64px between the hero's lower edge and the top of the
 * article, and the sidebar's first card starts on the same line.
 *
 * Padding on the section rather than a margin, so it sits inside the section's
 * own background and cannot collapse against the hero's margin. It goes on the
 * article body section only: everything below it is spaced by its own band.
 */
.ota-news-body {
	padding-top: 64px;
}

@media (max-width: 900px) {
	/*
	 * The sidebar has dropped under the article by here, so the gap is doing
	 * less work and the hero is shorter to begin with.
	 */
	.ota-news-body {
		padding-top: 36px;
	}
}

/*
 * THE NESTED BANDS: RESOURCES, AUTHOR CARD, RELATED TAGS
 *
 * All three were built as FULL-WIDTH BANDS, each bringing its own centred
 * container, its own generous vertical padding and, in the resources' case,
 * equal-height cards for a three-across row. Dropped into a 740px article
 * column, every one of those assumptions is wrong, and they were wrong in
 * different amounts, which is why the bands did not even line up with each other:
 * the article prose sat at 190, the author card at 200 and the resource cards at
 * 232.
 *
 * Everything below is scoped to `.ota-news-body`, so the interest group pages
 * keep the full-width treatment these components were designed for.
 *
 * FIRST, the 10px Elementor puts on every inner section's widget-wrap, which is
 * what held the bands 10px inside the prose. `:not(.ota-aside-card)` spares the
 * sidebar cards, whose own 24px padding sits inside that same wrap and would
 * tighten if this reached them.
 */
.ota-news-body .elementor-inner-section:not(.ota-aside-card) > .elementor-container > .elementor-column > .elementor-widget-wrap {
	padding: 0;
}

/*
 * One card per row. Three across in a 740px column gave two narrow columns that
 * wrapped "PDF · 776 KB" onto two lines and each title onto three.
 */
.ota-news-body .ota-sig-resources__grid {
	grid-template-columns: 1fr;
	/* 39px is the frame's gap between three columns side by side. Stacked, that
	   reads as a hole; 20px is the same relationship the cards' own rows use. */
	gap: 20px;
}

/*
 * The band's own chrome comes off. `padding-block: 96px` is the air a full-width
 * section needs to separate itself from the bands above and below it; inside a
 * column the section spacing already does that job, and 96 top and bottom was
 * most of the empty space on the page.
 *
 * The Download buttons layout is excluded: that one is a sand box with its own
 * 36px of inner padding, not a full-width band, and this rule loads after the
 * widget's stylesheet at the same specificity, so without the exclusion it
 * flattened the box and left the heading on its top edge.
 */
.ota-news-body .ota-sig-resources:not(.ota-sig-resources--downloads) {
	padding-block: 0;
}

/*
 * The centred container likewise. `max-width` plus `margin-inline: auto` plus
 * `padding-inline: 2rem` is how a full-bleed band holds its content to a
 * readable measure, and the column has already done that: the only thing left of
 * it here was the 32px that pushed the cards out of line with everything else.
 */
.ota-news-body .ota-sig-resources__inner {
	max-width: none;
	margin-inline: 0;
	padding-inline: 0;
	gap: 24px;
}

/*
 * `min-height: 336px` exists so three cards in a row are the same height
 * whatever their copy. One per row, nothing needs matching, and the floor just
 * became a large empty gap between each description and its footer. The widget
 * already drops it at its own single-column breakpoint (767px), for exactly this
 * reason; this is that same decision at a different trigger.
 */
.ota-news-body .ota-sig-resources__card {
	min-height: 0;
}

/*
 * Even spacing between the bands, replacing the padding each used to bring.
 */
.ota-news-body .elementor-inner-section:not(.ota-aside-card) + .elementor-inner-section:not(.ota-aside-card) {
	margin-top: 40px;
}

/* And air between the prose and the first band. */
.ota-news-body .elementor-widget-theme-post-content + .elementor-inner-section:not(.ota-aside-card) {
	margin-top: 40px;
}

/*
 * RELATED TAGS
 *
 * Group 2460:14216 on frame 404:9883: an uppercase muted label, then the post's
 * tags as mint pills. This is Elementor Pro's Post Info widget, whose terms row
 * ships as an icon-list line with a tag glyph and comma-separated links, so all
 * of the below is turning that into the frame's row.
 *
 * THE COLOURS ARE ROLES, and the pill carries the Mint theme to get them. The
 * frame draws a #D4F0D9 pill with #005361 text, and on Mint that is exactly
 * `--ota-background` over `--ota-text-muted`, so nothing here names a colour.
 *
 * The theme rides on the WIDGET, as an `ota-theme--mint` class in its CSS
 * Classes box, not as the section's Colour Theme setting. Two reasons. Elementor
 * Pro's post-info widget has no Colour Theme control, because
 * `Elementor::register_theme_control()` is opt-in per widget and the generic hook
 * only covers containers and sections, so the setting is stored and no class is
 * ever emitted. And putting it on the SECTION works but paints the whole band
 * mint, which hides a mint pill inside it.
 *
 * A theme class does two things: `.ota-theme--mint` remaps the role variables,
 * and `:where(.ota-theme--mint)` paints background and colour. That paint is
 * inside `:where()`, so it carries ZERO specificity and any real selector beats
 * it. That is the hook for a nested theme: take the roles, drop the paint, which
 * is the single `background-color: transparent` below. The same trick is what
 * lets the News Block put a white card inside a teal band.
 *
 * Hover inverts to the theme's CTA pair, which on Mint is navy on mint. That is
 * the hollow-to-solid swap assets/css/ota-buttons.css already documents, rather
 * than a hand-darkened version of the resting colour.
 *
 * The one value with no token behind it is the label's #5a6b6e, which is not in
 * the palette at all. It takes the muted-text role instead, which resolves to
 * #005361 here: a deliberate divergence, on the grounds that a role that
 * follows the theme beats a grey that matches one frame.
 *
 * THE COMMA IS THE AWKWARD PART. Elementor joins the term links with a literal
 * ", " TEXT NODE between the anchors, which no selector can reach. `font-size: 0`
 * on the list collapses it to nothing and each pill restores its own size, which
 * is why the pills are spaced with margins rather than a flex `gap`: in a flex
 * row the comma becomes an anonymous flex item and the gap would still reserve
 * space on both sides of it. The pill's own size is set at class-plus-element
 * strength, because Elementor sets a font-size on the icon-list anchor and a
 * bare class only ties with it.
 */
/*
 * Take the Mint theme's roles, drop its zero-specificity paint. See the note
 * above: this one declaration is what makes a nested theme possible.
 */
.ota-related-tags .elementor-widget-post-info {
	background-color: transparent;
}

.ota-related-tags .elementor-post-info {
	margin: 0;
	padding: 0;
	list-style: none;
}

.ota-related-tags .elementor-post-info__item {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
}

/* The frame draws no glyph. */
.ota-related-tags .elementor-icon-list-icon {
	display: none;
}

.ota-related-tags .elementor-post-info__item-prefix {
	margin-right: 14px;
	/* 12.5px, the frame's own number. */
	font-size: 0.78125rem;
	font-weight: 700;
	line-height: 1.65;
	letter-spacing: 1px;
	text-transform: uppercase;
	color: var(--ota-text-muted, #5a6b6e);
	white-space: nowrap;
}

.ota-related-tags .elementor-post-info__terms-list {
	font-size: 0;
}

/*
 * ROW SPACING LIVES ON THE PILL, NOT ON THE FLEX ROW. The `row-gap` that used
 * to sit on `.elementor-post-info__item` could never separate pill rows: the
 * whole terms list is ONE flex item there, and the pills wrap as inline
 * content inside it, out of the gap's reach. So the pills in a second row sat
 * flush against the first. Bottom margin on each pill is what the wrapped rows
 * actually respond to. Reported by Bryce 1 Oct 2026 with a screenshot.
 *
 * `white-space: nowrap` is belt and braces: an inline-block never fragments
 * across lines, but a long label can still wrap INSIDE its pill when the row
 * is tight, and a two-line pill reads as two pills. A label is one unit.
 *
 * The selector names the list AND the widget so it weighs (0,4,0), above any
 * (0,3,x) rule Elementor or the theme might put on the same anchor.
 */
.ota-related-tags .elementor-widget-post-info .elementor-post-info__terms-list .elementor-post-info__terms-list-item,
.ota-related-tags a.elementor-post-info__terms-list-item {
	display: inline-block;
	white-space: nowrap;
	vertical-align: top;
	margin: 0 10px 10px 0;
	/* 39px tall in the frame, reached with padding so a wrapped label still
	   grows the pill rather than clipping. */
	padding: 0.5rem 1.125rem;
	border-radius: 999px;
	/* Fallbacks are Mint's own values, for an environment where the colour
	   themes (customizer/DB config) have not been handed over yet. */
	background: var(--ota-background, #d4f0d9);
	color: var(--ota-text-muted, #005361);
	font-size: 0.875rem;
	font-weight: 500;
	line-height: 1.65;
	text-decoration: none;
}

.ota-related-tags a.elementor-post-info__terms-list-item:hover,
.ota-related-tags a.elementor-post-info__terms-list-item:focus-visible {
	background: var(--ota-cta-bg, #003038);
	color: var(--ota-cta-text, #d4f0d9);
	text-decoration: none;
}

/*
 * FIVE PILLS, THEN "+ N MORE" (Teamwork 49743801)
 *
 * A resource can carry dozens of areas of practice: the Capability Framework
 * for adults has 49, which ran this row to seven lines of pills. Each list now
 * shows its first five, and assets/js/ota-related-tags.js adds a pill after
 * them that opens the rest in place and closes them again.
 *
 * THE HIDING IS HERE, NOT IN THE SCRIPT, AND ONLY UNDER `html.ota-tags-js`.
 * News_Single prints that class into <head> before first paint, so a long list
 * never paints in full and snaps shut, and a visitor with scripts blocked gets
 * no class and so every pill, as before. The script only adds the control and
 * flips `is-expanded`.
 *
 * `:nth-of-type(n+6)` IS THE FIVE. It cannot read News_Single::TAGS_VISIBLE,
 * so the two move together. `of-type` is safe because the pills in one list
 * are all the same element (anchors, or spans where the taxonomy has no
 * archive) and the control is a <button>, a different type, so it is never
 * counted and never hidden. Weighs (0,6,1), over the (0,4,0) rule above that
 * sets the pills to inline-block.
 *
 * ONLY FROM A SEVENTH PILL. A list of six would hide one pill behind a
 * "+ 1 more" that takes the same room on the row, so `:has()` limits the
 * hiding to lists with a seventh, and the script holds back its control on
 * the same rule.
 */
html.ota-tags-js .ota-related-tags .elementor-post-info__terms-list:not(.is-expanded):has(> .elementor-post-info__terms-list-item:nth-of-type(7)) > .elementor-post-info__terms-list-item:nth-of-type(n+6) {
	display: none;
}

/*
 * The control. The pill's own geometry, so it sits on the row as one of them,
 * but hollow: an outline in the pill's text colour where the tags are filled.
 * It is the one thing in the row that is not a tag, and filled it read as a
 * forty-ninth area of practice called "+ 44 more". The padding gives back the
 * border's 1px each side so the two are the same height.
 *
 * Every text property is restated rather than inherited: the list sets
 * `font-size: 0` to swallow Elementor's commas, and a <button> does not
 * inherit its font from the page in any case. Named with the element and
 * three classes (0,3,1) so the theme's and Elementor's own button rules, all
 * written against bare `button` or one class, stay underneath it.
 */
.ota-related-tags .elementor-post-info__terms-list button.ota-related-tags__more {
	display: inline-block;
	vertical-align: top;
	width: auto;
	min-width: 0;
	min-height: 0;
	margin: 0 10px 10px 0;
	padding: calc(0.5rem - 1px) calc(1.125rem - 1px);
	border: 1px solid currentColor;
	border-radius: 999px;
	background: transparent;
	box-shadow: none;
	color: var(--ota-text-muted, #005361);
	font-family: inherit;
	font-size: 0.875rem;
	font-weight: 500;
	line-height: 1.65;
	letter-spacing: normal;
	text-transform: none;
	white-space: nowrap;
	cursor: pointer;
	-webkit-appearance: none;
	appearance: none;
}

/* The tags' own hover, so the row answers the pointer the same way throughout. */
.ota-related-tags .elementor-post-info__terms-list button.ota-related-tags__more:hover,
.ota-related-tags .elementor-post-info__terms-list button.ota-related-tags__more:focus-visible {
	border-color: var(--ota-cta-bg, #003038);
	background: var(--ota-cta-bg, #003038);
	color: var(--ota-cta-text, #d4f0d9);
}

.ota-related-tags .elementor-post-info__terms-list button.ota-related-tags__more:focus-visible {
	outline: 2px solid var(--ota-cta-bg, #003038);
	outline-offset: 2px;
}

/*
 * The theme's list rules reach this one on the id, same fight as the sidebar.
 * The li selector doubles the widget class to reach 1-4-2 against the theme's
 * 1-3-4 li + li spacing rule; there is only one li today, but a second Post
 * Info item would sit 0.5rem low without it.
 */
#agendtheme-content .ota-related-tags .elementor-post-info,
#agendtheme-content .ota-related-tags .elementor-widget.elementor-widget-post-info .elementor-post-info > li {
	margin: 0;
	padding: 0;
	list-style: none;
}

/*
 * The Research and Resource Singles (9 Sep 2026) put three items in this widget,
 * tags, the type, areas of practice, where the News Single has one. Pro lays the
 * items out inline (`elementor-inline-items`, a wrapping flex row), which ran
 * "RESEARCH TYPE" on after the last tag pill at a different baseline. Stacked
 * instead: one label and its pills per row, 12px apart. With a single item, as
 * on news, a one-child column is indistinguishable from before. Same id-led
 * chain as the rule above so it outranks Pro's inline layout.
 */
#agendtheme-content .ota-related-tags .elementor-widget.elementor-widget-post-info .elementor-post-info {
	display: flex;
	flex-direction: column;
	align-items: flex-start;
	row-gap: 12px;
}

/*
 * THE FULL-WIDTH AD BAND
 *
 * Frame 409:12410 runs the ad band's colour edge to edge with the two ads held
 * at the content width. Elementor's Stretch Section on its own does not do
 * that, and the reason is worth writing down: the band is painted by the
 * WIDGET (`.ota-ads`, from assets/css/ota-ad-block.css), which sits inside the
 * section's boxed 1140px container. Stretching the section moves the section,
 * measured and correct (`width: 100vw; left: -230px`), and changes nothing you
 * can see, because the thing carrying the colour never left the container.
 *
 * So the colour moves to the section, which IS full width, and the widget's
 * band goes transparent through the `--oad-section-bg` hook its own Background
 * control writes. Setting that control to `transparent` in the panel would work
 * identically; it is done here so the band stays bound to the theme role rather
 * than to a colour an editor picked, and so the pair cannot be half-applied.
 *
 * The alternative, `content_width: full`, was rejected: it widens the ads
 * themselves to ~800px each, which the ad block's own Columns control warns
 * about and which the frame does not draw.
 */
.ota-ad-band {
	background-color: var(--ota-background, #f0e7d8);
}

.ota-ad-band .ota-ads {
	--oad-section-bg: transparent;
}

/*
 * The sidebar is a column, not a page: below the two-column breakpoint it
 * falls under the article and the cards keep their own shape, so there is
 * nothing to restack. Only the padding eases, matching what the jump bar does
 * at the same width.
 */
@media (max-width: 900px) {
	.ota-aside-card {
		padding: 20px;
	}
}
