Every SWR persona is rendered here in five different visual registers — from a print magazine spread to a terminal log feed to a brutalist file viewer. Pick the one that fits the room. The underlying JSON is identical.
Each register renders the same 8 personas (Indie musician, Beatmaker, DJ, Small label, Belgrade / Serbian artist, Podcaster, Sound designer, Music manager) in its own visual language. Different typography, palette, layout — same content.
Print-quarterly aesthetic. Paper-feel background, terracotta rules, byline intros. Use for blog posts, press kits, or when the audience expects reading.
Live status board. Each persona is a log entry with timestamp, pid, INFO/STARRED level. Use for dev-tool audiences, on socials where the terminal aesthetic fits.
Profile cards with round avatars, "Say hi →" CTAs, greetings in 5 languages. Use for the warmest possible landing, creator-friendly audiences, indie scenes.
KPI tiles, 7-column data table, zebra striping, sparkline. Use when you want the audience to feel they're looking at a real product, not a marketing page.
Raw file cards, ASCII art, hard black borders, no radius. Use when you want the audience to see source data, not a curated product. For the design-curious.
CDN-loaded Three.js renders a rotating icosahedron hero, 8 distinct wireframe primitives per persona, animated mesh dividers. Use for the technical-curious or to show that the engine itself is algorithmic.
The same 8 personas will be read by indie musicians, beatmakers, label managers, and sound designers — and they'll each show up in a different mood. The Editorial register reads like a magazine feature. The Dark register reads like a terminal. The Friendly register reads like a community board. The Dashboard reads like a SaaS admin. The Brutalist reads like a file dump.
Same content, different rooms. Pick the room that fits the audience you're talking to this week.
Source of truth: personas.json in the project root.
Tweak the 8 personas there and all 5 registers pick up the change on next
regen.