Case Route – Production Validation
This controlled production case page validates the CFS technical solution route against the fixed Template_CasePage slot contract before final customer storytelling is attempted.
Why this case proof exists
The earlier matrix showed CFS Case reference drift. This page proves the current route can publish into the declared case shell, hero, facts grid, solution cards, proof block, risk grid, and final CTA without falling back to free-form body HTML.
Fixed Case Slot Contract
Hero and media stay paired
The case hero uses the declared copy and image slots, so customer context and rack visuals remain in the same controlled grid.
Metrics stay in facts grid
Route proof values are rendered through cfs-case-facts-grid instead of being scattered into raw paragraphs or tables.
CTA remains theme-owned
Both top and bottom actions reuse cfs-cta-btn, preserving the CFS site button styling while keeping the validation marker visible.
Proof is tied to a real front-end render
The page must pass WP readback and browser measurement. Required markers alone are not enough if the Avada shell creates a visible blank gap before the hero.
Known Failure Modes Covered
Legacy marker-only validation
Checking only cfs-case-shell and an image is insufficient. The grid must include the current BEM sections from Template_CasePage.slot_schema.json.
Header spacing drift
The browser gate measures the gap from the CFS navigation to the first case hero block so a class hit cannot hide a broken first viewport.
EN 
DE 
RU 
NL 
PT 
JA 
ES 
IT