Voice & identity
Writing about Sporting Scouter
Consistent naming builds trust. Inconsistent naming looks like two products merged in a hurry.
Product names
| Name | Use |
|---|---|
| Sporting Scouter | Company and platform. First mention per page; "Sporting Scouter" not "SportingScouter" in prose. |
| Verified Trust | Brand essence — messaging only. Never a CSS token, component name, or UI label. |
| Scouter Trust Layer | Product line name when needed; do not shorten to "trust layer" in customer-facing legal copy without context. |
Surfaces (domains)
Use domain names in technical docs; use plain language in customer copy.
www.sportingscouter.com— public marketing and event pagesbusiness.sportingscouter.com— organizer workspace (say "organizer dashboard" or "your Sporting Scouter account")feedback.sportingscouter.com— participant feedback (say "feedback form" or "post-race survey")
Capitalization
- Product name: Sporting Scouter (two words, capital S on both)
- UI labels: sentence case ("Create event", not "Create Event")
- Eyebrows and badges: uppercase via CSS
text-transform, never typed in source strings
Never invent in UI
Do not create UI components or tokens named TrustBadge, VerifiedPill, or --color-trust. Verification status uses existing status tokens plus icon and text — never colour alone. See design system handoff.
Sporting Scouter Content Style Guide
Component-enforceable rules: design-system.sportingscouter.com/voice. Tokens from
packages/config/tailwind/theme.css.