Reframe atproto page and login around "the Atmosphere"
Two adjustments to the framing around the AT Protocol:
- `docs/understand/at-protocol.mdx`: renamed the lead section from
"Why We Built This" to "Why Opake was built on the Atmosphere".
The old phrasing implied we built the network; we built a cabinet
on top of it. The rewrite makes the distinction explicit — Opake
picked atproto because it already solves identity, portability, and
federation, and because being a resident of an ecosystem is a better
long-term bet than running our own silo. Shifted sharing language
from "AT Protocol network" to "the Atmosphere" to match the
user-facing terminology Bluesky and the wider community use.
- Login page: the old copy framed the identity as an "AT Protocol
handle", which is accurate but jargon-heavy. New framing:
Sign in with your Atmosphere account
Use the handle from any AT Protocol app — Bluesky, your own PDS,
or anywhere else in the Atmosphere. Opake doesn't issue its own
accounts.
The button is now "Continue to your PDS" (which is what actually
happens on submit), with a reassurance line underneath about the
redirect flow and the password never touching us.
Below the form, a new "What's an Atmosphere account?" explainer
lists concrete starting points so visitors without an atproto
handle have a path forward: Bluesky, Eurosky, pckt.blog, Tangled,
and Smoke Signal, each linked with a short description. A closing
note covers the self-hosted-PDS case so that lane isn't invisible.