feat: identity redesign v2 — editorial layout, Zinc palette, FAQ page, SEO fixes

.claude/CLAUDE.md

@@ -102,11 +102,11 @@ CI clones `rtk/main` at `./rtk-repo`. Once `feat-refac-doc` is merged into main,
 
 | Page type | Nav component |
 |-----------|--------------|
-| Landing (`/`) | `src/components/landing/Nav.astro` |
-| Product pages (`/vox/`, `/icm/`) | `src/components/landing/ProductNav.astro` |
+| Landing (`/`) | `src/components/global/SiteHeader.astro` (variant="landing") |
+| Product pages (`/vox/`, `/icm/`) | `src/components/global/SiteHeader.astro` (variant="product") |
 | Docs (`/guide/**`) | `src/components/global/Header.astro` (via Starlight override) |
 
-Anchor links in Nav.astro use absolute paths (`/#problem`, `/#install`) so they work from any page.
+Anchor links in SiteHeader.astro use absolute paths (`/#problem`, `/#install`) so they work from any page.
 
 ## Workflow before push to main
 

.claude/commands/review.md

@@ -0,0 +1,125 @@
+---
+name: review
+description: Code review for rtk-ldp — Astro components, CSS token compliance, design system rules, generated file integrity, and build correctness.
+---
+
+Run a thorough code review of the current changes against the RTK Landing standards.
+
+## Step 1 — Diff scope
+
+```bash
+git diff --name-only HEAD
+git diff HEAD --stat
+```
+
+If no staged/unstaged changes, review the last commit: `git diff HEAD~1 HEAD --name-only`.
+
+## Step 2 — Read changed files
+
+Read every changed `.astro`, `.css`, `.ts`, `.mjs`, `.md` file in full before issuing findings.
+
+## Step 3 — Checklist
+
+### 3a. CSS Token Compliance (BLOCKER)
+
+Check every changed `.astro` and `.css` file:
+
+- No inline `color:`, `background:`, `border-color:`, `fill:` using raw hex values that match a design token
+- Tokens to enforce (source: `src/styles/global.css`):
+  - `--bg: #060b18`, `--bg-alt: #0c1225`, `--bg-card: #0f1629`
+  - `--text: #e2e8f0`, `--text-muted: #8294ab`, `--text-dim: #64748b`
+  - `--accent: #00e599`, `--cyan: #38bdf8`, `--violet: #a78bfa`, `--border: #1a2344`
+- No duplicate token declarations in `src/styles/landing.css` (tokens defined in `global.css` must not be redefined)
+- New color values must be added to `global.css` as tokens, not hardcoded
+
+### 3b. Generated Files Integrity
+
+These files must NEVER be manually edited:
+
+| File                              | Generator                        |
+| --------------------------------- | -------------------------------- |
+| `src/content/docs/guide/**`       | `scripts/prepare-docs.mjs`       |
+| `src/data/docs-search-entries.ts` | `scripts/build-search-index.mjs` |
+| `src/data/docs-anchor-map.json`   | `scripts/prepare-docs.mjs`       |
+
+Flag any manual edits to these files.
+
+### 3c. Source of Truth Compliance
+
+| Data             | Must be in                                                         | Never in                  |
+| ---------------- | ------------------------------------------------------------------ | ------------------------- |
+| RSS entries      | `src/data/rss-entries.ts`                                          | `src/pages/rss.xml.ts`    |
+| Nav anchor links | `Nav.astro` / `ProductNav.astro` with absolute paths (`/#section`) | Inline in pages           |
+| Docs content     | `rtk/docs/guide/` (external repo)                                  | `src/content/docs/guide/` |
+
+### 3d. Astro Component Quality
+
+- No inline styles for anything covered by a design token
+- Component props typed with TypeScript interfaces
+- No `<style>` blocks using magic hex values
+- Imports cleaned up (no unused imports)
+- No hardcoded URLs in components — use constants or config
+
+### 3e. Nav Architecture
+
+- Landing (`/`): uses `Nav.astro`
+- Product pages (`/vox/`, `/icm/`): uses `ProductNav.astro`
+- Docs (`/guide/**`): uses `Header.astro` via Starlight override
+
+Anchor links must use absolute paths (`/#problem`, not `#problem`) so they work from any page.
+
+### 3f. Build Readiness
+
+If `.astro`, `.ts`, or `.mjs` files were changed, run:
+
+```bash
+rtk pnpm build 2>&1 | head -80
+```
+
+Report: pass/fail, error count, pages generated.
+
+## Step 4 — Report
+
+```
+## Code Review — RTK Landing
+
+**Files reviewed**: [list]
+**Date**: [YYYY-MM-DD]
+
+### Blockers
+[BLOCKER] file.astro:42 — Hardcoded `#00e599` — use `var(--accent)` instead
+...
+
+### Warnings
+[WARN] landing.css:15 — Duplicates `--text` token already in global.css
+...
+
+### Token violations
+| File | Line | Value | Token to use |
+|------|------|-------|-------------|
+| ... | ... | ... | ... |
+
+### Generated files
+[OK] No manual edits detected
+or
+[BLOCKER] src/content/docs/guide/commands.md edited manually — regenerate via prepare-docs.mjs
+
+### Build
+[PASS] 12 pages generated, 0 errors
+or
+[FAIL] Build errors: [list]
+
+### Summary
+- Blockers: X
+- Warnings: Y
+- Token violations: Z
+- Build: PASS/FAIL
+
+Verdict: [READY / NEEDS FIXES]
+```
+
+## Post-review
+
+If blockers exist: do not proceed until fixed.
+If only warnings: propose fixes and let user decide.
+If READY: suggest `pnpm build && git push` (never run push automatically).

.claude/palettes.md

@@ -0,0 +1,94 @@
+# RTK Landing — Palette options (Identity Redesign v2)
+
+Évaluées en Phase 0.5 via `/preview`. Switcher interactif A/B/C/D.
+Accent vert `#00e599` commun à toutes les options.
+
+---
+
+## Option B — Slate dark
+
+Garde la teinte bleue-navale du site actuel, beaucoup plus sombre.
+Continuité visuelle avec l'existant, identité "nuit profonde".
+
+```css
+--bg:            #0a0f1c;
+--bg-alt:        #0d1322;
+--bg-card:       #0f1625;
+--bg-card-hover: #141c30;
+--bg-elevated:   #1a2540;
+--bg-glass:      rgba(10, 15, 28, 0.82);
+--border:        #1e2a45;
+--border-light:  #243258;
+--text:          #e8edf5;
+--text-bright:   #f8fafc;
+--text-muted:    #94a3b8;
+--text-dim:      #64748b;
+```
+
+Contraste vérifié sur `#0a0f1c` :
+- `--text #e8edf5` → ~14.5:1 AAA
+- `--text-muted #94a3b8` → ~6.2:1 AAA
+- `--text-dim #64748b` → ~4.6:1 AA ✓
+
+---
+
+## ✅ Option A — Zinc (neutre pur) (RETENUE)
+
+Référence LeanCTX / Linear / Vercel. Sans teinte de couleur.
+
+```css
+--bg:            #09090b;
+--bg-alt:        #0c0c0e;
+--bg-card:       #121215;
+--bg-card-hover: #18181b;
+--bg-elevated:   #1f1f23;
+--bg-glass:      rgba(9, 9, 11, 0.80);
+--border:        #1f1f23;
+--border-light:  #2a2a2e;
+--text:          #f4f4f5;
+--text-bright:   #ffffff;
+--text-muted:    #a1a1aa;
+--text-dim:      #86868e;
+```
+
+---
+
+## Option C — GitHub Dark
+
+Palette exacte de GitHub. Familière pour les devs, légère teinte bleu-grise.
+
+```css
+--bg:            #0d1117;
+--bg-alt:        #10161e;
+--bg-card:       #161b22;
+--bg-card-hover: #1c2330;
+--bg-elevated:   #21262d;
+--bg-glass:      rgba(13, 17, 23, 0.82);
+--border:        #30363d;
+--border-light:  #3d444d;
+--text:          #e6edf3;
+--text-bright:   #f0f6fc;
+--text-muted:    #8b949e;
+--text-dim:      #6e7681;
+```
+
+---
+
+## Option D — Stone (warm)
+
+Légère teinte warm/brun. Distinctif, mais moins standard dans l'écosystème dev.
+
+```css
+--bg:            #0c0a09;
+--bg-alt:        #110f0d;
+--bg-card:       #1c1917;
+--bg-card-hover: #231f1d;
+--bg-elevated:   #292524;
+--bg-glass:      rgba(12, 10, 9, 0.82);
+--border:        #292524;
+--border-light:  #3d3734;
+--text:          #f5f0ee;
+--text-bright:   #fafaf9;
+--text-muted:    #a8a29e;
+--text-dim:      #78716c;
+```