User Story
As a visitor evaluating ApexYard, I want a dedicated Architecture page on the marketing site that shows the 5-layer model (governance / capability / framework defaults / customisation / per-project data) + the optional split-portfolio sibling repo at a glance, so I can decide whether the framework's shape fits my needs without reading the README first.
Context
A keynote-shaped SVG of the architecture exists at /Users/ahmed/Desktop/D/apexyard-A-keynote.html (operator-authored). It captures the canonical mental model but uses an Apple/SF Pro aesthetic — pastel layer fills, drop shadows, rounded corners, SF Pro typeface — which clashes with the site's terminal-native brutalism (JetBrains Mono, warm cream paper, single accent red, sharp corners, no shadows).
The architecture page should preserve the diagram's information (5 layers, override arrows, sibling-repo coupling) but be recolored + restyled to feel native to the site.
Acceptance Criteria
Design Notes
- Information preservation over fidelity. The keynote's pastel layer encoding doesn't translate to the site's monochrome-cream aesthetic. Use tonal contrast (paper-2 vs paper-3) + border treatment (solid vs dashed) to retain the 5-layer grouping. Layer labels stay above each row to anchor the reader.
- Single accent. The site uses red (
#C8321A) as a stamp, not a fill. Use it only on the customisation-override arrows (their semantic IS the override). Everything else in cream + ink.
- No new typeface. JetBrains Mono only — including in the SVG (set
font-family="var(--mono)" via inline style or matching font-stack string).
- Footer hint. Tiny line at the bottom: "Right-click the diagram → Save Image As → drop into a slide" — same shareability the keynote offers.
- Out of scope for v1: dark-mode palette swap for the SVG itself (the site already does
prefers-color-scheme: dark for CSS; the SVG can stay light for v1 and inherit if values are CSS-driven). Capture as a follow-up.
Glossary
| Term |
Definition |
| 5-layer model |
Governance / Capability / Framework defaults / Customisation overlay / Per-project data — the canonical mental model for what lives where in an ApexYard fork |
| Customisation overlay |
custom-templates/, custom-skills/, custom-handbooks/ — adopter-authored files that override or layer onto framework defaults |
| Sibling private repo |
Optional split-portfolio v2 pattern — adopters on GitHub Free who don't want portfolio names on a public fork; resolved via .claude/project-config.json |
| Override arrow |
A pink/red-coloured arrow in the diagram pointing from the customisation layer to the framework default it replaces |
User Story
As a visitor evaluating ApexYard, I want a dedicated
Architecturepage on the marketing site that shows the 5-layer model (governance / capability / framework defaults / customisation / per-project data) + the optional split-portfolio sibling repo at a glance, so I can decide whether the framework's shape fits my needs without reading the README first.Context
A keynote-shaped SVG of the architecture exists at
/Users/ahmed/Desktop/D/apexyard-A-keynote.html(operator-authored). It captures the canonical mental model but uses an Apple/SF Pro aesthetic — pastel layer fills, drop shadows, rounded corners, SF Pro typeface — which clashes with the site's terminal-native brutalism (JetBrains Mono, warm cream paper, single accent red, sharp corners, no shadows).The architecture page should preserve the diagram's information (5 layers, override arrows, sibling-repo coupling) but be recolored + restyled to feel native to the site.
Acceptance Criteria
site/architecture.htmlwith the same titlebar + sticky-nav pattern assite/skills.html~/apexyard · architecture--paper-2/--paper-3cream tones (no pastels)--rule(ink) — solid for static layers, dashed for optional/sibling-repo--accent(warning-red) — preserves the "override" semantic--monols .claude/hooks/*.sh | wc -l)architectureadded to bothsite/index.htmlandsite/skills.htmltitlebars (next toskills)viewBox+ CSSmax-width: 100%; titlebar collapses links per existing@media (max-width: ...)patternskills.htmlshape)Design Notes
#C8321A) as a stamp, not a fill. Use it only on the customisation-override arrows (their semantic IS the override). Everything else in cream + ink.font-family="var(--mono)"via inline style or matching font-stack string).prefers-color-scheme: darkfor CSS; the SVG can stay light for v1 and inherit if values are CSS-driven). Capture as a follow-up.Glossary
custom-templates/,custom-skills/,custom-handbooks/— adopter-authored files that override or layer onto framework defaults.claude/project-config.json