/* Site-wide hyperlink color -- native Customizer CSS is used here (not
   WatuPRO's Additional CSS field) because WatuPRO only enqueues its CSS on
   pages that actually contain a [watupro N] quiz shortcode -- search
   results, archives, and the homepage never got it. This loads on every
   page unconditionally. */
body a { color: #23407A; }
body a:hover { color: #375FAE; }


/* Dark-background section override -- the theme's own "Section 2" style
   variation (navy background, white text via currentColor inheritance,
   used by the homepage's kept "Resources" block) had its link color
   silently overridden by the site-wide hyperlink-color rule above,
   making its post-title links nearly invisible against the navy
   background. Restore inheritance specifically within that section --
   higher specificity than the bare "body a" rule, so it wins there
   without touching the global fix anywhere else. */
.is-style-section-2 a { color: inherit; }


/* Content images must never exceed their column width, regardless of the
   image's own HTML width/height attributes. Confirmed live 2026-08-21
   (Task 27): the raw post_content Gutenberg image markup has no
   width/height at all -- Jetpack's own client-side lazy-image script
   injects width="1800" height="1200" (the full original upload size,
   not the rendered/CSS-constrained size) onto the <img> tag after the
   page loads, then rewrites its src to request that same oversized file
   from the Photon CDN. Core's own .wp-block-image img{max-width:100%}
   rule (confirmed present and its selector confirmed to match) still
   loses to that afterwards -- exact mechanism not fully pinned down
   (Jetpack's script is third-party/minified), but the practical, durable
   fix is a plain max-width:100% here with enough weight to win
   regardless of what gets added to the img tag later, by JS or by any
   future oversized upload. Small images were never visibly broken by
   this (their full size already fit the column), which is why it went
   unnoticed until a genuinely large upload (1800x1200) hit it. */
.entry-content img { max-width: 100% !important; height: auto !important; }