# editor

> Edit a working web app the way you edit a shared document. Everyone on the link changes the same page at once, its words, styles, layout and components, while its buttons and forms keep working.

Each page is markdown at its own path plus .md; these pages are the project's spec. Components are self-closing tags such as <Status />, filled in when the site is built; compare.json holds the Compare page's data.

## Pages

- [editor](https://editor.notez.beer/index.md): Edit a working web app the way you edit a shared document. Everyone on the link changes the same page at once, its words, styles, layout and components, while its buttons and forms keep working.
- [Features](https://editor.notez.beer/features.md): What the editor promises, in five groups, each promise with the proof that would show it. Status says which are proven.
- [How it works](https://editor.notez.beer/how-it-works.md): A page is a tree of components in a CRDT, edited through a document-style surface, kept in your browser and synced between its tabs, and published as static HTML. Each technology and what it beat, how comments and AI work with no server, and what it costs to run.
- [Compare](https://editor.notez.beer/compare.md): Builder.io, Puck, Webstudio, Onlook, Webflow, Notion and others, by tool and by need, each claim dated. What each is better at, and when to use it instead.
- [Status](https://editor.notez.beer/status.md): What isn't done, first, then every promise as planned, built or proven, worked out from the code and tests when the site was built.

## Optional

- [Everything in one file](https://editor.notez.beer/llms-full.txt)
- [Compare data](https://editor.notez.beer/compare.json)