Get started
Four ways into the handbook, depending on what you have in mind.
Four layers
An app is composed of toolkit modules. The modules read through the Data Interface and write through the capabilities the connector offers. A connector links it to a data source: Web of Trust, Supabase or your own.
Apps, modules and connectors can be swapped as long as they keep to the Data Interface: it is the fixed contract in the middle. The sections below walk through them from top to bottom.
Modules that fit together
Map, calendar, kanban and feed are standalone React components in TypeScript. Each runs on its own; together they make an app. The reference app composes them, and your app can do the same.
If you would rather not write code, run the finished white-label app and choose modules, colours and content in its configuration.
One interface for all modules
All modules speak the same language. What they read and write are items in spaces, related to one another and to people; an event, a place, a task, a profile differ only in their fields. That is why the same neighbourhood festival can sit in the calendar and on the map without existing twice.
When an item changes, every surface showing it follows. And what the backend underneath can do decides what the surface offers: a connector that cannot write gets no write buttons, but an app that still runs.
Two connectors, one contract
Below the interface sits the connector. It decides where the data lives; the surface does not notice the switch. Two ship ready-made, each an npm package.
A connector of your own implements the same interface against another source, with exactly the capabilities the source offers. What it cannot do, the surface hides.
See it in action
The demo shows the reference app with every module. The handbook takes you to your own instance or app.