/*
  Shared tokens for every code component.

  A site-level CSS *class* never reaches inside a shadow root, but a site-level
  *variable* does (CLAUDE.md section 2) - so this file is where the components
  meet the site's own design system. Each --na-* name below resolves to the real
  Webflow variable first and to the value from the Figma file only as a fallback,
  which means retuning a colour in the Designer moves every block with it, while
  the components still render correctly in the local gallery, in Figma-faithful
  isolation, and on any site that does not define these.

  The Webflow names are the ones the Designer emits for the "Semantic Colors"
  and "Base" collections of the Nebius Academy site; every fallback here was
  checked against the live value and matches it.
*/
/* Both selectors on purpose: the CLI rewrites `:root` to `:host` when it builds
   the shadow-DOM stylesheet (section 2), but the local gallery inlines this file
   as-is, where `:root` matches nothing and every token would silently fall back.
   Naming `:host` as well makes the gallery behave like the real thing. */
:host,
:host {
  --container-max-width: 1280px;

  /* Type. Webflow holds no font-family variables - the faces are set in the
     site's typography settings - so these are ours, with the project's own
     "Inter 28" first and metric-compatible Arial behind it. */
  --na-font-sans: "Inter 28", Arial, sans-serif;
  --na-font-display: "Inter Tight", "Inter 28", Arial, sans-serif;
  --na-font-serif: "Tiempos Text", Georgia, "Times New Roman", serif;

  /* Text */
  --na-content-primary-bold: var(--_semantic-colors---content--primary-bold, #14070f);
  --na-content-primary: var(--_semantic-colors---content--primary, rgba(20, 7, 15, 0.9));
  --na-content-secondary: var(--_semantic-colors---content--secondary, rgba(20, 7, 15, 0.7));
  --na-content-tertiary: var(--_semantic-colors---content--tertiary, rgba(20, 7, 15, 0.5));
  --na-content-inverse-primary-bold: var(--_semantic-colors---content--inverse-primary-bold, #f9f8f6);
  --na-content-inverse-primary: var(--_semantic-colors---content--inverse-primary, rgba(249, 248, 246, 0.9));
  --na-content-inverse-secondary: var(--_semantic-colors---content--inverse-secondary, rgba(249, 248, 246, 0.7));
  --na-content-inverse-tertiary: var(--_semantic-colors---content--inverse-tertiary, rgba(249, 248, 246, 0.5));

  /* Surfaces */
  --na-background-primary: var(--_semantic-colors---background--primary, #f3efe8);
  --na-background-secondary: var(--_semantic-colors---background--secondary, #f9f8f6);
  --na-background-inverse: var(--_semantic-colors---background--inverse, rgba(20, 7, 15, 0.95));
  --na-background-primary-hover-subtle: var(--_semantic-colors---background--primary-hover-subtle, #eae6dc);

  /* Borders */
  --na-border-primary: var(--_semantic-colors---border-stroke--black--primary, rgba(20, 7, 15, 0.2));
  --na-border-secondary: var(--_semantic-colors---border-stroke--black--secondary, rgba(20, 7, 15, 0.1));
  --na-border-inverse-primary: var(--_semantic-colors---border-stroke--white--primary, rgba(249, 248, 246, 0.7));
  --na-color-black-alpha-20-a: var(--black--alpha--20-a, rgba(20, 7, 15, 0.2));

  /* No counterpart in the site's collections, so these stay ours - but they are
     still variables, so a page can retune them.

     Two of them deliberately do NOT use the similarly named Webflow token:
     Background/primary-hover is #ab9c8f there, and primary-hover-subtle is the
     opaque #eae6dc. Both are meant for beige cards. Over the header's glass bar
     a hover has to be a transparent wash or it reads as a solid chip, which is
     what the two "ghost" names below are for. */
  --na-background-primary-subtle: #f3efe8;
  --na-background-white: #fff;
  --na-background-glass: rgba(255, 255, 255, 0.5);
  --na-background-primary-hover: rgba(20, 7, 15, 0.06);
  --na-background-ghost-hover: rgba(20, 7, 15, 0.06);
  --na-background-ghost-hover-subtle: rgba(20, 7, 15, 0.04);
  --na-color-white-alpha-70-a: rgba(255, 255, 255, 0.7);
  --na-color-white-alpha-50-a: rgba(255, 255, 255, 0.5);
  --na-color-white-alpha-40-a: rgba(255, 255, 255, 0.4);

  /* The Problem section's "Tint" stat card (Figma node 21245-5945): a solid
     lavender card with a black-fading-to-lavender figure. No counterpart in
     the site's collections, so this stays ours the way the block above does. */
  --na-background-tint-purple: #d3d3fa;
  --na-gradient-stat-fade: linear-gradient(90deg, rgba(20, 7, 15, 0.95) 0%, rgba(20, 7, 15, 0.95) 35%, rgba(211, 211, 250, 0.9) 100%);

  /* The gradient every *emphasis* italic run in a heading is clipped to
     (Figma node 21045-20, the Hero heading). Webflow has no gradient
     variables to bridge to (same reasoning as the fonts above), so this one
     is ours outright - defined once here and referenced by every section's
     .emphasis rule instead of repeating the five stops seven times. */
  --na-gradient-emphasis: linear-gradient(213deg, #b5a9ea 18%, #8873de 54%, #2e2e7d 75%, #43425b 95%);
}

/* The section's own padding is the 12px gutter Figma keeps at every width -
   the banner, not the page, is what carries the real padding. */
.DeE3KBe0bgHNLcXmoHiB {
  width: 100%;
  box-sizing: border-box;
  padding: var(--na-spacing-56, 56px) 12px;
}

.sbonuXjB4fdJ2LwXfVlV {
  position: relative;
  box-sizing: border-box;
  width: 100%;
  max-width: var(--container-max-width, 1280px);
  margin-inline: auto;
  padding: var(--na-spacing-24, 24px);
  overflow: hidden;
  border-radius: var(--na-border-radius-24, 24px);
  /* Stands in for the artwork until one is uploaded: the same green-to-violet
     sweep Figma's blurred render resolves to, so an empty Artwork field still
     reads as the designed banner rather than as a grey box. */
  background-image: linear-gradient(101deg, #17240f 0%, #2f4a20 22%, #6d8f4c 48%, #7fa3ba 72%, #b9bdf3 100%);
  background-color: var(--na-background-inverse, rgba(20, 7, 15, 0.95));
}

.os5jfC_zhrNCZNBqS6wt {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
}

.FntOKCbbRGwtjypwoX7Q {
  position: relative;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--na-spacing-24, 24px);
  width: 100%;
}

.Qu0q7tFs7IePYgBvRssg {
  margin: 0;
  max-width: 760px;
  font-family: var(--na-font-display, "Inter Tight", "Inter 28", Arial, sans-serif);
  font-weight: 400;
  font-size: 34px;
  line-height: 38px;
  text-align: center;
  /* No `text-wrap: balance` here, unlike the other sections: Figma fills the
     first line right out to the 760px measure and lets "for your workforce"
     drop, and balancing pulls "baseline" down with it instead. */
  overflow-wrap: break-word;
  color: var(--na-content-inverse-primary, rgba(249, 248, 246, 0.9));
}

/* The one .emphasis in the library that is NOT clipped to the purple gradient
   (CLAUDE.md section 12): those stops are tuned for dark type on a light page
   and go muddy on this banner, and Figma draws the italic run here in the same
   light ink as the rest of the line. */
.TeR6IEmV2m29Vmei9vvS {
  font-family: var(--na-font-serif, "Tiempos Text", Georgia, "Times New Roman", serif);
  font-style: italic;
  color: inherit;
}

.fZOduKncP1lhLBho1Uzy {
  display: inline;
}

.WWNXL3ujzK5CH3NgCEw_ {
  margin: 0;
  max-width: 560px;
  font-family: var(--na-font-sans, "Inter 28", Arial, sans-serif);
  font-weight: 400;
  font-size: 16px;
  line-height: 24px;
  letter-spacing: -0.2px;
  text-align: center;
  color: var(--na-content-inverse-secondary, rgba(249, 248, 246, 0.7));
}

.WWNXL3ujzK5CH3NgCEw_ p {
  margin: 0;
}

.WWNXL3ujzK5CH3NgCEw_ p + p {
  margin-top: 0.75em;
}

/* Full-width buttons on a phone, shrink-to-fit from tablet up. */
.ZJ84qy15mTh60Kx0PwKW {
  display: flex;
  flex-direction: column;
  gap: var(--na-spacing-16, 16px);
  width: 100%;
}

.H4umSz9ZKCbrb8bDoMpr {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  box-sizing: border-box;
  height: 52px;
  padding: var(--na-spacing-12, 12px) 24px;
  border: none;
  border-radius: var(--na-border-radius-14, 14px);
  background: var(--na-background-primary, #f3efe8);
  font-family: var(--na-font-sans, "Inter 28", Arial, sans-serif);
  font-weight: 400;
  font-size: 16px;
  line-height: 24px;
  letter-spacing: -0.2px;
  color: var(--na-content-primary, rgba(20, 7, 15, 0.9));
  text-decoration: none;
  white-space: nowrap;
  cursor: pointer;
}

@media (min-width: 768px) {
  .sbonuXjB4fdJ2LwXfVlV {
    padding: var(--na-spacing-80, 96px) var(--na-spacing-80, 80px);
  }

  .Qu0q7tFs7IePYgBvRssg {
    font-size: 54px;
    line-height: 58px;
  }

  .ZJ84qy15mTh60Kx0PwKW {
    flex-direction: row;
    justify-content: center;
    width: auto;
  }
}

@media (min-width: 1200px) {
  .DeE3KBe0bgHNLcXmoHiB {
    padding: var(--na-spacing-80, 96px) 12px;
  }

  .Qu0q7tFs7IePYgBvRssg {
    font-size: 62px;
    line-height: 66px;
  }
}

/* Three identical tiles stacked - the site's own recipe (see NoiseOverlay.tsx),
   not something to simplify to one: stacking the same tile compounds the
   blend into visible grain, where a single layer reads as almost nothing. */
/* No z-index here on purpose. A positioned element with z-index:0/auto still
   paints after in-flow, non-positioned content in the same stacking context
   (CSS 2.1 Appendix E) - so as long as the real content sitting over this
   overlay is itself `position: relative` (as every card content wrapper in
   this project already is) and comes later in the DOM, tree order alone keeps
   the grain under the copy. A fixed z-index here would instead force the
   overlay in front of any caller that isn't giving its content a *higher*
   one, which is one more number every caller would have to know to match. */
.VjIzBc5zC6slMhcdqEWS {
  position: absolute;
  inset: 0;
  overflow: hidden;
  pointer-events: none;
}

.YqJvn0ptuHfTjC_wXJLP {
  position: absolute;
  inset: 0;
  background-color: var(--na-background-secondary, #f9f8f6);
  background-image: var(--noise-url);
  background-size: var(--noise-size, 256px);
  mix-blend-mode: color-burn;
}