/* Community events - the submission form (submit-event-controller.js) and
   the admin edit modal (admin-events-controller.js). The public browse page
   (/events/, events-controller.js) deliberately reuses the Directory's own
   classes (.directory-hero/.directory-layout/.directory-sidebar/.directory-
   controls/.near-me-btn/.taxonomy-map/.view-toggle, all in nova.css/
   directory-cards.css) rather than inventing its own, so it looks and
   behaves like the rest of the site's one established "browse a list of
   things" pattern instead of a one-off design. */

.event-form{display:grid;grid-template-columns:1fr 1fr;gap:18px 20px;max-width:920px;margin:0 auto;padding:clamp(24px,4vw,40px);background:#fff;border:1px solid var(--line,#e2e6ec);border-radius:14px}
.event-form .form-field--full{grid-column:1/-1}
/* Anything the form's script hides with the [hidden] attribute (the address
   fields for a virtual event, the time fields for an all-day one, the
   "set from your address" note, the Featured-only required stars) must
   actually disappear. A class rule that sets display (add-business.css's
   .form-field{display:grid}, and this file's own small/label rules) beats the
   browser's built-in [hidden]{display:none}, so without this the fields
   stayed on screen with only their "required" flag switched off. !important
   so it also holds regardless of stylesheet order after a soft navigation. */
form.event-form [hidden]{display:none!important}
.event-form-disclaimer{max-width:920px;margin:16px auto 0;font-size:12px;line-height:1.6;color:var(--muted)}
/* The base field rules below are written as form.event-form (class + two
   elements) on purpose: add-business.css's ".form-field label/select/
   textarea/input" rules have the same single-class-plus-element
   specificity as ".event-form label" etc., so which won depended on
   stylesheet LOAD ORDER - fine on a direct load of /submit-event/, but a
   soft-nav click from another page (soft-nav-router.js appends missing
   stylesheets at the END of <head>) flipped it: bolder labels, taller
   dropdowns, darker borders, until a refresh. The extra element makes these
   win in either order. */
form.event-form label{display:block;font-weight:700;font-size:13px;margin-bottom:6px}
form.event-form input[type="text"],form.event-form input[type="date"],form.event-form input[type="time"],form.event-form input[type="email"],form.event-form input[type="url"],form.event-form input[type="tel"],form.event-form select,form.event-form textarea{width:100%;padding:10px 12px;border:1px solid var(--line,#d7dce3);border-radius:8px;font:inherit;background:#fff}
form.event-form select[multiple]{height:180px}
form.event-form small{display:block;color:#6b7280;font-size:12px;margin-top:4px}
.event-form .event-form__row{display:grid;grid-template-columns:1fr 1fr;gap:12px}
.event-form .event-form__row--3{grid-template-columns:1fr 1fr 1fr}
.event-form .event-form__row .form-field{margin:0}
.event-form__section-title{grid-column:1/-1;margin:8px 0 -6px;font-size:13px;font-weight:800;text-transform:uppercase;letter-spacing:.04em;color:#6b7280;border-top:1px solid var(--line,#e2e6ec);padding-top:18px}
.event-form__section-title:first-of-type{border-top:none;padding-top:0;margin-top:0}
/* .event-form .event-form__checkbox (two classes), not just
   .event-form__checkbox - this file's own generic ".event-form
   label{display:block}" rule above (one class + one element = higher
   specificity than a single class alone) was winning over this rule's
   own display:flex, collapsing the checkbox and its own label text back
   to plain inline flow instead of the intended flex row. */
.event-form .event-form__checkbox{display:flex;align-items:center;gap:8px;font-weight:600;font-size:14px}
/* Two classes + an element (not just .event-form__checkbox input): add-business.css's
   ".form-field input{width:100%}" has the SAME specificity as the old
   single-class version, so whichever stylesheet loaded last won. A direct
   load of /submit-event/ happens to load events.css last (fine), but a
   soft-nav click from another page (soft-nav-router.js appends the new
   page's missing stylesheets at the END of <head>) loaded add-business.css
   after it - the checkbox became a ~570px-wide box with its glyph centered
   in it and the label text pushed far to the right, until a refresh. */
.event-form .event-form__checkbox input{width:auto;flex:0 0 auto}
.event-form__image-preview{margin-top:10px;max-width:220px;border-radius:10px;display:none}
.event-form__image-preview.is-visible{display:block}
@media(max-width:620px){.event-form,.event-form .event-form__row{grid-template-columns:1fr}.event-form .form-field{grid-column:1}}

/* Stronger than the sitewide .form-status--error (add-business.css's own
   muted maroon-on-pink) - a submission failure here needs to actually read
   as "something is wrong, fix it" at a glance, not blend into the rest of
   the form. */
.event-form .form-status--error{background:#fdecea;color:#b3261e;border:1px solid #f3b9b4;border-left:4px solid #b3261e;font-weight:700}
/* The specific field a failed submission is about (submit-event-controller.js's
   FIELD_BY_ERROR_CODE) - the red banner says what's wrong, this points at
   exactly where to fix it. */
.event-form__field--error{border-color:#b3261e!important;background:#fef6f5}

/* .directory-hero sets color:#fff for everything inside it, but .lead's own
   base rule (nova.css) is a dark color meant for a white section - every
   other dark hero that uses .lead has its own override (.hero .lead,
   .city-hero .lead); .directory-hero never needed one until this page
   reused it with a lead paragraph of its own. */
.directory-hero .lead{color:#cbd8ea}
/* .directory-search is a 3-column grid built for the WHAT/WHERE search
   inputs + button (nova.css) - dropping a single button into it leaves two
   empty white grid cells beside it. This page's hero only ever has the one
   CTA button, no search fields, so it gets its own plain wrapper instead. */
.events-hero-cta{margin-top:28px}
/* .btn--primary has no site-wide hover state at all (nova.css) - only a
   couple of scoped ones exist elsewhere (the add-business form, the portal
   shell). Same lift-and-shadow treatment as those, scoped to this button. */
.events-hero-cta .btn--primary{transition:transform .16s ease,box-shadow .16s ease}
.events-hero-cta .btn--primary:hover{transform:translateY(-1px);box-shadow:0 8px 22px rgba(0,84,204,.36)}
.events-hero-cta .btn--primary:active{transform:translateY(0);box-shadow:0 3px 10px rgba(0,84,204,.28)}
/* .section-head (nova.css) lays its own <p> out beside the eyebrow/heading
   (flex row, space-between) - the city page's own "Upcoming Events in
   <City>" section wants that paragraph below the heading instead, per the
   owner's own call. Scoped to this one modifier so every other section
   using the plain .section-head keeps its existing side-by-side layout. */
.section-head--stack{flex-direction:column;align-items:flex-start;gap:6px}
.section-head--stack p{max-width:640px}
/* Event detail page hero - .eyebrow/.blog-hero are shared with blog posts
   (blog.css), so these are scoped to .event-detail-hero specifically
   rather than changed site-wide. A little bigger per the owner's own ask,
   and the city name is a real link now (/local/<slug>/) with its own
   hover state - inherits the eyebrow's light blue by default, same orange
   accent every other link on a dark section already hovers to
   (.section--ink .city-module-list a:hover). */
.event-detail-hero .eyebrow{font-size:13px}
.event-detail-hero .eyebrow a{color:inherit;text-decoration:underline;text-decoration-color:rgba(255,255,255,.35)}
.event-detail-hero .eyebrow a:hover,.event-detail-hero .eyebrow a:focus-visible{color:#ffb892;text-decoration-color:currentColor}
/* Saved/Share/Report row - reuses business-profile.css's own .profile-share/
   .profile-save-trigger/.profile-report-trigger as-is (self-contained white
   chips, so they already read fine over this hero's own dark gradient, same
   as over .profile-hero--themed's). Only the row's own top spacing needs a
   scoped rule here, since on a business profile this row sits beside the
   identity block in a flex row (.profile-hero__top) that already has its
   own gap, but here it's stacked directly under the two date/time lines
   instead. */
.event-detail-hero__actions{margin-top:20px}
/* The row also holds two text links (Report this listing / Request a change
   to this event); .profile-share itself never wraps, which is fine for the
   business profile's shorter row but pushed this one ~6px past a 390px
   screen. Let it wrap and keep the two links on a line of their own once it
   does, so neither is orphaned mid-row. */
.event-detail-hero__actions{flex-wrap:wrap;row-gap:10px}
.event-detail-hero__actions .event-change-link{margin-left:0}
@media (max-width:560px){.event-detail-hero__actions .profile-report-trigger{margin-left:0}.event-detail-hero__actions .profile-report-trigger[data-event-report-trigger]{flex-basis:auto}}

/* renderEventDetailPage reuses business-profile.css's .featured-detail-row
   for the venue/date-time/address/price/host rows, but not its sidebar
   wrapper (.featured-sidebar{display:grid;gap:14px}) that .featured-
   detail-row's own margin:13px 0 was designed to sit inside - here it's
   nested in .event-card__body (display:flex;gap:6px) instead, and the two
   stack (13px margin + 6px gap + 13px margin = ~32px between rows) instead
   of just one or the other applying. Zeroing the margin here leaves the
   6px flex gap as the only spacing source, same as the result card's own
   .event-card__detail-row rows just below. */
.event-card .featured-detail-row{margin:0}
/* A bit more breathing room than the compact result card's own 6px gap -
   this block's icons/text (.profile-icon at 21px, .featured-detail-row--name
   at 17px) are noticeably larger than the card's 14px rows, so the same
   tight gap reads as cramped here. Scoped to the detail page's own wrapper
   (event-card--detail) so the result card's gap is untouched. */
.event-card--detail .event-card__body{gap:10px}
/* Heading for the detail page's own facts card, now that removing the
   venue-name row left it with no name/title line of its own at the top -
   same bold-blue-17px treatment .featured-detail-row--name strong used for
   venue name (business-profile.css), just as a plain heading instead of an
   icon row, since there's no icon that fits "this is the event" the way a
   business/pin icon fits a venue or address. */
.event-card-detail__title{margin:0;font-size:17px;font-weight:800;color:#0054cc}

/* Bottom-of-page CTAs on an event's own detail page - "Browse all" plus a
   "Submit Your Event" nudge (same copy as the hub page's own hero CTA),
   per the owner's own ask for a submit link somewhere on this page. */
.event-detail-footer-ctas{display:flex;flex-wrap:wrap;gap:12px}

/* "Load more" control under the upcoming-events grid/list - reveals more of
   the already-filtered set (events-controller.js keeps the full match in
   memory), it doesn't re-fetch anything. Hidden entirely once every
   matching event is already showing. */
.events-load-more{display:flex;justify-content:center;margin-top:24px}
.events-load-more[hidden]{display:none}

/* Event result card - shaped like .business-card (directory-cards.css) on
   purpose (image on top, body below, meta row, a text-link action) so it
   reads as the same kind of object in the same kind of list, just for an
   event instead of a business. Used by the /events/ browse page's own
   list/grid views and the event's own detail page body. */
.event-card{display:flex;flex-direction:column;background:#fff;border:1px solid var(--line,#e2e6ec);border-radius:12px;overflow:hidden;height:100%;min-width:0}
.event-card__image{width:100%;aspect-ratio:16/10;object-fit:cover;background:#f1f3f6}
.event-card__body{padding:16px;display:flex;flex-direction:column;gap:6px;flex:1}
/* Category/city eyebrow - .eyebrow's own sitewide default (nova.css) is a
   small orange label; the owner's own call for this one card was blue and
   bigger, so it's scoped here rather than changed site-wide (every other
   .eyebrow, e.g. the business directory cards, keeps the orange default). */
.event-card .eyebrow{color:#0054cc;font-size:14px}
/* Each fact (date, time, venue, address, price) on its own icon row -
   replaced the old single-line .event-card__date/.event-card__meta text
   per the owner's own request, and bumped up a size from that original
   13px while at it. */
.event-card__detail-row{display:flex;align-items:center;gap:7px;font-size:14px;color:#444;margin:0}
.event-card__detail-row svg{flex:0 0 auto;color:#8a98aa}
.event-card__detail-row--date{font-weight:800;font-size:14px;letter-spacing:.02em;text-transform:uppercase;color:var(--orange,#cc4400)}
.event-card__detail-row--date svg{color:var(--orange,#cc4400)}
.event-card__title{font-size:17px;font-weight:800;margin:0}
.event-card__title a{color:inherit;text-decoration:none}
.event-card__title a:hover{text-decoration:underline}
.event-card__tags{display:flex;flex-wrap:wrap;gap:6px;margin-top:auto;padding-top:8px}
/* Plain, non-interactive label - not a link anywhere anymore (see
   renderEventTagPills's own comment), so no hover state. Bumped up from
   11px per the owner's own ask; background/color here are just the
   fallback for a tag whose tag-color-N hash class (nova.css, shared with
   the blog's own tags) hasn't loaded yet. */
.event-card__tag{font-size:13px;font-weight:700;background:#eef1f5;color:#44505c;border-radius:999px;padding:5px 11px}

/* Past Events - one compact line per event (date, title, category/city)
   instead of the full event-card treatment above, which was eating a lot
   of page height for a record nobody's actually about to attend. A grid of
   compact cards, not a single full-width row per event - a plain list at
   this section's full container width stretched each event into an
   oddly long, thin bar with a tiny thumbnail and mostly empty space. */
.past-events-list{list-style:none;margin:0;padding:0;display:grid;grid-template-columns:repeat(auto-fill,minmax(380px,1fr));gap:14px}
.past-event-row{display:flex;gap:14px;align-items:stretch;padding:14px;border:1px solid var(--line,#e2e6ec);border-radius:10px}
.past-event-row__thumb{flex:0 0 auto;align-self:stretch}
.past-event-row__image{display:block;width:120px;height:100%;min-height:120px;border-radius:8px;object-fit:cover;background:var(--paper,#f5f7fa)}
.past-event-row__image--placeholder{height:100%;min-height:120px;background:var(--paper,#f5f7fa) linear-gradient(135deg,transparent 45%,var(--line,#e2e6ec) 45%,var(--line,#e2e6ec) 55%,transparent 55%)}
.past-event-row__body{flex:1;min-width:0}
.past-event-row__head{display:flex;flex-wrap:wrap;gap:2px 10px;font-size:12px;font-weight:700}
.past-event-row__date{color:#c24000}
.past-event-row__meta{color:#0054cc}
.past-event-row__title{margin:2px 0;font-size:14px;line-height:1.3}
.past-event-row__title a{color:inherit;text-decoration:none}
.past-event-row__title a:hover{text-decoration:underline}
.past-event-row__desc{margin:0;font-size:13px;color:var(--muted,#5b6b80);line-height:1.4;overflow:hidden;display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical}

/* .directory-result-list (list view) lays business cards out as
   [media | body] side by side - this matches that exact shape so an event
   card in list view looks identical in structure to a business one. */
.directory-result-list .event-card{display:grid;grid-template-columns:380px 1fr}
.directory-result-list .event-card .event-card__image{height:258px;aspect-ratio:auto}
.directory-result-list.is-grid .event-card{display:flex;flex-direction:column}
.directory-result-list.is-grid .event-card .event-card__image{height:258px;aspect-ratio:auto}
@media(max-width:620px){.directory-result-list .event-card{display:flex;flex-direction:column}.directory-result-list .event-card .event-card__image{height:210px}}

/* Admin edit modal (admin-events-controller.js) - display:flex lives here,
   on the class, NOT as an inline style on the element - an inline style
   beats the browser's own [hidden]{display:none} rule. */
.event-edit-modal{position:fixed;inset:0;background:rgba(15,23,42,.55);display:flex;align-items:flex-start;justify-content:center;overflow-y:auto;padding:40px 16px;z-index:1000}
.event-edit-modal[hidden]{display:none}

/* Sidebar "Date" filter (events-controller.js) - a From/To range, each
   side a styled display sitting over a real native <input type="date">,
   not a custom-built calendar widget. The native input is stretched
   invisibly across the whole box (opacity:0, position:absolute, inset:0)
   so a click anywhere on it opens the browser's own date picker - no JS
   popover to build or maintain, and it works the same (keyboard, mobile
   wheel picker, etc.) as any other native date input on the site. The
   visible <span> is just a label the JS updates after a date is chosen;
   the calendar icon is purely decorative, sitting under that same
   invisible input. Stacked (not side-by-side) so a fully-formatted date
   like "SUNDAY, MAY 2, 2027" has room to sit on one line inside the
   sidebar's own ~250px column.
*/
.event-date-range{display:flex;flex-direction:column;gap:12px;margin-top:10px}
.event-date-range__field{display:flex;flex-direction:column}
.event-date-range__label{margin-bottom:5px;font:800 10px var(--mono);letter-spacing:.06em;text-transform:uppercase;color:var(--muted)}
.event-date-trigger{position:relative;display:flex;align-items:center;gap:8px;padding:12px 14px;border:1px solid var(--line);border-radius:8px;cursor:pointer;color:var(--ink-2);font:800 12px var(--mono);letter-spacing:.03em;text-transform:uppercase;transition:border-color .14s ease}
.event-date-trigger:hover,.event-date-trigger:focus-within{border-color:var(--blue)}
.event-date-trigger svg{flex:0 0 auto;color:var(--blue)}
.event-date-trigger span{flex:1;min-width:0}
.event-date-trigger input[type="date"]{position:absolute;inset:0;width:100%;height:100%;opacity:0;cursor:pointer;border:0;padding:0;margin:0}

/* ---------------------------------------------------------------------
   Featured events (src/backend/event-promotions.js) - a paid strip at the
   top of /northern-va-events/, deliberately its own band above the filters
   so it never mixes into (or reorders) the chronological list below.
   Markup: render.js renderEventsFeaturedStrip + events-controller.js's
   renderFeaturedStrip. The one gold accent (badge star, card border, box
   border) is the "paid placement" signal everywhere it appears.
   --------------------------------------------------------------------- */
.event-card{position:relative}
.event-card__badge,.event-featured-badge{display:inline-flex;align-items:center;gap:4px;padding:5px 11px;border-radius:999px;background:#0b1b33;color:#ffd66b;font:800 11px var(--mono);letter-spacing:.06em;text-transform:uppercase;white-space:nowrap}
/* "Featured" sits top-right so the date tab below owns the top-left corner. */
.event-card__badge{position:absolute;top:12px;right:12px;z-index:3;box-shadow:0 2px 8px rgba(11,27,51,.3)}
/* The date tab on an event card's photo (.event-card__date-badge) is styled by
   its own markup (render.js eventDateBadgeHtml / events-controller.js), not
   here, so it can't lose its look to a stale cached copy of this file. */
.event-card--featured{border-color:#e9b949}

.events-featured{background:linear-gradient(180deg,#f3f7ff 0,#fff 100%);border-bottom:1px solid var(--line,#e2e6ec);padding:36px 0 40px}
.events-featured__head{display:flex;align-items:flex-end;justify-content:space-between;gap:12px 20px;flex-wrap:wrap;margin-bottom:20px}
.events-featured__head h2{margin:2px 0 0;font-size:26px;font-weight:800;color:var(--ink,#0b1b33)}
.events-featured__cta{font-size:14px;font-weight:800;color:#0054cc;text-decoration:none}
.events-featured__cta:hover{text-decoration:underline}
.events-featured__grid{display:grid;grid-template-columns:repeat(3,minmax(0,1fr));gap:20px}
/* The rotation hides cards with the hidden attribute - !important because
   nothing else here should ever win against "this card is off the current
   page". */
.events-featured__item[hidden]{display:none!important}
.events-featured__item{min-width:0}
@media(max-width:979px){.events-featured__grid{grid-template-columns:repeat(2,minmax(0,1fr))}}
@media(max-width:620px){.events-featured{padding:28px 0 32px}.events-featured__grid{grid-template-columns:1fr}}

.events-featured__controls{display:flex;align-items:center;justify-content:center;gap:14px;margin-top:22px}
.events-featured__arrow{display:inline-flex;align-items:center;justify-content:center;width:38px;height:38px;border:1px solid var(--line,#e2e6ec);border-radius:50%;background:#fff;color:#0b1b33;font-size:22px;line-height:1;cursor:pointer;transition:border-color .15s,color .15s}
.events-featured__arrow:hover{border-color:#0054cc;color:#0054cc}
.events-featured__dots{display:flex;gap:8px;align-items:center}
.events-featured__dot{width:10px;height:10px;padding:0;border:0;border-radius:50%;background:#c3cfe3;cursor:pointer}
.events-featured__dot.is-active{background:#0054cc;transform:scale(1.25)}
.events-featured__pause{padding:6px 12px;border:1px solid var(--line,#e2e6ec);border-radius:999px;background:#fff;color:#44546b;font:800 12px var(--mono);letter-spacing:.04em;text-transform:uppercase;cursor:pointer}
.events-featured__pause:hover{border-color:#0054cc;color:#0054cc}
.events-featured__arrow:focus-visible,.events-featured__dot:focus-visible,.events-featured__pause:focus-visible,.events-featured__cta:focus-visible,.event-feature-box .btn:focus-visible{outline:2px solid #0054cc;outline-offset:2px}

/* Nothing featured yet: one slim pitch instead of an empty strip. */
.events-featured--empty{padding:22px 0;background:#f3f7ff}
.events-featured__pitch{display:flex;align-items:center;justify-content:space-between;gap:16px 24px;flex-wrap:wrap;padding:20px 24px;border:1px dashed #9db8e6;border-radius:12px;background:#fff}
.events-featured__pitch-title{margin:4px 0 2px;font-size:18px;font-weight:800;color:var(--ink,#0b1b33)}
.events-featured__pitch p{margin:0;font-size:14px;line-height:1.5;color:#44546b}

/* Event detail page: the "Feature your event" promo box (links to the submit
   form) and the Featured badge (render.js renderEventDetailPage). */
.event-featured-badge{margin:10px 0 0;display:inline-flex}
.event-feature-box{display:flex;flex-direction:column;gap:10px;padding:18px;border:1px solid #e9b949;border-radius:12px;background:#fffaf0}
.event-feature-box__eyebrow,.event-feature-info__eyebrow{font:800 11px var(--mono);letter-spacing:.06em;text-transform:uppercase;color:#9a6a00}
.event-feature-box p{margin:0;font-size:14px;line-height:1.5}
.event-feature-box .btn{width:100%;justify-content:center}

/* Submit page: the short "optional featuring" explainer above the form. */
.event-feature-info{display:flex;flex-direction:column;gap:6px;margin-bottom:24px;padding:16px 20px;border:1px solid #e9b949;border-radius:12px;background:#fffaf0;scroll-margin-top:90px}
.event-feature-info p{margin:0;font-size:14px;line-height:1.6;color:#33415a}

/* "← Back to Events" at the top of an event page's header - same look as
   the business listing pages' .profile-directory-back (a small, slightly
   dimmed link in the hero's own text color), kept as its own class here
   because that one's styling is injected by profile-directory-back-link.js,
   which only runs on business profiles. */
.event-detail-back{display:inline-flex;align-items:center;margin:0 0 18px;color:inherit;font-size:14px;font-weight:700;text-decoration:none;opacity:.86}
.event-detail-back::before{content:'←';margin-right:7px;font-size:16px}
.event-detail-back:hover,.event-detail-back:focus-visible{text-decoration:underline;opacity:1}

/* A field next to a taller neighbour (e.g. "Your email" with its note under
   it) was stretched to the neighbour's height, and its input absorbed the
   extra space - "Your name" rendered as a 71px-tall box beside a 47px email
   box. Keep each field's contents packed at the top of its cell. */
.event-form .form-field{align-content:start}

/* Bold button above the event Description box (submit form and admin edit form). */
.event-format-bar{display:flex;align-items:center;gap:10px;margin:0 0 6px}
.event-format-bar__btn{width:34px;height:34px;border:1px solid #cdd7e3;border-radius:8px;background:#fff;color:#0b1a2e;font:700 15px/1 Arial,sans-serif;cursor:pointer}
.event-format-bar__btn:hover{background:#eef3fb;border-color:#0054cc}
.event-format-bar__btn:focus-visible{outline:2px solid #0054cc;outline-offset:2px}
.event-format-bar__hint{font-size:12px;color:#5b6b80}

/* Event detail page photo: a frame as wide as the event details card and map below it (so the edges line up) and
   630px tall (an 8:9 box on phones). Every photo is shown WHOLE, never cropped, centered in the frame; the extra
   space around it is filled with a blurred, darkened copy of the same photo instead of a plain color. With 2 or 3
   photos only ONE is on screen at a time: the photos are stacked, the others are hidden, and the arrow on each
   side (or a swipe, the arrow keys, or the dots) fades to the next one, wrapping from the last back to the first.
   The behavior is in home-experience.js (data-event-gallery). */
.event-gallery{position:relative;width:100%;height:630px;margin:0 0 26px;border-radius:14px;overflow:hidden;background:#0b1a2e;box-shadow:0 10px 28px rgba(11,26,46,.16)}
.event-gallery:focus-visible{outline:3px solid rgba(0,84,204,.5);outline-offset:3px}
.event-gallery__slide{position:absolute;inset:0;opacity:0;visibility:hidden;transition:opacity .45s ease,visibility 0s linear .45s}
.event-gallery__slide.is-active{opacity:1;visibility:visible;transition-delay:0s}
.event-gallery__slide img{width:100%;height:100%;display:block}
.event-gallery__photo{position:relative;z-index:1;object-fit:contain}
.event-gallery__backdrop{position:absolute;inset:0;z-index:0;object-fit:cover;filter:blur(24px) brightness(.8);transform:scale(1.2)}
.event-gallery__arrow{position:absolute;z-index:2;top:50%;width:44px;height:44px;margin-top:-22px;padding:0;border-radius:50%;border:1.5px solid rgba(255,255,255,.9);background:rgba(7,19,33,.62);color:#fff;display:flex;align-items:center;justify-content:center;cursor:pointer;transition:background .15s ease}
.event-gallery__arrow--prev{left:12px}
.event-gallery__arrow--next{right:12px}
.event-gallery__arrow:hover,.event-gallery__arrow:focus-visible{background:#e8590c}
.event-gallery__dots{position:absolute;z-index:2;left:0;right:0;bottom:10px;display:flex;justify-content:center;gap:7px;pointer-events:none}
.event-gallery__dot{width:9px;height:9px;padding:0;border-radius:50%;border:0;background:rgba(255,255,255,.55);box-shadow:0 0 0 1px rgba(7,19,33,.35);cursor:pointer;pointer-events:auto}
.event-gallery__dot.is-active{background:#fff;transform:scale(1.25)}
@media(prefers-reduced-motion:reduce){.event-gallery__slide{transition:none}}
@media(max-width:700px){.event-gallery{height:auto;aspect-ratio:8/9}}
@media(max-width:560px){.event-gallery{border-radius:12px;margin-bottom:20px}.event-gallery__arrow{width:38px;height:38px;margin-top:-19px}.event-gallery__arrow--prev{left:8px}.event-gallery__arrow--next{right:8px}}

/* Community Events listing page: still three cards across, but a little wider. The filter sidebar is
   220px (was 250px) and the gaps are tighter, which gives each card about 16px more width on a laptop or desktop,
   so its photo shows a little more of the picture. Only this page (the layout that holds data-events-results);
   the business directory is untouched. Below 981px the page is a single column as before. */
@media(min-width:981px){.directory-layout:has([data-events-results]){grid-template-columns:220px minmax(0,1fr);gap:28px}}
.directory-result-list.is-grid[data-events-results]{gap:18px 12px}

/* "Add to Calendar" under the date and time on an event page (render.js
   renderEventDetailPage). A <details>, so it opens and closes with no script;
   event-detail-controller.js only adds close-on-outside-click and Escape. */
.event-calendar{position:relative;display:inline-block;margin:0 0 4px;z-index:20}
.event-calendar>summary{list-style:none}
.event-calendar>summary::-webkit-details-marker{display:none}
.event-calendar__button{display:inline-flex;align-items:center;gap:8px;min-height:44px;padding:0 18px;border-radius:999px;background:#fff;color:var(--ink);font:800 14px var(--sans);cursor:pointer;box-shadow:0 2px 10px rgba(0,0,0,.18);transition:background-color .16s ease,color .16s ease}
.event-calendar__button svg{width:18px;height:18px;flex:0 0 auto}
.event-calendar__button:hover,.event-calendar__button:focus-visible,.event-calendar[open]>.event-calendar__button{background:#eef5ff;color:#0054cc}
.event-calendar__menu{position:absolute;left:0;top:calc(100% + 8px);margin:0;padding:6px;list-style:none;min-width:min(340px,calc(100vw - 32px));max-width:calc(100vw - 32px);background:#fff;border:1px solid #dbe4f3;border-radius:12px;box-shadow:0 14px 34px rgba(10,25,45,.28)}
.event-calendar__menu a{display:flex;align-items:center;gap:12px;padding:11px 12px;border-radius:8px;color:var(--ink);font:600 14px var(--sans);text-decoration:none}
.event-calendar__menu a:hover,.event-calendar__menu a:focus-visible{background:#f1f6ff;color:#0054cc}
.event-calendar__menu svg{width:20px;height:20px;flex:0 0 auto;fill:currentColor}
.event-calendar__menu a[data-calendar-kind="web"]::after{content:"\2197";margin-left:auto;color:#8a98aa;font-size:13px}
.event-calendar__menu a:hover .event-calendar__note,.event-calendar__menu a:focus-visible .event-calendar__note{color:#4b6a9a!important}
