/* =========================================================
   Divi conflict overrides
   =========================================================
   header.php/footer.php are fully replaced by this child theme, so
   Divi's own #main-header / #page-container / #main-content wrapper
   markup never prints on any of the six ported templates — there is
   no Divi nav, logo, or module CSS to fight on those pages. The Divi
   Builder remains fully available on *new* pages that use the default
   page.php (no "Dafcon:" template assigned).

   The items below are the conflicts that *can* still occur even
   without Divi's header/footer markup present:
   ========================================================= */

/* Divi can add 'et_fixed_nav' / header-height body classes via
   wp_body_class even though its header markup itself is never
   printed here — without this, that can leave unwanted top padding
   with nothing to offset it. Our header is position:fixed and every
   hero already reserves space for it via --header-h, so body padding
   should always be zero regardless of what Divi's body classes ask for. */
body {
  padding-top: 0;
}

/* Lock the root font size so this design's rem-based scale
   (--fs-14 … --fs-72 in dafcon-styles.css) is correct regardless of
   what base font-size Divi's own stylesheet sets on html. */
html {
  font-size: 16px;
}

/* Divi's global stylesheet sets its own font-family on body/button/
   input/select/textarea via the Customizer "Body Font" option. Our
   design relies on Sora for body copy and Fraunces for display type —
   reassert both explicitly rather than hoping load order wins, since
   a future Divi update could tip the specificity balance. */
body,
input,
textarea,
select,
button {
  font-family: var(--font-body);
}

h1, h2, h3, h4 {
  font-family: var(--font-display);
}

/* Divi's .et_pb_button / global button styles can bleed into generic
   <button> elements (e.g. the accordion trigger, filter buttons,
   nav-toggle) that intentionally have no Divi-style border/background
   in the original design. */
button {
  background: none;
  border: none;
  border-radius: 0;
  padding: 0;
}

/* …then let this design's own component classes re-apply their
   intentional padding/border/radius/background on top. */
.btn,
.filter-btn,
.accordion-trigger,
.nav-toggle,
.modal-close {
  padding: inherit;
}
.btn { padding: 14px 28px; }
.btn-sm { padding: 10px 20px; }
.filter-btn { padding: 10px 18px; }
.accordion-trigger { padding: 22px 26px; }

/* Divi's responsive container padding/max-width can leak onto our
   `.container` if a Divi update ever targets the bare class name
   instead of its own `.et_pb_row`/`.et_pb_section` wrappers. */
.container {
  max-width: var(--container);
  padding-inline: 24px;
}
