01 · Content in the repository

An entry is a file. It has a title, a date, paragraphs and a few descriptive fields, and it sits in its series' directory along with the rest. Deployment takes those files as they are — there is no database between them and the page into which they would first have to be imported.

Several things follow at once. The change history is the repository's history, so it is visible who corrected what and when. A backup is a copy of a directory. Moving to another tool needs no export and no request for help — the files are already in a format readable without this engine.

What is missing: a panel for writing in the browser. That is a deliberate cost. An author who wants an editor with a preview has one in their own tool; the engine does not try to be a word processor, because every such tool built along the way is worse than the ones that do only that.

The gain is that no state exists which can be lost on someone else's side. The site can be raised again from the repository alone, and the repository sits wherever the author keeps it.