Articles
Longer-form writing on craft, publishing, and the tools we make.
Products
Start with the writing or planning tool you already know, then identify the Story views, local Project, author workflow, or publishing handoff your next book still needs.
Scrivener builds a mature long-form environment with Binder, Corkboard, and Research. When time, relationships, places, and evidence begin to interact, see how Scroll uses multiple Story views to help a writer inspect the whole work.
Manuskript helps a novel grow through open source, premise development, Outline, and Index Cards. As the work becomes a long-term writing practice, see how Scroll keeps planning, prose, tasks, versions, and the publishing handoff in one coherent desktop experience.
Ulysses uses Library, Sheets, and continuity across Apple devices to protect focused writing. When characters, research, revision, and versions turn a book into a large Project, see how Scroll keeps planning, prose, and publishing preparation together.
Obsidian lets local Markdown, Links, Graph, Canvas, and an extensible ecosystem grow into a lasting knowledge network. When a novelist maintains separate vaults for separate worlds, see how Scroll gives every local Project the same planning, writing, task, version, and publishing workflow.
Notion uses database views, comments, and permissions to give a team one creative map. When the work becomes a book-length manuscript with versions and a publishing handoff, see how Scroll provides a focused local Project for the author and a clear path to Scribe.
Conflicting ages and dates, an outline with too many levels, and scattered world records are different problems. Learn how Aeon Timeline, OmniOutliner, Fantasia Archive, and Scroll divide specialist depth and an integrated writing workflow.
From ideas and story planning to focused drafting, research, revision, and manuscript versions—start with the pressure point holding up your long-form Project.
What should a timeline, relationship graph, map, or whiteboard tell you? Learn how Scroll views read the same Story data from different angles.
Start with the minimum useful Story data, then decide when a character, place, event, property, or relation deserves a reusable Project model.
Separate story events from author tasks, then use Kanban, Calendar, Task list, and a bounded schedule to manage drafting and revision.
Use a clear goal, limited feedback, Mask, Typewriter, and a safe exit to build focused writing sessions you can repeat.
Write on a formatted surface, inspect Markdown and YAML directly, and understand the save and backup boundaries around one manuscript.
When world notes grow but scenes remain blocked, use minimum Story data, explicit relations, Map, and Timeline to connect setting with character choice.
For mysteries with conflicting testimony or two timelines, separate actual events, character knowledge, and reader revelation before using views, search, and tasks.
When PDFs, web notes, and interviews are scattered, distinguish the original, Project copy, author judgment, and prose, then recover the chain through cards, links, and search.
When feedback covers the whole manuscript, define one structural question, inspect it through focused views, and turn it into bounded cross-chapter work.
Separate working files, Works, Manuscript versions, Publish Version, and whole-Project backups so revisions and self-publishing sources remain explainable.
Choose long-form writing and planning tools by the problem your book needs to solve, not by a single “best” label.
Planning a multi-viewpoint story? Explore seven tools for long-form structure, time models, knowledge networks, collaboration, and multi-view Story data.
Explore six tools for settings, relationships, maps, and timelines—and decide whether your world needs an enduring encyclopedia or Story data close to the draft.
How does saved research reach the draft? Explore Zotero, Scrivener, Obsidian, Notion, Aeon Timeline, and Scroll across sources, search, judgment, and citation.
How should a trilogy manage shared facts, separate Works, revision drafts, and publication sources? Explore seven approaches to series planning and version boundaries.
Scroll keeps planning and manuscript work together; once the text is ready, Scribe handles typesetting, pagination, and publication outputs.
A practical Scroll to Scribe workflow for choosing a manuscript source, checking the handoff, and beginning book production.
Before book production begins, check manuscript authority, book scope, recovery, Scroll delivery preparation, and Scribe's recognition of the intended source.
Products
Neutral, side-by-side comparisons with the writing and typesetting tools authors already know.
Scrivener redefined the way long-form novels manage their source material; Scribe carries the same manuscript all the way to print and CJK typesetting.
Vellum makes elegant, simple e-books and printed books for Mac users; Scribe carries the same simplicity to Windows and Linux, and adds CJK and CMYK.
Ulysses polishes Markdown writing in the Apple ecosystem to near-perfection; Scribe keeps the same writing experience and wires the e-book and print pipeline into the same application.
A comparison of Atticus and Scribe for indie authors choosing between browser-based book formatting and a local-first Markdown desktop workflow.
Affinity Publisher is a one-time-purchase professional layout tool covering visually dense projects; Scribe puts the layout capabilities authors actually need inside the writing tool itself.
Word is the most ubiquitous writing tool, but it was never designed for print and e-book; Scribe keeps Word compatibility while wiring the publishing pipeline into the same application.
InDesign is the de facto standard in publishing; Scribe pulls the print capabilities indie authors actually use into the same app as Markdown writing, at roughly half the monthly fee.
Concrete workflows that walk a stuck manuscript out the door.
If you already write in Markdown but keep wrestling with 'the last step — typesetting,' here's a route that folds the whole pipeline into one app.
CJK vertical typesetting + ruby + print-grade PDF have long been a gray zone between Word and InDesign. Here's a realistic desktop-side route.
EPUB and print PDF follow different layout logic, but the manuscript should only exist once. Here's a path that keeps the source single and the outputs multi-form.
Papers, nonfiction, and textbooks have long been fragmented across an 'editor + citation manager + formula typesetter' triad. Pulling them into one app is possible.
Cloud writing tools are convenient, but manuscript ownership and offline availability are separate dimensions. Local-first doesn't mean isolated.
InDesign is the industry standard, but the monthly fee is steep for an indie author. If you only need to do book interiors, you can walk the same path on roughly half the budget.
A short, current shortlist for the year, refreshed annually.
A practical shortlist of free-start and paid typesetting software for small publishers, indie studios, and self-publishing authors in 2026.
A 2026 shortlist of writing software still being maintained and genuinely suited to long-form novel work, grouped by use case.
2026's usable EPUB export tools, grouped by workflow type, with notes on retailer hand-off and a separate look at the technical-minded options.
2026's genuinely three-platform-native writing software — not web wrappers — grouped by scenario with fair pros and cons.
Connect Scribe to the writing, notes, and reference tools you already use.
Obsidian is good for growing worldbuilding and research; Scribe is good for taking a long draft to a finished book. Splitting the work cleanly avoids cross-contamination between notes and prose, and avoids maintaining the same content in two places.
Notion is good for team outlining and shared research; Scribe is good for turning a long draft into a book. This piece covers when to switch, the structural losses you'll hit on Markdown export, and where the knowledge goes once the book is out.
Editors, collaborators, and publishers often only accept Word (or equivalents). This piece explains the docx bridge between Scribe and Word, version control across review rounds, and when to leave Word and come back to the Markdown side.
A practical workflow for using Grammarly, ProWritingAid, or LanguageTool with Scribe while keeping Markdown, chapter structure, and author voice intact.
Reedsy Studio fits cloud co-editing with a professional editor; Scribe fits author-led long-form and the print pipeline. This piece sets the boundary between the two, the styling gaps on the export path, and why print parameters belong back on the Scribe side.