@charset "UTF-8";
/*
* 9o9 Brand Technologies -- Home Page CSS (consolidated, responsive)
* Replaces hpstyle.css + mstyle.css (separate desktop/mobile stylesheets
* with duplicated markup) with one stylesheet driving one real responsive
* markup. See PROJECT-NOTES.md for the full history of this rebuild.
* Version: 2.0
*/

/* ========================================================
   SELF-HOSTED FONTS -- Urbanist (variable font, weights 100-900)
   ========================================================
   Previously loaded via a Google Fonts <link> in every page's <head>
   (index.php, web/header.php, error/header.php, error/index.php).
   For launch, self-hosting it here avoids an extra DNS/TLS round-trip
   to fonts.googleapis.com/fonts.gstatic.com on every page load, and
   removes an external dependency. Files live in /assets/fonts/.

   Google's CSS2 API splits the single Urbanist variable-font family
   into 4 files (italic/normal x latin/latin-ext unicode ranges); each
   file covers the full 100-900 weight axis internally, which is why
   font-weight below is written as a RANGE (100 900) rather than a
   single value -- that's correct for a variable font, not a typo.

   NOTE: the old Google Fonts link also requested "Montserrat", but a
   full-codebase search found no CSS rule or inline style anywhere that
   actually references font-family: Montserrat -- it was being loaded
   and never used. Deliberately dropped rather than self-hosting dead
   weight. If a future page legitimately needs it, it will need to be
   added back explicitly.
   ======================================================== */

@font-face {
    font-family: 'Urbanist';
    font-style: italic;
    font-weight: 100 900;
    font-display: swap;
    src: url('/assets/fonts/urbanist-italic-latin-ext.woff2') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C4, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
    font-family: 'Urbanist';
    font-style: italic;
    font-weight: 100 900;
    font-display: swap;
    src: url('/assets/fonts/urbanist-italic-latin.woff2') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
    font-family: 'Urbanist';
    font-style: normal;
    font-weight: 100 900;
    font-display: swap;
    src: url('/assets/fonts/urbanist-normal-latin-ext.woff2') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C4, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
    font-family: 'Urbanist';
    font-style: normal;
    font-weight: 100 900;
    font-display: swap;
    src: url('/assets/fonts/urbanist-normal-latin.woff2') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}

/* ========================================================
   SHARED -- identical at every width
   ======================================================== */

.note{ font-size: .9em; }
.nine{ text-transform: lowercase; }

.error_msg{ font-size: .9em; text-align: center; color: red; }
.success_msg{ font-size: .9em; text-align: center; color: green; }
.emailsuccess_msg{ font-size: .9em; text-align: center; color: green; } /* 2026-11-11: was #f7f318 (yellow), unreadable on the white newsletter box */

h2{ font-family: Urbanist, "sans-serif"; text-transform: uppercase; margin-top: 30px; }
h2 span{ font-size: .5em; }
h3{ text-transform: uppercase; }

a{ text-decoration: none; }
a:hover{ color: #30c0cf; }

html{ width: 100vw; overflow-x: hidden; }

body{
    width: 100%;
    min-width: 100%;
    max-width: 100%;
    margin: 0;
    padding: 0;
    overflow-x: hidden;
    font-family: "Urbanist", "Sans-serif";
    background: url('/assets/images/hero1bg.webp') no-repeat 0px 0px / 100% 1000px;
}

main{ width: 100%; margin-bottom: 0px !important; }

.main-container{
    display: flex;
    flex-wrap: wrap;
    flex-direction: row;
    flex-flow: row wrap;
    justify-content: flex-start;
    gap: 0px;
    width: 100%;
}

/* ---- header / logo / top nav / hamburger ---- */

header{ width: 100%; margin: 0; padding: 0; }

.header-row{
    display: flex;
    align-items: center;
    flex-wrap: wrap;
    width: 100%;
}

#logo{ flex: 0 0 auto; }
#logo a{ display: block; }
#logo img{ display: block; }

#nav ul{
    list-style-type: none;
    margin: 0;
    padding: 0;
    overflow: hidden;
    display: flex;
}

#nav ul li a{
    display: block;
    color: #002;
    text-align: center;
    padding: 5px 16px;
    text-decoration: none;
}

#nav ul li a:hover{ color: #30c0cf; }

#hamburgerBtn{ cursor: pointer; flex-shrink: 0; }
#hamburgerBtn:focus{ outline: none; }
#hamburgerBtn:focus-visible{ outline: 3px solid #30c0cf; outline-offset: 2px; }

/* ---- side-menu (single drawer, sized per breakpoint below) ---- */

.side-menu{
    position: fixed;
    top: 50%;
    transform: translateY(-50%);
    background: #fff;
    color: #002;
    padding-top: 10px;
    transition: left 0.5s ease;
    z-index: 1000;
    border: 1px solid #ccc;
    border-radius: 16px;
    box-shadow: 2px 0 5px rgba(0,0,0,.3);
    overflow-y: auto;
    overflow-x: hidden;
}

/* neutralize Bootstrap's .row/.col gutters inside the menu -- those negative
   row margins + column padding were pushing content past the menu's own
   width and causing a horizontal scrollbar */
.side-menu .row{ margin-left: 0; margin-right: 0; }
.side-menu [class*='col-']{ padding-left: 0; padding-right: 0; }

.side-menu.active{ left: 0; }

.side-menu h2{
    color: #002;
    text-align: left;
    float: left;
    margin: 15px 0 0;
}

.side-menu button{
    position: absolute;
    top: 16px;
    right: 16px;
    margin: 0;
    width: 32px;
    height: 32px;
    min-width: 32px;
    min-height: 32px;
    border: 1px solid #d6bf85;
    border-radius: 8px;
    background: url('/assets/images/close-orange.webp') no-repeat 50% 50% / 18px 18px, #fff;
    padding: 0;
    appearance: none;
    cursor: pointer;
}

.side-menu button:focus{ outline: none; }
.side-menu button:focus-visible{ outline: 3px solid #30c0cf; outline-offset: 2px; }

.side-menu button:hover{
    background: url('/assets/images/close-teal.webp') no-repeat 50% 50% / 18px 18px, #fff;
    border: 1px solid #d6bf85;
}

.side-menu h3{ text-align: left; }
.side-menu h4{ text-align: left; padding-right: 20px; }
.side-menu .margin-top-30{ margin-top: 30px; }
/* a <ul>'s own browser-default ~16px margin-bottom was never reset here;
   it normally collapses invisibly into the next h3's margin-top-30 when
   both sit in the same column (Company->Apps, Websites->Domains), landing
   on a clean 30px either way -- but the Apps/Websites columns stack on
   mobile (see the mobile .side-menu rules), and a flex item's children
   can't collapse their margins out through it, so that same 16px survives
   uncollapsed right where Apps' column ends and Websites' begins, making
   that one gap 46px instead of 30px. Reset it so all three gaps match. */
.side-menu ul{ margin-left: 0; margin-bottom: 0; list-style: none; padding-left: 0; }
.side-menu li:last-child{ margin-bottom: 0; }
.side-menu li{ width: 100%; margin: 4px 0; padding: 0px; list-style: none; }
.side-menu li a{ text-align: left; color: #002; font-size: 1.1em; }
.side-menu li a:hover{ color: #30c0cf; }

.gradient-underline{
    max-width: 75%;
    position: relative;
    padding-bottom: 4px;
    background-image: linear-gradient(to right, #6deafc, #7562ee);
    background-repeat: no-repeat;
    background-size: 100% 1px;
    background-position: 0 100%;
}

/* ---- hero ---- */

#hero{ position: relative; }
#hero #tagline sup{ font-size: .6em; }

#hero #tagline, #hero #image{ position: relative; }

/* hero slideshow (fade transition) */
.hero-slide{
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
    opacity: 0;
    visibility: hidden;
    transition: opacity 1s ease-in-out;
    pointer-events: none;
}
.hero-slide.active{
    opacity: 1;
    visibility: visible;
    pointer-events: auto;
}

#image-slide1{ background: url('/assets/images/slide1.webp') no-repeat center center / cover; }
#image-slide2{ background: url('/assets/images/slide2.webp') no-repeat center center / cover; }

.hero-dots{
    position: absolute;
    left: 50%;
    bottom: 16px;
    transform: translateX(-50%);
    display: flex;
    gap: 10px;
    z-index: 2;
    width: auto;
    max-width: none;
    padding: 0;
}
.hero-dot{
    min-width: 0;
    width: 10px;
    height: 10px;
    padding: 0;
    border-radius: 50%;
    background: rgba(0,2,34,.2);
    border: 1px solid rgba(0,2,34,.35);
    cursor: pointer;
}
.hero-dot:hover{ background: rgba(0,2,34,.4); }
.hero-dot.active{ background: #ffb900; border-color: #ffb900; }

/* ---- content (apps/domains/websites) ---- */

#content{
    /* Round 2 item 17: this used to be 175px, leaving a long stretch of
       plain white space below the Websites button before #blog's own
       background (blogbg.webp) began -- since that background has a hard
       box edge (no fade of its own at the very top), the sudden flat-white-
       to-wave-pattern transition read as a visible seam/"crease" between
       the two sections. Shrinking this pulls #blog's whole box (and so its
       background) up to cover most of that gap; #blog h2's own margin-top
       below is increased by the same amount so the "LATEST / NEWS & BLOG"
       heading keeps the same distance from the button as before -- only the
       background/seam moves, not the text spacing. */
    padding-bottom: 40px;
    /* content1bg.webp is blank for most of its own top edge, but the
       diagonal wave shape at the right starts with a hard edge rather than
       a fade. Because this image renders much shorter than #content at
       most viewport heights (it's bottom-anchored), that hard edge sits
       exposed out in open white space instead of blending in. Layer a
       white-to-transparent fade over the image's own top ~180px (sized and
       positioned to match the image's box exactly, so the fade tracks it
       at any viewport width) so it eases in instead of appearing abruptly. */
    background-image:
        linear-gradient(to bottom, #fff 0%, rgba(255,255,255,0) 180px),
        url('/assets/images/content1bg.webp');
    background-repeat: no-repeat, no-repeat;
    background-position: 0% 100%, 0% 100%;
    background-size: 100% 617px, 100% 617px;
}

#content h2{ padding-left: 5px; padding-right: 5px; }

#content .content-tagline{
    font-weight: 700;
    font-size: 1.15em;
    margin-top: -10px;
}

#content p{
    width: 75%;
    margin-right: 20%;
    padding-left: 5px;
    padding-right: 5px;
}

#content button{ margin-right: 5px; margin-left: 5px; }

.float-right{ margin-left: 25%; }

#content #image1{ background: url('/assets/images/content-image1.webp') no-repeat 0 0 / 500px 500px; height: 500px; }
#content #image2{ background: url('/assets/images/content-image2.webp') no-repeat 0 0 / 500px 500px; width: 500px; height: 500px; }
#content #image3{ background: url('/assets/images/content-image3.webp') no-repeat 0 0 / 500px 500px; height: 500px; }

/* ---- Entry 55: wider gap between the image and text in the Apps and
   Websites sections (Shaunie: "increase the margin between the image
   and the content to about double what currently exist"), each judged
   against ITS OWN current gap. Apps and Websites aren't built quite the
   same way under the hood -- Websites' zigzag position already carries
   an extra leading spacer column that Apps doesn't have (unrelated to
   this change), so it already had a bigger gap than Apps' before this,
   and doubling each section's own measured gap takes a different
   amount of added padding-left in each case. Domains (#image2 /
   #image2text) wasn't mentioned and is untouched. ---- */
#content #image1text{ padding-left: 29px; }
/* ---- Entry 55: in the Websites section specifically, the paragraph
   text was running past the right edge of the Domains image sitting
   directly above it on desktop (that section swaps to text-left /
   image-right there -- see #image2{order:2} / #image2text{order:1}
   further down). #image2's own width is a fixed 500px rather than the
   fluid % every other column here uses, so capping the Websites
   paragraph at a matching fixed max-width (on top of keeping a fluid %
   for narrower desktop widths) is what keeps the text from drifting
   past that edge as the viewport gets wider, not just at one screen
   size. Confirmed clear at 1200-2560px wide; some overlap remains at
   the narrow end of the desktop range (~1024px and below), which is a
   separate, pre-existing issue to revisit during the mobile/responsive
   review.

   Round 6 follow-up (Shaunie: "adjust the width of the content of the
   Websites section on the home page"): the 391px cap above was leaving
   a big dead strip of whitespace to the right of the paragraph inside
   its own (732px-wide) column, noticeably narrower than Apps' matching
   column right above it (~518px, no cap at all there). Re-measured the
   actual available headroom live on staging at 1200/1440/1920/2560px
   wide (the whole "confirmed clear" range from the comment above): the
   gap between the Domains image's right edge and where this paragraph
   starts is a constant 421px at every one of those widths (both sides
   of that gap are part of the same fluid-width row, so they move
   together as the viewport changes) -- with zero vertical gap between
   the two sections at some of those widths, so that 421px is a hard
   ceiling, not a rough guess. Widened to 405px (keeping a 16px safety
   margin rather than cutting it to the exact edge), and switched from a
   flat `width` to `width:100% + max-width` so the paragraph can never
   overflow its own column if some in-between breakpoint turns out to be
   narrower than 405px -- Apps/Domains have no cap at all and don't need
   one, but this section does, so it should at least degrade safely.

   Round 9 follow-up (Shaunie: "make the Website content section a
   little wider maybe 36px wider"): re-verified the real constraint
   directly on THIS section's own elements this time (not the Domains
   proxy measurement above) -- #image3text (this column) has no trailing
   spacer to its right at all: #image3section's three trailing/leading
   col-md-1 spacers plus #image3 (col-md-4) plus #image3text (col-md-6)
   sum past 100% of the row, so the flex row wraps the LAST spacer clean
   off; #image3text's own right edge lands exactly flush with #content's
   right edge at every width tested (769-2560px). #image3text's box
   height is also flex-stretched to match #image3's image column, so it
   doesn't grow/shrink with the paragraph's own line-wrap count either.
   Net effect: there's no real ceiling here except the column's own
   available width, which only matters below ~920px (where, same as
   today, the cap simply isn't reached and width:100% takes over --
   confirmed in an isolated harness this degrades exactly as gracefully
   at 441px as it already did at 405px). 405 + 36 = 441px. ---- */
#content #image3text{ padding-left: 29px; }
#content #image3text p{ width: 100%; max-width: 441px; }

/* Round 3 item 27 (second pass): wraps the Websites section's own flex
   items (index.php) so the mobile-only background fix below can be scoped
   to just this section's own box. display:contents makes the wrapper
   generate no box of its own on desktop, so #image3/#image3text/the
   spacer columns still flex directly against #content exactly as if the
   wrapper weren't there -- this rule alone should have zero visible effect
   above the mobile breakpoint. */
#image3section{ display: contents; }


/* ---- newsletter CTA ---- */

#ctanewsletter{
    text-align: center;
    padding: 50px 0 70px;
    margin-top: 0px;
    min-height: 285px;
    background-color: #fff;
    /* newsletterbg.webp renders taller than this section at most viewport
       widths (its own height scales with 100%-width sizing), and since it's
       anchored to the bottom, the image's soft, faded-in top portion gets
       clipped off -- what's left showing is already deep into the image's
       more saturated color, so it appears out of nowhere right at the top
       of this section. Layer a white-to-transparent gradient over the
       first 110px to fade that into a soft entrance instead. */
    background-image:
        linear-gradient(to bottom, #fff 0%, rgba(255,255,255,0) 100%),
        url("/assets/images/newsletterbg.webp");
    background-repeat: no-repeat, no-repeat;
    background-position: center top, center bottom;
    background-size: 100% 110px, 100% auto;
}

.parallax{
    background-image: url("/assets/images/ctabg.webp");
    min-height: 285px;
    background-attachment: fixed;
    background-position: center;
    background-repeat: no-repeat;
    background-size: cover;
}

#ctanewsletter .newsletter-box{
    background: #fff;
    color: #002;
    box-sizing: border-box;
    max-width: 760px;
    margin: 0 auto;
    padding: 4px 60px 50px;
    border: 1px solid #ccc;
    border-radius: 8px;
}

#ctanewsletter .newsletter-box h2{
    margin-top: 0;
    margin-bottom: -18px;
    font-size: 2em;
    font-weight: 500;
    color: #002;
    transform: translateY(-50%);
}

#ctanewsletter .newsletter-box h2 span{
    display: block;
    font-size: .5em;
    font-weight: 500;
    color: #002;
}

#ctanewsletter .newsletter-box h2 span.title-word{
    display: inline-block;
    position: relative;
    top: 4.5px;
    font-size: 1em;
    font-weight: inherit;
    border-top: 4px solid #fff;
}

#ctanewsletter .newsletter-box p{ color: #002; }

#ctanewsletter .ctamessage:empty{ display: none; }

#ctanewsletter .form-row{
    display: flex;
    flex-direction: column;
    gap: 16px;
    margin-bottom: 8px;
}

#ctanewsletter .form-col{
    flex: 1 1 0%;
    text-align: left;
    width: 44%;
    margin: 0 auto;
}

#ctanewsletter .form-col label{
    width: auto;
    float: none;
    margin-top: 10px;
}

/* honeypot -- hidden from sighted users AND assistive tech; never shown, never reachable by tab */
#ctanewsletter .hp-field{
    position: absolute;
    width: 1px;
    height: 1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    white-space: nowrap;
}

/* same visually-hidden-but-focusable honeypot technique as #ctanewsletter's
   own .hp-field above, scoped to the 6 modal popup forms (footer.php) */
#emailPopupForm .hp-field,
#noirPopupForm .hp-field,
#mlbPopupForm .hp-field,
#appPopupForm .hp-field,
#webPopupForm .hp-field,
#seoPopupForm .hp-field{
    position: absolute;
    width: 1px;
    height: 1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    white-space: nowrap;
}

/* visually-hidden utility -- NOT a honeypot: unlike the .hp-field rules
   above (which exist only as a spam trap and are never meant to be
   announced), text wrapped in this class IS fully exposed to screen
   readers -- it's just not shown on screen. Used to announce "(opens in
   a new tab)" on external links without adding visible clutter for
   sighted users. */
.visually-hidden{
    position: absolute;
    width: 1px;
    height: 1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    white-space: nowrap;
}

/* small arrow icon flagging a link that opens in a new tab; aria-hidden
   since the .visually-hidden text alongside it already announces the
   same thing to screen readers */
.ext-link-icon{
    display: inline-block;
    margin-left: 4px;
}

#ctanewsletter .form-col input[type="text"],
#ctanewsletter .form-col input[type="email"]{
    width: 100%;
}

#ctanewsletter .check-box{
    text-align: left;
    width: 44%;
    margin-left: auto;
    margin-right: auto;
}

#ctanewsletter .check-box label{
    width: auto;
    float: none;
    margin-top: 0px;
    display: flex;
    align-items: flex-start;
    gap: 8px;
    cursor: pointer;
}

#ctanewsletter .submit-row{
    text-align: center;
    margin-top: 16px;
}

#ctanewsletter button{
    min-width: 100px;
    padding: 10px 20px;
    background: #fff;
    /* Round 4 item 4: this was #e0b400, a darker/more mustard gold that
       doesn't match the house amber (#ffb900) used everywhere else
       (Learn More button fill, breadcrumb links, etc.) -- Shaunie flagged
       it as "gold" when it should read as the brand orange. */
    border: 1px solid #ffb900;
    color: #002;
    border-radius: 8px;
    font-weight: 600;
    text-transform: uppercase;
    margin-top: 0px;
}

#ctanewsletter button:hover{
    background: #fdf6e3;
    border: 1px solid #ffb900;
    color: #002;
}

#ctanewsletter input[type="text"]:focus-visible,
#ctanewsletter input[type="email"]:focus-visible,
#ctanewsletter input[type="checkbox"]:focus-visible,
#ctanewsletter button:focus-visible{
    outline: 3px solid #30c0cf;
    outline-offset: 2px;
}

/* ---- blog ---- */

#blog{
    /* blogbg.webp at "100% auto" renders shorter than this section at most
       viewport widths (e.g. ~833px tall inside a ~950px section), leaving a
       gap of no image at all near the bottom -- and because the image's own
       trailing edge is a faint tint rather than pure white, that gap showed
       up as a visible hard-edged cutoff instead of a clean fade. background-
       size: cover guarantees the image always fully fills the section
       height (cropping a little off the left/right instead, which this
       wide, edge-faded wave graphic hides well), so there's no gap or seam
       left to show. */
    /* Round 3 item 27 (carryover from Round 2 item 17), first pass: tried
       layering a white-to-transparent fade over this image's own top edge
       (blogbg.webp's top is a solid light blue, not white/transparent, so
       #content's white background met it in one hard line). That worked,
       but Shaunie's second look asked for a different approach instead --
       give the Websites section above its own matching background (see
       #image3section, mobile-only, further down) so both sections already
       read as the same wave artwork meeting itself, no seam-hiding fade
       needed on either side. Reverted this rule to its pre-fade form. */
    background-image: url('/assets/images/blogbg.webp');
    background-repeat: no-repeat;
    background-position: center top;
    background-size: cover;
    position: relative;
    align-content: flex-start;
}

#blog h2{
    text-align: center;
    margin-bottom: 0px !important;
    max-height: 100px;
}

#blog img{
    width: 100%;
    max-width: 320px;
    height: auto;
    aspect-ratio: 482 / 412;
    object-fit: cover;
    margin-left: auto;
    margin-right: auto;
    display: block;
}

#blog .blog-posts{
    box-sizing: border-box;
    max-width: 1100px;
    margin-left: auto;
    margin-right: auto;
}

#blog .author{ font-size: .9em; color: #555; margin-top: 0px; }
#blog .readtime{ font-size: .95em; }
#blog .title{
    font-family: "Urbanist", Sans-serif;
    font-weight: 500;
    font-size: 1.1em;
    color: #555;
    line-height: 1.5;
    margin-top: 25px;
    margin-bottom: 0px;
}
#blog .excerpt{
    font-size: 1.1em;
    color: #555;
    line-height: 1.5;
    margin-top: 30px;
    margin-bottom: 16px;
}
#blog .instruction{ margin-top: 0px !important; text-align: center; }

#blog button{
    min-width: 100px;
    padding: 10px 20px;
    font-weight: 600;
    text-transform: uppercase;
    margin-top: 10px;
    background: #ffb900;
    border: 1px solid #ffb900;
    color: #fff;
    border-radius: 8px;
}

#blog button:hover{
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
}

/* ---- footer ---- */

footer{
    background: #f9f9fb;
    padding-top: 20px;
    width: 100%;
}

footer a{ text-decoration: none; }
footer a:hover{ color: #30c0cf; }

footer #logo{ margin-left: 0; }
footer #logo img{ display: block; margin: 0 auto; }

.footer-links{
    display: grid;
    gap: 30px 15px;
    max-width: 1000px;
    margin: 0 auto;
    padding: 0 20px;
    box-sizing: border-box;
}

.footer-links h3{ margin-top: 0; }
.footer-links ul{ list-style-type: none; margin: 0; padding: 0; }
.footer-links li{ margin-bottom: 5px; }
.footer-links a{ color: #002; }

footer #connect img{ width: 24px; height: 24px; margin-right: 5px; }

/* Contact column: icon + text used to be siblings inside a single <a>,
   so when the text wrapped onto a second line (narrower columns, longer
   addresses) or a second link followed on its own line, that continuation
   line had nothing holding it in from the left and sat flush under the
   icon instead of under where the text itself starts. Making the <li> a
   flex row with the icon as a fixed-width item and the rest of the entry
   in one text column fixes that at any width -- any wrap inside
   .contact-text stays inside that column. */
footer #contactinfo li{ display: flex; align-items: flex-start; gap: 5px; }
footer #contactinfo img{ width: 16px; height: 16px; margin-right: 0; margin-top: 3px; flex-shrink: 0; }
footer #contactinfo .contact-text{ min-width: 0; }

footer #copyright{
    width: 100%;
    padding-top: 10px;
    padding-bottom: 12px;
    background: #0e0f28;
    color: #fff;
    font-size: .9em;
    text-align: center;
}

footer #copyright p{ margin: 0; }
footer #copyright a{ color: skyblue; }

/* ---- buttons / forms (shared) ---- */

button{
    min-width: 100px;
    background: #ffb900;
    border: 1px solid #ffb900;
    color: #fff;
    border-radius: 8px;
}

button a{ text-decoration: none; color: #fff; }

button:hover{
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
}

button .active{
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
}

/* hollow/outline button -- reusable sitewide. Border (and text) stay the
   same brand orange (#ffb900) as the solid button's fill, just without the
   fill, so it reads as a lower-emphasis sibling of the solid .btn style. */
.btn-hollow{
    background: transparent;
    color: #ffb900;
    border: 1px solid #ffb900;
}

.btn-hollow:hover{
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
}

form p{ float: left; width: 90%; margin-left: 5%; }

label{ width: 100%; float: left; margin-top: 10px; color: #555; }
label span{ width: 90%; float: left; text-align: center; }
label p{ margin-left: 5%; max-width: 75%; margin-bottom: 0px; margin-top: 8px; }

.check-box{
    display: flex;
    align-items: flex-start;
    gap: 8px;
    margin-top: 0px;
    padding-top: 0px;
    padding-bottom: 3px;
    margin-bottom: 20px;
}

.check-box p{ margin: 0; flex: 1; min-width: 0; }

input[type="text"], input[type="email"], input[type="tel"]{
    width: 100%;
    padding: 8px;
    margin: 8px 0;
    border: 1px solid #ccc;
    border-radius: 4px;
    box-sizing: border-box;
}

input[type="checkbox"]{
    width: 25px;
    height: 25px;
    border: 1px solid #ccc;
    flex-shrink: 0;
}

/* ---- popup / modal ---- */

.modal{
    display: none;
    position: fixed;
    z-index: 1;
    left: 0; top: 0;
    width: 100%; height: 100%;
    background-color: rgba(0,0,0,0.5);
}

.modal h2{ margin-top: 0px; padding-top: 0px; }

.modal-content{
    position: relative;
    background: #fff;
    padding: 10px 20px;
    border-radius: 16px;
    box-shadow: 0 4px 8px rgba(0,0,0,0.2);
    box-sizing: border-box;
}

/* same close-button treatment as the pop-out nav menu's close button */
.close, .closeNoir, .closeMLB, .closeAppConsult, .closeWebConsult, .closeSeoConsult{
    position: absolute;
    top: 16px;
    right: 16px;
    margin: 0;
    width: 32px;
    height: 32px;
    min-width: 32px;
    min-height: 32px;
    border: 1px solid #d6bf85;
    border-radius: 8px;
    background: url('/assets/images/close-orange.webp') no-repeat 50% 50% / 18px 18px, #fff;
    appearance: none;
    cursor: pointer;
}

.close:hover, .closeNoir:hover, .closeMLB:hover, .closeAppConsult:hover, .closeWebConsult:hover, .closeSeoConsult:hover{
    background: url('/assets/images/close-teal.webp') no-repeat 50% 50% / 18px 18px, #fff;
    border: 1px solid #d6bf85;
}

/* center the whole set of form fields (labels, inputs, checkbox/terms row)
   as one column, and keep the ~20% field-width reduction from Entry 29 --
   doing the inset here, on the form itself, instead of on each field
   individually, is what keeps them all centered together. */
.modal-content form{
    width: 80%;
    margin: 0 auto;
}

.modal-content input[type="text"],
.modal-content input[type="email"],
.modal-content input[type="tel"]{ width: 100%; }

/* the 3 "consult request" popups (App/Web/SEO) add a phone field + this
   select; it had no width rule at all before, so it sat at its native
   shrink-to-fit size instead of lining up with the text inputs above it */
.modal-content select{
    width: 100%;
    padding: 8px;
    margin: 8px 0;
    border: 1px solid #ccc;
    border-radius: 4px;
    box-sizing: border-box;
    font-family: inherit;
    font-size: 1em;
}

.modal button{
    background: #ffb900;
    color: #fff;
    padding: 10px;
    border: none;
    border-radius: 8px;
    cursor: pointer;
}

.modal button:hover{
    background: #30c0cf;
    border: 1px solid #30c0cf;
}

/* hollow/outline variant -- higher specificity than ".modal button" so it
   overrides the solid-fill default above when this class is added */
.modal button.btn-hollow{
    background: transparent;
    color: #ffb900;
    border: 1px solid #ffb900;
}

.modal button.btn-hollow:hover{
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
}

.message{ margin-top: 10px; font-size: 14px; }

@keyframes fadeIn{
    from { opacity: 0; transform: translateY(-20px); }
    to { opacity: 1; transform: translateY(0); }
}

/* ---- cookie disclaimer (matches 9o9Designs' .cookie-banner card pattern
   -- a white card with a thin accent border that slides up from the
   bottom and persists a real cookie on accept -- recolored to 9o9Brand's
   own amber/teal button palette. Replaces the old .cookie-popup
   opacity-fade card and its non-functional JS, which only ever toggled
   CSS classes and never actually read or wrote a real cookie, so the
   popup reappeared on every page load. See PROJECT-NOTES.md Entry 51.) ---- */

.cookie-banner{
    position: fixed;
    left: 20px;
    right: 20px;
    bottom: -220px;
    z-index: 999;
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: space-between;
    gap: 15px;
    max-width: 650px;
    margin: 0 auto;
    padding: 18px 22px;
    background: #fff;
    border: 1px solid #ffb900;
    border-radius: 8px;
    box-shadow: 0 10px 30px rgba(0,0,0,.15);
    font-size: 0.875rem;
    line-height: 1.5;
    color: #002;
    transition: bottom .5s ease;
}

.cookie-banner.show{ bottom: 20px; }

.cookie-banner p{ margin: 0; flex: 1 1 320px; }

.cookie-banner a{ color: #002; text-decoration: underline; }

.cookie-banner a:hover{ color: #30c0cf; }

.cookie-banner-actions{ flex: 0 0 auto; }

.cookie-banner-actions button{
    font-size: 0.75rem;
    text-transform: uppercase;
    letter-spacing: .05em;
    padding: 10px 22px;
    cursor: pointer;
    transition: all 0.2s ease;
}

/* ===================================================================
   Scroll-reveal animation, sitewide (home + inner pages). Pattern
   matches 9o9Designs' own assets/css/style.css, which was itself
   borrowed from sacredexecutiveprotection.com per Shaunie's request --
   plain CSS transitions + a small IntersectionObserver script (see
   assets/src/scroll-reveal.js), no animation library. Replaces the
   earlier .glideup scroll-listener version (PROJECT-NOTES.md Entry 54).
   Elements start hidden/offset, then animate in the moment they
   actually scroll into view (each element animates once, via
   observer.unobserve() in the script). .reveal = fade + slide up;
   .reveal-left/-right = fade + slide in from that side (use on a side
   image/visual paired with a text block on the opposite side);
   .reveal-scale = fade + gentle zoom in from 0.8. Respects
   prefers-reduced-motion. ===================================================
   =================================================================== */
.reveal{
    opacity: 0;
    transform: translateY(30px);
    transition: opacity .7s ease, transform .7s ease;
}
.reveal.in-view{
    opacity: 1;
    transform: translateY(0);
}
.reveal-left{
    opacity: 0;
    transform: translateX(-50px);
    transition: opacity .7s ease, transform .7s ease;
}
.reveal-left.in-view{
    opacity: 1;
    transform: translateX(0);
}
.reveal-right{
    opacity: 0;
    transform: translateX(50px);
    transition: opacity .7s ease, transform .7s ease;
}
.reveal-right.in-view{
    opacity: 1;
    transform: translateX(0);
}
.reveal-scale{
    opacity: 0;
    transform: scale(.8);
    transition: opacity .7s ease, transform .7s ease;
}
.reveal-scale.in-view{
    opacity: 1;
    transform: scale(1);
}
@media (prefers-reduced-motion: reduce){
    .reveal, .reveal-left, .reveal-right, .reveal-scale{
        opacity: 1;
        transform: none;
        transition: none;
    }
}

/* ========================================================
   INNER PAGES -- .inner-page body class (added by header.php /
   header_noindex.php). Scoped under .inner-page so these rules
   never touch the home page's own #hero / #content / #breadcrumbs,
   which have different meanings there. See PROJECT-NOTES.md.
   ======================================================== */

.inner-page #hero p{ text-align: center; }

.inner-page #breadcrumbs{
    padding-top: 10px;
    padding-bottom: 5px;
    background: #fff;
    color: #30c0cf;
}

.inner-page #breadcrumbs a{ color: #ffb900; text-decoration: none; }
.inner-page #breadcrumbs a:hover{ color: #30c0cf; text-decoration: none; }

.inner-page #content{
    min-height: 300px;
    padding-top: 25px;
    padding-bottom: 75px;
    background: #fff;
}

/* #content carries the sitewide .reveal class (scroll-reveal.js), which
   starts every .reveal element at opacity:0 until the IntersectionObserver
   in that script fires. That script loads as a plain, non-deferred <script>
   at the very end of the body, so on a slow connection -- or just a user
   who scrolls before it's done loading -- there's a real window where
   #content (and its "background:#fff" above) is still fully transparent,
   letting body's own hero1bg.webp bleed straight through for the whole
   content area instead of just the hero/banner above it. Inner-page
   content doesn't need a scroll-triggered fade-in anyway (it's short,
   text-driven, and usually already in view on load), so force it visible
   immediately and skip the animation here entirely. */
.inner-page #content.reveal{
    opacity: 1;
    transform: none;
}

.inner-page #content p{
    width: 100%;
    margin-right: 0;
}

/* 2-column list (e.g. the Contact page's Observed Holidays), matching
   9o9Designs's own contact page layout. */
.inner-page #content .two-cols{
    columns: 2;
    column-gap: 30px;
}

.inner-page #content .two-cols li{
    break-inside: avoid;
    margin-bottom: 12px;
}

/* generic text form field styling the site never needed until now --
   non-modal select and textarea, and the "* Denotes a required field"
   note, all matching 9o9Designs's own contact-page conventions. */
.inner-page .required-note{
    color: #555;
    font-size: 14px;
    margin-top: 10px;
}

.inner-page .select{
    width: 100%;
    float: left;
    border: 1px solid #ccc;
    height: 45px;
    margin: 8px 0;
    padding-right: 5px;
    background: #fff;
    box-sizing: border-box;
    font-family: inherit;
    font-size: 1em;
}

.inner-page .select option{ color: #000; }
.inner-page .select option:first-child{ color: #999; }

.inner-page textarea{
    width: 100%;
    height: 100px;
    font-family: "Urbanist", "Sans-serif";
    color: #555;
    font-size: 1em;
    padding: 8px;
    border: 1px solid #ccc;
    box-sizing: border-box;
}

/* pair First/Last Name and Email/Phone side by side on the Contact Us
   form, same as 9o9Designs's contact page. display:flex takes
   .consult-form-col out of the sitewide label/input float flow
   entirely (flex items -- and anything floated inside them -- compute
   their own height correctly, regardless of the sitewide float rules),
   so no extra clearing is needed. Scoped to #contactUsForm only, so no
   other form on the site is affected. */
#contactUsForm .consult-form-row{
    display: flex;
    gap: 24px;
}

#contactUsForm .consult-form-col{
    flex: 1;
    min-width: 0;
}

/* the sitewide "label span{width:90%;float:left;text-align:center}"
   rule would otherwise catch the "(optional)" note next to the Message
   label and force it onto its own centered line instead of sitting
   inline after the label text. Scoped to just this one label. */
#contactUsForm label[for='comments'] .note{
    float: none;
    width: auto;
    text-align: left;
    display: inline;
}

/* the submit button's wrapping <p class='text-center'> is caught by two
   sitewide rules that conflict for a form living inside #content on an
   inner page: form p{float:left;width:90%;margin-left:5%} and
   .inner-page #content p{width:100%;margin-right:0}. The second rule
   wins on width (it has an #id, so it's more specific) but doesn't
   touch margin-left, so the wrapper ends up 100% wide *plus* a leftover
   5% left margin -- an asymmetric box that pushes the centered button
   left of true center. This conflict never existed before #contactUsForm
   (no inner-page form had a plain <p>-wrapped button directly inside
   #content until now). Resetting float/width/margin here restores true
   centering; margin-top adds space above the button. */
#contactUsForm p.text-center{
    float: none;
    width: 100%;
    margin-left: 0;
    margin-right: 0;
    margin-top: 20px;
}

/* ---- Do Not Sell form (mirrors #contactUsForm's own fixes above,
   adapted for this form's extra section-intro paragraphs and divider) ---- */

/* pair First/Last Name, same flex pairing as #contactUsForm. clear:both
   is needed here (unlike #contactUsForm) because each row sits right
   after a floated, uncleared <p class='section-intro'> -- see that
   rule below -- which would otherwise squeeze the row into a narrow
   sliver at the float's leftover ~5-10% width. */
#donotsellForm .consult-form-row{
    display: flex;
    gap: 24px;
    clear: both;
}

#donotsellForm .consult-form-col{
    flex: 1;
    min-width: 0;
}

/* the sitewide form p{float:left;width:90%;margin-left:5%} rule would
   otherwise indent these two intro paragraphs the same way it indents
   every other <p> in a form -- these read better full-width, directly
   under their headings. */
#donotsellForm p.section-intro{
    float: none;
    width: auto;
    margin-left: 0;
}

/* spacing between "Your Information" and "Conservator Section" */
#donotsellForm hr.section-divider{
    clear: both;
    margin-top: 30px;
    margin-bottom: 20px;
}

/* both checkboxes in this form sit right after a floated, 100%-wide
   sitewide label{float:left;width:100%} (the Email label, and the
   State label) with nothing between them to clear it. .check-box is a
   flex container, which establishes its own block-formatting-context,
   so -- unlike a plain block box -- it tries to fit in the float's
   leftover horizontal space instead of ignoring it, squeezing its
   contents into a narrow vertical sliver. clear:both forces it below
   the float instead. */
#donotsellForm .check-box{
    clear: both;
}

/* same bug as #donotsellForm .check-box above (see that comment), but
   here the float it sits behind is the "Best Time to Contact You"
   .select{float:left;width:100%} dropdown -- the 3 "consult request"
   popups (App/Web/SEO) all have this select directly before .check-box
   with nothing to clear it, squeezing the terms note into an unreadable
   single-character-wide column. Added 2026-11-08 after Shaunie flagged
   it on the SEO consult popup. */
#appPopupForm .check-box,
#webPopupForm .check-box,
#seoPopupForm .check-box{
    clear: both;
}

/* same submit-button centering/margin fix as #contactUsForm, and for
   the same reason -- this form also has a plain <p>-wrapped button
   directly inside #content on an inner page. */
#donotsellForm p.text-center{
    float: none;
    width: 100%;
    margin-left: 0;
    margin-right: 0;
    margin-top: 20px;
}

/* ---- Careers: job application form (#jobApplicationForm), same fixes as
   #contactUsForm above -- nothing floated precedes this form's first row,
   so (unlike #donotsellForm) no clear:both is needed on it. ---- */
#jobApplicationForm .consult-form-row{
    display: flex;
    gap: 24px;
}

#jobApplicationForm .consult-form-col{
    flex: 1;
    min-width: 0;
}

#jobApplicationForm p.text-center{
    float: none;
    width: 100%;
    margin-left: 0;
    margin-right: 0;
    margin-top: 20px;
}

/* the resume file input -- no sitewide input[type="file"] rule exists yet,
   this is the first one on the site -- just a little breathing room to
   match the text inputs around it. */
#jobApplicationForm input[type="file"]{
    width: 100%;
    margin: 8px 0;
    box-sizing: border-box;
}

/* ---- Careers: job listing cards (careers.php) -----------------------
   New component -- the site had no existing "card grid" to reuse, so this
   borrows the modal's rounded-corner/shadow treatment (.modal-content)
   and the sitewide .btn colors to stay visually consistent. Stacks full
   width on mobile by default; the >=769px block below opens it up to a
   2-up grid on desktop. */
.job-cards{
    display: flex;
    flex-wrap: wrap;
    gap: 24px;
    margin-top: 10px;
    margin-bottom: 20px;
}

.job-card{
    flex: 1 1 100%;
    background: #fff;
    border-radius: 8px;
    box-shadow: 0 0 0.625rem 0 rgba(0,0,0,.15);
    padding: 24px;
    box-sizing: border-box;
    display: flex;
    flex-direction: column;
}

.job-card h3{ margin-top: 0; }
.job-card .job-card-excerpt{ color: #555; flex: 1; }
.job-card .job-card-cta{ margin-bottom: 0; margin-top: 10px; }
.job-card .job-card-cta .btn{ margin-bottom: 0; }

/* byline/CTA paragraphs on the job description page sit directly in
   #content, outside the form, so the sitewide form p{...} rule never
   touches them -- just a couple of small spacing tweaks. */
.job-byline{ color: #555; font-style: italic; margin-top: -10px; }
.job-apply-cta{ margin: 20px 0; }

/* ---- Team page: founder photo + bio -------------------------------------
   New component -- no existing photo+bio pattern on the site to reuse.
   Side-by-side on desktop (circular photo, bio text wrapping beside it),
   stacked with the photo centered above the bio on mobile. */
.founder-section{
    display: flex;
    flex-wrap: wrap;
    gap: 30px;
    align-items: flex-start;
    margin-top: 10px;
}

.founder-photo{
    flex: 0 0 220px;
    margin: 0 auto;
}

/* there's already a generic "#content img{width:500px;height:500px;}" rule
   (and its 280x280 mobile counterpart, further below) meant for the
   9o9Tech/Domains/Designs content images on other inner pages -- being an
   id+type selector, it would otherwise override a plain ".founder-photo
   img" rule, so this needs the extra class in the chain to out-specify it. */
.inner-page #content .founder-photo img{
    display: block;
    width: 220px;
    height: 220px;
    max-width: 100%;
    object-fit: cover;
    border-radius: 50%;
    border: 4px solid #fff;
    box-shadow: 0 0 0.625rem 0 rgba(0,0,0,.15);
}

.founder-bio{
    flex: 1 1 260px;
    min-width: 260px;
}

.founder-bio h3{ margin-top: 0; }

.inner-page .btn{
    min-width: 100px;
    padding: 10px 20px;
    background: #ffb900;
    border: 1px solid #ffb900;
    color: #fff;
    border-radius: 8px;
    margin-bottom: 30px;
    cursor: pointer;
}

.inner-page .btn a{ text-decoration: none; color: #fff; }
.inner-page .btn:hover{ background: #30c0cf; border: 1px solid #30c0cf; color: #fff; }

.inner-page .btn-active{
    min-width: 100px;
    padding: 10px 20px;
    background: #30c0cf;
    border: 1px solid #30c0cf;
    color: #fff;
    border-radius: 8px;
    cursor: default;
}

.inner-page .btn-active:hover{ opacity: .75; }

/* 2026-11-09: web/blog/index.php redesign -- matches 9o9Designs.com's
   dedicated blog page layout (https://9o9designs.com/web/blog/): one
   featured "latest" post with a larger image, side by side with its
   text, followed by a stacked list of previous posts with a smaller
   image, each image+text side by side. Base rules below are the
   desktop (side-by-side) layout; see the max-width:768px block near
   the end of this file for the mobile (stacked) version. Unlike
   9o9Designs' internal blog, 9o9Brand's blogfeed.xml links out to
   each post's original author site (9o9Designs/9o9Domains/9o9Tech),
   so there's no details page or .blogdetail-* styling here -- Read
   More opens the original post in a new tab, matching this page's
   existing behavior.
   Note: .blogpost-image sets BOTH flex-basis and width (260px /
   50%) -- flex-basis alone isn't a definite width for the <img>
   inside it to resolve its own width:100% against (confirmed via
   harness testing: without the explicit width, the image ignores
   its 260px column and renders at its full natural size instead).
   Also: the img rule below is chained as
   .inner-page #content .blogpost-image img (not just
   .blogpost-image img) for the same reason documented above
   .founder-photo img -- #content img{width:500px;height:500px;}
   is an id+type selector that otherwise overrides a plain class
   selector regardless of source order (confirmed via harness
   testing: without the extra specificity, every blog post image
   rendered at a flat 500x500 instead of its column width). */
.blogpost{
    display: flex;
    align-items: flex-start;
    gap: 32px;
}
.blogpost-featured{
    margin-bottom: 48px;
    padding-bottom: 48px;
    border-bottom: 1px solid #eee;
}
.blogpost-list{
    margin-top: 10px;
}
.blogpost-list .blogpost{
    padding: 32px 0;
    border-bottom: 1px solid #eee;
}
.blogpost-list .blogpost:first-child{
    padding-top: 0;
}
.blogpost-list .blogpost:last-child{
    border-bottom: none;
}
.blogpost-image{
    flex: 0 0 50%;
    width: 50%;
    min-width: 0;
}
.blogpost-list .blogpost-image{
    flex: 0 0 260px;
    width: 260px;
}
.inner-page #content .blogpost-image img{
    display: block;
    width: 100%;
    max-width: 100%;
    height: auto;
    aspect-ratio: 4 / 3;
    object-fit: cover;
    border-radius: 6px;
    background-color: #f2f2f2;
}
.blogpost-body{
    flex: 1 1 auto;
    min-width: 0;
}
.blogpost-title{
    font-weight: 700;
    color: #0e0f28;
    font-size: 1.2em;
}
.blogpost-featured .blogpost-title{
    font-size: 1.7em;
}
.blogpost-meta{
    margin-top: 6px;
    font-size: .85em;
    color: #777;
    text-transform: uppercase;
    letter-spacing: .02em;
}
.blogpost-excerpt{
    margin-top: 14px;
    color: #555;
}
.blogpost-readmore{
    margin-top: 20px;
}

/* ========================================================
   DESKTOP (>= 769px)
   ======================================================== */

@media (min-width: 769px){

    .hideondesktop{ display: none; }

    /* width:100vw + overflow-x:hidden on the base html{} rule (top of this
       file) is what keeps mobile free of the horizontal-scrollbar-gutter
       sliver. But that pairing -- overflow-x set on BOTH html and body --
       has a side effect browsers apply silently: whenever overflow-x is
       restricted while overflow-y is left unset, the UA treats overflow-y
       as "auto" too (an unrelated CSS rule most people have never heard
       of). With BOTH html and body doing this at once, body ends up being
       computed as its own private scroll box distinct from the real page
       viewport -- and position:sticky always anchors to the nearest such
       box, so a sticky header silently stops sticking (it just scrolls
       off like position:static) even though every visible thing about the
       layout looks completely normal otherwise. Verified in an isolated
       Playwright harness that this exact pairing -- and only this pairing
       -- was the cause; removing overflow-x restriction from just one of
       the two ancestors restores sticky immediately. Confirmed (same
       harness, 375-2560px) that neither html nor body has any actual
       horizontal overflow of its own at >=769px once this override is
       scoped to desktop only, so mobile's original protection is left
       completely untouched below. */
    html{ height: 100vh; width: 100%; overflow-x: visible; }

    /* open the careers listing up to a 2-up grid on desktop */
    .job-card{ flex: 1 1 calc(50% - 12px); }

    h1{ font-size: 3.5em; text-transform: uppercase; }

    /* sticky header (desktop only, per Shaunie's request) -- transparent
       at the top of the page (the home page's own hero1bg.webp is white
       up there, so a transparent bar blends in rather than showing a
       visible seam), then crossfades to solid white the moment the page
       scrolls -- .scrolled is toggled by assets/src/sticky-header.js via
       an IntersectionObserver watching a tiny sentinel placed just above
       the header (same technique as .reveal's scroll-reveal.js, no raw
       scroll-position listener). The transition is background-color only
       so it never fights the position:sticky/top animation itself.
       z-index 100 stays comfortably below .side-menu (1000) and
       .cookie-banner (999) so both still stack above the stuck header. */
    header{
        height: 100px;
        position: sticky;
        top: 0;
        z-index: 100;
        background: transparent;
        transition: background-color .25s ease;
    }
    header.scrolled{ background: #fff; }
    .header-row{ height: 100px; }

    /* logo ~5% smaller on desktop per Shaunie's request: 146 * 0.95 = 138.7 -> 139 */
    #logo{ margin-left: 8.3333%; }
    #logo img{ width: 139px; height: auto; }

    #nav{ order: 2; margin-left: auto; margin-right: 24px; }
    #nav ul li{ padding: 20px; font-size: 1.1em; text-transform: uppercase; }

    #hamburgerBtn{
        order: 3;
        width: 64px;
        height: 64px;
        margin-right: 110px;
        background: url('/assets/images/hamburger.webp') no-repeat center / 48px 48px;
    }
    #hamburgerBtn:hover{ background: url('/assets/images/hamburger-teal.webp') no-repeat center / 48px 48px; }

    .side-menu{ width: 50%; height: 580px; left: -100%; margin-left: 25%; }
    .side-menu h2{ width: 80%; padding-left: 30px; }
    .side-menu h3{ margin-left: 30px; font-size: 1.5em; }
    .side-menu h4{ margin-left: 40px; font-size: 1.3em; }
    .side-menu ul{ margin-left: 30px; }
    .side-menu li a{ height: 32px; padding-left: 0; }

    #hero{ height: 617px; }
    #hero #tagline{ text-align: right; }
    #hero #tagline h1{ margin-top: 64px; }
    #hero #tagline span{ font-size: .5em !important; margin-top: 0px; }
    #content img{ width: 500px; height: 500px; }
    #image2{ order: 2; }
    #image2text{ order: 1; }

    #blog{ min-height: 950px; }
    /* Round 2 item 17: was 30px -- raised by the same 135px #content's
       padding-bottom (above) was cut by, so the heading still sits the
       same distance below the button even though #blog's own box (and
       background) now starts 135px higher, covering the former gap. */
    #blog h2{ margin-top: 165px; }
    #blog .blog-posts{ padding: 0 60px; margin-top: 20px; }
    #blog .author, #blog .readtime, #blog .title{ clear: both; }

    footer{ padding-bottom: 0; }
    .footer-links{ grid-template-columns: repeat(4, 1fr); margin-top: 30px; max-width: 1280px; }
    footer #copyright{ margin-top: 50px; }

    button{ padding: 10px 20px; }
    /* height:auto + min-height (not a fixed height) so the 3 "consult
   request" popups (App/Web/SEO), which are taller than the simpler
   signup popups thanks to their extra Phone field and "Best Time to
   Contact You" select, can grow to fit their own content instead of
   overflowing past the bottom of this box -- matches the approach the
   mobile .modal-content rule below already uses. Added 2026-11-08
   alongside the .check-box clear:both fix above, after Shaunie flagged
   the SEO consult popup's checkbox/terms row rendering broken; this was
   a second, independent bug behind the same screenshot (once the terms
   row was no longer squeezed into a sliver, it -- and the Submit button
   below it -- were tall enough to spill past this box's old fixed
   550px height onto the backdrop). */
.modal-content{ margin: 10% auto; width: 425px; height: auto; min-height: 550px; }

/* ---- Entry 55: the general Email Signup popup (#emailSignupModal)'s
   content is much shorter than the 3 "consult request" popups the base
   550px min-height above was sized for, leaving ~94px of dead blank
   space below its Sign Up button. Scoped to just this one modal by id,
   so every other popup reusing .modal-content keeps the base 550px.
   Shaunie: "reduce the excess blank space at the bottom by about 50%"
   -- 550px -> 500px cuts that blank space to ~44px (~53% less). ---- */
#emailSignupModal .modal-content{ min-height: 500px; }


    /* ---- inner pages (desktop) ---- */
    .inner-page #hero{ height: 270px; }
    .inner-page #hero h1{ text-align: center; margin-top: 100px; font-size: 2.5em; }
    .inner-page #content{ margin-bottom: 30px; }

    /* ---- Services pages: pill-style toggle switcher between service
       categories -- replaces the old .serviceBox grid-of-colored-boxes.
       Matches 9o9Designs' own Service Catalog toggle (navy track, pill-
       shaped active state), but uses 9o9Brand's own orange brand color
       (#ffb900, same as .inner-page .btn's fill) for the active pill
       instead of 9o9Designs' gold, and real <a> links -- this switches
       between real pages, not a same-page filter, so a real link is both
       more accessible and SEO-friendly than 9o9Designs' onclick <button>
       approach, while looking identical. */
    .serviceToggle{
        display: flex;
        align-items: center;
        width: fit-content;
        margin: 20px auto;
        background: #0e0f28;
        border-radius: 999px;
        padding: 4px;
        box-shadow: 0 2px 6px rgba(0,0,0,.2);
    }
    .serviceToggle a{
        display: flex;
        align-items: center;
        justify-content: center;
        min-width: 150px;
        height: 38px;
        padding: 0 20px;
        border-radius: 999px;
        background: transparent;
        color: #fff;
        font-weight: 600;
        text-transform: uppercase;
        letter-spacing: .03em;
        text-decoration: none;
        text-align: center;
        white-space: nowrap;
        box-sizing: border-box;
        transition: background-color .25s ease, color .25s ease;
    }
    .serviceToggle a:hover{ background: rgba(255,255,255,.15); }
    .serviceToggle a.active{ background: #ffb900; color: #0e0f28; }
    .serviceToggle a.active:hover{ background: #ffb900; opacity: .9; }

    /* 2026-11-08: service-page detail cards, added per Shaunie's request to
       match the .productcard-grid/.productcard layout used on 9o9Designs.com's
       service pages -- same component pattern, using 9o9Brand's own orange
       (#ffb900) / dark navy (#0e0f28) brand colors instead of 9o9Designs' gold. */
    .inner-page .productcard-grid{
        display: flex;
        flex-wrap: wrap;
        gap: 16px;
        margin-top: 16px;
    }
    .inner-page .productcard{
        display: block;
        flex: 1 1 calc(50% - 8px);
        margin: 0;
        text-decoration: none;
        cursor: pointer;
    }
    .inner-page .productcard-visual{
        display: block;
        height: 100%;
        border: 2px solid #f1f1f1;
        border-radius: 5px;
        padding: 16px;
        text-align: left;
        box-sizing: border-box;
        transition: border-color .15s ease;
    }
    .inner-page .productcard:hover .productcard-visual{ border-color: #ffb900; }
    .inner-page .productcard-name{
        display: block;
        font-weight: bold;
        color: #0e0f28;
    }
    .inner-page .productcard-desc{
        display: block;
        font-size: .9em;
        color: #555;
        margin-top: 8px;
    }
    .inner-page .productcard-cta{
        display: block;
        font-size: .9em;
        font-weight: bold;
        color: #ffb900;
        margin-top: 12px;
    }
    .inner-page .productcard:hover .productcard-cta{ color: #30c0cf; }
}

/* ========================================================
   MOBILE (<= 768px)
   ======================================================== */

@media (max-width: 768px){

    .hideonmobile{ display: none; }

    /* cookie disclaimer -- stack and center on mobile, full-width button */
    .cookie-banner{
        left: 10px;
        right: 10px;
        flex-direction: column;
        align-items: stretch;
        text-align: center;
    }
    .cookie-banner p{ flex: none; }
    .cookie-banner-actions button{ width: 100%; }

    /* collapse the Contact Us / Do Not Sell forms' 2-column rows back to
       stacked fields -- no room for two columns at this width. */
    #contactUsForm .consult-form-row{ display: block; }
    #donotsellForm .consult-form-row{ display: block; clear: both; }
    #jobApplicationForm .consult-form-row{ display: block; }

    /* the application form's fields were running edge-to-edge on mobile
       (inheriting #content's own near-0 side padding) -- inset the whole
       form by the same 15px already used for the service toggle pills. */
    #jobApplicationForm{ padding: 0 15px; box-sizing: border-box; }

    /* Round 3 item 29: the Contact page's own consultation-style form had
       the same edge-to-edge problem as #jobApplicationForm above (same
       root cause -- #content's near-0 side padding on mobile), but here
       Shaunie asked specifically for a narrower, visually centered form
       rather than just inset content, so this uses width+margin (same
       15px-per-side inset as #jobApplicationForm, for consistency) instead
       of padding. */
    #contactUsForm{ width: calc(100% - 30px); margin: 0 auto; box-sizing: border-box; }

    /* single column on mobile -- sized a bit in from the card list's own
       edges (which otherwise run flush with the page) and centered, so
       the cards don't look glued to the screen edge. */
    .job-cards{ justify-content: center; }
    .job-card{ flex: 0 1 calc(100% - 30px); max-width: 400px; margin: 0 auto; }

    h1{ font-size: 2.6em; text-transform: uppercase; }

    header{ height: auto; min-height: 50px; padding: 8px 15px; box-sizing: border-box; }
    .header-row{ width: 100%; }

    #logo{ margin-left: 16px; }
    /* Round 4 (Shaunie's note): mobile logo read too large -- was 117px,
       cut by about 20% (117 * .8 = 93.6, rounded to 94px). */
    #logo img{ width: 94px; height: auto; }

    /* Round 2: moved the hamburger back up to share the logo's line
       (order 2, floated to the end of that line via margin-left:auto --
       .header-row's own align-items:center keeps it vertically centered
       against the logo with no extra margin-top needed). Nav drops to
       order 3 so it wraps onto its own full-width line below, now that
       it's alone there -- sized to its own content and centered as a
       tight group instead of stretched edge-to-edge with space-around. */
    #nav{ order: 3; flex: 0 1 100%; min-width: 0; margin-top: 10px; text-transform: uppercase; }
    #nav ul{ width: 100%; justify-content: center; }
    #nav ul li{ flex: 0 1 auto; text-align: center; font-size: .95em; padding: 10px 0; }
    #nav ul li a{ padding: 5px 12px; }

    #hamburgerBtn{
        order: 2;
        margin-left: auto;
        margin-right: 16px;
        width: 44px;
        height: 44px;
        background: url('/assets/images/hamburger.webp') no-repeat center / 32px 32px;
    }
    #hamburgerBtn:hover{ background: url('/assets/images/hamburger-teal.webp') no-repeat center / 32px 32px; }

    .side-menu{ width: 100%; height: 100%; left: -100%; margin-left: 0; }
    .side-menu h2{ width: 70%; padding-left: 15px; }
    .side-menu h3{ margin-left: 15px; font-size: 1.3em; }
    .side-menu h4{ margin-left: 40px; font-size: 1.1em; }
    /* Round 3 item 28: each section's <ul> (Company/Apps/Websites/Domains)
       stacked its <li> items in a single column on mobile, making the
       pop-out menu run much taller than it needs to -- wrap each list into
       2 columns instead, same multi-column technique already used for the
       Observed Holidays list (see .two-cols further up). break-inside:avoid
       on the <li> keeps a single item from splitting across the column
       gap; the existing right-side padding on .side-menu's own column
       (col-md-12, unaffected here) plus this column-gap keeps both
       columns off the menu's edges. */
    .side-menu ul{ margin-left: 15px; margin-right: 15px; columns: 2; column-gap: 16px; }
    .side-menu li{ break-inside: avoid; }
    .side-menu li a{ height: 28px; padding-left: 0; }

    #hero{ height: auto; padding: 30px 15px 20px; box-sizing: border-box; }
    /* Mobile hero background swap: Shaunie asked for this section's
       background to use a new image (hero-mobile-bg.webp) instead of the
       shared hero1bg.webp above -- her own words were that this image's
       "seams are better" (it fades to white at its own edges rather than
       needing a hard crop), so sizing it at 100% width / auto height (vs.
       hero1bg's fixed "100% 1000px") lets it scale naturally and always
       fade out before it would otherwise need cropping, at any width in
       this breakpoint. Desktop is untouched -- this only overrides body's
       shared background rule (near the top of this file) inside this
       mobile media query.
       Round 4 follow-up: this image's own fade wasn't actually complete
       everywhere -- a pixel-level check of the bottom-right corner (the
       "blunt cut" Shaunie circled, which also shows up wherever body's
       background runs out on a short page, e.g. the inner-page banner)
       found residual blue tint (RGB roughly 20-30 points off pure white)
       still present right at the image's own last row, instead of fully
       resolving to #fff. Edited the image file itself -- not a CSS
       overlay, since the fade needs to track the image's own bottom edge
       at whatever height "100% auto" renders it, which varies by
       viewport width -- blending a smooth alpha ramp to pure white over
       its bottom ~18% (most of the artwork is untouched; only that
       trailing band changes), so this image now reaches true #fff before
       its own canvas ends everywhere, not just in spots. */
    body{ background: url('/assets/images/hero-mobile-bg.webp') no-repeat center top / 100% auto; }
    /* Round 2 item 23: slide 0's actual content (headline + button) only
       needs ~264px of this box, leaving ~36px of dead space below the
       button before #image starts. Slide 1 (headline + paragraph +
       button) is the taller of the two and needs ~286px, so that's the
       real floor -- 294px keeps a small safety buffer for it while still
       trimming slide 0's excess space some; the rest of the gap
       reduction comes from the #image-slide1/#image-slide2 crop below.
       Round 3 item 25 correction (2026-11-10): that "~286px" estimate for
       slide 1 (the ADA/WCAG slide) was never actually measured -- a real
       Playwright measurement found its headline+paragraph+button content
       needs ~336px, 42px MORE than this 294px box. Since .hero-slide is
       position:absolute with no overflow:hidden on this box, that excess
       wasn't clipped -- it silently overflowed down into #image's own
       area, where #image's later-painted background covered it up. The
       practical effect: slide 1's "Learn More" button was completely
       invisible (though still present and clickable) on mobile, hidden
       behind the top of the TruAccess artwork. Fixing that and shrinking
       slide 0's dead space at the same time need two different box
       heights, so this is no longer one static value: showSlide() in the
       script below now also stamps #tagline with data-active-slide, and
       the two heights are set per slide -- 270px for slide 0 (cuts its
       gap from ~36px to ~10px) and 345px for slide 1 (small buffer over
       its real ~336px need, instead of overflowing it). transition here
       smooths the height change alongside the existing opacity crossfade. */
    #hero #tagline{ text-align: center; min-height: 270px; transition: min-height .4s ease; }
    /* Round 3 item 1 (second-pass feedback): 345px was sized to the exact
       measured minimum slide 2's real content needs (~336px) plus a 9px
       buffer -- enough to avoid the overflow bug this fix originally
       solved, but not enough to read as an intentional gap before the
       image below. +24px gave the button real breathing room above the
       image, same margin-reads-as-extra-min-height technique as before
       (only slide 2 changes; slide 1's own, already-minimal 270px is
       untouched).
       Third pass (live-site feedback, 2026-11-10): 369px overshot -- a
       live measurement on the actual staging site (not the harness) found
       slide 2's real content now needs ~286px (not 336px; this slide's own
       copy/wrapping has since settled shorter) and the resulting gap below
       the button measured 83px, read by Shaunie as too much margin. Cut
       that gap by about half (~42px) per her request: 286 + 42 = 328px.
       Fourth pass (same day): still a bit much -- cut the ~42px gap by
       about another 25% (down to ~32px): 286 + 32 = ~317px. */
    #hero #tagline[data-active-slide="1"]{ min-height: 317px; }
    #hero #tagline h1{ margin-top: 0; }
    /* "-A Lane Of Our Own.(TM)-" inherited the same font-size as the rest of
       the headline (no mobile-specific override existed), so it wrapped onto
       a second line. Match the smaller size already used for this same span
       at wider widths so it reliably fits on one line here too. */
    #hero #tagline span{ font-size: .5em; }
    /* Slide 0's Learn More button sits in a <p class="text-end"> (a Bootstrap
       utility that right-aligns it); every other button on this page relies
       on #tagline's own text-align:center above. Override just this one
       paragraph's alignment on mobile so the button centers like the rest. */
    /* Bootstrap's own .text-end utility sets text-align:right !important,
       so overriding it here needs !important too, not just higher specificity. */
    #hero #tagline p.text-end{ text-align: center !important; }
    #hero #image{ height: 340px; }
    /* slide1.webp/slide2.webp (the device-mockup collage) both have a wide
       band of plain white space above the actual monitor/tablet/phone
       artwork -- background-size:cover matches this 340px box's height
       exactly with no slack, so that white band renders as real blank
       space before the mockups appear (on top of the gap above from
       #tagline). Scaling up a bit further than cover's own match and
       shifting the image up crops that band away instead, so the mockups
       start right near the top of the box. Checked every column (not
       just center) of both images at their native 854x617 so the
       tablet/phone corners never get clipped by this.
       Round 3 item 25: slide1.webp's own artwork (tablet + monitor + phone
       spread across ~680px of its 854px-wide canvas) is much wider,
       relative to its canvas, than slide2.webp's (phone + tablet, ~430px
       of the same 854px canvas) -- the shared 401px-tall crop above scales
       slide1's wide spread past this box's ~360px width, clipping the
       tablet on the left and the phone on the right. Split the two apart:
       slide1 now scales down further (300px tall instead of 401px) so the
       full tablet-monitor-phone spread fits inside the box with a small
       margin on both sides. Since this is a fixed px height while the box
       width scales with viewport, checked the whole mobile range with
       Playwright rather than assuming one width generalizes: clean with
       small even margins from ~360px up through the 768px top of this
       media query; at the legacy 320px width (first-gen iPhone SE, long
       obsolete) the phone on the right still clips by a few px -- far
       better than the original overflow, not pixel-perfect there, and a
       percentage-based size (which would scale with box width) was tried
       first but made it worse higher up, since the box's height here
       stays a flat 340px while a percentage width keeps growing with the
       viewport, overflowing vertically well before 768px. Slide2 keeps
       the original values, which already fit it fine at every width
       checked. */
    #image-slide1{ background-size: auto 300px; background-position: 35% -31px; }
    #image-slide2{ background-size: auto 401px; background-position: center -24px; }

    /* Round 2 item 17: was 60px -- see the matching #blog h2 margin-top
       comment further down for why this got smaller.
       Round 3 item 27 (third pass): now that the Websites section paints
       its own background all the way to #content's own bottom edge (see
       #image3section, mobile-only, further down), this padding-bottom was
       the last bit of plain, unpainted white space left between the two
       sections -- a visible gap/seam right where neither #image3section's
       nor #blog's background reaches. Zeroed it so #content's box ends
       exactly where #image3section's background ends, and #blog's own
       background (which already starts flush against #content, no margin
       between the two) picks up with nothing uncovered in between. */
    #content{ padding-bottom: 0px; }
    #content p{ width: 100%; margin-right: 0; }
    .float-right{ margin-left: 0; }
    #content img{ width: 280px; height: 280px; max-width: 90vw; }
    /* Round 2 items 15/20 (Domains/Apps) + 14 (Websites): each product image
       (#image1/#image2/#image3) was sitting flush against the row's own left
       edge on mobile with no inset, unlike its text column (#image1text/
       #image3text already carry padding-left:29px -- see the comment above
       #image1text further up). Correction (2026-11-09): the visible photo
       here is actually this div's own CSS background-image (content-image1/
       2/3.webp, set further up in this file) -- the nested <img> tag only
       carries a near-blank 722-byte placeholder (contentbg.webp) used for
       alt text/layout, not the real photo. padding-left alone does NOT move
       a background-image: with the default background-origin:padding-box,
       background-position:0 0 (inherited from the base rule above) anchors
       the image to the padding box's own edge -- the same place as the
       border edge, since there's no border -- so it ignores padding-left
       entirely and stays flush regardless of this div's padding. The
       padding-left below still correctly shifts the invisible placeholder
       <img>, but that was never the visible fix; background-position here is
       the part that actually moves the photo. Confirmed with an isolated
       Playwright reproduction before and after adding it. */
    #content #image1, #content #image2, #content #image3{ background-size: 280px 280px; background-position: 29px 0; height: auto; padding-left: 29px; }
    #content #image2{ width: auto; }
    /* Apps (#image1text) and Websites (#image3text) already carry this same
       29px padding-left globally (see the comment above #image1text further
       up in this file); Domains (#image2text) was deliberately left alone
       on desktop, but on mobile its text was sitting flush at the row's own
       edge with no inset at all, unlike its siblings -- add the same 29px
       here so Domains' heading/paragraph lines up with Apps and Websites. */
    #content #image2text{ padding-left: 29px; }
    /* Round 2 item 14: Websites' paragraph kept the fixed 391px width from
       the desktop zigzag fix above (#image3text p{width:391px}) -- that rule
       out-specifies this file's own "#content p{width:100%}" mobile reset
       two lines up (two ids beats one), so on mobile the text stayed a fixed
       391px wide even inside a much narrower ~350px column, overflowing off
       the right edge of the screen instead of wrapping to fit. Go fluid again
       here (same specificity, later in the file, so this wins the tie) and
       add a right inset to match the left one, so the Websites text block
       gets real breathing room on both sides instead of running to the edge.
       Round 6 follow-up: the desktop rule above switched from a flat
       `width:391px` to `width:100% + max-width:405px` (see its own comment),
       and max-width is a separate property from width -- it isn't replaced
       just because this rule below wins the `width` tie, so without an
       explicit override here it would carry through the cascade and clip
       this paragraph back down to 405px on the wider end of this very
       breakpoint (e.g. a 768px-wide tablet, where the real available column
       is a good deal wider than that). Cancel it explicitly so mobile stays
       genuinely full-width exactly as this fix originally intended. */
    #content #image3text p{ width: 100%; max-width: none; }
    #content #image3text{ padding-right: 29px; }
    /* Round 3 item 27 (second pass): replaces the previous blog-side fade
       (see #blog's own comment, reverted) with a background on the
       Websites section itself, so the two sections read as the same wave
       artwork meeting itself at the seam instead of needing a fade to hide
       a mismatch. websitesbg.webp is blogbg.webp's own artwork, mirrored,
       with a real alpha fade baked into its upper-right corner (no CSS
       gradient needed on top of it) so it eases in from the Domains
       section above and is fully solid by the time it reaches #blog's own
       (also solid-at-the-top) artwork below. display:block overrides this
       wrapper's desktop display:contents (see the base #image3section
       rule) only here, so it's a real box with a real background exclusively
       on mobile; its children (the spacer columns, #image3, #image3text)
       still just stack top to bottom same as always. */
    #image3section{
        display: block;
        background-image: url('/assets/images/websitesbg.webp');
        background-repeat: no-repeat;
        background-position: center bottom;
        background-size: cover;
    }
    #image2, #image2text{ order: 0; }

    /* stack the founder photo above the bio, centered, on mobile.
       .founder-photo's base flex-basis (220px) was sized for the desktop
       220px circle; the mobile photo shrinks to 160px (below) but the
       flex item itself stayed 220px tall, leaving an accidental 60px dead
       strip under the photo before the 30px row gap even started -- so
       the real gap on mobile was ~90px, not the intended 30px. Cut the
       item down to match the photo it now holds (removing that 60px
       accident), and set the gap itself to 45px -- about half of the
       original ~90px of blank space the photo and bio actually sat at. */
    .founder-section{ flex-direction: column; align-items: center; text-align: center; gap: 45px; }
    .founder-photo{ flex-basis: 160px; }
    .founder-bio{ text-align: left; min-width: 0; }
    .inner-page #content .founder-photo img{ width: 160px; height: 160px; }

    #blog{ height: auto; min-height: 480px; padding-bottom: 20px; }
    /* Round 2 item 17: was 40px -- raised by the same 45px #content's mobile
       padding-bottom (above) was cut by, keeping the heading the same
       distance below the button while #blog's box/background moves up to
       cover the former gap/seam. */
    #blog h2{ margin-top: 85px; }
    #blog .blog-posts{ padding: 0 20px; margin-top: 15px; }
    #blog .excerpt{ margin-top: 10px; }
    #blog button{ padding: 4px 8px; }
    /* Round 2 item 21: the mobile-only "View All Blogs" row (.hideondesktop
       -- the other two blog cards' own Read More buttons are hidden on
       mobile, see blogpost2/blogpost3's .hideonmobile class) sat only 10px
       below the visible post's Read More button, with no spacing of its
       own beyond the <br><br> already in the markup -- close enough that
       the two buttons read as one group instead of two separate actions. */
    #blog .row.hideondesktop{ margin-top: 30px; }

    /* The newsletter section on inner pages (footer.php) is given an extra
       '.parallax' class the home page's own copy of this same section
       doesn't have, which layers a fixed background-attachment under the
       same newsletterbg.webp image (the id-level rule above still wins on
       which image and position/size are used -- only background-attachment
       comes from .parallax). "Fixed" backgrounds are unreliable on mobile
       browsers' compositors and are why this background wasn't reliably
       showing up as the page scrolled on inner pages; forcing it back to a
       normal scrolling background here (mobile only -- desktop keeps its
       parallax effect) makes inner pages render the same base-of-section
       image the home page already shows. */
    #ctanewsletter.parallax{ background-attachment: scroll; }
    /* Round 3 item 26: on inner pages, the real end-to-end gap between a
       page's own content (e.g. the Contact form's Submit button) and the
       "Subscribe To Our Newsletter" heading below it measured ~155px at
       mobile widths -- not just this section's 30px top padding plus
       .inner-page #content's 75px bottom padding (shared rule, not
       mobile-specific -- see that rule's own comment): the rest comes
       from this section's own box ending flush against #ctanewsletter's
       box (no extra margin there) plus the heading's own sitewide
       "h2{margin-top:30px}" rule, which isn't touched here. Measured with
       a Playwright harness built from the real Contact page markup
       (/tmp/newsletter_harness/, not a placeholder), confirming the
       105px hand-estimate from the first pass of this fix undercounted
       the true gap and only cut it by ~35%. Trimmed further here (top
       padding down to 8px) and on #content's mobile padding-bottom
       (down to 20px, see that rule below) to land at a measured ~78px
       -- a ~50% cut from the real ~155px baseline, matching Shaunie's
       ask. Desktop is untouched either way. */
    #ctanewsletter{ padding: 8px 15px 40px; }
    #ctanewsletter .newsletter-box{ padding: 4px 20px 30px; }
    /* desktop narrows and centers these (Shaunie's request) -- reverted to full width/left-
       aligned here so the fields stay usable on small screens */
    #ctanewsletter .form-col{ width: 100%; margin: 0; }
    #ctanewsletter .form-col input[type="text"],
    #ctanewsletter .form-col input[type="email"]{ width: 100%; }
    #ctanewsletter .check-box{ width: 100%; margin-left: 0; margin-right: 0; }

    .footer-links{ grid-template-columns: repeat(2, 1fr); padding: 0 15px; }
    footer #copyright{ margin-top: 20px; }

    button{ padding: 7px 17px; }
    .modal-content{ margin: 20% auto; width: 90%; max-width: 385px; height: auto; min-height: 420px; }

    /* ---- inner pages (mobile) ---- */
    /* Banner title/tagline used to be centered with a hardcoded h1
       margin-top guess, which only lined up for a single short line and
       drifted off-center whenever a title wrapped or a page had a longer
       tagline underneath it. Switched the row itself to a flex column
       that centers its content both ways, so this holds regardless of
       how much text is in the banner. */
    .inner-page #hero{ width: 105%; height: 170px; float: left; display: flex; flex-direction: column; flex-wrap: nowrap; align-items: center; justify-content: center; }
    .inner-page #hero h1{ margin-top: 0; font-size: 2em; text-align: center; }
    .inner-page #breadcrumbs{ float: left; width: 105%; padding-left: 8px; }
    .inner-page #content{ width: 105%; float: left; padding-left: 5px; }
    /* Round 3 item 26: see the matching comment on the mobile #ctanewsletter
       rule above -- this 75px (set higher up, shared with desktop) is part
       of the real ~155px gap before the newsletter section; cut to 20px
       here (paired with that rule's 8px) to land the measured real gap at
       ~78px, about half of ~155px. */
    .inner-page #content{ padding-bottom: 20px; }

    /* mobile: 'Branding & Marketing' is longer than any of 9o9Designs'
       own 4 toggle labels (Branding/Domains/Marketing/Websites), so a
       fixed min-width per item (as 9o9Designs uses) risks overflowing a
       narrow viewport. Instead each pill takes an equal 1/4 share of the
       full-width track and wraps its own text to 2 lines if needed,
       rather than growing the row wider than the screen. */
    .serviceToggle{
        display: flex;
        align-items: stretch;
        width: calc(100% - 30px);
        margin: 15px 15px;
        background: #0e0f28;
        border-radius: 999px;
        padding: 3px;
        box-shadow: 0 2px 6px rgba(0,0,0,.2);
    }
    .serviceToggle a{
        display: flex;
        align-items: center;
        justify-content: center;
        flex: 1;
        min-width: 0;
        padding: 6px 3px;
        border-radius: 999px;
        background: transparent;
        color: #fff;
        font-size: .72em;
        font-weight: 600;
        text-transform: uppercase;
        letter-spacing: .02em;
        text-decoration: none;
        text-align: center;
        white-space: normal;
        line-height: 1.2;
        box-sizing: border-box;
        transition: background-color .25s ease, color .25s ease;
    }
    .serviceToggle a:hover{ background: rgba(255,255,255,.15); }
    .serviceToggle a.active{ background: #ffb900; color: #0e0f28; }
    .serviceToggle a.active:hover{ background: #ffb900; opacity: .9; }

    /* 2026-11-08: see the desktop block comment above -- cards stack
       1-per-row on mobile instead of 2-per-row. */
    .inner-page .productcard-grid{
        display: flex;
        flex-wrap: wrap;
        gap: 16px;
        margin-top: 16px;
    }
    .inner-page .productcard{
        display: block;
        flex: 1 1 100%;
        margin: 0;
        text-decoration: none;
        cursor: pointer;
    }
    .inner-page .productcard-visual{
        display: block;
        height: 100%;
        border: 2px solid #f1f1f1;
        border-radius: 5px;
        padding: 16px;
        text-align: left;
        box-sizing: border-box;
        transition: border-color .15s ease;
    }
    .inner-page .productcard:hover .productcard-visual{ border-color: #ffb900; }
    .inner-page .productcard-name{
        display: block;
        font-weight: bold;
        color: #0e0f28;
    }
    .inner-page .productcard-desc{
        display: block;
        font-size: .9em;
        color: #555;
        margin-top: 8px;
    }
    .inner-page .productcard-cta{
        display: block;
        font-size: .9em;
        font-weight: bold;
        color: #ffb900;
        margin-top: 12px;
    }
    .inner-page .productcard:hover .productcard-cta{ color: #30c0cf; }

    /* 2026-11-09: mobile (stacked) version of the blog-page layout
       above -- image above text, full width, matching the site's
       other desktop-row/mobile-stack components
       (#jobApplicationForm .consult-form-row and friends). */
    .blogpost{
        display: flex;
        flex-direction: column;
        align-items: stretch;
        gap: 16px;
    }
    .blogpost-featured{
        margin-bottom: 32px;
        padding-bottom: 32px;
    }
    .blogpost-list .blogpost{
        padding: 24px 0;
    }
    .blogpost-image,
    .blogpost-list .blogpost-image{
        flex: 0 0 auto;
        width: 100%;
    }
    .inner-page #content .blogpost-image img{
        display: block;
        width: 100%;
        max-width: 100%;
        height: auto;
        aspect-ratio: 4 / 3;
        object-fit: cover;
        border-radius: 6px;
        background-color: #f2f2f2;
    }
    .blogpost-featured .blogpost-title{
        font-size: 1.4em;
    }
}
