:root {
  --navy: #133457;
  --navy-dark: #0c2440;
  --text: #1c2b3a;
  --muted: #5b6b7a;
  --bg: #ffffff;
  --bg-alt: #f4f6f8;
  --border: #e2e8ed;
}

* { box-sizing: border-box; }

html, body {
  margin: 0;
  padding: 0;
  font-family: "Segoe UI", system-ui, -apple-system, Roboto, Helvetica, Arial, sans-serif;
  color: var(--text);
  background: var(--bg);
  line-height: 1.5;
}

.wrap {
  max-width: 1080px;
  margin-inline: auto;
  padding-inline: 24px;
}

.wrap.narrow {
  max-width: 640px;
  text-align: center;
}

a {
  color: var(--navy);
  text-decoration: none;
}
/* Nav links, buttons, and the contact email are already visually
   distinguished by position/shape, not just color — but an inline link
   INSIDE a paragraph of prose (the Client Portal section's "reach out
   directly") isn't. Caught live via a Lighthouse audit, 2026-09-25:
   `link-in-text-block` failed — 2.31:1 contrast against the surrounding
   muted text, well under the 3:1 WCAG 1.4.1 minimum, with no non-color
   indicator either. Underline is that indicator; scoped to `p a` only
   so it doesn't also apply to the nav/footer/button links that don't
   need it. */
p a {
  text-decoration: underline;
}

/* Header */
.site-header {
  border-bottom: 1px solid var(--border);
  position: sticky;
  top: 0;
  background: rgba(255, 255, 255, 0.95);
  backdrop-filter: blur(6px);
  z-index: 10;
}
.site-header .wrap {
  display: flex;
  align-items: center;
  justify-content: space-between;
  height: 64px;
}
.brand {
  display: flex;
  align-items: center;
  gap: 10px;
  font-weight: 700;
  font-size: 17px;
  color: var(--navy);
}
.brand-mark {
  width: 28px;
  height: 28px;
}
.site-nav {
  display: flex;
  align-items: center;
  gap: 24px;
  font-size: 14px;
  font-weight: 600;
}
.site-nav a {
  color: var(--muted);
}
.site-nav a:hover {
  color: var(--navy);
}
/* Set apart from the plain scroll-to-section links above — this one
   navigates to a whole separate app (the CMS/admin portal), not a spot
   on this page. `.site-nav a.nav-login`, not bare `.nav-login` — needs to
   out-specify `.site-nav a` above (one class + one element) to actually
   win on `color`, not just happen to come later in the file. */
.site-nav a.nav-login {
  padding: 6px 14px;
  border-radius: 999px;
  border: 1px solid var(--navy);
  color: var(--navy);
}
.site-nav a.nav-login:hover {
  background: var(--navy);
  color: #fff;
}

/* Hero */
.hero {
  padding: 96px 0 80px;
  text-align: center;
  background: linear-gradient(180deg, var(--bg-alt), var(--bg));
}
.hero h1 {
  font-size: clamp(32px, 5vw, 52px);
  line-height: 1.15;
  letter-spacing: -0.5px;
  margin: 0 0 20px;
  color: var(--navy-dark);
}
.lede {
  max-width: 560px;
  margin: 0 auto 32px;
  color: var(--muted);
  font-size: 18px;
}
.price-tag {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 4px;
  margin-bottom: 32px;
}
.price {
  font-size: 40px;
  font-weight: 800;
  color: var(--navy);
}
.price-period {
  font-size: 18px;
  font-weight: 600;
  color: var(--muted);
}
.price-note {
  font-size: 13px;
  color: var(--muted);
}

.btn-primary {
  display: inline-block;
  background: var(--navy);
  color: #fff;
  padding: 14px 28px;
  border-radius: 8px;
  font-weight: 700;
  box-shadow: 0 6px 16px rgba(19, 52, 87, 0.25);
}
.btn-primary:hover {
  background: var(--navy-dark);
}

/* Bands */
.band {
  padding: 72px 0;
}
.band h2 {
  font-size: 28px;
  text-align: center;
  margin: 0 0 40px;
  color: var(--navy-dark);
}
.band-alt {
  background: var(--bg-alt);
}
/* Must come AFTER the general `.band h2` rule above — same selector
   specificity (one class + one element each), so source order is what
   decides which wins on an h2 inside a `.band.band-dark` element. Caught
   live: without this ordering, "Let's talk about your website" rendered
   in the general dark navy-on-navy instead of white, nearly invisible. */
.band-dark {
  background: var(--navy);
  color: #fff;
  text-align: center;
}
.band-dark h2 {
  color: #fff;
}
.band-dark p {
  color: #cdd8e3;
}
.band-dark .btn-primary {
  background: #fff;
  color: var(--navy);
}
.band-dark .btn-primary:hover {
  background: #e8edf2;
}

.contact-form {
  display: grid;
  gap: 14px;
  text-align: left;
  margin-top: 8px;
}
.contact-form label {
  display: grid;
  gap: 6px;
  font-size: 13px;
  font-weight: 600;
  color: #cdd8e3;
}
.contact-form input,
.contact-form textarea {
  font: inherit;
  font-size: 15px;
  padding: 10px 12px;
  border-radius: 8px;
  border: 1px solid rgba(255, 255, 255, 0.25);
  background: #fff;
  color: var(--text);
}
.contact-form textarea {
  resize: vertical;
  min-height: 90px;
}
.contact-form button {
  justify-self: start;
  border: none;
  cursor: pointer;
}
.contact-form button:disabled {
  opacity: 0.6;
  cursor: default;
}
.contact-status {
  margin: 4px 0 0;
  font-size: 13.5px;
  min-height: 1.2em;
}

.grid {
  display: grid;
  /* 280px, not the original 220px — caught live: at 220px, 6 cards in
     "What's included" fit 4-per-row inside .wrap's 1080px, leaving 2
     orphaned alone on a second row. 280px settles both this 6-card grid
     AND "Why local businesses choose us"'s existing 3-card grid to a
     clean 3-per-row within the same .wrap width, so one column width
     works for both sections. */
  grid-template-columns: repeat(auto-fit, minmax(280px, 1fr));
  gap: 24px;
}
.card h3 {
  font-size: 17px;
  margin: 0 0 8px;
  color: var(--navy-dark);
}
.card p {
  margin: 0;
  color: var(--muted);
  font-size: 15px;
}

#client-sign-in p {
  color: var(--muted);
}

/* Footer */
.site-footer {
  padding: 28px 0;
  border-top: 1px solid var(--border);
  font-size: 13px;
  color: var(--muted);
  text-align: center;
}

@media (max-width: 640px) {
  .site-nav {
    gap: 14px;
    font-size: 13px;
  }
}