Foldkit 응용 프로그램을 확장하는 패키지 outward - 에이전트, 서버, 기타 장치, URL 및 설계 시스템 - 국가를 지키는 두 번째 장소를 주지 않고.

Foldkit 응용 프로그램은 하나의 주 기계입니다 : Schema-typed ** Model**, a Message 일어날 수있는 모든 것을 조합 naming update 다음 모델과 일부 명령으로 메시지를 변환하는 기능. 그 모양 , 시험 및 재생에 대한 이유가 쉽습니다. 앱이 성장하는 순간을 잃게됩니다. 훅에 캐시, URL의 저장소, 다시 단순화 도구 핸들러 전환, 또는 자체 감속기를 가진 동기화 층.

이 저장소에 있는 모든 것은 1개의 국가 기계를 지킵니다. 대리인은 단지 할 수 있습니다 메시지 보내기 update 이미 핸들. 서버 데이터는 모델에 살고 있으며 update에 의해 재구성. Replicas는 같은 메시지를 재생합니다. update. URL과 로컬 저장소는 모델의 슬라이스를 미러; 그들은 결코 소유하지 이름 * 조회는 포획 없이 외부에서 작풍됩니다. 각 패키지 답변 질문, 그리고 그들은 명시된 응용 프로그램 경계를 충족하기 때문에 작곡.

** 웹 사이트:** 접킷 플러스.pages.dev 각 패키지의 가이드와 API 참조, 데모, 각 예제

foldkit-plus

Packages that extend a Foldkit application outward — to agents, servers, other devices, the URL, and design systems — without giving it a second place to keep state.

A Foldkit application is one state machine: a Schema-typed Model, a Message union naming everything that can happen, and one pure update function that turns a Message into the next Model and some Commands. That shape is easy to reason about, test, and replay. It gets lost the moment an app grows a cache in a hook, a store in the URL, a tool handler that re-implements a transition, or a sync layer with its own reducer.

Everything in this repository keeps the one state machine. An agent can only send Messages update already handles. Server data lives in the Model and is reconciled by update. Replicas replay the same Messages through the same update. The URL and local storage mirror a slice of the Model; they never own one. Views are styled from outside without forking. Each package answers one question, and they compose because they meet at explicit application boundaries.

The website: foldkit-plus.pages.dev has each package’s guides and API reference, and the demos, each an example from this repository built as static files. Those with a server run it in your browser, shared by every tab, so nothing you do leaves it:

• A blog studio and its site (examples/cms): Drafts beside the row, revisions, scheduled publishing and a page builder, with the public site rendered at build time.
• Two devices, one registry (examples/registry): Two devices edit 10,000 products in a data grid, offline and in conflict, and agree once both are back.
• Pages two tabs edit at once (examples/pages): Rich text two people edit at the same time, online or not, converging through one journal.
• A rich text playground (examples/richtext-playground): One document with movable blocks, anchored discussions, images, tables, code, toggles and footnotes, every edit a transition of the Model.
• A todo list an agent can use (examples/todo-app): One application definition drives the view, the tools an agent calls, the document replicas share, and the policy the server enforces.
• A Twitter clone, Chirp (examples/chirp): Posts declared once as Entities, guarded on the server, served through Remote, posted and edited through forms built from the same input, and liked in one round trip.