/* ==========================================================================
   Codingkart — Contact Us
   Figma: Contact Us (161594:9554)

   A lead-capture page, not a marketing page: the frame is Hero → Footer and
   nothing else. Every other section on the canvas is hidden — About Us
   alternates, CaseStudies, CaseStudies v1, Services, FAQ, the Maxuse Desktop
   footer, and the coffee-vertical checklist left in the hero. The FinalCTA
   (161594:11308) is hidden too and its copy is Shopify Plus specific, so it
   is not built; the Footer instance sits directly under the hero at y=1094.

   The form itself is the shared .form component in global.css §9 — it was
   put there rather than here because the input treatment is reusable, not
   specific to this layout. What is genuinely local is below: this hero is
   centred with no aside, and it carries a second ring stack that no other
   page has.
   ========================================================================== */

.contact-hero {
  position: relative;
  padding: 90px var(--section-120) 110px;
  background-color: var(--color-bg);
  overflow: hidden;
}

.contact-hero__inner {
  position: relative;
  z-index: 1;
  display: flex;
  width: 100%;
  max-width: 962px;
  margin-inline: auto;
  flex-direction: column;
  align-items: center;
  gap: var(--section-40);
}

.contact-hero__heading {
  width: 100%;
  color: var(--color-text-primary);
  font-size: var(--font-size-64);
  font-weight: var(--font-weight-semibold);
  line-height: 70.4px;
  text-align: center;
  text-transform: capitalize;
}

/* --------------------------------------------------------------------------
   Decorative ring stacks

   Two of them here, where every other hero has one. The right-hand stack is
   the shared .cs-hero__rings component at this design's anchor point; the
   left-hand stack is the same four rings at 55.14% scale, rotated 117.03°
   and centred just off the left edge. Reusing the ring exports keeps both
   stacks on the one glyph set.
   -------------------------------------------------------------------------- */

/* Two adjustments to the shared stack. Figma measures its offsets from the
   frame top, where the nav is an overlay — our .site-header is in flow, so
   the hero box starts 113px lower and both stacks take the design's value
   minus that. And the component's 150px blur is tuned for the case-study
   heroes, where it sits almost entirely off-canvas; here both stacks read
   well inside the frame, and at 150px the concentric banding the design is
   built on washes out entirely. */
.contact-hero .cs-hero__rings {
  top: 431px;
  right: -664px;
  filter: blur(60px);
}

/* The container is a zero-size anchor at the stack's shared centre; each ring
   is then centred on it, so all four stay concentric at any size. */
.contact-hero__rings-left {
  position: absolute;
  top: 366px;
  left: -81px;
  width: 0;
  height: 0;
  /* Same 60px, scaled with the rings (60 × 0.5514). */
  filter: blur(33px);
  pointer-events: none;
}

.contact-hero__rings-left img {
  position: absolute;
  top: 0;
  left: 0;
  max-width: none;
  transform: translate(-50%, -50%) rotate(117.03deg);
}

.contact-hero__rings-left img:nth-child(1) {
  width: 546.947px;
  height: 546.947px;
}

.contact-hero__rings-left img:nth-child(2) {
  width: 448.805px;
  height: 448.805px;
}

.contact-hero__rings-left img:nth-child(3) {
  width: 391.464px;
  height: 391.464px;
}

/* The innermost ring is nudged off the shared centre in the design. */
.contact-hero__rings-left img:nth-child(4) {
  width: 283.398px;
  height: 283.398px;
  transform: translate(-50%, -50%) translate(8.45px, 9.81px) rotate(117.03deg);
}

/* --------------------------------------------------------------------------
   Responsive

   global.css re-declares --section-120 at 1200px (64px) and 768px (24px), and
   already stacks .form__row at 768. Only the hero's own metrics are here.
   -------------------------------------------------------------------------- */

@media (max-width: 1200px) {
  .contact-hero {
    padding-block: var(--section-64) var(--section-80);
  }

  .contact-hero__heading {
    font-size: 48px;
    line-height: 1.1;
  }

  /* Both stacks are decorative and cost a large blur to paint; the shared
     component already drops out here, so the local one follows. */
  .contact-hero__rings-left {
    display: none;
  }
}

@media (max-width: 768px) {
  .contact-hero {
    padding-block: var(--section-40) var(--section-64);
  }

  .contact-hero__heading {
    font-size: var(--font-size-32);
    line-height: 1.15;
  }

  .contact-hero__inner {
    gap: var(--gap-4);
  }
}

/* --------------------------------------------------------------------------
   Honeypot

   Off-screen rather than display:none or hidden — a bot that respects either
   of those would skip the field and defeat the trap. Also removed from the
   tab order and the accessibility tree at the markup level.
   -------------------------------------------------------------------------- */

.form__trap {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}