A free, open-source, self-hosted place to write a novel.
Fablewright PRODUCT.md
9.2 kB · 109 lines
Markdown
at main

Product #

Platform #

web

Users #

Novelists and long-form fiction writers who want a Dabble-class writing environment they control. They draft in long sessions, often daily, over months or years per book, and plan beside the draft with notes and a plot grid.

A Fablewright instance typically serves a small group: one person self-hosting for themselves, a writing circle, a family, or co-authors. The first account on an instance becomes its admin, and the admin controls sign-ups. The admin is usually a writer too.

Secondary audience: self-hosters installing and maintaining an instance through Docker Compose, Cloudron, or bare Node, who need boring backups and painless upgrades.

Product Purpose #

Fablewright is a free, open-source, self-hostable novel-writing platform. A writer organizes a manuscript (project, books, parts, chapters, scenes), drafts in a rich-text editor that saves continuously, keeps story notes and a plot grid beside the draft, and can leave with every word at any time.

Success: a writer can plan and draft a whole novel on a server they trust without needing a hosted subscription, and can export everything in open formats.

Positioning #

  • The writer owns the data. It lives on a server the writer, or someone they trust, controls. Full export at any time in open formats (DOCX, EPUB, Markdown). No lock-in.
  • Plain-file portability. Manuscripts export as Markdown that works with git.
  • Free, no paywalls. Every feature is available on every instance. No tiers.
  • No generative AI, ever. A firm, public commitment.
  • Copyleft. Licensed under the Mutualist License (MutuaL-1.3).

Dabble, LivingWriter, Novlr, NovelPad, Novelize, and Reedsy Studio are hosted services, mostly subscription-based, and several ship AI features. Fablewright's combination of self-hosted, free, human-only, and plain-file export is what a neighbouring product cannot truthfully claim.

Operating Context #

  • The editor is the primary surface. Writing sessions run for hours, at any time of day, under any light.
  • Core loop: create a project, add a book, build chapters and scenes, draft in scenes, consult and edit notes and the plot grid, save a scene version before revising, search and replace, export.
  • The server holds the saved copy. The browser keeps a local recovery buffer between saves when storage is available. The buffer can be lost, and Fablewright does not support offline drafting.
  • Self-hosting rituals: docker compose up, a Cloudron install, or node server.js under systemd. Backup means copying one SQLite file and one uploads directory.

Capabilities and Constraints #

MVP scope (confirmed 2026-10-21) #

  • Accounts: email and password (better-auth). The first account becomes admin; the admin controls sign-up.
  • Homepage: a real landing page at / for signed-out visitors that introduces Fablewright, with sign-in, sign-up when open, and the source link. Signed-in writers go straight to their library.
  • Library: the writer's projects.
  • Manuscript organization (Dabble-style): a project holds one or more books (a series). A book holds optional parts, then chapters, then scenes. Each book also holds unnumbered front and back matter pages, edited directly in the prose editor. Writing happens in scenes. Drag and drop reorders and moves items within the hierarchy. Notes can be shared across a series.
  • Editor: rich text with Markdown-style input shortcuts (typing ** or # formats), built on TipTap/ProseMirror. Lossless storage, continuous autosave, word counts.
  • Colour modes: the Digital Rust dark theme and Safe Mode, with a manual switch.
  • Story notes: characters, places, and other note types with templates and images, linkable to scenes, shareable across a series.
  • Plot grid: storylines as rows, chapters or scenes as columns. Cards link to scenes and notes.
  • Export and import: Export a project to DOCX, EPUB, or a project archive. The archive is a .zip holding manuscript.json and readable Markdown. Export one book, chapter, or scene to DOCX, EPUB, or print. Import a Fablewright archive, Scrivener folder or ZIP, DOCX, Markdown, or plain text. Scrivener, Word, and Markdown imports show proposed structure and conversion limits before committing. Scrivener research and extra metadata become notes. The app attempts to keep each import source and a downloadable report. A selected Scrivener folder is kept as a ZIP.
  • Focus mode: distraction-free writing with the chrome hidden.
  • Scene versions: per-scene version history, automatic and manual, with diff and restore.
  • Reading and outline: a read-through of the whole project, one book, one chapter, or one scene, and an outline that shows each chapter and scene with its word count, synopsis and status. Split a scene at the caret and merge it with the next one; both keep a project version and a scene version.
  • Reader access: a project member with the reader role can use the read-through and outline, which are read-only for that role. The role is enforced on every route, and the owner can invite an existing account from Sharing. Invitations require acceptance.
  • Recovery: trash restore for deleted structure, notes and storylines; note and card versions; whole-project versions opened as a separate copy. Exports keep this history.
  • Search: full-text search across scenes and notes; find and replace inside the open scene.
  • Writing goals: an optional daily word target for one writer in one project, with days off, a two-week chart of words added, and a streak the writer turns on. A goal can also carry a deadline: a number of words to add by a date, counted from the day the writer set it, with the writing days left and the pace a writing day needs. The status bar shows the words added today against the target. Progress counts words added in the scene editor under the writer's own local date; deleted words never subtract, and imports are not writing.
  • Sharing and feedback: The owner can invite readers and co-authors. Expiring secret links allow guests to read, comment, or edit scene prose without an account. A link covers the whole project or one book, chapter, or scene. Feedback can refer to a passage, scene, or chapter. Passage feedback keeps a quotation and can suggest replacement text.

Deferred #

  • Later: real-time co-editing.
  • Projects start private. The owner chooses when to invite members or create secret links.

Never #

  • Generative AI features of any kind.

Technical constraints #

  • SvelteKit 3, Svelte 5 (runes), TypeScript, pnpm, Tailwind 4, adapter-node.
  • SQLite only (node:sqlite through Drizzle). One database file per instance.
  • better-auth for authentication.
  • Supported deployments: Docker image with docker-compose, a Cloudron package, and bare Node with a systemd example.
  • Tests: unit tests and Playwright end-to-end tests for core flows. Storybook documents the design-system components.

Terminology #

Instance, Admin, Writer, Library, Project, Book, Part, Chapter, Scene, Note, Note type, Template, Plot grid, Storyline, Card, Scene version, Project version, Focus mode.

Brand Commitments #

  • Name: Fablewright.
  • Palette: the Digital Rust palettes are mandatory (the rust ramp and the six failure accents, in both the dark theme and Safe Mode). Everything else in Digital Rust is optional, at the design director's discretion. All design work goes through Impeccable.
  • No generative AI, stated publicly where useful.
  • License: Mutualist License v1.3, Short ID MutuaL-1.3. Credit block: name Fablewright; project home https://tangled.org/katsuricata.com/Fablewright; original copyright holder Kat Suricata.
  • Source link: every instance shows a clear link to the source code and the project home, as the license's Notice and Mutualism sections expect. Self-hosters keep it in place.

Evidence on Hand #

  • No users, testimonials, screenshots, logo, press, or usage numbers exist yet. Never fabricate them.
  • License text: LICENSE.md in this repository is the canonical copy.

Product Principles #

  1. The words are sacred. Protect the draft with autosave, a local recovery buffer, and versions before destructive changes. A browser buffer is not a backup.
  2. Leave any time. Every piece of writer data exports in open formats. No feature traps data.
  3. Writing first. The manuscript is the primary surface. Planning tools sit beside it, never in front of it.
  4. Human-made. No generative AI.
  5. Boring to host. One process, one SQLite file, one uploads directory.

Accessibility & Inclusion #

  • Both colour modes are always reachable: saved preference first, then the OS preference, then the dark theme, with a manual switch. Safe Mode is the light accessibility projection.
  • WCAG 2.1 AA contrast in both modes, which the Digital Rust palette is built to clear. This target comes from the pinned palette's specification rather than a separate product decision.
  • Full keyboard operation of the editor, the manuscript tree, and every dialog, with a visible focus ring.
  • prefers-reduced-motion is respected.