/*
Theme Name: Making Unlimited Memories
Description: WordPress theme for the M.U.M migration spike, built to match the live site (ebonyher-party-event-site repo) exactly. Real CSS/JS/images ported directly from the live site rather than approximated here — see functions.php and todo.md item 28.
Author: M.U.M
Version: 0.2.0
*/

/* This file exists only because WordPress requires a style.css header
   block to identify the theme. All real styling is the live site's own
   css/style.css and css/home.css, ported unmodified into
   assets/css/ and enqueued in functions.php. */

/* WooCommerce integration fix, not a design change: WooCommerce's own
   woocommerce-layout.css ships ".woocommerce img, .woocommerce-page img
   { height: auto; max-width: 100% }" (specificity 0,1,1), which beats the
   live site's single-class ".nav__logo-img"/".footer-logo-img" rules
   (0,1,0) on any page WordPress tags with a woocommerce/woocommerce-page
   body class (the shop archive) — rendering the logo at its native
   1005x682 instead of the intended 77px/44px. The live site has no such
   plugin CSS to fight, so this only needed fixing here. Scoped to
   .site-header/.site-footer to match specificity without touching the
   ported stylesheet itself. */
.site-header .nav__logo-img { height: 77px; width: auto; }
.site-footer .footer-logo-img { height: 44px; width: auto; }
@media (max-width: 782px) {
	.site-header .nav__logo-img { height: 62px; }
}

/* WooCommerce integration fix, not a design change: the "Booking and
   Rental Manager for WooCommerce" plugin (installed for this spike's
   capacity/availability proof-of-concept, see todo.md item 28) loads
   its own CSS site-wide, unscoped to its own admin/booking pages. That
   stylesheet (rbfw_style.css) ships "h1, h2, h3, h4, h5, h6 {
   font-family: inherit; ... }" with the exact same selector as the live
   site's own heading rule in css/style.css. Both have identical
   specificity, and the plugin's loads later in the page, so its
   `inherit` (pulling the body font, Poppins) wins the tie over the real
   site's Nunito display font on every heading, site-wide — confirmed by
   inspecting matched CSS rules directly in a browser, not assumed from
   a screenshot. The live site has no such plugin to conflict with, so
   this only needed fixing here. !important is the right tool against an
   unscoped third-party plugin reset like this, not a scoping trick. */
h1, h2, h3, h4, h5, h6 {
	font-family: var(--font-display) !important;
}

/* Landing-page template fix, not a design change: the live site's coral/
   italic heading emphasis (css/style.css's ".page-hero__title em" etc.)
   only applies to specific hero-heading classes that don't exist on this
   install's generic landing-page template. Editors here create emphasis
   the normal way, italicising a word in the block editor, which outputs a
   plain <em> with no matching selector, so it rendered as plain italic
   with no colour. Scoped to this template's own heading instead of
   touching the ported stylesheet. */
article > h1 em {
	font-style: italic;
	color: var(--coral);
}