Write and autosave

Open an existing document

The configured generator adapter discovers collections and returns stable document references. Listing a workspace is read-only: files that you do not edit remain byte-identical.

When a document opens, Studio shows the newest acknowledged draft when one exists; otherwise it shows the file source. The header save state distinguishes local changes, an in-flight save, a confirmed snapshot, an error, and an optimistic-version conflict.

Start a native draft

Choose New article, enter a title, and optionally provide a lowercase kebab-case slug. The generator adapter creates a real draft in the site’s native draft collection—for Hexo, source/_drafts. It refuses duplicate or unsafe paths instead of overwriting an existing file.

The new file and the acknowledged SQLite snapshot have different jobs: the file keeps the site portable, while the snapshot lets Studio autosave without rewriting Git-tracked content on every keystroke. Discard changes removes only the acknowledged snapshot and restores the native file; it never deletes the Markdown file.

Choose the right editing mode

• Visual mode is useful for ordinary Markdown structure.
• Source mode is the lossless escape hatch for raw HTML, Hexo tags, or syntax the visual editor cannot represent safely.

Studio may choose source mode automatically when it detects generator-specific constructs. Switching modes must not itself create a draft change.

What an acknowledged save means

An autosave response includes a monotonically increasing draft version. Once acknowledged, that version survives browser refresh and service restart in the mounted SQLite database. A request with a stale expected version is rejected as a conflict instead of silently overwriting newer work.

Draft save does not commit Git, rewrite the source file, build the site, or publish. Those remain explicit release actions.

When a native draft is published, Studio builds it in an isolated workspace. Only after upload, cache invalidation, and public marker verification succeed does Studio promote the canonical draft into the published collection and clear its snapshot. A failed build or verification leaves both canonical source and acknowledged draft intact.

Conflict recovery

When Studio reports a conflict:

1. copy any unsaved text you need to retain;
2. reload the current server draft;
3. reconcile the two versions in source mode; and
4. save again against the current version.

v0.1 is a trusted single-user product, but optimistic revisions also protect against stale tabs and prepare the data model for later collaboration.