/* ============================================================================ * La2etlak — 6B PUBLIC CONTENT TEMPLATES (L4) * ============================================================================ * Ported by 6B-PUBLIC-CONTENT-TEMPLATES-STAGE-B-FINAL-PORT-001 from the locked * design package: * * docs/design/locked/2026-08-11/phase-6b-public-content-templates.html FINAL AUTHORITY * docs/design/locked/2026-08-11/phase-6a-component-system.html shared-component authority * docs/design/locked/2026-08-11/uploads/DESIGN_RULES.md rule layer * docs/design/locked/2026-08-11/FINAL_DESIGN_FOUNDATION.md token / role contract * * PORT, DO NOT INTERPRET. Every value below is copied from the locked board. * Do not "tidy", round or re-derive a number here. * * -- ONE OWNER, FIVE TEMPLATES ---------------------------------------------- * This is the ONE stylesheet of the 6B family. It serves all five L4 templates — * Editorial, Legal, Help, Contact and the public system response — because they * are one family that shares one vocabulary, exactly as the board's frame 01 * requires. There is no about.css / terms.css / faq.css / errors.css: six * competing design systems is the failure mode this file exists to prevent * (CLAUDE.md section 6). * * -- THE `pc-` PREFIX ------------------------------------------------------- * Every member carries a `pc-` prefix, mechanically applied to the board's own * class name, for the reason 5E carries `msg-`, 5F `ntf-`, 5G `dsh-`, 5H `set-`, * 5J `rcl-`, 5K `prf-`, 5L `sub-` and 4C `au-`: the board's short names already * have owners in the ported layer or in Bootstrap — `.bc` is Item Detail's, * `.fld` and `.stack` are far too generic to claim, `.alert` and `.status` would * collide with Bootstrap, `.code` and `.dr` are HTML-shaped names, and `.cats` * neighbours Search's filter vocabulary. Correspondence to the board is by * `data-parity` hook, never by name (PARITY_METHOD section 4). * * -- WHAT THIS FILE DELIBERATELY DOES NOT OWN ------------------------------- * `.btn` / `.b-pri` / `.b-sec` / `.b-quiet` / `.btn.sm`, the `.ico` mask family, * `.vh` and `.wrap` are foundation.css's. The Public Shell header, drawer and * footer are public-shell.css's. Nothing here re-declares one of them, and * nothing here re-points one to suit this board. * * THE BUTTON SIZE, RECORDED BECAUSE IT LOOKS LIKE A DIVERGENCE AND IS NOT. * The 6B board declares `.btn{min-height:44px;padding:0 16px;font:600 14px/1}` * — and so does the 6A component-system board, which is the button's OWN * subject board. foundation.css's `.btn` is 48px/15px, ported from * phase-3-homepage-redesign-v3.html and consumed by fourteen closed families. * Re-pointing it would move every one of them, which is the ruling `--warnBg` * got in 5E and the icons got in 5F. foundation's `.btn.sm` is * `min-height:44px; font-size:14px; padding:0 16px` — byte-identical to what * both 6-series boards declare — so this family consumes `.btn.sm` and the * shared owner is neither forked nor moved. Reconciling foundation with the 6A * component system is 6A's own Stage A -> C, not 6B's. * * -- ONE KNOWN DUPLICATION IN KIND, DELIBERATELY LEFT ----------------------- * `.pc-bc` restates a breadcrumb that item-detail.css also declares as `.bc`, * for exactly the reason 5C's `.rfbc` and 5D's `.claim-bc` do: the breadcrumb is * genuinely SHARED and its correct owner is the Public shell family (ledger * section 1 row 2), which is not ported yet. Moving it there now would mean * editing three closed families' stylesheets and re-verifying them for no visual * gain. The class is NAMED differently rather than re-declaring `.bc`, so the * ownership guard still sees exactly one owner per name. * * Its VALUES are the 6B board's own, not a copy of item-detail's, because this * board is this family's FINAL AUTHORITY and `.pc-bc` is a 6B-owned name that * moves no closed family. Three values differ from the 5B breadcrumb and the * board states all three outright: 12px rather than 13px, an explicit `--muted` * ink rather than the inherited body ink, and the 44px target floor on the link, * which item-detail.css does not declare and which both 6-series boards do. The * SEPARATOR is the shared `.ico i-chev-r` mask where the board draws a text * chevron — the ported layer has one icon construction and this family does not * fork it. Declared in tests/Design/maps/public-content.json. * ========================================================================== */ /* ============================================================================ 1 - THE CONTENT REGION AND THE BREADCRUMB ============================================================================ `.pc-page` is the board's own `.bd`: the content region's vertical rhythm. The board draws it as a 14px-inset grid with a 10px gap inside its simulated viewport; production keeps that VERTICAL rhythm and takes its HORIZONTAL gutter from the shared `.wrap` measure every ported page uses, because the page gutter is the Public Shell's settled property and not this family's. `.pc-bc` is the board's `.bc` — the breadcrumb ROW itself, which is why the class sits on the `
    ` and the `