Un kit modulare per la connessione locale

Get started

Four ways into the handbook, depending on what you have in mind.

Full handbook →

Run an instanceThe finished app under your own name and domain: image, configuration, branding, updates.Build your own appYour own app on the frame in ten minutes: connector, router, frame, done.Extend the stackDev environment, spec, guards, review. How a contribution becomes a PR.Work with agentsEntry points, task shape, rules and checks for coding agents.

Architecture

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.

Apps

• Reference app
• Your app

Toolkit

• Map
• Calendar
• Kanban
• Feed

Data Interface

• Items
• Spaces
• Capabilities

Connectors

• Web of Trust
• Supabase
• Your own

Toolkit

Kit frontend modulare

Real Life Stack viene sviluppato come kit frontend modulare in TypeScript con React. Comprende componenti autonomi utilizzabili sia nell'applicazione di riferimento sia come libreria riutilizzabile nei propri progetti.

Inoltre nasce un'app white-label self-hostable con un'interfaccia di amministrazione intuitiva, con cui i gruppi possono attivare moduli e personalizzare colori e contenuti senza conoscenze tecniche.

MappaOpenStreetMap via MapLibreCalendarioiCal / CalDAVKanbanTasks in columnsFeedFlusso di attività

Plus list, graph and resonance: every module live in Storybook →

Data Interface

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.

Items & relationsOne object, many views

Spaces & membersWho sees what, who belongs

CapabilitiesWhat a connector can do, the surface checks

Connectors

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.

Web of TrustLocal-first, end-to-end encrypted, identity as a DID

npm

SupabaseCentral server with sign-in, permissions and realtime

npm

Your own connectorThe same interface against your source: REST, GraphQL, local or P2P

Spec

See it in action

The demo shows the reference app with every module. The handbook takes you to your own instance or app.

Guarda la demo →Handbook