Goal: customer and partner comms
Reader: External audiences receiving a brief, story or bulletin. Meta cluster: D — knowledge & expression Scenarios: 5 · Examples: 5
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| customer story | T2 | html-css | customer-story-card.md |
| education module | T2 | html-css | education-module-card.md |
| news bulletin | T2 | html-css | news-bulletin-card.md |
| partner brief | T2 | html-css | partner-brief-card.md |
| sales brief | T2 | html-css | sales-brief-card.md |
Reading order
Outbound documents need a headline, a proof point and a next step — in that order.
Engines in this goal
- HTML/CSS — system architecture diagrams, cards and page-level layouts (no fence)
Details, limits and anti-patterns: ../engines/html-css.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- Internal jargon or metric naming in an external brief
- A customer story with no quantified outcome