Working across machines
There is no account and no sync service, and there does not need to be: a project is an ordinary folder, so the sync you already use just works. Moondonut adds nothing here and configures nothing on your behalf — the folder stays yours.
Whatever you already have
- iCloud Drive, Dropbox, OneDrive. Put the folder in the synced directory. There is nothing else to do.
- Syncthing. The no-cloud option, if you would rather nothing left your machines at all. It is one of the choices here, not a special path — Moondonut cannot tell the difference.
- Git. Markdown diffs cleanly, and a documentation project is a repository like any other.
Three things worth knowing
A sync conflict leaves a file like
notes.sync-conflict-20260824.md in the folder, and it
shows in the tree on purpose. A conflict is something
you should see, not something a tool should quietly pick a winner for.
Dot-entries are skipped everywhere — the tree, the scan, the export — so
.stfolder, .git and friends stay out of your
way and out of what you publish.
If a file changes underneath you while it is open, Moondonut tells you rather than guessing which copy wins.