/* g-cwv */
.wp-site-blocks>header.wp-block-template-part{margin-block-start:0!important}@keyframes gcwv-show{to{visibility:visible}}body:not(:has(main ~ *)) .g-hero:not(:has(+ *))>.g-hero-content,body:not(:has(main ~ *)) #hero:not(:has(+ *))>.g-home-hero-media video,body:not(:has(main ~ *)) #hero:not(:has(+ *))::before{visibility:hidden;animation:gcwv-show 0s linear 2.5s forwards}
/* gill-li-follow */
body #linkedin .g-linkedin-follow .g-cta-teal{display:inline-flex !important;align-items:center;gap:10px}body #linkedin .g-linkedin-follow .g-cta-teal::before{content:"";flex:0 0 18px;width:18px;height:18px;background:url("data:image/svg+xml,%3Csvg xmlns=%22http://www.w3.org/2000/svg%22 viewBox=%220 0 24 24%22%3E%3Cpath fill=%22%230A66C2%22 d=%22M20.45 20.45h-3.55v-5.57c0-1.33-.03-3.04-1.85-3.04-1.85 0-2.14 1.45-2.14 2.94v5.67H9.35V9h3.41v1.56h.05c.48-.9 1.64-1.85 3.37-1.85 3.6 0 4.27 2.37 4.27 5.46v6.28zM5.34 7.43a2.06 2.06 0 1 1 0-4.12 2.06 2.06 0 0 1 0 4.12zM7.12 20.45H3.56V9h3.56v11.45zM22.22 0H1.77C.79 0 0 .77 0 1.73v20.54C0 23.23.79 24 1.77 24h20.45c.98 0 1.78-.77 1.78-1.73V1.73C24 .77 23.2 0 22.22 0z%22/%3E%3C/svg%3E") center/contain no-repeat !important;display:block !important}body #linkedin .g-linkedin-follow .g-cta-teal:hover::before,body #linkedin .g-linkedin-follow .g-cta-teal:focus-visible::before{filter:brightness(0) invert(1)}
/* g-onegill-extra */

/* One Gill module CSS. In the TEMPLATE, not Global Styles, because a
   concurrent build session overwrites the Global Styles record. */

/* ══ PRODUCT MODULES THAT HAD NO CSS ════════════════════════════════════════
      Added 16 Sep 2026. Four modules on the product estate were rendering as
      raw HTML because nothing in Global Styles or the page-product template
      ever matched them. Verified by asking the browser, for every visible
      element carrying a g- class, whether ANY rule in the CSSOM matches it.
   ────────────────────────────────────────────────────────────────────────── */

/* ── 1. The model chooser, .g-var. Nine range pages. It was a bare stack: a
      run-together "ModelChoose it whenHow to buy it" header and three jammed
      links per row. Three columns on desktop, stacked on a phone, colours
      inherited so it works on the dark navy band and on a light one. ─────── */

.g-var { margin-top: 28px; border-top: 1px solid currentColor; }
.g-var__head,
.g-var__row {
  display: grid;
  grid-template-columns: minmax(200px, 1.1fr) minmax(220px, 1.9fr) minmax(220px, 1.2fr);
  gap: 12px 32px;
  align-items: start;
}
.g-var__head {
  padding: 12px 0;
  font-size: 11px;
  font-weight: 700;
  letter-spacing: .1em;
  text-transform: uppercase;
  opacity: .65;
}
.g-var__row { padding: 22px 0; border-top: 1px solid; border-color: color-mix(in srgb, currentColor 22%, transparent); }
.g-var__row--guard { opacity: .92; }

.g-var__model { margin: 0 0 4px; font-size: 20px; font-weight: 700; line-height: 1.25; }
.g-var__model a { text-decoration: none; }
.g-var__model a:hover { text-decoration: underline; }
.g-var__note { margin: 0; font-size: 14px; line-height: 1.45; opacity: .78; }

/* The per-row "Choose it when" label repeats the column header, so it is for
   the stacked view only. */
.g-var__k { display: none; }
.g-var__when p { margin: 0; font-size: 15px; line-height: 1.55; }

.g-var__act { display: flex; flex-wrap: wrap; align-items: center; gap: 10px 16px; }
.g-var__state {
  display: inline-block;
  padding: 3px 9px;
  font-size: 11px;
  font-weight: 700;
  letter-spacing: .08em;
  text-transform: uppercase;
  border: 1px solid;
  border-color: color-mix(in srgb, currentColor 45%, transparent);
}
.g-var__buy { display: flex; flex-wrap: wrap; align-items: center; gap: 8px 18px; }
/* One solid button per row, nine rows deep, shouts louder than the model
   names. The primary action keeps a button shape but stays outlined. */
.g-var__cta {
  display: inline-flex;
  align-items: center;
  min-height: 34px;
  padding: 6px 14px;
  font-size: 13px;
  font-weight: 700;
  text-decoration: none;
  border: 1.5px solid;
  border-color: color-mix(in srgb, currentColor 55%, transparent);
}
.g-var__cta:hover { border-color: currentColor; background: color-mix(in srgb, currentColor 10%, transparent); }
.g-var__more,
.g-var__doc { font-size: 13px; font-weight: 600; text-decoration: underline; text-underline-offset: 3px; }

@media (max-width: 900px) {
  .g-var__head { display: none; }
  .g-var__row { grid-template-columns: 1fr; gap: 14px; }
  .g-var__k {
    display: block;
    margin-bottom: 4px;
    font-size: 11px;
    font-weight: 700;
    letter-spacing: .1em;
    text-transform: uppercase;
    opacity: .65;
  }
}

/* ── 2. The on-this-page bar, .g-secnav__inner. Its band already had a linen
      ground and a link colour, but the links themselves had no layout, so they
      ran together as one underlined string. ─────────────────────────────── */

.g-secnav__inner {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 8px 30px;
}
.g-secnav__inner a {
  display: inline-flex;
  align-items: center;
  min-height: 36px;
  font-size: 13px;
  font-weight: 600;
  letter-spacing: .01em;
  text-decoration: none;
}
.g-secnav__inner a:hover { text-decoration: underline; text-underline-offset: 4px; }
@media (max-width: 700px) {
  .g-secnav__inner {
    flex-wrap: nowrap;
    overflow-x: auto;
    -webkit-overflow-scrolling: touch;
    overscroll-behavior-x: contain;
    gap: 22px;
  }
  .g-secnav__inner a { white-space: nowrap; }
}

/* ── 3. The hub and range FAQ, .g-faq. Twenty-two pages. It is a plain
      h3 + p list, not the <details> accordion the model pages use, so it is
      styled as a clean question list rather than faked into an accordion.
      Answers stay open, which is what the AI-extraction rule wants. ─────── */

.g-faq { margin-top: 28px; border-top: 1px solid var(--wp--preset--color--pale-grey); }
.g-faq__row { padding: 22px 0; border-bottom: 1px solid var(--wp--preset--color--pale-grey); }
.g-faq__row > h3 {
  margin: 0 0 8px;
  font-size: 19px;
  font-weight: 700;
  line-height: 1.35;
  color: var(--wp--preset--color--dark-teal);
}
.g-faq__row > p { margin: 0; font-size: 16px; line-height: 1.6; max-width: 72ch; }
.g-faq__row > p + p { margin-top: 10px; }
.g-ground-dark .g-faq,
.g-ground-dark .g-faq__row { border-color: color-mix(in srgb, currentColor 25%, transparent); }
.g-ground-dark .g-faq__row > h3 { color: inherit; }

/* The nine top-level pages use a <details> variant, .g-faq__item, with all its
   styling inline and `list-style:none`, which removes the disclosure triangle
   and puts nothing back. Nothing on the row said it opened. Same + and en-dash
   marker the model pages use for .g-vp-faq. */

.g-faq__item > summary {
  list-style: none;
  display: flex;
  justify-content: space-between;
  align-items: flex-start;
  gap: 16px;
}
.g-faq__item > summary::-webkit-details-marker { display: none; }
.g-faq__item > summary::after {
  content: "+";
  flex: none;
  font-size: 22px;
  line-height: 1;
  color: var(--wp--preset--color--dark-teal);
}
.g-faq__item[open] > summary::after { content: "\2013"; }

/* ── 4. Card text blocks stop floating mid-card.
      `.g-card > :last-child{margin-top:auto}` lines CTAs up when the last child
      is a footer. On the two-part cards (image plus one text block) it hits the
      text block itself, and an auto margin beats flex-grow for free space, so
      the whole block was pushed to the bottom and the headings sat at four
      different heights across one row. Those blocks carry no class. ─────── */

.g-card > div:not([class]):last-child { margin-top: 0; }

/* ── 5. THE CARD GRID. .g-grid had no display rule anywhere on this template,
      so every card grid on the nine range pages and the three category hubs
      rendered as one 1200px-wide column and cascaded down the page. The same
      block was added to seven top-level pages inline on 16 Sep; it belongs in
      the template so every page-product page gets it from one place.
      Three columns, not the four the /products/ inline copy uses: these cards
      carry a heading, a paragraph and a CTA, and at four across the card drops
      to 282px and grows to 406px tall. Three across is 384px and 278px, and a
      six-card section falls as two clean rows instead of four-plus-two. ── */

.g-grid { display: grid; gap: 24px; }
.g-grid--cards { grid-template-columns: repeat(3, 1fr); }
@media (max-width: 1024px) { .g-grid--cards { grid-template-columns: repeat(2, 1fr); gap: 20px; } }
@media (max-width: 600px)  { .g-grid--cards { grid-template-columns: 1fr; } }

/* Card image frame, same treatment as the hub pages. A photograph fills it, a
   product cut-out sits inside it on linen. */
.g-card__img { height: 200px; overflow: hidden; background: var(--wp--preset--color--dark-teal); display: flex; align-items: center; justify-content: center; }
.g-card__img img { display: block; width: 100%; height: 100%; max-width: 100%; object-fit: cover; }
.g-card__img--product { background: var(--wp--preset--color--linen); }
.g-card__img--product img { width: auto; height: auto; max-width: 82%; max-height: 86%; object-fit: contain; }

/* ── 6. .g-fig, the in-band figure. The 16x9 modifier had no rule, so a
      non-16x9 source drew at its own ratio and pushed the band out. ── */
.g-fig { margin-block: 28px; }
.g-fig img { display: block; width: 100%; height: auto; }
.g-fig--16x9 img { aspect-ratio: 16 / 9; object-fit: cover; }
.g-fig figcaption { margin-top: 10px; font-size: 14px; line-height: 1.5; opacity: .8; }

/* The in-situ photograph at the foot of the applications band ran the full
   1200px grid and drew 675px tall, taller than the six cards above it, so it
   read as a second hero dropped in at random. The other figure on the same
   page sits in a constrained band at 780px. Cap both at 780 and the page has
   one figure size instead of two. No crop: the seven in-situ photographs put
   the sensor at different heights in the frame, so a fixed object-position
   clips the mast on some and the ground on others. */
.g-band .g-fig { max-width: 780px; }

/* The range group shots were dark-studio composites. Shell, 16 Sep: "any of
   this style image needs to be removed we dont like the black background."
   Every range already has a transparent cut-out of the same group, shot at
   1600 x 551, so the figure takes the cut-out treatment the mega menu and the
   product cards already use: linen panel, contained, never cropped. */
/* The panel is on the IMAGE, not the figure, so the caption sits below it on
   the band rather than floating inside a tinted box, and the padding does not
   add to the 780px cap. */
.g-fig--cut { background: none; padding: 0; }
.g-fig--cut img {
  box-sizing: border-box;
  aspect-ratio: auto;
  width: 100%;
  height: auto;
  padding: 26px 32px;
  background: var(--wp--preset--color--linen);
  object-fit: contain;
}
/* On a linen band the panel would disappear into it, and on the dark grounds
   linen is the wrong weight. Both take the base ground instead. */
.g-band.has-linen-background-color .g-fig--cut img,
.g-ground-dark .g-fig--cut img,
.g-band.has-dark-teal-background-color .g-fig--cut img,
.g-band.has-deep-sage-background-color .g-fig--cut img { background: var(--wp--preset--color--base); }



/* ── 7. ACCESSIBILITY FLOORS ON .g-var. The module shipped at 11px on three
      labels and gave the model link and the two secondary links a 21 to 22px
      hit area. The estate floor is 12px type and a 30px target, so the labels
      go to 12px and the links get real padding without changing how they read. ── */

.g-var__head, .g-var__k, .g-var__state { font-size: 12px; }
.g-var__model a { display: inline-flex; align-items: center; min-height: 30px; }
.g-var__more, .g-var__doc {
  display: inline-flex;
  align-items: center;
  min-height: 30px;
  font-size: 13px;
}


/* ── 8. THE SPLIT BAND. Shell, 16 Sep: "the products are not as important as
      what we are saying - they need to sit next to something." The range shot
      was a standalone block owning a whole row. It now sits beside the band's
      own eyebrow, heading and lead, which is the estate width rule: a band with
      an image splits half and half, copy one side, image the other, vertically
      centred. Core columns do the layout and stack on their own at 781px, so
      there is no media query here. The chooser list or card grid that follows
      still runs the full band. ── */

.g-split { align-items: center; }
.g-split .g-eyebrow { margin-top: 0; }
.g-split h2 { margin-top: 0; }
.g-split p:last-child { margin-bottom: 0; }

/* In a column the figure fills its half, and the cap that tames the standalone
   figure does not apply. The panel is given a height band so a wide group
   (WindObserver, 2.76:1) and a tall one (WindUltra, 0.94:1) both land at a
   comparable size instead of one drawing 159px and the other 546px. */
.g-split .g-fig { max-width: none; margin-block: 0; }
.g-split .g-fig--cut img {
  min-height: 260px;
  max-height: 340px;
  height: auto;
  object-fit: contain;
}
@media (max-width: 781px) {
  .g-split .g-fig { margin-top: 24px; }
  .g-split .g-fig--cut img { min-height: 200px; max-height: 280px; }
}


/* ── 9. THE PHOTO BAND. Shell, 18 Sep: "this section is all the same colour
      ... this is just floating ... can we not use these images like this as
      like background in some of the sections?" The in-situ photograph was a
      standalone block sitting between the cards and the CTA. It is now the
      band's own background, under the band's own ground colour at 90%, so the
      section reads as a photograph rather than a flat field and nothing floats.
      Same construction as the homepage hero media layer. ── */

.g-band--photo { position: relative; overflow: hidden; isolation: isolate; }
.g-band--photo > * { position: relative; z-index: 1; }
/* The constrained layout rule loads after this and carries margin:auto plus a
   max-width, so the media layer has to out-specify both to reach the edges. */
.g-band--photo > .g-bandmedia {
  position: absolute;
  inset: 0;
  z-index: 0;
  max-width: none !important;
  width: auto;
  margin: 0 !important;
  padding: 0;
  overflow: hidden;
}
.g-bandmedia img { display: block; width: 100%; height: 100%; object-fit: cover; object-position: center; }
.g-bandmedia::after { content: ""; position: absolute; inset: 0; }

/* The tint is the band's own ground, so a sage band stays sage and a navy band
   stays navy. It is a vertical gradient, not a flat wash: dense across the top
   third where the eyebrow, heading and lead sit as white type on the band, then
   opening up below where the only things over it are opaque white cards and a
   solid button. A flat 0.90 was safe but the photograph barely read, which is
   the "all the same colour" complaint it was meant to answer. */
.g-band--photo > .g-bandmedia::after {
  background: linear-gradient(180deg,
    var(--g-tint-94) 0%, var(--g-tint-90) 30%, var(--g-tint-74) 66%, var(--g-tint-68) 100%);
}
.g-band--photo.has-deep-sage-background-color > .g-bandmedia::after {
  --g-tint-94: rgba(67, 105, 91, 0.94);  --g-tint-90: rgba(67, 105, 91, 0.90);
  --g-tint-74: rgba(67, 105, 91, 0.74);  --g-tint-68: rgba(67, 105, 91, 0.68);
}
.g-band--photo.has-dark-blue-background-color > .g-bandmedia::after {
  --g-tint-94: rgba(14, 31, 59, 0.94);   --g-tint-90: rgba(14, 31, 59, 0.90);
  --g-tint-74: rgba(14, 31, 59, 0.76);   --g-tint-68: rgba(14, 31, 59, 0.70);
}
.g-band--photo.has-dark-teal-background-color > .g-bandmedia::after {
  --g-tint-94: rgba(0, 61, 76, 0.94);    --g-tint-90: rgba(0, 61, 76, 0.90);
  --g-tint-74: rgba(0, 61, 76, 0.74);    --g-tint-68: rgba(0, 61, 76, 0.68);
}

/* A photograph behind a phone-width band is mostly cropped away and costs a
   download for texture nobody sees, so it steps back to the flat ground. */
@media (max-width: 600px) {
  .g-band--photo > .g-bandmedia { display: none; }
}

/* ══ END PRODUCT MODULES THAT HAD NO CSS ═══════════════════════════════════ */


