Files
AsterionWP2026/wp-content/themes/asterion-bricks/README.md
j.foucher fba223004f chore: phase 1 reset — minimalist child theme + content-source extraction
Resets the child theme to its Bricks-first minimalist form (per RESTART-PLAN.md
phases 1a-1d) and extracts the textual copy into a runtime-independent
/content-source/ directory.

Child theme files removed
- header.php, footer.php, page.php, index.php, front-page.php
- template-parts/{solution,industry,conversion-form}.php
- templates/page-*.php (10 Custom Page Templates)
- inc/render-blocks.php, render-blocks-native.php, render-bricks.php
- inc/shortcodes.php, i18n.php, form-handler.php, seo.php
- assets/css/components.css, assets/js/main.js

Reasoning: Bricks Templates (Header / Footer / Single — Page) and Bricks-edited
pages now drive every screen. Anything emitted from the child theme would
fight Bricks' own rendering and waste CSS specificity battles.

Child theme now contains only
- style.css, functions.php (simplified to ~60 lines), theme.json
- inc/cpt.php (case_study + scenario + industry taxonomy)
- assets/css/tokens.css (untouched — design system source of truth)
- assets/css/utilities.css (trimmed to skip-link + sr-only + focus-visible
  + reduced motion — everything else handled by Bricks)
- assets/fonts/Inter-Variable*.woff2 (RGPD self-hosted)
- README.md spelling out the Bricks-first contract

Content moved to /content-source/
- solutions-data.php, industries-data.php, technology-data.php,
  editorial-data.php, forms-data.php — git mv preserves history
- README.md explaining their dual role: copy reference while building
  in Bricks, and source for programmatic page generation when we
  replicate an archetype across its variants.

Root README.md updated with the new repo layout + a pointer to
RESTART-PLAN.md and the archive/session-2-php-templates branch.

Memory file project_asterion_status.md updated for next-session resume.

What's preserved as before
- /BRIEF-Claude-Code.md, both PDFs, all .txt extracts
- /MISSING-ASSETS.md
- /ThirdParty/ (Bricks + WPML ZIPs, gitignored)
- LocalWP site at localhost:10004, Bricks v2.3.4 + WPML 4.9.3 active
- WPML EN/FR with directory URL strategy
- All Git history, both main and archive/session-2-php-templates branches

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-09 14:36:19 +02:00

85 lines
4.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Asterion Bricks — Child theme (minimalist, Bricks-first)
Custom WordPress child theme for **asterionvr.com**, built on top of [Bricks Builder](https://bricksbuilder.io). The whole site is rendered by Bricks Templates and Bricks-edited pages — this theme exists only to give Bricks a design system, GDPR-compliant fonts, and the project's Custom Post Types.
## What this theme does
- 🎨 Loads `assets/css/tokens.css` on the public frontend AND inside the Bricks builder iframe — so every `--color-*`, `--space-*`, `--font-*` variable defined there is available to Bricks elements via the **CSS Class** field or **Custom CSS** panel.
- 🔤 Self-hosts Inter Variable (latin subset) for RGPD compliance, with a `<link rel="preload">` injected on every page.
- 📰 Registers two Custom Post Types — `case_study` (slug `/customers/`) and `scenario` (slug `/scenarios/`) — plus the shared `industry` taxonomy.
- 📐 Adds three image sizes : `av-hero` (2400×1350), `av-card` (800×600), `av-thumb` (400×300).
- 🌐 Ships an `asterion-bricks` text domain for future i18n.
## What this theme does NOT do (intentionally)
- ❌ No `header.php` / `footer.php` / `page.php` / `front-page.php` / `index.php`. Bricks Templates (Header / Footer / Single — Page) drive every screen.
- ❌ No Custom Page Templates (`templates/page-*.php`). Pages render through their Bricks data (`_bricks_page_content_2` post meta).
- ❌ No PHP renderers, Gutenberg block helpers, shortcodes. Content lives in Bricks data and WPML translations.
If you find yourself adding any of the above back, stop and revisit `RESTART-PLAN.md` at the repo root — there are usually better Bricks-native alternatives.
## File map
```
asterion-bricks/
├── style.css # WP theme metadata only
├── functions.php # enqueue tokens, preload font, theme support, CPT include
├── theme.json # Gutenberg color/typo palette aligned with tokens.css
├── README.md # this file
├── inc/
│ └── cpt.php # case_study, scenario, industry taxonomy
└── assets/
├── css/
│ ├── tokens.css # design system source of truth (single file, big)
│ └── utilities.css # skip-link, sr-only, focus-visible, reduced motion
├── fonts/
│ ├── Inter-Variable.woff2
│ └── Inter-Variable-Italic.woff2
└── img/
```
Total : ~10 files, < 700 lines of code (with tokens.css being the lion's share).
## Where the content copy lives
The textual copy from the Strategy & Content PDF (page-by-page EN copy, deliverable D.1 to D.29) lives at the repo root in `/content-source/`. Those are PHP arrays keyed by page slug — they are not loaded at runtime. Their job is twofold:
- **Reference** when building a Bricks page : copy/paste the appropriate strings into the Bricks elements as you build.
- **Source for programmatic generation** when we replicate a Bricks-built archetype across its variants (e.g. the 4 industry detail pages, the 6 technology pillars).
## Activation
1. Install Bricks parent theme (`wp-content/themes/bricks/`) — the ZIP lives in `ThirdParty/`.
2. Install + activate WPML core (also in `ThirdParty/`).
3. WP Admin → Appearance → Themes → activate **Asterion Bricks**.
4. WP Admin → Bricks → Settings → check **Page** in « Builder access · Post types ».
## Tokens to know
The full design system lives in `assets/css/tokens.css`. The most-referenced tokens:
| Variable | Value |
|---|---|
| `--color-brand-navy` | `#0B1F3A` |
| `--color-brand-gold` | `#C9A45A` |
| `--color-text-primary` | `#0B1F3A` |
| `--font-display` | Inter Display fallback to Inter |
| `--font-body` | Inter |
| `--space-1..32` | 8-pt grid (4px → 128px) |
| `--container-max` | 1280px |
| `--ease-default` | `cubic-bezier(0.16, 1, 0.3, 1)` |
| `--shadow-sm`/`--shadow-md`/`--shadow-lg` | navy-tinted elevation |
Reference them inside Bricks via Custom CSS:
```css
%root% {
background: var(--color-brand-navy);
color: var(--color-text-on-dark);
padding-block: var(--space-20);
}
```
## License
GPL v2 or later, matching WordPress core.