The shape of the setup

The whole workflow lives in three folders on your machine:

  • ~/Writing/, manuscripts, one folder per project
  • ~/Writing/_world/, series bible, character sheets, world files
  • ~/Writing/_backup/, rolling local backup target before off-site

Plain folders. No vendor account required. You can rsync them anywhere.

The editor

For Linux authors who want a real writing application (not a code editor), Edda ships a native Linux build and keeps everything on your own disk, in a single database file. For a folder-and-files workflow, turn on its plain-text mirror (Settings > Data): Edda then also writes every chapter, character, location, article and timeline as a Markdown file in a folder you choose, rewritten each time you save, ready for grep, git or rsync. The mirror is a read-only copy; you keep writing in Edda. If you'd rather use a generic text setup, Markdown in Vim or Helix, exported through Pandoc, that works too; the workflow below applies either way.

Writing assistance, built in

Edda ships with the Skald, a deterministic writing assistant that runs entirely inside the editor on your machine. There's no service to install, no server to start, no port to point at. Open Edda; it's there.

  • Prompts. 135 hand-curated prompts across nine categories, plus a combinatorial roller that assembles fresh premises from fixed archetype/situation/complication/twist parts.
  • Inline spell check. Bundled dictionaries in 19 languages, chosen by the project's language, plus a per-project dictionary that travels with the project, so the Norse name you invented for chapter three doesn't get underlined for the rest of the series.
  • Style flags. Passive voice, weasel words, repeated words, wrong indefinite article, adverb density, filter words, telling words, dialogue-tag adverbs, and clichés, all rule-based.
  • Readability. Flesch, Flesch-Kincaid grade, Gunning Fog, SMOG, Coleman-Liau, Automated Readability, classic formulas, computed locally.

You can confirm with a network monitor: pull a prompt, run a chapter report, type for ten minutes with spell check active. No packets leave the machine.

Backups that aren't a vibe

The point of an offline workflow is to own your files. The point is undermined if your only copy is one disk crash from gone. A boring backup plan:

  • Local rolling backup: rsync or borg from ~/Writing/ to ~/Writing/_backup/ hourly via a cron job.
  • Off-site, encrypted: same content, but encrypted, to a remote you control, an SSH server, an S3 bucket with client-side encryption, or a friend's NAS. Daily.
  • Cold copy: monthly, to a USB drive you keep in a drawer. Boring, indestructible.

Why this beats the SaaS workflow

Cloud writing apps sell sync as a feature. For most authors the sync is invisible 95% of the time and a blocker the other 5%, the trip without WiFi, the locked account, the document that wouldn't load. An offline-first Linux workflow inverts that: it's there 100% of the time, and you opt into sync (e.g. via a self-hosted Syncthing or Nextcloud) on your own terms.

For the broader case, see Privacy-First Writing Apps: A Working Author's Guide.

Related: The real cost of subscription writing apps.