) a 24px top margin — a visible
* gap between the header's 3px orange border-bottom and the hero banner.
* PHP-templated inner pages (services, kitchen-products, why-us, …) have
* NO .wp-site-blocks wrapper, so their hero sits flush. Measured gaps:
* promotion 24px; finance 48px (finance also carries an empty leading
* — wpautop wrapped a marker comment — pushing the hero to the 2nd
* flow child inside .wp-block-post-content for a second 24px margin).
*
* Fix: pull and the in-content hero flush to the top, matching the
* PHP pages (header→hero gap → 0). Specificity beats the :where()-scoped
* core rules, so no !important needed. Only the block-template pages emit
* these selectors, so PHP-templated pages are untouched.
* ============================================================ */
.wp-site-blocks > main { margin-block-start: 0; }
.wp-block-post-content > .kub-inner__hero { margin-block-start: 0; }
/* ============================================================
* task 86d35nhr9 — Clean 404 "Page Not Found" template.
*
* Before: no templates/404.html existed, so block-theme template
* hierarchy fell back to templates/index.html — the blog/posts
* query — and 404 responses dumped the full post listing under a
* "Blog" hero. Reporter saw page content where there should have
* been a plain Not Found message.
*
* After: templates/404.html renders the canonical .kub-inner__hero
* with title "Page Not Found", then a single short message + Home
* button inside .kub-container. Styling below.
* ============================================================ */
.kub-404__body { padding: 56px 0 80px; }
.kub-404__body .kub-container { max-width: 780px; }
.kub-404__lead { font-size: clamp(16px, 1.4vw, 18px); line-height: 1.6; margin: 0 0 24px; color: #333; }
.kub-404__cta { margin: 0; }
.kub-404__cta .kub-btn { display: inline-block; }
@media (max-width: 781px) {
.kub-404__body { padding: 40px 0 56px; }
}
/* ============================================================
* task 86d35qc47 — /promotion/ form to match /contact-us/ form
*
* The /contact-us/ form gets its orange uppercase submit button from
* the body.page-id-87 Run 27c rules (~L194–206) which use !important to
* beat Gravity Forms' inline Orbital theme (--gf-color-primary:#204ce5
* blue, applied via #gform_wrapper_1[data-form-index="0"].gform-theme).
* The portable .kub-contact-form_wrapper .gform_button rule (~L3582) has
* no !important, so on /promotion/ the GF inline style wins and the
* button renders blue + sentence-case "Send my details".
*
* Fix: replicate Run 27c's button + hover rules scoped to
* .kub-contact-form_wrapper so they apply on ANY page using the
* portable wrapper (promotion, future pages, …) — idempotent on
* contact-us where it produces the same orange CTA.
* ============================================================ */
.kub-contact-form_wrapper input[type=submit].gform_button,
.kub-contact-form_wrapper input[type=submit].button,
.kub-contact-form_wrapper button[type=submit] {
background: #ff7545 !important;
color: #fff !important;
border: none !important;
border-radius: 4px !important;
padding: 14px 32px !important;
font-size: 14px !important;
font-weight: 700 !important;
letter-spacing: 1px !important;
text-transform: uppercase !important;
cursor: pointer;
transition: background .2s;
}
.kub-contact-form_wrapper input[type=submit].gform_button:hover,
.kub-contact-form_wrapper input[type=submit].button:hover,
.kub-contact-form_wrapper button[type=submit]:hover {
background: #e8633b !important;
}