/*
 * LeadX Security — new home page
 * ─────────────────────────────────────────────────────────────────────────────
 *
 * HOW THIS FILE IS MEANT TO BE EDITED
 *
 * Everything a design decides — colour, type size, spacing, radius — is a token
 * in :root below, and nothing further down this file hardcodes one. So matching
 * Figma means editing the :root block and nothing else; the layout underneath
 * already knows what to do with whatever the values turn out to be.
 *
 * Tokens tagged FIGMA carry a value read off the comp. Tokens tagged GUESS were
 * measured from a screenshot and still need confirming.
 *
 * The rules below :root are structure — flex, stacking, responsive behaviour.
 * Those are engineering decisions rather than design ones, and should not need
 * touching to match a comp.
 */

/* ═══════════════════════════════════════════════════════════════════════════
   FONTS
   Product Sans, self-hosted to match LeadXForms. Three weights only — the full
   family is twelve files and 1.1 MB, and nothing on this page sets the other
   nine. font-display:swap so text paints in the fallback immediately rather
   than holding the hero blank while a 90 KB file arrives.
   ═══════════════════════════════════════════════════════════════════════════ */

@font-face {
  font-family: 'Product Sans';
  src: url('../fonts/product-sans/ProductSans-Regular.ttf') format('truetype');
  font-weight: 400;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: 'Product Sans';
  src: url('../fonts/product-sans/ProductSans-Medium.ttf') format('truetype');
  font-weight: 500;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: 'Product Sans';
  src: url('../fonts/product-sans/ProductSans-Bold.ttf') format('truetype');
  font-weight: 700;
  font-style: normal;
  font-display: swap;
}

/* ═══════════════════════════════════════════════════════════════════════════
   TOKENS — this is the block to edit
   ═══════════════════════════════════════════════════════════════════════════ */

:root {

  /* ── Type families ──────────────────────────────────────────────────────
     The comp uses three, the same three LeadXForms does. Which one applies is
     decided per element rather than per level, so they are named for the job
     they do here rather than a hierarchy they do not follow:

       --font         Product Sans — headline and both lede paragraphs, and the
                      page default, which the carried-over nav inherits
       --font-ui      Poppins      — eyebrow and the checked claims
       --font-accent  Albert Sans  — the text CTA and the micro line
       --font-dash    Inter        — the dashboard mock only, which imitates a
                      real product UI rather than this page's own voice

     The fallback stacks matter more than they look: font-display is swap, so
     these are what a visitor actually reads for the first few hundred
     milliseconds, and they are chosen to be geometric rather than whatever the
     platform default happens to be. */
  --font: 'Product Sans', 'Poppins', system-ui, -apple-system, 'Segoe UI', Roboto, Arial, sans-serif;
  --font-ui: 'Poppins', 'Product Sans', system-ui, -apple-system, 'Segoe UI', Roboto, Arial, sans-serif;

  --fw-regular: 400;
  --fw-semibold: 600;
  --fw-bold: 700;
  /* FIGMA — 110% */
  --text-heading: #000;
  /* FIGMA — 150% */

  /* ── Colour ───────────────────────────────────────────────────────────── */
  --text: #151515;
  /* FIGMA */

  --green: #008744;

  /* ── Hero background wash ───────────────────────────────────────────────
     The wash itself is assets/images/hero-gradient.webp, applied in .hero-bg. Only the
     base colour is a token now — the three stop colours that used to build it
     by hand are gone along with the gradients they fed. */
  --wash-base: #FFFFFF;

  /* ── Layout ───────────────────────────────────────────────────────────── */
  /* The comp's own content width. Nothing reads it any more — .container is
     Bootstrap's, to match the brand — but it is the number every Figma frame
     is drawn against, so it is worth being able to look up. */

  /* Height of the fixed header. site.js overwrites this on load and on resize
     with the real measured height, so the hero always clears it — the value
     here is only what applies for the moment before that script runs. */
  --header-h: 88px;

  --engine-accent: #17A05A;
  /* FIGMA */

  /* A pale wash across the copy cell, fading out toward the rule in the
     middle of the row. Turned around on mirrored rows. */

  /* site.js overwrites this the first time the bar sticks; the fallback only
     covers the frames before any scroll has happened. */
  --header-h-sticky: 74px;
  /* GUESS */

  /*
   * One constant page gutter below 992 — see the fluid-container block.
   *
   * 10, not 24. The Engine section was carrying its own 10px while every other
   * band sat at 24, and a page whose margin changes from section to section
   * reads as unfinished however carefully each section is built. This is the
   * number the whole page shares now, and the Engine's special case is gone
   * (see THE ENGINE, UNPINNED).
   *
   * One value to change if 10 turns out to be too tight for body copy.
   */
  --page-gutter: 15px;
  /* GUESS */

  /* ── Header and footer ────────────────────────────────────────────────── */

  /* Every value here is LeadXForms', copied so the two products wear the same
     chrome. They are tokens so this file can read them, not so they can be
     tuned — changing one breaks the match, which is the point of them. */
  --hf-ink: #151823;
  /* LEADXFORMS — --lxf-dark */
  --hf-ink-hover: #44464F;
  /* LEADXFORMS */
  --hf-green-hover: #339F69;
  /* LEADXFORMS */
  --hf-body: #404040;
  /* LEADXFORMS — footer copy and links */
  --hf-line: #E5E5E5;
  /* LEADXFORMS — the footer's top rule */

  --hf-bar-pad: 20px;
  /* LEADXFORMS */
  --hf-bar-pad-sticky: 12px;
  /* LEADXFORMS */
  --hf-logo-w: 200px;
  /* LEADXFORMS */
  --hf-logo-w-sticky: 180px;
  /* LEADXFORMS */
  --hf-footer-logo-w: 224px;
  /* LEADXFORMS */
  /*
   * 38, not LeadXForms' 25. That 25 was set for a bar of six items whose labels
   * were single words — Home, Features, Templates, Integrations, Resources,
   * Pricing. This bar carries "How It Works" and "AI Guardian", two-and
   * three-word labels, and at 25px the gaps between items read as narrower than
   * the spaces inside them, so the bar looked like one long string rather than
   * six things. 38 puts the gap comfortably wider than a word space at
   * --fs-hf-menu and the items separate again.
   */
  --hf-menu-gap: 38px;
  --hf-btn-h: 50px;
  /* The button component's own cost, tokenised so the phone block can cut it.
     --hf-btn-icon-pad-r reserves the arrow disc: 6px inset + the disc + clearance. */
  --hf-btn-pad-y: 6px;
  --hf-btn-pad-x: 24px;
  --hf-btn-disc-w: 50px;
  --hf-btn-icon-pad-r: 65px;
  /* LEADXFORMS */

  --fs-hf-menu: 17px;
  /* LEADXFORMS */
  /* LeadXForms' .button sets no font-size at all — it inherits body's 18px.
     Stated here instead of relying on a body size this page does not set: at
     the browser default of 16px the pills came out about 30px narrower each
     and the labels visibly smaller than the brand's. */
  --fs-hf-btn: 18px;
  /* LEADXFORMS — inherited from body there */
  --fs-hf-heading: 25px;
  /* LEADXFORMS — footer column headings */
  --fs-hf-body: 16px;
  /* LEADXFORMS */
  --fs-hf-small: 14px;
}

/* ═══════════════════════════════════════════════════════════════════════════
   BASE
   ═══════════════════════════════════════════════════════════════════════════ */

*,
*::before,
*::after {
  box-sizing: border-box;
}

html {
  -webkit-text-size-adjust: 100%;
}

body {
  margin: 0;
  font-family: var(--font);
  font-weight: var(--fw-regular);
  color: var(--text);
  background: var(--wash-base);
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
}

img {
  max-width: 100%;
  height: auto;
  display: block;
}

a {
  color: inherit;
}

/* Never remove a focus ring without replacing it — keyboard users navigate by
   it. :focus-visible shows it for keyboard traversal and hides it for a mouse
   click, which is the behaviour that made people remove the outline in the
   first place. */
:where(a, button):focus-visible {
  outline: 2px solid var(--green);
  outline-offset: 3px;
  border-radius: 4px;
}

/* ═══════════════════════════════════════════════════════════════════════════
   HEADER AND FOOTER
   Ported from LeadXForms rather than designed here, so the two products wear
   the same chrome. Every measurement below is that stylesheet's — the bar's
   20px band, the 200px logo, the menu's 25px gap and 17px links, the pill
   buttons at 50px tall with their 2px border and 50px radius.

   The values are inlined as tokens rather than left as literals so the rest of
   this file can read them, but they are not open design decisions: change one
   and this page stops matching LeadXForms, which is the whole point of it.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ── The bar ─────────────────────────────────────────────────────────────── */

/*
 * Transparent at the top of the page, solid once it scrolls — the hero's wash
 * runs under the bar rather than stopping at it, and the bar only becomes a
 * strip when there is content that would otherwise pass behind it.
 *
 * style.css says background:#fff here; MasterLayout.vue overrides it to
 * transparent, and the override is what actually renders. Measuring the live
 * header confirms it — the bar reads #EAF5EF there, which is that page's own
 * hero wash showing through, not a colour the header sets.
 *
 * Absolute, not fixed, until .header-sticky makes it fixed. site.js adds that.
 */
.main-header {
  background: transparent;
  padding: var(--hf-bar-pad) 0;
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  z-index: 999;
  transition: all .3s ease-in-out;
}

.header-sticky {
  position: fixed;
  background: #fff;
  box-shadow: 0 2px 20px rgba(1, 41, 112, .08);
  padding: var(--hf-bar-pad-sticky) 0;
}

/*
 * Where a jump to a section stops.
 *
 * section[id], not the list of seven this used to name. The list was the nav's
 * own targets, and it had already fallen behind: the dashboard's "see it in
 * action" link points at #product-in-action, which was not on it, so that one
 * jump still parked the heading under the bar. An attribute selector cannot
 * drift — a section that gains an id gains the offset with it, and <body>#top is
 * not a section so it is still excluded for free.
 *
 * assets/js/site.js carries no anchor handler, so the browser's native jump does this
 * and it parks the section's top edge at the very top of the viewport — which is
 * behind the bar above, because .header-sticky is fixed. Measured before this
 * rule, with the sticky bar ending at 74px, four of the six targets put their
 * eyebrow — the section's actual first line — at 50px:
 *
 *   #how-it-works              "How Protection Works, In Real Time"   50px
 *   #features                  "Feature Deep-Dives"                   50px
 *   #live-threat-intelligence  "Live Threat Intelligence"             50px
 *   #plans                     "Plans"                                50px
 *
 * Each one was sliced by the bar, so a reader clicking Features landed on a
 * section that appeared to start at its heading with its label missing.
 *
 * This was nearly dismissed on the grounds that the headings cleared the bar at
 * 87px and so nothing was wrong. They did — but the heading is not the top of
 * the section, the eyebrow above it is, and measuring the h2 is what hid it.
 *
 * --header-h-sticky, not --header-h: the bar is in its scrolled state by the
 * time any of these lands, and the two are different numbers (74 against 94).
 * The section's own 50px of top padding then does the breathing, which is what
 * it was drawn for.
 *
 * #top is in the nav as well and needs nothing: it is <body>, and at scroll 0
 * the bar is not fixed yet.
 */
section[id] {
  scroll-margin-top: var(--header-h-sticky);
}

/*
 * The scroll itself, and the browser does all of it.
 *
 * Every item in the bar is a plain <a href="#…">, so the hash, the history
 * entry and Back all keep working exactly as they did — this only changes how
 * fast the page gets there. No click handler, no library, and nothing that
 * breaks if a script fails to load.
 *
 * It is the pair that makes it right: scroll-behavior decides HOW the page
 * travels and the scroll-margin-top above decides WHERE it stops, which is the
 * part a sticky header otherwise gets wrong. The nav spy in site.js reads the
 * same header height for its reading line, so the section the bar marks as
 * current is the one the click parked.
 *
 * no-preference, not the global reduce block further down: that one shortens
 * durations, and a smooth scroll is not a duration — the declaration has to be
 * absent for the jump to be instant.
 */
@media (prefers-reduced-motion: no-preference) {
  html {
    scroll-behavior: smooth;
  }
}

.logo {
  display: block;
  width: var(--hf-logo-w);
  transition: all .3s ease;
}

.header-sticky .logo {
  width: var(--hf-logo-w-sticky);
}

.logo img {
  width: 100%;
  height: auto;
}

/*
 * 28×28 was the whole tap target — the glyph and nothing else. The padding takes
 * it to 44×44, the size a thumb is designed against, and the negative margin
 * hands every one of those pixels back to the layout, so the button sits exactly
 * where it did with more of it to hit.
 */
.menu-btn {
  all: unset;
  box-sizing: border-box;
  display: block;
  font-size: 28px;
  line-height: 28px;
  padding: 8px;
  margin: -8px;
  color: var(--hf-ink);
  cursor: pointer;
}

/* ── Menu ────────────────────────────────────────────────────────────────── */

/* The two actions, hard against the right of the bar. LeadXForms spells this
   out with Bootstrap utilities; only the grid half of that framework is loaded
   here, so the same three declarations are stated directly. */
.other-nav-links {
  display: flex;
  align-items: center;
  justify-content: flex-end;
  gap: 8px;
}

.main-menu {
  display: flex;
  align-items: center;
  gap: var(--hf-menu-gap);
}

.main-menu a {
  color: var(--hf-ink);
  font-size: var(--fs-hf-menu);
  text-decoration: none;
  white-space: nowrap;
  transition: all .3s;
}

/*
 * :focus-visible, not :focus — and the difference is what makes .active mean
 * anything.
 *
 * .active is set by the scroll-spy in assets/js/site.js and marks the section the
 * reader is actually in. With plain :focus in this list, a MOUSE click left the
 * clicked item green for as long as it kept focus, so after clicking Home and
 * scrolling to Features the bar showed two green items and neither one told the
 * truth. :focus-visible only paints when the focus came from the keyboard, which
 * is the case where the ring is wanted anyway.
 */
.main-menu a:is(:hover, :focus-visible, .active) {
  color: var(--green);
}

/* ── Buttons ─────────────────────────────────────────────────────────────── */

/*
 * `all: unset` first, because this class is worn by both <a> and <button> and
 * the two arrive with different defaults. Everything the button is is then
 * stated, so neither element can bring anything of its own.
 */
.button {
  all: unset;

  /*
   * Restated immediately after `all: unset`, which is what makes it necessary.
   * `all` sets every property to inherit or initial, and box-sizing is not an
   * inherited one — so it lands on initial, which is content-box. The page's
   * global border-box rule is on `*` at specificity 0,0,0 and loses to this
   * class's own declaration.
   *
   * LeadXForms never sees this because its reset carries !important, which
   * outranks `all` — so the same rule behaved differently the moment it was
   * moved to a stylesheet whose reset is polite.
   *
   * Cost of getting it wrong: height:50 became 50 of CONTENT plus 12 of padding
   * plus 4 of border — a 66px pill. And the icon disc is height:calc(100% - 12px)
   * against a fixed 50px width, so it went from 50×38 to 50×54: a horizontal
   * lozenge turned into a vertical one, which is the shape that was reported.
   */
  box-sizing: border-box;

  position: relative;
  display: inline-flex;
  justify-content: center;
  align-items: center;
  flex-shrink: 0;
  gap: 10px;
  /*
   * min-height, not height, and that distinction is the whole bug.
   *
   * With a hard 50px the pill could not grow, so a label that wrapped was not
   * laid out taller — it overflowed a 46px content box by 7px and `overflow:
   * hidden` above cut it. Both lines were still drawn, one bleeding off the top
   * edge and one off the bottom, which is what "the button breaks" looked like.
   * It bit exactly two labels at 390px — the hero's "Get My Free Security
   * Assessment" and the guardian card's "See how AI Code Guardian works" — and
   * would bite any label long enough on any narrower screen.
   *
   * min-height keeps every single-line button at exactly 50px, because 20.5px
   * of line box plus this padding and the 4px border comes to 48.5 and the
   * minimum wins. Only a wrapped label grows the pill, which is what it should
   * have done from the start.
   *
   * The padding stays at 6px, and that is measured rather than assumed. The
   * line box here is 24px, so 12 of padding and 4 of border come to 40 — well
   * under the 50 minimum, which is why every single-line button on the page
   * still lays out at exactly 50px and nothing that was already right moves.
   * Raising it to 12px was tried first and pushed all of them to 52.
   */
  min-height: var(--hf-btn-h);
  padding: var(--hf-btn-pad-y) var(--hf-btn-pad-x);

  /*
   * ONE LINE, ALWAYS. A wrapped label breaks the pill's shape, and the shape is
   * the component — so the label is never allowed to wrap and the button is
   * sized to hold it instead.
   *
   * min-height above is the safety net, not the plan: with nowrap the label
   * cannot wrap, so the pill only ever grows if something else in it does.
   *
   * What makes this work is that the button's OWN cost comes down on a phone
   * rather than the text having to fit around it. Measured at 18px, the two long
   * labels are 263px and 259px, and the fixed padding+border was 93px — on a
   * 320px screen the guardian card's button is 242px wide altogether, so 93 of
   * chrome left 149px for 259px of text. No font size fixes that. The phone
   * block near the end of this file cuts the chrome and steps the type; see it
   * for the numbers.
   */
  white-space: nowrap;
  border: 2px solid var(--hf-ink);
  border-radius: 50px;
  background-color: var(--hf-ink);
  color: #fff;
  font-family: var(--font);
  font-weight: var(--fw-regular);
  font-size: var(--fs-hf-btn);
  text-decoration: none;
  cursor: pointer;
  overflow: hidden;

  /*
   * color is in this list now, and that is the whole fix.
   *
   * Every variant already carried the same transition declaration, so the three
   * filled ones looked right - their label is white before and after the hover,
   * so a missing color transition had nothing to show. .button-outline is the
   * one that changes it, ink -> white, and with color left out the label jumped
   * to white on the first frame while the background behind it was still half
   * way through its half second. The button read as two different animations
   * running at once, which is what made the plan CTAs feel unlike the navbar.
   *
   * Same duration and easing as the rest of the list, so nothing about the
   * buttons that were already correct changes.
   */
  transition:
    transform .5s cubic-bezier(.76, 0, .24, 1),
    background-color .5s cubic-bezier(.76, 0, .24, 1),
    border-color .5s cubic-bezier(.76, 0, .24, 1),
    color .5s cubic-bezier(.76, 0, .24, 1),
    box-shadow .5s cubic-bezier(.76, 0, .24, 1);
}

.button:is(:hover, :focus) {
  background-color: var(--hf-ink-hover);
  border-color: var(--hf-ink-hover);
  color: #fff;
  transform: translateY(-2px);
  box-shadow: 0 10px 20px rgba(0, 0, 0, .12);
}

.button:active {
  transform: translateY(0) scale(.98);
}

/*
 * The header carries both a signed-out and a signed-in pair of buttons and hides
 * one with the `hidden` attribute. .button sets display: inline-flex, and an
 * author rule beats the UA stylesheet's [hidden] { display: none } - so without
 * this the hidden pair draws anyway. Same cause as .plans-grid[hidden] above.
 *
 * The attribute selector takes it to 0-2-0, which clears .button (0-1-0) on
 * specificity rather than on source order.
 */
.button[hidden] {
  display: none;
}

.button-dark {
  background-color: var(--hf-ink);
  border-color: var(--hf-ink);
  color: #fff;
}

.button-outline:is(:hover, :focus) {
  background-color: var(--hf-ink);
  color: #fff;
}

.button-outline:is(:hover, :focus) .button-icon-span {
  background-color: #fff;
  color: var(--hf-ink);
}

.button-primary {
  background-color: var(--green);
  border-color: var(--green);
}

.button-primary:is(:hover, :focus) {
  background-color: var(--hf-green-hover);
  border-color: var(--hf-green-hover);
  color: #fff;
  box-shadow: 0 10px 25px rgba(51, 159, 105, .3);
}

/*
 * The icon sits in a white disc pinned to the right of the pill rather than
 * riding in the flex line, which is why the label is pushed left and the button
 * reserves 65px on that side for it.
 */
.button.button-icon {
  justify-content: flex-start;
  padding-right: var(--hf-btn-icon-pad-r);
}

.button-icon-span {
  position: absolute;

  /*
   * Held at the single-line size and centred, rather than stretched to the
   * pill. It used to be top:6px + height:calc(100% - 12px), which tracked the
   * pill's height — fine while the pill could not grow, wrong the moment
   * min-height let it. A wrapped label made the pill 69px and the disc went
   * 50x34 to 50x57: the horizontal lozenge turned vertical, which is the exact
   * shape the box-sizing note above records as having been reported once
   * before.
   *
   * 16px, not 12: the percentage height resolved against the PADDING box
   * (50 - 4 of border = 46), so the disc was 34px, not 38. Keeping 34 is what
   * makes this a no-op for every button that was already correct.
   *
   * `translate`, not `transform`, because :hover below sets transform: scale()
   * and the two would overwrite each other. The individual property composes
   * with it instead.
   */
  top: 50%;
  translate: 0 -50%;
  right: 6px;
  width: var(--hf-btn-disc-w);
  height: calc(var(--hf-btn-h) - 16px);
  display: flex;
  justify-content: center;
  align-items: center;
  border-radius: 50px;
  background-color: #fff;
  color: var(--hf-ink);
  /*
   * The disc needs the two colour properties for the same reason the pill needs
   * color. On .button-outline the disc inverts on hover - ink fill with a white
   * arrow becomes a white fill with an ink arrow - and with only transform and
   * box-shadow listed, that inversion landed in a single frame while the disc
   * was still easing through its scale. Listing them makes the disc fade with
   * the button instead of flipping ahead of it.
   */
  transition:
    transform .5s cubic-bezier(.76, 0, .24, 1),
    background-color .5s cubic-bezier(.76, 0, .24, 1),
    color .5s cubic-bezier(.76, 0, .24, 1),
    box-shadow .5s cubic-bezier(.76, 0, .24, 1);
}

.button:is(:hover, :focus) .button-icon-span {
  transform: scale(1.05);
  box-shadow: 0 4px 10px rgba(0, 0, 0, .08);
}

.button-icon-span svg {
  transition: transform .5s cubic-bezier(.76, 0, .24, 1);
}

.button:is(:hover, :focus) .button-icon-span svg {
  transform: rotate(-15deg) scale(1.1);
}

/*
 * SUPERSEDED — the button is one size now, on every screen.
 *
 * These were LeadXForms' own three steps, carried over with the component: the
 * disc narrowed 50 -> 40 -> 35 as the bar tightened and padding-right followed
 * it 65 -> 50, so the label kept the same clearance from the disc at every size.
 *
 * The trouble is that this page is not that bar. The same component is used
 * here for a hero CTA, a plan's Choose button and the header's Get Started,
 * and the steps made all of them shrink together — so a phone showed a visibly
 * smaller arrow than a desktop on buttons that had plenty of room for the full
 * one. The desktop button is wanted everywhere, and there is a second
 * reason for it: 35px is under the 44px minimum for a touch target, and the
 * disc is the part of the button people aim at. The small size was landing on
 * exactly the devices where the target matters most.
 *
 * Nothing replaces them. .button-icon-span's own width: 50px and
 * .button.button-icon's padding-right: 65px above now apply at every width.
 *
 * @media (min-width: 992px) and (max-width: 1199px) {
 *   .button.button-icon .button-icon-span {
 *     width: 40px;
 *   }
 * }
 *
 * @media (max-width: 991.98px) {
 *   .button.button-icon .button-icon-span {
 *     width: 35px;
 *   }
 *
 *   .button.button-icon {
 *     padding-right: 50px;
 *   }
 * }
 */

/* ── Mega-menu feature cards ─────────────────────────────────────────────── */

.ac-card-nav {
  position: relative;
  background: #ffffff;
  border: 1px solid #E5E5E5;
  border-radius: 10px;
  padding: 18px;
  display: flex;
  flex-direction: column;
  gap: 10px;
  cursor: pointer;
  transition: box-shadow 0.2s, border-color 0.2s, transform 0.15s;
  z-index: 0;
}

.ac-card-nav:not(.disabled):hover {
  box-shadow: 0 4px 18px rgba(0, 0, 0, 0.08);
  border-color: #bbf7d0 !important;
  transform: translateY(-1px);
}

/* The dropdown arrow. LeadXForms draws this with a Remix Icon glyph, which
   sits on the text baseline; an SVG does not, so it is nudged to the optical
   centre of the label beside it. */
.nav-chevron {
  flex-shrink: 0;
  margin-top: 1px;
}

/* ── The Get Started wave ────────────────────────────────────────────────── */

/*
 * Each letter is its own box with a copy of itself sitting directly underneath,
 * and hovering slides the whole strip up by exactly one line. The 0.03s per-index
 * delay is what turns ten letters flipping at once into a wave running left to
 * right.
 *
 * The button's overflow:hidden is what keeps the lower copy out of sight until
 * it is wanted.
 */
.button-text-wave {
  display: inline-flex;
  overflow: hidden;
  height: 24px;
  line-height: 24px;
}

.char {
  position: relative;
  display: inline-block;
  transition: transform .45s cubic-bezier(.76, 0, .24, 1);
  transition-delay: calc(var(--i) * .03s);
}

/* The second copy, drawn from the element's own data-char so the markup states
   each letter once. */
.char::after {
  content: attr(data-char);
  position: absolute;
  left: 0;
  top: 100%;
  width: 100%;
  height: 100%;
}

.button:hover .char {
  transform: translateY(-100%);
}

.char-space {
  display: inline-block;

  /*
   * em, not px. It was a flat 5px, which is right at the 18px this was built
   * at and wrong everywhere else — at the 15px the phone now uses, five of
   * them made the label measurably wider than the same text set normally, and
   * that was the last few pixels the guardian button was overflowing by.
   * 0.28em is 5.04px at 18, so desktop does not move.
   */
  width: 0.28em;
}

/*
 * Out is not staggered. Running the wave backwards leaves the label still
 * settling long after the pointer has gone, which reads as lag rather than as
 * motion; dropping the delay brings every letter home together.
 */
.button:not(:hover) .char {
  transition-delay: 0s;
}

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

/* ── Pricing, and the offer badge it carries ─────────────────────────────── */

/*
 * The badge is absolutely positioned against this link, so the link is the box
 * it hangs off. nowrap guards the word itself: a nav item that can fold in half
 * breaks the header rather than the item.
 */
.main-menu a.nav-pricing-link {
  position: relative;
  display: inline-flex;
  align-items: center;
  white-space: nowrap;
}

/*
 * A superscript on the link's top-right corner, hanging into header padding that
 * already exists — so it costs the nav row no width at all. That is the property
 * not to trade away: inline, this badge cost the row 83px and had to be paid for
 * by closing the gaps between every other nav item.
 *
 * left:62% rather than right:0. Anchored to the right edge the pill sits entirely
 * outside the word and drifts toward the buttons; overlapping the word's last
 * third reads as attached to it. bottom:calc(100% - 6px) laps it over the cap
 * height rather than floating it clear, which is what makes it a superscript
 * rather than a second row.
 */
.nav-offer-badge {
  position: absolute;
  bottom: calc(100% - 6px);
  left: 62%;
  top: auto;
  display: inline-flex;
  align-items: center;
  gap: 4px;
  padding: 2px 6px;
  border: 0;
  border-radius: 999px;
  background: #C4EFD8;
  color: #056B3E;
  box-shadow: none;
  font-size: 10px;
  font-weight: 700;
  letter-spacing: .02em;
  line-height: 1;
  white-space: nowrap;
  transition: background-color .3s, color .3s;
  animation:
    nav-offer-in .5s ease .8s backwards,
    nav-offer-flash 2.4s linear 1.3s infinite;

  /* A label, not a target: the cursor passes through to the link underneath, so
     hovering the pill hovers "Pricing". One target, which is why the hover rules
     below hang off the link rather than off this. */
  pointer-events: none;
}

/*
 * Withdrawn below 1200. The badge adds 83px to a row that is already over budget
 * at those widths, and a badge attached to a clipped link cannot be read anyway.
 */
@media (max-width: 1199.98px) {
  .nav-offer-badge {
    display: none;
  }
}

/*
 * Both colours are restated. Without the second line the badge inherits
 * .main-menu a's hover colour and the text shifts to a green the badge never
 * asked for while its background moves somewhere else.
 */
.main-menu a.nav-pricing-link:is(:hover, :focus, .active) .nav-offer-badge {
  background: #B3E8CA;
  color: #04552F;
}

/*
 * Reaching for the link stops the flash — someone with a cursor on "Pricing" has
 * already been got by it, and continuing to flash makes the offer harder to read
 * at the moment they are trying to read it.
 *
 * animation:none rather than play-state:paused, which would freeze the badge on
 * whatever frame it was passing through. Killing the animation hands the colours
 * back to the rule above, and the .3s transition carries them there.
 */
.main-menu a.nav-pricing-link:is(:hover, :focus) .nav-offer-badge {
  animation: none;
}

/*
 * The promotion and annual variants both wear the house promotion accent. Amber
 * is the only colour in the palette that is unmistakably neither the tint this
 * header wears at rest nor the white it turns once stuck, so it holds in both
 * states without needing a flash to carry it — which is why it drops the flash
 * and keeps only the fade-in.
 */
.nav-offer-badge--annual {
  background: #FFB020;
  color: #0B1220;
  animation: nav-offer-in .5s ease-out .8s both;
}

.main-menu a.nav-pricing-link:is(:hover, :focus, .active) .nav-offer-badge--promotion,
.main-menu a.nav-pricing-link:is(:hover, :focus, .active) .nav-offer-badge--annual {
  background: #FF9800;
  color: #0B1220;
}

@keyframes nav-offer-in {
  0% {
    opacity: 0;
  }

  100% {
    opacity: 1;
  }
}

/*
 * The beat, over 2.4s: a 0.24s attack, held to 0.82s while a halo pushes out and
 * fades, back to base at 0.96s, then 1.44s of rest so it reads as a beat rather
 * than a strobe.
 *
 * The colours STEP rather than cross-fade, and that is the load-bearing line.
 * Interpolating a fill one way while its text travels the other means the two
 * pass through each other — the worst frame measured 1.00:1, with the label
 * invisible twice per cycle. step-end makes that frame impossible rather than
 * merely brief.
 */
@keyframes nav-offer-flash {
  0% {
    background: #C4EFD8;
    color: #056B3E;
    box-shadow: 0 0 0 0 rgba(5, 107, 62, .38);
    animation-timing-function: step-end;
  }

  10% {
    background: #95E1B5;
    color: #04552F;
    box-shadow: 0 0 0 0 rgba(5, 107, 62, .34);
    animation-timing-function: ease-out;
  }

  34% {
    background: #95E1B5;
    color: #04552F;
    box-shadow: 0 0 0 8px rgba(5, 107, 62, 0);
    animation-timing-function: step-end;
  }

  40% {
    background: #C4EFD8;
    color: #056B3E;
    box-shadow: 0 0 0 0 rgba(5, 107, 62, 0);
  }

  100% {
    background: #C4EFD8;
    color: #056B3E;
    box-shadow: 0 0 0 0 rgba(5, 107, 62, .38);
  }
}

/* The page's own reduced-motion block already zeroes every animation, so the
   badge rests on its declared fill — legible, just not moving. */

/* ── Resources dropdown ──────────────────────────────────────────────────── */

.blog-preview-text {
  font-size: 13px;
  line-height: 1.4;
  color: #64748b !important;
}

.blog-action-link {
  width: max-content;
  padding-bottom: 2px;
  border-bottom: 2px solid #151823;
  font-size: 14px;
  font-weight: 700;
  color: #151823 !important;
  transition: color .2s ease;
}

.blog-action-link:hover {
  color: #008744 !important;
  border-color: #008744;
}

.mega-hdr i {
  font-size: 16px;
  color: #64748b;
}

/* ── The mobile drawer (below xl) ─────────────────────────────────────────── */
/*
 * The same drawer LeadXForms uses: a white panel that slides in from the left
 * over a dimmed page, with the logo and a close button on top, the links below
 * and the account buttons last. The page behind stays visible but dimmed, and
 * tapping it closes the drawer.
 *
 * The wrapper covers the viewport and only catches the pointer while open
 * (pointer-events), so a closed drawer never blocks the page. The dimming is
 * the wrapper's own ::before, behind the panel.
 */
.aside-menu {
  position: fixed;
  inset: 0;
  z-index: 1000;
  pointer-events: none;
}

.aside-menu.show {
  pointer-events: auto;
}

.aside-menu::before {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  background-color: rgba(0, 0, 0, 0.4);
  opacity: 0;
  transition: opacity .3s linear;
}

.aside-menu.show::before {
  opacity: 1;
}

/*
 * min(360px, 88vw): 360 is the drawer's width, but on a 320 or 360px phone that
 * would be the whole screen, so it never takes more than 88% and a strip of the
 * dimmed page stays visible - that strip is what tells you a tap outside closes it.
 * Moved with transform rather than left, so opening it never re-lays out the page.
 */
.aside-menu-box {
  position: relative;
  display: flex;
  flex-direction: column;
  width: min(360px, 88vw);
  height: 100%;
  background-color: #fff;
  box-shadow: rgba(100, 100, 111, 0.2) 0 7px 29px 0;
  transform: translateX(-100%);
  visibility: hidden;
  transition: transform .3s linear, visibility 0s linear .3s;
}

.aside-menu.show .aside-menu-box {
  transform: translateX(0);
  visibility: visible;
  transition: transform .3s linear, visibility 0s;
}

.aside-logo-wrap {
  display: flex;
  flex-shrink: 0;
  align-items: center;
  justify-content: space-between;
  padding: 20px;
  border-bottom: 1px solid #ddd;
}

.aside-logo {
  display: block;
  width: 160px;
}

.aside-logo img {
  display: block;
  width: 100%;
  height: auto;
}

/* 44px: the only way out of the drawer has to be a finger-sized target. */
button.aside-menu-close {
  all: unset;
  box-sizing: border-box;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 44px;
  min-height: 44px;
  color: var(--hf-ink);
  cursor: pointer;
}

button.aside-menu-close:focus-visible {
  outline: 2px solid var(--green);
  outline-offset: 2px;
  border-radius: 6px;
}

/* min-height: 0 lets this scroll inside the drawer instead of pushing the logo row away. */
.aside-main-menu {
  flex: 1 1 auto;
  min-height: 0;
  padding: 16px 20px 24px;
  overflow-y: auto;
  overscroll-behavior: contain;
  -webkit-overflow-scrolling: touch;
}

.aside-nav-menu {
  display: flex;
  flex-direction: column;
  margin-bottom: 24px;
}

/* The whole row is the tap target, not just the letters. */
.aside-nav-menu a {
  display: flex;
  align-items: center;
  min-height: 48px;
  color: var(--hf-ink);
  font-size: 16px;
  text-decoration: none;
  transition: color .3s;
}

.aside-nav-menu a:is(:hover, :focus-visible, .active) {
  color: var(--green);
}

.aside-actions {
  display: flex;
  flex-direction: column;
  gap: 10px;
}

.aside-actions .button {
  width: 100%;
}

/* Stop the page scrolling behind the open drawer. */
body.menu-lock {
  overflow: hidden;
}

@media (prefers-reduced-motion: reduce) {
  .aside-menu::before,
  .aside-menu-box {
    transition: none;
  }
}

/* ── Footer ──────────────────────────────────────────────────────────────── */

.main-footer {
  background-color: #fff;
  border-top: 1px solid var(--hf-line);
}

.footer-top {
  padding: 30px 0;
}

.footer-info {
  display: flex;
  flex-direction: column;
  gap: 20px;
}

.footer-logo {
  display: inline-block;
  width: var(--hf-footer-logo-w);
}

.footer-logo img {
  width: 100%;
  height: auto;
}

/* Full width rather than LeadXForms' 302px, which its own media queries
   override to 100% at every viewport anyway. */
.footer-info p {
  width: 100%;
  margin-bottom: 0;
  color: var(--hf-body);
  font-size: var(--fs-hf-body);
  line-height: 1.3;
}

.footer-head {
  margin-bottom: 35px;
}

.ft-heading {
  margin: 0;
  color: var(--hf-ink);
  font-size: var(--fs-hf-heading);
  font-weight: var(--fw-bold);
  line-height: normal;
}

.footer-links {
  display: flex;
  flex-direction: column;
  gap: 12px;
  margin: 0;
  padding: 0;
  list-style: none;
}

.footer-links a {
  color: var(--hf-body);
  font-size: var(--fs-hf-body);
  font-weight: var(--fw-regular);
  text-decoration: none;
  transition: all .3s;
}

.footer-links a:is(:hover, :focus, .active) {
  color: var(--green);
}

/* ── Product badges ──────────────────────────────────────────────────────── */

.footer-link-with-badge,
.footer-link-disabled {
  display: inline-flex;
  align-items: center;
  gap: 6px;
}

/* Two products carry a pill beside their name, so the pair is allowed to wrap
   onto a second line rather than push the column wider. */
.footer-link-with-badge {
  flex-wrap: wrap;
}

/*
 * A product that is named but not yet linkable. Not an <a>, because a link that
 * goes nowhere is worse than plain text for anyone navigating by links.
 *
 * 14px rather than the column's 16, and nowrap with it — both deliberate, and
 * LeadXForms says why in its own comment on this rule: the label is set smaller
 * than the other footer links specifically so a Coming Soon pill still fits
 * beside it in this narrow column. At 16px ‘LeadX Call Tracking’ folds and the
 * pill ends up alone on the second line, which is what it was doing here.
 */
.footer-link-disabled {
  color: var(--hf-body);
  opacity: .7;
  font-size: 14px;
  font-weight: var(--fw-regular);
  cursor: not-allowed;
  white-space: nowrap;
}

.footer-badge {
  padding: 3px 6px;
  border-radius: 4px;
  background-color: #e2fbf0;
  color: var(--green);
  font-size: 9px;
  font-weight: var(--fw-bold);
  line-height: 1;
  text-transform: uppercase;
}

/*
 * Smaller and quieter than the New pill — 8px against 9, grey against mint —
 * because it reports an absence rather than announcing something.
 *
 * text-transform:none is the one line that is not simply inherited: .footer-badge
 * above upper-cases, which suits NEW and turns this into COMING SOON — wider than
 * the column it has to fit in, and a shout about a product that is not shipping.
 * LeadXForms writes this badge inline and never applies the transform to it.
 */
.footer-badge--soon {
  padding: 2px 5px;
  border: 1px solid #e2e8f0;
  background-color: #f1f5f9;
  color: #64748b;
  font-size: 8px;
  font-weight: var(--fw-semibold);
  line-height: 1.4;
  text-transform: none;
  white-space: nowrap;
}

/* ── Socials and store badges ────────────────────────────────────────────── */

/*
 * The icons are drawn in currentColor rather than the black they carry in
 * LeadXForms' markup, so the hover below moves the glyph itself and not just its
 * opacity — and so a single colour change reaches all four.
 */
.social-icon {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  color: #000;
  transition: opacity .2s ease, color .2s ease;
}

.social-icon:hover {
  opacity: .7;
}

.footer-app-links .app-btn img,
.footer-mobile-app-stack .app-btn img {
  border-radius: 6px;
  object-fit: contain;
}

/*
 * The two badges of the bottom row are the same height. They were set to a width of 145px with
 * the height left to the image, and the two files are not the same shape (453x135 and 400x135),
 * so Google Play came out 43px tall and the App Store 49px: the pair did not share a top or a
 * bottom edge. LeadXForms gives both 44px; here the width follows the image (148px and 130px),
 * so the App Store badge also ends flush with the right edge of the row and of the legal links
 * below it. (The phone column keeps its own 110px / 120px sizes.)
 */
.footer-app-links .app-btn img {
  display: block;
  width: auto;
  height: 44px;
}

/*
 * The row under the columns: socials at one end, badges at the other. Shown from
 * md (768px) up, where the three link columns are in one row and there is width
 * for it (it used to start at lg, which left the "Follow Us" column alone at the
 * left of a second row from 768px to 991px); below that the same two blocks ride
 * in the "Follow Us" column instead, which is the only place a stacked layout has
 * room for them.
 */
.footer-bottom-row {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 24px;
  margin-top: 56px;
}

/* LeadXForms puts these on the elements as mt-3 / mb-3; stated here because
   only the grid build is loaded and its spacing utilities are not the full
   set. 1rem either side, which is what mt-3 and mb-3 are. */
.footer-socials {
  margin-top: 1rem;
  margin-bottom: 1rem;
}

/* ── Bottom bar ──────────────────────────────────────────────────────────── */

.footer-bottom {
  padding: 20px 0;
  border-top: 1px solid #f1f5f9;
  background-color: #fff;
}

.footer-bottom-inner {
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 15px;
  text-align: center;
}

.copyright-text {
  margin: 0;
  color: var(--hf-body);
  font-family: var(--font-ui);
  font-size: var(--fs-hf-small);
  font-weight: var(--fw-regular);
  line-height: normal;
}

.footer-bottom-links {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 8px 12px;
}

.footer-bottom-links a {
  color: var(--hf-body);
  font-family: var(--font);
  font-size: 13px;
  font-weight: var(--fw-regular);
  line-height: 20px;
  text-decoration-line: underline;
  text-decoration-color: var(--hf-body);
  text-underline-offset: 3px;
}

.footer-bottom-links a:hover {
  color: var(--green);
  text-decoration-color: var(--green);
}

.link-separator {
  color: var(--hf-body);
}

/* At md and up the bar spreads: copyright left, links right. */
@media (min-width: 768px) {
  .footer-bottom-inner {
    flex-direction: row;
    justify-content: space-between;
    text-align: left;
  }

  .footer-bottom-links {
    justify-content: flex-end;
  }
}

/* ── Footer, below desktop ───────────────────────────────────────────────── */

/*
 * LeadXForms' own footer breakpoints, at its own widths rather than this file's.
 * They were missed on the first pass, which left a 224px logo in a viewport
 * narrower than that and the social row at its desktop size on a phone.
 */

@media (min-width: 992px) and (max-width: 1199px) {
  .footer-logo {
    width: 180px;
  }

  .ft-heading {
    font-size: 22px;
  }
}

@media (max-width: 991.98px) {
  .footer-logo {
    width: 180px;
    margin: 0;
  }

  .ft-heading {
    font-size: 20px;
  }

  /* The description runs the column's full width here — the 302px it carries on
     desktop is most of a phone screen. */
  .footer-info {
    align-items: flex-start;
    margin-bottom: 30px;
    text-align: left;
  }

  .footer-info p {
    width: 100%;
    max-width: 100%;
    text-align: left;
  }

  /* Badges stack under the icons rather than sitting beside them. */
  .footer-mobile-app-stack {
    flex-direction: column;
    align-items: flex-start;
    gap: 12px;
    margin-top: 15px;
  }

  /* 110px: the size the two images were given with an inline style (which beat the 120px that
     was written here and so never showed). The inline style is removed from the HTML and this
     is the value that applies, so the badges look the same as before. */
  .footer-mobile-app-stack .app-btn img {
    display: block;
    width: 110px;
    height: auto;
  }
}

/* Tablet (768-991px): the description has a measure, as it has in LeadXForms. It ran the whole
   738-961px of the footer, which is 95-120 characters a line; 560px is about 70, three lines at
   768px. The phone keeps 100%, where the column is narrower than that anyway. Written after the
   max-width: 100% above so it wins on order. */
@media (min-width: 768px) and (max-width: 991.98px) {
  .footer-info p {
    max-width: 560px;
  }
}

/* ── The Bootstrap utilities the mega-menus use ──────────────────────────── */

/*
 * LeadXForms loads the whole framework; this page loads only bootstrap-grid,
 * which is 51 KB against 227. The header markup reaches for 31 utility classes
 * that live in the other 176 KB, and these are those 31, copied at Bootstrap's
 * own values.
 *
 * Writing them out rather than loading the full build saves 176 KB of CSS for
 * roughly forty lines, and none of the rest of that file is used anywhere on
 * this page.
 */

.badge {
  display: inline-block;
  padding: .35em .65em;
  border-radius: .375rem;
  font-size: .75em;
  font-weight: 700;
  line-height: 1;
  text-align: center;
  white-space: nowrap;
  vertical-align: baseline;
}

.bg-white {
  background-color: #fff;
}

.border {
  border: 1px solid #dee2e6;
}

.border-0 {
  border: 0;
}

.fs-6 {
  font-size: 1rem;
}

.fw-semibold {
  font-weight: 600;
}

.fw-bold {
  font-weight: 700;
}

.gap-1 {
  gap: .25rem;
}

.gap-2 {
  gap: .5rem;
}

.gap-3 {
  gap: 1rem;
}

.h-100 {
  height: 100%;
}

.position-static {
  position: static;
}

.rounded-4 {
  border-radius: 1rem;
}

.text-dark {
  color: #212529;
}

.text-muted {
  color: #6c757d;
}

.text-secondary {
  color: #6c757d;
}

.text-decoration-none {
  text-decoration: none;
}

.text-uppercase {
  text-transform: uppercase;
}

/* ═══════════════════════════════════════════════════════════════════════════
   MEGA MENU
   LeadXForms' header dropdown system, ported whole from MasterLayout.vue's
   style block. Kept as it is written there rather than rewritten to this
   file's conventions — the point of it is to match, and a rule that has been
   tidied is a rule that has been changed.
   ═══════════════════════════════════════════════════════════════════════════ */

/* ======================================================= */
/* 1. HEADER & STICKY GLOBAL RULES */
/* ======================================================= */
header {
  position: relative;
}

/* ======================================================= */
/* 2. NAVIGATION ITEM BASE STYLING & POSITIONING */
/* ======================================================= */
.mega-menu-item {
  position: relative;
  /* Default context standard templates layout ke liye */
  padding: 15px 0;
}

/* Integrations menu helper: Relative scope remove karke pure screen border par push karne ke liye */
.mega-menu-item.position-static {
  position: static !important;
}

/* ======================================================= */
/* 3. DROPDOWNS TIMINGS & BEHAVIORS */
/* ======================================================= */
/* Base dropdown attributes */
.mega-dropdown {
  position: absolute;
  top: 100%;
  left: 50%;
  transform: translateX(-50%) translateY(15px);
  width: 650px;
  background: #fff;
  border-radius: 12px;
  z-index: 9999;
  opacity: 0;
  visibility: hidden;
  transition: all 0.3s cubic-bezier(0.165, 0.84, 0.44, 1) !important;
  /* Synced duration */
  text-align: left;
}

/* Full screen custom parameters for integrations */
.mega-dropdown-full {
  left: 0 !important;
  right: 0 !important;
  width: 100% !important;
  /* opacity: 1 !important; */
  /* visibility: visible  !important; */
  transform: translateY(0) !important;
  display: block !important;
  /* layout and design inspect karne ke liye */
  /* transform: translateY(15px) !important; */
  border-radius: 0px !important;
  /* Edge to edge visual screen sync */
  border-top: 1px solid #f1f5f9 !important;
  border-bottom: 1px solid #e2e8f0 !important;
}

/*
 * Focus opens the dropdown as well as hover.
 *
 * These menus were hover-only, so nothing in them could be reached from a
 * keyboard at all — the links exist in the DOM, they are focusable, and the
 * panel holding them stays visibility:hidden while you tab through it. One
 * selector fixes all five, and costs a mouse user nothing.
 */
.mega-menu-item:focus-within .mega-dropdown,
.mega-menu-item:focus-within .mega-dropdown-full {
  opacity: 1;
  visibility: visible;
}

/* Trigger display states on hover */
.mega-menu-item:hover .mega-dropdown {
  opacity: 1;
  visibility: visible;
  transform: translateX(-50%) translateY(0);
}

.mega-menu-item:hover .mega-dropdown-full {
  opacity: 1;
  visibility: visible;
  transform: translateY(0) !important;
}

/* Icon + title + description row (e.g. Popular Templates) — the whole row
   highlights on hover instead of just the icon/text color changing. */
.mega-featured-link-card {
  /* Negative left/right margin cancels the card's own padding so its icon
       lines up flush with the column header above it (which has no side
       padding of its own) — the hover background still gets the padded,
       rounded-corner look without shifting the content to the right. */
  padding: 10px 12px;
  margin: 0 -12px;
  border-radius: 10px;
  display: flex;
  align-items: center;
  transition: background-color 0.2s ease-in-out;
  text-decoration: none;
}

.mega-featured-link-card:hover {
  background-color: #EDF7F2;
}

.mega-featured-link-card:hover .fw-bold.text-dark {
  color: #008744 !important;
}

/* Column 2 is re-keyed per category, so each swap re-mounts these rows and
   replays the fade — a plain swap read as a jarring flicker. */

/* Grid Separators */
.border-end {
  border-right: 2px solid #f1f5f9 !important;
}

/* ======================================================= */
/* 3a. FEATURES MEGA MENU — FEATURED PRODUCT CARDS (PREMIUM) */
/* ======================================================= */
.mega-feat-card {
  position: relative;
  border-radius: 14px;
  padding: 16px;
  border: 1px solid #edf1f5 !important;
  overflow: hidden;
  z-index: 0;
  transition: all 0.3s cubic-bezier(0.165, 0.84, 0.44, 1) !important;
}

/* Soft brand-tinted sheen that fades in on hover, sits behind content */
.mega-feat-card::before {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  background: linear-gradient(135deg, rgba(0, 135, 68, 0.06), rgba(21, 24, 35, 0.03));
  opacity: 0;
  transition: opacity 0.3s ease-in-out;
}

/* Subtle arrow affordance revealed on hover, no extra markup needed */
.mega-feat-card::after {
  content: "\2192";
  position: absolute;
  right: 18px;
  top: 50%;
  transform: translate(6px, -50%);
  opacity: 0;
  color: #008744;
  font-size: 18px;
  font-weight: 700;
  transition: all 0.3s ease-in-out;
}

.mega-feat-card:hover {
  border-color: #d7f5e4 !important;
  box-shadow: 0 12px 28px rgba(15, 23, 42, 0.09);
  transform: translateY(-3px);
}

.mega-feat-card:hover::before {
  opacity: 1;
}

.mega-feat-card:hover::after {
  opacity: 1;
  transform: translate(0, -50%);
}

.mega-feat-card-icon {
  transition: transform 0.3s ease-in-out, box-shadow 0.3s ease-in-out;
}

.mega-feat-card:hover .mega-feat-card-icon {
  transform: scale(1.08);
  box-shadow: 0 6px 16px rgba(15, 23, 42, 0.12);
}

/* ======================================================= */
/* 5. MOBILE VIEW PROTECTION CODE */
/* ======================================================= */
/* Screen resolutions check for megamenu display */
@media (max-width: 991.98px) {
  .mega-dropdown {
    display: none !important;
  }
}

/* Vertical dividers inside dynamic grid */
.border-end {
  border-right: 1px solid #f1f5f9 !important;
}

.border-end {
  border-right: 1px solid #f1f5f9 !important;
}

.mega-hdr {
  font-size: 11px;
  font-weight: 700;
  text-transform: uppercase;
  letter-spacing: 0.8px;
  opacity: 0.8;
}

/*
 * LeadXForms leaves this class unstyled — the link picks up .main-menu a and
 * reads as dark, the same weight as the four cards above it. Given its own
 * rule here so the column's one real link is the one thing in it wearing the
 * brand colour, which is what it is for.
 */
.mega-see-all {
  font-size: 13px;
  font-weight: 600;
  color: var(--green);
}

.main-menu .mega-see-all:is(:hover, :focus) {
  color: var(--hf-green-hover);
}

@media (max-width: 991.98px) {
  .mega-dropdown {
    display: none !important;
  }
}

/* ═══════════════════════════════════════════════════════════════════════════
   THE PAGE RAIL BELOW 992
   ═══════════════════════════════════════════════════════════════════════════ */

/*
 * Bootstrap's container steps; the viewport does not. Between two steps the
 * container holds still while the screen keeps growing, and the difference
 * turns into margin. Measured, content width and margin each side:
 *
 *     767px screen -> 516 content, 126 margin   <- a column in a field of nothing
 *     744px screen -> 516 content, 114 margin
 *     700px screen -> 516 content,  92 margin
 *     576px screen -> 516 content,  30 margin
 *     575px screen -> 551 content,  12 margin   <- and now it is too tight
 *
 * So the same file has both faults: a tablet wastes a third of its width, and a
 * phone has 12px between the text and the edge of the glass. 540 — the width
 * this was reported at — sits right in the middle of it.
 *
 * Below 992 the container goes fluid with one constant gutter instead. The
 * handover is smooth by measurement, not by luck: 991 gives 943 content against
 * 992's 936, so nothing jumps as the breakpoint is crossed.
 *
 * This is the one place this page's container deliberately differs from
 * LeadXForms'. Above 992 — every width the comps were drawn at — it is still
 * Bootstrap's, untouched.
 */
@media (max-width: 991.98px) {
  .container {
    max-width: none;
    padding-inline: var(--page-gutter);
  }
}

@media (prefers-reduced-motion: reduce) {

  *,
  *::before,
  *::after {
    transition-duration: .01ms !important;
    animation-duration: .01ms !important;

    /* Without this a looping animation does not stop, it runs a hundred
       thousand times a second on a .01ms cycle — no motion to see and a core
       spinning to produce it. The map's pins are the first thing on this page
       to animate forever, which is what turned that into a real cost. */
    animation-iteration-count: 1 !important;
  }
}

/* ═══════════════════════════════════════════════════════════════════════════
   THE BUTTON ON A PHONE — MAKING ONE LINE POSSIBLE
   ═══════════════════════════════════════════════════════════════════════════

   .button sets white-space:nowrap, so no label ever wraps. That is a promise
   the component cannot keep on its own, because two labels on this page are
   longer than the button they sit in:

     "Get My Free Security Assessment"   263px at 18px
     "See how AI Code Guardian works"    259px at 18px

   Against that, the room actually available, measured:

     viewport   hero button   guardian card button
        320px       290px            242px
        360px       330px            282px
        390px       360px            312px

   and the component was spending 93px of every one of those on itself — 24px of
   left padding, 65px reserved on the right for the arrow disc, 4px of border. On
   a 320px screen that left 149px of the guardian button for 259px of text. There
   is no font size that fixes a gap that size, which is why the label was wrapping
   and the pill was losing its shape.

   So the chrome comes down where it can, and the type makes up the rest.

   THE DISC IS NOT WHERE THE CHROME COMES FROM. It was, in a first pass — 50 ->
   36, which reads as the obvious saving because the 65px reserved for it is by
   far the biggest single number here. It is also the one thing in the button
   that must not move: the disc is 50 wide and 34 tall, a horizontal lozenge, and
   at 36 it becomes 36x34, which is a circle. That is a different component. The
   65px stays.

   What does come down is the side padding, 24 -> 12, and the guardian card's own
   inset, 24 -> 16, which is worth another 16px to the button sitting inside it.

   The rest comes off the type: 18 -> 14. That is an ordinary size for a button
   label on a phone — 18 was simply the desktop number carried down unchanged —
   and it is the price of keeping the disc's shape, which is the right trade.

   Under 360 there is a second step, and it is not pretty: a 320px screen is
   simply too narrow for a 31-character label at a comfortable size. 12px keeps
   it on one line with its shape intact, which is the thing that was asked for.
   ═══════════════════════════════════════════════════════════════════════════ */

@media (max-width: 575.98px) {
  :root {
    /*
     * The disc and the padding-right it reserves are NOT touched here. They
     * were, briefly — 50 -> 36 — and that was wrong: at 36 the disc is 36x34,
     * which is a circle, and the component draws a 50x34 horizontal lozenge.
     * The shape is the design, so the pixels have to come from somewhere else.
     */
    --hf-btn-pad-x: 12px;

    /*
     * 14, not 15, and the disc is why. Keeping it at 50 keeps 65px reserved on
     * the right, and that is 14px more chrome than the 36px disc was costing —
     * so the point has to come off the type instead. 14px is an ordinary size
     * for a button label on a phone; a circle where the design draws a lozenge
     * is not an ordinary shape.
     */
    --fs-hf-btn: 14px;
  }
}

@media (max-width: 359.98px) {
  :root {
    --fs-hf-btn: 12px;
  }
}

/* ═══════════════════════════════════════════════════════════════════════════
   THE SIGNOUT CONFIRM
   ═══════════════════════════════════════════════════════════════════════════

   Drawn to match the SweetAlert2 dialog LeadXForms opens before ending a
   session, because a visitor moving between the two sites should meet the same
   control. Its warning palette (#facea8 ring, #f8bb86 mark) and Bootstrap's
   btn-danger / btn-dark are copied literally rather than tokenised: they are
   another project's component, and a value changed here would only put the two
   dialogs out of step.

   A native <dialog>, so the parts that are easy to get wrong are not written at
   all - focus is trapped, Escape closes, the page behind goes inert, and the top
   layer puts it above everything without a z-index.
   ═══════════════════════════════════════════════════════════════════════════ */

.lx-confirm {
  width: min(92vw, 420px);
  padding: 40px 28px 32px;
  border: 0;
  border-radius: 12px;
  background: #fff;
  color: var(--text);
  font-family: var(--font);
  text-align: center;
  box-shadow: 0 24px 60px rgba(0, 0, 0, .18);
}

/* Not inherited: ::backdrop is a separate box, not a child. */
.lx-confirm::backdrop {
  background: rgba(0, 0, 0, .45);
}

/*
 * The warning mark. A bordered circle with a character in it rather than an
 * SVG - the glyph IS the shape, so there is nothing to draw.
 *
 * aria-hidden in the markup: it repeats what the title and the buttons already
 * say, and "exclamation mark" read aloud adds nothing.
 */
.lx-confirm-icon {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 80px;
  height: 80px;
  margin: 0 auto 26px;
  border: 4px solid #facea8;
  border-radius: 50%;
  color: #f8bb86;
  font-size: 44px;
  font-weight: var(--fw-bold);
  line-height: 1;
}

.lx-confirm-title {
  margin: 0 0 16px;
  font-size: 28px;
  font-weight: var(--fw-bold);
  line-height: 1.2;
  color: var(--text-heading);
}

.lx-confirm-text {
  margin: 0;
  font-size: 18px;
  font-weight: var(--fw-regular);
  line-height: 1.5;
  color: var(--text);
}

.lx-confirm-actions {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  gap: 8px;
  margin-top: 40px;
}

/*
 * Not .button. That component is a 50px pill with an arrow disc and a hover
 * lift, built for the page's calls to action - a destructive confirm should not
 * look like one of those, and LeadXForms' own dialog uses plain Bootstrap
 * buttons here for the same reason.
 */
.lx-confirm-btn {
  padding: 8px 24px;
  border: 0;
  border-radius: 8px;
  font-family: var(--font);
  font-size: 16px;
  font-weight: var(--fw-regular);
  line-height: 1.5;
  color: #fff;
  cursor: pointer;
  transition: background-color .15s ease;
}

.lx-confirm-btn:focus-visible {
  outline: 2px solid var(--green);
  outline-offset: 2px;
}

.lx-confirm-btn--danger {
  background: #dc3545;
}

.lx-confirm-btn--danger:hover {
  background: #bb2d3b;
}

.lx-confirm-btn--dark {
  background: #212529;
}

.lx-confirm-btn--dark:hover {
  background: #424649;
}

@media (max-width: 575.98px) {
  .lx-confirm {
    padding: 32px 20px 24px;
  }

  .lx-confirm-title {
    font-size: 24px;
  }

  .lx-confirm-text {
    font-size: 16px;
  }

  /* Stacked, and the destructive one is no longer the first thing a thumb
     reaches - "No, return" sits under it, nearest the bottom of the screen. */
  .lx-confirm-actions {
    flex-direction: column-reverse;
    margin-top: 32px;
  }

  .lx-confirm-btn {
    width: 100%;
  }
}

/* ═══════════════════════════════════════════════════════════════════════════
   MOTION
   One reveal system for the whole page, plus the pieces that need something of
   their own. Three levels, and they are deliberately different weights:

     1  Micro      hover and focus on things you can click. CSS only.
     2  Reveal     a section's parts arrive as it enters. [data-reveal] + one
                   IntersectionObserver in site.js, which stops watching each
                   element the moment it has fired.
     3  Story      the four places where the motion says something the copy
                   does not — the hero's entrance, the Engine's scroll-driven
                   layers (already built, see .engine-track), the Deep-Dives'
                   zig-zag (already built, see @keyframes deep-in) and the
                   Guardian's scan.

   WHAT IS NOT HERE, ON PURPOSE. No library. Every rule below animates opacity
   or transform and nothing else, so none of it costs layout — the one exception
   is the FAQ's height, which is a transition on a user action rather than on
   scroll, and which the browser now interpolates natively.
   ═══════════════════════════════════════════════════════════════════════════ */

/*
 * FIVE DURATIONS FOR THE WHOLE PAGE.
 *
 * Every animated thing below picks one of these rather than naming its own
 * number, which is what stops the page accumulating .25s here and .32s there
 * until nothing quite agrees with anything. The rungs are far enough apart to be
 * distinguishable and the choice between them is about WEIGHT:
 *
 *   fast     a thing acknowledging the pointer
 *   normal   a card or a disclosure changing state
 *   medium   a small part of a section arriving
 *   slow     a section arriving
 *   story    a background, which should already be there when the copy lands
 */
:root {
  --motion-normal: 280ms;

  /* Ease-out with a long tail. Nothing on this page overshoots. */
  --rv-ease: cubic-bezier(.22, .61, .36, 1);

  /* Travel. Short enough that nothing arrives from off-screen — the point is
     that the element settles, not that it flies in. */
  --rv-y: 26px;
  --rv-x: 30px;
}

/*
 * Only the four moving variants get a transform, and that is not tidiness.
 *
 * .action-wash, .plans-wash and every .geo-pin already carry a transform of
 * their own — translateX(-50%) and translate(-50%,-50%) — which is what places
 * them. A blanket transform here would overwrite it and drop all three half
 * their own width off their mark. Those elements use the opacity-only variants,
 * "fade" and "wash", which never name transform at all.
 */
.js-anim :is([data-reveal="up"],
  [data-reveal="left"],
  [data-reveal="right"],
  [data-reveal="scale"]) {
  transform:
    translate3d(var(--rv-dx, 0), var(--rv-dy, var(--rv-y)), 0) scale(var(--rv-s, 1));
}

.js-anim :is([data-reveal="up"],
  [data-reveal="left"],
  [data-reveal="right"],
  [data-reveal="scale"]).is-in {
  transform: none;
}

/* The two halves of an alternating row enter from the edge each one sits
   against, so the row reads as assembling rather than as two fades. */
[data-reveal="left"] {
  --rv-dx: calc(var(--rv-x) * -1);
  --rv-dy: 0;
}

[data-reveal="right"] {
  --rv-dx: var(--rv-x);
  --rv-dy: 0;
}

/* For a large single object — the dashboard, the map, the CTA card — where
   sliding a 1200px box reads as a slab moving, and settling into place does
   not. */
[data-reveal="scale"] {
  --rv-dy: 14px;
  --rv-s: .97;
}

/* ── Reduced motion ──────────────────────────────────────────────────────── */

/*
 * The global block further up already flattens every duration on the page. This
 * one is about something that block cannot fix: a duration of .01ms still needs
 * the observer to add .is-in before anything becomes visible, so a reader who
 * has asked for no motion would still have content appear only once scrolled to.
 *
 * So the reveal is switched off rather than shortened — everything is at its end
 * state from the first paint, and the observer's work is invisible.
 *
 * transform: none is named only for the four variants that set one, for the same
 * reason the base rule is: the washes and the pins place themselves with a
 * transform, and clearing it would move them.
 */
@media (prefers-reduced-motion: reduce) {

  .js-anim :is([data-reveal="up"],
    [data-reveal="left"],
    [data-reveal="right"],
    [data-reveal="scale"]) {
    transform: none;
  }
}

/* ── Below desktop ───────────────────────────────────────────────────────── */

/*
 * Not the desktop numbers scaled down — one of them is a different decision.
 *
 * The sideways reveals become vertical. At lg the alternating halves sit side by
 * side and entering from the edge each one occupies means something; stacked,
 * they are one above the other and a horizontal slide says nothing about a
 * layout that no longer has a left and a right. It also removes the only way a
 * reveal could reach past the viewport — .page-wrap clips the overflow, so
 * nothing would scroll, but the area crossed still costs a composite.
 */
@media (max-width: 991.98px) {
  :root {
    --rv-y: 18px;
  }

  [data-reveal="left"],
  [data-reveal="right"] {
    --rv-dx: 0;
    --rv-dy: var(--rv-y);
  }
}

@media (max-width: 575.98px) {

  /*
   * Shorter and quicker. A phone's viewport is a third of a laptop's, so the
   * same 26px of travel is proportionally three times the movement, and the same
   * 620ms is three times as long to wait for a screen you can take in at once.
   */
  :root {
    --rv-y: 14px;
  }

  [data-reveal="scale"] {
    --rv-s: .985;
  }
}

/* ── How far down the page you are ───────────────────────────────────────── */

/*
 * A 2px rule along the bottom edge of the bar, and it only exists once the bar
 * is sticky — at the top of the page there is nothing to report and a progress
 * bar reading zero is just a line under the logo.
 *
 * Driven by scroll(root block), so it is the document's own scroll position
 * rather than a number this page calculates. That is the entire implementation:
 * no listener, no rAF, nothing added to the one the header already runs.
 *
 * Every declaration sits inside the @supports, which is what makes the element
 * safe to put in the markup: where the timeline is unavailable the span has no
 * styles at all and renders nothing, rather than a bar stuck at full width.
 *
 * This page is about sixteen thousand pixels tall. A reader three screens in has
 * no way to tell whether that is a tenth of it or half, and that is the one
 * question this answers.
 */
@supports (animation-timeline: scroll()) {
  @media (prefers-reduced-motion: no-preference) {

    @keyframes scroll-progress {
      to {
        scale: 1 1;
      }
    }

    .scroll-progress {
      position: absolute;
      left: 0;
      right: 0;
      bottom: 0;
      height: 2px;
      pointer-events: none;

      background: var(--engine-accent);
      transform-origin: 0 50%;
      scale: 0 1;

      opacity: 0;
      transition: opacity var(--motion-normal) var(--rv-ease);

      animation: scroll-progress linear both;
      animation-timeline: scroll(root block);
    }

    .header-sticky .scroll-progress {
      opacity: 1;
    }
  }
}