Colibri (pronounced /ˈkoʊ lɪ bri/) is a next-generation social chat app built on the AT protocol. It functions entirely by using ATproto as infrastructure and utilizes the protocol to its limits.
This documentation aims to provide an overview over the architecture of the project, the specifications for lexicons, associated labels and the AppView, as well as helpful pages about contributing to Colibri.
| Page |
Contents |
| AppView Architecture |
Architectural and technical details about our AppView implementation |
| Client Architecture |
Architectural and technical details about our client implementation |
| Communities |
How communities work and where their records are stored |
| Page |
Contents |
| AppView Specification |
The XRPC endpoints and event stream an AppView must implement |
| Lexicons |
The AT Protocol record schemas Colibri defines |
| Facets |
How rich-text facets are encoded, rendered, and which take precedence |
| Page |
Contents |
| Overview |
The local stack, prerequisites, and how dev mode differs from production |
| AppView Development |
Running the Rust service, its dependencies, migrations, and tests |
| Client Development |
The SolidJS client, the Astro website, and the native shell |
| Running a PDS |
The PDS communities live on, why it’s required, and how to run one |
| Page |
Contents |
| Getting Started |
Running your own AppView and connecting a client to it |
| Page |
Contents |
| Overview |
How to get involved and contribute to Colibri |