/*----------------------------------------------------------------------------------

Project     :   DataNature - Landing Page
Purpose     :   1. Reconciles the landing design with the Tailwind app it lives in.
                2. Card patterns the original design lacks, for sections carried
                   over from the previous landing page.
                Loaded last, so it wins on equal specificity.

[Table of contents]

tailwind reconciliation
hero product logos
shared tokens
new section spacing
deployment chips
data format cards
industry cards
comparison table

-------------------------------------------------------------------------------------*/

/*-------------------------------------------------------------------------------------
    hero product logos

    The design's `.caption-download-btns` are 40px green-gradient circles built
    for a single white glyph. The real product marks (AI360, Voir, DocuContext)
    are full-colour logos on light backgrounds, so this variant swaps the badge
    to white and sizes it up a touch to give each mark room to read against the
    dark-green hero.
---------------------------------------------------------------------------------------*/

.caption-download-btns.product-logos li a {
    width: 72px;
    height: 72px;
    line-height: normal;
    background-image: none;
    background-color: #fff;
    border: 1px solid rgba(255, 255, 255, 0.6);
    -webkit-box-shadow: 0 8px 20px -6px rgba(4, 30, 14, 0.5);
    box-shadow: 0 8px 20px -6px rgba(4, 30, 14, 0.5);
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    overflow: hidden;
    margin: 0 6px;
}

.caption-download-btns.product-logos li a img {
    width: 100%;
    height: 100%;
    object-fit: contain;
    /* Padding keeps the mark off the badge edge; the circle crops the corners
       of the wider logos gracefully. */
    padding: 9px;
}

/* Keep the hover cue but don't shift a raster logo's background. */
.caption-download-btns.product-logos li a:hover {
    background-size: auto;
    -webkit-transform: translateY(-2px);
    transform: translateY(-2px);
    -webkit-box-shadow: 0 12px 26px -6px rgba(4, 30, 14, 0.6);
    box-shadow: 0 12px 26px -6px rgba(4, 30, 14, 0.6);
}

/* The design's decorative art (.faq-area-img, app-download imagery, rotated
   circle blobs) is absolutely positioned and wider than a phone, so it bled
   ~75px past the right edge and gave the whole page a phantom horizontal
   scroll — which read as "content doesn't fill the width" on mobile. Clip it
   at the landing root. `clip` (not hidden) doesn't spawn a scroll container,
   so the JS sticky header is unaffected; real content lives inside `.container`
   (never wider than the viewport) so nothing meaningful is cut. */
.dn-landing {
    overflow-x: clip;
}

/* Make every landing section its own containing block AND clip it, so decorative
   absolutes (.faq-area-img, blob circles) can't widen the page. The real bug:
   #faq-area is position:STATIC, so its abspos image (left:-330px, 934px wide)
   resolved against the VIEWPORT, not the section — escaping every ancestor clip
   and producing horizontal overflow (the white gutters around the header, on
   desktop and mobile alike). position:relative pins it back inside the section.
   All widths; a section's own inner scroller (.compare-wrap) is a child and
   keeps scrolling normally. */
.dn-landing section {
    position: relative;
    overflow-x: clip;
}

/* Footer clip on phones. The HEADER is deliberately NOT clipped here.
   #navbarContent is `position:absolute; top:100%; width:100vw` — it hangs below
   and outside the header on purpose — and #header is its containing block, so
   any `overflow: clip` on the header clips the open menu.
   Chrome honours `overflow-x: clip` with `overflow-y: visible` and clips only
   sideways, so this looked fine there. WebKit's `clip` support is far newer and
   clips both axes, which cut the whole dropdown away on iOS: the tap toggled
   the state correctly and nothing appeared, which reads as a dead hamburger.
   The header has nothing that bleeds horizontally anyway — the panel is exactly
   100vw and centred — so it needs no clipping. */
@media only screen and (max-width: 767px) {

    .dn-landing footer {
        overflow-x: clip;
    }

    /* Explicit, so nothing further down the cascade re-clips the open menu. */
    .dn-landing header {
        overflow: visible;
    }
}

/* Hide the page scrollbar on the mobile/tablet view (<992px, matching the
   hamburger + fixed-header breakpoint) so it doesn't eat content width, WITHOUT
   touching overflow (changing it breaks the window scroll the sticky-header and
   scroll-nav JS depend on). This sheet is landing-only, so the rest of the app
   keeps its scrollbar. */
@media only screen and (max-width: 991px) {

    html,
    body {
        scrollbar-width: none;
        /* Firefox + Chrome 121+ */
        -ms-overflow-style: none;
        /* legacy Edge */
    }

    html::-webkit-scrollbar,
    body::-webkit-scrollbar {
        width: 0;
        height: 0;
        display: none;
    }
}

/* Mobile / tablet nav menu — the hamburger dropdown (shown below 992px). The
   template renders the open menu (#navbarContent, which already carries the
   green→blue gradient) as an inset box floating over the hero with a gap on
   each side, so it reads as a detached rectangle overlapping the headline.
   Turn it into a clean full-width panel that drops straight down from under the
   header, edge to edge. A full-bleed transform gives it the viewport width
   without touching the navbar's own positioning, and it's clipped to <992px so
   the desktop inline nav is untouched. */
@media only screen and (max-width: 991px) {

    /* Pin the header on mobile/tablet so the nav (and hamburger) stays reachable
       while scrolling. The template only makes it fixed after 100px via the
       .sticky JS, which leaves a gap where it scrolls away first — force it fixed
       from the top. It's transparent over the dark hero, and the .sticky JS still
       adds the solid gradient background once scrolled, so text stays readable. */
    #header {
        position: fixed;
    }

    #header .navbar {
        position: relative;
    }

    #header #navbarContent.navbar-collapse {
        position: absolute;
        top: 100%;
        left: 50%;
        width: 100vw;
        -webkit-transform: translateX(-50%);
        transform: translateX(-50%);
        -webkit-box-shadow: 0 16px 34px -12px rgba(4, 30, 14, 0.45);
        box-shadow: 0 16px 34px -12px rgba(4, 30, 14, 0.45);
        /* The panel hangs off a fixed header, so the page can't scroll it: with a
           submenu open it ran past the screen bottom with no way to reach the rest.
           It scrolls on its own instead (76px = where the panel starts). */
        max-height: calc(100vh - 76px);
        max-height: calc(100dvh - 76px);
        overflow-y: auto;
        overscroll-behavior: contain;
        -webkit-overflow-scrolling: touch;
        scrollbar-width: thin;
        scrollbar-color: #b9c4bd transparent;
    }

    #header #navbarContent.navbar-collapse::-webkit-scrollbar {
        width: 5px;
    }

    #header #navbarContent.navbar-collapse::-webkit-scrollbar-thumb {
        background: #b9c4bd;
        border-radius: 5px;
    }

    /* Even, comfortable inset for the links now that the panel is full width. */
    #header #navbarContent .navbar-nav {
        padding: 18px 28px 26px;
    }
}

/*-------------------------------------------------------------------------------------
    white navbar

    The design ships a white logo + white links for the dark hero. The navbar is
    now solid white at all times (top and sticky), so switch the marks to dark ink.
    Loaded last, so these win over the transparent-top / dark-emerald-sticky states.
    (The logo <img> src is swapped to logo-color.png in LandingHeader.jsx.)
---------------------------------------------------------------------------------------*/

/* Pin the header at all widths so it never scrolls away. The design keeps it
   position:absolute until the .sticky JS fires at 100px, so on the way down it
   scrolls off and then snaps back — the "disappears then reappears" flicker.
   Fixed-from-the-top keeps it constant; with a solid white bar in both states,
   .sticky toggling is now visually seamless. Consistent padding avoids a height
   jump when .sticky flips. */
#header,
#header.sticky {
    position: fixed;
    top: 0;
    left: 0;
    width: 100%;
    padding: 12px 0;
    background: #fff;
    -webkit-box-shadow: 0 2px 14px rgba(8, 60, 28, 0.09);
    box-shadow: 0 2px 14px rgba(8, 60, 28, 0.09);
}

/* Keep the logo one constant size. The design shrank it (36->32px) when .sticky
   fires; with the bar height now fixed, that shrink reads as the logo "jumping"
   on scroll. Hold it steady so the whole navbar stays constant. */
#header .logo img,
#header.sticky .logo img {
    height: 36px;
}

.navbar-nav .nav-link {
    color: #0f2418;
    transition: color 0.25s;
}

/* The template flagged the hovered/active link with a 15px dotted rule, which
   reads as a stray "..." under the label. Swap it for a solid underline that
   wipes out from the centre. Scoped off the two button items — they kill their
   own :after and must not sprout a bar. */
.navbar-nav .nav-item:not(.download-btn) .nav-link:after {
    content: '';
    position: absolute;
    /* Explicit, because the template hides this pseudo on the "Sign in" item
       (it was a button there, and a button must not sprout a bar). That rule
       and this one have the same specificity, so overrides.css wins on order —
       but only for properties it actually declares. */
    display: block;
    left: 0;
    right: 0;
    top: calc(100% - 7px);
    width: 60%;
    height: 2px;
    margin: 0 auto;
    border-bottom: 0;
    border-radius: 2px;
    background-color: #1E8A3D;
    -webkit-transform: scaleX(0);
    transform: scaleX(0);
    -webkit-transition: -webkit-transform 0.25s ease;
    transition: transform 0.25s ease;
}

.navbar-nav .nav-item:not(.download-btn) .nav-link.active:after,
.navbar-nav .nav-item:not(.download-btn) .nav-link:hover:after {
    -webkit-transform: scaleX(1);
    transform: scaleX(1);
}

.navbar-nav .nav-item:not(.download-btn) .nav-link:hover,
.navbar-nav .nav-item:not(.download-btn) .nav-link.active {
    color: #1E8A3D;
}

/* "Sign in" is a PLAIN LINK, not a button. It used to be an outline button
   beside the solid one, which gave the bar two button shapes and made the
   secondary action compete with the primary for the same attention. As a text
   link it steps back into the nav row — one button in the bar, and it is the
   one we want clicked.

   Nothing here but a reset of the template's button chrome: the 1px border, the
   8px radius, the 9px/26px padding and the 600 weight all go, leaving the same
   geometry, weight and colour as Home / Pricing / Docs. It also picks up their
   underline-on-hover, because the rules above no longer exclude it. */
.navbar-nav .nav-item.signin-btn .nav-link {
    border: 0;
    border-radius: 0;
    padding: 0.5rem 1rem;
    font-weight: 500;
    background-color: transparent;
    color: #0f2418;
}

/* "Start free" primary CTA: solid emerald so it stands out on the white bar. The
   design made it white-bg/green-text for the old dark hero; on white it needs the
   fill. Scoped to the navbar button only — the hero/pricing/footer white buttons
   still sit on dark grounds and keep their treatment.

   No shadow, on either state. The template threw `0px 10px 30px 0px
   rgba(8,60,28,0.35)` under it and an earlier pass here replaced that with a
   green one — but a wide, fully saturated blur under a saturated fill is a glow,
   not depth: it smeared a green haze onto the white bar under the button and
   made the edge look soft. `box-shadow: none` is what kills the template's, so
   it has to stay declared even though nothing here adds one. Hover is carried by
   the colour step (#1E8A3D -> #047857) alone. */
.navbar-nav .nav-item.download-btn .nav-link {
    background-image: none;
    background-color: #1E8A3D;
    color: #fff;
    -webkit-box-shadow: none;
    box-shadow: none;
}

.navbar-nav .nav-item.download-btn .nav-link:hover {
    background-color: #047857;
    color: #fff;
    -webkit-box-shadow: none;
    box-shadow: none;
}

/*-------------------------------------------------------------------------------------
    desktop nav layout — links beside the logo, auth buttons hard right

    The template hangs the whole <ul> off the right edge (`ml-auto` on
    .navbar-nav), so Home / Pricing / Docs drift into the middle of the bar with
    a wide dead gap after the wordmark, and the two auth buttons sit wherever
    that pile happens to end.

    Split the row instead: cancel the list's auto margin so it starts right after
    the logo, then push everything from "Sign in" rightwards with an auto margin
    on that item. The logo itself is untouched — it keeps the exact position it
    already had.

    Scoped to >=992px, the navbar's expand breakpoint. Below it the panel is a
    stacked dropdown where `margin-left: auto` would only indent the buttons.
---------------------------------------------------------------------------------------*/

@media only screen and (min-width: 992px) {

    /* The list can only reach the right edge if its parent spans the bar. */
    #header .navbar-collapse {
        -webkit-box-flex: 1;
        -ms-flex-positive: 1;
        flex-grow: 1;
    }

    /* Beats Bootstrap's `.ml-auto { margin-left: auto !important }` on the <ul>. */
    #header .navbar-nav.ml-auto {
        margin-left: 0 !important;
        width: 100%;
    }

    /* A little air so "Home" is next to the wordmark, not welded to it. */
    #header .navbar-nav>.nav-item:first-child {
        padding-left: 20px;
    }

    /* "Sign in" and everything after it (Start free) go to the far right. */
    #header .navbar-nav>.nav-item.signin-btn {
        margin-left: auto;
    }
}

/* Widen the header's own container so the bar spans nearly the whole window:
   the logo sits close to the left edge and the auth buttons close to the right.
   #header > .container and .navbar > .container are nested, each with its own
   max-width cap and 15px side padding, so the outer one goes fluid with a 40px
   gutter and the inner one drops its cap and padding — otherwise the inner cap
   clamps the width back down and the two paddings stack into a 30px indent.

   The 1600px ceiling keeps the bar from stretching absurdly on ultra-wide
   screens. At 1440px the logo is 40px from the left edge and "Start free" 40px
   from the right.

   Scoped to >=992px, the desktop inline-nav breakpoint. Below it the hamburger
   layout is already near full-width.

   Note this deliberately breaks the header's alignment with the rest of the
   page: the hero copy, sections and footer still sit in 1140px containers, so
   the nav now starts outside them. That is the requested look. */
@media only screen and (min-width: 992px) {

    #header>.container {
        max-width: 1600px;
        padding-left: 40px;
        padding-right: 40px;
    }

    #header .navbar>.container {
        max-width: none;
        padding-left: 0;
        padding-right: 0;
    }
}

/*-------------------------------------------------------------------------------------
    feature / security card icons — one brand colour, no decoration

    The template gives the four card variants four unrelated accent colours for
    the round icon badge: #1E8A3D green, #1F5FD4 blue, #35B44A green again and
    #14b8a6 teal — two greens, a blue and a teal sitting in one row. On a site
    whose palette is now a single green hue, the blue and teal read as foreign,
    and the duplicated green makes the set look accidental rather than coded.

    The hover states were worse: the cards flipped to #d22d4a red, #14b8a6 teal
    and #d59d17 amber, none of which appear anywhere else on the site.

    Two corrections. First, drop the decorative halo rings that wrapped each
    badge, so what is left is the icon and nothing else.

    Second, put the badges on TWO colours, alternating — the brand green #1E8A3D
    and the brand blue #1F5FD4, the same blue the primary buttons use. A single
    flat green across a whole row made the four cards read as one repeated item;
    alternating gives the row a rhythm without inventing a colour, because both
    hexes are already the site's own. It stays brand rather than data: the pair
    marks position in the row, not a property of the feature, which is why it is
    a two-step alternation and not four distinct accents (the template's own
    green/blue/green/teal scheme is exactly the arbitrary-looking set this
    replaced).

    The mapping is by VARIANT, not by DOM position: `` and `.three` are green,
    `.two` and `.four` are blue. All three card sets in LandingPage.jsx cycle
    their variants in that order — including the 6-up capability grid, which
    repeats ``/`two` for cards 5 and 6 — so the alternation holds in every grid
    without any :nth-child rules that would break when a card is added.

    Hover keeps the pairing: the card fills with its own colour and the badge
    inverts to a white disc with that same colour as the glyph.

    Applies to all three sections built from .core-feature-single (core features,
    capabilities and security). To limit it to the security cards, prefix each
    selector with #security-area.
---------------------------------------------------------------------------------------*/

/* Odd cards — brand green. */
.core-feature-single .core-feature-single-item .icon,
.core-feature-single .core-feature-single-item.three .icon {
    background-color: #1E8A3D;
}

/* Even cards — brand blue. */
.core-feature-single .core-feature-single-item.two .icon,
.core-feature-single .core-feature-single-item.four .icon {
    background-color: #1F5FD4;
}

/* The badge shipped wrapped in two concentric halo rings (a 125px :before and a
   100px :after, both absolutely positioned around the 70px disc). With the
   colour gone they are just grey targets, and they were what made the icon area
   read as a layered effect rather than an icon. Remove both — the icon is the
   icon. */
.core-feature-single .core-feature-single-item .icon:before,
.core-feature-single .core-feature-single-item .icon:after {
    display: none;
}

/* The rings dictated the spacing around the badge: 60px of card padding cleared
   the :before's -27px overhang, and the icon's 50px bottom margin was mostly the
   28px the ring hung below the disc. With the rings gone that geometry leaves a
   hole above and below the icon, so pull both back to the gap the eye actually
   saw before. */
.core-feature-single .core-feature-single-item {
    padding-top: 40px;
}

.core-feature-single .core-feature-single-item .icon {
    margin-bottom: 26px;
}

/* Hover: the card fills with ITS OWN colour rather than the template's red,
   teal and amber, so hovering along the row keeps the green/blue alternation
   instead of introducing a third and fourth hue. The white-disc inversion is
   already on the template's base rule; what needs pinning here is the fill and
   the glyph colour, per pair.

   The trigger is the WRAPPER's hover, not the card's. The template fires the
   floating shapes on `.core-feature-single:hover` but the fill on
   `.core-feature-single-item:hover`, and responsive.css pads the wrapper around
   the card (60px 10px 10px at 992-1200, 60px 30px 25px at 480-767). Pointing at
   that padding — or at a shape — showed the shapes over a still-white card, a
   half-hovered state. Keying everything off the wrapper makes it all-or-nothing. */
.core-feature-single:hover .core-feature-single-item,
.core-feature-single:hover .core-feature-single-item.three {
    background-color: #1E8A3D;
}

.core-feature-single:hover .core-feature-single-item.two,
.core-feature-single:hover .core-feature-single-item.four {
    background-color: #1F5FD4;
}

.core-feature-single:hover .core-feature-single-item .icon,
.core-feature-single:hover .core-feature-single-item.three .icon {
    background-color: #fff;
    color: #1E8A3D;
}

.core-feature-single:hover .core-feature-single-item.two .icon,
.core-feature-single:hover .core-feature-single-item.four .icon {
    background-color: #fff;
    color: #1F5FD4;
}

/* `!important` to match the template's own hover rule for the copy. */
.core-feature-single:hover .core-feature-single-item h3,
.core-feature-single:hover .core-feature-single-item p {
    color: #fff !important;
}

/*-------------------------------------------------------------------------------------
    contact form — centred submit

    The theme leaves the submit button at the form's left edge (it is an inline
    button with `margin: 25px 0 0`), which reads as unfinished under three
    full-width fields. Centre it in the form column at every width: `display:
    block` gives the auto side margins something to resolve against, and the
    25px top margin is preserved.

    The status line under it is centred to match — it is that button's own
    success/error text, so left-aligning it under a centred button would just
    reintroduce the same ragged edge.
---------------------------------------------------------------------------------------*/

.contact-form button {
    display: block;
    margin: 25px auto 0;
}

.contact-form .messages {
    text-align: center;
}

/* Compact contact form. The template's form was 55px inputs, a 10-row message
   box and 16px gaps — about 460px of form under a 330px heading, so at a
   laptop's viewport height the section was all form. Now: fields two to a row
   (see LandingPage.jsx), 46px controls, a 4-row message box that the visitor can
   still drag taller, and tighter gaps. With the two added fields it is still
   shorter than the old three-field form. */
.contact-form .form-group {
    margin-bottom: 12px;
}

.contact-form input.form-control,
.contact-form select.form-control {
    height: 46px;
}

.contact-form textarea.form-control {
    min-height: 110px;
    padding: 12px 16px;
    resize: vertical;
}

.contact-form button {
    margin-top: 16px;
}

/* Country <select>. The template only styles `input` and `textarea`, so the
   select fell back to Bootstrap's grey-bordered control. Match the inputs' box,
   draw our own chevron, and grey the "Country*" prompt like a placeholder —
   `:invalid` holds exactly while the required select still sits on it. */
.contact-form select.form-control {
    border: 1px solid #e0e2e5;
    border-radius: 8px;
    padding: 0 40px 0 16px;
    font-family: 'Inter', sans-serif;
    font-size: 14px;
    color: #0f2418;
    background-color: transparent;
    background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='14' height='14' viewBox='0 0 24 24' fill='none' stroke='%236b7280' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m6 9 6 6 6-6'/%3E%3C/svg%3E");
    background-repeat: no-repeat;
    background-position: right 16px center;
    -webkit-appearance: none;
    -moz-appearance: none;
    appearance: none;
    cursor: pointer;
}

.contact-form select.form-control:invalid {
    color: #6c757d;
}

.contact-form select.form-control option {
    color: #0f2418;
}

.contact-form select.form-control:focus {
    border-color: #1E8A3D;
    -webkit-box-shadow: 0 0 0 3px rgba(30, 138, 61, 0.12);
    box-shadow: 0 0 0 3px rgba(30, 138, 61, 0.12);
    outline: 0;
}

/* Contact section fits a laptop screen (>= 992px, where the illustration shows).
   At 1440x900 the section was ~770px — the whole viewport under the header.
   What it spent that on, besides the form itself (trimmed above):
     - the template's 54px gap under every section heading; 28px here, since the
       form is the heading's own content, not a new block;
     - 72px of bottom padding under a centred button that already has air; 48px;
     - the illustration: contact-bg-1.png (850x854) was sized to 47% of the WIDTH,
       so it stayed ~680px tall however short the section got, and a shorter
       section would have cut the figure off at the knees. Sized to the section's
       HEIGHT instead, it shrinks with the content and always shows whole.
   The heading also got wider columns in LandingPage.jsx, so it holds one line.
   `.bg-1` in the selector outranks the plain `#contact-area` padding rule in the
   (min-width: 768px) block further down, which would otherwise win on order. */
@media only screen and (min-width: 992px) {
    #contact-area.bg-1 {
        padding-bottom: 48px;
        background-size: auto 100%;
    }

    #contact-area .section-heading {
        margin-bottom: 28px;
    }
}

/* Hamburger icon dark on the white bar. */
.navbar-toggler span {
    color: #0f2418;
}

/* Mobile dropdown goes white too, so the now-dark links stay readable. */
@media only screen and (max-width: 991px) {
    #header #navbarContent {
        background: #fff;
    }
}

/*-------------------------------------------------------------------------------------
    hamburger tap target

    The menu "opened sometimes and not others" on phones. The React state that
    owns the panel is deterministic — if the button's click fires, the class
    flips — so the misses were taps that never landed on the button at all.

    Bootstrap gives .navbar-toggler `padding: .25rem .75rem` and the theme sizes
    the glyph at 30px, which works out to a ~38x54px box whose visible ink is
    only ~24px wide. That is under the 44px minimum every mobile HIG asks for,
    and a near-miss is silent: nothing happens, the user taps again, and the
    second tap (which does land) reads as "it finally worked" — or, if the first
    one landed after all, the pair toggles open-then-closed and reads as "it
    didn't open".

    So: a real 48x48 target with the glyph centred in it, and the inner span/<i>
    made pointer-transparent so every hit inside the box is the button itself.
    `touch-action: manipulation` opts out of double-tap-to-zoom, which is what
    makes the browser hold a tap back before dispatching the click.
---------------------------------------------------------------------------------------*/

.navbar-toggler {
    position: relative;
    z-index: 12;
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    width: 48px;
    height: 48px;
    padding: 0;
    border: 0;
    background: none;
    -ms-touch-action: manipulation;
    touch-action: manipulation;
    -webkit-tap-highlight-color: transparent;
    cursor: pointer;
}

/* Nothing inside the button competes for the tap — the whole 48px box is one
   hit area, and event.target is always the <button>. */
.navbar-toggler span,
.navbar-toggler span i {
    pointer-events: none;
    line-height: 1;
}

/* Bootstrap leaves the default focus ring off; give keyboard users a visible
   one without adding a border on tap (:focus-visible skips mouse/touch). */
.navbar-toggler:focus {
    outline: 0;
}

.navbar-toggler:focus-visible {
    outline: 2px solid #1E8A3D;
    outline-offset: 2px;
    border-radius: 6px;
}

/* Pressed feedback, so a tap that did land is never ambiguous. */
.navbar-toggler:active {
    background: rgba(15, 36, 24, 0.06);
    border-radius: 6px;
}

/*-------------------------------------------------------------------------------------
    equal-height capability cards — #capabilities-area

    Card heights varied with body-text length. Bootstrap flex rows already stretch
    the columns equal; make each card fill its column so every card in a row matches
    the tallest. Scoped to the card row (:not(.about-info)) so the stats row below
    is untouched.
---------------------------------------------------------------------------------------*/

#capabilities-area .row:not(.about-info)>[class*="col-"] {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
}

#capabilities-area .core-feature-single {
    width: 100%;
}

#capabilities-area .core-feature-single-item {
    height: 100%;
}

/*-------------------------------------------------------------------------------------
    core-feature icons — lucide (SVG)

    The "data foundation" cards now render lucide-react SVGs instead of the icon
    font. Flex-centre the SVG in the gradient circle (the design's line-height
    centring only works for a font glyph) and paint it white via currentColor.
    Scoped to #core-feature-area so the icon-font sections are untouched.
---------------------------------------------------------------------------------------*/

#core-feature-area .core-feature-single-item .icon,
#capabilities-area .core-feature-single-item .icon,
#security-area .core-feature-single-item .icon {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
}

/* Follow the circle's own `color` (white on the coloured circle normally, brand
   colour once the circle flips white on hover) rather than pinning the SVG
   white — pinning made it white-on-white and vanish on hover. lucide strokes
   with currentColor, and `.icon` already sets color:#fff, so inherit is enough. */
#core-feature-area .core-feature-single-item .icon svg,
#security-area .core-feature-single-item .icon svg {
    color: inherit;
}

/* Solid glyphs on hover. When the card fills, the icon disc turns white, and an
   outline-only glyph on it looked unfinished. The core-feature icons are local
   SVGs in LandingPage.jsx (SolidIcon) with each shape tagged: `.dn-fill` shapes
   fill with the glyph colour, `.dn-cut` shapes stroke white (the disc colour) so
   lines drawn over a filled shape — the database lid and band, the shield's
   check — still show as cut-outs. Untagged open line-work stays as it is. */
.core-feature-single:hover .core-feature-single-item .icon svg.dn-icon-solid .dn-fill {
    fill: currentColor;
}

.core-feature-single:hover .core-feature-single-item .icon svg.dn-icon-solid .dn-cut {
    stroke: #fff;
}

/* Hero on phones — the design only reduces the generic `h1` (to 36px) and never
   touches the long hero sentence, the h4 sub-copy, or these 72px logo badges,
   so all three read oversized on a phone. Scale them for the hero specifically;
   `.caption h1` (0,1,1) still beats the design's `h1` (0,0,1) inside the query. */
@media only screen and (max-width: 767px) {

    .caption h1 {
        font-size: 30px;
        line-height: 38px;
    }

    .caption h4 {
        font-size: 16px;
        line-height: 26px;
    }

    .caption-download-btns.product-logos li a {
        width: 56px;
        height: 56px;
    }

    .caption-download-btns.product-logos li a img {
        padding: 7px;
    }
}

@media only screen and (max-width: 479px) {

    .caption h1 {
        font-size: 26px;
        line-height: 34px;
    }

    .caption-download-btns.product-logos li a {
        width: 50px;
        height: 50px;
        margin: 0 4px;
    }
}

/*-------------------------------------------------------------------------------------
    tailwind reconciliation
---------------------------------------------------------------------------------------*/

/* Tailwind ships a `.collapse` utility meaning `visibility: collapse`, and it
   emits it because the word "collapse" appears in prose elsewhere in the app —
   so excluding this page from Tailwind's source scan doesn't prevent it.
   Bootstrap's own `.collapse` only ever sets `display`, so it has no rule to
   win with, and the utility silently blanked the navbar and the FAQ answers.
   Bootstrap drives collapse state via `display`; visibility is never its job. */
.collapse {
    visibility: visible;
}

/* Tailwind's preflight also forces `img { display: block }`, but this design is
   built on Bootstrap's reboot, which leaves images inline. With block, an icon
   sitting inline before its label breaks onto its own line — the Play Store
   button grew 18px taller than the reference. Scoped to the design's own
   containers so React overlays (AuthDialog) keep Tailwind's rules. */
#header img,
#footer img,
section img {
    display: inline;
    vertical-align: middle;
}

/*-------------------------------------------------------------------------------------
    shared tokens

    Everything below reuses the design's existing vocabulary — the
    core-feature card shadow/radius, the green→blue icon gradient, #047857
    eyebrows, #4a5a52 body copy — so the added sections read as original.
---------------------------------------------------------------------------------------*/

.dn-card {
    background-color: #fff;
    border-radius: 4px;
    -webkit-box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    -webkit-transition: 0.3s;
    transition: 0.3s;
}

.dn-card:hover {
    -webkit-transform: translateY(-6px);
    transform: translateY(-6px);
    -webkit-box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
    box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
}

/*-------------------------------------------------------------------------------------
    new section spacing — matches #core-feature-area's 112/118 rhythm
---------------------------------------------------------------------------------------*/

#capabilities-area,
#formats-area,
#deploy-area,
#industries-area,
#comparison-area,
#security-area {
    padding: 42px 0 28px;
    position: relative;
    overflow: hidden;
    background-repeat: no-repeat;
    /* Deliberately not `contain`: these sections are far taller than
       #core-feature-area, and contain would scale the blob to full bleed. */
    background-size: 38% auto;
}

/*-------------------------------------------------------------------------------------
    section backdrops — the same soft blob + drifting bubbles the original
    sections use (.core-feature-circle, .about-area-circle, …). Each section
    gets its own blob, corner and bubble placement so none reads as a repeat.
---------------------------------------------------------------------------------------*/

#capabilities-area.bg-1 .capabilities-area-circle img,
#formats-area.bg-1 .formats-area-circle img,
#deploy-area.bg-1 .deploy-area-circle img,
#industries-area.bg-1 .industries-area-circle img,
#comparison-area.bg-1 .comparison-area-circle img,
#security-area.bg-1 .security-area-circle img {
    position: absolute;
    opacity: 0.5;
    -webkit-animation: zoominoutsinglefeatured 4s infinite;
    animation: zoominoutsinglefeatured 4s infinite;
}

/* capabilities — blob top-left, bubbles down the left gutter */
#capabilities-area.bg-1 {
    background-image: url(../images/feature-bg-1.png);
    background-position: top left;
    background-size: 40% auto;
}

#capabilities-area.bg-1 .capabilities-area-circle .circle1 {
    left: 3%;
    top: 9%;
    width: 3%;
}

#capabilities-area.bg-1 .capabilities-area-circle .circle2 {
    left: 8%;
    top: 30%;
    width: 5%;
}

#capabilities-area.bg-1 .capabilities-area-circle .circle3 {
    right: 5%;
    top: 14%;
    width: 3%;
}

/* formats — blob top-right, one large bubble left, one small right */
#formats-area.bg-1 {
    background-image: url(../images/awesome-feat-bg-1.png);
    background-position: top right;
    background-size: 34% auto;
}

#formats-area.bg-1 .formats-area-circle .circle1 {
    left: 4%;
    top: 26%;
    width: 5%;
}

#formats-area.bg-1 .formats-area-circle .circle2 {
    right: 7%;
    bottom: 16%;
    width: 3%;
}

/* deployment — blob bottom-left, bubbles on the right */
#deploy-area.bg-1 {
    background-image: url(../images/feature-bg-1.png);
    background-position: bottom left;
    background-size: 38% auto;
}

#deploy-area.bg-1 .deploy-area-circle .circle1 {
    right: 6%;
    top: 12%;
    width: 3%;
}

#deploy-area.bg-1 .deploy-area-circle .circle2 {
    right: 12%;
    bottom: 14%;
    width: 5%;
}

/* industries — bubbles only; the card grid already fills the section */
#industries-area.bg-1 .industries-area-circle .circle1 {
    left: 3%;
    top: 10%;
    width: 3%;
}

#industries-area.bg-1 .industries-area-circle .circle2 {
    right: 2%;
    top: 44%;
    width: 5%;
}

#industries-area.bg-1 .industries-area-circle .circle3 {
    left: 5%;
    bottom: 10%;
    width: 2.5%;
}

/* comparison — blob top-left, bubbles framing the table */
#comparison-area.bg-1 {
    background-image: url(../images/feature-bg-1.png);
    background-position: top left;
    background-size: 32% auto;
}

#comparison-area.bg-1 .comparison-area-circle .circle1 {
    right: 4%;
    top: 18%;
    width: 5%;
}

#comparison-area.bg-1 .comparison-area-circle .circle2 {
    left: 4%;
    bottom: 18%;
    width: 3%;
}

/* security — blob top-right, mirrors the capabilities grid it echoes */
#security-area.bg-1 {
    background-image: url(../images/feature-bg-1.png);
    background-position: top right;
    background-size: 40% auto;
}

#security-area.bg-1 .security-area-circle .circle1 {
    left: 4%;
    top: 16%;
    width: 3%;
}

#security-area.bg-1 .security-area-circle .circle2 {
    right: 6%;
    bottom: 14%;
    width: 5%;
}

/*-------------------------------------------------------------------------------------
    deployment chips
---------------------------------------------------------------------------------------*/

.chip-single {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    padding: 20px;
    margin-bottom: 30px;
    /* Bootstrap rows are flex, so stretching to the column makes every chip in a
       row the same height regardless of how many lines its role label wraps to. */
    height: calc(100% - 30px);
}

/* Centred with flex, not text-align: the app's Tailwind preflight forces
   `img { display: block }` onto this page, which would pin a logo to the
   circle's top-left corner. Flex centring is immune to that. */
.chip-single .icon {
    width: 58px;
    height: 58px;
    border-radius: 50%;
    -ms-flex-negative: 0;
    flex-shrink: 0;
    margin-right: 16px;
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    background-image: -webkit-gradient(linear, left top, right top, from(rgb(30, 138, 61)), to(rgb(31, 95, 212)));
    background-image: linear-gradient(90deg, rgb(30, 138, 61) 0%, rgb(31, 95, 212) 100%);
    -webkit-box-shadow: 0px 8px 15px -5px #047857;
    box-shadow: 0px 8px 15px -5px #047857;
}

.chip-single .icon i {
    font-size: 26px;
    color: #fff;
    line-height: 1;
}


.chip-single .content {
    min-width: 0;
}

.chip-single .content h3 {
    font-size: 18px;
    line-height: 26px;
    font-weight: 600;
    color: #052e1a;
    margin-bottom: 2px;
}

.chip-single .content p {
    font-size: 14px;
    line-height: 22px;
    margin-bottom: 0;
}

/*-------------------------------------------------------------------------------------
    data format cards
---------------------------------------------------------------------------------------*/

.format-single {
    padding: 34px 30px;
    height: 100%;
}

.format-single .badge-tag {
    display: inline-block;
    font-family: 'IBM Plex Mono', monospace;
    font-size: 11px;
    font-weight: 600;
    letter-spacing: 0.08em;
    text-transform: uppercase;
    padding: 5px 12px;
    border-radius: 20px;
    margin-bottom: 18px;
    background-color: #eef2ef;
    color: #4a5a52;
}

.format-single h3 {
    font-size: 22px;
    line-height: 32px;
    font-weight: 600;
    color: #052e1a;
    margin-bottom: 8px;
}

.format-single p {
    margin-bottom: 0;
}

/* The default format gets the brand gradient border treatment — same role the
   `.highlighted` pricing table plays. */
.format-single.featured {
    border-top: 3px solid #1E8A3D;
}

.format-single.featured .badge-tag {
    background-image: -webkit-gradient(linear, left top, right top, from(rgb(30, 138, 61)), to(rgb(31, 95, 212)));
    background-image: linear-gradient(90deg, rgb(30, 138, 61) 0%, rgb(31, 95, 212) 100%);
    color: #fff;
}

/*-------------------------------------------------------------------------------------
    industry cards
---------------------------------------------------------------------------------------*/

.industry-single {
    padding: 34px 30px;
    margin-bottom: 30px;
    height: calc(100% - 30px);
}

.industry-single .industry-head {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    margin-bottom: 24px;
}

.industry-single .industry-head .icon {
    width: 58px;
    height: 58px;
    border-radius: 50%;
    -ms-flex-negative: 0;
    flex-shrink: 0;
    margin-right: 16px;
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    background-image: -webkit-gradient(linear, left top, right top, from(rgb(30, 138, 61)), to(rgb(31, 95, 212)));
    background-image: linear-gradient(90deg, rgb(30, 138, 61) 0%, rgb(31, 95, 212) 100%);
    -webkit-box-shadow: 0px 8px 15px -5px #047857;
    box-shadow: 0px 8px 15px -5px #047857;
}

.industry-single .industry-head .icon i {
    font-size: 26px;
    color: #fff;
    line-height: 1;
}

.industry-single .industry-head h3 {
    font-size: 22px;
    line-height: 30px;
    font-weight: 600;
    color: #052e1a;
    margin-bottom: 0;
}

.industry-single .industry-metric {
    border: 1px solid #e6ece8;
    border-radius: 4px;
    padding: 16px 18px;
    margin-bottom: 24px;
    /* Keeps the pair level when one label wraps to a second line. */
    height: calc(100% - 24px);
}

.industry-single .industry-metric h4 {
    font-size: 28px;
    line-height: 36px;
    font-weight: 700;
    color: #047857;
    margin-bottom: 2px;
}

.industry-single .industry-metric p {
    font-family: 'IBM Plex Mono', monospace;
    font-size: 11px;
    line-height: 16px;
    letter-spacing: 0.06em;
    text-transform: uppercase;
    color: #6b7c73;
    margin-bottom: 0;
}

.industry-single ul li {
    position: relative;
    padding-left: 26px;
    margin-bottom: 10px;
    font-family: 'Inter', sans-serif;
    font-size: 15px;
    line-height: 24px;
    color: #4a5a52;
}

.industry-single ul li:last-child {
    margin-bottom: 0;
}

.industry-single ul li i {
    position: absolute;
    left: 0;
    top: 5px;
    color: #1E8A3D;
    font-size: 14px;
}

/*-------------------------------------------------------------------------------------
    comparison table
---------------------------------------------------------------------------------------*/

.compare-wrap {
    overflow-x: auto;
    /* Only two columns remain, so a full-width card left big empty margins on
       either side of the table. Shrink the card to the table and centre it. */
    width: -webkit-fit-content;
    width: fit-content;
    max-width: 100%;
    margin: 0 auto;
}

.compare-table {
    /* Only two columns remain (Feature + DataNature), so a 100%-wide table left
       the content stranded on the left. Size to content and centre the whole
       table in the section instead. */
    width: auto;
    min-width: 460px;
    margin: 0 auto;
    border-collapse: collapse;
    font-family: 'Inter', sans-serif;
}

.compare-table th,
.compare-table td {
    padding: 16px 20px;
    text-align: left;
    border-bottom: 1px solid #e6ece8;
}

.compare-table thead th {
    font-size: 13px;
    font-weight: 600;
    color: #6b7c73;
    text-transform: uppercase;
    letter-spacing: 0.06em;
}

.compare-table tbody td {
    font-size: 14px;
    line-height: 22px;
    color: #4a5a52;
}

.compare-table tbody th {
    font-size: 15px;
    font-weight: 600;
    color: #052e1a;
}

.compare-table tbody tr:hover th,
.compare-table tbody tr:hover td {
    background-color: #f6f9f6;
}

.compare-table tbody tr:last-child th,
.compare-table tbody tr:last-child td {
    border-bottom: 0;
}

/* The DataNature column is the recommended one — same tinted-band idea the
   `.price-tbl-single.highlighted` table uses. */
.compare-table .col-dn {
    background-color: rgba(30, 138, 61, 0.07);
    border-left: 1px solid rgba(30, 138, 61, 0.28);
    border-right: 1px solid rgba(30, 138, 61, 0.28);
    /* Centre the DataNature values within the highlighted band. */
    text-align: center;
}

.compare-table thead .col-dn {
    color: #047857;
    font-weight: 700;
    border-bottom: 2px solid #1E8A3D;
}

.compare-table tbody .col-dn {
    color: #047857;
    font-weight: 600;
}

.compare-table tbody tr:hover .col-dn {
    background-color: rgba(30, 138, 61, 0.14);
}

.compare-table tbody tr:last-child .col-dn {
    border-bottom: 2px solid #1E8A3D;
}

.compare-table .col-dn i {
    margin-right: 6px;
    color: #1E8A3D;
}

/*-------------------------------------------------------------------------------------
    responsive — follows the same breakpoints and 80/75px section padding
    that responsive.css applies to #core-feature-area
---------------------------------------------------------------------------------------*/

@media only screen and (min-width: 480px) and (max-width: 767px) {

    #capabilities-area,
    #tools-area,
    #formats-area,
    #deploy-area,
    #industries-area,
    #comparison-area,
    #security-area {
        padding: 80px 0 50px;
    }
}

@media only screen and (min-width: 360px) and (max-width: 479px) {

    #capabilities-area,
    #tools-area,
    #formats-area,
    #deploy-area,
    #industries-area,
    #comparison-area,
    #security-area {
        padding: 75px 0 50px;
    }
}

@media only screen and (max-width: 359px) {

    #capabilities-area,
    #tools-area,
    #formats-area,
    #deploy-area,
    #industries-area,
    #comparison-area,
    #security-area {
        padding: 75px 0 50px;
    }
}

@media only screen and (max-width: 767px) {

    .format-single,
    .industry-single {
        margin-bottom: 30px;
        height: auto;
    }

    .industry-single .industry-head h3 {
        font-size: 19px;
        line-height: 27px;
    }
}

/* ── Stack section: laptop-framed desktop mockups ─────────────────────────────
   The base theme sizes .awesome-feat-img for a portrait phone (max-width 400px,
   pushed right via margin-left:36%). A laptop screenshot is landscape, so give
   the .is-desktop variant more width and pull it back left to sit centred over
   the section. Phone items (Voir) are untouched. */
.awesome-feat-img .feat-screen-single.is-desktop {
    margin-left: -34%;
    margin-top: 60px;
}

.awesome-feat-img .feat-screen-single.is-desktop img {
    max-width: 660px;
    width: 100%;
}

@media only screen and (max-width: 991px) {
    .awesome-feat-img .feat-screen-single.is-desktop {
        margin-left: 0;
        margin-top: 0;
    }

    .awesome-feat-img .feat-screen-single.is-desktop img {
        max-width: 100%;
    }
}

/* ── Stack section: swap the pale-green blob for the brand lime→blue gradient ──
   Keeps the original organic blob shape by masking the gradient with the same
   awesome-feat-bg-1.png, at low opacity so it reads as a soft branded wash (not
   a saturated panel). Brand hexes are inlined because --lime-deep/--blue live in
   .dn-welcome scope, not here. Content is lifted above the blob with z-index. */
#awesome-feat-area.bg-1 {
    background-image: none;
}

#awesome-feat-area.bg-1::before {
    content: "";
    position: absolute;
    inset: 0;
    z-index: 0;
    pointer-events: none;
    /* Brand lime→blue, the exact combo from the welcome page (.dn-welcome
       --lime-deep → --blue). Both colours read clearly at this opacity. */
    background: linear-gradient(140deg, #1E8A3D 0%, #1F5FD4 100%);
    -webkit-mask: url(../images/awesome-feat-bg-1.png) 0 40% / 45% no-repeat;
    mask: url(../images/awesome-feat-bg-1.png) 0 40% / 45% no-repeat;
    opacity: 0.38;
}

#awesome-feat-area.bg-1>.container {
    position: relative;
    z-index: 1;
}

/* ── Footer ground: a flat brand gradient, not the theme's shaped PNG ─────────
   footer-bg-1.png is a solid green shape with a diagonal cut across its
   top-left. It was previously used as a MASK over the brand gradient, sized
   `cover` so the shape would fill the footer at any width.

   That only holds while the footer is tall. With the "Transform your business"
   CTA parked, the footer is now short and wide, so `cover` scales the shape by
   height and the diagonal cut lands straight across the first widget column —
   PLATFORM, DataNature and AI360 Studio were white text on the bare white page,
   i.e. invisible.

   A masked shape can never be made safe here, because the cut's position
   depends on the footer's aspect ratio, which changes with the link count and
   with whether the CTA is parked. So the gradient is painted flat across the
   whole element: every column sits on it at every size, and the top edge is a
   straight line rather than the theme's curve. */
#footer.bg-1 {
    /* Green end to end, on the hero's own range rather than an invented one:
       the hero blob's brightest green measures #0AAF26 and its darkest #003108,
       so the footer runs #0AA524 -> #00310A along the same 140deg the theme
       used. What changed is only the far stop — it was #1F5FD4, the last blue
       surface left on the page. */
    background-image: -webkit-gradient(linear, left top, right bottom, from(#0AA524), to(#00310A));
    background-image: linear-gradient(140deg, #0AA524 0%, #10702A 46%, #00310A 100%);
}

#footer {
    position: relative;
}

#footer>.container {
    position: relative;
    z-index: 1;
}

/* ── Hero: full-bleed pure-green background image ─────────────────────────
   home-bg-green.png is home-bg-1.png with the teal ground hue-mapped to brand
   green (hue 130); the illustration and the transparent right wedge are
   untouched.

   home-bg-green-overview.png is that file with the WHOLE HANDSET replaced by the
   real Command Center dashboard. The phone was never a separate element — it is
   painted into this raster — so the swap had to happen in pixels:

   - The handset's front face is a parallelogram (pure vertical shear), measured
     off the raster at TL (1466,257) with edge vectors (212,87) and (0,506).
     Scanning alpha outward puts the body's right edge at s=1.10 of that face and
     its bottom at t=1.03, and that footprint is erased and replaced by the
     dashboard panel, affine-warped onto it so it stands at the scene's own
     angle, with a thin white edge, rounded corners and a soft shadow.
   - The screenshot is cropped to the panel's 0.484 aspect before warping, not
     squeezed into it. A 3136x3844 desktop capture scaled whole would put every
     label below a pixel at this hero's render size, so it is cropped to the
     top-left 1300px — header, both KPI rows and the throughput chart.
   - Erasing the handset exposes background it had covered. Most of that is the
     transparent wedge; a thin corner is the green blob, whose edge is hidden
     behind the handset, so it comes from a quadratic fitted to the edge where it
     IS visible (above the handset, and below where it clears the footprint).
   - Four things stand in front of the handset and had to survive. The two
     figures are separated by hue: the screen art is green, white and a lavender
     that never passes ~8% saturation. That test is windowed to where the figures
     are, because the handset's own side strip measures sat 0.27 at hue 216 and
     would otherwise protect itself. The blue side of that cut starts at 205deg,
     not 185: the old screen's pale cards are CYAN (hue 194, sat 0.20), and
     inside a 185deg cut fill_holes welded one onto the woman and carried it
     through as though it were part of her. Everything actually on a figure is
     well clear of 205 — denim and navy at 225-240deg, skin and the pink top at
     0-30deg. The dark-green bar she lifts IS hers but is green, so the hue test
     cannot claim it; it is taken on its own, as the only strongly saturated
     green inside a small box around it.
     The podium and the paper stack are the same
     white as the handset and sit directly on it, sharing one connected bright
     region, so no colour or connectivity rule can cut them out — they are traced
     as two polygons instead, then intersected with the light pixels inside them
     so the traced edges don't drag along a sliver of the old screen.

   home-bg-green.png is kept beside it. To go back to the illustrated phone,
   point the three url() references below and in style.css at that file instead. It is a full opaque rectangle (was a shaped/transparent PNG
   sized `auto` + positioned bottom). Cover-fit it so it fills the hero edge to
   edge; centre-right keeps the isometric illustration in frame on the right. */
#home-area.bg-1 {
    background-size: cover;
    background-position: center right;
}

/* Stack section: phone mockups (DocuContext, Voir) read a touch large at the
   theme's 400px. Scale the non-desktop screens down; laptop images keep their
   own 660px rule above, so they're unaffected. */
.awesome-feat-img .feat-screen-single:not(.is-desktop) img {
    max-width: 320px;
}

/* Capability cards sat too close. Widen the horizontal gutter (matching the row's
   negative margin so the outer edges stay aligned to the container) and add a
   vertical gap between the two rows. Scoped to the card row, not the stats row. */
#capabilities-area .row:not(.about-info) {
    margin-left: -18px;
    margin-right: -18px;
}

#capabilities-area .row:not(.about-info)>[class*="col-"] {
    padding-left: 18px;
    padding-right: 18px;
    margin-bottom: 36px;
}

/* Hero heading + subhead: always white, hover or not. A hover sheen used to
   clip an animated green -> blue gradient to the h1's glyphs; it read as the
   headline changing colour on the green hero, so it is gone. `background-clip`
   is reset alongside the fill colour so no clipped-gradient state can leak back
   in, and the h4 is pinned for the same reason. */
#home-area .caption h1,
#home-area .caption h4,
#home-area .caption:hover h1,
#home-area .caption:hover h4,
#home-area .caption:hover h1.text-white {
    color: #fff;
    -webkit-text-fill-color: #fff;
    background-image: none;
    -webkit-background-clip: border-box;
    background-clip: border-box;
    animation: none;
}

/*-------------------------------------------------------------------------------------
    newsletter subscribe button — mobile

    Below 480px responsive.css restacks the button under the input with
    `position: unset`. The desktop rule it inherits is built for an ABSOLUTE
    button overlaid on the input:

        .newsletter-form button { height: 100%; padding: 0 46px; }

    Once the button is static, `height: 100%` has no sized parent to resolve
    against and computes to auto — and with zero vertical padding that leaves a
    button only as tall as its text, a thin sliver that is hard to hit and looks
    broken. Give it real height and padding back, and restore the 8px radius the
    wrapper can no longer clip (it drops to border-radius:0 at this width).

    Scoped to 479px to match exactly where the restacking happens; above that the
    absolute overlay is correct and height:100% is what we want.
---------------------------------------------------------------------------------------*/

@media only screen and (max-width: 479px) {
    .newsletter-form .newsletter-input-bx button {
        height: auto;
        min-height: 52px;
        padding: 15px 24px;
        border-radius: 8px;
        font-size: 15px;
        line-height: 1.2;
    }

    /* Match the input to it so the pair reads as one control. */
    .newsletter-form .newsletter-input-bx input {
        min-height: 52px;
        border-radius: 8px;
    }
}

/*-------------------------------------------------------------------------------------
    hero readability — mobile

    On desktop the hero artwork is anchored to the bottom, well clear of the
    headline:

        #home-area.bg-1 { background-position: bottom; }

    responsive.css re-anchors it to `center` on small screens, which slides the
    busy, light-heavy illustration directly behind the white h1/h4 — the text
    becomes unreadable wherever it crosses a pale part of the artwork.

    Rather than hide the artwork, layer a dark scrim over it: the illustration
    still reads through, but the copy always has a dark ground beneath it. The
    gradient is strongest at the top (where the headline sits) and eases off
    lower down so the graphic keeps its presence.
---------------------------------------------------------------------------------------*/

/* Raised from 767px to 991px when the product shot went in. The shot is hidden
   below 992px and the copy goes full width there, which runs the headline past
   the green blob's curved edge and onto the white wedge — white text on white.
   The scrim is exactly the fix for that, so it now covers the whole range where
   the copy is full width rather than only phones. */
@media only screen and (max-width: 991px) {
    #home-area.bg-1 {
        background-image:
            -webkit-gradient(linear, left top, left bottom,
                from(rgba(3, 26, 20, 0.88)), color-stop(50%, rgba(3, 26, 20, 0.74)), to(rgba(3, 26, 20, 0.45))),
            url(../images/home-bg-green-clean.png);
        background-image:
            linear-gradient(180deg,
                rgba(3, 26, 20, 0.88) 0%,
                rgba(3, 26, 20, 0.74) 50%,
                rgba(3, 26, 20, 0.45) 100%),
            url(../images/home-bg-green-clean.png);
        background-repeat: no-repeat, no-repeat;
        background-position: center, center;
        background-size: cover, auto;
        /* The artwork is a shaped PNG: past the blob's curved edge it is
           transparent, so the white page showed through and the scrim turned
           that corner GREY — a hard grey wedge across the bottom right. Put the
           blob's own mid green behind it (sampled at #045E14) so the scrim has
           green to darken there too and the edge stops reading as a seam. */
        background-color: #045e14;
    }

    /* The decorative blobs sit above the scrim and re-introduce bright patches
       right where the headline is. Push them back and soften them. */
    #home-area.bg-1 .home-bg-circle .circle1,
    #home-area.bg-1 .home-bg-circle .circle2 {
        opacity: 0.25;
    }

    /* A touch more weight helps the headline hold up over a busy ground. */
    .caption h1 {
        text-shadow: 0 2px 12px rgba(0, 0, 0, 0.45);
    }

    .caption h4 {
        text-shadow: 0 1px 8px rgba(0, 0, 0, 0.4);
    }
}

/*-------------------------------------------------------------------------------------
    footer — mobile vertical rhythm

    Below 768px the four `col-lg-3 col-md-6` widgets lose both their grid classes
    and fall back to the Bootstrap base rule (width:100%), so they stack one per
    row. Twenty-seven links at 13px of padding each, plus four 20px headings and
    a 40px gap per widget, is roughly 1700px of near-empty footer to scroll past
    — and the theme's block padding (#footer's 230px top, .footer-cont's 80px)
    is still desktop-scale on top of that.

    Two fixes, no markup change:
      • put the widgets back on a 2-up grid, which halves the column height;
      • tighten the per-row and per-block padding to phone scale.

    #footer's top padding stays large on purpose: .get-started is pulled up
    -170px into the section above it, so the padding is what keeps the link
    columns clear of that box. 200px leaves the same ~30px of breathing room the
    tighter box now needs.
---------------------------------------------------------------------------------------*/

@media only screen and (max-width: 767px) {
    #footer {
        padding-top: 200px;
    }

    .get-started {
        padding: 36px 22px;
    }

    .footer-cont {
        padding: 32px 0 10px;
    }

    /* Two widgets per row. The columns carry Bootstrap's base 15px gutters at
       every width, so they only need a flex basis. */
    .footer-cont .footer-col {
        -ms-flex: 0 0 50%;
        flex: 0 0 50%;
        max-width: 50%;
    }

    .footer-widget {
        margin-bottom: 26px;
    }

    .footer-widget h3 {
        font-size: 17px;
        line-height: 24px;
        margin-bottom: 4px;
    }

    .footer-widget li {
        padding: 8px 0;
    }

    .footer-widget li a {
        font-size: 14px;
        line-height: 20px;
    }

    .footer-copyright {
        padding: 22px 0;
    }

    .footer-copyright p {
        font-size: 13px;
        line-height: 20px;
    }
}

/* Narrowest phones (<360px): a 50% column is only ~125px wide, which is not
   enough for the longest labels ("Enterprise Context Layer", "Accounts and
   Billing") at the sizes above — they wrap to two lines. Falling back to one
   column is the wrong trade (measured at 340px: ~1950px stacked against
   ~1280px two-up), so keep the grid and buy the width back from the gutters
   and the type instead. At 320px that brings every label back onto one line. */
@media only screen and (max-width: 359px) {
    .footer-cont .footer-col {
        padding-left: 8px;
        padding-right: 8px;
    }

    .footer-widget h3 {
        font-size: 15px;
    }

    .footer-widget li a {
        font-size: 13px;
        line-height: 18px;
    }

    .footer-widget li {
        padding: 7px 0;
    }
}

/*-------------------------------------------------------------------------------------
    mobile vertical rhythm — the whole page

    At 430px the home page measured 26,280px tall, and most of that was empty.
    Three separate causes, all of them "desktop numbers left running on a phone":

    1. THE 145px CARD GAP. `.core-feature-single` is a bare wrapper around the
       white card. responsive.css gives it `padding: 60px 30px 25px` in the
       480–767 band — on top of the card's own 60px top padding — and both the
       wrapper and its column carry `margin-bottom: 30px`. Stacked one-up, that
       put 25 + 30 + 30 + 60 = 145px of nothing between consecutive cards. It is
       the gap in every screenshot of #core-feature-area and #capabilities-area.

    2. CARDS SIZED FOR A GRID CELL. Inside the card, 60px of top padding and the
       icon's 50px bottom margin are proportionate to a 270px-wide desktop
       column; at full phone width they just make each card a screenful.

    3. SECTION PADDING. 75–118px top and 50–180px bottom per section, times
       nineteen sections, with a 54px gap under every heading.

    Everything here is spacing and type scale only — no layout, colour or
    component changes, so the desktop design is untouched above 767px.
---------------------------------------------------------------------------------------*/

@media only screen and (max-width: 767px) {

    /* ── 1. Section rhythm ─────────────────────────────────────────────────── */
    /* 44, not the theme's 75-118. Two adjacent sections contribute both their
       paddings to the visual break, so this is an ~88px band between the last
       line of one section and the heading of the next — measured, and about
       right for a phone. At 56 it was ~112-147px and read as a hole. */
    #awesome-feat-area,
    #core-feature-area,
    #about-area,
    #formats-area,
    #capabilities-area,
    #deploy-area,
    #comparison-area,
    #industries-area,
    #security-area,
    #video-area,
    #testimonial-area {
        padding-top: 44px;
        padding-bottom: 44px;
    }

    /* These four keep an asymmetric bottom: each has artwork or an overlapping
       panel living in that padding (the how-it-works illustration, the Voir
       carousel's phone frame, the app-download mockups). Trimmed, not removed. */
    /* how-work-bg-1.png is the section's own background, anchored bottom-right.
       It is 1075x1068 — near square — so any width-proportional size (the
       theme's `contain`, or a percentage) makes it TALLER as the viewport
       widens, while the copy above it gets SHORTER because the lines rewrap.
       The two therefore collide, and no single percentage fixes every width:
       at 78% the third step cleared it at 430px but was overrun at 760px.

       Pin the height instead. At a fixed 200px the artwork occupies the same
       band on every phone, so one bottom padding clears it everywhere — 210px,
       leaving ~10px between the last line and the top of the mockup. */
    #how-work-area {
        padding: 44px 0 210px;
        background-size: auto 200px;
        /* The theme anchors it bottom-RIGHT, which on a phone clipped it against
           the edge and left it off-axis under three centred steps. */
        background-position: center bottom;
    }

    /* The 180px bottom the theme reserved here held the desktop artwork that is
       now hidden at this width, and the iPhone frame is already display:none
       below 992px — nothing overhangs, so it is pure dead space. */
    #screenshot-area {
        padding: 44px 0 44px;
    }

    #app-download-area {
        padding-top: 48px;
    }

    #contact-area {
        padding: 0 0 28px;
    }

    /* The theme's 80px top margin sat on top of the section padding AND the
       previous section's, stacking to a 167px break. The padding alone is the
       break. */
    #faq-area {
        margin: 0 0 16px;
        padding: 0 0 36px;
    }

    #newsletter-area {
        padding: 44px 0;
        margin-bottom: 24px;
    }

    .section-heading {
        margin-bottom: 30px;
    }

    /* Hero: the theme reserves 150px above the headline and 105px below it.
       The top figure exists to clear the fixed header, which measures 83px —
       120px keeps a comfortable 37px and stops the headline starting a third of
       the way down the screen. The 105px tail was the single largest empty band
       on the page (173px once the next section's padding was added). */
    .caption {
        padding: 120px 0 56px;
    }

    /* The section below already carries 44px of top padding; this margin just
       stacked on top of it. */
    #home-area.bg-1 {
        margin-bottom: 0;
    }

    .section-heading p {
        font-size: 15px;
        line-height: 24px;
    }

    /* ── 2. Feature + capability cards ─────────────────────────────────────── */

    /* Collapse the wrapper entirely — it exists to position the desktop
       hover-shapes, which are position:absolute and so unaffected. The single
       remaining margin is the whole card-to-card gap. */
    .core-feature-single {
        padding: 0;
        margin: 0 0 18px;
    }

    #core-feature-area .col-lg-3,
    #capabilities-area .row:not(.about-info)>[class*="col-"] {
        margin-bottom: 0;
    }

    /* Card interior at phone scale.

       The vertical numbers are set by the icon's decorative halo, not by the
       icon: `.icon:before` is a 125px disc offset top:-27px on a 70px icon, so
       it overhangs 27px above the icon box and 28px below it. Anything less
       than that as padding-top or icon margin-bottom puts the pale ring hard
       against the card edge and into the title. 44/42 leaves a balanced ~17px
       above the ring and ~14px between the ring and the h3. */
    .core-feature-single .core-feature-single-item,
    #core-feature-area .core-feature-single-item {
        padding: 44px 22px 28px;
    }

    .core-feature-single .core-feature-single-item .icon {
        margin: 0 auto 42px;
    }

    .core-feature-single .core-feature-single-item h3 {
        font-size: 20px;
        line-height: 28px;
    }

    /* ── 3. Repeated blocks in the remaining sections ──────────────────────── */
    .how-work-single {
        margin-bottom: 32px;
    }

    .counter-single {
        margin-bottom: 34px;
    }

    .about-info-single {
        margin-bottom: 16px;
    }

    .format-single,
    .industry-single {
        margin-bottom: 20px;
    }
}

/* ── Counter units ────────────────────────────────────────────────────────────
   custom.js runs jQuery counterUp on `.counter-single h2`, and the plugin
   animates by repeatedly overwriting the element with `.text()`. Anything
   inside the h2 is therefore destroyed on the first frame, and — worse — the
   plugin computes each frame as `parseInt(element.text() / n * f)`, so a single
   non-numeric character turns the whole sequence into NaN. "70%" rendered as a
   literal "NaN" on the page at every width.

   The number now lives alone in the h2 (so counterUp's arithmetic works) and
   the unit is painted from a data attribute, which `.text()` cannot reach. */
.counter-single h2[data-suffix]::after {
    content: attr(data-suffix);
}

/* ── "The numbers" block: colour it for the ground it actually sits on ────────
   On desktop this block sits on #video-area's dark teal panel, so the eyebrow
   needs the light treatment its sibling paragraph already uses — `.title h5`
   is #047857, the deep green meant for eyebrows on white, which measures about
   1.4:1 there and read as invisible.

   The h2 colour lives here rather than on a `.text-white` class in the markup:
   Bootstrap declares that utility `!important`, so the phone override below
   could not have won against it. */
#video-area .counter.title h5 {
    color: #8fe3b0;
}

#video-area .counter.title h2 {
    color: #fff;
}

/* ── #video-area: the curved wave is back ─────────────────────────────────────
   This section used to carry a straight full-bleed band painted on the
   counters' own `.row`, with `#video-area.bg-1 { background-image: none }`
   above it. That existed for one reason: the video circle was parked, which
   took away the 325px `.video.title` reserves, everything slid up, and the
   wave PNG — anchored to the section's BOTTOM — cut straight through the black
   "Measurable outcomes, not promises" copy.

   The circle is back in the markup (LandingPage.jsx), so the reserve is back,
   so the wave clears the copy again and the section matches the design: white
   behind "Proven impact", teal behind "The numbers" and the counters, with the
   curve running between them. Nothing here needs to override the theme any
   more — `#video-area.bg-1` paints counter-bg-1.png on its own.

   The light treatment for "The numbers" stays where it is, just above: that
   block sits on the band in this arrangement exactly as it did before.

   The band and the circle are green now, not teal — see the note below. */

/* ── #video-area artwork: teal/blue -> green ──────────────────────────────────
   Two rasters carried the last of the template's teal-and-blue into this
   section, and no CSS could reach either of them: the colour is baked into the
   pixels. Both are remapped the way the hero's home-bg-1.png was, and both are
   saved beside the originals rather than over them, so the source art is still
   in the repo:

   counter-bg-green.png (from counter-bg-1.png) — the wave behind the counters.
   Every saturated pixel in it sat in one hue family (192-195deg), so it gets
   the hero's exact treatment: hue pinned to 130, saturation and value kept, and
   the gradient, the curve and its antialiased edge come through untouched.

   video-bg-green.png (from video-bg.png) — the isometric circle. This one is an
   illustration, not a flat ground, so a single hue would have flattened it: 93%
   of its saturated pixels run a blue->cyan sweep (175-248deg), and that sweep IS
   the artwork's depth. It is mapped onto a green sweep of the same shape
   (122-152deg) instead, with two corrections. Saturation drops to 0.86, because
   green reads hotter than blue at equal HSV saturation. And each pixel is scaled
   back to the luminance it started with — luma weights green at 0.72 against
   blue's 0.07, so a straight hue rotation turned the circle neon and erased the
   shading. The yellow cubes, the pink and green screens and the white phone are
   outside the mapped band and are left exactly as they were.

   Everything the section draws over these two — the counters' white icon discs
   and their translucent halo rings — is painted in rgba white, so it followed
   the new ground with no change of its own. */


/* ── Voir section: keep the decorative orbit off the copy on phones ───────────
   `.screenshot-area-img` is position:absolute with a 50%-wide image floated
   right — a desktop composition that lands the solid green disc directly over
   the h2 and paragraph once the column goes full width. It carries no
   information, so drop it below the phone breakpoint rather than fight it. */
@media only screen and (max-width: 767px) {

    /* !important is required, not lazy: the element also carries Bootstrap's
       `.d-flex` utility, which is itself declared `display: flex !important`. */
    #screenshot-area.bg-1 .screenshot-area-img {
        display: none !important;
    }

    /* 95px of padding under a three-line block, on a phone. */
    .counter.title {
        padding-bottom: 32px;
    }

}

/* ── Video section: put the play-button circle back in normal flow on phones ──
   The theme centres `.video-cont` between the intro copy and the counters using
   position:absolute with a hand-tuned `top` per breakpoint, while `.video.title`
   reserves the space with a 350px bottom padding. Two fixed numbers against two
   fluid ones: the intro paragraph runs three lines at 430px and four at 320px,
   and the circle itself is 300px below 480px but 400px above it. Measured, the
   circle already crossed the paragraph at 320px and sat 184px over "The numbers"
   at 760px — the section only looked right in the band it was tuned in.

   `.video-cont` now sits between the two text blocks in the markup, so on
   phones it can simply be static and centred: the gaps above and below become
   ordinary margins that hold at every width. Desktop is untouched — the element
   stays absolute there, and absolute positioning ignores source order. */
@media only screen and (max-width: 767px) {
    .video-cont {
        position: static;
        margin: 8px auto 24px;
    }

    .video.title {
        padding-bottom: 0;
    }
}

/* The 325px `.video.title` reserve is live again — `.video-cont` is absolutely
   positioned, so that padding is the only thing holding its column open. It was
   zeroed here while the circle was out of the markup; both came back together.
   The phone block above still drops the reserve below 767px, where the circle
   moves into normal flow and carries its own margins. */

/* ── Footer CTA parked ───────────────────────────────────────────────────────
   The "Transform your business" box (.get-started) is commented out in
   LandingFooter.jsx. It normally hangs -170px up into the section above, and
   #footer's oversized top padding (230px desktop, 200px in the phone block
   further up this file) exists only to clear it. With the box gone that
   padding is just a blank band, so bring the footer back to ordinary section
   spacing. Delete this block when the CTA is restored. */
#footer {
    padding-top: 60px;
}

@media only screen and (max-width: 767px) {
    #footer {
        padding-top: 40px;
    }
}

/*-------------------------------------------------------------------------------------
    pricing page vertical rhythm — /pricing

    The page (src/pages/pricing.jsx) is inline-styled, so its section padding
    was a set of fixed desktop numbers that no media query could reach. Two of
    them read as holes:

      • ABOVE THE FIRST HEADING. The header is fixed and ~60px tall, and the
        page cleared it with 92px of padding on <main> — then the hero added
        another 72px on top. That is ~104px of empty white above the "Pricing"
        eyebrow, which is a third of a phone screen before any content.

      • BETWEEN THE PRICE CARD AND THE CALCULATOR. The tier section ended with
        96px of bottom padding and the estimator opened with 40px of top: a
        136px band of nothing between the $30/DCU card and "Estimate your
        spend", with no artwork or overlap living in it.

    Padding now lives here so the ≤767px block can trim it, matching the phone
    rhythm the landing page uses (56px sections, 30px under a heading).
---------------------------------------------------------------------------------------*/

/* Header clearance only — the hero supplies the breathing room below it. */
.dn-pricing-main {
    padding-top: 72px;
}

.dn-pricing-hero {
    padding: 40px 0 24px;
}

.dn-pricing-tier {
    padding: 24px 0 40px;
}

.dn-pricing-estimator {
    padding: 16px 0 72px;
}

/* Stacked below 992px the two estimator columns are siblings in a flex row with
   no gutter of their own, so the summary card sat flush against the storage
   card. (Above 992px they are side by side and this margin never applies.) */
@media only screen and (max-width: 991px) {
    .dn-pricing-summary-col {
        margin-top: 24px;
    }
}

@media only screen and (max-width: 767px) {
    .dn-pricing-main {
        padding-top: 64px;
    }

    .dn-pricing-hero {
        padding: 24px 0 12px;
    }

    .dn-pricing-tier {
        padding: 12px 0 0px;
    }

    .dn-pricing-estimator {
        padding: 16px 0 56px;
    }
}

/*-------------------------------------------------------------------------------------
    price badge — /pricing tier card

    The template's badge is a fixed 102px circle sitting behind an <h2> that it
    never measures. Its own demo prices are short ("$29"), but ours reads
    "$30/DCU": a 50px figure plus a 24px "$" superscript plus a 24px unit, all on
    one line — about 132px of text across a 102px circle, so the "$" and "/DCU"
    hung out over the white card either side.

    Fixed by laying the amount out as two centered lines — "$30", then the unit
    beneath it as a small caps label — and centering the circle on that stack
    instead of hanging it from a magic negative offset. The unit reads as a unit
    rather than as part of the number, and the badge now sizes off the type, so
    it holds whatever the price string is.
---------------------------------------------------------------------------------------*/

.dn-pricing-tier .price-tbl-single .price {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-orient: vertical;
    -webkit-box-direction: normal;
    -ms-flex-direction: column;
    flex-direction: column;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    min-height: 148px;
    margin: 0;
    padding: 8px 0 12px;
}

/* Centered on the stack above, so it no longer needs the template's per-
   breakpoint `top` nudges. */
.dn-pricing-tier .price-tbl-single .price-bg {
    width: 148px;
    height: 148px;
    top: 50%;
    -webkit-transform: translateY(-50%);
    transform: translateY(-50%);
}

.dn-pricing-tier .price-tbl-single .price h2 {
    margin: 0;
    font-size: 48px;
    line-height: 1;
}

/* "$" rides the top of the figure rather than the baseline. */
.dn-pricing-tier .price-tbl-single .price h2 sup {
    top: -0.45em;
    margin-right: 1px;
    font-size: 22px;
}

/* The unit drops to its own line — a label under the number, not a second
   number beside it. */
.dn-pricing-tier .price-tbl-single .price h2 span {
    display: block;
    margin-top: 10px;
    font-family: 'Poppins', sans-serif;
    font-size: 12px;
    font-weight: 600;
    line-height: 1;
    letter-spacing: 0.14em;
    text-transform: uppercase;
    opacity: 0.62;
}

/* Rupee amounts ("Rs.4,530") run wider than the badge at full size. */
.dn-pricing-tier .price-tbl-single .price h2.is-long {
    font-size: 38px;
}

/* Phones: the card narrows, so bring the badge and figure down with it. */
@media only screen and (max-width: 575px) {
    .dn-pricing-tier .price-tbl-single .price {
        min-height: 124px;
    }

    .dn-pricing-tier .price-tbl-single .price-bg {
        width: 124px;
        height: 124px;
    }

    .dn-pricing-tier .price-tbl-single .price h2 {
        font-size: 40px;
    }

    .dn-pricing-tier .price-tbl-single .price h2 sup {
        font-size: 19px;
    }

    .dn-pricing-tier .price-tbl-single .price h2.is-long {
        font-size: 32px;
    }
}

/*-------------------------------------------------------------------------------------
    desktop vertical rhythm (>= 768px)

    Same class of problem the phone block above solves, one breakpoint up, and
    made worse by the parked sections. Measured at 1440px, the empty bands
    between the last line of one section and the first of the next were:

        hero 310  ·  core-feature 202  ·  about 174  ·  video 176 / 170
        how-work 553  ·  screenshot 354  ·  faq 238  ·  footer 325

    Three causes, all of them the theme's own numbers:
      • .caption reserves 275px under the hero copy;
      • several sections carry 100-126px of bottom padding on top of the next
        section's own top padding, so each boundary pays twice;
      • #how-work-area and #screenshot-area reserve 410px and 220px for artwork
        that is either much smaller than the reserve or, since the video and
        app-download blocks were parked, no longer there at all.

    Desktop keeps more air than the phone block — the target here is a ~120px
    break between sections, not 88.
---------------------------------------------------------------------------------------*/

@media only screen and (min-width: 768px) {

    /* Hero: 230px above clears the fixed header with room to spare; 275px below
       was simply a hole between the copy and the next section. */
    .caption {
        padding: 170px 0 100px;
    }

    #core-feature-area {
        padding-bottom: 72px;
    }

    #about-area {
        padding-bottom: 56px;
    }

    #video-area {
        padding-top: 72px;
    }

    /* how-work-bg-1.png is 1075x1068 and sits bottom-right at natural size, so
       the theme reserves 410px for it. Pin the height as the phone block does —
       same reasoning, larger figure — and the reserve follows. */
    #how-work-area {
        padding: 72px 0 340px;
        background-size: auto 320px;
    }

    /* The 220px bottom held the parked app-download overlap. The iPhone frame
       that remains is absolutely positioned and does not need reserved flow. */
    #screenshot-area {
        padding: 72px 0 64px;
    }

    /* Bottom trimmed to 48px: with the last accordion card's dead 20px margin
       gone (see the faq -> contact block at the end of this file), 48 + the
       contact section's own 72px top lands on the ~120px break this block
       targets. The 64px top is already on target against #screenshot-area. */
    #faq-area {
        padding: 64px 0 48px;
    }

    #contact-area {
        padding: 72px 0 72px;
    }

    /* #footer's 60px top existed to clear the parked .get-started box, and
       .footer-cont adds another 115px on top of that. */
    #footer {
        padding-top: 28px;
    }

    .footer-cont {
        padding: 44px 0 40px;
    }
}


/*-------------------------------------------------------------------------------------
    how-it-works: reclaim the reserved artwork lane (>= 992px)
---------------------------------------------------------------------------------------*/

/* At lg the three steps are col-lg-3 with a leading offset — 9 of 12 columns —
   so the right-hand third of that row is empty, and beyond the container there
   is another gutter of nothing. how-work-bg-1.png is a BACKGROUND anchored
   `bottom right`, which means it grows UPWARD from the section's bottom edge:
   shrinking the bottom padding does not clip it, it just lets it ride up into
   that empty right-hand column instead of demanding a lane of its own.

   The 340px reserve in the >= 768px block was therefore buying a 320px image an
   exclusive band it never needed at this width, and paying for it with ~300px
   of blank white under the copy — the single worst boundary on the page, and
   far outside the ~120px break the rest of the desktop rhythm targets.

   768-991px keeps the full reserve: there the steps are col-md-4 and fill all
   twelve columns, so there is no empty corner for the artwork to occupy. */
@media only screen and (min-width: 992px) {
    #how-work-area {
        padding-bottom: 64px;
    }
}

/* Between 992px and the container's next step up, the right-hand quarter is
   only ~256px of clear space. The artwork is near-square (1075x1068), so at
   320px tall it is also ~320px wide and would push under the third step's
   text. Trim it to fit the gap rather than reinstating the padding. */
@media only screen and (min-width: 992px) and (max-width: 1199px) {
    #how-work-area {
        background-size: auto 240px;
    }
}


/*-------------------------------------------------------------------------------------
    FAQ accordion — white cards, no fill

    The open question, its answer panel and any hovered question were painted
    with a green->blue sweep (`linear-gradient(90deg, #1E8A3D, #1F5FD4)`), set on
    the header and on the body as two SEPARATE gradients. They are all plain
    white now: opening a question no longer repaints it, it just reveals the
    answer underneath, and the row reads as one set of cards rather than one
    coloured card among white ones.

    Three things follow from taking the fill away.

    1. THE TEXT HAD TO COME BACK. The template painted the open question, the
       hovered question and every answer #fff, which was right on a saturated
       fill and invisible on white. They take the page's own ink and body
       colours instead — #04140c for the question, #4a5a52 for the answer, the
       same pair the section headings and paragraphs use.

    2. THE SHADOW MOVED FROM THE HEADER TO THE CARD. The design put the card
       shadow on .card-header, which is fine while the header IS the card — but
       an open card is header + body, and a shadow on the header alone draws a
       glow straight across the seam between the two white halves. On .card it
       wraps whichever of the two are showing, so an open card reads as one
       block. Closed cards are unchanged: the collapse is zero-height, so the
       card box is still exactly the header box.

    3. HOVER NEEDED A NEW SIGNAL. It used to be the fill appearing. It is now a
       slightly deeper shadow on the whole card, which is the same hover language
       .dn-card uses, and no colour change at all.

    `background-image: none` is required, not optional: the gradient is set with
    `background-image`, and `background-color` does not replace it — set only the
    colour and the sweep stays painted on top.

    The `.card.two` variants carry the same treatment. Nothing in this app renders
    that class today (the FAQ markup emits a bare `.card`), but leaving its 45deg
    sweep in place would mean the next `.two` card silently reintroduces the
    gradient this removes.
---------------------------------------------------------------------------------------*/

.card {
    border-radius: 10px;
    -webkit-box-shadow: 0px 0px 15px 0px rgba(30, 138, 61, 0.4);
    box-shadow: 0px 0px 15px 0px rgba(30, 138, 61, 0.4);
    -webkit-transition: box-shadow 0.2s;
    transition: box-shadow 0.2s;
}

.card:hover {
    -webkit-box-shadow: 0px 0px 20px 0px rgba(30, 138, 61, 0.55);
    box-shadow: 0px 0px 20px 0px rgba(30, 138, 61, 0.55);
}

.card .card-header,
.card .card-header.active,
.card .card-header:hover,
.card.two .card-header.active,
.card.two .card-header:hover,
.card-body,
.card.two .card-body {
    background-image: none;
    background-color: #fff;
    -webkit-box-shadow: none;
    box-shadow: none;
}

.card .card-header a,
.card .card-header.active a,
.card .card-header:hover a {
    color: #04140c;
}

.card-body p {
    color: #4a5a52;
}


/*-------------------------------------------------------------------------------------
    faq -> contact boundary
---------------------------------------------------------------------------------------*/

/* `.card` carries `margin-bottom: 20px` to space the accordion's items from one
   another, but it fires after the LAST one too, where there is no next item to
   separate from — so it lands on top of the section's own bottom padding as
   dead space. Measured at 1440px, the accordion's last row to the "CONTACT US"
   label was 156px (20 + 64 + 72), the widest boundary on the page. */
#accordion>.card:last-child {
    margin-bottom: 0;
}

/* No glow on the FAQ cards. The green 15px halo above (20px on hover) read as a
   glow rather than an edge, so the shadow goes and a thin neutral border marks
   the card instead — the same #E5E7EB ring the stack carousel uses. Hover
   darkens the border slightly so the row still responds. The header and body
   shadows are already `none` above. */
#accordion>.card,
#accordion>.card:hover {
    -webkit-box-shadow: none;
    box-shadow: none;
    border: 1px solid #E5E7EB;
    -webkit-transition: border-color 0.2s;
    transition: border-color 0.2s;
}

#accordion>.card:hover {
    border-color: #CBD5E1;
}


/*-------------------------------------------------------------------------------------
    #video-area: keep the circle off the counters (>= 1201px)
---------------------------------------------------------------------------------------*/

/* The theme sizes `.video-cont` 708x708 at `top: 255px` above 1200px. Both of
   those are fixed pixels, and so is the flow above the counters, so the circle
   overran the counter row by exactly 55px at EVERY width from 1280 to 1920 —
   measured, not estimated. It landed across the third and fourth icons.

   Trim the diameter rather than moving the circle up or padding the counters
   down. Moving it up walks it into the "Measurable outcomes" paragraph, which
   shares its band; padding the counters down re-opens the section-height
   problem. Shrinking fixes both edges at once — the bottom clears the counters
   by 33px, and the left edge pulls right, away from that paragraph.

   620px also tracks the design more closely than 708 did: the artwork reads as
   about a third of the viewport there, which is what 620 gives at 1920. */
@media only screen and (min-width: 1201px) {
    .video-cont {
        width: 620px;
        height: 620px;
    }
}

/* Every indexable page needs exactly one <h1>, and on /pricing and /schedule the
   page's real heading was an <h2> inside .section-heading — the template only
   ever uses h1 in the landing hero. Promoting those to h1 is a semantics fix
   (search engines and screen readers both take h1 as "what this page is"), and
   these rules keep it a purely semantic one: the template's bare h1 is 60px,
   the h2 it replaced is 50px, so without them the promotion would resize the
   page. Mirrors `h2` in style.css and the 30px it drops to at <=991px in
   responsive.css — change those and change these. */
.section-heading h1 {
    font-size: 50px;
    line-height: 60px;
    letter-spacing: -0.03em;
    font-weight: 700;
    margin-bottom: 10px;
}

@media only screen and (max-width: 991px) {
    .section-heading h1 {
        font-size: 30px;
        line-height: 40px;
    }
}


/*-------------------------------------------------------------------------------------
    product carousel: don't lift the card onto the laptop on phones
---------------------------------------------------------------------------------------*/

/* `.feat-carousel-wrap { margin-top: -60px }` (style.css) pulls the product
   cards up under the section heading, and its own comment says that lift is
   for wide screens — but the rule is unscoped, so it applied here too.

   Below 768px the two columns STACK: the laptop mockup sits directly above the
   card instead of beside it, so there is no heading to tuck under and the -60px
   is simply subtracted from the space between them. Measured at 360-767px the
   card's top edge landed exactly 0px from the bottom of the laptop image — the
   two touched.

   Zero the lift at this width; the gap below is measured back to a deliberate
   figure rather than left to whatever the negative margin happens to leave. */
@media only screen and (max-width: 767px) {
    .feat-carousel-wrap {
        margin-top: 0;
    }
}

/*-------------------------------------------------------------------------------------
    every icon badge on one green

    A previous pass put the feature / capability / security card badges on the
    single brand green #1E8A3D (see "feature / security card icons" above). The
    rest of the page was still on the template's original scheme: the icon discs
    in the stack carousel, the about + platform-stat counters, the deployment
    chips, the industry headers and the how-it-works steps all carry a
    green -> blue gradient (#1E8A3D or #35B44A into #1F5FD4), and each one drops
    a BLUE shadow underneath — rgba(31, 95, 212, .x) — so even the glow around
    the icon read as blue.

    That left one page with two icon systems: flat green in three sections,
    green-fading-to-blue in five. Finish the job. Every icon badge is now the
    same flat #1E8A3D with a green shadow, so the badge colour means "brand"
    everywhere on the page instead of meaning it in some sections and something
    else in others.

    `background-image: none` is required, not optional: the template sets the
    gradient with `background-image`, which is a different property from
    `background-color` — setting only the colour leaves the gradient painted on
    top of it and nothing changes.

    Everything else here was already green and is left alone: the counter PNGs,
    the play button, the carousel arrows, the industry tick marks, the
    comparison-table ticks and the how-it-works step numbers.
---------------------------------------------------------------------------------------*/

/* Stack carousel — the four product logo discs (90px, white logo inside). */
.awesome-feat-single .icon,
.awesome-feat-single .icon.two,
.awesome-feat-single .icon.three {
    background-image: none;
    background-color: #1E8A3D;
    -webkit-box-shadow: 0px 8px 10px 0px rgba(30, 138, 61, 0.4);
    box-shadow: 0px 8px 10px 0px rgba(30, 138, 61, 0.4);
}

/* About-section stat badges and the platform-stat row under the capability
   cards — both are built from .about-info-single, and `.two` is the alternate
   the markup applies to every second item.

   These two carry the same green/blue alternation as the feature cards above
   (see "feature / security card icons"), and for the same reason: a pair or a
   row of identical green discs reads as one item repeated. `.two` is the blue
   step, so the context section runs green then blue, and the three platform
   stats run green / blue / green.

   `background-image: none` is required, not optional: the template paints these
   with a green->blue gradient via `background-image`, a different property from
   `background-color` — set only the colour and the gradient stays on top of it.
   Each rule carries the disc's own colour darkened as its shadow (#047857 under
   green, #16409B under blue) to keep the pair consistent, but note that the
   "flatten the badges" rule further down this file zeroes box-shadow on both
   selectors — so the shadows only matter if that rule is ever lifted. */
.about-info-single .icon i {
    background-image: none;
    background-color: #1E8A3D;
    -webkit-box-shadow: 0px 8px 15px -5px #047857;
    box-shadow: 0px 8px 15px -5px #047857;
}

.about-info-single.two .icon i {
    background-image: none;
    background-color: #1F5FD4;
    -webkit-box-shadow: 0px 8px 15px -5px #16409B;
    box-shadow: 0px 8px 15px -5px #16409B;
}

/* Deployment chips (public / private / on-prem). */
.chip-single .icon {
    background-image: none;
    background-color: #1E8A3D;
}

/* Industry card headers. */
.industry-single .industry-head .icon {
    background-image: none;
    background-color: #1E8A3D;
}

/* How-it-works: three 120px step discs. One colour per step now — blue for
   "Start with data", orange for "Add intelligence", yellow for "Deploy agents"
   — reusing the exact hexes and glyph pairings the deployment chips and the
   industry badges already use, so no new colour enters the page.

   Same two-variable pattern as those, and for the same reason: the warm tones
   cannot carry a white glyph. Measured, glyph against disc:

       01  white   on #1F5FD4   5.8:1
       02  white   on #F97316   2.8:1  (white by request)
       03  white   on #EAB308   2.1:1  (white by request)

   Three parts take the step's colour, not just the disc: the 120px disc, the
   1px ring around it (a green ring around an orange disc reads as a mistake),
   and the 48px .number badge riding on top of it. The number used to stay green
   as the one thing telling the steps apart; now the colour does that, so it
   follows its step instead — and takes the glyph colour with it, since white
   "03" on yellow is the same 1.7:1 failure the disc would have been. */
.how-work-single {
    --hw-disc: #1F5FD4;
    --hw-glyph: #fff;
}

.how-work-single.two {
    --hw-disc: #F97316;
    --hw-glyph: #fff;
}

.how-work-single.three {
    --hw-disc: #EAB308;
    --hw-glyph: #fff;
}

/* `background-image: none` is required, not optional: the template paints these
   discs with a gradient via `background-image`, which `background-color` does
   not replace — set only the colour and the gradient stays painted on top. */
.how-work-single i,
.how-work-single.two i,
.how-work-single.three i {
    background-image: none;
    background-color: var(--hw-disc, #1E8A3D);
    /* White glyph on all three discs, by request — the icons read as one set.
       --hw-glyph still colours the small .number badge below. */
    color: #fff;
}

.how-work-single .icon:before {
    border-color: var(--hw-disc, #1E8A3D);
}

.how-work-single .number,
.how-work-single.two .number,
.how-work-single.three .number {
    background-image: none;
    background-color: var(--hw-disc, #1E8A3D);
    color: var(--hw-glyph, #fff);
}

/*-------------------------------------------------------------------------------------
    footer socials — each network's own colour

    The five badges were five identical white rings that filled brand green on
    hover, so the row said "social links" and nothing more: which network is
    which was carried entirely by a 14px glyph on a dark ground. These are the
    one place on the page where the colour is NOT ours to choose — a blue disc
    with an f on it is recognised before the glyph is read — so each badge wears
    its own network's colour and the brand palette steps aside.

    Two variables per network, the same pattern as the deployment chips and the
    industry badges:

        --soc-disc     the fill (a --soc-grad gradient overrides it, for
                       Instagram, whose mark IS a gradient)
        --soc-glyph    the icon on that fill

    X is the one that cannot use its literal brand colour. X's mark is black, and
    black on this footer's #003E03..#035D03 ground is about 1.5:1 — a hole, not a
    badge. Its brand has always had a light-ground form, so it takes it: white
    disc, black glyph. That is the mark as X itself renders it on dark, not an
    invented colour.

    Measured, glyph against disc:

        facebook   #fff on #1877F2   3.7:1
        x          #000 on #ffffff  21.0:1
        linkedin   #fff on #0A66C2   5.0:1
        instagram  #fff on #DD2A7B   4.9:1  (mid-stop of the gradient)
        youtube    #fff on #FF0000   4.0:1

    These are 14px icon-font glyphs, so they are large-text-equivalent only at
    the top of that range; the disc colour, not the glyph, is doing the
    identifying work here, and every disc clears 3:1 against the footer ground.

    Hover keeps the network colour — turning it green again would undo the point
    — and lifts the badge with a white ring instead. */

.footer-social li a {
    background-color: var(--soc-disc, transparent);
    background-image: var(--soc-grad, none);
    border-color: var(--soc-disc, #fff);
    color: var(--soc-glyph, #fff);
    -webkit-transition: 0.2s;
    transition: 0.2s;
}

.footer-social li a.is-facebook  { --soc-disc: #1877F2; }
.footer-social li a.is-linkedin  { --soc-disc: #0A66C2; }
.footer-social li a.is-youtube   { --soc-disc: #FF0000; }

.footer-social li a.is-x {
    --soc-disc: #ffffff;
    --soc-glyph: #000000;
}

/* Instagram's mark is a corner-to-corner sweep, not a flat colour — the four
   stops are its own. `--soc-disc` stays the middle magenta so the border and
   the contrast figure above have a single colour to resolve against. */
.footer-social li a.is-instagram {
    --soc-disc: #DD2A7B;
    --soc-grad: linear-gradient(45deg, #F58529 0%, #DD2A7B 50%, #8134AF 75%, #515BD4 100%);
}

/* The template's hover repainted the disc green->blue with a blue glow. Keep the
   network's colour and mark the hover with a white ring and a small lift, so the
   affordance does not cost the badge its identity. */
.footer-social li a:hover {
    background-color: var(--soc-disc, #35B44A);
    background-image: var(--soc-grad, none);
    border-color: #fff;
    color: var(--soc-glyph, #fff);
    -webkit-transform: translateY(-2px);
    transform: translateY(-2px);
}


/*-------------------------------------------------------------------------------------
    counter icon halos — tint them green, not white

    The four counter badges are three concentric circles: a 70px white disc
    holding the icon, wrapped in a 100px ring and a 125px ring. Both rings are
    painted in translucent WHITE — rgba(255,255,255,.5) and .2 — so they take
    their colour from whatever is behind them.

    That is why they still looked grey after the band went green. White does not
    tint a colour, it desaturates it: laying 20% white over the deep green ground
    pulls the result toward the neutral axis, so the rings came out sage/grey
    however green the band underneath became. Nothing was left un-recoloured
    here — the rings were doing exactly what they were told, and what they were
    told was "wash this out".

    Lighten within the hue instead. These are tints of the brand's bright green
    #35B44A rather than white, so the rings read as green at the same lightness
    they had before and the badge is green through all three rings.

    The white disc itself stays white: the icon PNGs inside it are green line
    art, and a green disc leaves them with almost no contrast — measured, the
    glyphs nearly vanish. White disc + green glyph is the same inversion the
    feature cards already use when they fill green on hover.

    The alternative was to drop both rings, the way the feature/security badges
    lost theirs above. It is clean, but the reason those went was that they were
    invisible grey clutter on white; here the rings are what give a 70px disc
    presence on a full-bleed band, so they earn their place once they are green.
---------------------------------------------------------------------------------------*/

.counter-single .icon:before {
    background-color: rgba(122, 222, 140, 0.28);
}

.counter-single .icon:after {
    background-color: rgba(160, 235, 175, 0.55);
}


/*-------------------------------------------------------------------------------------
    hero: product shot on the right

    The hero used to be a single raster: green ground, transparent wedge and an
    isometric scene with a handset in it, all baked into one PNG. It now splits
    in two — home-bg-green-clean.png carries just the ground and the wedge, and
    the product screenshot is a real element on top.

    That split is the point. The screenshot is now swappable without touching
    pixels, it scales with the viewport, and it can be shown at a size where the
    dashboard is actually readable — which a scene-sized handset never allowed.

    Absolutely positioned rather than a grid column, so it can run off the right
    edge and off the bottom instead of being boxed by the container. #home-area
    already sets overflow-x: clip, so that bleed is trimmed at the section rather
    than widening the document and creating a horizontal scrollbar.

    overview-hero.png is a crop of the 3136x3844 capture: the licence banner is
    taken off the top and the node cards off the bottom, leaving the header,
    both KPI rows, the throughput chart AND the three panel charts with their
    stat lists — the capture from y=90 to y=3150, downscaled to 1400 wide. That
    is still about 2.3x the card's rendered width, so it stays retina-sharp
    without shipping a 3136px PNG. The tile numbers and panel headings read at
    this size; the smallest labels do not, which is the trade for depth.

    Its 0.976 aspect is what sets the card's height (the image is width:100%,
    height:auto), so a different crop changes the card's shape — that is the
    knob to turn if you want it shorter, not a CSS height. Note the pairing
    below: the card is top-anchored and the section carries a min-height sized
    from that same aspect, so re-cropping means re-deriving that min-height.
---------------------------------------------------------------------------------------*/

#home-area.bg-1 {
    position: relative;
}

/* The card is anchored to the TOP of the hero, not centred in it. With the
   deeper crop the card is most of the section's height, so centring it left a
   sliver of green above and below and read as a band across the middle; top-
   anchored, it starts just under the header and runs down past the copy, which
   is what makes it read as a window onto the running product.

   116px = the fixed header's 92px plus a 24px gap. The section is given a
   matching min-height below so the card always has somewhere to land. */
@media only screen and (min-width: 992px) {
    #home-area.bg-1 {
        /* Room for the card: 116 top + 34 chrome bar + the image's own height
           (card width x the 0.976 crop aspect) + a 64px gap under it. Card
           width is 42vw until it hits the 780px max-width at ~1857px viewport,
           where the whole thing tops out at 975px — hence the min(). Below
           ~1430px this computes under the hero's natural 796px and so does
           nothing, which is the intent: only wide viewports need the extra. */
        min-height: min(calc(41vw + 214px), 975px);
    }
}

#home-area.bg-1 .hero-shot {
    position: absolute;
    top: 116px;
    /* Square-on, no perspective. It used to carry
       `perspective(1800px) rotateY(-5deg) rotateX(1deg)` to give the card a near
       and a far side; with the deeper crop that tilt cost more than it bought —
       the far edge leaned into the copy, every rule in the dashboard ran off
       level, and the small labels smeared. A flat rectangle reads as a real
       screen. Don't reinstate the rotation without re-checking the min-height
       below: a tilt makes the card's bounding box taller than its layout box. */
    -webkit-transform: none;
    transform: none;
    /* Flush to the viewport edge. Earlier revisions held it 4% clear so it read
       as a floating card; pinned at 0 it reads as the product continuing off
       the page instead, which is the stronger image. The right corners are
       squared off to match — a rounded corner against the viewport edge looks
       like a rendering slip rather than a deliberate shape. */
    right: 0;
    width: 42%;
    max-width: 780px;
    border-radius: 12px 0 0 12px;
    overflow: hidden;
    z-index: 1;
    background: #fff;
    /* Three layers rather than one: a hairline contact shadow that keeps the
       edge crisp, a mid shadow for the lift, and a wide soft one for ambient.
       A single large blur on its own just reads as a grey smudge. */
    border: 1px solid rgba(8, 60, 28, 0.08);
    /* No right edge — that side is the viewport edge, and a hairline there just
       reads as a stray line. */
    border-right: 0;
    -webkit-box-shadow:
        0 2px 6px rgba(4, 34, 16, 0.07),
        0 18px 40px -12px rgba(4, 34, 16, 0.26),
        0 54px 96px -34px rgba(4, 34, 16, 0.44);
    box-shadow:
        0 2px 6px rgba(4, 34, 16, 0.07),
        0 18px 40px -12px rgba(4, 34, 16, 0.26),
        0 54px 96px -34px rgba(4, 34, 16, 0.44);
}

/* Browser chrome. The screenshot IS a page, so framing it as one costs a strip
   of markup and makes the card read as the running product rather than an
   image. Built in CSS, not baked into the PNG: it scales with the card, stays
   crisp at any density, and the screenshot can be swapped without redrawing
   it. The pill carries the real domain — nothing invented. */
#home-area.bg-1 .hero-shot-bar {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    height: 34px;
    padding: 0 13px;
    background: #f1f4f2;
    border-bottom: 1px solid #e3e9e5;
}

#home-area.bg-1 .hero-shot-bar .dot {
    width: 9px;
    height: 9px;
    border-radius: 50%;
    margin-right: 6px;
    -ms-flex-negative: 0;
    flex-shrink: 0;
}

#home-area.bg-1 .hero-shot-bar .dot-1 { background: #ec6a5e; }
#home-area.bg-1 .hero-shot-bar .dot-2 { background: #f4bf4f; }
#home-area.bg-1 .hero-shot-bar .dot-3 { background: #61c554; }

#home-area.bg-1 .hero-shot-bar .url {
    -webkit-box-flex: 1;
    -ms-flex: 1;
    flex: 1;
    margin-left: 10px;
    height: 19px;
    line-height: 19px;
    border-radius: 10px;
    background: #fff;
    border: 1px solid #e3e9e5;
    padding: 0 10px;
    font-size: 10px;
    color: #8b968f;
    overflow: hidden;
    white-space: nowrap;
}

/* The card takes its height from the image, so the crop's aspect sets it. */
#home-area.bg-1 .hero-shot img {
    display: block;
    width: 100%;
    height: auto;
}

/* Between 992 and 1199 the container is narrow enough that a 46% shot crowds
   the headline. Pull it in and let the copy keep its measure. */
@media only screen and (min-width: 992px) and (max-width: 1199px) {
    #home-area.bg-1 .hero-shot {
        width: 42%;
        right: 3%;
    }

    .caption h1 {
        font-size: 40px;
        line-height: 50px;
    }
}

/* Below 992px there is nothing to sit beside — the copy runs full width — so
   the card stops being absolutely positioned and becomes a normal block under
   it. That is why the element sits after .container in the markup: on desktop
   its source order is irrelevant (it is absolute), and here source order is
   exactly what puts it below the copy rather than over it. */
@media only screen and (max-width: 991px) {
    #home-area.bg-1 .hero-shot {
        position: static;
        -webkit-transform: none;
        transform: none;
        right: auto;
        /* The card is a child of the section, not of .container, so `auto`
           width made it span the full screen — corners clipped at both edges
           and no gutter. Give it the page's own margin back. */
        width: calc(100% - 40px);
        max-width: 560px;
        margin: 0 auto;
        /* Centred here rather than pinned to an edge, so it gets all four
           corners back and its right border with them. */
        border-radius: 12px;
        border-right: 1px solid rgba(8, 60, 28, 0.08);
    }

    /* .caption's bottom padding IS the hero's bottom gap in this design — 230px
       at tablet, ~100px on phones. With a card underneath, that padding became
       a hole between the copy and the card, and the card then had nothing below
       it at all. Move the space: a small gap above the card, and real padding on
       the section under it. */
    .caption {
        padding-bottom: 34px;
    }

    #home-area.bg-1 {
        padding-bottom: 64px;
    }
}


/*-------------------------------------------------------------------------------------
    mobile menu: the two auth buttons sat at different heights

    In the open hamburger panel "Sign in" rode about 8px higher than "Start free"
    and the two touched, with no gap between them.

    The cause is one leftover rule. responsive.css gives the primary button
    `.navbar-nav .nav-item.download-btn .nav-link { margin: 16px 0 0 }` at every
    width below 992px. That margin was written for the template's ORIGINAL mobile
    menu, where the panel was a stacked column and "Start free" sat on its own
    row under "Sign in" — there it was the gap between two rows.

    The panel is a wrapping row now, so the two buttons share the last row, and
    that 16px only applies to one of them. It makes the download item 67px tall
    against the sign-in item's 52px; the list is `align-items: center`, so the
    shorter item centres itself in the taller one's row and floats up by exactly
    half the difference — the ~8px offset that was visible.

    So: drop the margin at this width and put the separation from the links above
    on BOTH items instead, where it can't tilt one against the other. Then a real
    gap between them, and one min-width so the pair reads as a matched set rather
    than two buttons sized by their label lengths.

    Above 992px nothing here applies; the desktop bar keeps its own layout.
---------------------------------------------------------------------------------------*/

@media only screen and (max-width: 991px) {

    .navbar-nav .nav-item.download-btn .nav-link {
        margin: 0;
    }

    /* Equal margins, so the pair moves as one and stays level. */
    #header #navbarContent .navbar-nav>.nav-item.signin-btn,
    #header #navbarContent .navbar-nav>.nav-item.download-btn {
        margin-top: 14px;
    }

    #header #navbarContent .navbar-nav>.nav-item.signin-btn {
        margin-right: 12px;
    }

    /* The min-width is the BUTTON's, and only the button's. "Sign in" is a plain
       link now (see "Sign in is a PLAIN LINK" above) — padding a text link out
       to 118px and centring the label in it just makes a wide empty box. */
    .navbar-nav .nav-item.download-btn .nav-link {
        min-width: 118px;
        -webkit-box-pack: center;
        -ms-flex-pack: center;
        justify-content: center;
    }
}

/*-------------------------------------------------------------------------------------
    buttons — one flat blue, no gradient

    Every filled button on a white ground was a LEFT-TO-RIGHT GRADIENT: the
    primary actions ran #1F5FD4 -> #14b8a6, so a single button started brand blue
    and finished teal (see "Actions, rule 2" in style.css).

    The navbar's "Start free" is NOT in this list, deliberately. It is the one
    button a visitor sees before anything else on the page, and it is green —
    #1E8A3D, set in "Start free primary CTA" further up this file. The blue here
    is for filled actions further down the page, where they read as controls
    rather than as the site's own colour. Do not add the navbar selector back
    without moving that rule too.

    Two problems with that. The blue->teal sweep put a colour on the page that is
    in no other part of the brand — teal appears only as the tail of a button —
    and because the ramp runs across the button rather than down it, a wide
    button and a narrow one showed visibly different colours at their right edge.
    Between that and the emerald navbar button, the same "primary action" role
    was painted differently depending on which part of the page you were in.

    So: one flat #1F5FD4 for every filled action, #1848A6 on hover. Flat, not a
    blue-to-blue gradient — with the sweep gone there is nothing left to drift
    with button width, and the fill means "primary action" and nothing else.

    `background-image: none` is required, not optional: the template paints these
    with `background-image`, which is a different property from
    `background-color` — setting only the colour leaves the gradient on top of it
    and nothing changes. `background-size` is reset for the same reason: the
    template's hover was `background-size: 200% auto`, which slides a gradient
    that no longer exists and would otherwise sit as a dead declaration.

    `.dn-pricing-hero .plan-btn a` is in that list for a second reason. "Use Cost
    Calculator" appears twice: on the landing page inside a green band, and on
    /pricing directly under the h1. Rule 1 painted BOTH white-with-a-green-label
    because it matched on `.plan-btn a` alone, which is right on the green band
    and wrong on /pricing — a white button on the white hero, readable only by
    its shadow. Scoping this to the pricing hero turns that one blue and leaves
    the landing band's copy white.

    NOT touched: the other buttons on the green fields — the hero CTAs, the "get
    started" band, the pricing plan buttons and the newsletter bar. Those are
    deliberately WHITE with green labels ("Actions, rule 1" in style.css) because
    #1F5FD4 and the deep green ground sit at nearly the same luminance (1.4:1) —
    a blue button there would not be a blue button, it would be an invisible one.
    They carry no gradient either way, so there is no "colour effect" on them to
    change.
---------------------------------------------------------------------------------------*/

.load-more-btn a,
.contact-form button,
.price-tbl-single .table-inner a,
.dn-pricing-hero .plan-btn a {
    background-image: none;
    background-color: #1F5FD4;
    background-size: auto;
    color: #fff;
    border: 0;
    -webkit-box-shadow: 0 8px 20px -8px rgba(31, 95, 212, 0.45);
    box-shadow: 0 8px 20px -8px rgba(31, 95, 212, 0.45);
}

.load-more-btn a:hover,
.contact-form button:hover,
.price-tbl-single .table-inner a:hover,
.dn-pricing-hero .plan-btn a:hover {
    background-image: none;
    background-color: #1848A6;
    background-size: auto;
    color: #fff;
    -webkit-box-shadow: 0 12px 26px -8px rgba(31, 95, 212, 0.6);
    box-shadow: 0 12px 26px -8px rgba(31, 95, 212, 0.6);
}

/* The last gradient left on any button, and the reason it survived: rule 1
   recoloured `.download-btns a.bg` (the "App Store" fill) and gave it a white
   hover, but its hover rule only names `a.bg`. The outline "Play Store" beside
   it kept `.download-btns a:hover` from the template — a #35B44A -> #1E8A3D
   sweep, which is the one thing this band cannot show: it sits ON the green
   field, so the button filled green-on-green and all but vanished under the
   cursor.

   Blue is not the answer here for the same luminance reason as the rest of the
   band. Give it the white hover its sibling already has, so the pair behaves as
   primary + secondary instead of one of them dissolving. */
.download-btns a:hover {
    background-image: none;
    background-color: #e6f7f0;
    color: #064e3b;
    border-color: #e6f7f0;
}


/*-------------------------------------------------------------------------------------
    icon badges — drop the glow

    Every icon disc on the page threw a coloured drop-shadow underneath itself:
    `0px 8px 15px -5px #047857` on the stat badges, deployment chips and industry
    headers, and `0px 8px 10px 0px rgba(30,138,61,.4)` on the stack-carousel
    discs. Those are not depth shadows — the offset is small and the blur is wide
    and fully saturated, so what they actually render is a coloured halo bleeding
    out from behind the circle.

    That was fine when the badges were the page's only colour. They are not any
    more: the cards they sit in already have their own soft shadow, so each icon
    was a glow inside a shadow, and against the white sections the green bleed
    read as a smudge rather than as lift. The core-feature badges lost their
    concentric halo rings for exactly this reason (see "every icon badge on one
    green" above) — this finishes the same pass on the shadows.

    The badge keeps its flat #1E8A3D fill and its size. Only the halo goes, so
    the icon reads as an icon against the card instead of as a lit object
    floating over it. The card's own shadow still does the depth.

    Declared after the rules that set these shadows, so `none` wins without
    !important. The footer socials are included: the ring is on a dark ground
    where the glow was widest, and it is the same treatment.

    The remaining icon badges are already flat and are not listed, because a
    `box-shadow: none` that overrides nothing is just a rule to trip over later:
    the core-feature / capability / security badges lost their glow when the
    halo rings went, and the how-it-works step discs never had one.

    Left alone: the four counter badges in the green band. Their two concentric
    rings are not a glow — they are what gives a 70px disc presence on a
    full-bleed band, and dropping them leaves the counters looking unfinished.
    Delete `.counter-single .icon:before/:after` above if you want those too.
---------------------------------------------------------------------------------------*/

.awesome-feat-single .icon,
.awesome-feat-single .icon.two,
.awesome-feat-single .icon.three,
.about-info-single .icon i,
.about-info-single.two .icon i,
.chip-single .icon,
.industry-single .industry-head .icon,
.footer-social li a:hover {
    -webkit-box-shadow: none;
    box-shadow: none;
}


/*-------------------------------------------------------------------------------------
    stack carousel — the four product logos

    The four cards in "Four products, one governed stack" showed the template's
    stock icon PNGs, and only two of them: icon-setting.png for DataNature AND
    DocuContext, icon-responsive.png for AI360 AND Voir. So the section that
    exists to say these are four distinct products showed a cog twice and a
    stack-of-screens twice, and neither mark was ours.

    They carry their real logos now (see STACK in LandingPage.jsx). That needs
    the badge itself to change, not just the file in it: the design's 90px circle
    is a brand-green disc built to hold ONE WHITE GLYPH from an icon font. A
    full-colour mark on it either disappears (DataNature's green hexagon on
    green) or fights it (AI360 and DocuContext are blue, Voir is emerald).

    So `.product-logo` turns the badge into a white disc with a thin neutral grey
    ring. Each logo then sits on the light ground it was drawn for, and the ring
    keeps the disc visible against the white card without adding colour to it —
    the logo is the only colour inside the card.

    Sizing. The design's disc is 90px, which was built to frame a single icon-font
    glyph, not a logo — at 18px padding that left the marks 54px across and they
    read as small. The disc goes to 110px and the padding down to 14px, so the
    usable area is 82px: half again as much logo, and the badge itself carries
    more weight in the card.

    The padding is not slack to be trimmed further, though. A circle clips the
    corners of whatever square sits in it, and DocuContext's mark is a square
    whose four corner brackets ARE the logo — clip them and the logo is wrong,
    not just tight. What has to hold is that the mark's half-diagonal stays
    inside the radius:

        disc 110px -> radius 55px
        content box            110 - 2*14        = 82px
        DocuContext ink        82 * (326.8/392.2) = 68.3px  (it carries 10% of
                               its own padding in the viewBox)
        half-diagonal          68.3 * 0.7071      = 48.3px  <= 55  OK
        AI360 ink              82 / 1.10          = 74.5px
        half-diagonal          74.5 * 0.7071      = 52.7px  <= 55  OK

    DataNature's hexagon and Voir's sightline V are both well inside that, being
    round-ish rather than square. Going below ~7px padding is where DocuContext
    starts losing its brackets — but the numbers above assume these four specific
    assets, so re-check them before dropping in a fifth product.

    `object-fit: contain` keeps each mark's aspect ratio — they range from a wide
    hexagon to a tall sightline V — and `line-height: normal` undoes the disc's
    glyph-centring line-height, which would otherwise push an <img> off-centre.
---------------------------------------------------------------------------------------*/

/* The card itself is plain white. The template paints it
   `linear-gradient(160deg, #fff 53%, rgb(230,245,228) 100%)`, which left a green
   wash across the lower-right of every card — colour inside a card whose content
   is just a logo, a heading and a paragraph. `background-image: none` is what
   removes it; the neutral shadow alone carries the card's edge.

   `border-color` is for responsive.css, which swaps the shadow for a mint
   `1px solid #e6f7f0` border at 992-1200px and 320-359px. Only the colour is
   set, so it greys that border where it exists and adds none elsewhere. */
.awesome-feat-single {
    background-image: none;
    background-color: #fff;
    border-color: #E5E7EB;
}

/* Equal-height cards. Each Owl slide sized itself to its own copy, so a product
   with a shorter blurb gave a visibly shorter card beside a longer one. Making
   the stage and each slide flex rows stretches every slide to the tallest one,
   and the card fills its slide. Owl positions the stage with `transform` and an
   explicit width, and the slides' floats are simply ignored inside a flex
   container, so the sliding itself is unaffected. */
.awesome-feat-carousel.owl-carousel .owl-stage {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
}

.awesome-feat-carousel.owl-carousel .owl-item {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    float: none;
}

.awesome-feat-carousel.owl-carousel .owl-item .awesome-feat-single {
    -webkit-box-flex: 1;
    -ms-flex: 1 1 auto;
    flex: 1 1 auto;
    width: 100%;
}

.awesome-feat-single .icon.product-logo,
.awesome-feat-single .icon.product-logo.two,
.awesome-feat-single .icon.product-logo.three {
    width: 110px;
    height: 110px;
    background-image: none;
    background-color: #fff;
    border: 1px solid #E5E7EB;
    line-height: normal;
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    overflow: hidden;
}

/* `max-width` is the important one, and it is why the logo looked tiny however
   big the disc got: the theme caps EVERY image in this card at
   `.awesome-feat-single img { max-width: 50px }` — written for the 50px icon
   PNGs it used to hold. That cap is only (0,1,1), so it loses to this rule on
   any property this rule actually declares — but `width: 100%` is not one of
   them. `max-width` beats `width` regardless of specificity, so the image was
   clamped to a 50px box and `object-fit: contain` then fitted the mark into
   what was left of it after padding: about 22px of logo in a 110px circle.
   `max-height: none` is here for the same reason, pre-emptively. */
.awesome-feat-single .icon.product-logo img {
    width: 100%;
    height: 100%;
    max-width: none;
    max-height: none;
    padding: 14px;
    object-fit: contain;
}

/*-------------------------------------------------------------------------------------
    industry card icons — one colour each

    "Industry-specific solutions" rendered as four identical cards, right down to
    the same #1E8A3D icon disc on every one. Four industries with nothing to tell
    them apart until you read the heading, in a section whose whole job is to let
    someone find THEIR industry at a glance.

    The BADGE is what carries the difference now — only the badge. Metric
    figures, tick marks, headings and card borders stay exactly as they were, on
    the section's common green, so the colour is a marker on the icon rather than
    a theme applied to the whole card.

    Each card sets two custom properties, which the badge rules below read:

        --ind-disc    the icon badge fill
        --ind-glyph   the icon sitting on that fill

    Two rather than one because yellow does not behave like the other three. Red,
    blue and green are dark enough to carry a white glyph. A yellow that reads as
    YELLOW (#EAB308) is not — white on it is 1.7:1, invisible. So the aviation
    badge fills with the real yellow and puts a DARK glyph on it instead, which
    measures 6.9:1. Same colour identity, still legible.

    Measured, glyph against disc:

        bank    white on #1E8A3D   4.4:1
        telco   white on #1F5FD4   5.8:1
        health  white on #C62828   5.6:1
        air     #3F2D00 on #EAB308 6.9:1

    `.is-bank` is the green the section already used, so the banking badge is
    unchanged and the other three moved off it.
---------------------------------------------------------------------------------------*/

.industry-single.is-bank {
    --ind-disc: #1E8A3D;
    --ind-glyph: #fff;
}

.industry-single.is-telco {
    --ind-disc: #1F5FD4;
    --ind-glyph: #fff;
}

.industry-single.is-health {
    --ind-disc: #C62828;
    --ind-glyph: #fff;
}

/* White glyph by request, matching the other three badges. Note this is the
   1.7:1 pairing the comment above warns about. */
.industry-single.is-air {
    --ind-disc: #EAB308;
    --ind-glyph: #fff;
}

/* `background-image: none` is still required here — the section further up
   flattened the template's gradient to a flat green, and without it that
   gradient would paint back over the tone colour. The fallbacks keep a card
   sane if it is ever rendered without a tone class. */
.industry-single .industry-head .icon {
    background-image: none;
    background-color: var(--ind-disc, #1E8A3D);
}

.industry-single .industry-head .icon i {
    color: var(--ind-glyph, #fff);
}


/*-------------------------------------------------------------------------------------
    deployment chip icons — one colour each

    "Deploy anywhere" listed six deployment modes on six identical green badges,
    so the row read as one item repeated rather than six real choices.

    Same treatment as the industry cards above, and the same limit: only the
    BADGE takes the colour. Headings, body copy, the chip's border and its shadow
    stay common, so the tone marks the icon and nothing else.

        --chip-disc    the icon badge fill
        --chip-glyph   the icon sitting on that fill

    Every glyph is WHITE, so all six chips share one icon treatment and only the
    disc colour differs. The warm tones used to take a dark #3F2D00 glyph for
    contrast; that made Private Cloud, On-Premises and Bring Your Own WH look like
    a different icon style from the other three, and was changed on request.

    Measured, glyph against disc:

        blue    white on #1F5FD4    5.8:1
        yellow  white on #EAB308    1.7:1
        red     white on #C62828    5.6:1
        orange  white on #F97316    2.8:1

    The yellow and orange pairs are low-contrast. The variable is kept so a darker
    disc (e.g. #CA8A04 / #EA580C) can be dropped in here if the glyphs read faint.

    Orange is deliberately the BRIGHT #F97316 rather than a deeper #C2410C: the
    deeper one's hue sits ~18deg from the red badge at almost the same lightness,
    so "airgap" and "bring your own warehouse" became two chips of the same brick
    colour.

    The chips are `col-lg-4`, so the grid is three across: yellow lands in
    positions 2 and 4 and orange in position 6, which keeps the two adjacent hues
    off each other — orange sits beside red, not beside yellow.
---------------------------------------------------------------------------------------*/

.chip-single.is-blue {
    --chip-disc: #1F5FD4;
    --chip-glyph: #fff;
}

.chip-single.is-yellow {
    --chip-disc: #EAB308;
    --chip-glyph: #fff;
}

.chip-single.is-red {
    --chip-disc: #C62828;
    --chip-glyph: #fff;
}

.chip-single.is-orange {
    --chip-disc: #F97316;
    --chip-glyph: #fff;
}

/* `background-image: none` is still required — the "every icon badge on one
   green" section flattened the template's gradient to a flat colour, and without
   it that gradient paints back over the tone. */
.chip-single .icon {
    background-image: none;
    background-color: var(--chip-disc, #1E8A3D);
}

.chip-single .icon i {
    color: var(--chip-glyph, #fff);
}


/*-------------------------------------------------------------------------------------
    counter badges — rings off, one colour each

    This supersedes "counter icon halos" further up, which tinted the rings green
    rather than removing them. The reasoning there was that a 70px disc needs the
    rings to hold its own on a full-bleed band. It does not: what the rings
    actually read as is a glow around the icon, and with each badge now carrying
    its own colour the disc has enough to say on its own.

    So both rings go. They are a 125px `:before` at top:-27px and a 100px
    `:after` at top:-14px, sitting behind a 70px disc — `display: none` on the
    pair, which also drops the `z-index: -1` stacking they needed.

    Removing them leaves a hole below the icon, the same way the core-feature
    badges did. The design's `margin: 0 auto 50px` was measured to clear the
    `:before`, which hung 28px past the bottom of the disc — so of that 50px only
    about 22px was ever visible as a gap. Pulling it back to 24px keeps the
    spacing the eye actually saw instead of leaving the ring's footprint behind
    as empty space.

    No transition and no hover state is added here, deliberately: these are
    read-once figures, not controls.

    The colour is in the ICON, not the disc. The disc stays white because the
    band behind it is dark green — white is what separates the badge from the
    ground, and a coloured disc would have to fight the band before it could
    carry any meaning. The glyph is coloured per counter instead (blue #1D4ED8,
    red #B91C1C, violet #6D28D9, orange #C2410C — 5.2:1 to 7.2:1 on white), which
    is the part of the badge with contrast to spare.

    The glyphs are SOLID Font Awesome 5 icons, not the theme's line-art PNGs. The
    outline drawings were a 1-2px stroke at 40px, so on a 70px disc they read as
    thin colour sketches; a filled glyph puts the colour into the whole shape.
    Being a font, it is coloured here with `color` rather than baked into a file.
    See COUNTERS in LandingPage.jsx.

    Flex centring replaces the design's `line-height: 65px`, which was tuned for
    the PNG's baseline and sits a font glyph a few px low. The font-size is set
    once here: responsive.css's 34-40px per breakpoint was sized for the old
    images, and a solid glyph at that size crowds the disc edge.
---------------------------------------------------------------------------------------*/

.counter-single .icon:before,
.counter-single .icon:after {
    display: none;
}

.counter-single .icon {
    margin-bottom: 24px;
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    line-height: 1;
    font-size: 32px;
}

.counter-single .icon i {
    color: var(--counter-glyph, #1E8A3D);
}

.counter-single .icon.is-blue {
    --counter-glyph: #1D4ED8;
}

.counter-single .icon.is-red {
    --counter-glyph: #B91C1C;
}

.counter-single .icon.is-violet {
    --counter-glyph: #6D28D9;
}

.counter-single .icon.is-orange {
    --counter-glyph: #C2410C;
}


/*-------------------------------------------------------------------------------------
    stack carousel arrows — blue

    The prev/next controls under the product cards were the theme's green: a
    #35B44A arrow on a white disc, filling with a flat green and throwing a green
    shadow on hover.

    They are controls, and every other control on a white ground is now the brand
    blue (see "buttons — one flat blue" above), so these were the last green
    interactive element left on the page. Same flat treatment: #1F5FD4 arrow,
    filling #1F5FD4 with a white arrow on hover.

    The hover fill was written as `linear-gradient(55deg, #35B44A 0%, #35B44A
    100%)` — a "gradient" between one colour and itself, which is just a fill
    with extra steps. `background-image: none` clears it so the flat
    `background-color` below is what paints.
---------------------------------------------------------------------------------------*/

.awesome-feat-carousel.owl-carousel .owl-nav>div {
    color: #1F5FD4;
}

.awesome-feat-carousel.owl-carousel .owl-nav>div:hover {
    background-image: none;
    background-color: #1F5FD4;
    color: #fff;
    -webkit-box-shadow: 0px 12px 20px 0px rgba(31, 95, 212, 0.35);
    box-shadow: 0px 12px 20px 0px rgba(31, 95, 212, 0.35);
}


/*-------------------------------------------------------------------------------------
    data formats — make the default read as chosen

    Apache Iceberg is the default of the three, and almost nothing said so. Its
    only distinction was `border-top: 3px solid #1E8A3D` — and because that rule
    sets the TOP border alone, the card had no left, right or bottom border at
    all, while the two optional cards carry a full 1px #e5e7eb ring. So the one
    card meant to stand out was actually the LESS defined of the two shapes:
    same size, same shadow, same white, one green line on top.

    Four cues instead, all of them static — the card is a statement about which
    format is default, not a control, so nothing here animates or glows:

      1. A full 2px #1F5FD4 ring. Blue is what "chosen" already means on this
         site — `.price-tbl-single.highlighted` marks the recommended pricing
         table the same way — and it now matches the buttons. It also closes the
         three open sides the card was missing.
      2. A faint blue wash (#f7faff) so the card reads as filled-in rather than
         merely outlined. Kept very light: the noise texture and the body copy
         both still sit on it.
      3. A 6px lift plus a deeper shadow. Neutral, not a coloured glow — the
         same rgba(8,60,28,...) the cards already use, just stronger, so the
         card sits above its neighbours rather than lighting up.
      4. The badge goes flat #1F5FD4 with a tick, so it reads "selected" rather
         than merely "labelled".

    `z-index` keeps the ring and the deeper shadow over the adjacent cards
    instead of being overlapped by them.

    The lift is a `transform`, so it does not move anything else in the row —
    the three columns keep their heights and the row keeps its baseline.
---------------------------------------------------------------------------------------*/

.format-single.featured {
    border: 2px solid #1F5FD4;
    background-color: #f7faff;
    -webkit-transform: translateY(-6px);
    transform: translateY(-6px);
    -webkit-box-shadow: 0 18px 38px -12px rgba(8, 60, 28, 0.28);
    box-shadow: 0 18px 38px -12px rgba(8, 60, 28, 0.28);
    position: relative;
    z-index: 2;
}

/* The badge was the section's last green->blue gradient. Flat blue, matching the
   ring and the buttons. */
.format-single.featured .badge-tag {
    background-image: none;
    background-color: #1F5FD4;
    color: #fff;
}

/* A tick turns the label from a name into a state. Added in CSS rather than the
   markup because it is decoration — a screen reader still hears "Default". */
.format-single.featured .badge-tag:before {
    content: "\2713";
    margin-right: 6px;
    font-weight: 700;
}

/* The two optional cards recede a step, so the contrast is mutual rather than
   the default card having to do all the work alone. */
.format-single:not(.featured) {
    background-color: #fcfdfc;
}


/*-------------------------------------------------------------------------------------
    how-it-works: no artwork

    The phone-and-two-people illustration (how-work-bg-1.png, the section's own
    background) has been removed. Every #how-work-area rule above that pins its
    size or reserves a bottom lane for it — 210px on phones, 340px on tablets,
    up to 540px in responsive.css — was only there to keep the copy clear of the
    image, so with it gone the bottom padding drops back to the page rhythm.
    This block must stay after all of them; it wins on source order alone.
---------------------------------------------------------------------------------------*/

#how-work-area {
    background-image: none;
    padding-bottom: 64px;
}

@media only screen and (max-width: 767px) {
    #how-work-area {
        padding-bottom: 44px;
    }
}

/*-------------------------------------------------------------------------------------
    data foundation cards — one colour each

    "Every byte unified" gives each of its four cards its own colour, in page
    order: blue, green, yellow, orange. Scoped to #core-feature-area, so the
    capability and security grids keep the green/blue pairing above. The ID
    also lets these beat those rules without !important (except the hover copy,
    which the template already pins with !important).

    Card 1 has no variant class, hence the :not() chain.

    The yellow card's database glyph is white like the others (by request). On
    hover its copy stays white like the other cards (also by request, despite
    white on #F5B800 being under 2:1), and its glyph on the white hover disc is
    a deeper amber so it doesn't wash out.
---------------------------------------------------------------------------------------*/

/* Resting badges. */
#core-feature-area .core-feature-single-item:not(.two):not(.three):not(.four) .icon {
    background-color: #1F5FD4;
    color: #fff;
}

#core-feature-area .core-feature-single-item.two .icon {
    background-color: #1E8A3D;
    color: #fff;
}

#core-feature-area .core-feature-single-item.three .icon {
    background-color: #F5B800;
    color: #fff;
}

#core-feature-area .core-feature-single-item.four .icon {
    background-color: #EA580C;
    color: #fff;
}

/* Hover: the card fills with its own colour, the badge turns white. */
#core-feature-area .core-feature-single:hover .core-feature-single-item:not(.two):not(.three):not(.four) {
    background-color: #1F5FD4;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.two {
    background-color: #1E8A3D;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.three {
    background-color: #F5B800;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.four {
    background-color: #EA580C;
}

/* The white disc is set in each per-card rule, not once for all four: card 1's
   resting selector carries three :not()s, which out-rank a shared hover rule, so
   its badge stayed blue on the blue card and the icon vanished on hover. */
#core-feature-area .core-feature-single:hover .core-feature-single-item:not(.two):not(.three):not(.four) .icon {
    background-color: #fff;
    color: #1F5FD4;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.two .icon {
    background-color: #fff;
    color: #1E8A3D;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.three .icon {
    background-color: #fff;
    color: #B45309;
}

#core-feature-area .core-feature-single:hover .core-feature-single-item.four .icon {
    background-color: #fff;
    color: #EA580C;
}

/*-------------------------------------------------------------------------------------
    stat cards: no outline

    .about-info-single shipped with a 1px near-black border, which read as a form
    box next to every other card on the page. It now takes the same surface as the
    format cards (.format-single.dn-card): no border, soft green-tinted shadow,
    4px radius, and the same lift on hover. Covers both the context-section pair
    and the platform stats row.
---------------------------------------------------------------------------------------*/

.about-info-single,
.about-info-single.dark {
    border: 0;
    border-radius: 4px;
    background-color: #fcfdfc;
    -webkit-box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    -webkit-transition: 0.3s;
    transition: 0.3s;
}

.about-info-single:hover {
    -webkit-transform: translateY(-6px);
    transform: translateY(-6px);
    -webkit-box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
    box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
}

/*-------------------------------------------------------------------------------------
    equal-height security cards — #security-area

    Same fix #core-feature-area got (style.css, "equal-height feature cards"):
    each card was only as tall as its own paragraph, so the four cards in the row
    ended at different heights. Bootstrap's .row already stretches the columns;
    chain that stretch down through .core-feature-single to the visible card.
    On tablet the 2-up pairs match each other; on phone they stack as before.
---------------------------------------------------------------------------------------*/

#security-area .col-lg-3 {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
}

#security-area .core-feature-single {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    width: 100%;
}

#security-area .core-feature-single-item {
    display: -webkit-box;
    display: -ms-flexbox;
    display: flex;
    -webkit-box-orient: vertical;
    -webkit-box-direction: normal;
    -ms-flex-direction: column;
    flex-direction: column;
    width: 100%;
}

/*-------------------------------------------------------------------------------------
    platform stats — one merged card

    The three stats (cost / flexibility / scalability) read as one result, so they
    sit in a single card and a thin rule separates them, instead of three floating
    boxes. The .row itself becomes the card: its negative gutters are zeroed so the
    surface lines up with the container, and the columns lose their padding so the
    dividers run edge to edge. The inner .about-info-single drops its own surface
    and hover lift (the stat-card block above); the whole strip lifts instead.

    Dividers are inset (24px from each end) so they read as separators, not
    borders. Below 768px the columns stack and the rule turns horizontal.
---------------------------------------------------------------------------------------*/

.about-info.about-info-merged {
    margin-left: 0;
    margin-right: 0;
    background-color: #fcfdfc;
    border-radius: 4px;
    -webkit-box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    box-shadow: 0px 10px 30px 0px rgba(8, 60, 28, 0.2);
    -webkit-transition: 0.3s;
    transition: 0.3s;
}

.about-info.about-info-merged:hover {
    -webkit-transform: translateY(-6px);
    transform: translateY(-6px);
    -webkit-box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
    box-shadow: 0px 18px 40px 0px rgba(8, 60, 28, 0.26);
}

.about-info-merged>[class*="col-"] {
    position: relative;
    padding-left: 0;
    padding-right: 0;
}

.about-info-merged .about-info-single,
.about-info-merged .about-info-single:hover {
    background-color: transparent;
    -webkit-box-shadow: none;
    box-shadow: none;
    -webkit-transform: none;
    transform: none;
    margin-bottom: 0;
}

.about-info-merged>[class*="col-"]+[class*="col-"]:before {
    content: "";
    position: absolute;
    top: 24px;
    bottom: 24px;
    left: 0;
    width: 1px;
    background-color: #e3e9e5;
}

@media (max-width: 767px) {
    .about-info-merged>[class*="col-"]+[class*="col-"]:before {
        top: 0;
        bottom: auto;
        left: 24px;
        right: 24px;
        width: auto;
        height: 1px;
    }
}

/*-------------------------------------------------------------------------------------
    platform stat icons — solid white

    The three stats under the capability cards render SolidIcon SVGs inside the
    disc `<i>` (the icomoon line glyphs they replaced can't be filled). Centre
    the SVG in the disc, fill `.dn-fill` shapes white, and stroke `.dn-cut`
    lines in the disc colour so the cog's hub and the eye's iris still show as
    cut-outs.

    Each stat takes its own disc colour from the shared palette (`is-<tone>` in
    LandingPage.jsx): blue, orange, red. These selectors out-rank the green/blue
    `.about-info-single .icon i` rules further up.
---------------------------------------------------------------------------------------*/

.about-info-merged .about-info-single.is-blue {
    --stat-disc: #1F5FD4;
}

.about-info-merged .about-info-single.is-orange {
    --stat-disc: #F97316;
}

.about-info-merged .about-info-single.is-red {
    --stat-disc: #C62828;
}

.about-info-merged .about-info-single .icon i {
    display: -webkit-inline-box;
    display: -ms-inline-flexbox;
    display: inline-flex;
    -webkit-box-align: center;
    -ms-flex-align: center;
    align-items: center;
    -webkit-box-pack: center;
    -ms-flex-pack: center;
    justify-content: center;
    background-image: none;
    background-color: var(--stat-disc, #1E8A3D);
    color: #fff;
}

.about-info-merged .about-info-single .icon svg.dn-icon-solid .dn-fill {
    fill: currentColor;
}

.about-info-merged .about-info-single .icon svg.dn-icon-solid .dn-cut {
    stroke: var(--stat-disc, #1E8A3D);
}

/*-------------------------------------------------------------------------------------
    data foundation — plain white

    The section sat on the template's green blob (feature-bg-1.png, top-right)
    with three drifting green circles over it, so only the cards were white.
    The whole section is white now: the blob goes here, and the circles were
    removed from the markup in LandingPage.jsx.
---------------------------------------------------------------------------------------*/

#core-feature-area,
#core-feature-area.bg-1 {
    background-image: none;
    background-color: #fff;
}

/*-------------------------------------------------------------------------------------
    capability & security cards — one colour each, solid white icons

    "One platform, every data motion" used the shared green/blue variant pairing,
    so six cards read as two repeated colours. Each card now takes a tone from
    the deployment-chip palette (`is-<tone>` in LandingPage.jsx): blue, yellow,
    red, green, orange, blue. "Enterprise-grade security" (#security-area) uses
    the same rules: red, blue, green, orange; its icofont glyphs are already
    solid and just follow the disc's `color`. The tone sets the icon disc at
    rest and the card fill on hover; the ID out-ranks the shared variant rules
    without !important.

    Icons are solid all the time, reusing the SolidIcon tagging (see "solid
    glyphs on hover" above): `.dn-fill` shapes fill white, and `.dn-cut` lines
    are stroked in the DISC colour so they still show as cut-outs. On hover the
    disc turns white, the glyph takes the card colour, and the cut-outs go back
    to white. Yellow's hover glyph is a deeper amber so it doesn't wash out on
    the white disc.
---------------------------------------------------------------------------------------*/

#capabilities-area .core-feature-single-item.is-blue,
#security-area .core-feature-single-item.is-blue {
    --cap-color: #1F5FD4;
    --cap-hover-glyph: #1F5FD4;
}

#capabilities-area .core-feature-single-item.is-yellow,
#security-area .core-feature-single-item.is-yellow {
    --cap-color: #EAB308;
    --cap-hover-glyph: #B45309;
}

#capabilities-area .core-feature-single-item.is-red,
#security-area .core-feature-single-item.is-red {
    --cap-color: #C62828;
    --cap-hover-glyph: #C62828;
}

#capabilities-area .core-feature-single-item.is-green,
#security-area .core-feature-single-item.is-green {
    --cap-color: #1E8A3D;
    --cap-hover-glyph: #1E8A3D;
}

#capabilities-area .core-feature-single-item.is-orange,
#security-area .core-feature-single-item.is-orange {
    --cap-color: #F97316;
    --cap-hover-glyph: #EA580C;
}

#capabilities-area .core-feature-single-item .icon,
#security-area .core-feature-single-item .icon {
    background-image: none;
    background-color: var(--cap-color, #1E8A3D);
    color: #fff;
}

#capabilities-area .core-feature-single:hover .core-feature-single-item,
#security-area .core-feature-single:hover .core-feature-single-item {
    background-color: var(--cap-color, #1E8A3D);
}

#capabilities-area .core-feature-single:hover .core-feature-single-item .icon,
#security-area .core-feature-single:hover .core-feature-single-item .icon {
    background-color: #fff;
    color: var(--cap-hover-glyph, #1E8A3D);
}

#capabilities-area .core-feature-single-item .icon svg.dn-icon-solid .dn-fill,
#security-area .core-feature-single-item .icon svg.dn-icon-solid .dn-fill {
    fill: currentColor;
}

#capabilities-area .core-feature-single-item .icon svg.dn-icon-solid .dn-cut,
#security-area .core-feature-single-item .icon svg.dn-icon-solid .dn-cut {
    stroke: var(--cap-color, #1E8A3D);
}

#capabilities-area .core-feature-single:hover .core-feature-single-item .icon svg.dn-icon-solid .dn-cut,
#security-area .core-feature-single:hover .core-feature-single-item .icon svg.dn-icon-solid .dn-cut {
    stroke: #fff;
}

/*-------------------------------------------------------------------------------------
    data foundation icons — solid white at rest

    Same treatment as "capability & security cards" above, with this
    section's own disc colours for the cut-out lines: blue (card 1), green
    (.two), yellow (.three), orange (.four). Card 1 has no variant class, hence
    the :not() chain.
---------------------------------------------------------------------------------------*/

#core-feature-area .core-feature-single-item .icon svg.dn-icon-solid .dn-fill {
    fill: currentColor;
}

#core-feature-area .core-feature-single-item:not(.two):not(.three):not(.four) .icon svg.dn-icon-solid .dn-cut {
    stroke: #1F5FD4;
}

#core-feature-area .core-feature-single-item.two .icon svg.dn-icon-solid .dn-cut {
    stroke: #1E8A3D;
}

#core-feature-area .core-feature-single-item.three .icon svg.dn-icon-solid .dn-cut {
    stroke: #F5B800;
}

#core-feature-area .core-feature-single-item.four .icon svg.dn-icon-solid .dn-cut {
    stroke: #EA580C;
}

/* Hover: white disc, so the cut-outs go back to white. */
#core-feature-area .core-feature-single:hover .core-feature-single-item:not(.two):not(.three):not(.four) .icon svg.dn-icon-solid .dn-cut,
#core-feature-area .core-feature-single:hover .core-feature-single-item.two .icon svg.dn-icon-solid .dn-cut,
#core-feature-area .core-feature-single:hover .core-feature-single-item.three .icon svg.dn-icon-solid .dn-cut,
#core-feature-area .core-feature-single:hover .core-feature-single-item.four .icon svg.dn-icon-solid .dn-cut {
    stroke: #fff;
}


/*-------------------------------------------------------------------------------------
    footer — six widgets on one row

    Training and Contact took the footer from four widgets to six, so from 1200px
    each is a 2-column slot (~160px of text). The theme's 30px uppercase heading
    wraps at that width ("WORK WITH US" alone is ~230px), so it drops to the 20px
    the theme already uses at 992–1199px, and the links follow a step down.
---------------------------------------------------------------------------------------*/
@media only screen and (min-width: 1200px) {
    .footer-widget h3 {
        font-size: 20px;
        line-height: 30px;
    }

    .footer-widget li a {
        font-size: 15px;
    }
}

/* Email and phone numbers must not break mid-token. */
.footer-widget li a[href^="mailto:"],
.footer-widget li a[href^="tel:"] {
    white-space: nowrap;
}

/* Contact section — email and phone numbers under the intro copy. */
.dn-contact-links {
    display: flex;
    flex-wrap: wrap;
    gap: 10px 28px;
    margin: 18px 0 0;
    padding: 0;
    list-style: none;
}

.dn-contact-links a {
    display: inline-flex;
    align-items: center;
    gap: 10px;
    color: #0f2418;
    font-size: 16px;
    font-weight: 600;
    white-space: nowrap;
}

.dn-contact-links a:hover {
    color: #1F5FD4;
}

.dn-contact-links i {
    width: 32px;
    height: 32px;
    line-height: 32px;
    border-radius: 50%;
    text-align: center;
    font-size: 13px;
    color: #fff;
    background-color: #1F5FD4;
}

/* ── Demo video in the "Proven impact" circle ────────────────────────────────
   The circle keeps its size and position (.video-cont above); the isometric
   artwork is swapped for the demo's thumbnail inside a translucent ring, the
   same ring the artwork drew. Play button reuses the theme's white disc and
   pulsing bubble; the popup has a white title bar over the dark player. */
.video-cont.has-video {
    background-image: none;
    border-radius: 50%;
    padding: 0;
    background-color: rgba(255, 255, 255, 0.28);
    box-shadow: 0 30px 80px -30px rgba(4, 20, 12, 0.55);
}

/* Phones put .video-cont back in flow (position: static above); the thumb's
   inset needs it to stay the containing block. */
@media only screen and (max-width: 767px) {
    /* relative honours the theme's `top`, which pushed the circle down over
       "The numbers"; clear the offsets so it sits where the flow puts it. */
    .video-cont.has-video {
        position: relative;
        top: auto;
        left: auto;
        right: auto;
        bottom: auto;
        transform: none;
    }
}

/* Inset, not padding: a padding percentage is measured against the SECTION's
   width, which made the ring about a sixth of the circle. Insets are measured
   against the circle itself, so the ring stays thin at every size. */
.video-cont.has-video .video-thumb {
    position: absolute;
    inset: 2.5%;
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    gap: 18px;
    padding: 0;
    border: 0;
    border-radius: 50%;
    overflow: hidden;
    cursor: pointer;
    background-color: #04140c;
    background-size: cover;
    background-position: center;
}

/* Green wash so the thumbnail sits in the section's palette. */
.video-cont.has-video .video-thumb::before {
    content: "";
    position: absolute;
    inset: 0;
    background: linear-gradient(135deg, rgba(4, 60, 20, 0.55) 0%, rgba(30, 138, 61, 0.25) 100%);
    transition: opacity 0.25s ease;
}

.video-cont.has-video .video-thumb:hover::before,
.video-cont.has-video .video-thumb:focus-visible::before {
    opacity: 0.55;
}

.video-cont.has-video .video-play {
    position: relative;
    z-index: 1;
    display: inline-flex;
    align-items: center;
    justify-content: center;
    width: 84px;
    height: 84px;
    border-radius: 50%;
    font-size: 30px;
    background-color: #fff;
    color: #1E8A3D;
    transition: transform 0.2s ease, background-color 0.2s ease, color 0.2s ease;
}

.video-cont.has-video .video-play i {
    margin-left: 4px; /* optical centre of the triangle */
}

.video-cont.has-video .video-play::after {
    content: "";
    position: absolute;
    left: -5px;
    top: -5px;
    width: 94px;
    height: 94px;
    border: 3px solid #fff;
    border-radius: 50%;
    animation: icon-bubble 1s infinite forwards linear;
}

.video-cont.has-video .video-thumb:hover .video-play,
.video-cont.has-video .video-thumb:focus-visible .video-play {
    transform: scale(1.06);
    background-image: linear-gradient(90deg, #35B44A 0%, #1E8A3D 100%);
    color: #fff;
}

.video-cont.has-video .video-caption {
    position: relative;
    z-index: 1;
    padding: 6px 14px;
    border-radius: 999px;
    font-size: 13px;
    font-weight: 600;
    letter-spacing: 0.06em;
    text-transform: uppercase;
    color: #fff;
    background: rgba(4, 20, 12, 0.45);
    backdrop-filter: blur(4px);
}

.video-cont.has-video .video-thumb:focus-visible {
    outline: 3px solid #fff;
    outline-offset: 4px;
}

.dn-video-modal {
    position: fixed;
    inset: 0;
    /* Above #header.sticky (9999) so the close button is never covered. */
    z-index: 10000;
    display: flex;
    align-items: center;
    justify-content: center;
    padding: 24px 16px;
    background: rgba(4, 20, 12, 0.78);
    backdrop-filter: blur(6px);
    animation: dn-video-fade 0.2s ease;
}

.dn-video-box {
    width: 100%;
    /* Narrow on short screens so the head + 16:9 frame + foot fit vertically. */
    max-width: min(960px, (100vh - 180px) * 16 / 9);
    overflow: hidden;
    border-radius: 16px;
    background: #04140c;
    box-shadow: 0 40px 100px -20px rgba(0, 0, 0, 0.6);
    animation: dn-video-rise 0.25s ease;
}

.dn-video-head {
    display: flex;
    align-items: center;
    gap: 12px;
    padding: 14px 18px;
    background: #fff;
    border-bottom: 1px solid rgba(4, 20, 12, 0.08);
}

.dn-video-head h5 {
    flex: 1;
    margin: 0;
    min-width: 0;
    overflow: hidden;
    color: #04140c;
    font-size: 15px;
    font-weight: 600;
    white-space: nowrap;
    text-overflow: ellipsis;
}

.dn-video-close {
    flex-shrink: 0;
    width: 34px;
    height: 34px;
    border: 0;
    border-radius: 50%;
    font-size: 16px;
    color: #1E8A3D;
    background: rgba(53, 180, 74, 0.12);
    cursor: pointer;
}

.dn-video-close:hover {
    color: #fff;
    background-image: linear-gradient(90deg, #35B44A 0%, #1E8A3D 100%);
}

.dn-video-frame {
    position: relative;
    aspect-ratio: 16 / 9;
    background: #000;
}

.dn-video-frame iframe {
    position: absolute;
    inset: 0;
    width: 100%;
    height: 100%;
    border: 0;
}

.dn-video-foot {
    display: flex;
    justify-content: flex-end;
    padding: 12px 18px;
}

.dn-video-foot a {
    display: inline-flex;
    align-items: center;
    gap: 8px;
    font-size: 14px;
    font-weight: 600;
    color: #fff;
}

.dn-video-foot a:hover {
    color: #35B44A;
}

@keyframes dn-video-fade {
    from { opacity: 0; }
    to { opacity: 1; }
}

@keyframes dn-video-rise {
    from { opacity: 0; transform: translateY(12px) scale(0.98); }
    to { opacity: 1; transform: none; }
}

@media only screen and (max-width: 767px) {
    .video-cont.has-video .video-play {
        width: 64px;
        height: 64px;
        font-size: 24px;
    }

    .video-cont.has-video .video-play::after {
        width: 74px;
        height: 74px;
    }

    .video-cont.has-video .video-caption {
        font-size: 11px;
    }
}
