/* ══════════════════════════════════════════════════════════════════════════════════ FaultLine wiki shell — the SHARED chrome for both wiki properties. Consumed by: • saas/landing/wiki*.html (marketing origin — loads landing.css first) • saas/dashboard/help/* (app origin — loads its own inline token block) The point of this file is that those two surfaces stop looking like two products. It ships LAYOUT + STRUCTURE ONLY and deliberately declares NO new colours: every colour here is `var(--…)` resolved from whatever token block the host page already loaded (landing.css :root, or the help wiki's inline :root). Load it AFTER the host stylesheet: Because the tokens come from the host, light mode is free: landing.css already swaps the whole set under :root[data-theme="light"] and @media (prefers-color-scheme: light), and the help wiki swaps it under :root[data-theme="light"] + its data-accent variants. Nothing in this file hard-codes a hue that would survive that swap. No build step, no imports, no external fonts/images/requests. ══════════════════════════════════════════════════════════════════════════════════ */ /* ── token bridge ───────────────────────────────────────────────────────────── NOT a palette. Each alias forwards a token the host page defines; the literal after the comma is only a FALLBACK for hosts that never declared it, and every fallback is copied verbatim from landing.css's dark :root — so a page that is missing a token gets landing's value rather than an invented one. Concretely: landing.css defines all of these; the help wiki's inline block defines --bg/--bg-soft/--fg/--muted/--border/--accent/--accent-dim/--danger/ --warn/--mono but NOT --bg-card, --accent-glow, --accent-halo or --on-accent. Those four are the ones that actually fall back today. --wiki-sticky-top is the height of the host's sticky top bar. It defaults to 0 and wiki-shell.js overwrites it on with the measured header height, so the sticky sidebar and every scroll-margin below stay in step with whatever chrome the host page happens to have. A page may also set it by hand; the JS leaves any author-declared non-zero value alone. ───────────────────────────────────────────────────────────────────────────── */ :root { --wiki-card: var(--bg-card, var(--bg-soft, #141614)); --wiki-glow: var(--accent-glow, rgba(63,185,80,0.16)); --wiki-halo: var(--accent-halo, rgba(63,185,80,0.55)); --wiki-on-accent: var(--on-accent, #05160B); /* neutral wash for hover states — grey at low alpha reads correctly in BOTH themes, which a tinted background would not. Same trick the help wiki uses. */ --wiki-hover: rgba(127,127,127,.08); --wiki-hover-on: rgba(127,127,127,.14); --wiki-sticky-top: 0px; /* set by wiki-shell.js from the measured header */ --wiki-gap: 12px; /* breathing room under a sticky header when jumping */ --wiki-sidebar-w: 264px; --wiki-maxw: 1320px; } /* ══════════════════════════════════════════════════════════════════════════════ 1. SHELL — the two-column MediaWiki frame: persistent rail + article column. The table of contents is IN-ARTICLE (like MediaWiki), not a third rail, so both properties can use the identical grid regardless of viewport. ══════════════════════════════════════════════════════════════════════════════ */ .wiki-shell { display: grid; grid-template-columns: var(--wiki-sidebar-w) minmax(0, 1fr); align-items: start; gap: 0; max-width: var(--wiki-maxw); margin: 0 auto; } /* ══════════════════════════════════════════════════════════════════════════════ 2. SIDEBAR — the persistent left rail. Styled by ELEMENT rather than by bespoke child classes, so either property can write plain