/*
 * ProShield — CSS the hard load gets from PHP-printed <style> blocks, restated
 * as a lander sheet so a client-side navigation gets it too.
 *
 * A soft nav runs no PHP, and the router appends lander sheets to the END of
 * <body>, so neither of these survived it on their own:
 */

/*
 * 1) WPBakery's post-meta CSS (_wpb_shortcodes_default_css /
 *    _wpb_shortcodes_custom_css), printed inline by js_composer on a hard load
 *    only. Without it the FAQ band lost its navy background + padding and the
 *    warranty section's spacing shifted. The vc_custom_* class names are
 *    hard-coded in the JSX (sections/Faq.jsx, sections/YearWarranty.jsx), so
 *    the rules are copied verbatim from the post meta to match.
 */
.vc_do_custom_heading{margin-bottom:0.625rem;margin-top:0;}
.vc_custom_1689330467619{padding-top: 3rem !important;padding-bottom: 3rem !important;background-color: #002244 !important;}.vc_custom_1596013369071{margin-bottom: 0px !important;}

/*
 * 2) The [members_logos] shortcode's own <style> (inc/shortcodes-logos.php),
 *    injected with logosHtml. It is still in the DOM after a soft nav, but the
 *    router appends slick.css AFTER it, so slick's `.slick-list{margin:0}` won
 *    and the logo marquee shifted 15px. This sheet is ordered after slick.
 */
.slick-list {
    margin: 0 -15px;
}