Browse your archive, edit pieces, and publish them for other people to wander through. Your Markdown stays yours. The web stack just gives it a front door.
- Deployment — start the published Docker images.
- Configuration — set up your site, storage, and sign-in.
- Templates — choose how pieces look and map your metadata.
- Development — work on the web stack from a checkout.
New to the files underneath? Start with archives or the CLI guide.
With authentication configured, open /admin to manage
pieces. Save edits, preview them, then use /admin/publish to check changes and
publish. Saving a file is not the same as publishing it.
Check lists all pending changes. Choose which added or updated pieces to publish. Publishing uses saved files, so edits saved after Check may be included. Unselected edits stay pending.
Every publish also applies all pending removals, regardless of selection. They are listed separately; you can apply removals without selecting any pieces. Schema changes also apply globally. A renamed file looks like a removal and an addition: the old public version can disappear before you select its replacement. Check alone does not change the public site.
Source and text-asset editors start with Standard keybindings. Press Ctrl+Alt+V while focused to toggle Vim mode; the browser remembers your choice. Use the Save button: Vim save/quit commands do not trigger application actions. If Vimium steals Escape, exclude the editor URLs in Vimium with an empty excluded-keys field.