/* * Academy chrome: the header navbar shadow and the footer. * * Unit C owns this file. Contract Addendum 10. * * WHAT THIS IS, AND WHY IT IS NOT A PORTED FILE * --------------------------------------------- * 8882 styles the academy chrome with two Oxygen-compiled stylesheets, * `uploads/oxygen/css/post-91.css` (the academy header, 9 rules) and * `uploads/oxygen/css/post-53.css` (the global footer, 81 rules). Those are ONE PAGE'S COMPILED * LAYOUT, named for Oxygen post IDs that mean nothing on this site and unregenerable here because * Oxygen is not installed. Shipping them would rebuild the platform dependency Addendum 7 existed * to remove, only on Oxygen instead of Divi, and it would fail the owner's "edits via Claude" * requirement, which needs readable CSS. * * So the rules that apply to OUR DOM are extracted here, readable, with the origin of each block * named. This is the opposite of the tailwind.css decision and deliberately so: Tailwind is a * design system, stable and regenerable and addressed by class name, so it ships byte-identical. * * WHAT WAS LEFT OUT, and why * -------------------------- * - `oxygen/css/global-settings.css` (25 KB). NOT PORTED. It carries the system-ui heading * override the owner overruled in Addendum 4. Porting it would silently undo the Jost ruling. * - The 28 `.breakdance .bde-wp-menu-53-{7,10,13,17}` rules from post-53.css. Every one either * sets `--menu-hide-on-desktop`, which only Oxygen's awesome-menu.css reads, or an active-link * colour already covered by the `.footer .breakdance-menu` rules below. Nothing in our DOM * carries a `bde-wp-menu-53-N` class. * - post-91.css's `.ph-fill` rule. No academy template uses a fill glyph, and the matching font * is not shipped, so keeping the rule would only produce fallback boxes if someone used one. * - The Oxygen per-template sheets (`post-124.css`, `post-124-defaults.css`, `post-121.css` and * friends) belong to Units D and E, under this same extract-do-not-port rule. * * The `content: "\eNNN"` escapes below are safe HERE because this is a file on disk. Never move * them into post meta or Divi custom CSS: WordPress strips backslashes on save and the glyphs * would silently become empty. * * Load order matters. This sheet must come after tailwind.css, whose preflight resets lists, * margins and heading sizes that the footer rules then set. */ /* --------------------------------------------------------------------------- * Custom properties. From 8882 `oxygen/css/variables.css`, which declares 180. * Only the four the extracted rules actually reference are taken; a whole design * token set that nothing reads is dead weight and invites accidental coupling. * * Three still hold 8882's values verbatim. `--lm-midnight-blue` no longer does: * it carries an owner ruling and the reason is recorded on the declaration itself. * --------------------------------------------------------------------------- */ :root { /* * OWNER RULING, contract Addendum 28 item 1 (Unit V1, 2026-08-25): the footer must be * darker, from our own palette. 8882's value was #121948. GATE 1 EXCEPTION: the footer * is deliberately darker than the reference. Do not "restore fidelity" here. * * Derived, not invented, and not a Tailwind utility: per Addendum 21 our tailwind.css is * a purged copy of 8882's build, so `.bg-gray-900` is the only darker option that exists * in it and it is a neutral, not our navy. Instead every channel of #121948 is scaled by * 0.70: * * #121948 rgb(18, 25, 72) -> #0D1232 rgb(13, 18, 50) * * A uniform channel scale is close to a pure lightness change, but 8-bit ROUNDING moves hue and * saturation slightly. Measured on the SHIPPED colour: hsl(231.892, 58.730%, 12.16%). * CORRECTED 2026-08-25: the original comment claimed "preserved to the decimal" at * hsl(232.2, 60.0%), computed on the UNROUNDED rgb(12.6, 17.5, 50.4), not on the * #0D1232 actually shipped. The colour is right; the claimed precision was not. So the * brand hue is untouched and only the value moves. The name still fits: it is the same * midnight blue, later at night. * * Contrast against the footer's own foregrounds all IMPROVES (measured, Unit V1): * #fff headings / hover / social glyphs 16.69:1 -> 18.27:1 * rgba(255,255,255,.85) body and links 12.26:1 -> 13.27:1 * (figures re-measured on the shipped #0D1232; the originals were computed on the * unrounded value and read ~0.05 high. Every ratio still improves.) * rgba(255,255,255,.78) brand paragraph 10.48:1 -> 11.28:1 * rgba(255,255,255,.70) bottom row and links 8.66:1 -> 9.24:1 * #fff glyph on the .social pill 13.41:1 -> 15.00:1 * The only figure that falls is the hairline `.bottom` border at * rgba(255,255,255,.15), 1.57:1 -> 1.54:1. It is decoration, not information, and 3:1 * was already out of reach at 8882's value. * * `.footer { background }` below is the ONLY consumer of this property on the whole site * (verified by grep across wp-content), so nothing else moves when it changes. */ --lm-midnight-blue: #0D1232; --duration-fast: 120ms; --ease-standard: cubic-bezier(0.2, 0, 0.2, 1); --leading-normal: 1.5; } /* --------------------------------------------------------------------------- * Header. From post-91.css. * * The navbar itself is Tailwind, in templates/header.php, so only the scrolled * state needs CSS. Unit C's academy-behaviour.js adds `scrolling` to #navbar * above scrollY 50, matching 8882 exactly, and this is what that class paints. * --------------------------------------------------------------------------- */ #navbar.scrolling { -webkit-backdrop-filter: blur(16px); backdrop-filter: blur(16px); background: rgba(255, 255, 255, 0.7); box-shadow: 0 0 0 1px rgba(17, 24, 39, 0.10), 0 2px 2px -1px rgba(17, 24, 39, 0.05), 0 4px 4px -2px rgba(17, 24, 39, 0.05), 0 8px 8px -4px rgba(17, 24, 39, 0.05), 0 0 3px 7px rgba(17, 24, 39, 0.05); } /* --------------------------------------------------------------------------- * Phosphor icon font. From post-91.css. * * The faces are declared in uploads/credit-applications/fonts.css, which is * first-party and ported whole (Addendum 10). These are the rules that turn an *