דלגו לתוכן
Real Life Stack

ערכת כלים מודולרית עבור חיבור מקומי

כלים שמאפשרים לקהילות להתארגן באופן מבוזר, בהגדרה עצמית ומושרשים במפגשים אמיתיים.
לצפייה בהדגמהHandbuchStorybook

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.

Toolkit

ערכת פרונטאנד מודולרית

Real Life Stack מפותח כערכת פרונטאנד מודולרית ב-TypeScript עם React. הוא כולל רכיבים עצמאיים שניתן להשתמש בהם גם באפליקציית הייחוס וגם כספרייה לשימוש חוזר בפרויקטים משלכם.

בנוסף נבנית אפליקציית white-label לאירוח עצמי עם ממשק ניהול אינטואיטיבי, שבאמצעותו קבוצות ללא ידע טכני יכולות להפעיל מודולים ולהתאים צבעים ותכנים.

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.

לצפייה בהדגמה →Handbook