/* JP-1068 - Shopsystem und Warenwirtschaft: body copy grey -> JTL Dark Blue
   DE: /de/themen/shopsystem/shop-und-wawi   |   EN twin: /en/topics/ecommerce/ecommerce-and-erp

   Bug: the prose under "Grenzen eines Shopsystems ohne Warenwirtschaft",
   "Zusammenspiel von Shopsystem und Warenwirtschaft in der Praxis" and
   "Fazit: Shopsystem und Warenwirtschaft als Effizienz-Duo" renders #333333
   instead of the approved body-copy colour #0b1b45.

   Root cause (measured, not inferred): the plain RTE paragraphs carry no colour
   of their own. CSS.getMatchedStylesForNode on both twins returns exactly two
   inherited colour declarations for them - `body { #585858 }` and, winning,
   `.page-template-product-landing main { color: #333333 }` from the widget
   plugin's global stylesheet
   (wpb-oop-widget-with-global/assets/scss/style.scss:134-142). Neither is
   !important. The redesign recoloured the widget WRAPPERS on this page
   (.product-management-section__text already measures navy) but never the bare
   RTE prose, which still falls through to the template default.

   Why this is not fixed at the plugin: that selector list covers EVERY
   product-landing / wawi-landing / connect / convention template page on the
   site. Flipping it to navy is a site-wide recolour whose blast radius reaches
   hundreds of pages that were never audited for it, so it needs its own ticket
   and a full per-element colour diff. This page is fixed page-scoped, the same
   way the identical symptom was already fixed on four sibling pages
   (jp-1000, jp-1006, jp-1010, jp-1037).

   No !important, on purpose. The colour above reaches <p> only by INHERITANCE,
   and any rule matching <p> directly beats an inherited value at any
   specificity - so this wins without it. Leaving !important off means an
   intentional white-on-dark paragraph rule elsewhere would still win, which is
   the safer failure mode. Verified: all 152 paragraphs land on #0b1b45 without
   it.

   `> section` is load-bearing, not cosmetic. footer.php emits three GLOBAL
   overlay widgets (DisruptorStandard, ExitIntentDisruptor, ExitIntentStandard)
   INSIDE main#content, before </main>. They render nothing on this page today
   (measured: main#content has no non-<section> children besides <style>, and 0
   paragraphs outside a direct-child <section>), but they wrap editor RTE
   content and are display:none at rest - so if an editor ever adds one, a
   plain `#content p` rule would silently repaint its copy in a state no
   page-at-rest screenshot can catch. Restricting to direct-child <section>
   excludes them structurally; the overlays are <div>, not <section>.

   Scope + safety, measured on both twins at 1440px:
   - Every <p> inside #content enumerated with its effective background:
     104 are already #0b1b45 (this rule is a no-op on them) and 48 are #333333,
     sitting on white or light-sand #eeeee7. Not one paragraph sits on a dark
     background, so navy stays readable everywhere on this page. Counts are
     identical on DE and EN.
   - <li> deliberately not included: the 5 bare <li> on this page (those with no
     <p> child) already measure #0b1b45, so adding them would only widen the
     blast radius for no gain. Every other list item wraps its text in a <p> and
     is covered.
   - Links are untouched, and not because they "are not <p>" - `.page-template-
     product-landing a { color:#333333 }` (style.scss:145-151) matches <a>
     directly, so links never inherit this and stay #333333 either way. The
     ticket asks only for body copy.

   WPML twin scope: 288435 is the DE original id; WPML stamps it on the EN twin
   too, so this ONE scope covers BOTH pages (verified on the rendered <body
   class>: DE carries page-id-288435, EN carries page-id-293999 page-id-288435).
   `#content` is a language-neutral structural hook present on both twins - the
   section anchors are NOT (DE #anchor-grenzen vs EN
   #anchor-limitations-of-a-store-system-without-erp), so they must not be used
   as the hook here. */

body.page-id-288435 #content > section p {
    color: #0b1b45;
}