# Content source — copy reference PHP arrays of all the textual content authored in the Strategy & Content PDF (`Asterion-VR_Refonte-2026_Strategie-et-Contenu.pdf`, sections D.1 to D.29). Each file holds the EN copy for one site section, keyed by page slug. These files are **not** loaded at runtime. They serve two purposes: 1. **Reference while building Bricks pages** — open the file matching the page you're editing and copy/paste the EN copy into the Bricks elements (Heading, Basic Text, Button…). 2. **Source for programmatic generation** — once a Bricks archetype template is built and validated visually, a one-shot script can iterate over the data here, clone the template, swap in each variant's strings, and create the WP page programmatically. This avoids rebuilding the same layout 4–6 times for similar pages (e.g. the 4 industry detail pages). ## Files | File | Pages covered | |---|---| | `solutions-data.php` | `/solutions/my-proserve/`, `/solutions/proserve-flex/`, `/solutions/proserve-academy/`, `/solutions/customization/` | | `industries-data.php` | `/industries/police/`, `/industries/special-forces/`, `/industries/military/`, `/industries/firefighters/` | | `technology-data.php` | 6 technology pillars under `/technology/` | | `editorial-data.php` | Why Asterion, About, Customers hub, Trust, Partners | | `forms-data.php` | Conversion forms (Demo, T&E Kit, Quote, Contact) | ## Schema Every entry follows roughly the same shape : ```php 'slug-of-page' => [ 'eyebrow' => 'Small overline above the H1', 'title' => 'Short page title', 'tagline' => 'Hero H1', 'meta_title' => 'For + OpenGraph', 'meta_description' => 'For <head> meta description', 'hero_lead' => 'Long sub-headline under the H1', 'ctas' => [['label' => '...', 'href' => '/...', 'variant' => 'primary'], …], 'sections' => [ ['type' => 'prose' , 'eyebrow' => '…', 'title' => '…', 'body' => '…'], ['type' => 'cards' , 'eyebrow' => '…', 'title' => '…', 'items' => [['title' => '…', 'body' => '…'], …]], ['type' => 'list' , 'eyebrow' => '…', 'title' => '…', 'items' => ['line 1', 'line 2', …]], ['type' => 'cta' , 'eyebrow' => '…', 'title' => '…', 'body' => '…', 'ctas' => […]], ], ], ``` `forms-data.php` deviates slightly — see its inline header comment. ## Why we keep these in PHP arrays (vs JSON / YAML / Markdown) - They were extracted programmatically from the PDF and were already used by the previous PHP-rendering approach. Keeping the format means zero re-extraction work. - A future PHP migration script will `include $file_path` and use the returned array directly — no parsing layer required. - For the human reading them while building in Bricks, plain PHP arrays are perfectly readable. ## French translations These files are **EN only**. The FR translations will live inside WordPress, written by the linguist via WPML's Translation Editor against each Bricks-edited page.