forked from
standard.site/standard.site
Standard.site landing page built in Next.js
1---
2title: Introduction
3description: A brief introduction to Standard.site lexicons, what they are, and how they're used.
4date: 2026-02-10
5atUri: "at://did:plc:re3ebnp5v7ffagz6rb6xfei4/site.standard.document/3mek5jhntva2i"
6ogImage: opengraph-image-docs-introduction-v2.png
7---
8
9import { StandardSite } from '@/app/components/docs'
10
11# Introduction
12
13<StandardSite /> lexicons bring long-form writing into the social web by linking blog posts and articles to the AT Protocol. This integration helps make published work easier to share and find, while ensuring authors maintain ownership of their writing in the form of records stored on their Personal Data Server (PDS).
14
15## What is Standard.site?
16
17Our lexicons are built with discovery and connectivity in mind. <StandardSite /> lexicons bridge the gap between writers and the communities they intend to reach.
18
19We have two main lexicons that are used to create and manage publications and written documents. In addition to these base lexicons, we maintain a handful of supporting lexicons for social features and utility.
20
21## Core Lexicons
22
23### Publications
24
25The [`site.standard.publication`](/docs/lexicons/publication) lexicon is a representation of a collection of documents published to the web. It includes important information about a publication including its location on the web, theming information, user preferences, and more.
26
27### Documents
28
29The [`site.standard.document`](/docs/lexicons/document) lexicon provides metadata for individual documents. Including the document's relation to a publication if applicable, a path to the document, and more information like a document's complete contents.
30
31### Subscriptions
32
33The [`site.standard.graph.subscription`](/docs/lexicons/subscription) lexicon tracks relationships between users and publications, enabling follow functionality and personalized content feeds across the AT Protocol network.
34
35## Design Philosophy
36
37There are minimal requirements to use these lexicons, ensuring adoptability is as straightforward as possible. As long as the minimum required properties are included in published records, they will be available for other AT Protocol platforms to consume.
38
39While <StandardSite /> lexicons are lightweight on their own, they can be expanded with additional properties to fit individual needs if necessary. The existing properties should not be seen as constraints, but rather as starting points.
40
41## Next steps
42
43- Read the [Quick Start](/docs/quick-start) guide to begin implementing
44- Explore the [Publication lexicon](/docs/lexicons/publication) schema
45- Learn about [Verification](/docs/verification) to link records to a domain
46- Check out [Implementations](/docs/implementations) to see tools and platforms using <StandardSite />