@charset "UTF-8";
/* Cormorant / Nunito faces come from vendored static/css/wp/fonts.css,
   loaded by template/layout.html before this file. No @font-face here. */
/* ============================================================
   smq-landing.scss — soulmatequestmatch.com
   ============================================================ */
/* ── Design tokens ── */
:root {
  --smq-ink: #121212;
  --smq-ink-lt: #202020;
  --smq-gold: #FFC72C;
  --smq-accent: #D50032;
  --smq-white: #FFFFFF;
  --smq-text: #202020;
  --smq-max-width: 1200px;
  --smq-radius-card: 20px;
  --smq-radius-btn: 100px;
}

/* ── Reset / base ── */
*, *::before, *::after {
  box-sizing: border-box;
  margin: 0;
  padding: 0;
}

html {
  scroll-behavior: smooth;
}

/* Every page on this site renders on a black/near-black surface: Elementor
   pages force it via their vendored post-<ID>.css (body.elementor-page-<ID>
   background-color, or the homepage's --e-global-color-primary, itself
   #121212), so this is the real, permanent default for the handful of
   custom (non-Elementor) pages too, not a fallback that's ever meant to
   show. */
body {
  font-family: "Nunito", sans-serif;
  background: var(--smq-ink);
  color: var(--smq-white);
  line-height: 1.6;
  -webkit-font-smoothing: antialiased;
}

/* ── Buttons ──
   Only used on contact/thank-you.html, which sits on the site's permanent
   dark body — gold-on-ink is the established dark-surface high-contrast
   combo (~5.06:1, see CLAUDE.md), not the ink-on-light pairing this used
   before body defaulted to dark. */
.smq-btn-primary {
  background: var(--smq-gold);
  color: var(--smq-ink);
  padding: 0.85rem 2rem;
  border-radius: var(--smq-radius-btn);
  text-decoration: none;
  font-weight: 600;
  font-size: 0.95rem;
  letter-spacing: 0.03em;
  transition: background 0.2s, transform 0.15s;
  display: inline-block;
}

.smq-btn-primary:hover {
  background: white;
  color: var(--smq-ink);
  transform: translateY(-1px);
}

/* ── Honeypot ── */
/* Hidden from humans, visible to scrapers. Required class for every honeypot
   field site-wide (see CLAUDE.md "Forms") — never inline style="display:none;". */
.mailing-list-hp,
.elementor-field-group.mailing-list-hp {
  display: none;
}

/* ── Section commons ── */
section:not(.elementor-section):not(.elementor-inner-section) {
  padding: 5rem 2rem;
}

.smq-section-tag {
  display: inline-block;
  font-size: 0.72rem;
  font-weight: 700;
  letter-spacing: 0.12em;
  text-transform: uppercase;
  color: var(--smq-accent);
  margin-bottom: 0.75rem;
}

.smq-section-tag--light {
  color: var(--smq-gold);
}

/* ── INNER PAGE HERO ── */
.smq-page-hero {
  background: linear-gradient(160deg, var(--smq-ink) 0%, var(--smq-ink-lt) 100%);
  padding: 4rem 2rem;
  text-align: center;
}

.smq-page-hero-inner {
  max-width: var(--smq-max-width);
  margin: 0 auto;
}

.smq-page-hero h1 {
  font-family: "Cormorant", serif;
  font-weight: 600;
  font-size: clamp(2.2rem, 4vw, 3.2rem);
  color: white;
  line-height: 1.2;
  margin-bottom: 0.75rem;
}

.smq-page-hero p {
  font-size: 1.05rem;
  color: rgba(255, 255, 255, 0.7);
  max-width: 560px;
  margin: 0 auto;
  line-height: 1.7;
}

/* ── TERMS / PRIVACY ── */
.smq-legal-content {
  max-width: 760px;
  margin: 0 auto;
  padding: 4rem 2rem;
}

.smq-legal-content h2 {
  font-family: "Cormorant", serif;
  font-weight: 600;
  font-size: 2rem;
  color: white;
  margin: 2rem 0 0.75rem;
}

.smq-legal-content h3 {
  font-family: "Cormorant", serif;
  font-weight: 600;
  font-size: 1.45rem;
  color: white;
  margin: 1.5rem 0 0.5rem;
}

.smq-legal-content p {
  font-size: 0.97rem;
  color: rgba(255, 255, 255, 0.75);
  line-height: 1.8;
  margin-bottom: 1rem;
}

.smq-legal-content ul {
  padding-left: 1.5rem;
  margin-bottom: 1.25rem;
}

.smq-legal-content ul li {
  font-size: 0.97rem;
  color: rgba(255, 255, 255, 0.75);
  line-height: 1.7;
  margin-bottom: 0.5rem;
}

/* ── ERROR 404 PAGE ── */
.smq-error-code {
  font-size: clamp(80px, 16vw, 140px);
  font-weight: 700;
  line-height: 1;
  margin-bottom: 8px;
  color: rgba(255, 255, 255, 0.15);
  font-family: "Cormorant", serif;
}

.smq-quicklinks {
  padding: 4rem 2rem;
  text-align: center;
}

.smq-quicklinks-inner {
  max-width: 480px;
  margin: 0 auto;
}

.smq-quicklinks h2 {
  font-family: "Cormorant", serif;
  font-weight: 600;
  font-size: 1.9rem;
  color: white;
  margin-bottom: 1.5rem;
}

.smq-quicklinks-grid {
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 1rem;
}

.smq-quicklink {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 0.5rem;
  padding: 1rem;
  background: white;
  border-radius: 16px;
  text-decoration: none;
  color: var(--smq-ink);
  box-shadow: 0 2px 12px rgba(0, 0, 0, 0.06);
  font-weight: 500;
  transition: box-shadow 0.2s, transform 0.2s;
}

.smq-quicklink:hover {
  transform: translateY(-2px);
  box-shadow: 0 4px 24px rgba(0, 0, 0, 0.1);
}

.smq-quicklink svg {
  flex-shrink: 0;
}

/* ── Responsive ── */
@media (max-width: 640px) {
  .smq-quicklinks-grid {
    grid-template-columns: 1fr;
  }
}
/* ── BIO PAGE LAYOUT ── */
.smq-bio-layout {
  padding: 4rem 2rem;
}

.smq-bio-layout .smq-inner {
  max-width: var(--smq-max-width);
  margin: 0 auto;
}

.smq-bio-grid {
  display: grid;
  grid-template-columns: 1fr 2fr;
  gap: 3rem;
  align-items: start;
}

.smq-bio-sidebar {
  position: sticky;
  top: 90px;
}

.smq-bio-sidebar img {
  width: 100%;
  height: auto;
  border-radius: var(--smq-radius-card);
  display: block;
  aspect-ratio: 1/1;
  object-fit: cover;
}

.smq-bio-back {
  display: inline-flex;
  align-items: center;
  gap: 0.35rem;
  font-size: 0.85rem;
  font-weight: 600;
  color: var(--smq-gold);
  text-decoration: none;
  margin-top: 1rem;
  transition: gap 0.2s;
}

.smq-bio-back:hover {
  gap: 0.6rem;
}

.smq-bio-content h1 {
  font-family: "Cormorant", serif;
  font-weight: 600;
  font-size: clamp(1.8rem, 3vw, 2.4rem);
  color: white;
  margin-bottom: 0.35rem;
  line-height: 1.2;
}

.smq-bio-role {
  font-size: 0.82rem;
  font-weight: 700;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--smq-gold);
  margin-bottom: 1.5rem;
}

.smq-bio-divider {
  width: 60px;
  height: 3px;
  background: linear-gradient(90deg, var(--smq-accent), var(--smq-gold));
  border-radius: 2px;
  margin-bottom: 1.75rem;
}

.smq-bio-content p {
  font-size: 1.02rem;
  color: rgba(255, 255, 255, 0.75);
  line-height: 1.8;
  margin-bottom: 1.25rem;
  max-width: 680px;
}

@media (max-width: 900px) {
  .smq-bio-grid {
    grid-template-columns: 1fr;
  }
  .smq-bio-sidebar {
    position: static;
  }
  .smq-bio-sidebar img {
    max-width: 280px;
    margin: 0 auto;
  }
}
/* -- WORDPRESS / ELEMENTOR MIGRATION OVERRIDES -----------------------------
   Elementor's posts + archive-posts widgets size thumbnails with a
   padding-bottom ratio box (post-565.css / post-556.css:
   `.elementor-posts-container .elementor-post__thumbnail{padding-bottom:calc(1 * 100%)}`,
   0.5 under @media max-width:767px) and then crop the <img> into it at
   runtime via Elementor Pro's archive-posts/posts webpack chunk, which adds
   .elementor-has-item-ratio to the container and .elementor-fit-height to the
   thumbnail. That chunk is not part of this static clone, so the <img> stays
   in normal flow at the top of the box and the ratio spacer shows through
   below it (visible on /blog/ as a gray band, because the card's white
   background is under Elementor's .elementor-posts__hover-gradient overlay;
   invisible but equally broken in the white related-posts sidebar on posts).
   object-fit: cover is equivalent to both branches of the JS: landscape source
   in a 1:1 box == fit-height (crop sides), portrait source == no fit-height
   (crop top/bottom). Keep the ratio padding so the per-breakpoint ratios keep
   coming from the vendored Elementor CSS. */
.elementor-posts.elementor-posts-container .elementor-post__thumbnail {
  position: relative;
  overflow: hidden;
}

.elementor-posts.elementor-posts-container .elementor-post__thumbnail img {
  position: absolute;
  top: 0;
  left: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: center;
}

/* Blog archive hero (Elementor archive template 565, section 66f8a34).
   post-565.css ships `padding:573px 0px 0px 0px` on top of an 870px min-height
   container -> a 1443px contentless image band on desktop, 973px on tablet
   (the mobile padding reset only kicks in at <=767px). Verified against the WP
   backup (wplb_postmeta row 4526) as faithful to the original, but the padding
   is an authoring artifact: the section holds an empty column, and every other
   hero on the site is min-height only with zero padding (post-328 our-team
   600/400/200, post-3468 services 820, post-684 coaching 820). Normalised to
   our-team, whose hero is structurally identical (full_width +
   height-min-height + items-middle + empty column + background image). */
body.elementor-page-565 .elementor-565 .elementor-element.elementor-element-66f8a34 {
  padding-top: 0;
}

body.elementor-page-565 .elementor-565 .elementor-element.elementor-element-66f8a34 > .elementor-container {
  min-height: 600px;
}

@media (max-width: 1024px) {
  body.elementor-page-565 .elementor-565 .elementor-element.elementor-element-66f8a34 > .elementor-container {
    min-height: 400px;
  }
}
@media (max-width: 767px) {
  body.elementor-page-565 .elementor-565 .elementor-element.elementor-element-66f8a34 > .elementor-container {
    min-height: 200px;
  }
}
/* Blog/category archive title (element ef2a59d, shared by /blog/ and every
   category page via this one template). post-565.css hardcodes this widget's
   text to color:#000000 - not merely undifferentiated like the h1/h2 pairs
   above, but genuinely invisible: body is permanently dark site-wide (see the
   base `body` rule up top), and nothing else in the cascade lightens this
   specific widget, so it renders as black text on a black/near-black page.
   --smq-gold, matching every other page-title treatment on the site. */
body.elementor-page-565 .elementor-565 .elementor-element.elementor-element-ef2a59d .elementor-heading-title {
  color: var(--smq-gold);
}

/* Matchmaking-for-women hero (Elementor page template 948, section 29baf40).
   This is the one hero on the site built with `elementor-section-height-full`
   instead of the `elementor-section-height-min-height` every sibling hero uses
   (our-team 3bb0e22, blog archive 66f8a34, services b450525, coaching 3b829dd) -
   frontend.min.css's rule for that class is a flat `height:100vh` on the section
   itself, so with the empty column here (the actual h1 lives in the section
   below, not this one) it renders as the full browser viewport filled with
   nothing but the background photo. post-948.css also pads that same empty
   column 452px/200px/100px, the same authoring leftover already normalised on
   the blog archive hero above. Neutralise both and match our-team's
   600/400/200 min-height convention, since the structure (full_width + empty
   column + background image) is identical. */
body.elementor-page-948 .elementor-948 .elementor-element.elementor-element-29baf40 {
  height: auto;
  padding-top: 0;
}

body.elementor-page-948 .elementor-948 .elementor-element.elementor-element-29baf40 > .elementor-container {
  min-height: 600px;
}

@media (max-width: 1024px) {
  body.elementor-page-948 .elementor-948 .elementor-element.elementor-element-29baf40 > .elementor-container {
    min-height: 400px;
  }
}
@media (max-width: 767px) {
  body.elementor-page-948 .elementor-948 .elementor-element.elementor-element-29baf40 > .elementor-container {
    min-height: 200px;
  }
}
/* Coaching-page hero (Elementor page template 684, section 3b829dd).
   post-684.css carries a "Start custom CSS for section" block - an editor-only
   experiment left in the WP custom CSS field, not part of the base export -
   that force-sets `min-height:130vh !important` on the section itself for any
   viewport >=780px, on top of (not replacing) the base rule's own structural
   min-height on `.elementor-container` (820px desktop / 500px <=1024px /
   245px <=767px, the same fixed-height pattern every other hero on the site
   uses: post-3468 services 820, post-328 our-team 600/400/200). 130% of
   viewport height is far taller than any sibling hero, and the block's own
   comment ("Full height only on HD screens") doesn't match its 780px
   breakpoint, which covers tablets too - confirming this is a leftover bug,
   not a deliberate full-height design. Zeroing the section's own min-height
   lets it fall back to sizing itself from the container's real min-height,
   same as every other hero. One breakpoint covers both vendor media queries
   since >=1366px is already inside >=780px. */
@media (min-width: 780px) {
  .elementor-element-3b829dd {
    min-height: 0 !important;
  }
}
/* Single-post hero (Elementor single-post template 556).
   post-556.css pulls the title widget up under a decorative "Blogs" watermark
   heading (element 2e2ec12, Cormorant 8.5em): `.elementor-element-77a9ae9
   {margin:-82px 0 …}` desktop, -68px @<=1024, -44px @<=767. That watermark has been
   removed from template/blog-posts/_post.html, so there is nothing left to pull
   under and the negative margin would drag the title into the section padding.
   Zero it at all three breakpoints. */
body.elementor-page-556 .elementor-556 .elementor-element.elementor-element-77a9ae9 {
  margin-top: 0;
}

@media (max-width: 1024px) {
  body.elementor-page-556 .elementor-556 .elementor-element.elementor-element-77a9ae9 {
    margin-top: 0;
  }
}
@media (max-width: 767px) {
  body.elementor-page-556 .elementor-556 .elementor-element.elementor-element-77a9ae9 {
    margin-top: 0;
  }
}
/* The post title was promoted h2 -> h1 for a correct document outline. Elementor's
   kit (post-8.css) sizes h1 from --e-global-typography-primary-font-size
   (4em / 2.8em <=1024 / 2.4em <=767) and h2 from --e-global-typography-secondary-*
   (3em / 2.3em / 1.9em), so the tag change alone would enlarge the title by a third.
   Pin it back to the secondary scale; the vars are themselves redefined per
   breakpoint, so one rule covers all three. Colour is identical for h1 and h2
   (--e-global-color-8becef4), so it is not restated. */
body.elementor-page-556 .elementor-556 .elementor-element.elementor-element-77a9ae9 .elementor-heading-title {
  font-family: var(--e-global-typography-secondary-font-family), Sans-serif;
  font-size: var(--e-global-typography-secondary-font-size);
  font-weight: var(--e-global-typography-secondary-font-weight);
}

/* The opposite problem, on eight other pages: each page's real h1 was manually
   given a custom Elementor font size (or, on the homepage, pinned to the h2/
   secondary scale, or on contact.html, a third bespoke global-typography
   preset - --e-global-typography-4d0af27-font-size, 1.3em/1.2em) in the WP
   editor, and that per-widget size renders smaller than the h2 tagline sitting
   right below it - the h1 and h2 read as visually identical or backwards.
   Bump each of these h1s up to the same primary scale documented above so the
   h1 is reliably the more prominent heading at every breakpoint; one rule per
   widget is enough since the var is redefined per breakpoint already. */
body.elementor-page-474 .elementor-474 .elementor-element.elementor-element-97abe29 .elementor-heading-title,
body.elementor-page-1398 .elementor-1398 .elementor-element.elementor-element-bbeeb31 .elementor-heading-title,
body.elementor-page-3427 .elementor-3427 .elementor-element.elementor-element-149d52e .elementor-heading-title,
body.elementor-page-328 .elementor-328 .elementor-element.elementor-element-2137e20 .elementor-heading-title,
body.elementor-page-3468 .elementor-3468 .elementor-element.elementor-element-d6d18f5 .elementor-heading-title,
body.elementor-page-684 .elementor-684 .elementor-element.elementor-element-fe8fc15 .elementor-heading-title,
body.elementor-page-86 .elementor-86 .elementor-element.elementor-element-85a6bdd .elementor-heading-title,
body.elementor-page-269 .elementor-269 .elementor-element.elementor-element-33b4f5e .elementor-heading-title {
  font-size: var(--e-global-typography-primary-font-size);
}

/* All thirteen of these h1 widgets (the eight above plus four whose h1 already
   sized correctly once retagged, plus matchmaking-for-women.html's h1, which
   was already correctly the larger of its pair) carry a hardcoded
   color:#FFFFFF from the WP export, same as the h2/h3 text sharing their hero -
   on a page with both an h1 and an h2 hero line, the two read as one
   undifferentiated block of white text. Every one of these heroes sits on a
   solid black or near-black section (confirmed per-page against each
   post-<ID>.css body/section background), so --smq-gold (the site's
   dark-surface accent token, ~5.06:1 against --smq-ink) is safe to use here:
   give the h1 the accent color so it reads as the page's title at a glance,
   and leave the h2 tagline white. */
body.elementor-page-474 .elementor-474 .elementor-element.elementor-element-97abe29 .elementor-heading-title,
body.elementor-page-1398 .elementor-1398 .elementor-element.elementor-element-bbeeb31 .elementor-heading-title,
body.elementor-page-3427 .elementor-3427 .elementor-element.elementor-element-149d52e .elementor-heading-title,
body.elementor-page-328 .elementor-328 .elementor-element.elementor-element-2137e20 .elementor-heading-title,
body.elementor-page-3468 .elementor-3468 .elementor-element.elementor-element-d6d18f5 .elementor-heading-title,
body.elementor-page-684 .elementor-684 .elementor-element.elementor-element-fe8fc15 .elementor-heading-title,
body.elementor-page-889 .elementor-889 .elementor-element.elementor-element-7e030f7 .elementor-heading-title,
body.elementor-page-3274 .elementor-3274 .elementor-element.elementor-element-7163bde .elementor-heading-title,
body.elementor-page-764 .elementor-764 .elementor-element.elementor-element-7163bde .elementor-heading-title,
body.elementor-page-3221 .elementor-3221 .elementor-element.elementor-element-7163bde .elementor-heading-title,
body.elementor-page-86 .elementor-86 .elementor-element.elementor-element-85a6bdd .elementor-heading-title,
body.elementor-page-269 .elementor-269 .elementor-element.elementor-element-33b4f5e .elementor-heading-title,
body.elementor-page-948 .elementor-948 .elementor-element.elementor-element-78fcfd2 .elementor-heading-title {
  color: var(--smq-gold);
}

/* frontend.min.css zeroes both margin and padding on .elementor-heading-title,
   so the only space between stacked widgets is each widget's own margin-bottom
   (--kit-widget-spacing, 20px on this site per post-8.css) - the same gap
   whether a heading is followed by a paragraph or a paragraph is followed by a
   heading. A heading that starts a new subsection needs more room above it
   than a paragraph needs above it, or the two read as one continuous block.
   Padding, not margin, so there is no sibling-margin-collapsing risk between
   this and the preceding widget's own bottom margin - the two add together. */
.elementor-widget-text-editor + .elementor-widget-heading .elementor-heading-title {
  padding-top: 1.5rem;
}

/* Category chips in the post-info row inherit the widget's white text from
   post-556.css; just make them read as links. */
.elementor-post-info__terms-list-item {
  color: inherit;
  text-decoration: none;
  border-bottom: 1px solid currentColor;
}

.elementor-post-info__terms-list-item:hover {
  border-bottom-color: transparent;
}

/* Archive-card date bar. The cards-skin footer (border-top + 15px/30px padding)
   already comes from widget-posts.min.css; only the colour needs help.
   widget-posts.min.css ships #adadad, which is ~2.1:1 on the card's vendored
   #fff background - lighter than the card excerpt's own #777. Scoped to
   .elementor-post__card so it cannot reach the related-posts sidebar, which is
   classic skin (no card wrapper) and is deliberately white via post-556.css.
   --smq-ink is safe here without a dark-mode override, unlike --smq-text:
   the card background is a fixed #fff from the vendored CSS in both colour
   schemes, and --smq-ink is not remapped in the dark-mode block. */
.elementor-posts .elementor-post__card .elementor-post__meta-data {
  color: var(--smq-ink);
  opacity: 0.65;
}

/* Elementor Pro's post-info widget CSS (widget-post-info.min.css) was never part
   of this static export - grep the whole of static/css/wp/ for "post-info" or
   "terms-list" and you get nothing, and the WordPress backup holds only an XML
   export + SQL dump, no CSS. Without it, this rule from widget-icon-list.min.css
   reaches too far:
       .elementor-widget .elementor-icon-list-item a { display: flex; }
   It is meant for the icon-list row's own anchor, but as a descendant selector it
   also hits the category links nested inside .elementor-post-info__terms-list.
   Blockified anchors inside an inline context each take their own line, stranding
   the ", " separators on lines of their own, and each anchor stretches to the full
   width of its containing block - which is why the currentColor border-bottom
   above renders as a fixed-width rule rather than hugging the word.
   Put them back in the inline flow; the <ul> is already display:flex + flex-wrap
   from the same vendored file, so the date and the category row sit side by side. */
.elementor-widget-post-info .elementor-icon-list-item .elementor-post-info__terms-list a {
  display: inline;
}

/* Mobile nav dropdown. widget-nav-menu.min.css hardcodes this panel to a stark
   white background at 13px text - a flat, unbranded look next to the header's
   solid-black bar it drops from, and small enough to be hard to read on a
   phone. Make the panel a continuation of the header instead of a flip to
   white: --smq-ink background (not remapped in dark mode, so it stays black
   in both OS schemes, matching the always-black header bar), literal white
   text (var(--smq-white) is dark-mode-remapped to a near-black surface tone
   and would vanish here - see the dark-mode block below), and --smq-gold for
   hover/current, which is exactly the dark-surface use case that token is
   meant for. This also fixes the pre-existing contrast bug where post-8.css's
   kit-wide .elementor-kit-8 a { color: var(--e-global-color-fddf1c1) } (gold)
   ties the widget's own .elementor-nav-menu--dropdown a on specificity (both
   are one class + one tag) and previously won on source order, rendering
   gold-on-white; this file loads last, so the rule below wins the tie instead. */
.elementor-nav-menu--dropdown {
  background-color: var(--smq-ink);
  /* Mirrors the header bar's own 6px solid gold bottom border (post-55.css,
     .elementor-element-cd1c277) so the open panel reads as a continuation of
     the header rather than content bleeding straight into the page below. */
  border-bottom: 6px solid var(--smq-gold);
}

.elementor-nav-menu--dropdown a {
  color: white;
  font-size: 1.05rem;
}

.elementor-nav-menu--dropdown .elementor-item.elementor-item-active,
.elementor-nav-menu--dropdown .elementor-item.highlighted,
.elementor-nav-menu--dropdown .elementor-item:focus,
.elementor-nav-menu--dropdown .elementor-item:hover,
.elementor-nav-menu--dropdown a.current {
  color: var(--smq-gold);
}

/* FAQ toggle bars (Elementor page template 1398, widget 3e7c6209). post-1398.css
   sets the closed-question bar to a fully-saturated #D60032 - fine as a small
   accent, harsh as a full-width background block with white text. Desaturate
   and lighten slightly; still reads as red, no longer neon. */
body.elementor-page-1398 .elementor-1398 .elementor-element.elementor-element-3e7c6209 .elementor-tab-title {
  background-color: #B5445A;
}

/* ── Dark mode ──
   body is already permanently dark, so no OS-preference remap is needed
   for it. --smq-white/--smq-text still get remapped here for the light
   *surface* components (e.g. .smq-quicklink's white card) so they don't
   render a jarring pure-white/near-black card against an OS dark scheme. */
@media (prefers-color-scheme: dark) {
  :root {
    --smq-white: #1C1C1C;
    --smq-text: #F9F7F1;
  }
}

/*# sourceMappingURL=smq-landing.css.map */