atmosphere.community#

The community hub for the AT Protocol ecosystem. Aggregates blog posts from Offprint, upcoming events from Smoke Signal and community accounts, and links to regional AT Protocol communities and apps.

Built with Astro and deployed to Dokploy through Tangled and GitHub workflows.

Getting started#

npm install
npm run dev

The dev server starts at localhost:4321. The site fetches live data from ATProto at build time (blog posts, events), so you'll need internet access for a full build.

Commands#

Deployment#

The Tangled and GitHub workflows both verify and build the site, then trigger Dokploy. Deployment runs on:

• Push to main on Tangled or GitHub
• Manual runs of the GitHub workflow

OpenSocial join, leave, and sharing actions read secrets at runtime, so configure these variables in the deployed server environment, not only in the build workflows:

OPENSOCIAL_CIMD_PRIVATE_KEY_BASE64=
OPENSOCIAL_SIGNATURE_KEY_ID=
# Optional; generated by the key script and defaults to opensocial-cimd-1
OPENSOCIAL_CIMD_KID=
# Optional override; defaults to https://api.opensocial.community
OPENSOCIAL_SERVICE=

OPENSOCIAL_CIMD_PRIVATE_KEY_PEM is supported as an alternative to the base64 private key. Existing deployments may continue to use OPENSOCIAL_APP_ID as a legacy alias for OPENSOCIAL_SIGNATURE_KEY_ID.

Generate a signing key with:

node scripts/generate-cimd-key.mjs

Project structure#

src/
├── components/        # Astro components (Header, Footer, Hero, cards)
├── data/
│   ├── apps.yml       # App directory listings
│   └── communities.yml # Community group listings
├── layouts/
│   └── Base.astro     # Base HTML layout
├── lib/
│   ├── atproto.ts     # ATProto helpers (profile resolution)
│   ├── blog.ts        # Blog post fetcher (standard.site documents)
│   └── events.ts      # Event fetcher (community.lexicon.calendar.event)
├── pages/
│   ├── index.astro    # Homepage
│   ├── about.astro    # About page
│   ├── apps.astro     # App directory
│   ├── communities.astro # Community listings
│   └── events.astro   # Events listing
└── styles/
    └── global.css     # Design system (tokens, reset, utilities)

Adding content#

Add a new community#

Edit src/data/communities.yml and add an entry:

- name: ATProto My City
  handle: mycity.atproto.camp
  location: My City, ST
  description: My City ATProtocol user group
  bluesky: https://bsky.app/profile/mycity.atproto.camp

Community accounts are also used to fetch events — any community.lexicon.calendar.event records on the account's PDS will automatically appear on the Events page and homepage.

Data sources#

License#

MIT