/*
 * v1 / v2 / v3 marketing content swap.
 *
 * Pages that carry multiple content variants wrap each block with the matching
 * data attribute:
 *
 *   <section data-content-v1>...</section>
 *   <section data-content-v2>...</section>
 *   <section data-content-v3>...</section>
 *
 * The active variant is selected per-deploy via PL_CONFIG.contentVersion
 * (set in scripts/deploy.sh from the `content_version` Terraform output).
 * An inline <script> at the top of each touched page's <head> sets
 * <html data-content-version="..."> before paint; the rules below hide the
 * inactive blocks.
 *
 *   v1 = pre-1.0 copy. v2 = post-1.0 feature copy (per-rig targets, Folder
 *   Export, CSV light_dir). v3 = analytics/archive-intelligence repositioning;
 *   same shipped feature set as v2, re-framed to outcomes + a Roadmap section.
 *
 * Variants are mutually exclusive — only the active one renders. So any block
 * that exists for one variant MUST have a sibling for every other variant a
 * page supports, or it vanishes when that variant is live. Genuinely neutral
 * sections (stats, FAQ, how-it-works) stay untagged and render under all.
 *
 * Pages with no variant markup are unaffected — the data attribute on <html>
 * is present but matches nothing.
 *
 * See photon-ledger-website/CLAUDE.md → Gotchas → "v1/v2/v3 content swap" for
 * the full design notes and SEO caveats.
 */

html[data-content-version="v1"] [data-content-v2],
html[data-content-version="v1"] [data-content-v3] { display: none !important; }
html[data-content-version="v2"] [data-content-v1],
html[data-content-version="v2"] [data-content-v3] { display: none !important; }
html[data-content-version="v3"] [data-content-v1],
html[data-content-version="v3"] [data-content-v2] { display: none !important; }

/*
 * Span helpers, to avoid duplicating identical copy across adjacent variants:
 *
 *   [data-content-legacy]  renders under v1 AND v2, hidden under v3. For
 *                          sections whose v1/v2 copy is identical — the
 *                          pre-repositioning block only needs a v3 sibling.
 *   [data-content-modern]  renders under v2 AND v3, hidden under v1. For the
 *                          post-1.0 feature copy (per-rig targets, Folder
 *                          Export, CSV light_dir) that v3 carries forward
 *                          unchanged — no separate v3 copy required.
 *
 * Pair a [data-content-legacy] block with a [data-content-v3] block; use
 * [data-content-modern] alone where v2 and v3 say the same thing.
 */
html[data-content-version="v3"] [data-content-legacy] { display: none !important; }
html[data-content-version="v1"] [data-content-modern] { display: none !important; }
