/* MRM brand overrides for the Georgetown theme on closure pages.
   This file is the theme's own (originally empty) customization hook, loaded
   after styles.css. Keep it small and commented. */

/* Teal graphics -> Morgan navy family. The color lives in the PNGs, not CSS:
   service-icon tiles, the heart outline (shape-01), the plus grid (shape-04).
   The dots (shape-02) and circles (shape-03) are warm-toned and left alone. */
.service-icon img,
.shape-01 img,
.shape-04 img {
    filter: hue-rotate(45deg) saturate(0.75);
}

/* Flatten the cream paper texture (Dan 2026-08-10): the 50%-opacity backdrop
   the theme paints behind the banner's rounded corners. The navbar and the
   requesting-records panel textures are template-level data-background
   attributes, removed in georgetown_template.py in the same change. */
.main-banner:before,
.page-title-bg:before {
    background-image: none;
}


/* --- Salmon accent removed (Dan 2026-09-02) ----------------------------------
   styles.css had the theme accent #f8a683 in 58 places; it is now #1f4b8e. Two
   consequences need fixing here rather than in the vendor sheet. */

/* 1. .butn's hover fill was already #1f4b8e, so with a navy base the hover read
      as no change at all. Darker navy keeps the interaction visible. */
.butn:before {
    background: #15335f;
}

/* 2. .butn.white never had a white background - it only recoloured hover text,
      which is why the hero call-to-action was salmon like everything else. On the
      dark hero overlay a white button with navy text is the correct contrast. */
.butn.white {
    background-color: #ffffff;
    color: #1f4b8e;
}
.butn.white:before {
    background: #1f4b8e;
}
.butn.white:hover,
.butn.white:focus,
.butn.white:active {
    color: #ffffff;
}

/* 3. The last warm elements: the dot grid (shape-02) and circles (shape-03).
      The 2026-08-10 patch deliberately left these "warm-toned" while the accent
      was still salmon, so they matched. With the accent now navy they are the
      only warm thing on the page. Targeted by src rather than container class so
      the rule holds wherever the theme places them.
      NOTE the existing hue-rotate(45deg) above is tuned for TEAL sources; these
      are warm (~17deg hue), so reaching navy (~217deg) needs ~200deg instead. */
img[src*="shape-02"],
img[src*="shape-03"] {
    filter: hue-rotate(200deg) saturate(0.9);
}

/* 4. WOW.js reveal is NOT reliable - force content visible (2026-09-03).
      Measured with real scroll events: 12 of 13 .wow sections sit at
      visibility:hidden on our v2 render, and 8 of 9 on the live original
      georgetownsleepcenter.com - so it is inherited theme behaviour, not ours.
      Either way the page BODY ("Requesting Your Records", "How it works") is
      invisible to a normally-scrolling visitor, and a patient looking for how to
      request their records must never depend on an animation library firing.
      This disables the fade-in rather than trying to repair WOW: content
      availability beats animation on an informational page.
      NOTE an earlier check using window.scrollTo() found 0 hidden and looked
      fine - the theme's smooth-scroll plugin swallows programmatic scrolls, so
      that test never actually scrolled. Measure with real scroll events. */
.wow,
.wow.fadeIn,
.wow.fadeInUp,
.wow.fadeInLeft,
.wow.fadeInRight {
    visibility: visible !important;
    animation-name: none !important;
    opacity: 1 !important;
}