/**
 * The OTA member dashboard.
 *
 * Figma "OTA Dashboard", frame 377:23179. Two surfaces in one file, because
 * they are one screen:
 *
 *   1. THE CHROME  the sidebar navigation and the welcome bar, which the theme
 *      draws on every dashboard route. Scoped to
 *      `body.theme-agend--account-is-dashboard` so My CPD, Orders and the rest
 *      get the same rail as the landing page.
 *   2. THE LANDING PAGE  the cards, benefits, events and Loop band on page 50,
 *      reached through `ota-dash-*` classes stamped on that page's sections.
 *      Nothing here fires on a page that has not opted in by carrying one.
 *
 * WHY THIS FILE OVERRIDES THE THEME
 *
 * Everything in the chrome section is drawn by wordpress-theme-agend, which is
 * the shared Agend product and out of bounds for OTA work. Its rules are
 * answered from here at matching or greater weight rather than edited. The ones
 * that matter, all compiled into the theme's `member-dashboard-*.css`:
 *
 *   #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner
 *     .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a
 *   ...the same chain ... ul li > a > span.icon
 *   ...the same chain ... ul li.current-menu-item
 *   ...the same chain ... ul li.current-menu-item > a:after
 *
 * That is two ids and four classes, so every chrome rule below restates the
 * whole chain. Do not shorten them: the page still renders if the count drops,
 * it just renders at the theme's values, which is the failure mode that looks
 * like nothing happened.
 *
 * COLOUR
 *
 * Roles, never hexes, through the same `--ota-*` custom properties the rest of
 * the plugin uses, with the frame's own values as fallbacks so the screen is
 * never unstyled on a site whose colour themes have not been configured. The
 * frame is four variable modes: White for the chrome and the page, Navy for the
 * membership card, Teal for the CPD snapshot, Ash for the benefit and event
 * cards. Those are applied as `ota-theme--*` classes in the page's own Elementor
 * config, not here, so an editor can retheme a card without touching CSS.
 *
 * TYPE
 *
 * Elementor global fonts with the Figma number as the fallback, matching the
 * Events and News blocks. The frame's Heading/H5 is the kit's h3 (32px) and its
 * Heading/H4 is the kit's h4 (24px); the names differ because the kit has no H5.
 */

/* ==========================================================================
   1. THE CHROME
   ========================================================================== */

body.theme-agend--account-is-dashboard {
	/*
	 * The chrome is the frame's White mode, and Dashboard::theme_the_rail() puts
	 * `ota-theme--white` on the header so these resolve to it. They are declared
	 * on the body rather than on the header because the welcome bar reads them
	 * too, and it is not inside the header; the fallbacks below are that mode's
	 * own values, for the case where colour themes are not configured at all.
	 */
	--otd-surface: var(--ota-background, #ffffff);
	--otd-text: var(--ota-text, #003038);
	--otd-active-bg: var(--ota-cta-bg, #003038);
	--otd-active-text: var(--ota-cta-text, #ffffff);

	/* The frame's 300px rail and the 32px gutters either side of the content. */
	--otd-rail: 300px;
	--otd-gutter: 32px;
}

/*
 * AND DECLARED AGAIN ON THE RAIL, WHICH IS NOT BELT AND BRACES.
 *
 * `--otd-surface: var(--ota-background, …)` is substituted where it is
 * DECLARED, not where it is used, so the copy on `body` freezes to whatever
 * `--ota-background` is on the body — the site's default theme, Ash — and then
 * inherits into the header as that fixed value. The `ota-theme--white` class
 * further down the tree never gets a look in, and the rail comes out ash.
 * (assets/css/ota-theme-buttons.css records the same trap with the theme's own
 * button variables.)
 *
 * Redeclaring them on the header re-runs the lookup there, where the White mode
 * is in force. The body copy above is still needed: the welcome bar reads these
 * too and is not inside the header.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header.agendtheme-dashboard-header {
	--otd-surface: var(--ota-background, #ffffff);
	--otd-text: var(--ota-text, #003038);
	--otd-active-bg: var(--ota-cta-bg, #003038);
	--otd-active-text: var(--ota-cta-text, #ffffff);
}

/*
 * The welcome bar sits outside the header, where the roles fall through to the
 * site's default theme. The frame draws that region in the White mode too.
 */
body.theme-agend--account-is-dashboard #agendtheme-content .agendtheme-dashboard-welcome-bar {
	--otd-text: #003038;
}

/* --- Sidebar navigation --------------------------------------------------- */

/*
 * The rail. The theme sizes the dashboard header from its own skin variables,
 * which put it at a width the frame does not use. `flex: none` because the
 * header is a flex child of #agendtheme-dashboard and a wide content column
 * would otherwise shrink it.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header.agendtheme-dashboard-header {
	flex: none;
	width: var(--otd-rail);
	/*
	 * !important, and it answers exactly one declaration: the theme's compiled
	 * skin carries `#agendtheme-dashboard #agendtheme-header { background:
	 * #F0E7D8 !important }`, a hardcoded ash with no variable behind it. Nothing
	 * else in this file needs it, and the strip of ash either side of the white
	 * logo block was this rule showing through.
	 */
	background: var(--otd-surface) !important;
}

/*
 * The logo block is 198px wide inside a 300px rail, so anything the header is
 * painted with shows as a strip either side of it. The frame paints all three
 * the same, which is the rail's surface.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-logo {
	background: var(--otd-surface);
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-navigation .agendtheme-header-navigation-wrap {
	padding-inline: 12px;
}

/*
 * The row. 12px between glyph and label, 24px in from the rail's inner edge,
 * and the frame's 53px pitch kept as a 49px pill with 2px of margin either side
 * rather than a 53px pill with none.
 *
 * The frame never has to answer this, because it draws one active row. This
 * menu has two — "Dashboard" and "My Account" both point at /my-account — and
 * two 53px pills stacked with no gap merge into one peanut-shaped blob. The
 * duplicate is the real fix and it is the client's menu to change; until then
 * the gap makes two pills read as two.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li {
	margin-block: 2px;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a {
	display: flex;
	align-items: center;
	gap: 12px;
	padding: 10px 24px;
	color: var(--otd-text);
	font-size: 1rem;
	font-weight: 400;
	line-height: 1.753em;
	text-decoration: none;
}

/*
 * The glyph box. The theme reserves 2em with 1.5rem of trailing padding, which
 * is its own icon rhythm and twice the frame's. Zeroed rather than adjusted,
 * because the row's `gap` is what sets the distance now.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a > span.icon {
	display: inline-flex;
	flex: none;
	align-items: center;
	justify-content: center;
	width: 20px;
	height: 20px;
	padding: 0;
	color: inherit;
}

/*
 * THE GLYPHS
 *
 * Font Awesome, not artwork shipped here. The frame names eleven Classic Light
 * icons and the client sets them per menu item in Appearance > Menus, which is
 * where they belong: they are content, and the rail is theirs to change.
 *
 * WHAT "CLASSIC LIGHT" IS ON THIS SITE. The kit is loaded by Elementor and
 * serves Font Awesome 5.15.4 Pro in SVG+JS mode, verified by watching the
 * network: kit.fontawesome.com then releases/v5.15.4/js/pro.min.js then one
 * svgs/light/*.svg per icon. In 5.x the Classic Light style is the `fal`
 * prefix — `fa-light` is the 6.x spelling and 5.x's JavaScript ignores it, so a
 * `fa-light` class draws nothing. Four of the frame's layer names are 6.x
 * renames and were mapped back: basket-shopping to shopping-basket,
 * ticket-simple to ticket, chart-column to chart-bar, arrow-right-from-bracket
 * to sign-out.
 *
 * SVG+JS mode means the theme's `<i>` is REPLACED in the DOM by an
 * `<svg class="svg-inline--fa">`, so nothing here can key off the `<i>`, and
 * anything drawn alongside it lands as a second glyph in the same box.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a > span.icon > svg,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a > span.icon > i {
	display: block;
	width: 20px;
	height: 20px;
	font-size: 20px;
	line-height: 1;
	color: inherit;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a > span.label {
	flex-grow: 1;
	margin-right: 0;
}

/*
 * The pill. The theme gives the row `var(--at-border-radius)` and a secondary
 * background; the frame gives it a full round and the CTA role.
 *
 * ON THE LINK, NOT THE <li>. A parent row's <li> also holds its sub-menu, so
 * while the group is open the <li> is as tall as the row plus every child.
 * Painted there, the 999px radius and the navy fill became a 300 x 440
 * ellipse over the open My Account group on /my-account/edit-address, where
 * My Account is the current row because every WooCommerce account endpoint
 * queries page 15, and the child links inside it sat navy on navy (Bryce,
 * 4 Sep 2026). The <a> is only ever the row, so the pill is drawn on it. The
 * theme paints its own secondary background on the current <li>, and that
 * would fill the same tall box, so it is cleared for the same reason.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active {
	background-color: transparent;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > a {
	border-radius: 999px;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item > a,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active > a {
	background-color: var(--otd-active-bg);
}

/*
 * THE ONE !important IN THE CHROME, AND IT ANSWERS ONE RULE.
 *
 * The theme's `#agendtheme-dashboard #agendtheme-header .agendtheme-header-navigation a`
 * carries `color: #003038 !important`, so no amount of specificity reaches the
 * active row's label: on the frame's navy pill that is navy on navy, an
 * invisible label. Only the active state needs it; the resting row is already
 * the colour that rule wants.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item > a,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active > a {
	color: var(--otd-active-text) !important;
}

/*
 * The active marker. The theme already draws a dot here, at .4em of the
 * secondary accent held to 70%; the frame draws a 6px dot in the CTA text
 * colour. Same pseudo-element, restated values, so there is one dot and not two.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item > a::after,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active > a::after {
	flex: none;
	width: 6px;
	height: 6px;
	background: currentcolor;
	opacity: 1;
}

/* The glyph in an active row follows the row, not the theme's accent. */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item > a span.icon,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active > a span.icon {
	color: inherit;
}

/*
 * Sub-menu rows keep the theme's flyout behaviour and take only the frame's
 * spacing. The frame does not draw an open sub-menu, so nothing else is guessed
 * at here.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul > li > a {
	padding-left: 24px;
}

/*
 * The hover state is a RING, not a tint. The theme draws a full-bleed
 * square-cornered rectangle in 5% of its accent, which on a rail whose rows are
 * pills reads as a stray grey box — and it is wider than the pill, because the
 * theme sizes it to the anchor and centres it with a transform.
 *
 * The site has one hover state for an interactive surface and it is the 2px
 * ring in the Text Muted role, set out in assets/css/ota-news-block.css and
 * used by the News, Events and benefit cards. A percentage tint is not part of
 * that vocabulary, so the theme's pseudo-element is repurposed into the ring
 * rather than left as a second, softer, hover language in the same product.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:hover > a::before,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:focus-within > a::before {
	left: 0;
	top: 0;
	width: 100%;
	height: 100%;
	transform: none;
	border: 2px solid var(--ota-text-muted, #005361);
	border-radius: 999px;
	background: none;
	opacity: 1;
}

/* An active row is already painted; a wash on top of it only muddies the navy. */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.current-menu-item:hover > a::before,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-active:hover > a::before {
	display: none;
}

/*
 * The has-children caret. The theme draws it as a solid triangle in the site
 * accent, which puts an orange arrowhead on a rail the frame draws in two
 * colours. Kept, because a row with a flyout should say so, and given the row's
 * own colour so it belongs to the row.
 *
 * NOT on a current row. The theme builds the caret and the active dot out of
 * the SAME `a::after`, and its dot rule wins by carrying `border: 0 !important`;
 * dimming the caret to 60% here therefore dimmed the dot on any row that was
 * both current and a parent, which is why My Account's dot came out grey where
 * Dashboard's was white.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.menu-item-has-children:not(.current-menu-item):not(.is-active) > a::after {
	border-top-color: currentcolor;
	opacity: 0.6;
}

/*
 * THE CLOSED FLYOUT HAS TO BE HIDDEN, NOT JUST TRANSPARENT.
 *
 * The theme closes the My Account sub-menu with `opacity: 0` alone, leaving a
 * 262 x 198 panel laid over the first card of the page: it is transparent, but
 * it is painted, it takes the pointer, and it comes out solid white in a
 * screenshot. `visibility` is the missing half of that pair. It is not animated
 * by the theme's own opacity transition, so the flyout still fades exactly as
 * it did, and the two states below restore it on hover and on keyboard focus.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu {
	visibility: hidden;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:hover > ul.sub-menu,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:focus-within > ul.sub-menu {
	visibility: visible;
}

/*
 * THE OPEN FLYOUT, AND WHY IT WAS UNREADABLE.
 *
 * The theme paints the panel with `--at-header-background-color` and leaves the
 * labels at the body text colour. That variable is set PER PAGE from the page's
 * own header settings: white on the account dashboard, teal (#005361) on My
 * Courses. So the same menu draws navy-on-white on one dashboard route and
 * navy-on-teal on the next, which is the unreadable panel Bryce reported.
 *
 * Pinned to the rail's own roles instead, so it is an extension of the rail on
 * every route and follows the rail if the rail is ever rethemed. The frame does
 * not draw an open sub-menu, so the rail's own language is what it is given:
 * the card radius, the rail's 12px inset, and the rail's pill rows.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu {
	padding: 12px;
	border-radius: 14px;
	background-color: var(--otd-surface);
	box-shadow: 0 12px 32px rgb(0 48 56 / 14%);
}

/*
 * THE FLYOUT HAS NO POINTER TAIL.
 *
 * The theme builds one out of `ul:before` as a 10px CSS triangle, and the
 * dashboard skin re-aims it to point left with
 * `border-right-color: var(--at-color-background-primary)` at `left: -10px`, so
 * it juts out of the panel's left edge. Two reasons it goes: the frame draws
 * the flyout as a plain rounded card with no tail, and the tail is painted in
 * the theme's own background variable rather than the panel's, so once the
 * panel is repainted to `--otd-surface` above it no longer matches the thing it
 * is attached to.
 *
 * Both states are named. The dashboard skin only re-aims the `:hover` tail, so
 * on keyboard focus the base rule still draws the original downward tail above
 * the panel. Descendant rather than child, because the theme draws a rotated
 * tail on nested sub-menus too.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:hover ul.sub-menu::before,
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:focus-within ul.sub-menu::before {
	display: none;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu > li {
	margin-block: 2px;
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu > li > a {
	padding: 10px 20px;
	color: var(--otd-text);
	white-space: nowrap;
}

/*
 * NO FILL ON THE CHILD <li>. It used to carry the active fill here, from the
 * fly-out styling that predates the pill moving onto the link. The <li> only
 * ever gets the theme's `--at-border-radius`, 4px, so the current child came
 * out as a navy rectangle with the correct 999px pill hidden inside it, while
 * every sibling around it was a pill (Bryce, 11 Sep 2026). The rule above at
 * `li.current-menu-item > a` already paints this row, on the element that
 * holds the radius, so the fill is simply dropped rather than re-rounded: one
 * element paints the state, not two.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu > li.current-menu-item > a {
	color: var(--otd-active-text) !important;
}

/* --- Welcome bar ---------------------------------------------------------- */

body.theme-agend--account-is-dashboard #agendtheme-content .agendtheme-content-inner {
	padding-inline: var(--otd-gutter);
}

body.theme-agend--account-is-dashboard .agendtheme-dashboard-welcome-bar {
	align-items: flex-start;
	padding-block: 32px 8px;
}

/*
 * Heading/H2. The theme prints this as an h3 on its own scale; the frame draws
 * it at the kit's H2, the same size the page hero uses elsewhere on the site.
 */
body.theme-agend--account-is-dashboard .agendtheme-dashboard-welcome-bar-welcome__heading {
	color: var(--otd-text);
	font-size: var(--e-global-typography-h2-font-size, 2.75rem);
	font-weight: var(--e-global-typography-h2-font-weight, 400);
	line-height: var(--e-global-typography-h2-line-height, 1.08em);
	letter-spacing: var(--e-global-typography-h2-letter-spacing, -0.44px);
}

/* The avatar cluster: cart, rule, avatar, My Account, rule, Logout. */
body.theme-agend--account-is-dashboard .agendtheme-dashboard-avatar {
	align-items: center;
	color: var(--otd-text);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
}

/*
 * No avatar beside My Account, matching the site header. The theme prints it
 * with get_avatar() directly, so its Gravatar Customizer setting cannot turn it
 * off. The label's margin only spaced it from the avatar.
 */
body.theme-agend--account-is-dashboard .agendtheme-dashboard-avatar .agendtheme-icon-label-button > .icon {
	display: none;
}

body.theme-agend--account-is-dashboard .agendtheme-dashboard-avatar .agendtheme-icon-label-button > .label {
	margin-left: 0;
}

/*
 * The phone header's avatar button, gone once signed in (Teamwork 49488156).
 *
 * Under 992px the theme draws the dashboard header as logo, burger, avatar.
 * The avatar is the theme's profile toggle: it opens a panel carrying the
 * member's name, Logout and My Dashboard. On this site that panel duplicates
 * the rail, which starts with Dashboard and ends in Logout, and the picture
 * itself is Gravatar's grey placeholder for most members. The client asked for
 * it to go and for the close control to sit in the corner, which it does once
 * the avatar no longer takes the last slot in the row: the burger's wrapper
 * already grows to fill the bar and aligns its button to the end.
 *
 * Signed in only. Signed out the same button carries the person glyph and
 * opens the header login form, and although the page body carries
 * WooCommerce's own login form as well, a guest's phone header is not what
 * the ticket is about.
 *
 * The theme already hides this button at 992px and up, with `!important`,
 * so this is its own rule carried down to the phone. The `!important` is
 * needed here too: the element carries the `d-flex` utility class, which
 * sets `display: flex !important`.
 */
body.logged-in.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-profile-toggle {
	display: none !important;
}

/*
 * The member notifications band. The kiosk plugin prints this above the page's
 * own content on every dashboard route, and the frame does not draw it, so it
 * is left as the kiosk styles it and only given the page's rhythm: without this
 * it sits hard against the first card row.
 */
body.theme-agend--account-is-dashboard .agend-member-messaging:not(:empty) {
	margin-block-end: 32px;
}

/* ==========================================================================
   2. THE LANDING PAGE
   ========================================================================== */

/*
 * Every top-level section on page 50 carries `ota-dash`. The band spacing is set
 * once, here, rather than in each section's own Elementor padding, so the rhythm
 * lives in one place and survives an editor nudging a single band.
 *
 * The frame's vertical rhythm, measured off the artboard: cards at 164, the
 * benefits heading at 516, its grid at 623, the events heading at 1379, the Loop
 * band at 1975. That is 54px between a band and the next heading, and 48px
 * between a heading and the grid it introduces.
 */
/*
 * A band is a rounded card on a white page, so the SECTION paints nothing.
 *
 * Colour_Themes gives any element carrying an `ota-theme--*` class a default
 * paint through a zero-specificity `:where()` rule, and these sections carry
 * one so that the widgets inside them inherit the right roles. That paint is a
 * square-cornered rectangle occupying exactly the same box as the rounded band
 * inside it, so it filled the Loop band's four 24px corners back in and the band
 * read as a full-bleed block. The roles are what is wanted from the class here,
 * not the fill.
 */
.ota-dash.elementor-section {
	margin-block: 0;
	padding-block: 0;
	background-color: transparent;
}

.ota-dash + .ota-dash.elementor-section {
	margin-block-start: 54px;
}

.ota-dash-benefits-head + .ota-dash.elementor-section {
	margin-block-start: 48px;
}

/*
 * DASHBOARD ONLY, on purpose. On the dashboard the theme's content column is
 * the measure and a band fills it edge to edge, so Elementor's boxed 1140px
 * container has to let go. On any other page these blocks are pasted onto
 * (the client copies them between pages, 4 Sep 2026) the page's own boxed
 * width is the measure, and releasing it there would run a band out to the
 * viewport edge. Everything else in this file travels with the block's own
 * classes; this is the one rule that is about where the block sits.
 */
body.theme-agend--account-is-dashboard .ota-dash.elementor-section > .elementor-container {
	width: 100%;
	max-width: none;
}

/*
 * WHY EVERY CONTAINER RULE BELOW REPEATS `.elementor-section`
 *
 * Elementor's own `.elementor-section .elementor-container { display: flex }` is
 * two classes, and its frontend stylesheet loads after this file, so a
 * two-class override here loses the tie and the grid silently stays a flex row
 * with equal columns. Claiming the section class as well is what makes the
 * 704/340 split, and the benefit grid, actually take.
 *
 * Elementor also pays for its column gaps in column padding, which would sit
 * inside the cards' rounded corners; every grid below sets its own gap instead.
 */
.ota-dash.elementor-section > .elementor-container > .elementor-column > .elementor-widget-wrap {
	padding: 0;
}

/* --- 2a. The two cards ---------------------------------------------------- */

/*
 * 704 and 340 with 26 between, from the frame. Expressed as fr so the pair keeps
 * its proportion at any width, and as a grid rather than through Elementor's own
 * column gap, which is column padding and would sit inside the cards' rounded
 * corners instead of between them.
 */
.ota-dash-cards.elementor-section > .elementor-container {
	display: grid;
	grid-template-columns: minmax(0, 704fr) minmax(0, 340fr);
	gap: 26px;
	align-items: stretch;
}

/*
 * THE COLUMN IS THE CARD, and that is deliberate rather than convenient. Each of
 * these two columns carries its own `ota-theme--*` class, because the frame puts
 * a Navy card beside a Teal one inside a White page and a colour theme is a
 * section-level control, so per-column is the only way to say it. Colour_Themes
 * gives any themed element a default paint through a `:where()` rule, so the
 * background arrives on the column whatever else happens. Paint the card on an
 * inner element instead and that column paint shows through as four square
 * corners behind the rounded card.
 */
.ota-dash-cards.elementor-section > .elementor-container > .elementor-column {
	position: relative;
	width: 100%;
	overflow: hidden;
	border-radius: 14px;
	background-color: var(--ota-background, #003038);
	color: var(--ota-text, #f0e7d8);
}

.ota-dash-cards.elementor-section > .elementor-container > .elementor-column > .elementor-widget-wrap {
	position: relative;
	z-index: 1;
	min-height: 298px;
	height: 100%;
}

@media (max-width: 1024px) {
	.ota-dash-cards.elementor-section > .elementor-container {
		grid-template-columns: minmax(0, 1fr);
	}
}

/* --- The membership card -------------------------------------------------- */

/*
 * The kiosk plugin's Membership Card widget, restyled rather than replaced: the
 * fields, the CRM lookup and the non-member fallback are all its behaviour and
 * none of it is reproduced here. The widget's own box is left transparent, since
 * the column above is the card.
 */
.ota-dash-cards.elementor-section > .elementor-container > .ota-dash-membership.elementor-column > .elementor-widget-wrap {
	display: flex;
	flex-direction: column;
	justify-content: center;
	padding: 32px 44px;
}

/*
 * The frame's dot motif, 419.746 x 406.382, anchored so it runs off the card's
 * bottom-right corner. Painted as a mask rather than as a background image
 * because the export is one flat fill and the role behind it is `overlay`, which
 * changes with the theme; an <img> or a background-image could not follow it.
 * On the column and not on the widget, so the frame's x=467 is measured from the
 * same edge it is measured from in Figma.
 */
.ota-dash-membership.elementor-column::after {
	content: "";
	position: absolute;
	top: 55px;
	/*
	 * The frame puts the motif at x=467 in a 704px card, so 183px of it hangs off
	 * the trailing edge. Anchored to that edge rather than to the leading one, so
	 * the same amount hangs off at any card width instead of the motif sliding out
	 * of the card as it narrows.
	 */
	inset-inline-end: -183px;
	width: 419.746px;
	height: 406.382px;
	pointer-events: none;
	background-color: var(--ota-overlay, #005361);
	-webkit-mask: url("../icons/dashboard/membership-pattern.svg") no-repeat 0 0 / contain;
	mask: url("../icons/dashboard/membership-pattern.svg") no-repeat 0 0 / contain;
}

/*
 * The widget's own box stands down: the column above is the card. Its white
 * fill and its 2rem of padding are set by the widget's Background Color control
 * and by `.agend-membership-card` in the kiosk plugin's own stylesheet, so the
 * control is set to transparent in this page's config and the padding is zeroed
 * here.
 */
.ota-dash-membership .agend-membership-card {
	min-height: 0;
	padding: 0;
	background: none;
	color: inherit;
}

.ota-dash-membership .agend-membership-card__content {
	width: 100%;
}

.ota-dash-membership .agend-membership-card__main {
	display: flex;
	flex-direction: column;
	gap: 28px;
	width: 100%;
	max-width: 447px;
}

/* Heading/H5 in the frame, which is the kit's h3. */
.ota-dash-membership .agend-membership-card .agend-membership-card__title {
	margin: 0;
	font-size: var(--e-global-typography-h3-font-size, 2rem);
	font-weight: var(--e-global-typography-h3-font-weight, 400);
	line-height: var(--e-global-typography-h3-line-height, 1.08em);
	letter-spacing: 0;
}

/*
 * THE FIELD ROWS ARE THE WIDGET'S GRID, RETUNED, NOT A NEW LAYOUT.
 *
 * The kiosk plugin draws these as a two-column grid on `__details` with
 * `display: contents` on each `__field`, so every label and value is a grid
 * item in its own right. That is already the frame's structure; only the track
 * sizes and the rhythm differ. Fighting it with flex would mean overriding
 * `display: contents` first, for no gain.
 *
 * The frame's row is a 140px label at the leading edge and a 118px value box at
 * the trailing one, which is `1fr` and a fixed track. 8px between rows.
 */
.ota-dash-membership .agend-membership-card .agend-membership-card__details {
	display: grid;
	/*
	 * The frame's value box is a flat 118px, which is enough for its own sample
	 * data ("1000231", "1 July 2026") and not for a real membership level. The
	 * `max-content` ceiling keeps the frame's look — label at the leading edge,
	 * value at the trailing one, a wide gap between — while letting a long value
	 * stay on one line instead of wrapping inside a 118px column.
	 */
	grid-template-columns: minmax(0, 1fr) minmax(118px, max-content);
	column-gap: 24px;
	row-gap: 8px;
	align-items: center;
}

.ota-dash-membership .agend-membership-card .agend-membership-card__field {
	display: contents;
}

/* Label/Default Bold, and the widget's own #7e7c7c has to go. */
.ota-dash-membership .agend-membership-card .agend-membership-card__field .agend-membership-card__label {
	margin: 0;
	min-width: 140px;
	font-family: inherit;
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
	line-height: 1;
	text-align: left;
}

/* Body/Default. */
.ota-dash-membership .agend-membership-card .agend-membership-card__field .agend-membership-card__value {
	margin: 0;
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-body-font-weight, 300);
	line-height: var(--e-global-typography-body-line-height, 1.65em);
	text-align: left;
}

/*
 * The join prompt. Only a non-member ever sees it, so the frame does not draw
 * it; it is given the card's own rhythm rather than left at the widget's
 * default so the two states read as one object. The widget prints its own <hr>
 * above the block, which is the same rule twice once this border is on.
 */
.ota-dash-membership .agend-membership-card .agend-membership-card__cta {
	position: relative;
	margin-block-start: 28px;
	padding-block-start: 28px;
	border-block-start: 1px solid var(--ota-divider, rgba(240, 231, 216, 0.2));
}

.ota-dash-membership .agend-membership-card hr {
	display: none;
}

/* --- The CPD snapshot ----------------------------------------------------- */

/*
 * The heading widget and the CPD plugin's shortcode, stacked and centred inside
 * the column that is the card.
 */
.ota-dash-cards.elementor-section > .elementor-container > .ota-dash-cpd.elementor-column > .elementor-widget-wrap {
	display: flex;
	flex-direction: column;
	align-items: center;
	justify-content: center;
	gap: 27px;
	padding: 26px 24px;
}

.ota-dash-cpd > .elementor-widget-wrap > .elementor-element {
	width: 100%;
	margin: 0;
}

/*
 * The CPD plugin's own chrome around the dial. Elementor's widget margin and
 * the chart's padding together add 60px to a card the frame draws at 301, so
 * they are zeroed and the 27px rhythm below is the only spacing left.
 */
.ota-dash-cpd .elementor-widget-shortcode .elementor-widget-container,
.ota-dash-cpd .cpd-points-chart {
	margin: 0;
	padding: 0;
}

/* Label/Default Bold, and the frame's one use of the White Text role. */
.ota-dash-cpd .elementor-widget-heading .elementor-heading-title {
	margin: 0;
	color: var(--ota-white-text, #ffffff);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem);
	font-weight: 700;
	line-height: 1;
	text-align: center;
}

.ota-dash-cpd .cpd-points-chart {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 27px;
}

/*
 * The header line carries the CPD period start date, and the frame puts that
 * under the dial. The kiosk plugin's template prints it first, so it is
 * reordered rather than re-templated: that markup is the kiosk's and stays its
 * own. Body/Small.
 */
.ota-dash-cpd .cpd-points-header {
	order: 2;
	color: var(--ota-text, #f0e7d8);
	font-size: var(--e-global-typography-small-font-size, 0.9375rem);
	font-weight: var(--e-global-typography-small-font-weight, 300);
	line-height: var(--e-global-typography-small-line-height, 1.65em);
	text-align: center;
}

/* The 153px disc the dial sits on: Oval 390:6036, the CTA Background role. */
.ota-dash-cpd .cpd-points-snapshot-container {
	order: 1;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 153px;
	height: 153px;
	border-radius: 999px;
	background-color: var(--ota-cta-bg, #f0e7d8);
}

/*
 * THE DIAL'S ARITHMETIC, because the numbers below look arbitrary and are not.
 *
 * ProgressBar.js draws into a 0 0 100 100 viewBox at a radius of
 * 50 - strokeWidth/2, and the CPD plugin's cpd-points.js hardcodes
 * strokeWidth: 6, so the ring's centreline is always at r=47, i.e. 94% of
 * whatever the box is sized to. The frame draws the ring on a 115px centreline
 * diameter with a 12px band, so:
 *
 *   box     115 / 0.94        = 122.34px
 *   stroke  12 / (122.34/100) = 9.81 user units
 *
 * At that stroke the band's outer edge lands at 51.9 of a 100 box, so the SVG
 * needs `overflow: visible` or the ring is clipped 2px in on each side. Stroke
 * width is a presentation attribute on the path and CSS outranks it, so none of
 * this needs the CPD plugin's JavaScript changed.
 */
.ota-dash-cpd .cpd-points-snapshot-graph {
	position: relative;
	width: 122.34px;
	height: 122.34px;
}

.ota-dash-cpd .cpd-points-snapshot-graph svg {
	display: block;
	overflow: visible;
}

.ota-dash-cpd .cpd-points-snapshot-graph svg path {
	stroke-width: 9.81;
	stroke-linecap: round;
}

/*
 * ProgressBar.js appends the trail first and the progress arc second and gives
 * neither a class, so document order is the only handle on them.
 *
 * The trail is Oval 390:6037, white in every mode the frame draws.
 */
.ota-dash-cpd .cpd-points-snapshot-graph svg path:first-of-type {
	stroke: var(--ota-white-text, #ffffff);
}

/*
 * The progress arc is Stroke 1, 390:6038. It is the section's own background
 * colour, reading as a cut-out of the disc rather than as a second accent, which
 * is why this is `--ota-background` and not `--ota-accent`.
 */
.ota-dash-cpd .cpd-points-snapshot-graph svg path + path {
	stroke: var(--ota-background, #005361);
}

/*
 * ProgressBar.js writes `color` as an INLINE style on this element, from the
 * `data-color` the CPD plugin passes it, which is the kiosk's brand primary
 * setting (#303030 here) and nothing to do with the section's theme. An inline
 * style can only be answered with !important.
 */
.ota-dash-cpd .cpd-points-snapshot-graph .progressbar-text {
	color: var(--ota-cta-text, #005361) !important;
	font-size: 3rem;
	font-weight: 700;
	line-height: 1;
	text-align: center;
	white-space: nowrap;
}

.ota-dash-cpd .cpd-points-snapshot-graph .cpd-points-text {
	font-size: 0.875rem;
	font-weight: 400;
	line-height: 1;
}

/* The whole dial is the link when the shortcode has been given one. */
.ota-dash-cpd .cpd-points-graph-link {
	display: block;
	text-decoration: none;
}

/*
 * A non-member gets the CPD tracker invitation in place of the dial (see
 * CPD_Non_Member_Message), under the card's own heading.
 */
.ota-dash-cpd .ota-cpd-join {
	display: flex;
	flex-direction: column;
	align-items: center;
	gap: 16px;
	text-align: center;
}

.ota-dash-cpd .ota-cpd-join p {
	margin: 0;
}

/*
 * The membership card's Join button, whose markup the invitation copies
 * exactly. The markup alone is not enough: the kiosk's stylesheet only draws
 * `.agend-membership-card__cta__button a` (the 2px border, padding and weight)
 * inside `.agend-membership-card .agend-membership-card__cta`, and Join's navy
 * fill is the membership card's own colour, so it reads as a white outline. On
 * the teal card the fill is dropped to get the same outline. 0,4,1 to clear the
 * theme's `html body .btn.btn-primary`.
 */
.ota-dash-cpd .ota-cpd-join .agend-membership-card__cta__button a.btn,
.ota-dash-cpd .ota-cpd-join .agend-membership-card__cta__button a.btn:is(:hover, :focus, :active) {
	padding: 12px 24px;
	border: 2px solid currentColor;
	background-color: transparent;
	font-weight: 600;
}

/* Body/Small, as the dial's header line. */
.ota-dash-cpd .ota-cpd-join__body {
	color: var(--ota-text, #f0e7d8);
	font-size: var(--e-global-typography-small-font-size, 0.9375rem);
	font-weight: var(--e-global-typography-small-font-weight, 300);
	line-height: var(--e-global-typography-small-line-height, 1.65em);
}

/* --- 2b. Member benefits -------------------------------------------------- */

/*
 * The heading row: eyebrow and heading on the left, a text link on the right,
 * centred against each other rather than baseline-aligned, so a wrapped heading
 * does not drag the link down with it.
 */
.ota-dash-benefits-head.elementor-section > .elementor-container {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	justify-content: space-between;
	gap: 16px 24px;
}

.ota-dash-benefits-head.elementor-section > .elementor-container > .elementor-column {
	width: auto;
}

.ota-dash-benefits-head .ota-dash-headings > .elementor-widget-wrap {
	display: flex;
	flex-direction: column;
	gap: 8px;
}

/* Label/Eyebrow. */
.ota-dash-eyebrow .elementor-heading-title {
	margin: 0;
	color: var(--ota-accent, #f04c3a);
	font-size: var(--e-global-typography-eyebrow-font-size, 1.0625rem);
	font-weight: var(--e-global-typography-eyebrow-font-weight, 700);
	line-height: var(--e-global-typography-eyebrow-line-height, 1.46em);
	letter-spacing: var(--e-global-typography-eyebrow-letter-spacing, 1px);
}

/* Heading/H5 in the frame, which is the kit's h3. */
.ota-dash-title .elementor-heading-title {
	margin: 0;
	color: var(--ota-text, #003038);
	font-size: var(--e-global-typography-h3-font-size, 2rem);
	font-weight: var(--e-global-typography-h3-font-weight, 400);
	line-height: var(--e-global-typography-h3-line-height, 1.08em);
	letter-spacing: var(--e-global-typography-h3-letter-spacing, -0.32px);
}

/*
 * "All membership benefits" with the frame's 24px arrow. Body/Small at Bold in
 * the Text Muted role. The arrow is the design's own export, drawn as a mask so
 * it takes the link's colour with it.
 */
.ota-dash-link .elementor-heading-title {
	margin: 0;
	font-size: inherit;
	line-height: inherit;
}

/*
 * The arrow hangs off the TITLE, not off an anchor inside it. Elementor's
 * Heading widget only wraps its text in an `<a>` when a Link is set, and this
 * one has no destination yet: the frame draws the affordance, and the two
 * "Member Benefits" entries in the mega menu both still point at `#`. Drawn
 * here so the row is right either way, and so it keeps the arrow when the URL
 * arrives.
 */
.ota-dash-link .elementor-heading-title,
.ota-dash-link .elementor-heading-title a {
	display: inline-flex;
	align-items: center;
	gap: 8px;
	color: var(--ota-text-muted, #005361);
	font-size: var(--e-global-typography-small-font-size, 0.9375rem);
	font-weight: 700;
	line-height: var(--e-global-typography-small-line-height, 1.65em);
	text-decoration: none;
}

.ota-dash-link .elementor-heading-title::after {
	content: "";
	flex: none;
	width: 24px;
	height: 24px;
	background-color: currentcolor;
	-webkit-mask: url("../icons/dashboard/arrow-right.svg") no-repeat center / contain;
	mask: url("../icons/dashboard/arrow-right.svg") no-repeat center / contain;
}

/* With a link set, the anchor is the whole row and the arrow is the title's. */
.ota-dash-link .elementor-heading-title:has(a)::after {
	margin-inline-start: -8px;
}

.ota-dash-link .elementor-heading-title a:hover,
.ota-dash-link .elementor-heading-title a:focus-visible {
	text-decoration: underline;
}

/*
 * The 3 x 2 grid. Three Elementor columns with two Call to Action widgets in
 * each, so reading down a column gives the frame's reading order across a row.
 * 26px both ways.
 */
.ota-dash-benefits.elementor-section > .elementor-container {
	display: grid;
	grid-template-columns: repeat(3, minmax(0, 1fr));
	gap: 26px;
	align-items: stretch;
}

.ota-dash-benefits.elementor-section > .elementor-container > .elementor-column {
	width: 100%;
}

/*
 * Two equal rows, not two flexed children. A flex column equalises the pair
 * inside ITSELF, so with three columns of different content the six cards come
 * out at three different heights and the second row does not line up across the
 * grid. Explicit `1fr 1fr` rows against the stretched column give the frame's
 * six identical cards.
 */
.ota-dash-benefits.elementor-section > .elementor-container > .elementor-column > .elementor-widget-wrap {
	display: grid;
	grid-template-rows: repeat(2, minmax(0, 1fr));
	gap: 26px;
	height: 100%;
}

.ota-dash-benefits.elementor-section > .elementor-container > .elementor-column > .elementor-widget-wrap > .elementor-element {
	width: 100%;
	min-height: 0;
	margin: 0;
}

@media (max-width: 1024px) {
	.ota-dash-benefits.elementor-section > .elementor-container {
		grid-template-columns: repeat(2, minmax(0, 1fr));
	}
}

@media (max-width: 640px) {
	.ota-dash-benefits.elementor-section > .elementor-container {
		grid-template-columns: minmax(0, 1fr);
	}
}

/* --- The benefit card ----------------------------------------------------- */

/*
 * Component/benefit, 2333:34751. Deliberately NOT a new widget: it is Elementor's
 * Call to Action, which is what the three cards already on this page were, and
 * which assets/css/ota-buttons.css already reaches through its "branch C". That
 * keeps the card editable by the client the way the rest of the page is.
 *
 * The measurements are the Events Block card's, because in the frame they are
 * the same card: a 170px media strip, 24px of body padding, a rule above a 48px
 * action row.
 */
.ota-dash-benefit.elementor-widget-call-to-action {
	--otd-card-media: 170px;
	--otd-card-pad: 24px;
	--otd-dot-bg: var(--ota-background, #f0e7d8);
	--otd-dot-fg: var(--ota-text, #003038);
	/*
	 * The widget carries `ota-theme--ash` for the roles, and Colour_Themes
	 * paints anything with a theme class through its `:where()` default. On
	 * the widget that is a square ash box in exactly the card's footprint, so
	 * the card's 14px corners were filled back in (Bryce, 4 Sep 2026). Same as
	 * `.ota-dash.elementor-section` above: the class is for the roles, the
	 * card paints itself.
	 */
	background-color: transparent;
}

/*
 * THE CARD FILLS THE WIDGET. The grid above stretches each widget to its row,
 * but Elementor puts `.elementor-widget-container` between the widget and the
 * card, and that div has no height of its own, so the card's `height: 100%`
 * below resolved to auto and the card came out content-sized: 376px inside a
 * 397px widget on the Advocacy page, the See More row trailing the description
 * at whatever height the copy happened to reach (Bryce, 4 Sep 2026). The
 * widget and the container are made flex columns and the card grows, which
 * holds whether or not Elementor's optimised markup removes the container.
 */
.ota-dash-benefit.elementor-widget-call-to-action,
.ota-dash-benefit.elementor-widget-call-to-action > .elementor-widget-container {
	display: flex;
	flex-direction: column;
}

.ota-dash-benefit.elementor-widget-call-to-action > .elementor-widget-container,
.ota-dash-benefit .elementor-cta {
	flex: 1 1 auto;
}

.ota-dash-benefit .elementor-cta {
	position: relative;
	display: flex;
	flex-direction: column;
	height: 100%;
	min-height: 339px;
	overflow: hidden;
	border-radius: 14px;
	background-color: var(--ota-background, #f0e7d8);
	color: var(--ota-text, #003038);
}

/*
 * The media strip keeps its height with no image chosen, showing the divider
 * role rather than collapsing: a card whose top third vanishes reads as broken,
 * and this is the same placeholder the Events Block uses.
 */
.ota-dash-benefit.elementor-cta--skin-classic .elementor-cta__bg-wrapper {
	flex: none;
	width: 100%;
	/*
	 * Elementor's `.elementor-cta--skin-classic .elementor-cta__bg-wrapper` sets a
	 * 200px floor at the same weight as a two-class selector, so the skin class is
	 * claimed here to get past it. The widget's own Image Min Height control is
	 * ALSO set to 170 in the page's config, because that writes per-widget CSS
	 * which loads after this file and would win the tie back.
	 */
	min-height: var(--otd-card-media);
	height: var(--otd-card-media);
	background-color: var(--ota-divider, rgba(0, 48, 56, 0.2));
}

.ota-dash-benefit .elementor-cta__bg {
	background-position: center;
	background-size: cover;
}

/*
 * The doubled skin class is the theme's, not decoration: it paints this element
 * white through `.elementor-cta--skin-classic.elementor-cta--skin-classic
 * .elementor-cta__content` at three classes, and the frame's card is one ash
 * surface from the image strip down. One more class is all it takes.
 */
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__content {
	display: flex;
	flex: 1 1 auto;
	flex-direction: column;
	/* Title, then the copy under it, then the action row on the bottom edge
	   (component/benefit). `space-between` would float the copy halfway down
	   a tall card; the row is pushed down on its own margin instead. */
	justify-content: flex-start;
	gap: 10px;
	min-height: 0;
	padding: var(--otd-card-pad) var(--otd-card-pad) 0;
	background: none;
	text-align: left;
}

.ota-dash-benefit .elementor-cta__title,
.ota-dash-benefit .elementor-cta__description {
	margin: 0;
	color: inherit;
	text-align: left;
}

/*
 * Body/Lead, the same size the event card's title takes. The class is tripled to
 * clear the theme's own `.elementor-cta__title.elementor-cta__title.elementor-cta__title`,
 * which pins every Call to Action title to the h3 step of its scale.
 */
.ota-dash-benefit .elementor-cta__title.elementor-cta__title.elementor-cta__title {
	font-size: var(--e-global-typography-lead-font-size, 1.375rem);
	font-weight: 400;
	line-height: 1;
}

.ota-dash-benefit .elementor-cta__description {
	padding-block-end: 8px;
	font-size: var(--e-global-typography-small-font-size, 0.9375rem);
	font-weight: 400;
	line-height: 1.4;
}

/*
 * The action row. The rule and the 48px height belong to the card, not to the
 * button, which is why they are on the wrapper: the frame's See More has no fill
 * and no border of its own.
 */
.ota-dash-benefit .elementor-cta__button-wrapper {
	display: flex;
	align-items: center;
	min-height: 48px;
	margin: auto 0 0;
	padding-block: 8px;
	border-block-start: 1px solid var(--ota-divider, rgba(0, 48, 56, 0.2));
}

/*
 * THE BUTTON, AND WHY THIS SELECTOR IS THIS LONG.
 *
 * The theme paints every Call to Action button ochre and pill-shaped through
 *
 *   .elementor-cta--skin-classic.elementor-cta--skin-classic
 *     .elementor-button.elementor-cta__button
 *
 * which is four classes, and it marks `border-radius` and `font-size`
 * `!important` on the way past. The frame's See More is none of those things: it
 * is a flat full-width row with the label at one edge and an arrow dot at the
 * other, the same footer the Events Block card draws. So the skin class is
 * claimed twice here as well, to reach five, and the two declarations the theme
 * flagged are answered in kind. Both `!important`s in this file are here, and
 * both answer one specific theme declaration rather than hedging.
 *
 * The theme rule lives in the compiled skin bundle, from
 * src/scss/modules/elementor/widgets/_call-to-action.scss.
 */
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button {
	position: relative;
	display: flex;
	align-items: center;
	justify-content: space-between;
	width: 100%;
	min-height: 48px;
	margin: 0;
	padding: 0;
	border: 0;
	border-radius: 0 !important;
	background: none;
	color: var(--ota-text, #003038);
	font-size: var(--e-global-typography-body-font-size, 1.0625rem) !important;
	font-weight: 700;
	line-height: 1;
	text-align: left;
	text-decoration: none;
}

/*
 * The arrow dot. ota-buttons.css draws this on its branch A and B buttons from
 * the `.ota-btn__inner` span's two pseudo-elements, and says in its own header
 * why branch C cannot: the Call to Action widget renders no inner row for that
 * span to be. Both of the button's own pseudo-elements are free, so the circle
 * is one and the glyph is the other, from the same 13px export and against the
 * same two roles the event card's dot uses.
 *
 * `order: 2` because a ::before is otherwise the first flex item, and the circle
 * belongs after the label. The glyph is absolute rather than a third item, since
 * a mask on the circle would clip the circle to the arrow's shape.
 */
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button::before {
	content: "";
	order: 2;
	flex: none;
	width: 30px;
	height: 30px;
	border-radius: 999px;
	background-color: var(--otd-dot-bg);
	transition: background-color 150ms ease;
}

.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button::after {
	content: "";
	position: absolute;
	inset-inline-end: 8.5px;
	inset-block-start: 50%;
	width: 13px;
	height: 13px;
	transform: translateY(-50%);
	background-color: var(--otd-dot-fg);
	transition: background-color 150ms ease;
	-webkit-mask: url("../icons/dashboard/arrow-right-sm.svg") no-repeat center / contain;
	mask: url("../icons/dashboard/arrow-right-sm.svg") no-repeat center / contain;
}

/* The theme paints a hover background on the same rule; the frame has none. */
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button:hover,
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button:focus,
.ota-dash-benefit.elementor-cta--skin-classic.elementor-cta--skin-classic .elementor-cta__button.elementor-cta__button:active {
	background: none;
	color: var(--ota-text, #003038);
}

/*
 * The sitewide card hover: a 2px ring against the Text Muted role, the title
 * underlined, and the dot inverting to the CTA roles.
 *
 * A PSEUDO-BORDER, AND AN OUTLINE WILL NOT DO. This was an `outline` with a
 * negative offset, which is tidy and which does not work: an outline is painted
 * in its own element's phase, so the card's children paint over it, and the
 * 170px image strip swallowed the top third of the ring. Only the part crossing
 * the transparent body was ever visible, which is the "outline doesn't cover
 * the whole card" that Bryce saw.
 *
 * `::after` on the card is painted after every descendant, which is the whole
 * reason assets/css/ota-news-block.css reaches for it. The other two reasons
 * given there hold as well: a real border resizes the card and shifts the row,
 * and an inset shadow paints under the image.
 */
.ota-dash-benefit .elementor-cta::after {
	content: "";
	position: absolute;
	inset: 0;
	z-index: 2;
	pointer-events: none;
	border: 2px solid transparent;
	border-radius: inherit;
	transition: border-color 150ms ease;
}

.ota-dash-benefit .elementor-cta:hover::after,
.ota-dash-benefit .elementor-cta:focus-within::after {
	border-color: var(--ota-text-muted, #005361);
}

.ota-dash-benefit .elementor-cta:hover,
.ota-dash-benefit .elementor-cta:focus-within {
	--otd-dot-bg: var(--ota-cta-bg, #003038);
	--otd-dot-fg: var(--ota-cta-text, #ffffff);
}

.ota-dash-benefit .elementor-cta:hover .elementor-cta__title,
.ota-dash-benefit .elementor-cta:focus-within .elementor-cta__title {
	text-decoration: underline;
}

/* --- 2c. Events ----------------------------------------------------------- */

/*
 * The Events Block, unchanged: same widget, same card and same query bridge as
 * the Special Interest Group pages. Only the band's container is retuned, and
 * every number below is one of the block's published tokens rather than a
 * selector reaching inside it.
 */
.ota-dash-events .ota-events {
	--oeb-max: none;
	--oeb-pad: 0;
	/* The frame's 29px between event cards, against 26 between benefit cards. */
	--oeb-gap: 29px;

	padding-block: 0;
	background-color: transparent;
}

.ota-dash-events .ota-events__inner {
	/* Heading row to cards: 1493 - 1441 on the artboard. */
	gap: 52px;
}

/* Heading/H4 here, where the Interest Group pages draw the same block at H2. */
.ota-dash-events .ota-events__title {
	color: var(--ota-text, #003038);
	font-size: var(--e-global-typography-h4-font-size, 1.5rem);
	line-height: var(--e-global-typography-h4-line-height, 1.08em);
	letter-spacing: var(--e-global-typography-h4-letter-spacing, -0.24px);
}

/*
 * The frame's header button carries no arrow badge where the block's default
 * does. ota-buttons.css exposes `ota-btn-arrow--none` for exactly this, but the
 * widget has no control to add it, so the modifier's effect is restated on the
 * one button in this band.
 */
.ota-dash-events .ota-events__head .ota-btn .ota-btn__inner::before,
.ota-dash-events .ota-events__head .ota-btn .ota-btn__inner::after {
	content: none;
}

.ota-dash-events .ota-events__head .ota-btn {
	padding-inline: 29.5px;
}

/* --- 2d. The Loop band ---------------------------------------------------- */

/*
 * The same CTA Banner widget the Interest Group pages use for their Loop band,
 * with the same eyebrow, heading and body. The one thing the frame draws
 * differently is the container: on a group page the band is a stretched
 * full-bleed section, and on the dashboard it is a rounded card inside the
 * content column.
 */
.ota-dash-loop .ota-cta {
	/*
	 * The band's own published tokens, not padding added on top of them. Its
	 * `--ocb-pad-block` is already 103px and its `--ocb-content-max` 681px, which
	 * are the full-bleed measurements from the Home page frame; padding the inner
	 * as well simply added to them and the band came out 200px too tall.
	 */
	--ocb-pad-block: 73px;
	/*
	 * The measure is deliberately NOT set to the frame's 495px. The frame draws
	 * "Connect with your group in Loop" on one line at that width; the same
	 * string in the face the site actually serves needs about 630, so copying the
	 * number would buy the frame's measure at the cost of the frame's heading.
	 * The widget's own 681 default is what the Interest Group pages give this
	 * band, it keeps the heading on one line, and it puts the body on the frame's
	 * two.
	 */
	--ocb-max: none;
	--ocb-pad: 84.5px;

	overflow: hidden;
	/* spacing/24 in the frame, where every other card takes radius/md. */
	border-radius: 24px;
}

/*
 * The frame's button here is the Ochre variant. The CTA Banner widget hardcodes
 * `ota-btn ota-btn--primary` on its markup and offers no colour control, so the
 * modifier class cannot be added from the editor. What `ota-btn-colour--ochre`
 * does in assets/css/ota-buttons.css is set exactly these two tokens, and every
 * other part of the button — fill, label, badge and glyph — derives from them,
 * hover included. So the modifier's effect is reached by setting the same two,
 * rather than by restating any paint.
 */
.ota-dash-loop .ota-cta__actions .ota-btn--primary {
	--ob-fill: var(--ota-ochre-button, #f04c3a);
	--ob-on-fill: var(--ota-ochre-button-text, #000000);
}

/* ==========================================================================
   3. Narrow screens
   ========================================================================== */

/*
 * The frame is drawn at 1440 only. Below the theme's own expanded breakpoint the
 * rail becomes the theme's slide-out panel and stops being a rail, so the width
 * set above is released rather than fought.
 */
@media (max-width: 1199px) {
	body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header.agendtheme-dashboard-header {
		width: auto;
	}
}

@media (max-width: 782px) {
	body.theme-agend--account-is-dashboard {
		--otd-gutter: 20px;
	}

	.ota-dash + .ota-dash.elementor-section {
		margin-block-start: 40px;
	}

	/*
	 * On the wrap, not the card: the card's own padding is zeroed above (the
	 * column is the card), and re-padding it here would stack 24px inside the
	 * wrap's 32/44 instead of replacing them.
	 */
	.ota-dash-cards.elementor-section > .elementor-container > .ota-dash-membership.elementor-column > .elementor-widget-wrap {
		padding: 24px;
	}

	.ota-dash-loop .ota-cta__inner {
		padding-block: 40px;
		padding-inline: 24px;
	}
}

/* --- Form fields ------------------------------------------------------------ */

/*
 * The dashboard's pill fields moved to assets/css/ota-form-fields.css on
 * 11 Sep 2026, because the checkout needs the same treatment and cannot carry
 * this file's body class (Teamwork 49444942). Form_Fields loads that file on
 * both. Nothing about the dashboard's result changed in the move.
 */

/* --- The rail's sub-menus: accordion, not fly-out --------------------------- */

/*
 * Teamwork 49444919. The theme opens a parent row's children (My Account's
 * My Details, Addresses, Marketing Preferences...) as a panel floated beside
 * the rail on hover, `top: 0; left: calc(100% + 5px)`, and the fly-out rules
 * earlier in this file restyle that panel. The client asked for the accordion
 * pattern instead: click the row, the children drop down inside the rail
 * indented under it, click again to fold them away.
 *
 * The state is `is-open` on the parent <li>, set on the server for a first
 * paint that is already right (Dashboard::rail_item_classes()) and flipped by
 * assets/js/ota-dashboard-rail.js on click. Hover and focus no longer open
 * anything: a member who mouses down the rail should not have a group spring
 * open under the pointer, and focus opening it would make tabbing past My
 * Account unfold seven rows.
 *
 * Specificity: the theme positions the panel at (2,3,4) with `!important`, so
 * the body class takes these to (2,4,4) and matches the `!important`. The
 * fly-out rules above in this file are (2,4,4) without `!important` and are
 * simply later in the cascade here, so they lose on order; the ones that
 * matter (visibility on hover and focus-within, the panel's padding, radius,
 * shadow and surface) are each answered below rather than left to chance.
 *
 * The caret the theme draws on a parent row (`a::after`, see the note on it
 * further up) turns to point down while the group is open, which is the only
 * visual the state needs; the children's indent says the rest.
 *
 * UNDER 992px THE THEME HAS ITS OWN ACCORDION, and it has to be switched off
 * here or the two fight and neither wins. Its mobile-menu.js appends a
 * `button.agendtheme-menu-toggle-button` inside every parent link, shown at
 * that breakpoint, whose click stops propagation (so the row's own handler
 * never runs) and animates the sub-menu through `--height` on a rule that
 * sets `height: var(--height); overflow: hidden` with `--height: 0px`. Left
 * alone, tapping the row set `is-open` but the group stayed 0px tall, and
 * tapping the chevron animated a group that was still `display: none`: only
 * both taps together showed the children (raised in review on PR #25). So
 * the open rule below pins `height: auto` over the theme's variable, and
 * the theme's button is hidden in the rail at every width, leaving the row
 * as the one control on phone and desktop alike.
 */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu {
	position: static !important;
	top: auto !important;
	left: auto !important;
	visibility: visible;
	opacity: 1;
	/* The theme animates the fly-out in from scale(.95) on hover; static in the
	   rail, that read as the list zooming under the pointer. */
	transform: none !important;
	transition: none !important;
	margin: 4px 0 8px;
	padding: 0 0 0 44px;
	border-radius: 0;
	background-color: transparent;
	box-shadow: none;
}

/*
 * CLOSED MEANS HIDDEN ONLY WHEN SOMETHING CAN OPEN IT. `html.ota-rail-js` is
 * set from <head> by Dashboard::mark_rail_scripted() when the rail script
 * will run. Without it (scripts blocked, script failed to load) no group is
 * ever hidden, so every page in the rail stays reachable; the accordion is an
 * enhancement, not the only way in. Hover and focus-within are named so the
 * fly-out rules above cannot reopen a closed group.
 */
html.ota-rail-js body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu,
html.ota-rail-js body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:hover > ul.sub-menu,
html.ota-rail-js body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li:focus-within > ul.sub-menu {
	display: none;
}

html.ota-rail-js body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.is-open > ul.sub-menu {
	display: block;
	height: auto !important;
	overflow: visible;
}

/* The theme's mobile chevron button, injected into every parent link: the row
   itself is the control here, so the second caret is not drawn. */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.menu-item-has-children > a > .agendtheme-menu-toggle-button {
	display: none !important;
}

/* The little pointer the fly-out drew off its leading edge has no panel to point from. */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li ul.sub-menu::before {
	display: none !important;
}

/* Children read as rows of the rail, one step in. */
body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li > ul.sub-menu > li > a {
	padding: 8px 16px;
	white-space: normal;
}

/* The caret: right while closed, down while open. The theme draws it as a
   down-pointing triangle from borders on `a::after` and leaves it that way;
   the fly-out rules earlier in this file kept `transform: none`. Closed now
   turns it a quarter to the right, the disclosure convention, and open lets
   it fall back to the theme's own downward triangle. */
html.ota-rail-js body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.menu-item-has-children:not(.is-open):not(.current-menu-item):not(.is-active) > a::after {
	transform: rotate(-90deg);
}

body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.menu-item-has-children.is-open:not(.current-menu-item):not(.is-active) > a::after {
	transform: none;
}

/*
 * The 300px rail is a desktop measure. Under 992px the theme turns the same
 * header into its full-width mobile menu, and the fixed width was still on it,
 * so the menu opened as a narrow column down the middle of the phone (Bryce,
 * 3 Sep 2026, on the first round of PR #25). Released here; the theme's own
 * condensed layout sizes it.
 */
@media (max-width: 991.98px) {
	/* The theme's own values for this header at this width (`_chrome-dashboard.scss`
	   line 108): it positions the header absolutely here, so `auto` would shrink
	   it to its content, which is the 220px column seen on the first attempt. */
	body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header.agendtheme-dashboard-header {
		width: 100vw;
		max-width: 100%;
	}

	/*
	 * The theme only draws a parent row's caret (`a::after`) from 992px up; below
	 * that its indicator was the chevron button that mobile-menu.js injects, which
	 * this file hides so the row is the one control. Without either, My Account
	 * gave no sign it opens. The theme's own triangle is redrawn here at the
	 * phone width, and the rotate rules above then apply to it unchanged: right
	 * while closed, down while open.
	 */
	body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-inner .agendtheme-header-navigation .agendtheme-header-navigation-wrap ul li.menu-item-has-children > a::after {
		content: "";
		display: inline-block;
		margin-left: auto;
		border: 0.25rem solid transparent;
		border-top-color: currentcolor;
		border-bottom: 0;
	}

	/*
	 * The open/close glyphs in the phone header. The theme paints the SVGs from
	 * the header link colour, which the page's colour theme resolves to Ash on
	 * this site: a cream X on the white panel (Bryce, 3 Sep 2026). The rail's
	 * own text colour, same as every row beside it.
	 */
	body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-navigation-toggle .agendtheme-icon-button,
	body.theme-agend--account-is-dashboard #agendtheme-dashboard #agendtheme-header .agendtheme-header-navigation-toggle .agendtheme-icon-button svg {
		color: var(--otd-text);
	}
}

.lost_reset_password.lost_reset_password {
	margin: 0;
	max-width: 430px;
	padding: 0;
}
