. */ .kx .hero.scrim-hard .hero-media::after{ background:linear-gradient(180deg,rgba(10,14,20,.74) 0%,rgba(10,14,20,.52) 38%,rgba(10,14,20,.93) 100%)} /* --------------------------------------------------------------------------- v1.0.4 — THE ORPHANED THEME BUILDER FOOTER The global footer is a Divi Theme Builder layout authored against the Divi Tradesman child theme. Tradesman supplied the dark section background; the layout only ever set the TEXT colour, which is #fff. Tradesman was deactivated on 2026-08-02 when soar-gc went in. The background went with it. The white text did not. Result: 24 modules -- phone number, opening hours, Popular Services, Useful Links, newsletter, copyright -- rendering white on the white , invisible on every page on the site. This is not a SOAR page problem; it sits below .kx and applies sitewide. Restore the surface the layout was designed on, in SOAR tokens, so the existing white text works as authored and the footer reads as part of the dark pages above it. INTERIM. The real fix is a soar-gc footer in the repo, built when the service pages land -- the footer's Popular Services links point at legacy Tradesman URLs and have to be rewritten at that point anyway. */ .et-l--footer{background:var(--bg2,#0d1420);border-top:1px solid rgba(255,255,255,.10)} .et-l--footer a{color:var(--brass-2,#e4c98f)} .et-l--footer a:hover{color:#fff} .et-l--footer .et_pb_divider_internal{border-top-color:rgba(255,255,255,.14)} /* The is #fff. Any gap the footer does not cover -- overscroll, or a page shorter than the viewport -- flashes white under a dark page. */ body{background:var(--bg,#0a0e14)} /* --------------------------------------------------------------------------- v1.0.6 — PRIMARY ACTION SURFACES GO BRASS `.btn-gold` was painted with the blue primary ramp (--pri / --pri-2), so the class named "gold" rendered blue on every page. Charles ruled brass on 2026-08-03. Brass is already the accent throughout -- eyebrows, italic emphasis, stat units, tick marks -- so the CTA was the one element fighting the palette. Every surface that reads as "this is the action" moves together. Blue stays as the secondary/link ramp; it is more legible than brass for body links on a dark ground. Re-brand by editing _tokens.css alone. */ .kx .btn-gold{background:linear-gradient(135deg,var(--brass-2),var(--brass));color:#1a1206} .kx .btn-gold:hover{box-shadow:0 20px 44px -14px rgba(201,168,106,.45)} .kx .btn-solid{background:var(--brass);color:#1a1206} .kx .btn-solid:hover{background:var(--brass-2)} .kx .opt.sel{background:linear-gradient(135deg,var(--brass-2),var(--brass));color:#1a1206;border-color:transparent} .kx .tier .badge{background:linear-gradient(135deg,var(--brass-2),var(--brass));color:#1a1206} .kx .ba .la{background:linear-gradient(135deg,var(--brass-2),var(--brass));color:#1a1206} .kx .calc-result::before{background:radial-gradient(circle,rgba(201,168,106,.16),transparent 70%)} /* --------------------------------------------------------------------------- v1.0.7 — THE DIVI THEME BUILDER BODY LAYOUT FOR SINGLE PROJECTS Moving SOAR project pages onto the `project` post type inherited a Divi Theme Builder BODY layout from the Tradesman build. It wraps the post content in three sections, all with a white background: 0 post content -> holds .kx, which paints itself, so it read fine 1 comments -> "0 Comments / SUBMIT A COMMENT", 54px padding, white 2 fullwidth portfolio -> a related-projects slider, white, 9 thumbnails Sections 1 and 2 appeared below every project as a white band. Neither was wanted: - COMMENTS. Closed sitewide on the original build; new project posts default to open. Also killed in PHP (see functions.php) so the markup never renders -- this rule only handles posts created before that guard existed. - RELATED PROJECTS. It currently pulls the 12 legacy Tradesman projects that are queued for harvest-then-redirect, and stamps each with its WordPress publish date -- so a job built in 2018 is labelled with today's date. That is worse than showing nothing. Hidden until a SOAR "More projects" module is built off project_category during the /projects/ index work. Every Theme Builder section on a single project is forced to the SOAR ground so no white can show through a section we have not accounted for. */ .single-project .et-l--body .et_pb_section{background-color:var(--bg) !important} .single-project .et_pb_comments_module, .single-project .et_pb_fullwidth_portfolio{display:none !important} .single-project .et-l--body .et_pb_section_1_tb_body, .single-project .et-l--body .et_pb_section_2_tb_body{padding:0 !important;min-height:0 !important} /* --------------------------------------------------------------------------- v1.0.8 — #main-content IS WHITE Divi paints #main-content white. On a Page template the SOAR body filled it edge to edge so nothing showed. The project template adds ~55px of trailing space below the post content, and that strip rendered as a white band between the CTA and the footer -- visible on every project page. Fixed at the container rather than by padding-hacking the sections, so it also covers any future template that leaves slack below .kx. The :has() rule makes it automatic for the service pages when they land; the .single-project rule is the explicit fallback. */ .single-project #main-content{background-color:var(--bg)} #main-content:has(.kx){background-color:var(--bg)} /* v1.0.9 — belt and braces: literal fallbacks so these survive even if the token scope is ever narrowed again. See _tokens.css for why. */ .single-project #main-content{background-color:var(--bg,#0a0e14) !important} #main-content:has(.kx){background-color:var(--bg,#0a0e14) !important}

(the theme supplies exactly one), so the hero headline ships as