/* ==========================================================================
   ARCHIVES, FILTERS, FORMS AND SINGLES

   Everything that is not the homepage: the six category pages, the directory,
   /community, both event archives, /about/board, the submission form, search
   and 404.
   ========================================================================== */

/* --- Filter rails --------------------------------------------------------
   Used by the category pages, the community subsections and the event
   upcoming/past switch. One component, because to a visitor they are one
   idea: "narrow what I am looking at". */
.kbia-filters {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5rem 1.5rem;
	margin-bottom: 2rem;
	padding-bottom: 1rem;
	border-bottom: 1px solid var(--kbia-border);
}

.kbia-filter {
	font-family: var(--kbia-font-mono);
	font-size: var(--kbia-fs-eyebrow);
	letter-spacing: var(--kbia-ls-eyebrow);
	text-transform: uppercase;
	text-decoration: none;
	color: var(--kbia-muted);
	padding-bottom: 0.4rem;
	border-bottom: var(--kbia-rule) solid transparent;
	transition: color var(--kbia-dur-fast) var(--kbia-ease-out),
	            border-color var(--kbia-dur-slow) var(--kbia-ease-out);
}

.kbia-filter:hover,
.kbia-filter:focus-visible {
	color: var(--kbia-heading);
}

.kbia-filter.is-active {
	color: var(--kbia-heading);
	font-weight: 700;
	border-bottom-color: var(--kbia-accent);
}

/* The per-filter count. Tabular numerals so the rail does not jitter. */
.kbia-filter span {
	font-variant-numeric: tabular-nums;
	opacity: 0.6;
}

/* --- Directory filter form ----------------------------------------------- */
.kbia-dirfilters {
	display: grid;
	gap: 1rem;
	margin-bottom: 1.5rem;
	padding: 1.5rem;
	border-radius: var(--kbia-radius-xl);
	background: var(--kbia-surface-alt);
}

@media (min-width: 48rem) {
	.kbia-dirfilters { grid-template-columns: 2fr 1fr 1fr auto; align-items: end; }
}

.kbia-dirfilters__field { margin: 0; }

.kbia-dirfilters label,
.kbia-form__field label {
	display: block;
	font-family: var(--kbia-font-mono);
	font-size: var(--kbia-fs-eyebrow);
	letter-spacing: var(--kbia-ls-eyebrow);
	text-transform: uppercase;
	color: var(--kbia-muted);
	margin-bottom: 0.4rem;
}

.kbia-dirfilters input,
.kbia-dirfilters select,
.kbia-form input,
.kbia-form select,
.kbia-form textarea,
.kbia-searchform input {
	width: 100%;
	padding: 0.75rem 1rem;
	font: inherit;
	color: var(--kbia-body);
	background: var(--kbia-surface);
	border: 1px solid var(--kbia-border);
	border-radius: var(--kbia-radius);
}

.kbia-dirfilters input:focus-visible,
.kbia-dirfilters select:focus-visible,
.kbia-form :is(input, select, textarea):focus-visible,
.kbia-searchform input:focus-visible {
	outline: var(--kbia-underline) solid var(--kbia-accent);
	outline-offset: 2px;
	border-color: var(--kbia-accent);
}

.kbia-dirfilters__actions {
	display: flex;
	align-items: center;
	gap: 1rem;
	margin: 0;
}

.kbia-resultcount {
	font-family: var(--kbia-font-mono);
	font-size: var(--kbia-fs-eyebrow);
	letter-spacing: var(--kbia-ls-eyebrow);
	text-transform: uppercase;
	color: var(--kbia-muted);
	margin: 0 0 1.5rem;
}

/* --- Search -------------------------------------------------------------- */
.kbia-searchform {
	display: flex;
	gap: 0.75rem;
	max-width: 44rem;
	margin-bottom: 2.5rem;
}

.kbia-searchform .kbia-btn { flex: none; }

.kbia-results { margin-bottom: 3rem; }

.kbia-results__count {
	font-family: var(--kbia-font-mono);
	font-size: 1rem;
	font-variant-numeric: tabular-nums;
	color: var(--kbia-muted);
	margin-left: 0.5rem;
}

.kbia-results__list {
	list-style: none;
	margin: 0 0 1.5rem;
	padding: 0;
	display: grid;
	gap: 1.25rem;
}

.kbia-results__list li {
	padding-bottom: 1.25rem;
	border-bottom: 1px solid var(--kbia-border);
}

.kbia-results__list p {
	margin: 0.35rem 0 0;
	color: var(--kbia-muted);
	line-height: var(--kbia-lh-body);
}

/* --- Submission form ----------------------------------------------------- */
.kbia-form fieldset {
	border: 0;
	border-top: 1px solid var(--kbia-border);
	margin: 0 0 2rem;
	padding: 1.5rem 0 0;
}

.kbia-form legend {
	font-family: var(--kbia-font-heading);
	font-size: var(--kbia-fs-h3);
	color: var(--kbia-heading);
	padding: 0 1rem 0 0;
}

.kbia-form__field { margin: 0 0 1.25rem; }

.kbia-form__choice {
	display: grid;
	gap: 0.5rem;
	margin: 0 0 1.5rem;
}

.kbia-form__choice label {
	display: flex;
	gap: 0.6rem;
	align-items: baseline;
	font: inherit;
	text-transform: none;
	letter-spacing: normal;
	color: var(--kbia-body);
}

.kbia-form__choice input { width: auto; }

.kbia-form__hint {
	display: block;
	margin-top: 0.4rem;
	font-size: var(--kbia-fs-eyebrow);
	color: var(--kbia-muted);
	line-height: var(--kbia-lh-body);
}

.kbia-form .req { color: var(--kbia-warm-ink); }

/* Honeypot. Positioned off-screen rather than display:none, because a
   meaningful share of bots skip fields that are display:none and this one
   only works if they fill it in. Hidden from assistive tech via aria-hidden
   and removed from the tab order on the input itself. */
.kbia-hp {
	position: absolute;
	left: -9999px;
	width: 1px;
	height: 1px;
	overflow: hidden;
}

/* --- Notices ------------------------------------------------------------- */
.kbia-notice {
	padding: 1.5rem;
	margin-bottom: 2rem;
	border-left: var(--kbia-rule) solid var(--kbia-accent);
	border-radius: var(--kbia-radius-lg);
	background: var(--kbia-surface-alt);
}

.kbia-notice h2 {
	margin: 0 0 0.5rem;
	font-family: var(--kbia-font-heading);
	font-size: var(--kbia-fs-h3);
	color: var(--kbia-heading);
}

.kbia-notice p { margin: 0 0 1rem; line-height: var(--kbia-lh-body); }
.kbia-notice--error { border-left-color: var(--kbia-warm-ink); }

/* --- Single layouts ------------------------------------------------------ */
/* minmax(0, 1fr), not the implicit `auto` column: an auto track grows to its
   widest unbreakable content, so on a phone one 960px image or long URL in a
   post body made the whole page scroll sideways. */
.kbia-single__layout {
	display: grid;
	grid-template-columns: minmax(0, 1fr);
	gap: clamp(2rem, 4vw, 4rem);
	align-items: start;
}

@media (min-width: 60rem) {
	.kbia-single__layout { grid-template-columns: minmax(0, 2fr) minmax(16rem, 1fr); }
}

.kbia-single__narrow { max-width: var(--kbia-container-text); }

.kbia-single__figure { margin: 0 0 2rem; }
.kbia-single__figure img { width: 100%; height: auto; display: block; border-radius: var(--kbia-radius-lg); }

/* Running text caps at the reading measure, not at the layout container.
   --kbia-container-text is 64rem, which at 18px body copy is around 110
   characters a line; comfortable reading gives out somewhere near 75. The two
   were the same token until /community made the difference impossible to
   ignore -- its posts average 600 words each.

   The second selector is deliberate rather than redundant: three page
   templates carry `class="kbia-prose kbia-single__narrow"`, where both rules
   have equal specificity and the winner would otherwise be decided by which
   one happens to sit lower in this file. Naming the combination settles it. */
.kbia-prose,
.kbia-prose.kbia-single__narrow {
	max-width: var(--kbia-measure);
	font-size: var(--kbia-fs-body);
	line-height: var(--kbia-lh-body);
	color: var(--kbia-body);
}

.kbia-prose > * + * { margin-top: 1.25em; }

.kbia-prose :is(h2, h3, h4) {
	font-family: var(--kbia-font-heading);
	color: var(--kbia-heading);
	line-height: var(--kbia-lh-heading);
	margin-top: 2em;
}

/* Sizes of our own. These used to fall through to My Listing's h2/h3, so the
   step between a section and a subsection was whatever the parent theme
   happened to ship. A post with both -- "Ways to Support", then an
   organisation under it -- needs that step to be visible at a glance. */
.kbia-prose h2 {
	font-size: clamp(1.625rem, 1.2vw + 1.1rem, 2.25rem);  /* 26 -> 36 */
	font-weight: 700;
}

.kbia-prose h3 {
	font-size: clamp(1.25rem, 0.5vw + 1.05rem, 1.5rem);   /* 20 -> 24 */
	font-weight: 600;
}

/* A heading belongs to what follows it, so it sits closer to that than to
   what came before. A subsection straight under its section heading is part
   of the same unit and should not be pushed a full section away. */
.kbia-prose :is(h2, h3, h4) + * { margin-top: 0.6em; }
.kbia-prose h2 + h3 { margin-top: 0.9em; }

/* A rule over each section after the first, on single posts only. Pages built
   in the editor use h2 for all sorts of things; a post that uses it at all is
   dividing itself into sections, and the rule says where each one starts. */
.kbia-single .kbia-prose > h2:not(:first-child) {
	margin-top: 2.25em;
	padding-top: 1.1em;
	border-top: 1px solid var(--kbia-border);
}

.kbia-prose a { color: var(--kbia-accent); }

/* An opening line that carries more weight than body copy -- the BIA's "300+
   Stores, Over 1000 Personalities, One Community" at the top of /about is the
   case it exists for. It is the interior-page equivalent of
   .kbia-band__standfirst on the homepage, and takes the same scale, so a page
   written in the editor can open the way a band does. Add `kbia-lede` to the
   paragraph in the block editor's Advanced > Additional CSS class field. */
.kbia-prose .kbia-lede {
	font-size: var(--kbia-fs-hero-lede);
	line-height: var(--kbia-lh-body);
	color: var(--kbia-heading);
	text-wrap: balance;
}

/* A closing line set apart from the body -- "Every Child Matters" at the foot
   of the Truth and Reconciliation post is the case it exists for. The short
   accent rule is the system's signature mark (docs/design-reference.md §4),
   borrowed at a smaller scale. Add `kbia-signoff` to a group or paragraph in
   the block editor's Advanced > Additional CSS class field. */
.kbia-prose .kbia-signoff {
	margin-top: 2.5em;
	font-family: var(--kbia-font-heading);
	font-size: clamp(1.125rem, 0.4vw + 1rem, 1.3125rem);  /* 18 -> 21 */
	line-height: 1.45;
	color: var(--kbia-heading);
	text-wrap: balance;
}

.kbia-prose .kbia-signoff::before {
	content: "";
	display: block;
	width: 3rem;
	height: 4px;
	margin-bottom: 1.25rem;
	border-radius: 2px;
	background: var(--kbia-accent);
}

/* font-size: inherit because My Listing sets `p` to 14px outright, which
   would otherwise undo the size above on every line inside the sign-off. */
.kbia-prose .kbia-signoff > * { margin: 0; font-size: inherit; }
.kbia-prose .kbia-signoff > * + * { margin-top: 0.4em; }
.kbia-prose .kbia-signoff__mark { font-weight: 700; }

/* Body copy on single posts, taken back from My Listing. The parent theme
   styles bare elements -- `p { font-size: 14px; line-height: 22px }` and
   `ol, ul { list-style-type: none; padding: 0 }` -- so inside .kbia-prose
   paragraphs came out at 14px under a column set to --kbia-fs-body (14 -> 18,
   docs/design-reference.md), and a list lost its bullets and numbers and read
   as loose lines. The migrated community posts are where both show: they are
   mostly paragraphs, and their steps, prizes and opening hours are lists.

   Single posts only. Pages built in the editor also use .kbia-prose and were
   laid out against the 14px they have always had. */
.kbia-single .kbia-prose p {
	font-size: inherit;
	line-height: inherit;
	color: inherit;
}

/* The rule above outranks .kbia-prose .kbia-lede, and the lede's own token
   (--kbia-fs-hero-lede, 14 -> 17) was sized against a 14px body; beside an
   18px one it would read smaller than the copy it introduces. It takes the
   sign-off's scale instead, so a post opens and closes at the same weight. */
.kbia-single .kbia-prose .kbia-lede {
	font-size: clamp(1.125rem, 0.4vw + 1rem, 1.3125rem);  /* 18 -> 21 */
	line-height: 1.55;
	color: var(--kbia-heading);
}

/* Content lists only: a gallery is a <ul class="blocks-gallery-grid"> and must
   stay a grid, and lists typed in the editor never carry a class. */
.kbia-single .kbia-prose :is(ul, ol):not([class]) { padding-left: 1.5em; }
.kbia-single .kbia-prose ul:not([class]) { list-style-type: disc; }
.kbia-single .kbia-prose ol:not([class]) { list-style-type: decimal; }
.kbia-single .kbia-prose ol:not([class])[type="a"] { list-style-type: lower-alpha; }
.kbia-single .kbia-prose :is(ul, ol):not([class]) > li + li { margin-top: 0.4em; }
.kbia-single .kbia-prose li > :is(ul, ol):not([class]) { margin-top: 0.4em; }

/* The migrated posts carry the old blog's images with fixed width attributes
   (up to 960px) and WordPress's .alignnone margin of 20px on the right, and
   pasted URLs with no break in them. Any one of them is wider than a phone. */
.kbia-single .kbia-prose { overflow-wrap: anywhere; }
.kbia-single .kbia-prose img { max-width: 100%; height: auto; }
.kbia-single .kbia-prose img.alignnone { margin-right: 0; }

/* An image set into the running text rather than across the column. Square
   and portrait graphics -- the social tiles the BIA makes for a post -- at
   the full ~70-character measure are taller than a phone screen, and push the
   copy they illustrate out of view. The importer's {{image:N}} placeholder
   writes this markup. */
.kbia-prose .kbia-prose-figure {
	max-width: min(100%, 30rem);
	margin-inline: auto;
}

.kbia-prose .kbia-prose-figure img {
	display: block;
	width: 100%;
	height: auto;
	border-radius: var(--kbia-radius-lg);
}

/* --- Location: the [kbia_map] shortcode (inc/map.php) --------------------
 *
 * An address, the map, and a way out to directions, as one card, so a post
 * that names two places reads as two stops rather than two maps floating in
 * the copy.
 *
 * The map ratio is set here with two classes on purpose. about.css defines
 * .kbia-map at 21:8 on wide screens -- right for a full-width band, a
 * letterbox inside a ~70-character column -- and it loads after this file, so
 * a single-class override here would lose to it on source order alone.
 */
.kbia-location {
	padding: 1rem;
	border: 1px solid var(--kbia-border);
	border-radius: var(--kbia-radius-xl);
	background: var(--kbia-surface);
}

@media (min-width: 40rem) {
	.kbia-location { padding: 1.25rem; }
}

.kbia-location__address {
	display: flex;
	gap: 0.6rem;
	align-items: flex-start;
	margin: 0 0 1rem;
	font-size: 1rem;      /* a <p>, so My Listing's 14px applies otherwise */
	font-weight: 600;
	line-height: 1.4;
	color: var(--kbia-heading);
}

.kbia-location__pin {
	flex: none;
	margin-top: 0.05em;
	color: var(--kbia-accent);
}

.kbia-location__note {
	display: block;
	margin-top: 0.15rem;
	font-weight: 400;
	color: var(--kbia-muted);
}

.kbia-location .kbia-map {
	aspect-ratio: 16 / 10;
	max-height: none;
	border-radius: var(--kbia-radius);
}

.kbia-location__link {
	display: inline-flex;
	margin-top: 1rem;
}

/* --- Event facts sidebar ------------------------------------------------- */
.kbia-facts {
	margin: 0 0 2rem;
	padding: 1.5rem;
	border-radius: var(--kbia-radius-xl);
	background: var(--kbia-surface-alt);
}

.kbia-facts dt {
	font-family: var(--kbia-font-mono);
	font-size: var(--kbia-fs-eyebrow);
	letter-spacing: var(--kbia-ls-eyebrow);
	text-transform: uppercase;
	color: var(--kbia-muted);
}

.kbia-facts dd {
	margin: 0.2rem 0 1rem;
	color: var(--kbia-body);
	line-height: var(--kbia-lh-body);
}

.kbia-facts dd:last-child { margin-bottom: 0; }

.kbia-single__aside .kbia-btn { width: 100%; margin-bottom: 1.5rem; }

/* --- Participating businesses -------------------------------------------- */
.kbia-partners {
	margin-top: 3rem;
	padding-top: 2rem;
	border-top: 1px solid var(--kbia-border);
}

.kbia-partners h2 {
	font-family: var(--kbia-font-heading);
	font-size: var(--kbia-fs-h3);
	color: var(--kbia-heading);
	margin: 0 0 1rem;
}

.kbia-partners__list {
	list-style: none;
	margin: 0;
	padding: 0;
	display: grid;
	gap: 0.75rem;
	grid-template-columns: repeat(auto-fit, minmax(min(100%, 15rem), 1fr));
}

/* --- Pagination ---------------------------------------------------------- */
.kbia-pagination {
	margin-top: 3rem;
	padding-top: 2rem;
	border-top: 1px solid var(--kbia-border);
}

.kbia-pagination :is(.page-numbers, a) {
	display: inline-block;
	padding: 0.5rem 0.9rem;
	font-family: var(--kbia-font-mono);
	font-variant-numeric: tabular-nums;
	text-decoration: none;
	color: var(--kbia-body);
	border: 1px solid var(--kbia-border);
	border-radius: var(--kbia-radius);
	margin-right: 0.35rem;
}

.kbia-pagination .current {
	background: var(--kbia-accent);
	border-color: var(--kbia-accent);
	color: var(--kbia-on-accent);
}

.kbia-pagination .screen-reader-text { position: absolute; left: -9999px; }

/* --- 404 ----------------------------------------------------------------- */
.kbia-404 .kbia-hero__title,
.kbia-404 .kbia-hero__eyebrow,
.kbia-404 .kbia-hero__standfirst {
	color: var(--kbia-heading);
}

.kbia-404 .kbia-hero__eyebrow { color: var(--kbia-muted); }
.kbia-404 .kbia-hero__standfirst { color: var(--kbia-body); margin-bottom: 2.5rem; }

/* --- WPForms -------------------------------------------------------------
   The two forms from scripts/build/create_forms.php carry `kbia-wpform`, so
   the plugin's own chrome can be brought into the token system without
   restyling every WPForms form on the site. WPForms ships rounded corners and
   its own blue; both are overridden here rather than in the plugin's theme
   settings, so the values stay next to the rest of the design system. */

/* WPForms' modern renderer does not take a border-radius from its own rules --
   it reads three custom properties, which it prints on `:root` in an inline
   <style> block at 3px. Overriding `border-radius` on our side loses: the
   plugin's declaration is `var(--wpforms-field-border-radius)` at a specificity
   we would have to fight, which is why `.kbia-btn` on the submit button was
   still rendering at 3px. Rebinding the variables on the container wins
   instead -- a custom property set on this element beats one inherited from
   :root, whatever the two selectors score -- and it reaches every control the
   plugin renders, including ones we have written no selector for. */
.kbia-wpform {
	--wpforms-field-border-radius: var(--kbia-radius);
	--wpforms-button-border-radius: var(--kbia-radius);
	--wpforms-container-border-radius: var(--kbia-radius-lg);
}

.kbia-wpform .wpforms-field {
	padding: 0 0 1.25rem;
}

.kbia-wpform .wpforms-field-label {
	display: block;
	font-family: var(--kbia-font-mono);
	font-size: var(--kbia-fs-eyebrow);
	letter-spacing: var(--kbia-ls-eyebrow);
	text-transform: uppercase;
	font-weight: 600;
	color: var(--kbia-muted);
	margin-bottom: 0.4rem;
}

.kbia-wpform .wpforms-field-sublabel,
.kbia-wpform .wpforms-field-description {
	font-size: var(--kbia-fs-eyebrow);
	color: var(--kbia-muted);
	line-height: var(--kbia-lh-body);
}

.kbia-wpform :is(input[type="text"], input[type="email"], input[type="tel"], input[type="url"], select, textarea) {
	width: 100%;
	padding: 0.75rem 1rem;
	font: inherit;
	color: var(--kbia-body);
	background: var(--kbia-surface);
	border: 1px solid var(--kbia-border);
	border-radius: var(--kbia-radius);
	box-shadow: var(--kbia-shadow);
}

/* Selects go back to WPForms' own zero block padding. The plugin fixes every
   control at its 43px height token, and the 0.75rem above left a select 19px
   of content box for a 29px line, so its label rendered cut in half. The
   container class is only for specificity: the rule above scores (0,2,1)
   through :is(), so this matches it and wins by coming after. */
.kbia-wpform.wpforms-container select {
	padding-block: 0;
}

.kbia-wpform :is(input, select, textarea):focus-visible {
	outline: var(--kbia-underline) solid var(--kbia-accent);
	outline-offset: 2px;
	border-color: var(--kbia-accent);
}

.kbia-wpform .wpforms-required-label { color: var(--kbia-warm-ink); }

.kbia-wpform .wpforms-error {
	color: var(--kbia-warm-ink);
	font-size: var(--kbia-fs-eyebrow);
}

.kbia-wpform .wpforms-confirmation-container-full {
	padding: 1.5rem;
	background: var(--kbia-surface-alt);
	border-left: var(--kbia-rule) solid var(--kbia-accent);
	border-radius: var(--kbia-radius-lg);
}

/* The newsletter form sits in the dark band 7, where the plugin's default
   label grey falls below contrast. Inline on desktop: it is two fields. */
.kbia-wpform--inline .wpforms-field-label,
.kbia-wpform--inline .wpforms-field-description {
	color: var(--kbia-blue-100);
}

@media (min-width: 40rem) {
	.kbia-wpform--inline form {
		display: grid;
		grid-template-columns: 1fr 1fr auto;
		gap: 0.75rem;
		align-items: end;
	}

	/* WPForms wraps every field in .wpforms-field-container and the button in
	   .wpforms-submit-container, so the three tracks above were being handed
	   those wrappers rather than the controls: both fields stacked in one
	   track and the button sat alongside them, half the column left empty.
	   `display: contents` lifts the fields into the form's own grid, so name,
	   email and button share one row of equal halves plus the button. The two
	   anti-spam fields WPForms injects are absolutely positioned and the
	   noscript fallback is emptied out below, so neither claims a track. */
	.kbia-wpform--inline .wpforms-field-container { display: contents; }
	.kbia-wpform--inline form > .wpforms-error-noscript { display: none; }

	/* The row's own spacing is the grid gap, so the field padding and the
	   button's top margin both go. A plain `.kbia-wpform--inline .wpforms-field`
	   only ties with WPForms' field rule and loses on load order, so the
	   container class is carried into the selector.

	   The submit container needs `.wpforms-form` as well. WPForms sets its
	   top margin from `div.wpforms-container-full .wpforms-form
	   .wpforms-submit-container`, which scores (0,3,1) and beat the (0,3,0)
	   this rule had: the 10px margin survived, the stretched container was 33px
	   inside the 43px row, and the button followed it. (0,4,0) wins. */
	.kbia-wpform--inline.wpforms-container .wpforms-field { padding: 0; }
	.kbia-wpform--inline.wpforms-container .wpforms-form .wpforms-submit-container {
		margin: 0;
		align-self: stretch;
	}

	/* The button is 41px from WPForms' own size token against a 43px input, so
	   it is stretched to the row instead: the three controls then share one top
	   and one bottom edge. The token itself cannot be rebound here -- for this
	   form the plugin prints it in an inline block on the container's id, which
	   outranks any class of ours. */
	.kbia-wpform--inline.wpforms-container button[type="submit"] { height: 100%; }
}

/* ==========================================================================
   DETAILS PAGE — the empty Gallery and Social Networks blocks

   My Listing hides both blocks when the listing has nothing in them, which on
   this site means hiding them from 290 of 347 listings. The two overrides in
   templates/single-listing/content-blocks/ render them anyway, and this is
   what they look like when there is nothing to show yet.

   Both follow the honesty rule from components.css: a visitor must never read
   a placeholder as the real thing. Hence the muted treatment, the caption in
   words, and -- for the social buttons -- inert <span>s rather than anchors,
   so there is nothing to click and nothing to disappoint.
   ========================================================================== */

.kbia-gallery-empty__frames {
	display: grid;
	grid-template-columns: repeat(3, 1fr);
	gap: 0.75rem;
	margin: 0;
	padding: 0;
	list-style: none;
}

/* 4:3 matches the shape the real carousel renders into, so the section does
   not change size the day photographs arrive. */
.kbia-gallery-empty__frame {
	position: relative;
	overflow: hidden;
	aspect-ratio: 4 / 3;
	border-radius: var(--kbia-radius-lg);
	background: var(--kbia-surface-alt);
}

.kbia-gallery-empty__frame img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	opacity: 0.55;
	filter: saturate(0.6);
}

.kbia-gallery-empty__note,
.kbia-social-empty__note {
	margin: 0.75rem 0 0;
	color: var(--kbia-muted);
	font-size: var(--kbia-fs-eyebrow);
}

.kbia-gallery-empty__note a,
.kbia-social-empty__note a { color: var(--kbia-accent); }

.kbia-social-empty {
	display: flex;
	flex-wrap: wrap;
	gap: 0.5rem;
	margin: 0;
	padding: 0;
	list-style: none;
}

/* Outlined to match the block's populated state, which the listing types are
   configured to render as `outlined-icons`. Muted and unclickable so the two
   are never mistaken for each other. */
.kbia-social-empty__btn {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	padding: 0.5rem 0.875rem;
	border: 1px solid var(--kbia-border);
	border-radius: var(--kbia-radius);
	background: var(--kbia-surface);
	color: var(--kbia-muted);
	font-size: var(--kbia-fs-eyebrow);
	cursor: default;
}

.kbia-social-empty__icon {
	display: inline-flex;
	opacity: 0.6;
}

.kbia-social-empty__icon .svg-icon svg {
	width: 1em;
	height: 1em;
	fill: currentColor;
}

@media (max-width: 40rem) {
	.kbia-gallery-empty__frames { grid-template-columns: repeat(2, 1fr); }
	.kbia-gallery-empty__frame:last-child { display: none; }
}
