/* ============================================================
   26-global.css — site-wide rules that must hold everywhere
   ------------------------------------------------------------
   Everything in here is deliberately UNSCOPED. The earlier
   files in this directory each solved one template, which is
   why the search results page, the cart and the product pages
   fell outside the design: the stylesheets load on every page,
   but their selectors were keyed to one body class at a time.

   If a rule belongs to the whole site, it belongs in this file
   and nowhere else.
   ============================================================ */

/* Tokens are NOT defined here. css/00-tokens.css is the only file that
   declares a --fb-* value; this file reads them like every other.

   One token was declared here and had to go: `--awb-color1: #E8ECF4`, an
   attempt to dim Avada's palette slot 1 site-wide. It never took effect --
   Avada's dynamic CSS declares the same custom property on the same :root
   selector and is enqueued AFTER every child stylesheet, so it won on
   source order and the computed value stayed rgba(255,255,255,1). Our own
   rules now read --fb-text instead of borrowing Avada's slot, which is
   both what they meant and immune to that ordering. */

/* ---- 1. the boxed layout applies to EVERY template ------------------
   Avada's `layout = boxed` puts `layout-boxed-mode` on the body on every
   page -- verified -- but #wrapper kept `max-width: none` on the search
   results template, so search fell out of the 1140px box entirely while
   every other page stayed inside it. Header, content and footer were all
   1440 wide with a 10px horizontal overflow.

   This is the rule the rest of the site was already getting from Avada;
   stating it here makes it true for templates we have not looked at,
   including archives, 404 and anything a plugin adds later. */
body.layout-boxed-mode #wrapper {
	max-width: 1140px !important;
	margin-left: auto !important;
	margin-right: auto !important;
}

/* Gutenberg's wide/full alignments are measured against the viewport, not
   our box, so a block using them escapes the layout. The WooCommerce cart
   is a block (`wp-block-woocommerce-cart alignwide`) and rendered 1152px
   wide inside a 1080px row -- its contents hung 36px past the edge. */
#main .alignwide,
#main .alignfull {
	max-width: 100% !important;
	margin-left: auto !important;
	margin-right: auto !important;
}

/* ---- 2. form controls, everywhere ----------------------------------
   White text on a white field. Measured contrast 1.0 on the variation
   selects of both products, on the Name Your Price input, and on the
   search field: literally invisible until selected.

   Scoped to nothing, because the next form will be one we did not write
   -- a Woo variation dropdown, a checkout field, a plugin's settings
   form on the front end. `option` is styled too: a native dropdown list
   paints its own popup, and on Windows and Linux that popup inherits
   these colours rather than the field's. */
#main select,
#main textarea,
#main input[type="text"],
#main input[type="search"],
#main input[type="email"],
#main input[type="url"],
#main input[type="tel"],
#main input[type="number"],
#main input[type="password"],
#main input[type="date"],
.fusion-footer select,
.fusion-footer input[type="text"],
.fusion-footer input[type="email"] {
	background-color: var(--awb-color8) !important;
	color: var(--fb-text) !important;
	border: 1px solid var(--awb-color3) !important;
	border-radius: var(--fb-radius-sm) !important;
}
/* The native dropdown arrow is drawn by the platform and stayed white on a
   dark field, which read as a stray mark rather than a control. `appearance:
   none` removes it, so one is supplied here in the muted text colour -- as an
   inline SVG data URI, because an external asset for a 10px chevron is a
   request we would pay on every page. */
#main select,
.fusion-footer select {
	-webkit-appearance: none;
	-moz-appearance: none;
	appearance: none;
	padding-right: 2.2em !important;
	background-image: url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='8' viewBox='0 0 12 8'%3E%3Cpath d='M1 1l5 5 5-5' fill='none' stroke='%239AA3BA' stroke-width='1.8' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E") !important;
	background-repeat: no-repeat !important;
	background-position: right .85em center !important;
	background-size: 12px 8px !important;
}
#main select::-ms-expand {
	display: none;
}

#main select option,
.fusion-footer select option {
	background-color: var(--awb-color8) !important;
	color: var(--fb-text) !important;
}
#main select:focus,
#main textarea:focus,
#main input:focus {
	border-color: var(--awb-color4) !important;
	outline: 2px solid hsla(var(--awb-color4-h), var(--awb-color4-s), var(--awb-color4-l), calc(var(--awb-color4-a) - 60%)) !important;
	outline-offset: 1px;
}
#main ::placeholder {
	color: var(--awb-color6) !important;
	opacity: 1;
}

/* ---- 3. cards: one border, sharper corners -------------------------
   14-dark-contrast.css gave every card three grey edges and one violet
   one, turning cyan on hover. A single accent edge is a deliberate
   device when it is the only one on the page; on a grid of 13 cards it
   reads as a rendering fault. The border is uniform now, and the hover
   lifts all four edges rather than one. */
.ppe-series-card {
	border-color: var(--awb-color3) !important;
	border-left-color: var(--awb-color3) !important;
}
.ppe-series-card:hover {
	border-color: var(--awb-color5) !important;
	border-left-color: var(--awb-color5) !important;
}

.ppe-series-card,
.ppe-g-card,
.ppe-g-card > a,
.fb-guest,
.fb-epnav-slot,
.ppe-row,
.fb-members,
.fb-note,
.fb-card,
.ppe-locked,
.fb-footer-nav,
#main .shop_table,
#main .woocommerce-info,
#main .woocommerce-message,
#main .woocommerce-error {
	border-radius: var(--fb-radius) !important;
}

/* Square art should meet the card edge squarely. The guest monogram is
   deliberately NOT in this list: it is a circle by design, and sweeping it
   in here squared every avatar on the home page. */
.fb-series-card-art,
.fb-series-card-img,
.ppe-sq,
.ppe-sq img {
	border-radius: 0 !important;
}
/* ...except where the art IS the shape, like a round avatar. */
.ppe-g-av,
.ppe-g-av img,
.fb-guest-mono,
.ppe-g-ini {
	border-radius: 50% !important;
}

/* ---- 4. centring -- nothing to do ---------------------------------
   Checked rather than assumed: on the home page and /join/, every block
   with `text-align: center` already centres its contents, and the two
   hero buttons sit symmetrically as a pair (317px of gap on each side).
   The rules that were here targeted .fb-price-card / .fb-tier /
   .fb-cta-card / .fb-card / .is-centered -- none of which appear in any
   published page. Dead selectors removed rather than left looking load
   bearing. If a card does drift off centre, fix it where that card is
   defined, not with a speculative global.
   -------------------------------------------------------------------- */

/* ---- 5. the ghost button has to be visible before it is hovered ----
   `.fb-btn-ghost` sat at a dim border with dim text, so "Listen free
   first" on /join/ read as disabled until the pointer touched it. The
   resting state now carries the same weight as the primary button's
   outline; hover still brightens to the aurora cyan. */
.fb-btn-ghost,
.fb-btn-quiet {
	/* width and style as well as colour: .fb-btn-quiet used to inherit
	   `border: 1px solid` from a second definition in 15-home.css, so
	   stating only the colour here left it borderless the moment that
	   duplicate was removed. A rule that owns a property owns all of it. */
	border: 1px solid var(--awb-color6) !important;
	color: var(--fb-text) !important;
	background: hsla(var(--awb-color1-h), var(--awb-color1-s), var(--awb-color1-l), calc(var(--awb-color1-a) - 96%)) !important;
}
.fb-btn-ghost:hover,
.fb-btn-quiet:hover {
	border-color: var(--awb-color5) !important;
	color: var(--awb-color5) !important;
}

/* ---- 6. the content panel is glass ---------------------------------
   Ricky 2026-11-19: the body section inside the boxed layout should be
   "slightly opaque... so that if an animated background is placed behind
   it you can barely see the animation", and its contents must not
   inherit that.

   This is a translucent BACKGROUND plus a backdrop-filter, never
   `opacity`: opacity applies to the element and everything inside it,
   which would fade the text and images with it. Background alpha does
   not cascade, so the panel is glass and its contents stay solid.

   #wrapper is cleared so the backdrop being blurred is the page itself
   rather than the wrapper's own flat fill; the header and footer keep
   their colour explicitly so they look exactly as they did. */
body.layout-boxed-mode #wrapper {
	background-color: transparent !important;
}
#main {
	background-color: hsla(var(--awb-color8-h), var(--awb-color8-s), var(--awb-color8-l), calc(var(--awb-color8-a) - 14%)) !important;
	-webkit-backdrop-filter: blur(16px) saturate(118%);
	backdrop-filter: blur(16px) saturate(118%);
}
.fusion-header,
.fusion-secondary-main-menu,
.fusion-footer-copyright-area {
	background-color: var(--awb-color8) !important;
}

/* ---- 7. the accent notes keep their colour, lose the odd edge --------
   Ricky 2026-11-19, on the "A tip does not include access to anything."
   box: "I like the boxed note... and I like the color, but it also has
   that weird card border that looks bad."

   Same fault as the cards: three grey edges and one thick coloured one.
   The colour he likes is kept and carried all the way round at 1px, so
   the box still reads as a note rather than a panel. */
.fb-note,
.fb-members {
	border: 1px solid var(--awb-color5) !important;
}
.fb-note-offer {
	border-color: var(--awb-color4) !important;
}

/* ---- 8. form buttons are the site's buttons ------------------------
   Fluent Forms ships its own blue (#1A7EFB) with white text, which is
   the only thing on the site not wearing the palette. Styled here
   rather than in the plugin's settings so it cannot be lost when the
   form is rebuilt, and so every future form inherits it. */
.ff-btn-submit,
.ff-btn.ff-btn-submit,
.fluentform .ff-btn-submit,
#main input[type="submit"]:not(.fusion-search-submit),
#main button[type="submit"]:not(.fusion-search-submit) {
	background: var(--awb-color4) !important;
	border: 1px solid var(--awb-color4) !important;
	color: var(--fb-on-accent) !important;
	border-radius: var(--fb-radius) !important;
	font-weight: 600;
	letter-spacing: .02em;
}
.ff-btn-submit:hover,
.fluentform .ff-btn-submit:hover,
#main input[type="submit"]:not(.fusion-search-submit):hover,
#main button[type="submit"]:not(.fusion-search-submit):hover {
	background: var(--fb-violet-lit) !important;
	border-color: var(--fb-violet-lit) !important;
	color: var(--fb-ink-on-accent) !important;
}

/* ---- 9. admin-only notices wear the theme --------------------------
   Avada's "Shown only to administrators / Edit this content" badge is
   chrome no visitor sees, but Al previews the site logged in, so it is
   in the view we ask him to judge. Toned to the palette rather than
   hidden: hiding it would also hide the edit affordance he may want. */
/* The notice Ricky photographed is NOT Avada's -- it is the Newsletter
   plugin's, a bare <fieldset> with every colour written inline
   (newsletter/includes/module.php:1357: #ddd border, #eee fill, #777
   legend, #2d3748 text). Inline styles outrank a stylesheet, so these
   need !important; it is matched on the inline fill because the element
   carries no class of its own. Admin-only chrome, but Al previews the
   site logged in, so it is in the view we ask him to judge.
   Not reproducible on any public template as of 2026-11-19 -- the rule
   is written from the plugin source, not from a rendered page. */
#main fieldset[style*="background-color: #eee"] {
	border: 1px solid var(--awb-color3) !important;
	border-radius: var(--fb-radius) !important;
	background-color: var(--awb-color7) !important;
	font-family: inherit !important;
}
#main fieldset[style*="background-color: #eee"] > legend {
	background-color: var(--awb-color4) !important;
	color: var(--fb-on-accent) !important;
	border-radius: var(--fb-radius-sm) !important;
}
#main fieldset[style*="background-color: #eee"] p {
	color: var(--fb-text) !important;
}

.fusion-admin-only-notice,
.awb-admin-only,
.fusion-builder-live-editor-notice,
#main .fusion-admin-label {
	background: var(--awb-color7) !important;
	border: 1px dashed var(--awb-color3) !important;
	border-radius: var(--fb-radius-sm) !important;
	color: var(--awb-color6) !important;
	font-size: .8rem !important;
}

/* ---- 10. episode titles are not truncated --------------------------
   Measured on the home page: `.ppe-row-title` was clipping 220px of
   "Game of Initiates — Origins of Tarot & Preservation of Ancient
   Lore". A title is the one thing in a listing row that must survive;
   the date, the series and the icons all have fixed tracks, so the
   title cell can grow instead. Two lines, then ellipsis -- a row that
   can grow without limit would break the grid's rhythm. */
.ppe-row-title {
	white-space: normal !important;
	overflow: hidden;
	display: -webkit-box;
	-webkit-box-orient: vertical;
	-webkit-line-clamp: 2;
	line-clamp: 2;
	text-overflow: ellipsis;
}
.ppe-series {
	white-space: normal !important;
	overflow: hidden;
	display: -webkit-box;
	-webkit-box-orient: vertical;
	-webkit-line-clamp: 2;
	line-clamp: 2;
}
.ppe-row-link {
	align-items: center;
}

/* ---- 11. the two home-page widgets sit side by side ----------------
   Ricky 2026-11-19: "Alongside the newsletter widget on the front page,
   put a social links widget with a 'follow us' call to action. These
   two widgets should be half width, so two-column layout on desktop."

   Equal columns rather than auto, so the two panels are the same width
   whatever their content, and the same height because the grid stretches
   them -- a taller newsletter form would otherwise leave the follow
   panel floating. */
.fb-widget-row {
	display: grid;
	grid-template-columns: 1fr 1fr;
	gap: 20px;
	align-items: stretch;
	margin: 0 0 10px;
}
.fb-widget-row > .fb-signup,
.fb-widget-row > .fb-follow {
	margin: 0;
	padding: 26px 28px;
	background: var(--awb-color7);
	border: 1px solid var(--awb-color3);
	border-radius: var(--fb-radius);
}
.fb-widget-row h2 {
	margin: 0 0 6px;
	font-size: 1.25rem;
}
.fb-widget-row > section > p {
	margin: 0 0 16px;
	color: var(--awb-color6);
	font-size: .95rem;
	line-height: 1.6;
}

/* Platform pills. Named rather than icon-only: four of the eleven are
   stored as "custom" in Avada with no icon glyph, so an icon row would
   have had holes in it. */
.fb-social-links {
	display: flex;
	flex-wrap: wrap;
	gap: 8px;
}
.fb-social-link {
	display: inline-flex;
	align-items: center;
	padding: 7px 14px;
	border: 1px solid var(--awb-color3);
	border-radius: var(--fb-radius-pill);
	background: var(--awb-color8);
	color: var(--fb-text) !important;
	font-size: .85rem;
	line-height: 1.2;
	text-decoration: none !important;
	transition: border-color .15s ease, color .15s ease;
}
.fb-social-link:hover {
	border-color: var(--awb-color5);
	color: var(--awb-color5) !important;
}

@media (max-width: 860px) {
	.fb-widget-row {
		grid-template-columns: 1fr;
	}
}

/* ---- 12. WooCommerce ink ------------------------------------------
   Woo and Avada colour prices and account navigation with the brand
   violet (--awb-color4). That is a fine accent on white and a poor one
   on near-black: measured 2.44 for the price on a product page and
   2.41 for the My Account menu, both under the 4.5 floor.

   The violet stays as the button and border colour; only type that has
   to be READ is moved to the text colour, with the aurora cyan kept for
   hover so links still feel like links. */
.woocommerce-Price-amount,
.woocommerce-Price-amount *,
.woocommerce-MyAccount-navigation a,
.woocommerce-MyAccount-content a,
#main .woocommerce a:not(.button):not(.fb-btn),
.nyp-input,
.wc-nyp-price,
.woocommerce ul.products li.product .price {
	color: var(--fb-text) !important;
}
.woocommerce-MyAccount-navigation a:hover,
.woocommerce-MyAccount-content a:hover,
#main .woocommerce a:not(.button):not(.fb-btn):hover {
	color: var(--awb-color5) !important;
}
.woocommerce-MyAccount-navigation li.is-active a {
	color: var(--awb-color5) !important;
	font-weight: 600;
}

/* ---- 13. the checkout quantity badge -------------------------------
   Ricky 2026-11-19: "The cart number blip that shows up over a product
   at checkout is white on gray, hard to see."

   Measured: colour rgb(215,221,234) on background rgb(215,221,234) --
   the badge was painting its digit in exactly its own background
   colour, a contrast ratio of 1.00. It inherited the site's text colour
   as its fill while Woo's block stylesheet set the same variable for
   the circle.

   Given a colour of its own: the brand violet with white on top, which
   is the same pairing the premium pill already uses elsewhere. */
.wc-block-components-order-summary-item__quantity {
	background: var(--awb-color4) !important;
	border: 1px solid var(--awb-color4) !important;
	color: var(--fb-on-accent) !important;
	font-weight: 600;
}
