Design Context#

Users#

Community members, developers, and newcomers exploring the AT Protocol / Atmosphere ecosystem. They arrive from the newsletter, Bluesky, Discourse, or search. They want to see what's happening in the community — new blog posts, upcoming events, how to get involved, and where their local community meetup is. Context: casual browsing, often on mobile, during breaks or after seeing a link shared on Bluesky.

Brand Personality#

Warm, open, approachable. The Atmosphere community is grassroots, people-forward, decentralized. It should feel like a welcoming town square, not a corporate portal.

Aesthetic Direction#

"Horizon" — light theme with sky-blue palette and CSS cloud motifs. People-forward: author avatars and names are prominent on every content card. Clean card-based layouts with generous whitespace. serif display headings (Crimson Pro) paired with a geometric sans body (Plus Jakarta Sans). The cloud/atmosphere motif ties back to the "Atmosphere" name without being heavy-handed.

Anti-references: corporate SaaS dashboards, dark-mode-by-default dev tools, anything that feels like a generic startup landing page.

Design Principles#

1. People first — Every piece of content highlights who created it. Avatars, names, and community context are always visible.
2. Sky-light, not heavy — The light blue palette and cloud motifs create an airy, optimistic feel. Don't overload pages.
3. Structured simplicity — Card-based layout with clear hierarchy. Information-dense but not cluttered.
4. Real community, not marketing — Copy should be direct and helpful. No buzzwords, no hard sells.
5. Accessible by default — WCAG AA contrast, semantic HTML, keyboard-navigable, prefers-reduced-motion respected.