ARCHITECTURE

How Nabu works,
and why it works that way.

Seven short chapters, written by the people who made the choices, including the ones we got wrong. Read them in order in about twenty minutes, or jump to what worries you.

THE STORY · 7 CHAPTERS

each chapter has a live editor under X-ray
  1. 01 One contenteditableWhy the whole document is one editable surface, and what that costs us. ADR 001 · 003
  2. 02 The model is the truthA Loro tree holds the document. Blocks are Svelte classes over it. The DOM only reflects. ADR 000 · 002 · 004 · 010
  3. 03 The life of a keystrokeFrom your key to the paint, step by step. Two of the steps are timed live, on your machine. ADR 007 · 008
  4. 04 Where is the caret?Mapping a browser selection to the model and back, and why undo puts it back. ADR 006 · 015
  5. 05 Commands, not keycodesOne action bus, a keymap you can rebind, confirmations that never trap you. ADR 011 · 017
  6. 06 Nothing gets lostSaving, merging tabs, going offline, and files that live outside the document. ADR 010 · 014
  7. 07 We got regions wrong onceMarkers, then boxes. The story of a decision we reversed, and what it cost. ADR 016 → 018
THE LIMITS

What Nabu doesn't do well (yet)

Mobile keyboards, Firefox and Safari, typing in huge documents, tables. What we know, the numbers, and what we plan. THE RECORD

Decision records

Every architectural decision, as it was taken: context, decision, consequences, status. 18 records, 1 superseded. THE PEOPLE

How Nabu is made

One person and an AI: what each layer wrote, the real commit log, and Killian's own words about it.