Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Being implemented by multiple platforms:
More soon...
Introduction
Standard.site began as a conversation between developers building long-form platforms on AT Protocol. Each had working implementations. Each had defined similar schemas. Coordination was the missing piece.
Four principles guide the project:
01.
Unified discovery
One schema for indexers and tooling. No more supporting multiple lexicons.
02.
Content portability
Users move between hosts without losing their content, audience, or metadata.
03.
Community ownership
Maintained by the developers building on it. No single platform cont…
Standard.site provides shared lexicons for long-form publishing on AT Protocol. Making content easier to discover, index, and move across the ATmosphere.
Being implemented by multiple platforms:
More soon...
Introduction
Standard.site began as a conversation between developers building long-form platforms on AT Protocol. Each had working implementations. Each had defined similar schemas. Coordination was the missing piece.
Four principles guide the project:
01.
Unified discovery
One schema for indexers and tooling. No more supporting multiple lexicons.
02.
Content portability
Users move between hosts without losing their content, audience, or metadata.
03.
Community ownership
Maintained by the developers building on it. No single platform controls the standard.
04.
Minimal governance
Coordination through adoption, not committee. The schema evolves as the ecosystem does.
The lexicons focus on metadata: what a publication is, what a document contains, and where it lives. Content format is left to each platform. The standard grows when builders identify shared needs and align on solutions.
Definitions
We currently define two main lexicons that cover the core building blocks of long-form platforms: where content lives, and what it contains.
Modularity. Each lexicon is independent. Use them together for full support, or implement only what your platform requires.
Verification
Standard.site records point to domain names and webpages. We need a way for those to point back to the record. This is done through a .well-known route for publications and HTML link tags for documents.
Publication
Add a /.well-known/site.standard.publication endpoint to your domain. The response should be the AT-URI of your publication record.
This confirms the link between the publication and the domain.
Request
https://standard.site/.well-known/site.standard.publication
Response
at://did:plc:abc123/site.standard.publication/rkey
Document
Add a <link> tag in the document’s <head> that references its AT-URI.
HTML
<link rel="site.standard.document" href="at://did:plc:xyz789/site.standard.document/rkey">
Questions
Common questions about Standard.site, its governance, and implementation. If something is missing ask us on Bluesky.