/*
Theme Name: Dabuli
Theme URI: https://dabuli.org/
Description: An artistic, high-impact Full Site Editing block theme built for Dabuli — an arts & cultural non-profit. Fluid typography, a cool charcoal/gray/white palette, and modular block patterns keep artwork and community stories centre stage.
Author: Nepal Mandal
Author URI: https://nepalmandal.com/
Version: 1.0.0
Requires at least: 6.5
Tested up to: 6.7
Requires PHP: 8.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Text Domain: dabuli
Tags: full-site-editing, block-patterns, blog, portfolio, one-column, two-columns, wide-blocks, custom-colors, custom-logo, custom-menu, editor-style, featured-images, threaded-comments, translation-ready, accessibility-ready
*/

/*
 * ---------------------------------------------------------------------------
 * Dabuli — front-end utility layer
 * ---------------------------------------------------------------------------
 * Design tokens (colour, type, spacing, layout) live in theme.json.
 * This file only carries the small amount of structural polish that
 * theme.json cannot express: the header's centered desktop / left+hamburger
 * mobile layout, sticky chrome, dropdown styling, and card hover choreography.
 *
 * Breakpoint note: 600px is used throughout to match WordPress core's own
 * navigation block breakpoint (where it switches from the inline menu to the
 * hamburger-only toggle) — keeping our layout changes in lockstep with it.
 */

/*
 * Safety net for legacy/migrated page content: some pages (e.g. Connect)
 * carry embedded form markup from the old site with hardcoded pixel widths
 * that don't respect the mobile viewport, forcing the whole page — and with
 * it the fixed-position mobile menu — wider than the screen. WP core already
 * does this for images; form controls need it explicitly.
 */
input,
textarea,
select,
form {
	max-width: 100%;
	box-sizing: border-box;
}

/*
 * The actual culprit on the Connect page, traced down to its source: the
 * embedded Mailchimp signup form ships its own <style> block with
 * #mc_embed_signup{width:600px}. That ID selector beats the generic rule
 * above outright (the div itself isn't a form/input), so it needs calling
 * out by name. !important because the offending rule lives in the page's
 * own embedded <style>, which loads after this stylesheet.
 */
#mc_embed_signup,
#mc_embed_signup * {
	width: auto !important;
	max-width: 100% !important;
	box-sizing: border-box !important;
}

/* Long unbroken text (a raw URL used as its own link text, migrated content's
   habit) can force overflow on its own even after the fixes above — let any
   link wrap rather than push the page wider than the viewport. */
a {
	overflow-wrap: anywhere;
}

/*
 * Sticky header. This MUST live on the outer <header class="wp-block-template-part">
 * landmark, not on our inner .dabuli-header div — nesting it one level down
 * (verified empirically) silently fails to stick on this page's structure,
 * even with an !important inline override. The white background/padding stay
 * on the inner div; it fills the sticky box either way.
 */
header.wp-block-template-part {
	position: sticky;
	top: 0;
	z-index: 100;
}

.dabuli-header {
	border-bottom: 1px solid rgba(24, 24, 27, 0.08);
	transition: box-shadow 0.2s ease;
}

.dabuli-header.is-stuck {
	box-shadow: 0 8px 24px -16px rgba(24, 24, 27, 0.35);
}

.dabuli-brand .wp-block-site-logo {
	margin: 0;
}

/* Header layout: logo left, TRULY centered nav, button right — a 3-column
   grid handles the true centering regardless of how wide the logo/button are
   (flexbox space-between only centers the middle item when the sides match). */
.dabuli-header-row {
	display: grid;
	grid-template-columns: auto 1fr auto;
	align-items: center;
	column-gap: var(--wp--preset--spacing--30);
}

.dabuli-nav-wrap {
	min-width: 0;
	display: flex;
	justify-content: center;
}

.dabuli-nav-wrap .wp-block-navigation {
	min-width: 0;
	/* Items now carry their own hover-pill padding (below), so less bare
	   gap is needed between them than when the gap was the only spacing. */
	column-gap: 0.2rem !important;
}

/* Nav item hover (desktop bar): a soft rounded pill behind the WHOLE item —
   label and, for a submenu item, its chevron toggle too, since those are
   sibling elements (<a> + <button>) inside the same <li> — rather than
   just a text-color change. Modeled on elevationweb.org's nav. The pill
   lives on the <li> (.wp-block-navigation-item is already core's
   display:flex / align-items:center row for label+chevron), not the link
   itself, specifically so it wraps both children as one unit. */
.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item {
	border-radius: 999px;
	padding: 0.5rem 0.9rem;
	transition: background-color 0.25s ease;
}

/* The chevron toggle is a real <button>, which carries its own opaque
   browser-default background — left alone, that paints a small, slightly
   different-colored patch behind just the chevron, on top of whatever
   tint the <li>'s own pill background is showing (hover, or the
   .dabuli-nav-active-parent selected state). Making it transparent lets
   one continuous background show through across the whole pill. */
.dabuli-nav-wrap .wp-block-navigation-submenu__toggle {
	background-color: transparent;
}

.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item:hover,
.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item:focus-within {
	background-color: var(--wp--preset--color--warm-off-white);
}

/* Sliding hover indicator (see header.js): a single pill that glides
   between items — on top.wp-block-navigation__container, relative
   positioning anchors the indicator's absolute coordinates to the row as a
   whole, and raising each item's own stacking context above it (z-index:1)
   keeps the label/chevron readable as the indicator passes underneath. */
.dabuli-nav-wrap .wp-block-navigation__container {
	position: relative;
}

.dabuli-nav-indicator {
	position: absolute;
	top: 0;
	left: 0;
	height: 100%;
	border-radius: 999px;
	background-color: var(--wp--preset--color--warm-off-white);
	opacity: 0;
	transition: transform 0.28s cubic-bezier(0.22, 0.61, 0.36, 1), width 0.28s cubic-bezier(0.22, 0.61, 0.36, 1), opacity 0.18s ease;
	pointer-events: none;
	z-index: 0;
}

.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item {
	position: relative;
	z-index: 1;
}

/* Once the indicator script has initialized, it owns the moving highlight
   — each item's own instant background (above) would otherwise cross-fade
   underneath it at the same time the indicator slides, reading as two
   competing effects instead of one pill gliding across. Without JS (or if
   it throws before reaching this point), the plain per-item background
   stays as a working fallback. */
.dabuli-nav-wrap.dabuli-nav-indicator-ready .wp-block-navigation__container > .wp-block-navigation-item:hover,
.dabuli-nav-wrap.dabuli-nav-indicator-ready .wp-block-navigation__container > .wp-block-navigation-item:focus-within {
	background-color: transparent;
}

@media (max-width: 599px) {
	.dabuli-nav-indicator {
		display: none;
	}
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-nav-indicator {
		transition: opacity 0.18s ease;
	}
}

/* Nav link color: no underline (theme.json already turns off the default
   one for nav links) and no lift — the hover pill above is the feedback
   now, so the label itself only needs a gentle color shift. */
.dabuli-nav-wrap .wp-block-navigation-item__content {
	display: inline-block;
	transition: color 0.3s cubic-bezier(0.44, 0, 0.56, 1);
}

.dabuli-nav-wrap .wp-block-navigation-item__content:hover,
.dabuli-nav-wrap .wp-block-navigation-item__content:focus-visible {
	color: var(--wp--preset--color--terracotta-deep);
}

/* Active-page indicator (see header.js — WordPress's own current-menu-item
   detection doesn't fire for these custom-URL links). A soft rounded "chip"
   behind the label, like a selected tab, rather than a line underneath it —
   it hugs the text with its own padding, so there's no line-width math to
   get right the way there was with an underline. The tint stays light
   enough that the label's own text color (unchanged) keeps its normal
   contrast against it; the color only carries the background/border and a
   bolder weight, never the text itself. One rule covers the desktop bar,
   the dropdown panel, and the mobile overlay alike, since a background
   naturally adapts to each context's own padding instead of needing it
   repositioned per context the way the old underline did. */
.dabuli-nav-wrap .wp-block-navigation-item__content.dabuli-nav-active {
	background-color: rgba(0, 169, 209, 0.12);
	border: 1px solid rgba(0, 169, 209, 0.35);
	border-radius: 999px;
	padding: 0.3rem 0.85rem;
	font-weight: 600;
}

/* Has-child top-level parent, when the current page lives in its dropdown
   (e.g. viewing "About Us" or any project page — see header.js, which adds
   this class to the <li> rather than the link). The chevron toggle is the
   link's own sibling, not something nested inside it, so only a pill on
   the shared <li> wrapper — the same element the hover-state pill already
   uses — can highlight the label and the chevron together. Reuses the
   padding/radius every top-level <li> already carries (below); only the
   color needs adding here. */
.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item.dabuli-nav-active-parent {
	background-color: rgba(0, 169, 209, 0.12);
	border: 1px solid rgba(0, 169, 209, 0.35);
}

.dabuli-nav-wrap .wp-block-navigation__container > .wp-block-navigation-item.dabuli-nav-active-parent > .wp-block-navigation-item__content {
	font-weight: 600;
}

/* Logo: a small, unhurried lift on hover. */
.dabuli-brand .wp-block-site-logo a {
	display: inline-block;
	transition: transform 0.3s cubic-bezier(0.22, 0.61, 0.36, 1);
}

.dabuli-brand .wp-block-site-logo a:hover,
.dabuli-brand .wp-block-site-logo a:focus-visible {
	transform: scale(1.04);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-nav-wrap .wp-block-navigation-item__content,
	.dabuli-brand .wp-block-site-logo a {
		transition: none;
		transform: none;
	}
}

.dabuli-header-actions {
	display: flex;
	justify-content: flex-end;
}

/* On mobile: hide the CTA button and pin the (now hamburger-only) nav to the
   right edge of the remaining space, since there's no 3rd column pinning it there. */
@media (max-width: 599px) {
	/* !important: WordPress prints a per-instance "wp-container-core-group-is-layout-*"
	   rule for this block's own flex layout, same specificity, loaded after
	   this stylesheet — it otherwise wins over a plain override here. */
	.dabuli-header-actions {
		display: none !important;
	}

	.dabuli-nav-wrap {
		justify-content: flex-end;
	}
}

/* Navigation dropdown — DESKTOP hover menu only. Scoped to >=600px so this
   "floating card" styling never leaks into the flattened mobile overlay list. */
@media (min-width: 600px) {
	.dabuli-header .wp-block-navigation .wp-block-navigation__submenu-container {
		border: 1px solid rgba(24, 24, 27, 0.08);
		border-radius: 14px;
		padding: 0.5rem;
		box-shadow: var(--wp--preset--shadow--lift, 0 28px 48px -20px rgba(24, 24, 27, 0.32));
		background-color: var(--wp--preset--color--pure-white);
		/* core's own rule set is opacity-only (.1s linear) — this adds a
		   gentle fade + drop-in, closer to elevationweb.org's dropdown. */
		transition: opacity 0.22s ease, transform 0.22s cubic-bezier(0.22, 0.61, 0.36, 1), visibility 0.22s;
		transform: translateY(-6px);
	}

	/* Breathing room between the bar and the panel (was flush against the
	   trigger). A real gap here would be a dead zone for a pure-CSS hover
	   menu — moving the cursor straight down from the trigger into the
	   panel would cross empty space outside both elements' boxes and the
	   menu would close mid-move. The ::before below is an invisible
	   extension of the panel itself (same element, so it preserves :hover)
	   that exactly fills that gap, bridging it. */
	.dabuli-header .wp-block-navigation .has-child > .wp-block-navigation__submenu-container {
		top: calc(100% + 10px);
	}

	.dabuli-header .wp-block-navigation .has-child > .wp-block-navigation__submenu-container::before {
		content: "";
		position: absolute;
		left: 0;
		right: 0;
		top: -10px;
		height: 10px;
	}

	.dabuli-header .wp-block-navigation__submenu-container .wp-block-navigation-item {
		padding-inline: 0;
	}

	.dabuli-header .wp-block-navigation__submenu-container .wp-block-navigation-item__content {
		padding-block: 0.6rem;
		margin-inline: 0.3rem;
		border-radius: 9px;
	}

	.dabuli-header .wp-block-navigation__submenu-container .wp-block-navigation-item__content:hover,
	.dabuli-header .wp-block-navigation__submenu-container .wp-block-navigation-item__content:focus {
		color: var(--wp--preset--color--terracotta-deep);
		background-color: var(--wp--preset--color--warm-off-white);
	}

	/* WordPress core opens the hover/focus panel at a hard-coded min-width:200px
	   with wrapping item text — fine for short labels, but long submenu labels
	   ("Arts Classes & Workshop") wrap to two lines inside that fixed width.
	   Keep the 200px floor for short menus, but let the panel grow to fit its
	   widest label on one line instead of wrapping it. */
	.dabuli-header .wp-block-navigation__submenu-container .wp-block-navigation-item__content {
		white-space: nowrap;
	}

	.dabuli-header .wp-block-navigation .has-child:not(.open-on-click):hover > .wp-block-navigation__submenu-container,
	.dabuli-header .wp-block-navigation .has-child:not(.open-on-click):not(.open-on-hover-click):focus-within > .wp-block-navigation__submenu-container,
	.dabuli-header .wp-block-navigation .has-child .wp-block-navigation-submenu__toggle[aria-expanded="true"] ~ .wp-block-navigation__submenu-container {
		width: max-content !important;
		min-width: 200px;
		max-width: 320px;
		transform: translateY(0);
	}

	/* Chevron flips to point up while its panel is open — desktop only,
	   the mobile accordion (below) already drives its own rotation off
	   .dabuli-mobile-expanded instead of :hover. */
	.dabuli-header .wp-block-navigation .has-child .wp-block-navigation-submenu__toggle svg {
		transition: transform 0.22s ease;
	}

	.dabuli-header .wp-block-navigation .has-child:hover .wp-block-navigation-submenu__toggle svg,
	.dabuli-header .wp-block-navigation .has-child:focus-within .wp-block-navigation-submenu__toggle svg,
	.dabuli-header .wp-block-navigation .has-child .wp-block-navigation-submenu__toggle[aria-expanded="true"] svg {
		transform: rotate(180deg);
	}

	/* Directional dropdown entrance: moving from one dropdown item to
	   another (see header.js, which adds one of these two classes to the
	   newly-hovered panel based on which side the cursor came from) has the
	   new panel slide in from that side rather than just fading in place —
	   elevationweb.org does the same. A CSS *animation* (not a transition
	   on a changed property) is used specifically because it always plays
	   from its own "from" keyframe when the class is (re-)added, regardless
	   of whatever transform the panel happened to have a moment earlier —
	   a transition would only interpolate from that leftover value, which
	   is unreliable here since the hover state and the class both change
	   together. */
	@keyframes dabuli-submenu-slide-right {
		from {
			opacity: 0;
			transform: translateY(-6px) translateX(16px);
		}
		to {
			opacity: 1;
			transform: translateY(0) translateX(0);
		}
	}

	@keyframes dabuli-submenu-slide-left {
		from {
			opacity: 0;
			transform: translateY(-6px) translateX(-16px);
		}
		to {
			opacity: 1;
			transform: translateY(0) translateX(0);
		}
	}

	.dabuli-header .wp-block-navigation .has-child:hover > .wp-block-navigation__submenu-container.dabuli-slide-right,
	.dabuli-header .wp-block-navigation .has-child:focus-within > .wp-block-navigation__submenu-container.dabuli-slide-right {
		animation: dabuli-submenu-slide-right 0.26s cubic-bezier(0.22, 0.61, 0.36, 1) forwards;
	}

	.dabuli-header .wp-block-navigation .has-child:hover > .wp-block-navigation__submenu-container.dabuli-slide-left,
	.dabuli-header .wp-block-navigation .has-child:focus-within > .wp-block-navigation__submenu-container.dabuli-slide-left {
		animation: dabuli-submenu-slide-left 0.26s cubic-bezier(0.22, 0.61, 0.36, 1) forwards;
	}

	@media (prefers-reduced-motion: reduce) {
		.dabuli-header .wp-block-navigation .wp-block-navigation__submenu-container {
			transition: opacity 0.22s ease, visibility 0.22s;
			transform: none;
		}

		.dabuli-header .wp-block-navigation .has-child > .wp-block-navigation__submenu-container.dabuli-slide-right,
		.dabuli-header .wp-block-navigation .has-child > .wp-block-navigation__submenu-container.dabuli-slide-left {
			animation: none;
		}
	}
}

/*
 * Mobile overlay menu — accordion behavior.
 *
 * Core WordPress forces every submenu permanently open inside the mobile
 * overlay (no accordion, no differentiation from top-level items) — by
 * design, not a bug on our end. We override that here with our own
 * independent toggle (driven by header.js adding/removing
 * .dabuli-mobile-expanded), so subitems stay collapsed behind a chevron
 * until tapped, and read clearly as children once open.
 */
@media (max-width: 599px) {
	/*
	 * The menu panel covers the full viewport by default (WordPress's own
	 * top:0), which buries the header — logo included — behind it while
	 * open. Starting it below the header instead keeps the header genuinely
	 * visible (not just painted over), which also means our own open/close
	 * button in the header is no longer hidden underneath the panel — so
	 * WordPress's separate close button (pinned to the bare top-right
	 * corner of the panel, no padding) is redundant and hidden; our button
	 * already forwards clicks to it.
	 */
	.wp-block-navigation__responsive-container.is-menu-open {
		top: var(--dabuli-header-height, 74px) !important;
	}

	.wp-block-navigation__responsive-container-close {
		display: none !important;
	}

	/* WordPress stacks each nav item as a column here (link above its own
	   always-open submenu, its own default) — put the link + chevron back on
	   one row, with the submenu forced onto its own full-width line below. */
	.wp-block-navigation__responsive-container.is-menu-open .has-child {
		flex-direction: row !important;
		flex-wrap: wrap;
		justify-content: center;
		align-items: center;
		column-gap: 0.35rem;
	}

	/* The active-parent pill (desktop: see .dabuli-nav-active-parent above)
	   is sized for a row containing just the label + chevron. On mobile the
	   submenu sits inside that same <li>, in normal flow (flex-basis:100%,
	   not absolutely positioned like the desktop dropdown) — once expanded,
	   the <li>'s own background/border would stretch around the label,
	   chevron, AND the whole open list below it, reading as one big ring
	   around the entire section rather than a highlight on "About" itself.
	   The open submenu already makes which section you're in obvious, so
	   the parent ring is just dropped here; the bold label weight (set
	   alongside it above) is kept as a quieter collapsed-state hint. */
	.wp-block-navigation__responsive-container.is-menu-open .has-child.dabuli-nav-active-parent {
		background-color: transparent;
		border-color: transparent;
	}

	.wp-block-navigation__responsive-container.is-menu-open .has-child .wp-block-navigation__submenu-container {
		display: none;
		flex-basis: 100%;
		position: static;
		border: none;
		box-shadow: none;
		background: transparent;
		padding-left: 1.25rem;
	}

	.wp-block-navigation__responsive-container.is-menu-open .has-child.dabuli-mobile-expanded .wp-block-navigation__submenu-container {
		display: flex;
	}

	.wp-block-navigation__responsive-container.is-menu-open .has-child .wp-block-navigation__submenu-container .wp-block-navigation-item__content {
		font-size: var(--wp--preset--font-size--small);
		color: var(--wp--preset--color--ink-muted);
	}

	/*
	 * WordPress core hides the chevron entirely inside the mobile overlay
	 * (.wp-block-navigation__responsive-container.is-menu-open ...
	 * .wp-block-navigation__submenu-icon { display: none }) — its own
	 * "always show everything flattened" design, not a bug on our end. We
	 * need it visible and tappable here for the accordion above to work at
	 * all, so this reinstates it — small and centered on the text line
	 * rather than the oversized touch-target version tried first, which
	 * read as too big next to the label.
	 */
	.wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__submenu-icon {
		display: inline-flex !important;
		align-items: center;
		justify-content: center;
		width: 1rem;
		height: 1rem;
		padding: 0.35rem;
		box-sizing: content-box;
	}

	.wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__submenu-icon svg {
		width: 100%;
		height: 100%;
		margin-top: 0;
	}

	/*
	 * Rotation: WordPress's own rule rotates this 180deg whenever
	 * aria-expanded="true" — which core sets by default here (a leftover
	 * from the desktop hover-dropdown this same toggle also drives), so it
	 * rendered "already open" before anything had been tapped. Both rules
	 * below are !important so they win outright rather than depending on
	 * that attribute: closed points down (0deg) unconditionally, open
	 * (our own .dabuli-mobile-expanded class) points up — matching what the
	 * accordion is actually doing, not what core's unrelated default said.
	 */
	.wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation-submenu__toggle > svg {
		transform: rotate(0deg) !important;
		transition: transform 0.2s ease;
	}

	.wp-block-navigation__responsive-container.is-menu-open .has-child.dabuli-mobile-expanded > .wp-block-navigation-submenu__toggle > svg {
		transform: rotate(180deg) !important;
	}

	/* "Get Involved" appended as the last item inside the mobile menu itself —
	   not part of the sticky header on this breakpoint. Hidden on desktop,
	   where it already lives in .dabuli-header-actions instead. */
	.dabuli-mobile-cta {
		margin-top: var(--wp--preset--spacing--30);
		justify-content: center;
	}
}

@media (min-width: 600px) {
	/* !important: same reason as .dabuli-header-actions above — WordPress's
	   own per-instance flex-layout rule otherwise wins and this button
	   duplicates the one already in .dabuli-header-actions. */
	.dabuli-mobile-cta {
		display: none !important;
	}
}

/* Hamburger / close icon: a real three-line hamburger (via the nav block's
   "menu" icon), sized up and given breathing room so it's not a tiny mark
   jammed into the corner. */
.wp-block-navigation__responsive-container-open {
	padding: 0.5rem;
}

.wp-block-navigation__responsive-container-open svg {
	width: 26px;
	height: 26px;
}

/* A gentle lift on every filled button/link-button, site-wide */
.wp-element-button {
	transition: transform 0.25s cubic-bezier(0.22, 0.61, 0.36, 1), box-shadow 0.25s ease, background-color 0.25s ease;
}

.wp-element-button:hover,
.wp-element-button:focus-visible {
	transform: translateY(-2px);
}

@media (prefers-reduced-motion: reduce) {
	.wp-element-button:hover,
	.wp-element-button:focus-visible {
		transform: none;
	}
}

/* Project / news cards — lift + reveal on hover or keyboard focus */
.dabuli-card {
	height: 100%;
	transition: transform 0.35s ease, box-shadow 0.35s ease;
}

.dabuli-card:hover,
.dabuli-card:focus-within {
	transform: translateY(-6px);
	box-shadow: var(--wp--preset--shadow--lift, 0 34px 64px -32px rgba(24, 24, 27, 0.5));
}

.dabuli-card .wp-block-image,
.dabuli-card figure {
	overflow: hidden;
	margin: 0;
}

.dabuli-card img {
	display: block;
	width: 100%;
	aspect-ratio: 4 / 3;
	object-fit: cover;
	transition: transform 0.6s cubic-bezier(0.2, 0.8, 0.2, 1);
}

.dabuli-card:hover img,
.dabuli-card:focus-within img {
	transform: scale(1.05);
}

/* Thin color accent flush across the top of a .dabuli-card, one palette
   color per card (see the homepage Core Programs cards) — the color itself
   is set inline per instance since it varies card to card. */
.dabuli-card-accent {
	display: block;
	height: 10px;
	width: 100%;
}

/* Instagram feed placeholder tiles */
.dabuli-instagram-tile {
	aspect-ratio: 1 / 1;
	border: 1px solid rgba(24, 24, 27, 0.08);
	background: linear-gradient(135deg, var(--wp--preset--color--warm-sand), var(--wp--preset--color--warm-off-white));
}

/* Hero display heading rhythm */
.dabuli-hero__title {
	max-width: 18ch;
	margin-inline: auto;
	text-wrap: balance;
}

/* News list rows */
.dabuli-news-item {
	border-bottom: 1px solid rgba(24, 24, 27, 0.12);
}

.dabuli-news-item:last-of-type {
	border-bottom: 0;
}

/* Footer legibility on the dark panel */
.dabuli-footer a:where(:not(.wp-element-button)) {
	text-decoration: none;
	color: inherit;
}

.dabuli-footer a:where(:not(.wp-element-button)):hover,
.dabuli-footer a:where(:not(.wp-element-button)):focus {
	color: var(--wp--preset--color--gold);
	text-decoration: underline;
}

/* Quick Links is a core/navigation block, whose own CSS forces its anchor's
   color to `inherit` via a same-specificity-boosted selector
   (.wp-block-navigation-item__content.wp-block-navigation-item__content),
   which otherwise beats the generic footer-link hover rule above and makes
   Quick Links not visibly react on hover at all. Match that selector's
   specificity so Quick Links gets the same gold hover as Recent Posts. */
.dabuli-footer .wp-block-navigation .wp-block-navigation-item__content:hover,
.dabuli-footer .wp-block-navigation .wp-block-navigation-item__content:focus {
	color: var(--wp--preset--color--gold);
	text-decoration: underline;
}

.dabuli-footer .wp-block-navigation {
	font-family: var(--wp--preset--font-family--dabuli-body);
	font-size: var(--wp--preset--font-size--medium) !important;
	font-weight: 400;
}

/* Raleway's lower x-height reads noticeably smaller than the old body font
   did at the same size — bump the footer's running text (mission copy,
   Recent Posts links, newsletter blurb) up a step. The uppercase, letter-
   spaced column labels (h3) are left alone; they're a distinct UI treatment,
   not body copy. !important: these blocks set font-size inline via block
   attributes, which otherwise wins over a plain class rule here. */
.dabuli-footer p,
.dabuli-footer .wp-block-post-title {
	font-size: var(--wp--preset--font-size--medium) !important;
}

/* Soften the divider between Quick Links and Newsletter on the dark panel. */
.dabuli-footer .wp-block-separator {
	border-color: rgba(255, 255, 255, 0.18);
}

.dabuli-footer .wp-block-social-links.is-style-logos-only .wp-social-link {
	opacity: 0.85;
	transition: opacity 0.2s ease, transform 0.2s ease;
}

.dabuli-footer .wp-block-social-links.is-style-logos-only .wp-social-link:hover,
.dabuli-footer .wp-block-social-links.is-style-logos-only .wp-social-link:focus-within {
	opacity: 1;
	transform: translateY(-2px);
}

/* Footer bottom bar: bare 24x24 icons, grayed out at rest, white on hover. */
.dabuli-footer-social.wp-block-social-links {
	flex-wrap: wrap;
}

.dabuli-footer-social .wp-social-link a {
	padding: 0.35rem;
}

.dabuli-footer-social .wp-social-link svg {
	width: 24px;
	height: 24px;
}

.dabuli-footer-social .wp-social-link {
	transition: color 0.2s ease;
}

.dabuli-footer-social .wp-social-link:hover,
.dabuli-footer-social .wp-social-link:focus-within {
	color: #ffffff;
}

.dabuli-footer-bottom a:where(:not(.wp-social-link a)) {
	color: inherit;
}

/* Recent Posts column: query-loop post titles read like the other footer link lists.
   line-height: post-title renders as an h2, which inherits the theme's tight
   1.1 heading line-height by default — much tighter than the 1.7 body copy
   in column 1, which is why wrapped titles here looked cramped. Match it to
   the body line-height instead. */
.dabuli-footer .wp-block-post-title {
	margin: 0;
	font-weight: 400;
	line-height: 1.7;
}

/* Recent Posts list: plain stacked links, full titles, no marker — the gap
   between wp:post-template items (set on the block itself) is what separates
   each row. */
.dabuli-footer .wp-block-post-template {
	list-style: none;
	margin: 0;
	padding: 0;
}

/* Screen-reader-only labels (footer newsletter form field). */
.screen-reader-text {
	position: absolute;
	width: 1px;
	height: 1px;
	overflow: hidden;
	clip: rect(1px, 1px, 1px, 1px);
	white-space: nowrap;
}

/* Footer newsletter signup form. */
.dabuli-newsletter-row {
	display: flex;
	gap: 0.5rem;
	margin-top: var(--wp--preset--spacing--20);
}

.dabuli-newsletter-row input[type="email"] {
	flex: 1;
	min-width: 0;
	padding: 0.6rem 0.9rem;
	border: 1px solid rgba(255, 255, 255, 0.25);
	border-radius: 999px;
	background: transparent;
	color: var(--wp--preset--color--pure-white);
	font-size: var(--wp--preset--font-size--small);
	font-family: var(--wp--preset--font-family--dabuli-body);
}

.dabuli-newsletter-row input[type="email"]::placeholder {
	color: rgba(255, 255, 255, 0.5);
}

.dabuli-newsletter-row input[type="email"]:focus-visible {
	outline: 2px solid var(--wp--preset--color--gold-deep);
	outline-offset: 2px;
}

.dabuli-newsletter-submit {
	flex-shrink: 0;
	padding: 0.6rem 1.15rem;
	border: none;
	border-radius: 999px;
	background: var(--wp--preset--color--pure-white);
	color: var(--wp--preset--color--deep-charcoal);
	font-family: var(--wp--preset--font-family--dabuli-text);
	font-size: var(--wp--preset--font-size--small);
	font-weight: 600;
	cursor: pointer;
	transition: background 0.2s ease, transform 0.2s ease;
}

.dabuli-newsletter-submit:hover,
.dabuli-newsletter-submit:focus-visible {
	background: var(--wp--preset--color--gold-deep);
	transform: translateY(-2px);
}

/* Mailchimp spam-trap field: must stay off-screen and out of tab order, never visible. */
.dabuli-honeypot {
	position: absolute;
	left: -5000px;
}

@media (max-width: 480px) {
	.dabuli-newsletter-row {
		flex-wrap: wrap;
	}

	.dabuli-newsletter-submit {
		flex-basis: 100%;
	}
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-card,
	.dabuli-card img {
		transition: none;
	}
}

/* Floating "back to top" button (see functions.php + back-to-top.js). Hidden
   until back-to-top.js adds .is-visible after the visitor scrolls. */
.dabuli-back-to-top {
	position: fixed;
	right: 1.5rem;
	bottom: 1.5rem;
	z-index: 90;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 44px;
	height: 44px;
	border: none;
	border-radius: 50%;
	background-color: var(--wp--preset--color--deep-charcoal);
	color: var(--wp--preset--color--pure-white);
	box-shadow: var(--wp--preset--shadow--lift, 0 12px 28px -10px rgba(24, 24, 27, 0.4));
	cursor: pointer;
	opacity: 0;
	visibility: hidden;
	transform: translateY(12px);
	transition: opacity 0.25s ease, transform 0.25s ease, background-color 0.2s ease;
}

.dabuli-back-to-top.is-visible {
	opacity: 1;
	visibility: visible;
	transform: translateY(0);
}

.dabuli-back-to-top:hover,
.dabuli-back-to-top:focus-visible {
	background-color: var(--wp--preset--color--terracotta-deep);
}

.dabuli-back-to-top svg {
	width: 20px;
	height: 20px;
}

@media (max-width: 599px) {
	.dabuli-back-to-top {
		right: 1rem;
		bottom: 1rem;
		width: 40px;
		height: 40px;
	}
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-back-to-top {
		transition: opacity 0.2s ease;
		transform: none;
	}
}

/* Blog archive grid — 3 columns desktop, 2 tablet, 1 mobile (matches the
   charis.framer.website/blog reference). WP's own "grid" layout type doesn't
   vary column count per breakpoint, so the responsive steps are hand-rolled. */
.dabuli-blog-grid.wp-block-post-template {
	display: grid !important;
	grid-template-columns: repeat(3, 1fr) !important;
}

@media (max-width: 909px) {
	.dabuli-blog-grid.wp-block-post-template {
		grid-template-columns: repeat(2, 1fr) !important;
	}
}

@media (max-width: 599px) {
	.dabuli-blog-grid.wp-block-post-template {
		grid-template-columns: 1fr !important;
	}
}

/* Blog card: rounded image with a hover zoom, clipped to the rounded corners. */
.dabuli-blog-card-image {
	overflow: hidden;
	border-radius: 16px;
}

.dabuli-blog-card-image img {
	display: block;
	transition: transform 0.5s cubic-bezier(0.22, 0.61, 0.36, 1);
}

.dabuli-blog-card-image:hover img,
.dabuli-blog-card-image:focus-within img {
	transform: scale(1.08);
}

.dabuli-blog-card .wp-block-post-title {
	margin: 0;
}

/* Scroll-in reveal: each card starts hidden/offset, then fades and slides up
   into place as it enters the viewport (see scroll-reveal.js). Cards are
   staggered via --dabuli-reveal-index, set per-card by the script so the grid
   loads in one by one rather than all at once. */
.dabuli-blog-card {
	opacity: 0;
	transform: translateY(32px);
	transition: opacity 0.5s ease, transform 0.6s cubic-bezier(0.22, 0.61, 0.36, 1);
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 140ms);
}

.dabuli-blog-card.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-blog-card {
		opacity: 1;
		transform: none;
		transition: none;
	}
}

/* Single post: the same scroll-in reveal, applied to the hero image and each
   top-level block of the post content (see scroll-reveal.js). A lighter lift
   than the grid cards since these are usually text-height, not a full card. */
.dabuli-content-reveal {
	opacity: 0;
	transform: translateY(22px);
	transition: opacity 0.5s ease, transform 0.6s cubic-bezier(0.22, 0.61, 0.36, 1);
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 90ms);
}

.dabuli-content-reveal.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-content-reveal {
		opacity: 1;
		transform: none;
		transition: none;
	}
}

/* Generic page-hero reveal (About hero's photo + headline column + text
   column, and any future page-hero template using the same pattern) — kept
   as its own class rather than reusing .dabuli-content-reveal, since that
   one is wired up in scroll-reveal.js specifically to single-post pages
   (hero image + auto-tagged content blocks) and this needs to work on
   plain pages too, for a small, explicitly-marked group of elements. */
.dabuli-hero-reveal {
	opacity: 0;
	transform: translateY(26px);
	transition: opacity 0.6s ease, transform 0.7s cubic-bezier(0.22, 0.61, 0.36, 1);
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 130ms);
}

.dabuli-hero-reveal.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-hero-reveal {
		opacity: 1;
		transform: none;
		transition: none;
	}
}

/* Project page hero: the featured photo loads dark and desaturated, then
   eases into its natural color, like the image is "waking up". Runs as a
   plain CSS animation (no JS) so it starts the instant the image paints —
   `both` keeps the dark starting state applied before the animation begins
   and holds the final state afterwards. The eyebrow/title group follows a
   beat later with its own fade-up, so the sequence reads as photo, then
   text, rather than everything arriving at once. */
@keyframes dabuli-hero-color-reveal {
	from {
		filter: grayscale(85%) brightness(0.55) saturate(0.7);
	}
	to {
		filter: grayscale(0%) brightness(1) saturate(1);
	}
}

@keyframes dabuli-hero-text-reveal {
	from {
		opacity: 0;
		transform: translateY(18px);
	}
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

.dabuli-project-hero .wp-block-cover__image-background,
.dabuli-page-hero .wp-block-cover__image-background {
	animation: dabuli-hero-color-reveal 1.7s ease-out both;
}

.dabuli-hero-text-reveal {
	animation: dabuli-hero-text-reveal 0.9s ease-out 0.6s both;
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-project-hero .wp-block-cover__image-background,
	.dabuli-page-hero .wp-block-cover__image-background {
		animation: none;
		filter: none;
	}

	.dabuli-hero-text-reveal {
		animation: none;
		opacity: 1;
		transform: none;
	}
}

/* Pagination: pill-style current/hover states instead of plain text links. */
.dabuli-blog-pagination {
	gap: 0.5rem;
}

.dabuli-blog-pagination .page-numbers {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	min-width: 2.25rem;
	height: 2.25rem;
	padding-inline: 0.5rem;
	border-radius: 999px;
	text-decoration: none !important;
	color: var(--wp--preset--color--deep-charcoal);
	transition: background-color 0.2s ease, color 0.2s ease;
}

.dabuli-blog-pagination .page-numbers.current {
	background-color: var(--wp--preset--color--terracotta-deep);
	color: var(--wp--preset--color--pure-white);
}

.dabuli-blog-pagination .page-numbers:not(.current):hover {
	background-color: var(--wp--preset--color--warm-off-white);
}

.dabuli-blog-pagination .wp-block-query-pagination-previous,
.dabuli-blog-pagination .wp-block-query-pagination-next {
	color: var(--wp--preset--color--deep-charcoal);
}

/* Single post prev/next: with showTitle on, core renders a bare title link
   and nothing else by default — no "Previous"/"Next" wording, no arrow — so
   it reads as a random inline link rather than navigation. linkLabel+arrow
   (set on the block in single.html) bring back the "Previous:"/"Next:" text
   and the → / ← glyph; these rules just style them to read as a label +
   control instead of plain paragraph text. */
.wp-block-post-navigation-link .post-navigation-link__label {
	display: block;
	text-transform: uppercase;
	letter-spacing: 0.08em;
	font-weight: 600;
	color: var(--wp--preset--color--ink-muted);
	margin-bottom: 0.15rem;
}

.wp-block-post-navigation-link .post-navigation-link__title {
	font-weight: 500;
}

.wp-block-post-navigation-link a {
	display: inline-block;
	text-decoration: none;
}

.wp-block-post-navigation-link a:hover .post-navigation-link__title,
.wp-block-post-navigation-link a:focus-visible .post-navigation-link__title {
	text-decoration: underline;
}

/* On wide screens the two sit side by side (.dabuli-post-nav-row is a
   space-between flex row — see single.html) — right-align "Next" so both
   labels/arrows point outward toward their own edge of the row instead of
   both hugging the left like they do stacked on mobile. Below 600px the
   row is forced back to a single column, matching the rest of the site's
   mobile breakpoint, since two short lines side by side at that width reads
   cramped rather than as a clear left/right pair. */
@media (min-width: 600px) {
	.dabuli-post-nav-row .wp-block-post-navigation-link.post-navigation-link-next {
		text-align: right;
	}
}

@media (max-width: 599px) {
	.dabuli-post-nav-row {
		flex-direction: column;
	}

	/* The link itself is inline-block sized to its widest wrapped line (the
	   title), which on a narrow screen claims the full row width on its
	   own — leaving no room for the arrow to sit beside it, so it wraps
	   onto its own line above the label instead. Flex here keeps the arrow
	   and the label+title stack side by side the way they already sit on
	   the wider desktop row. */
	.dabuli-post-nav-row .wp-block-post-navigation-link {
		display: flex;
		align-items: center;
		gap: 0.4em;
	}
}

.wp-block-post-navigation-link__arrow-previous,
.wp-block-post-navigation-link__arrow-next {
	color: var(--wp--preset--color--ink-muted);
}

.wp-block-post-navigation-link__arrow-previous {
	margin-right: 0.4em;
}

.wp-block-post-navigation-link__arrow-next {
	margin-left: 0.4em;
}

/* "Our Core Values" section (About page, modeled on
   charis.framer.website/about-us-v3's values band) — 4 columns desktop,
   2 tablet, 1 mobile, same hand-rolled breakpoints as the blog grid since
   WP's own "grid" layout type doesn't vary column count on its own. */
.dabuli-values-grid.wp-block-group {
	display: grid !important;
	grid-template-columns: repeat(4, 1fr) !important;
}

@media (max-width: 909px) {
	.dabuli-values-grid.wp-block-group {
		grid-template-columns: repeat(2, 1fr) !important;
	}
}

@media (max-width: 599px) {
	.dabuli-values-grid.wp-block-group {
		grid-template-columns: 1fr !important;
	}
}

/* "What You Can Learn" (Arts Classes & Workshops page) — a portrait
   photo-and-text zigzag per category (Music/Dance/Arts), replacing the
   old 3-card grid: deliberately card-free (no border, no background
   tile) for a more editorial, white-space-forward feel. Each row
   alternates which side the photo sits on via block order; the CSS
   only needs to size the photo and space the text consistently. */
.dabuli-class-row.wp-block-columns {
	margin-top: var(--wp--preset--spacing--70) !important;
	/* Core forces align-items:initial with !important on the base
	   .wp-block-columns rule, which silently defeats the block's own
	   "vertically aligned center" class -- only another !important can
	   win that fight. */
	align-items: center !important;
	/* The generated per-block container class only sets a gap when the
	   editor's own "blockGap" control was used; ours wasn't, so without
	   this the columns sit flush with no gap at all. */
	column-gap: var(--wp--preset--spacing--70) !important;
	row-gap: var(--wp--preset--spacing--40) !important;
}

.dabuli-class-row.wp-block-columns:first-of-type {
	margin-top: var(--wp--preset--spacing--40) !important;
}

/* Reusable modifier for a zigzag row where the photo should sit on the
   right on desktop: the block markup always keeps the photo column
   first in source order (so mobile always stacks photo-then-text,
   never text-then-photo) and this just visually swaps the two columns
   above the mobile breakpoint via flex direction instead of DOM order.
   Reuse this same "<row-class> <row-class>--reverse" pairing on any
   future page's photo/text rows. */
@media (min-width: 782px) {
	.dabuli-class-row--reverse.wp-block-columns {
		flex-direction: row-reverse;
	}
}

.dabuli-class-photo img {
	width: 100%;
	aspect-ratio: 1 / 1;
	object-fit: cover;
	border-radius: 20px;
	box-shadow: 0 28px 48px -20px rgba(24, 24, 27, 0.18);
}

/* Landscape variant — for rows whose source photo is a wide screenshot or
   event shot (e.g. the Language Digitization page's "Key Initiatives" rows)
   rather than a portrait photo; same row/content chrome, different crop. */
.dabuli-class-photo--landscape img {
	aspect-ratio: 3 / 2;
}

.dabuli-class-content > * + * {
	margin-top: var(--wp--preset--spacing--20);
}

@media (max-width: 781px) {
	.dabuli-class-row.wp-block-columns {
		margin-top: var(--wp--preset--spacing--50) !important;
		column-gap: var(--wp--preset--spacing--40) !important;
	}
}

/* Card-free photo grid — a 2-up grid of photo + heading + text, no border
   or background tile, for presenting several items side by side instead of
   as a run of full-width zigzag rows (e.g. secondary spaces on the Dabuli
   Chhen page, after one is pulled out as a full zigzag "featured" row).
   Reuses .dabuli-class-photo for the image treatment and .dabuli-class-content
   for the heading/text spacing, so it stays visually consistent with the
   zigzag rows it's paired with. */
.dabuli-photo-card-grid.wp-block-group {
	display: grid !important;
	grid-template-columns: repeat(2, 1fr) !important;
	column-gap: var(--wp--preset--spacing--40) !important;
	row-gap: var(--wp--preset--spacing--50) !important;
	margin-top: var(--wp--preset--spacing--50) !important;
}

@media (max-width: 599px) {
	.dabuli-photo-card-grid.wp-block-group {
		grid-template-columns: 1fr !important;
	}
}

.dabuli-photo-card .dabuli-class-content {
	margin-top: var(--wp--preset--spacing--20);
}

/* CSS-only space selector (radio tabs, no JS): used to walk through a set
   of rooms/spaces one at a time instead of stacking repeated photo+text
   rows (e.g. the Dabuli Chhen "Multipurpose Cultural Hub" section). The
   hidden radio inputs and the tab list / panel wrapper must stay direct
   siblings inside .dabuli-space-tab-fieldset for the :checked ~ selectors
   below to reach both the active label and the visible panel. */
.dabuli-space-tabs {
	margin-top: var(--wp--preset--spacing--50);
}

.dabuli-space-tab-fieldset {
	border: none;
	margin: 0;
	padding: 0;
}

.dabuli-space-tab-input {
	position: absolute;
	opacity: 0;
	pointer-events: none;
}

.dabuli-space-tab-list {
	display: flex;
	flex-wrap: wrap;
	gap: var(--wp--preset--spacing--30);
	border-bottom: 1px solid var(--wp--preset--color--warm-sand);
}

.dabuli-space-tab-label {
	display: inline-flex;
	align-items: center;
	gap: 0.5em;
	padding: 0.7em 0.1em;
	cursor: pointer;
	color: var(--wp--preset--color--ink-muted);
	font-weight: 500;
	border-bottom: 3px solid transparent;
	margin-bottom: -1px;
	transition: color 0.2s ease, border-color 0.2s ease;
}

.dabuli-space-tab-label:hover {
	color: var(--wp--preset--color--deep-charcoal);
}

.dabuli-space-tab-num {
	font-size: 0.75em;
	font-weight: 700;
	color: var(--wp--preset--color--terracotta-deep);
	opacity: 0.65;
}

.dabuli-space-tab-panels {
	margin-top: var(--wp--preset--spacing--50);
}

.dabuli-space-tab-panel {
	display: none;
	flex-direction: column;
	gap: var(--wp--preset--spacing--40);
	align-items: center;
}

.dabuli-space-tab-photo {
	width: 100%;
	aspect-ratio: 3 / 2;
	object-fit: cover;
	border-radius: 16px;
	display: block;
}

.dabuli-space-tab-eyebrow {
	display: block;
	font-size: 0.8rem;
	font-weight: 700;
	letter-spacing: 0.08em;
	text-transform: uppercase;
	color: var(--wp--preset--color--terracotta-deep);
	margin: 0 0 0.6em;
}

.dabuli-space-tab-content p {
	margin-top: 0.5em;
}

@media (min-width: 782px) {
	.dabuli-space-tab-panel {
		flex-direction: row;
		align-items: center;
	}

	.dabuli-space-tab-photo {
		flex: 0 0 55%;
	}

	.dabuli-space-tab-content {
		flex: 1;
	}
}

#space-tab-1:checked ~ .dabuli-space-tab-list label[for="space-tab-1"],
#space-tab-2:checked ~ .dabuli-space-tab-list label[for="space-tab-2"],
#space-tab-3:checked ~ .dabuli-space-tab-list label[for="space-tab-3"],
#space-tab-4:checked ~ .dabuli-space-tab-list label[for="space-tab-4"],
#space-tab-5:checked ~ .dabuli-space-tab-list label[for="space-tab-5"] {
	color: var(--wp--preset--color--deep-charcoal);
	border-bottom-color: var(--wp--preset--color--terracotta-deep);
}

#space-tab-1:checked ~ .dabuli-space-tab-panels .dabuli-space-tab-panel[data-panel="1"],
#space-tab-2:checked ~ .dabuli-space-tab-panels .dabuli-space-tab-panel[data-panel="2"],
#space-tab-3:checked ~ .dabuli-space-tab-panels .dabuli-space-tab-panel[data-panel="3"],
#space-tab-4:checked ~ .dabuli-space-tab-panels .dabuli-space-tab-panel[data-panel="4"],
#space-tab-5:checked ~ .dabuli-space-tab-panels .dabuli-space-tab-panel[data-panel="5"] {
	display: flex;
}

#space-tab-1:focus-visible ~ .dabuli-space-tab-list label[for="space-tab-1"],
#space-tab-2:focus-visible ~ .dabuli-space-tab-list label[for="space-tab-2"],
#space-tab-3:focus-visible ~ .dabuli-space-tab-list label[for="space-tab-3"],
#space-tab-4:focus-visible ~ .dabuli-space-tab-list label[for="space-tab-4"],
#space-tab-5:focus-visible ~ .dabuli-space-tab-list label[for="space-tab-5"] {
	outline: 2px solid var(--wp--preset--color--terracotta-deep);
	outline-offset: 3px;
	border-radius: 2px;
}

/* Reusable big-number stats row (Project Stats pattern): a core columns
   block of N stat columns, each a big number over a small uppercase label.
   On narrow screens, switch from core's default full stack (one column
   per row) to a 2-up grid so a 4-stat row reads as a compact 2x2 block
   instead of four stacked rows. */
@media (max-width: 599px) {
	.dabuli-stats-row.wp-block-columns {
		display: grid !important;
		grid-template-columns: repeat(2, 1fr) !important;
		column-gap: var(--wp--preset--spacing--30) !important;
		row-gap: var(--wp--preset--spacing--40) !important;
	}

	.dabuli-stats-row.wp-block-columns > .wp-block-column {
		flex-basis: auto !important;
		width: auto !important;
	}
}

/* Generic 3-column card grid — same .dabuli-value-card chrome, for any
   section with exactly 3 cards (e.g. "What We Do" on the Technology for
   All page) without needing a new page-specific grid class each time. */
.dabuli-card-grid-3.wp-block-group {
	display: grid !important;
	grid-template-columns: repeat(3, 1fr) !important;
}

@media (max-width: 909px) {
	.dabuli-card-grid-3.wp-block-group {
		grid-template-columns: 1fr !important;
	}
}

/* Generic 2-column card grid — same idea, for sections with an even number
   of cards (e.g. the Language Documentation page's 4 "Key Initiatives" and
   2 "Works in Progress" cards) where 3 columns would leave an awkward gap. */
.dabuli-card-grid-2.wp-block-group {
	display: grid !important;
	grid-template-columns: repeat(2, 1fr) !important;
}

@media (max-width: 599px) {
	.dabuli-card-grid-2.wp-block-group {
		grid-template-columns: 1fr !important;
	}
}

/* Muted icon variant — for a card describing something not live yet (e.g.
   "Works in Progress" items), so it reads as deliberately less finished
   than the colorful icons used for shipped initiatives, without needing a
   separate card component. */
.dabuli-value-icon-muted {
	background-color: var(--wp--preset--color--warm-sand);
	color: var(--wp--preset--color--ink-muted);
}

/* Partner/institution logo marquee (Language Documentation page) — a
   single row of logos + names drifting right-to-left on a continuous
   loop. The track's logo set is duplicated once in the markup so the
   -50% translateX wraps seamlessly with no visible jump. Pauses on
   hover so a name stays readable while the cursor is over it. */
.dabuli-partner-marquee {
	overflow: hidden;
	width: 100%;
	margin-top: var(--wp--preset--spacing--40);
	-webkit-mask-image: linear-gradient(90deg, transparent, black 6%, black 94%, transparent);
	mask-image: linear-gradient(90deg, transparent, black 6%, black 94%, transparent);
}

.dabuli-partner-marquee-track {
	display: flex;
	align-items: center;
	width: max-content;
	gap: var(--wp--preset--spacing--60);
	animation: dabuli-partner-scroll 32s linear infinite;
}

.dabuli-partner-marquee:hover .dabuli-partner-marquee-track {
	animation-play-state: paused;
}

.dabuli-partner-logo-card {
	display: flex;
	flex-direction: column;
	align-items: center;
	justify-content: center;
	gap: 0.75rem;
	flex: 0 0 auto;
	width: 140px;
}

.dabuli-partner-logo-card img {
	max-width: 100%;
	max-height: 86px;
	object-fit: contain;
}

.dabuli-partner-logo-name {
	font-weight: 600;
	font-size: var(--wp--preset--font-size--small);
	text-align: center;
	white-space: nowrap;
}

@keyframes dabuli-partner-scroll {
	from {
		transform: translateX(0);
	}
	to {
		transform: translateX(-50%);
	}
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-partner-marquee-track {
		animation: none;
	}
}

/* App store badge buttons (Language Documentation page) — dark pill
   buttons with a brand icon + short label, modeled on the download
   badges at vividtemplate.framer.website rather than the site's
   default (terracotta) button block. */
.dabuli-store-buttons {
	display: flex;
	flex-wrap: wrap;
	gap: var(--wp--preset--spacing--20);
}

.dabuli-store-button {
	display: inline-flex;
	align-items: center;
	gap: 0.6rem;
	padding: 0.85rem 1.4rem;
	border-radius: 9999px;
	background-color: var(--wp--preset--color--deep-charcoal);
	color: var(--wp--preset--color--pure-white);
	font-weight: 600;
	font-size: var(--wp--preset--font-size--small);
	text-decoration: none;
	transition: transform 0.2s ease, opacity 0.2s ease;
}

.dabuli-store-button:hover {
	transform: translateY(-2px);
	opacity: 0.88;
	color: var(--wp--preset--color--pure-white);
}

.dabuli-store-button svg {
	width: 20px;
	height: 20px;
	flex-shrink: 0;
}

/* Load-in: the same staggered fade-up as the blog/Related Stories cards
   (see scroll-reveal.js, which observes .dabuli-value-card as its own
   group) — one box at a time rather than the whole row appearing at once,
   matching charis.framer.website's own values section. One combined
   "transition" list covers the reveal (opacity/transform) and the hover
   lift (transform/box-shadow) together, since a second rule re-declaring
   "transition" on the same selector would silently replace this one
   instead of adding to it. */
.dabuli-value-card {
	opacity: 0;
	transform: translateY(28px);
	transition: opacity 0.5s ease, transform 0.6s cubic-bezier(0.22, 0.61, 0.36, 1), box-shadow 0.25s ease;
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 140ms);
}

.dabuli-value-card.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

.dabuli-value-card:hover {
	box-shadow: var(--wp--preset--shadow--lift, 0 28px 48px -20px rgba(24, 24, 27, 0.18));
	transform: translateY(-3px);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-value-card {
		opacity: 1;
		transform: none;
		transition: none;
	}

	.dabuli-value-card:hover {
		transform: none;
	}
}

.dabuli-value-icon {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 3.25rem;
	height: 3.25rem;
	border-radius: 14px;
	margin-bottom: 0.4rem;
}

.dabuli-value-icon svg {
	width: 26px;
	height: 26px;
}

/* One accent per card, drawn from the logo's own teal/gold/pink triangles
   (sampled from the actual logo file) plus the site's established cyan —
   a deliberately colorful moment on an otherwise mostly-monochrome site,
   scoped to this one section rather than spread everywhere. */
.dabuli-value-icon-teal {
	background-color: rgba(14, 148, 136, 0.12);
	color: #0e9488;
}

.dabuli-value-icon-cyan {
	background-color: rgba(0, 169, 209, 0.12);
	color: #00a9d1;
}

.dabuli-value-icon-gold {
	background-color: rgba(194, 152, 11, 0.14);
	color: #c2980b;
}

.dabuli-value-icon-pink {
	background-color: rgba(209, 70, 143, 0.12);
	color: #d1468f;
}

/* "Follow us" (Connect page) — a grid of labeled social cards instead of a
   plain bulleted link list, which left a lot of empty whitespace since
   short words like "Facebook" don't fill a wide content column. Reuses
   the Core Values card chrome (.dabuli-value-card) and icon chip
   (.dabuli-value-icon) for a consistent look, with its own grid/link
   classes so this section can be tuned independently. */
.dabuli-social-grid.wp-block-group {
	display: grid !important;
	grid-template-columns: repeat(4, 1fr) !important;
	gap: var(--wp--preset--spacing--20) !important;
}

@media (max-width: 909px) {
	.dabuli-social-grid.wp-block-group {
		grid-template-columns: repeat(2, 1fr) !important;
	}
}

@media (max-width: 480px) {
	.dabuli-social-grid.wp-block-group {
		grid-template-columns: 1fr !important;
	}
}

.dabuli-social-card {
	transition: box-shadow 0.25s ease, transform 0.25s ease;
}

.dabuli-social-card:hover {
	box-shadow: var(--wp--preset--shadow--lift, 0 28px 48px -20px rgba(24, 24, 27, 0.18));
	transform: translateY(-3px);
}

.dabuli-social-card-link {
	display: flex;
	align-items: center;
	gap: 0.75rem;
	text-decoration: none;
	color: var(--wp--preset--color--deep-charcoal);
}

.dabuli-social-card .dabuli-value-icon {
	margin-bottom: 0;
	flex-shrink: 0;
}

.dabuli-social-card-label {
	font-weight: 600;
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-social-card {
		transition: none;
	}

	.dabuli-social-card:hover {
		transform: none;
	}
}

/* "Our Story" section (About page), modeled on the "A global charity
   organization" section of charis.framer.website/home-v3 — a solid color
   panel bleeding from the actual page edge, with the photo floating partly
   in front of it, text on the other side. The panel is a ::before on the
   alignfull section itself: since that section already stretches to the
   real viewport edge, left:0 on an absolutely-positioned child reaches the
   true page edge for free, no viewport-width math needed. */
.dabuli-story-section {
	position: relative;
	overflow: hidden;
}

.dabuli-story-section::before {
	content: "";
	position: absolute;
	top: 10%;
	bottom: 38%;
	left: 0;
	width: 28%;
	background-color: var(--wp--preset--color--teal-tint);
	border-radius: 0 28px 28px 0;
	z-index: 0;
}

.dabuli-story-columns {
	position: relative;
	z-index: 1;
	/* core's own columns gap resolves from the root block-gap, which this
	   theme intentionally keeps at 0 (see the single-post white-gap fix
	   elsewhere in this file) — fine for stacked sections, but it leaves
	   the photo and text with no breathing room between them here.
	   WordPress prints its own per-instance "wp-container-core-columns-
	   is-layout-*" gap rule after this stylesheet, so plain specificity
	   isn't enough to win; !important is. */
	column-gap: var(--wp--preset--spacing--60) !important;
}

/* The source photo is a near-square crop; the reference layout uses a
   tall portrait column. aspect-ratio + object-fit crops it to that
   proportion in the browser rather than needing a separately-cropped
   image file. */
.dabuli-story-photo {
	aspect-ratio: 3 / 4;
	overflow: hidden;
	border-radius: 16px;
}

.dabuli-story-photo img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	/* Centered by default — this class is reused across pages (About's
	   "Our Story", the Team page's founder spotlight, ...), each with its
	   own photo, so a crop bias tuned for one specific image doesn't
	   belong here. Where a photo's subject sits off-center (as About's
	   does — the teaching figure stands near the original frame's right
	   edge), set object-position as an inline style on that one wp:image
	   block instead of changing this shared rule. */
	object-position: center;
	border-radius: 16px;
	box-shadow: 0 28px 48px -20px rgba(24, 24, 27, 0.28);
}

@media (max-width: 781px) {
	/* The offset panel is sized for the two-column layout — once columns
	   stack (core's own behavior below this width), there's no "beside the
	   image" position left for it to bleed toward, so it's dropped rather
	   than shown as a mis-sized rectangle behind a now full-width photo. */
	.dabuli-story-section::before {
		display: none;
	}

	.dabuli-story-media-col {
		margin-bottom: var(--wp--preset--spacing--40);
	}
}

/* "Our Team" page — board member rows: one person per full-width row
   (photo + bio side by side, alternating which side the photo sits on)
   instead of a 3-up card grid — with full ~200-word bios, a narrow grid
   column read as a long, cramped strip. A full-width row gives the bio
   a wide column to breathe in, and a hairline divider between entries
   (instead of a boxed card) keeps the page feeling open rather than
   crowded. */
.dabuli-team-row {
	column-gap: var(--wp--preset--spacing--60) !important;
	padding-top: var(--wp--preset--spacing--50);
	padding-bottom: var(--wp--preset--spacing--50);
	opacity: 0;
	transform: translateY(28px);
	transition: opacity 0.5s ease, transform 0.6s cubic-bezier(0.22, 0.61, 0.36, 1);
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 140ms);
}

.dabuli-team-row.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

.dabuli-team-rows > .wp-block-columns:not(:first-child) {
	border-top: 1px solid var(--wp--preset--color--sand-deep);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-team-row {
		opacity: 1;
		transform: none;
		transition: none;
	}
}

.dabuli-team-row-photo {
	overflow: hidden;
	border-radius: 16px;
}

.dabuli-team-row-photo img {
	width: 100%;
	aspect-ratio: 1 / 1;
	object-fit: cover;
	display: block;
	border-radius: 16px;
	box-shadow: 0 28px 48px -20px rgba(24, 24, 27, 0.28);
	transition: transform 0.5s cubic-bezier(0.22, 0.61, 0.36, 1);
}

.dabuli-team-row-photo:hover img,
.dabuli-team-row-photo:focus-within img {
	transform: scale(1.08);
}

/* Founder/ED photo on this page only — same hover-zoom treatment as the
   board photos above, matched via body.page-id-12839 since .dabuli-story-photo
   is a shared component (About page's "Our Story" photo uses it too, and
   should keep its own plain, static treatment). Zooming the img rather than
   the figure keeps the frame's box-shadow/radius fixed in place. */
body.page-id-12839 .dabuli-story-photo img {
	transition: transform 0.5s cubic-bezier(0.22, 0.61, 0.36, 1);
}

body.page-id-12839 .dabuli-story-photo:hover img,
body.page-id-12839 .dabuli-story-photo:focus-within img {
	transform: scale(1.08);
}

@media (max-width: 781px) {
	.dabuli-team-row {
		padding-top: var(--wp--preset--spacing--40);
		padding-bottom: var(--wp--preset--spacing--40);
	}

	.dabuli-team-row-photo {
		order: 1;
		margin-bottom: var(--wp--preset--spacing--30);
	}

	.dabuli-team-row-body {
		order: 2;
	}
}

/* "Get Involved" CTA — the two buttons sit in a flex row with no gap set,
   so they'd otherwise touch (this theme's root blockGap is 0; see the
   "Our Story" column-gap fix above for the same root cause). */
.dabuli-get-involved-section .wp-block-buttons {
	gap: var(--wp--preset--spacing--20);
}

/* Static photo grid. Author a normal core/gallery block with the
   "dabuli-photo-grid" class, styled to match the blog-card hover-zoom
   treatment so it reads as part of the page rather than a distinct
   full-bleed/animated section.

   Core's own column-width CSS for the Gallery block depends on a
   "layout" attribute the real block editor writes automatically — since
   this content was authored directly (not through the editor), that
   attribute was never set, core's flex-wrap never applies, and every
   photo was rendering at full container width stacked in one column
   (the reported "big blank space" was actually several giant 1320px
   photos stacked vertically, not literal empty space). Same root cause
   as the earlier blockGap issues this session; fixed the same proven
   way — bypass core's flex sizing with an explicit grid. */
.dabuli-photo-grid.wp-block-gallery {
	display: grid !important;
	grid-template-columns: repeat(4, 1fr) !important;
	gap: var(--wp--preset--spacing--20) !important;
	margin-top: var(--wp--preset--spacing--50);
	margin-bottom: var(--wp--preset--spacing--50);
}

@media (max-width: 909px) {
	.dabuli-photo-grid.wp-block-gallery {
		grid-template-columns: repeat(2, 1fr) !important;
	}
}

@media (max-width: 480px) {
	.dabuli-photo-grid.wp-block-gallery {
		grid-template-columns: 1fr !important;
	}
}

/* Homepage Dabuli Chhen teaser: only 3 photos, sitting in a half-width
   column beside text — the site-wide 4-column grid above would leave an
   empty track and cramped squares at that width. A wide photo on top plus
   two square ones below reads better in the smaller space. */
.dabuli-chhen-teaser-grid.wp-block-gallery {
	grid-template-columns: repeat(2, 1fr) !important;
	gap: var(--wp--preset--spacing--20) !important;
}

.dabuli-chhen-teaser-grid .wp-block-image:first-child {
	grid-column: 1 / -1;
}

.dabuli-chhen-teaser-grid .wp-block-image:first-child img {
	aspect-ratio: 16 / 10;
}

.dabuli-photo-grid .wp-block-image {
	width: auto !important;
	margin: 0;
	overflow: hidden;
	border-radius: 12px;
}

.dabuli-photo-grid .wp-block-image img {
	display: block;
	width: 100%;
	aspect-ratio: 1 / 1;
	object-fit: cover;
	transition: transform 0.5s cubic-bezier(0.22, 0.61, 0.36, 1);
}

.dabuli-photo-grid .wp-block-image:hover img,
.dabuli-photo-grid .wp-block-image:focus-within img {
	transform: scale(1.06);
}

/* Nepal Festival page — year-by-year event timeline. One full-width row per
   year (year number + date/venue + description + optional links), divided
   by a hairline rule, same convention as .dabuli-team-row on the Our Team
   page rather than a boxed-card or dotted-line widget, so it reads as part
   of the same site rather than a one-off component. */
.dabuli-timeline-rows > .wp-block-columns:not(:first-child) {
	border-top: 1px solid var(--wp--preset--color--sand-deep);
}

.dabuli-timeline-row {
	column-gap: var(--wp--preset--spacing--40) !important;
	padding-top: var(--wp--preset--spacing--40);
	padding-bottom: var(--wp--preset--spacing--40);
	opacity: 0;
	transform: translateY(24px);
	transition: opacity 0.5s ease, transform 0.6s cubic-bezier(0.22, 0.61, 0.36, 1);
	transition-delay: calc(var(--dabuli-reveal-index, 0) * 120ms);
}

.dabuli-timeline-rows > .wp-block-columns:first-child {
	padding-top: var(--wp--preset--spacing--30);
}

.dabuli-timeline-row.is-revealed {
	opacity: 1;
	transform: translateY(0);
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-timeline-row {
		opacity: 1;
		transform: none;
		transition: none;
	}
}

.dabuli-timeline-year {
	font-size: var(--wp--preset--font-size--xx-large);
	font-weight: 700;
	line-height: 1;
	margin: 0;
}

.dabuli-timeline-meta {
	font-weight: 600;
	margin: 0 0 0.6rem;
}

.dabuli-timeline-links.wp-block-buttons {
	margin-top: var(--wp--preset--spacing--20) !important;
	gap: var(--wp--preset--spacing--20) !important;
}

.dabuli-timeline-links .wp-block-button__link {
	font-size: var(--wp--preset--font-size--small);
}

@media (max-width: 781px) {
	.dabuli-timeline-year {
		font-size: var(--wp--preset--font-size--large);
	}
}

/* Small photo per timeline row, stacked above the year number — most rows
   have a matching event photo; rows that don't (e.g. 2017) simply omit it
   rather than forcing an unrelated image in. */
.dabuli-timeline-photo {
	width: 100%;
	max-width: 120px;
	aspect-ratio: 1 / 1;
	overflow: hidden;
	border-radius: 12px;
	margin-bottom: 0.85rem;
}

.dabuli-timeline-photo img {
	display: block;
	width: 100%;
	height: 100%;
	object-fit: cover;
}

/* Standalone in-content photo break — a single wide, rounded, shadowed
   photo dropped between text sections (e.g. after the intro, before the
   card grid) on an otherwise text-heavy project page. Deliberately plain
   (no caption chrome, no band) so it reads as part of the page flow, the
   same reasoning that moved the photo gallery away from a colored band
   earlier. */
.dabuli-content-photo {
	margin-top: var(--wp--preset--spacing--50) !important;
	margin-bottom: var(--wp--preset--spacing--50) !important;
}

.dabuli-content-photo img {
	border-radius: 16px;
	box-shadow: 0 28px 48px -20px rgba(24, 24, 27, 0.18);
	width: 100%;
	height: auto;
	object-fit: cover;
	max-height: 560px;
}

/* Homepage hero: a rotating full-bleed photo background filling the banner,
   a dark overlay for text legibility, and the headline/subhead/CTAs
   centered on top. The rotator and overlay are plain markup (not WP
   blocks) since there is no block for "crossfading background photos
   behind overlaid text"; the heading/paragraph/buttons above them stay
   normal editable blocks. */
.dabuli-hero-collage {
	position: relative;
	min-height: 88vh;
	display: flex;
	align-items: center;
	justify-content: center;
	overflow: hidden;
}

/* Rotating hero background: all slides stacked full-bleed on top of each
   other (see assets/js/hero-rotator.js, which also drives the arrows and
   dots below). Only .is-active is visible at a given time; the incoming
   slide glows in (a brief overexposed flash settling to normal brightness)
   while the outgoing one plainly fades out underneath it. */
.dabuli-hero-rotator {
	position: absolute;
	inset: 0;
	z-index: 0;
}

.dabuli-hero-rotator__slide {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
	display: block;
	opacity: 0;
}

.dabuli-hero-rotator__slide.is-active {
	animation: dabuli-hero-glow-in 1.6s ease-out forwards;
}

.dabuli-hero-rotator__slide.is-leaving {
	animation: dabuli-hero-fade-out 0.9s ease-in forwards;
}

@keyframes dabuli-hero-glow-in {
	0% {
		opacity: 0;
		filter: brightness(0.15);
	}
	60% {
		opacity: 1;
		filter: brightness(0.6);
	}
	100% {
		opacity: 1;
		filter: brightness(1);
	}
}

@keyframes dabuli-hero-fade-out {
	0% {
		opacity: 1;
	}
	100% {
		opacity: 0;
	}
}

@media (prefers-reduced-motion: reduce) {
	.dabuli-hero-rotator__slide.is-active,
	.dabuli-hero-rotator__slide.is-leaving {
		animation: none;
	}
	.dabuli-hero-rotator__slide.is-active {
		opacity: 1;
	}
	.dabuli-hero-rotator__slide.is-leaving {
		opacity: 0;
	}
}

/* Prev/next arrows and position dots, both added by hero-rotator.js. */
.dabuli-hero-nav {
	position: absolute;
	top: 50%;
	z-index: 3;
	transform: translateY(-50%);
	width: 44px;
	height: 44px;
	border: none;
	border-radius: 999px;
	background: rgba(255, 255, 255, 0.18);
	color: var(--wp--preset--color--pure-white);
	font-size: 1.75rem;
	line-height: 1;
	cursor: pointer;
	display: flex;
	align-items: center;
	justify-content: center;
	transition: background-color 0.25s ease;
}

.dabuli-hero-nav:hover,
.dabuli-hero-nav:focus-visible {
	background: rgba(255, 255, 255, 0.32);
}

.dabuli-hero-nav--prev {
	left: var(--wp--preset--spacing--30);
}

.dabuli-hero-nav--next {
	right: var(--wp--preset--spacing--30);
}

.dabuli-hero-dots {
	position: absolute;
	left: 50%;
	bottom: var(--wp--preset--spacing--30);
	z-index: 3;
	transform: translateX(-50%);
	display: flex;
	gap: 0.6rem;
}

.dabuli-hero-dot {
	width: 9px;
	height: 9px;
	padding: 0;
	border: none;
	border-radius: 999px;
	background: rgba(255, 255, 255, 0.4);
	cursor: pointer;
	transition: background-color 0.25s ease, transform 0.25s ease;
}

.dabuli-hero-dot.is-active {
	background: var(--wp--preset--color--pure-white);
	transform: scale(1.3);
}

@media (max-width: 600px) {
	.dabuli-hero-nav {
		width: 36px;
		height: 36px;
		font-size: 1.4rem;
	}

	.dabuli-hero-nav--prev {
		left: 0.5rem;
	}

	.dabuli-hero-nav--next {
		right: 0.5rem;
	}
}

.dabuli-hero-collage__overlay {
	position: absolute;
	inset: 0;
	z-index: 1;
	background: linear-gradient(
		180deg,
		rgba(24, 24, 27, 0.45) 0%,
		rgba(24, 24, 27, 0.6) 55%,
		rgba(24, 24, 27, 0.72) 100%
	);
}

.dabuli-hero-collage__content {
	position: relative;
	z-index: 2;
	padding: var(--wp--preset--spacing--60) var(--wp--preset--spacing--40);
}

/* Headline sized to stay on one line down to small phones, rather than the
   theme's "display" preset (5rem) which forced three stacked lines and
   buried the photo collage behind it. */
.dabuli-hero-collage__title {
	font-size: clamp(1.375rem, 1rem + 2.6vw, 2.75rem);
	white-space: nowrap;
}

/* The theme's "large" preset (1.5rem) read as cramped against the narrow
   line length on a phone screen, with text nearly touching both edges —
   this scales down with viewport width instead of staying fixed. */
.dabuli-hero-collage__subhead {
	font-size: clamp(1rem, 0.9rem + 0.5vw, 1.25rem);
}

@media (max-width: 781px) {
	.dabuli-hero-collage {
		min-height: 78vh;
	}
}

@media (max-width: 480px) {
	/* More breathing room on phones: the spacing--40 token alone left only
	   ~26px of side padding, which read as edge-to-edge once the subhead
	   wrapped to several lines. */
	.dabuli-hero-collage__content {
		padding-left: 1.75rem;
		padding-right: 1.75rem;
	}

	/* Below this width the forced one-line title still read as cramped
	   against the viewport edges even with the extra padding above — drop
	   the "stay on one line" rule, let it wrap onto short, centered lines
	   with real margin on either side instead of stretching edge to edge. */
	.dabuli-hero-collage__title {
		font-size: clamp(1.5rem, 1.1rem + 4vw, 2rem);
		white-space: normal;
		max-width: 11ch;
		margin-inline: auto;
		text-wrap: balance;
	}
}

/* Events page: Google Calendar embed, framed to match the site's card
   language (rounded corners + lift shadow) instead of Google's bare iframe
   edge. Fixed height rather than an aspect-ratio box — the calendar's own
   list/grid toggle and popups need a tall, stable viewport, not one that
   reflows with content. */
.dabuli-calendar-embed {
	max-width: var(--wp--style--global--content-size, 1320px);
	margin-inline: auto;
	border-radius: 16px;
	overflow: hidden;
	box-shadow: var(--wp--preset--shadow--lift, 0 28px 48px -20px rgba(24, 24, 27, 0.32));
}

.dabuli-calendar-embed iframe {
	display: block;
	width: 100%;
	height: 650px;
	border: 0;
}

@media (max-width: 480px) {
	.dabuli-calendar-embed iframe {
		height: 560px;
	}
}

