Introducing Two: build the site, keep the source
A focused place to make a website—and a straightforward way to take it with you. Two brings visual editing, structured content and static publishing into one local workspace. The pages, posts and images remain in a folder you control.
The Two publishing model: create → connect → publish.
Make the site you imagined
Start with a page and shape it directly on the canvas. Write long-form posts in a focused editor. Add images, lists, tables, buttons and embeds where they belong. Contextual controls appear around the thing you are editing, so the document stays at the centre of the experience.
The canvas and contextual inspector, shown in the September 2026 interface review. Open the screenshot at full size.
Write once. Let the site connect the dots.
A post can have a date, an excerpt and tags. Save a collection query, then place that collection on a page: a Writing index, a Projects page or a recommended shelf can all draw from the same source. Update the post once and every place that uses it updates on the next build.
Publish a website you can carry anywhere
Two builds ordinary HTML, CSS and assets. Preview the output in the Website view, then deploy the generated folder to a static host. Your editable project stays separate from that output; a portable .wsite bundle can back up the project when you want one.
The Website view in the September 2026 interface review. Open the screenshot at full size.
An architecture built around ownership
The source of a Two site is a vault: an ordinary folder with a site manifest, readable .wcontent documents, saved collections and content-addressed assets. The generated website can be recreated from it. That simple boundary lets the editor, the site builder and an optional agent connection work on the same project.
- Create: the React editor, inside a Tauri desktop app or a supported browser, edits one document model.
- Keep: revision-aware commands save changes to the vault; History and draft recovery help when an edit is interrupted.
- Find: the document index powers tags, saved collections, Browse and dated archives.
- Publish: the exporter renders the source into portable static pages and copies the referenced media.
- Extend: the optional MCP server can work with an existing vault through the application command path; it is a separate runtime today.
Two’s development log
Follow the product’s own changes, not a feed of this website’s posts. Each dated milestone is an editable post tagged Two Devlog; a saved collection gathers them into a timeline page that can be changed in the builder or through MCP.
July 2026 · the foundation
Static publishing, local preview and MCP access established the path from an editable vault to a website you can inspect and deploy. An agent could work with the same vault as the visual editor.
September 2026 · a quieter editor
The interface review put the document first: contextual canvas tools, variants and a more focused inspector reduced the permanent UI around writing and page design.
October 2026 · from capability to product
A locally verified Windows installer, pagination and incremental builds, reviewable agent change sets, native embeds and richer image timelines moved Two forward. Shared vault work added owner and replica flows, with release checks still in progress. The full timeline links each milestone to its own short note.
Made for the next site you want to make
Two currently targets Windows x64 as a desktop release. Browser editing is also supported in the project, while macOS packaging and automatic updates are planned. This website was generated with Two: explore its pages, then follow the dated work in Devlogs.