/* ==========================================================================
   Deliver better — design tokens and component CSS
   --------------------------------------------------------------------------
   Paste this into the Hello Elementor child theme's style.css, or enqueue it
   as its own file. Every colour in every component comes from a token here.

   The rule that matters: never type a hex into an Elementor widget. Use the
   Global Colours, which map 1:1 onto the tokens below. The Thorntons prototype
   shipped a bug where chips were defined blush-on-blush in one theme and went
   invisible, because a colour was hardcoded per theme instead of tokenised.
   That is the failure mode this file exists to prevent.

   Palette source: the Deliver better service image brief.
     cream  #F5F1E8   ink   #171B20   blue  #009FEF
     pink   #E56399   green #386641
   Typeface: Poppins throughout, confirmed against the live site. Headings 700
   and 800, body 400. Roboto Slab on the live stat labels is a theme leftover
   and is not part of the brand.
   ========================================================================== */

/* --------------------------------------------------------------- theme ----
   The site is dark. That is the design, not a preference: the photography, the
   brand device and the whole palette were built for a dark ground, and on cream
   they were fighting it.

   Sections are told apart by a ladder of dark surfaces rather than by
   alternating light and dark. The steps are even in OKLab lightness (about
   0.05 apart), which is what makes them read as deliberate rather than as one
   band being slightly off. Each is measured against the body text: the
   shallowest still clears 12:1.

   IMPORTANT, and the reason half this file was rewritten: --ink is a TEXT
   colour. In the dark palette it is #E9ECF1. Anything that said
   `background: var(--ink)` therefore rendered a near-white band with white
   text on it — 1.11:1, completely unreadable — which is what the proof strip
   and every closing call to action were doing in dark mode. Backgrounds now
   come from the band tokens below, which mean the same thing in both themes.

   Light stays available through the toggle and is a complete, tested palette.
   It is no longer applied automatically from prefers-color-scheme, because the
   design is dark and a light-mode visitor should still see the site as built.
   -------------------------------------------------------------------------- */

:root{
  color-scheme: dark;

  /* brand. Blue lifts in the dark so it stays legible as a link colour. */
  --blue:#3FB9FF; --blue-deep:#6FCCFF; --blue-soft:#0C3A55;
  --pink:#F08BB5; --green:#6FA97A;

  /* Ink is TEXT. Never a background — use the band tokens for that. */
  --ink:#E9ECF1; --ink-2:#1B2129; --ink-deep:#0A0D11;

  /* The band ladder, deepest first. Every section background is one of these. */
  --well:#03080F;        /* hero, footer, image wells — the floor       */
  --band-deep:#080E15;   /* feature bands: proof strips, closing CTAs   */
  --ground:#0B121A;      /* the page, and the default band             */
  --band-alt:#181F28;    /* the alternating band                        */
  --surface-2:#181F28;   /* kept as an alias: older rules reference it  */
  --surface:#212932;     /* cards and anything sitting on top of a band */
  --line:#3C454E;        /* borders and rules                           */

  /* type */
  --text:#E9ECF1;
  --text-soft:#A9B2BE;
  --text-faint:#8B94A0;

  /* states */
  --good:#6FA97A; --warn:#D9A649; --crit:#E8756E;

  /* chips, callouts, quote marks */
  --chip-bg:#0C3A55; --chip-fg:#BFE6FB;
  --anno-bg:#0C3A55; --anno-fg:#E9ECF1; --anno-label:#8FD6FF;
  --plate:rgba(3,8,15,.66);

  /* geometry */
  --r:16px; --r-sm:10px; --r-pill:999px;
  --shadow:0 14px 40px rgba(0,0,0,.55);
  --wrap:1180px;
}

/* The light palette, for anyone who turns it on. Same token names, same roles,
   so nothing downstream has to know which theme is running. */
:root[data-theme="light"]{
  color-scheme: light;

  /* --blue stays the brand blue for marks and lines. --blue-deep is the one
     that carries small text and button fills, so it is a step darker than the
     brand value: at #0077C2 a 13px label on cream measured 4.22:1. */
  --blue:#009FEF; --blue-deep:#006BAF; --blue-soft:#CCECFD;
  --pink:#E56399; --green:#386641;
  --ink:#171B20; --ink-2:#232A33; --ink-deep:#0E1216;

  --well:#0E1216;
  --band-deep:#171B20;
  --ground:#F5F1E8;
  --band-alt:#EDE8DC;
  --surface-2:#EDE8DC;
  --surface:#FFFFFF;
  --line:#DED8C9;

  --text:#171B20;
  --text-soft:#4F5763;
  /* Was #828B97, which is 3.06:1 on cream — under the 4.5 a 14px label needs.
     Footnotes, dates, glossary terms and the at-a-glance labels all use it. */
  --text-faint:#5F6875;

  --good:#386641; --warn:#9A6B15; --crit:#B4322C;

  --chip-bg:#CCECFD; --chip-fg:#00527F;
  --anno-bg:#CCECFD; --anno-fg:#171B20; --anno-label:#0077C2;
  --plate:rgba(13,17,22,.58);

  --shadow:0 10px 30px rgba(23,27,32,.10);
}

/* --------------------------------------------------------------- base ---- */

*{box-sizing:border-box}
body{
  margin:0; background:var(--ground); color:var(--text);
  font-family:"Poppins", ui-sans-serif, system-ui, sans-serif;
  font-size:17px; line-height:1.68;
  -webkit-font-smoothing:antialiased;
}
h1,h2,h3,h4{
  font-family:"Poppins", ui-sans-serif, system-ui, sans-serif;
  letter-spacing:-0.02em; text-wrap:balance; margin:0; color:var(--text);
}
p{margin:0 0 15px; max-width:64ch;}
a{color:inherit; text-decoration:none;}
:focus-visible{outline:2px solid var(--blue); outline-offset:3px;}
img{max-width:100%; height:auto;}
.db-wrap{max-width:var(--wrap); margin:0 auto; padding-inline:20px;}

/* Respect the user. Every transition in this file is suppressed here. */
@media (prefers-reduced-motion:reduce){
  *,*::before,*::after{animation-duration:.01ms!important; animation-iteration-count:1!important;
    transition-duration:.01ms!important; scroll-behavior:auto!important;}
}

/* ---------------------------------------------------------- navigation --- */
/* A floating pill that docks to a solid bar on scroll. The JS in the child
   theme adds .scrolled past 40px; without JS it simply stays floating, which
   still works. */

.db-nav{position:sticky; top:0; z-index:70; padding-block:14px;
  transition:background .25s ease, box-shadow .25s ease, padding .25s ease;
  border-bottom:1px solid transparent;}
.db-nav.scrolled{background:var(--band-deep); border-bottom-color:rgba(255,255,255,.10);
  box-shadow:0 10px 30px rgba(10,14,18,.30); padding-block:9px;}
.db-nav .db-wrap{display:flex; align-items:center; gap:14px;}
.db-brand img{height:30px; width:auto; display:block;}
.db-nav.scrolled .db-brand img{height:26px;}

/* A glass pill on the dark ground. It used to be a white pill with ink links,
   which was right on cream and wrong on everything now. The fill is a light
   wash over whatever is behind it, so it works over the hero video as well as
   over a flat band. */
.db-navpill{display:flex; align-items:center; gap:4px; margin:0 auto;
  background:rgba(255,255,255,.07); backdrop-filter:blur(16px) saturate(140%);
  -webkit-backdrop-filter:blur(16px) saturate(140%);
  border:1px solid rgba(255,255,255,.12); border-radius:var(--r-pill); padding:5px;
  box-shadow:0 8px 30px rgba(0,0,0,.35);}
.db-navpill a{font-family:"Poppins"; font-size:14.5px; color:#DDE3EB;
  padding:8px 15px; border-radius:var(--r-pill); white-space:nowrap;
  transition:background .2s, color .2s;}
.db-navpill a:hover{background:rgba(255,255,255,.12); color:#fff;}
/* The open parent (SmartMenus adds .highlighted) looks like hover. !important
   because the header widget's own saved colours outrank a class rule, which
   left "What we do" dark grey on the dark pill while its menu was open. */
.db-navpill a.highlighted{background:rgba(255,255,255,.12)!important; color:#fff!important;}
.db-navpill a[aria-current="page"]{background:var(--blue); color:#06121B;}
.db-nav.scrolled .db-navpill{background:rgba(255,255,255,.09); box-shadow:none;}

/* The light theme keeps the original white pill. */
:root[data-theme="light"] .db-navpill{background:rgba(255,255,255,.92);
  border-color:rgba(0,0,0,.06); box-shadow:0 6px 28px rgba(23,27,32,.14);}
:root[data-theme="light"] .db-navpill a{color:#232A33;}
:root[data-theme="light"] .db-navpill a:hover{background:rgba(0,159,239,.12); color:var(--blue-deep);}
:root[data-theme="light"] .db-navpill a.highlighted{background:rgba(0,159,239,.12)!important; color:var(--blue-deep)!important;}
:root[data-theme="light"] .db-navpill a[aria-current="page"]{background:var(--blue-deep); color:#fff;}
:root[data-theme="light"] .db-nav.scrolled .db-navpill{background:rgba(255,255,255,.10);
  border-color:rgba(255,255,255,.16);}
:root[data-theme="light"] .db-nav.scrolled .db-navpill a{color:#E7EAF0;}

@media (max-width:1040px){ .db-navpill{display:none} }
/* The What we do dropdown. Elementor draws it white, and .db-navpill a is
   near-white in the dark theme, so unstyled it would be white on white.
   Surface and text tokens follow the theme; the pill's radius and lift. */
.db-navpill .sub-menu{background:var(--surface)!important; border:1px solid var(--line);
  border-radius:var(--r-sm); box-shadow:0 18px 40px -18px rgba(8,12,16,.45);
  padding:6px!important; min-width:210px!important; margin-top:8px!important;}
.db-navpill .sub-menu a{color:var(--text)!important; border-radius:8px; padding:10px 14px!important;
  background:transparent;}
.db-navpill .sub-menu a:hover,
.db-navpill .sub-menu a:focus-visible{background:rgba(0,159,239,.12)!important; color:var(--blue-deep)!important;}
.db-navpill .sub-menu a[aria-current="page"]{background:var(--blue-deep)!important; color:#fff!important;}

/* -------------------------------------------------------------- buttons -- */

/* The primary button.
   White on brand blue is 2.19:1 in the dark palette and 2.91:1 in the light
   one. Both fail, and both always did — a button label is normal-size text and
   needs 4.5:1. So the label follows the fill rather than being white by habit:
   near-black on the lifted blue in the dark theme (8.6:1), white on the deeper
   blue in the light theme (4.75:1). The brand blue is unchanged everywhere it
   is used as a mark or a line; this is only about text sitting on top of it. */
.db-btn:not(.elementor-widget),
.elementor-widget.db-btn .elementor-button{display:inline-flex; align-items:center; gap:8px;
  background:var(--blue); color:#06121B; border:1px solid var(--blue);
  border-radius:var(--r-pill); padding:11px 21px;
  font-family:"Poppins"; font-size:15px; font-weight:600;
  transition:background .18s, border-color .18s, color .18s;}
.db-btn:not(.elementor-widget):hover,
.elementor-widget.db-btn .elementor-button:hover{background:var(--blue-deep); border-color:var(--blue-deep); color:#03080F;}
/* :root[data-theme="light"] .db-btn is (0,3,0) and outranks
   .db-hero .db-btn--ghost at (0,2,0), so without these :not()s the light theme
   filled in every ghost and glass button on the page. */
:root[data-theme="light"] .db-btn:not(.db-btn--ghost):not(.db-btn--glass):not(.elementor-widget),
:root[data-theme="light"] .elementor-widget.db-btn:not(.db-btn--ghost):not(.db-btn--glass) .elementor-button{
  background:var(--blue-deep); border-color:var(--blue-deep); color:#fff;}
:root[data-theme="light"] .db-btn:not(.db-btn--ghost):not(.db-btn--glass):not(.elementor-widget):hover,
:root[data-theme="light"] .elementor-widget.db-btn:not(.db-btn--ghost):not(.db-btn--glass) .elementor-button:hover{
  background:#00568D; border-color:#00568D; color:#fff;}
.db-btn--ghost:not(.elementor-widget), .elementor-widget.db-btn--ghost .elementor-button{background:transparent; color:var(--text); border-color:var(--line);}
.db-btn--ghost:not(.elementor-widget):hover, .elementor-widget.db-btn--ghost .elementor-button:hover{background:transparent; border-color:var(--blue); color:var(--blue-deep);}
.db-btn--glass:not(.elementor-widget), .elementor-widget.db-btn--glass .elementor-button{background:rgba(255,255,255,.92); color:#232A33; border-color:transparent;}
.db-btn--glass:not(.elementor-widget):hover, .elementor-widget.db-btn--glass .elementor-button:hover{background:#fff;}
.db-btn--sm:not(.elementor-widget), .elementor-widget.db-btn--sm .elementor-button{padding:8px 15px; font-size:14px;}

/* ----------------------------------------------------------------- hero -- */

.db-hero{position:relative; background:var(--well); color:#fff;
  min-height:640px; display:flex; align-items:flex-end; overflow:hidden;
  margin-top:calc(var(--db-navh, 76px) * -1);}
.db-hero img.db-hero__bg{position:absolute; inset:0; width:100%; height:100%; object-fit:cover; z-index:0;}
.db-hero__scrim{position:absolute; inset:0; z-index:1;
  background:
    linear-gradient(180deg, rgba(14,18,22,.72) 0%, rgba(14,18,22,.42) 34%, rgba(14,18,22,.90) 100%),
    linear-gradient(95deg, rgba(14,18,22,.80) 0%, rgba(14,18,22,.34) 55%, rgba(14,18,22,.08) 100%);}
.db-hero .db-wrap{position:relative; z-index:3; width:100%;
  padding-block:calc(var(--db-navh, 76px) + 74px) 54px;}
.db-hero h1{font-size:clamp(34px,5.4vw,58px); font-weight:800; line-height:1.04;
  color:#fff; max-width:17ch;}
.db-hero h1 em{font-style:normal; color:var(--blue);}
.db-hero__sub{color:#D6DBE2; font-size:19px; max-width:54ch; margin-top:16px;}
.db-eyebrow{font-family:"Poppins"; font-size:12px; letter-spacing:.2em;
  text-transform:uppercase; color:var(--blue); font-weight:600; margin-bottom:18px; display:block;}
.db-hero h1, .db-hero .db-hero__sub, .db-hero .db-eyebrow{text-shadow:0 2px 18px rgba(8,12,16,.55);}
.db-hero__cta{display:flex; gap:10px; flex-wrap:wrap; margin-top:28px;}
/* The closing CTA's buttons: the same row, so two buttons never touch. */
.db-cta__btns{display:flex; gap:12px; flex-wrap:wrap; margin-top:24px;}

/* ---------------------------------------------------------- proof strip -- */
/* The numbers band under the hero. Each figure links to its case study. */

.db-proof{background:var(--band-deep); color:#fff; padding-block:26px;}
.db-proof .db-wrap{display:grid; grid-template-columns:repeat(auto-fit,minmax(170px,1fr)); gap:18px;}
.db-proof__n{font-family:"Poppins"; font-size:32px; font-weight:700; line-height:1; color:#fff;}
.db-proof__n em{font-style:normal; color:var(--blue);}
.db-proof__l{font-size:13.5px; color:#A6AEBA; margin-top:6px; max-width:28ch;}
.db-proof a{display:block;}
.db-proof a:hover .db-proof__n{color:var(--blue);}

/* ------------------------------------------------------------- sections -- */

.db-band{padding-block:64px;}
.db-band--alt{background:var(--band-alt);}
.db-band--ink{background:var(--band-deep); color:#fff;}
.db-band--ink h2, .db-band--ink h3{color:#fff;}
.db-band--ink p{color:#A6AEBA;}
.db-kicker{font-family:"Poppins"; font-size:11.5px; letter-spacing:.16em;
  text-transform:uppercase; color:var(--blue-deep); font-weight:600;}
/* The surfaces that stay dark in both themes. --blue-deep is the light theme's
   ink blue, 3.1:1 on these; they keep the dark theme's lifted blue instead. */
:root[data-theme="light"] :is(.db-band--ink, .db-proof, .picband, .db-foot, .lessonband, .db-cta, .db-hero) .db-kicker{
  color:#6FCCFF;}

/* Elementor's global colours are the kit's, set once for the dark palette:
   Text #E9ECF1 and Primary #3FB9FF. Elementor paints text widgets with the
   first and heading widgets with the second, and neither flips with the
   theme — so in light mode every paragraph was near-white on cream (1.05:1)
   and every section heading pale blue on cream (1.8:1). Point them at the
   theme's tokens instead. The body carries the kit class, so this outranks
   the kit's own .elementor-kit-N rule, while every class rule in this file —
   the ink bands, the hero, the CTA — still outranks Elementor's defaults.
   Primary moves in the light theme only: in the dark one the blue headings
   pass comfortably and are what the site shows today. */
body[class*="elementor-kit-"]{--e-global-color-text:var(--text);}
:root[data-theme="light"] body[class*="elementor-kit-"]{--e-global-color-primary:var(--text);}
/* …except on the surfaces that stay dark in both themes, where those same
   variables would put ink on ink: the closing CTA headings and the footer's
   column heads. Scoped to the surface, so everything inside follows. */
:root[data-theme="light"] :is(.db-band--ink, .db-proof, .picband, .db-foot, .lessonband, .db-cta, .db-hero, .elementor-location-footer){
  --e-global-color-primary:#FFFFFF; --e-global-color-text:#E9ECF1;}
h2.db-sec{font-size:clamp(27px,3.4vw,36px); font-weight:700; margin:10px 0 8px;}
.db-lede{color:var(--text-soft); font-size:18px; max-width:62ch; margin-bottom:30px;}

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

/* Two columns at most. auto-fit alone fitted three at desktop width, which
   left the fourth How-we-work stage alone on a row and ignored columns:2 in the
   data. The max() makes each track at least half the row, so a third never fits. */
.db-grid2{display:grid; grid-template-columns:repeat(auto-fit,minmax(max(300px, calc((100% - 18px) / 2)),1fr)); gap:18px;}
.db-grid3{display:grid; grid-template-columns:repeat(auto-fit,minmax(260px,1fr)); gap:18px;}
/* auto-fit with a 260px floor gives FOUR columns at 1280, not three, which is
   fine for a row of four and leaves a stranded card on a row of nine. Where the
   count is a multiple of three, say so and let it wrap properly below. */
.db-grid3--three{grid-template-columns:repeat(3,1fr);}
@media (max-width:1040px){ .db-grid3--three{grid-template-columns:repeat(2,1fr);} }
@media (max-width:660px){  .db-grid3--three{grid-template-columns:1fr;} }

.db-card{background:var(--surface); border:1px solid var(--line); border-radius:var(--r);
  padding:24px; display:flex; flex-direction:column; gap:9px;}
.db-card h3{font-size:20px; font-weight:600;}
.db-card p{font-size:15.5px; color:var(--text-soft); margin:0;}
.db-card--lift{transition:border-color .2s, transform .2s;}
.db-card--lift:hover{border-color:var(--blue); transform:translateY(-2px);}
.db-card__img{aspect-ratio:5/4; border-radius:var(--r-sm); overflow:hidden; margin:-4px 0 6px;}
.db-card__img img{width:100%; height:100%; object-fit:cover; display:block;}
.db-more{margin-top:auto; padding-top:14px; font-family:"Poppins"; color:var(--blue-deep); font-size:15px;}

/* Capability card — the four (now five) service cards */
.db-cap{background:var(--surface); border:1px solid var(--line); border-radius:var(--r);
  padding:26px; display:flex; flex-direction:column; gap:10px;
  transition:border-color .2s, transform .2s;}
.db-cap:hover{border-color:var(--blue); transform:translateY(-2px);}
.db-cap__tag{font-family:"Poppins"; font-size:11.5px; letter-spacing:.14em;
  text-transform:uppercase; color:var(--blue-deep);}
.db-cap h3{font-size:23px; font-weight:600;}
.db-cap p{font-size:15.5px; color:var(--text-soft); margin:0;}
.db-cap__list{margin:4px 0 0; padding:0; list-style:none; color:var(--text-faint);
  font-size:14px; font-family:"Poppins";}
.db-cap__list li{display:inline; }
.db-cap__list li:not(:last-child)::after{content:" · ";}

/* The capability grid: three across, then whatever is left shares the last
   row. Six tracks, two per card; a trailing pair takes three each. Written
   against the remainder rather than "the fourth and fifth", so a sixth
   capability becomes two rows of three without touching this. */
.db-grid3--caps{grid-template-columns:repeat(6,minmax(0,1fr));}
.db-grid3--caps > .db-cap{grid-column:span 2;}
@media (min-width:1041px){
  .db-grid3--caps > .db-cap:nth-child(3n+1):nth-last-child(2),
  .db-grid3--caps > .db-cap:nth-child(3n+2):last-child{grid-column:span 3;}
  .db-grid3--caps > .db-cap:nth-child(3n+1):last-child{grid-column:span 6;}
}
@media (min-width:661px) and (max-width:1040px){
  .db-grid3--caps > .db-cap{grid-column:span 3;}
  .db-grid3--caps > .db-cap:nth-child(odd):last-child{grid-column:span 6;}
}
@media (max-width:660px){
  .db-grid3--caps > .db-cap{grid-column:span 6;}
}

/* The service picture across the top of each card, bled to the card's edges.
   A fixed height rather than a ratio, so the wide cards on the second row
   line up with the narrow ones above instead of opening on a taller picture. */
.db-cap--pic{overflow:hidden;}
.db-cap__pic{display:block; margin:-26px -26px 6px; height:clamp(150px, 13vw, 190px);
  overflow:hidden; background:var(--well);}
.db-cap__pic img{display:block; width:100%; height:100%; object-fit:cover;
  transition:transform .6s cubic-bezier(.22,.61,.36,1);}
.db-cap:hover .db-cap__pic img{transform:scale(1.04);}
@media (prefers-reduced-motion:reduce){ .db-cap:hover .db-cap__pic img{transform:none;} }

/* -------------------------------------------------------------- numbers -- */
/* The How we work 01–04 steps */

.db-step{border-top:2px solid var(--line); padding-top:18px;}
.db-step__n{font-family:"Poppins"; font-size:13px; font-weight:600;
  letter-spacing:.14em; color:var(--blue-deep);}
.db-step h3{font-size:21px; font-weight:600; margin:8px 0 6px;}
.db-step p{font-size:15.5px; color:var(--text-soft); margin:0 0 8px;}
.db-step__q{font-size:14.5px; color:var(--text-faint); font-style:italic;}

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

.db-chip{display:inline-block; background:var(--chip-bg); color:var(--chip-fg);
  font-family:"Poppins"; font-size:12px; letter-spacing:.04em;
  padding:4px 11px; border-radius:var(--r-pill);}

/* ----------------------------------------------------------- answer block */
/* The 40–60 word plain-English answer. This class is the selector the
   Speakable schema points at — if you rename it, rename it in schema.php too. */

.answer-block{background:var(--anno-bg); color:var(--anno-fg);
  border-left:3px solid var(--anno-label); border-radius:0 var(--r-sm) var(--r-sm) 0;
  padding:16px 20px; margin:22px 0;}
.answer-block p{margin:0; font-size:17px;}

/* ----------------------------------------------------------------- prose */

.db-prose{max-width:64ch;}
/* Links in running text. The global rule above makes every link inherit its
   colour with no underline, which is right for cards and navigation and wrong
   for a sentence: a link in an article looked exactly like the words round it.
   Only bare links are caught, so buttons and cards inside prose keep their own
   look. Underlined as well as coloured, so it does not rely on colour alone. */
:is(.db-prose, .db-faq__a, .answer-block) a:not([class]){color:var(--blue-deep);
  text-decoration:underline; text-decoration-thickness:1px; text-underline-offset:3px;}
:is(.db-prose, .db-faq__a, .answer-block) a:not([class]):hover{text-decoration-thickness:2px;}
/* On the surfaces that stay dark in both themes the light theme's ink blue is
   too dark to read, so they keep the dark theme's lifted blue. */
/* Both orders: on an insight the whole article sits inside one .db-prose, so
   its closing call to action is a dark surface INSIDE prose, not around it. */
:root[data-theme="light"] :is(.db-band--ink, .db-proof, .picband, .db-foot, .lessonband, .db-cta, .db-hero) :is(.db-prose, .db-faq__a, .answer-block) a:not([class]),
:root[data-theme="light"] :is(.db-prose, .db-faq__a, .answer-block) :is(.db-band--ink, .db-proof, .picband, .db-foot, .lessonband, .db-cta, .db-hero) a:not([class]){
  color:#6FCCFF;}
.db-prose h2{font-size:28px; font-weight:500; margin:34px 0 10px;}
.db-prose h3{font-size:21px; font-weight:600; margin:26px 0 8px;}
.db-prose ul,.db-prose ol{color:var(--text-soft); padding-left:20px;}
.db-prose li{margin-bottom:7px;}
.db-prose blockquote{margin:24px 0; padding-left:20px; border-left:3px solid var(--blue);
  font-family:"Poppins"; font-size:21px; font-weight:400; color:var(--text);}

/* ------------------------------------------------------------- pull quote */

.db-pullquote{font-family:"Poppins"; font-size:clamp(21px,2.6vw,27px); font-weight:400;
  line-height:1.35; color:var(--text); border-left:3px solid var(--blue);
  padding-left:22px; margin:30px 0; max-width:30ch;}

/* ------------------------------------------------------------ case study -- */

.db-keynums{display:grid; grid-template-columns:repeat(auto-fit,minmax(150px,1fr));
  gap:18px; margin-top:26px;}
.db-keynum__n{font-family:"Poppins"; font-size:30px; font-weight:700; line-height:1.05; color:var(--blue);}
.db-keynum__l{font-size:13.5px; color:#A6AEBA; margin-top:5px;}

.db-glance{background:var(--surface); border:1px solid var(--line);
  border-radius:var(--r); padding:22px 24px;}
.db-glance dl{margin:0; display:grid; grid-template-columns:auto 1fr; gap:8px 18px; font-size:15px;}
.db-glance dt{font-family:"Poppins"; color:var(--text-faint);}
.db-glance dd{margin:0; color:var(--text);}

/* --------------------------------------------------------------- layout --- */
/* Content + sticky rail. Collapses to one column below 940px. */

.db-layout{display:grid; grid-template-columns:minmax(0,1fr) 340px; gap:40px; align-items:start;}
.db-rail{position:sticky; top:96px; display:flex; flex-direction:column; gap:16px;}
@media (max-width:940px){
  .db-layout{grid-template-columns:1fr;}
  .db-rail{position:static;}
}

/* ------------------------------------------------------------- jargon ----- */

.db-jargon{background:var(--surface); border:1px solid var(--line);
  border-radius:var(--r); padding:26px; box-shadow:var(--shadow);}
.db-jargon textarea{width:100%; min-height:120px; border:1px solid var(--line);
  border-radius:var(--r-sm); padding:14px 16px; font:inherit; font-size:16.5px;
  background:var(--ground); color:var(--text); resize:vertical;}
.db-jargon textarea:focus{outline:2px solid var(--blue); outline-offset:1px;}
.db-jargon__out{margin-top:18px; padding:18px 20px; background:var(--blue-soft);
  border-radius:var(--r-sm); font-size:17.5px; display:none;}
.db-jargon__out.is-shown{display:block;}

/* -------------------------------------------------------------- footer ---- */

.db-foot{background:var(--well); color:#A6AEBA; padding-block:48px 30px; font-size:14.5px;}
.db-foot h4{font-family:"Poppins"; font-size:12px; letter-spacing:.12em;
  text-transform:uppercase; color:#fff; font-weight:500; margin-bottom:12px;}
.db-foot a{display:block; padding:4px 0; color:#A6AEBA;}
.db-foot a:hover{color:#fff;}
.db-foot__cols{display:grid; grid-template-columns:repeat(auto-fit,minmax(170px,1fr)); gap:28px; margin-block:28px;}
.db-foot__base{border-top:1px solid rgba(255,255,255,.10); padding-top:20px;
  display:flex; gap:18px; flex-wrap:wrap; justify-content:space-between; font-size:13.5px;}

/* --------------------------------------------------------------- mobile --- */

@media (max-width:767px){
  body{font-size:16.5px;}
  .db-band{padding-block:48px;}
  .db-hero{min-height:520px;}
  .db-wrap{padding-inline:20px;}   /* never let the gutter reach 0 */
}

/* ---------------------------------------------------------------- print --- */

@media print{
  .db-nav,.db-foot,.db-hero__scrim{display:none!important;}
  body{background:#fff; color:#000;}
}

/* ==========================================================================
   Components used by the imported page blocks
   --------------------------------------------------------------------------
   Everything above is the design system. Everything below is the specific
   set of classes the importer attaches to generated containers. Keeping them
   in one place means you can see, in one screen, exactly what the generated
   pages depend on.
   ========================================================================== */

/* The short page top used by every page except the homepage. Same treatment
   as the hero, less height, no background image required. */
.db-hero--short{min-height:auto; background:var(--well); padding-block:0;}
.db-hero--short .db-wrap{padding-block:calc(var(--db-navh, 76px) + 56px) 48px;}
.db-hero--short h1{font-size:clamp(30px,4.6vw,46px); font-weight:800; max-width:20ch;}

/* The hero as Elementor builds it: picture and overlay are the container's own
   background (the importer's hero_background()), and the copy sits in
   .e-con-inner, not .db-wrap. Every .db-wrap rule above and in motion.css
   misses on the real site — including the z-index that lifted the copy over
   the old scrim, which is why the headline read as dark grey on a dark photo.
   These mirror the mockup's effective values: motion.css overrides the short
   top's padding, so its numbers are the ones that were signed off. */
.db-hero.e-con{justify-content:flex-end;}
.db-hero.e-con > .e-con-inner{width:100%;
  padding-block:calc(var(--db-navh, 76px) + 74px) 54px;}
/* Lift each widget over the overlay rather than .e-con-inner itself, so the
   scroll cue can still position against the hero and sit at its foot. */
.db-hero.e-con > .e-con-inner > *{position:relative; z-index:3;}
/* The homepage hero's background video. Elementor puts its container inside
   .e-con-inner, so the rule above caught it too: position:relative collapsed
   it to 0px tall inside the 1140px column and the loop never showed. Pin it
   back to the whole hero, under the gradient overlay (::before), with the
   copy above both. */
.db-hero.e-con{isolation:isolate;}
.db-hero.e-con::before{z-index:1;}
.db-hero.e-con > .e-con-inner > .elementor-background-video-container{position:absolute; inset:0;
  z-index:0; overflow:hidden;}
.db-hero .elementor-background-video-hosted{position:absolute; inset:0; width:100%!important;
  height:100%!important; object-fit:cover; transform:none!important; margin:0;}
.db-hero.e-con > .e-con-inner > .elementor-widget:has(> .hero-scroll){position:static;}
.db-hero.e-con .hero-scroll{z-index:3;}
.db-hero--short:not(.db-hero--lit).e-con > .e-con-inner{padding-block:116px 54px;}
.db-hero--short.db-hero--lit.e-con > .e-con-inner{padding-block:104px 62px;}
@media (max-width:760px){
  .db-hero.e-con > .e-con-inner{padding-block:40px 40px;}
  .db-hero--lit.e-con > .e-con-inner,
  .db-hero--short.db-hero--lit.e-con > .e-con-inner{padding-block:46px 40px;}
}
.db-hero__cta.e-con, .db-cta__btns.e-con{padding:0;}
/* The insight article's header: copy on the left, the article's featured
   image on the right, rounded and framed on the dark band. The pictures are
   cream illustrations, so they sit beside the copy rather than behind it:
   under the hero's scrim they would turn to mud. Stacks on narrow screens,
   copy first. */
.db-hero--split.e-con > .e-con-inner{display:flex; flex-direction:row; align-items:center;
  gap:clamp(28px,5vw,64px);}
.db-hero--split .db-hero__copy.e-con{flex:1 1 0; min-width:0; padding:0; gap:0;}
.db-hero--split .db-hero__copy h1{max-width:18ch;}
.db-hero--split .db-hero__pic{flex:0 0 42%; max-width:42%; margin:0;}
.db-hero__pic img{display:block; width:100%; height:auto; aspect-ratio:16/9; object-fit:cover;
  border-radius:var(--r); box-shadow:0 18px 44px rgba(0,0,0,.45);}
@media (max-width:900px){
  .db-hero--split.e-con > .e-con-inner{flex-direction:column; align-items:stretch; gap:28px;}
  .db-hero--split .db-hero__pic{flex:none; max-width:100%;}
}
/* Elementor Pro's background scroll effect is not reduced-motion aware. */
@media (prefers-reduced-motion:reduce){
  .db-hero .elementor-motion-effects-layer{transform:none!important;}
  /* Nor is its background video. Hidden, the container's fallback — the
     poster — shows in its place. */
  .db-hero .elementor-background-video-container{display:none!important;}
}

/* Sections drawn by a shortcode inside an Elementor container. motion.css was
   written against the mockup, where .resolve__sticky and .cta-art are direct
   children of their section. Elementor puts three wrappers in between —
   .e-con-inner, the widget, .elementor-shortcode — and that breaks both:

   - position:sticky only travels within its parent. The parent was the
     shortcode div, exactly as tall as the stage, so the stage never pinned:
     the section kept its 210vh of height as empty space and the animation
     played out while it was off screen.
   - The CTA artwork is absolute at height:100%, anchored to the nearest
     positioned ancestor. That was the widget, which has no height of its own,
     so the artwork drew into a zero-height box and vanished.

   display:contents removes the wrappers from layout without touching the
   markup, so the section is the parent again, as it is in the mockup. */
.resolve.e-con{padding:0; --padding-top:0; --padding-bottom:0;}
.resolve.e-con > .e-con-inner,
.resolve.e-con .elementor-widget-shortcode,
.resolve.e-con .elementor-shortcode{display:contents;}
.resolve.e-con .resolve__sticky{width:100%;}

/* The picture band has the same problem: its picture and scrim are absolute,
   so inside the widget they covered only the line of text. */
.picband.e-con{padding:0; --padding-top:0; --padding-bottom:0; --padding-left:0; --padding-right:0;}
.picband.e-con > .e-con-inner,
.picband.e-con .elementor-widget-shortcode,
.picband.e-con .elementor-shortcode{display:contents;}
/* With the wrappers gone the line's box is a flex item, and its auto margins
   centred it at the width of its words. Full width puts it back on the
   content column's left edge. */
.picband.e-con .picband__say{width:100%;}

/* Prose with a picture: the importer builds .db-col and .db-col__head as
   nested containers, and Elementor makes every container flex. The grid and
   the sticky head are motion.css's; this lets them apply. */
.db-col.e-con{display:grid; --display:grid; padding:0;}
.db-col__head.e-con{display:block; padding:0;}
.db-col__head .shot--portrait{margin:26px 0 0; max-width:360px;}

/* The header row. The Theme Builder container aligned its items to the top,
   so the button and theme toggle sat above the middle of the taller nav pill. */
.db-nav.e-con > .e-con-inner{align-items:center;}

.cta-converge.e-con .elementor-widget-shortcode:has(.cta-art),
.cta-converge.e-con .elementor-widget-shortcode:has(.cta-art) > .elementor-shortcode{display:contents;}
.cta-converge.e-con > .e-con-inner > .elementor-element{position:relative; z-index:2;}

/* The Insights archive's lead card. motion.css makes a lead of .db-card--lead
   inside .insight-grid, which is how the mockup writes it. A Loop Grid renders
   one template for every card, so no card carries --lead, and the class on the
   widget sits two levels above the cards: widget > .elementor-loop-container >
   .e-loop-item > .db-card. So the lead is the grid's first item, addressed
   through that structure. The badge is ::after, because an Elementor container
   already uses ::before for its background overlay.

   Two things the obvious selectors got wrong, both measured on the page:
   motion.css gives .insight-grid display:grid for the mockup's grid of cards,
   which on the widget made the widget a three-column grid and squeezed
   Elementor's loop container into one column (367px of 1140); and the loop
   container opens with a <style> element, so the first card is the first
   div, not :first-child. */
.elementor-widget-loop-grid.insight-grid{display:block;}
.insight-grid .elementor-loop-container > .e-loop-item:first-of-type{grid-column:1 / -1;}
.insight-grid .e-loop-item:first-of-type .db-card--insight{flex-direction:row; --flex-direction:row;
  align-items:stretch;}
.insight-grid .e-loop-item:first-of-type .db-card__img{flex:0 0 52%; aspect-ratio:auto; min-height:300px;}
.insight-grid .e-loop-item:first-of-type .db-card__img img{height:100%;}
.insight-grid .e-loop-item:first-of-type .db-card__body{justify-content:center; padding:34px 38px; flex:1 1 auto;}
.insight-grid .e-loop-item:first-of-type .db-card__h{font-size:clamp(23px,2.7vw,31px); font-weight:700;
  letter-spacing:-0.022em; line-height:1.16;}
.insight-grid .e-loop-item:first-of-type .db-card__body p{font-size:17px;}
.insight-grid .e-loop-item:first-of-type .db-card--insight::after{content:"Latest"; position:absolute;
  z-index:3; left:18px; top:18px; background:var(--blue); color:#fff; font-size:10.5px;
  font-weight:700; letter-spacing:.14em; text-transform:uppercase; padding:5px 11px;
  border-radius:var(--r-pill);}
@media (max-width:980px){
  .insight-grid .e-loop-item:first-of-type .db-card--insight{flex-direction:column; --flex-direction:column;}
  .insight-grid .e-loop-item:first-of-type .db-card__img{flex:none; aspect-ratio:16/9; min-height:0;}
  .insight-grid .e-loop-item:first-of-type .db-card__body{padding:22px 24px 24px;}
}

/* The article layout: content and a sticky rail. .db-layout and .db-rail are
   the stylesheet's; as Elementor containers they need to outrank .e-con's own
   display and position, and the sticky only holds if the layout grid aligns
   its columns to the top rather than stretching them. */
.db-layout.e-con{display:grid; --display:grid; padding:0;}
.db-rail.e-con{position:sticky; top:96px; padding:0; gap:16px;}
.db-layout__main.e-con{padding:0; min-width:0;}
.db-meta.e-con{padding:0; margin-top:14px; font-size:14px;}
.db-rail__cta.e-con{padding:20px 22px; gap:8px;}
.db-related__kicker{margin:56px 0 14px;}
/* The rail reuses the Insight card, compacted: a sticky rail taller than the
   window pins its top and hides its foot, and three full cards with 16:9
   pictures measured 1,967px, which put the call to action out of reach. So
   the picture is a thumbnail beside the title rather than a banner above it,
   still the whole 16:9 frame so the illustration is not cropped, and the
   excerpt stays out. */
.db-rail .e-loop-item .db-card--insight.e-con,
.db-rail .e-loop-item .db-card--insight.e-con > .e-con-inner{flex-direction:row; --flex-direction:row;
  align-items:stretch; flex-wrap:nowrap;}
.db-rail .db-card--insight .db-card__img{flex:0 0 118px; width:118px; aspect-ratio:auto;
  align-self:stretch; display:flex; align-items:center; background:#F4F0E7;}
.db-rail .db-card--insight .db-card__img img{width:100%; height:auto; aspect-ratio:16/9; object-fit:cover;}
.db-rail .db-card--insight .elementor-widget-text-editor{display:none;}
.db-rail .db-card--insight .db-card__body{padding:12px 14px; gap:4px; min-width:0; justify-content:center;}
.db-rail .db-card--insight .db-card__h{font-size:15px; line-height:1.3;}
.db-rail .e-loop-item .db-card--insight.e-con > .e-con-inner{gap:0; --gap:0; --row-gap:0; --column-gap:0;}
.db-rail .db-card--insight .db-card__h,
.db-rail .db-card--insight .db-card__h .elementor-heading-title{max-width:none; font-size:15px; line-height:1.3;}
.db-rail .db-card--insight .db-cap__tag{display:none;}
.db-rail .db-card--insight .db-more{padding-top:2px; font-size:13px;}
@media (max-width:940px){ .db-rail.e-con{position:static;} }

/* The AI readiness check ([db_readiness_check], tools/readiness.js). Every
   colour is a token, so it follows the theme. */
.db-check{max-width:820px;}
.db-check__area{border:0; margin:0 0 34px; padding:0;}
.db-check__area legend{display:flex; flex-direction:column; gap:4px; margin-bottom:10px; padding:0;}
.db-check__area-title{font-family:"Poppins"; font-size:22px; font-weight:600; color:var(--text);}
.db-check__area-intro{margin:0 0 14px; color:var(--text-soft); max-width:62ch;}
.db-check__q{border-top:1px solid var(--line); padding:16px 0;}
.db-check__text{margin:0 0 10px; font-size:16.5px; color:var(--text);}
.db-check__text b{color:var(--blue-deep); font-weight:700; margin-right:4px;}
.db-check__opts{display:flex; flex-wrap:wrap; gap:8px;}
.db-check__opt{position:relative; cursor:pointer;}
.db-check__opt input{position:absolute; opacity:0; inset:0; margin:0; cursor:pointer;}
.db-check__opt span{display:inline-block; padding:8px 16px; border:1px solid var(--line);
  border-radius:var(--r-pill); font-family:"Poppins"; font-size:14.5px; color:var(--text-soft);
  background:var(--surface); transition:background .15s, border-color .15s, color .15s;}
.db-check__opt:hover span{border-color:var(--blue);}
.db-check__opt input:checked + span{background:var(--blue-deep); border-color:var(--blue-deep); color:#fff;}
.db-check__opt input:focus-visible + span{outline:2px solid var(--blue); outline-offset:2px;}
.db-check__bar{position:sticky; bottom:0; z-index:5; display:flex; align-items:center;
  justify-content:space-between; gap:16px; padding:14px 0; background:var(--ground);
  border-top:1px solid var(--line);}
.db-check__progress{font-size:14.5px; color:var(--text-soft);}
.db-check__go[disabled]{opacity:.45; cursor:not-allowed;}
.db-check__result{margin-top:30px; padding:28px; border:1px solid var(--line);
  border-radius:var(--r); background:var(--surface); outline:none;}
.db-check__score{margin:0; font-size:18px; color:var(--text-soft);}
.db-check__score b{font-family:"Poppins"; font-size:52px; font-weight:800; color:var(--text);
  letter-spacing:-0.03em; margin-right:6px;}
.db-check__band{font-size:24px; margin:4px 0 6px;}
.db-check__band-text{color:var(--text-soft); margin:0 0 20px;}
.db-check__areas{display:flex; flex-direction:column; gap:12px; margin:8px 0 24px;}
.db-check__row-label{display:flex; justify-content:space-between; font-size:15px; color:var(--text); margin-bottom:5px;}
.db-check__row-n{color:var(--text-soft); font-variant-numeric:tabular-nums;}
.db-check__track{height:8px; border-radius:var(--r-pill); background:var(--line); overflow:hidden;}
.db-check__fill{display:block; height:100%; background:var(--blue); border-radius:inherit;}
.db-check__next-h{font-size:19px; margin:0 0 8px;}
.db-check__next{margin:0 0 22px; padding-left:20px; color:var(--text-soft);}
.db-check__next li{margin-bottom:10px;}
.db-check__next b{color:var(--text);}
.db-check__read{display:inline-block; margin-top:4px; color:var(--blue); font-weight:600; text-decoration:none;}
.db-check__read:hover{text-decoration:underline;}
.db-check__again{margin-top:4px;}

/* The header logo. The Site Logo widget serves the full 2x image and this
   sizes it, keeping its own proportions: a fixed 135 x 33 thumbnail suited
   the old logo, and cropped and blurred the new one. logo-intro.js lays the
   first-visit animation over this exact box. */
.elementor-location-header .db-brand img{height:38px; width:auto; max-width:none; display:block;}
@media (max-width:760px){ .elementor-location-header .db-brand img{height:32px;} }

/* The workflow diagram (free tools drop-in, flow-band.css). The drop-in asked
   for this in preview/motion.css and a motion rebuild; preview/ isn't in this
   copy of the kit, so it lives here, which the motion build never overwrites.

   Six stages across is unreadable at phone width, and scaling it to fit makes
   the type about four pixels tall, so it keeps a minimum width and the band
   scrolls sideways. The stage list is on the page as text underneath either
   way. The SVG paints itself from the theme tokens, so it follows the
   light/dark toggle with no second file.

   .db-wrap is the mockup's wrapper; on the site the band's content is in
   Elementor's .e-con-inner, and without that selector the 820px minimum
   pushed the whole page sideways on a phone instead of scrolling the band. */
.db-flow { margin: 0; }
.db-flow > svg { display: block; width: 100%; min-width: 820px; height: auto; }
.db-band--flow > .db-wrap,
.db-band--flow.e-con > .e-con-inner { overflow-x: auto; overflow-y: hidden;
  -webkit-overflow-scrolling: touch; padding-bottom: 6px; }
.db-flow figcaption { margin-top: 14px; font-size: .86rem; color: var(--text-soft);
  min-width: 820px; }
@media (min-width: 1040px) {
  .db-flow > svg, .db-flow figcaption { min-width: 0; }
}

/* Free tool downloads: the file buttons on a tool page, with the file size. */
.db-downloads{display:flex; flex-wrap:wrap; gap:10px; margin:0 0 6px;}
.db-downloads .db-btn span{font-weight:400; opacity:.75; font-size:13px;}

/* Button widgets. The importer can only class the widget wrapper, so every
   .db-btn rule above also names the link inside a button widget, and excludes
   the wrapper itself. The wrapper stays unpainted and the container aligns it
   — styling the wrapper as the pill painted it as a blue bar the width of a
   column, and pinning it with align-self sat the header button off-centre. */
.elementor-widget.db-btn .elementor-button{justify-content:center; line-height:1.2;}
@media (max-width:760px){
  :is(.db-hero__cta, .db-cta__btns) .elementor-widget.db-btn .elementor-button{width:100%;}
}

/* A band with less air, for the answer block and the at-a-glance table, which
   both sit tight under the thing above them. */
.db-band--tight{padding-block:0; margin-block:-8px 8px;}
.db-band--tight .db-wrap{padding-block:0;}

/* The proof strip's inner grid. The importer emits one HTML widget rather than
   four, because four widgets in a row is four things to accidentally drag. */
.db-proof__inner{display:grid; grid-template-columns:repeat(auto-fit,minmax(170px,1fr)); gap:18px;}
.db-proof__inner a{text-decoration:none;}

/* Signals — the "you might recognise one of these" block. One sentence per
   line, no bullets, because the brand guide asks for prose over bullet points
   and a list of six bullets reads as a specification rather than a nudge. */
.db-signals{display:grid; grid-template-columns:repeat(auto-fit,minmax(300px,1fr)); gap:0 36px;}
.db-signal{border-top:1px solid var(--line); padding:14px 0; margin:0;
  font-size:17px; color:var(--text-soft); max-width:none;}

/* The capability tag line under a service page's What we do section. */
.db-cap__tags{font-family:"Poppins"; font-size:14px; color:var(--text-faint);
  margin-top:20px; max-width:none;}

/* Key numbers on a case study. Sits inside .db-proof, so it inherits the ink
   background and the white type. */
.db-keynum{min-width:0;}

/* At-a-glance definition list. */
.db-glance dl{margin:0;}

/* FAQ. Native <details>, so it works with no JavaScript, is keyboard
   accessible for free, and can be opened by the browser's find-in-page. */
.db-faq{max-width:78ch;}
.db-faq__item{border-top:1px solid var(--line);}
.db-faq__item:last-child{border-bottom:1px solid var(--line);}
.db-faq__item summary{list-style:none; cursor:pointer; padding:18px 36px 18px 0;
  position:relative; font-family:"Poppins"; font-size:18.5px; font-weight:500; color:var(--text);}
.db-faq__item summary::-webkit-details-marker{display:none;}
.db-faq__item summary::after{content:""; position:absolute; right:6px; top:50%;
  width:9px; height:9px; margin-top:-6px; border-right:2px solid var(--blue);
  border-bottom:2px solid var(--blue); transform:rotate(45deg);
  transition:transform .2s ease;}
.db-faq__item[open] summary::after{transform:rotate(-135deg); margin-top:-2px;}
.db-faq__item summary:hover{color:var(--blue-deep);}
.db-faq__a{padding:0 0 18px; color:var(--text-soft);}
.db-faq__a p{margin:0 0 10px;}
.db-faq__a p:last-child{margin-bottom:0;}

/* Glossary. A definition list, because that is what it is — screen readers
   announce it as paired terms and values, which a grid of divs does not. */
.db-glossary{display:grid; grid-template-columns:repeat(auto-fit,minmax(310px,1fr));
  gap:0 36px; margin:0;}
.db-glossary__item{border-top:1px solid var(--line); padding-top:16px; margin-top:4px;}
.db-glossary dt{font-family:"Poppins"; font-size:17px; font-weight:500; color:var(--text);}
.db-glossary dd{margin:6px 0 18px; font-size:15.5px; color:var(--text-soft);}

/* The closing call to action. Ink background, so the buttons need the glass
   treatment rather than the ghost one. */
.db-cta{text-align:left;}
.db-cta .db-sec{color:#fff; max-width:22ch;}
.db-cta .db-lede{color:#A6AEBA;}
/* A ghost button takes its colour from the surface behind it. On the cream
   ground that is ink on a pale border; on any of the three dark surfaces it has
   to flip, or it renders ink-on-near-black at about 1.2:1 and disappears.
   Caught in the preview on the homepage hero's "See the work". */
.db-hero .db-btn--ghost:not(.elementor-widget), .db-hero .elementor-widget.db-btn--ghost .elementor-button,
.db-band--ink .db-btn--ghost:not(.elementor-widget), .db-band--ink .elementor-widget.db-btn--ghost .elementor-button,
.db-cta .db-btn--ghost:not(.elementor-widget), .db-cta .elementor-widget.db-btn--ghost .elementor-button{
  color:#fff; border-color:rgba(255,255,255,.34); background:transparent;}
.db-hero .db-btn--ghost:not(.elementor-widget):hover, .db-hero .elementor-widget.db-btn--ghost .elementor-button:hover,
.db-band--ink .db-btn--ghost:not(.elementor-widget):hover, .db-band--ink .elementor-widget.db-btn--ghost .elementor-button:hover,
.db-cta .db-btn--ghost:not(.elementor-widget):hover, .db-cta .elementor-widget.db-btn--ghost .elementor-button:hover{
  color:#fff; border-color:#fff; background:rgba(255,255,255,.08);}

/* Footnotes, source lines and the "please confirm" notes that ship with the
   draft content. Small, grey, and easy to spot when you are hunting for the
   things still to fill in. */
.db-footnote{font-size:14px; color:var(--text-faint); margin-top:16px;}
.db-cta .db-footnote{color:#7A8390;}

/* Jargon Buster output. */
.db-jargon__out h3{font-size:13px; font-family:"Poppins"; letter-spacing:.1em;
  text-transform:uppercase; color:var(--blue-deep); margin:0 0 6px;}
.db-jargon__out h3 + p{margin-bottom:18px;}
.db-jargon__out ul{margin:0; padding-left:20px; color:var(--text-soft); font-size:16px;}
.db-jargon__out li{margin-bottom:5px;}
.db-jargon__out p:last-child{margin-bottom:0;}

/* Elementor puts every widget in a wrapper div. These two rules stop the
   wrappers adding margins the design system did not ask for, which is the most
   common reason a generated page looks slightly loose compared with the design. */
.db-band > .elementor-widget:not(:last-child){margin-bottom:0;}
.db-band .elementor-widget-html,
.db-band .elementor-widget-shortcode{width:100%;}


/* ---------------------------------------------------------- Insights ------
   Each insight has its own flat illustration on cream. The picture runs to
   the card's edges with no inset, so the card's rounded corners clip it, and
   the card sits on white so the cream reads as a picture rather than the page.
   ------------------------------------------------------------------------- */

.db-card--insight{padding:0; overflow:hidden;}
/* Elementor pads a container's inner wrapper 10px top and bottom by default,
   which left a strip of white above every card picture (and below the lead
   card's). Measured on the Loop Grid; the extra class outranks Elementor's
   per-element rule. */
.e-loop-item .db-card--insight.e-con,
.e-loop-item .db-card--insight.e-con > .e-con-inner{padding:0; --padding-top:0; --padding-bottom:0;}
.db-card--insight .db-card__img{margin:0; border-radius:0; aspect-ratio:16/9;}
.db-card--insight .db-card__body{padding:20px 22px 22px; display:flex;
  flex-direction:column; gap:8px; flex:1;}
.db-card--insight h3{font-size:19px; font-weight:600;}
.db-card--insight .db-more{padding-top:10px;}

/* The lead image on an article page. Full width of the measure, and the only
   place on the site where a black block is allowed to be this large. */
.db-leadimg{aspect-ratio:16/9; border-radius:var(--r); overflow:hidden;
  margin:0 0 30px; background:var(--well);}
.db-leadimg img{width:100%; height:100%; object-fit:cover; display:block;}


/* ------------------------------------------------------------ hero video --
   The homepage hero can take a looping background video instead of a still.
   Three rules make it behave rather than become the heaviest thing on the site:

   1. The poster image is always present and always styled. It is what shows
      before the video loads, on a slow connection, on mobile, and for anyone
      who has asked for reduced motion. If the video never arrives, the hero is
      still correct — it just does not move.
   2. The video is only ever decoration. Nothing in it carries meaning that is
      not also in the headline, so hiding it costs the reader nothing.
   3. It sits under the same scrim as a still, so the contrast behind the
      headline does not change when it loads.
   ------------------------------------------------------------------------- */

.db-hero video.db-hero__bg,
.db-hero img.db-hero__bg{
  position:absolute; inset:0; width:100%; height:100%;
  object-fit:cover; z-index:0; display:block;}

/* The video sits above the poster once it can play, and fades in rather than
   snapping, so a slow connection degrades quietly. */
.db-hero video.db-hero__bg{opacity:0; transition:opacity .6s ease; z-index:1;}
.db-hero video.db-hero__bg.is-playing{opacity:1;}
.db-hero__scrim{z-index:2;}
.db-hero .db-wrap{z-index:3;}

/* Anyone who has asked their device to reduce motion gets the poster, full
   stop. This is not a nicety — for some people looping background motion is a
   genuine accessibility problem. */
@media (prefers-reduced-motion:reduce){
  .db-hero video.db-hero__bg{display:none!important;}
}

/* ---------------------------------------------------------------- tables --
 *
 * One table style, added for the cookie policy and usable anywhere. Scrolls
 * horizontally inside its own wrapper rather than widening the page, because a
 * four-column table and a 360px phone cannot both win and the page losing is
 * much worse than the table losing.
 */
/* A region that scrolls must be reachable by keyboard, or someone who cannot
   use a pointer can read the first three columns and nothing else. The markup
   carries tabindex="0" and a label; this gives the focus somewhere to show. */
.db-tablewrap:focus-visible{outline:2px solid var(--blue); outline-offset:2px;}
.db-tablewrap{
  overflow-x:auto; border:1px solid var(--line); border-radius:12px;
  background:var(--surface); margin:20px 0;
  -webkit-overflow-scrolling:touch;
}
.db-table{border-collapse:collapse; width:100%; min-width:560px; font-size:15px;}
/* --band-deep is a DARK plate in both themes — that is the point of it — so
   the header ink is a fixed light value rather than var(--text). Using --text
   here made the light theme render dark-on-dark at 1:1. */
.db-table th{
  background:var(--band-deep); color:#E9ECF1; text-align:left;
  font-family:"Poppins",system-ui,sans-serif; font-weight:600;
  font-size:11.5px; letter-spacing:.08em; text-transform:uppercase;
  padding:11px 14px; border-bottom:1px solid var(--line);
}
.db-table td{padding:11px 14px; border-top:1px solid var(--line); vertical-align:top; color:var(--text-soft);}
.db-table td:first-child{color:var(--text); font-weight:500;}
.db-table code{
  font-family:ui-monospace,SFMono-Regular,Menlo,monospace; font-size:.86em;
  background:var(--surface-2); border:1px solid var(--line);
  padding:1px 6px; border-radius:5px; word-break:break-word;
}
/* The caption sits ABOVE the table and is the only place a table is allowed to
   explain itself. caption-side:top is not the browser default everywhere. */
.db-table__cap{
  caption-side:top; text-align:left; padding:14px 14px 4px;
  color:var(--text-soft); font-size:14.5px; line-height:1.5;
}
@media (max-width:560px){ .db-table{min-width:460px; font-size:14px;} }

/* The footer's cookie-settings trigger. A real link, not a button styled as
   one, because it goes somewhere as far as the reader is concerned. */
.db-cookie-link{
  background:none; border:0; padding:0; font:inherit; color:inherit;
  text-decoration:underline; text-underline-offset:3px; cursor:pointer;
}
.db-cookie-link:hover{color:var(--blue);}

/* The service each proof figure belongs to, above the number. The proof strip
   is a dark band in both themes, so the colour is set, not taken from --text. */
.proof-fig__svc{font-family:"Poppins"; font-size:11.5px; font-weight:600; letter-spacing:.14em;
  text-transform:uppercase; color:#6FCCFF; margin-bottom:10px;}

/* The hero headline's lines are masks (.hero-line, overflow:hidden) for the
   slide-up reveal. At the headline's tight line-height the mask stopped just
   above the descenders, cutting the tail off the g in "digital". Room below
   each line, taken back with a negative margin, so the spacing is unchanged. */
.db-hero .hero-line{padding-bottom:.22em; margin-bottom:-.22em;}
/* The mask is now taller, so the hidden line starts lower to stay out of it
   (motion.css hides it at 102%). The revealed state (.is-in) still wins. */
.db-hero .hero-line > span{transform:translate3d(0,135%,0);}

/* Share links at the end of an insight (mu-plugin inc/share.php). Plain
   links, styled as quiet pills so they read as options, not calls to action;
   the device's own share sheet ("Share…"), where there is one, is the only
   filled button. */
.db-share{margin-top:44px; padding-top:26px; border-top:1px solid var(--line);}
.db-share__h{font-family:"Poppins"; font-size:12px; font-weight:600; letter-spacing:.14em;
  text-transform:uppercase; color:var(--text-soft); margin:0 0 14px;}
.db-share__list{list-style:none; margin:0; padding:0; display:flex; flex-wrap:wrap; gap:8px;}
.db-share__list li{margin:0; padding:0;}
.db-share__list li::before{content:none;}
.db-share__btn{display:inline-flex; align-items:center; min-height:40px; padding:8px 16px;
  font:500 14px/1.2 "Poppins",system-ui,sans-serif; color:var(--text); background:var(--surface);
  border:1px solid var(--line); border-radius:var(--r-pill); text-decoration:none; cursor:pointer;
  transition:border-color .15s, color .15s;}
.db-share__btn:hover{border-color:var(--blue); color:var(--blue-deep);}
.db-share__btn:focus-visible{outline:2px solid var(--blue); outline-offset:2px;}
.db-share__btn--primary{background:var(--blue); border-color:var(--blue); color:#fff;}
.db-share__btn--primary:hover{background:var(--blue-deep); border-color:var(--blue-deep); color:#fff;}
.db-share__note{margin:10px 0 0; min-height:1.4em; font-size:13.5px; color:var(--text-faint);
  overflow-wrap:anywhere;}

/* Case study cards (the Our work archive and related work). Elementor pads the
   card's inner wrapper 10px top and 22px at the sides, which left the picture
   inset from the card's edges. The picture now runs to the top and both
   sides, clipped by the card's rounded corners; only the text keeps the
   padding. */
.e-loop-item .work-tile.e-con > .e-con-inner{padding-top:0;}
/* Stretched rather than sized: Elementor sets a widget's width from its own
   variable, which kept the picture at the padded width and left a 45px gap on
   the right. Stretch plus negative side margins fills the card edge to edge. */
.e-loop-item .work-tile.e-con > .e-con-inner > .db-card__img{margin:0 -22px 16px; width:auto !important;
  max-width:none; align-self:stretch; border-radius:0;}
.e-loop-item .work-tile .db-card__img img{width:100%; height:100%; object-fit:cover; display:block;}

/* Our work: masonry. Loop Grid's masonry lets each card keep its own height;
   varying the picture's proportions down the grid gives it the stagger. The
   loop container opens with a <style>, so cards count by type, not child. */
.db-work-grid .e-loop-item:nth-of-type(3n+1) .work-tile .db-card__img{aspect-ratio:4/5;}
.db-work-grid .e-loop-item:nth-of-type(3n+2) .work-tile .db-card__img{aspect-ratio:16/10;}
.db-work-grid .e-loop-item:nth-of-type(3n) .work-tile .db-card__img{aspect-ratio:1/1;}
/* A case study with no picture yet keeps its top padding, so its text does not
   sit against the card's top edge. */
.e-loop-item .work-tile.e-con > .e-con-inner:not(:has(.db-card__img img)){padding-top:22px;}

/* The logo story on the About page (mu-plugin inc/logo-story.php): the logo
   animation large, beside what it shows. It sits on an ink band, which stays
   dark in both themes, so every colour here is set rather than taken from
   --text. The animation paints its own ink backdrop, rounded to sit as a
   picture on the band. */
.db-logo-story{display:grid; grid-template-columns:minmax(0,5fr) minmax(0,7fr); gap:clamp(28px,5vw,64px);
  align-items:center; margin:0;}
.db-logo-story .db-kicker{color:#6FCCFF;}
.db-logo-story .db-sec{color:#fff; margin-top:10px; line-height:1.12;}
.db-logo-story__text{font-style:normal;}
.db-logo-story__text p{color:#C9D0D8; font-size:17px; line-height:1.6; max-width:48ch; margin:0 0 14px;}
.db-logo-story__play{margin-top:10px;}
.db-logo-story__stage{border-radius:var(--r); overflow:hidden; box-shadow:0 18px 44px rgba(0,0,0,.45);
  aspect-ratio:1900/1070; background:#0A0E13;}
.db-logo-story__stage svg{display:block; width:100%; height:100%;}
@media (max-width:900px){
  .db-logo-story{grid-template-columns:1fr;}
  .db-logo-story__stage{order:-1;}
}

/* The homepage's Insights panel ([db_insight_cards]): the archive's insight
   card, picture included, three across. */
.db-insight-cards{margin-top:28px;}
.db-insight-cards .db-card--insight{display:flex; flex-direction:column; text-decoration:none; color:inherit;}
.db-insight-cards .db-card__img img{width:100%; height:100%; object-fit:cover; display:block;}
.db-insight-cards__all{margin-top:26px;}
@media (max-width:900px){ .db-insight-cards.db-grid3--three{grid-template-columns:1fr;} }

/* The homepage's "Selected experience" panel ([db_case_cards]): the case
   study card with its picture running to the card's edges. */
.db-case-cards{margin-top:28px;}
.db-case-card{padding:0; overflow:hidden; display:flex; flex-direction:column; text-decoration:none; color:inherit;}
.db-case-card .db-card__img{margin:0; border-radius:0; aspect-ratio:16/10; overflow:hidden;}
.db-case-card .db-card__img img{width:100%; height:100%; object-fit:cover; display:block;}
.db-case-card .db-card__body{padding:20px 22px 22px; display:flex; flex-direction:column; gap:8px; flex:1;}
.db-case-card .db-card__h{font-size:19px; font-weight:600; margin:0;}
.db-case-card p{margin:0; color:var(--text-soft);}
.db-case-card .db-go{margin-top:auto; padding-top:10px; font-weight:600; color:var(--text);}
.db-case-cards__all{margin-top:26px;}
@media (max-width:900px){ .db-case-cards.db-grid3--three{grid-template-columns:1fr;} }

/* Cards with a picture (the cards block's optional "image"): the picture runs
   to the card's edges and the text sits in a padded body under it. Used by the
   Related panel on every case study. */
.db-card--pic{padding:0; overflow:hidden; display:flex; flex-direction:column;}
.db-card--pic .db-card__img{margin:0; border-radius:0; aspect-ratio:16/9; overflow:hidden;}
.db-card--pic .db-card__img img{width:100%; height:100%; object-fit:cover; display:block;}
.db-card--pic .db-card__body{padding:18px 22px 22px; display:flex; flex-direction:column; gap:8px; flex:1;}
.db-card--pic .db-card__body h3{margin:0;}
.db-card--pic .db-more{margin-top:auto;}

/* The footer's copyright line ([db_copyright]), under the link columns. The
   footer is dark in both themes, so the colour is set. */
.db-foot__copy{margin:8px 0 0; padding-top:18px; border-top:1px solid rgba(255,255,255,.10);
  font-size:13px; color:#8B94A0;}

/* Band spacing, tightened. Each band had 64px of padding plus the 10px
   Elementor puts inside every container, so 74px above and below its content
   and about 148px between one section's last line and the next heading.
   Elementor's 10px goes (tight bands keep theirs, which is all the room they
   have), bands step down to 56px, and the long reads, where one section
   follows another all the way down, go tighter still: 44px on a case study,
   36px for the sections inside an insight. Phones keep their own values. */
.db-band.e-con:not(.db-band--tight) > .e-con-inner{padding-block:0;}
@media (min-width:761px){
  .db-band{padding-block:56px;}
  .single-case_study .db-band:not(.db-band--tight){padding-block:44px;}
  .db-prose .db-band:not(.db-band--tight){padding-block:36px;}
}
/* A heading that opens a band gets no top margin of its own. Article headings
   carry 34px for when they fall mid-text; at the top of a section that doubled
   the band's padding. */
.db-band.e-con > .e-con-inner > .elementor-widget-heading:first-child .elementor-heading-title,
.db-band.e-con > .e-con-inner > .elementor-widget:first-child h2:first-child{margin-top:0;}

/* The service pages' "what this covers" strip, as small tags rather than one
   long dotted line. The shortcode writes " · " between the tags; setting the
   paragraph's font size to 0 hides those separators, and each tag sets its
   own size back. */
.db-cap__tags{display:flex; flex-wrap:wrap; gap:8px; font-size:0; line-height:1; margin:20px 0 0;}
.db-cap__tags span{display:inline-block; font:500 13px/1.2 "Poppins",system-ui,sans-serif; letter-spacing:0;
  padding:7px 13px; border-radius:var(--r-pill); background:var(--chip-bg); color:var(--chip-fg);}

/* The top of the page, tightened. The short page top with a picture was a
   fixed min(62vh, 580px) tall (motion.css), so its copy ended about 350px
   down and the rest was empty picture: 558px before the answer block even
   began. It now ends 48px below its copy. And the answer block's band (the
   tight band) had picked up the 56px band padding added above, top and
   bottom; it gets 28px above and nothing extra below. */
.db-hero.db-hero--short.db-hero--lit.e-con{min-height:0; --min-height:0;}
.db-hero.db-hero--short.db-hero--lit.e-con > .e-con-inner{padding-block:104px 48px;}
.db-band.db-band--tight.e-con{padding-block:28px 0;}
@media (max-width:760px){
  .db-hero.db-hero--short.db-hero--lit.e-con > .e-con-inner{padding-block:46px 36px;}
  .db-band.db-band--tight.e-con{padding-block:20px 0;}
}

/* ------------------------------------------------- phone header, 30 Sep -- */
/* Four things measured at 390px on the live site.
   1. The desktop menu hides below 1040px, but .db-navpill kept its white pill
      background and 5px padding, so a 12px white dot sat in the middle of the
      bar. The rule above lost to Elementor's widget display; this one wins.
   2 and 3. The header is always a dark surface: it sits on the hero (--well)
      until the page scrolls, then on --band-deep, in both themes. The theme
      toggle and the burger were drawn in the page's colours instead: in light
      mode a 6% black fill and a dark icon, and burger lines in --text, which
      is near-black in light mode. Both are now light on dark, always, with
      the same ring so they read as a pair.
   4. The phone header is 93px tall, but the hero's copy started 60px down,
      so the tagline sat under the logo. The phone hero now starts its copy
      clear of the bar. */
@media (max-width:1040px){
  .db-nav .db-navpill,
  .db-nav .elementor-widget-nav-menu.db-navpill{display:none!important;}
  /* The 44px theme toggle is added by motion.js after the first paint, which
     took the bar from 84px to 93px and pushed the whole page down 9px
     (layout shift 0.11 at 412px, measured 2 Oct 2026). Hold the room for it. */
  .db-nav{min-height:93px;}
}
.db-nav .db-themer,
:root[data-theme="light"] .db-nav .db-themer,
:root[data-theme="light"] .db-nav.scrolled .db-themer{
  width:44px; height:44px; flex:0 0 44px; color:#fff;
  background:rgba(255,255,255,.12); border:1px solid rgba(255,255,255,.5);}
.db-nav .db-themer:hover,
:root[data-theme="light"] .db-nav .db-themer:hover{background:rgba(255,255,255,.22);}
.db-nav .db-themer svg{width:20px; height:20px; stroke-width:2;}
.db-nav .db-burger{padding:14px 12px; border-radius:50%;
  background:rgba(255,255,255,.12); border:1px solid rgba(255,255,255,.5);}
.db-nav .db-burger:hover{background:rgba(255,255,255,.22);}
.db-nav .db-burger span{background:#fff; height:2px;}
.db-nav .db-burger[aria-expanded="true"] span:nth-child(1){transform:translateY(6px) rotate(45deg);}
.db-nav .db-burger[aria-expanded="true"] span:nth-child(3){transform:translateY(-6px) rotate(-45deg);}
/* The overlay follows the page (--ground), so in light mode it is cream, and
   the header logo is the white-lettered one: open the menu and the wordmark
   vanished, leaving two blue bars. The bar stays dark while the menu is open,
   so the logo, the toggle and the close button look as they do everywhere
   else, and the menu opens beneath it. */
html.menu-open .db-nav{background:var(--band-deep);}
@media (max-width:760px){
  .db-hero.e-con > .e-con-inner,
  .db-hero--lit.e-con > .e-con-inner,
  .db-hero--short.db-hero--lit.e-con > .e-con-inner,
  .db-hero.db-hero--short.db-hero--lit.e-con > .e-con-inner{padding-top:104px;}
}

/* ------------------------------------------------ footer headings, 2 Oct -- */
/* The footer's column headings were H4s, which skipped two levels and failed
   Lighthouse's heading-order check. As H2s they took the browser's H2 size,
   because the footer template sets no size of its own. Keep them at the size
   the H4s had, whatever level they are. */
.elementor-location-footer .elementor-widget-heading .elementor-heading-title{font-size:1em;}

/* ------------------------------------------------- product panels, 5 Oct -- */
/* [db_products]: the products sold with a demo (Tools and Products pages).
   A wider picture than a case card, and two actions at the foot, so the card
   itself is not a link. */
.db-product .db-card__img{aspect-ratio:16/9;}
.db-product h3{font-size:23px;}
.db-product__actions{margin-top:auto; padding-top:14px; display:flex; flex-wrap:wrap;
  align-items:center; gap:12px 22px;}
.db-product .db-go{font-family:"Poppins"; font-size:15px; color:var(--blue-deep);}
.db-product .db-go:hover{color:var(--blue);}
