31: Story Studio - transcript
Jessica: The QUILL Cast, episode thirty-one. I'm Jessica. Today is for the long-haul writers: novels, memoirs, theses, anything too big for one file. Story Studio.
Liam: I'm Liam. The genre is the binder application, made famous by tools like Scrivener: the book as an organized project, chapters you can rearrange, research beside manuscript. Beloved tools, and famously rough with screen readers. Story Studio is the keyboard-first answer.
Jessica: And it opens with the most QUILL move possible: a project is just a folder of plain text files, plus one small companion file for the metadata. Delete the companion, and every word you wrote is still there in ordinary files. No proprietary format, no export hostage situation, ever.
Liam: Open it from Tools, Story Studio, and you get the binder: a tree you arrow through. Manuscript at the top, then groups for Characters, Places, Plot Threads, Research, and Brainstorm.
Jessica: Here's the elegant part, and by now, episode thirty-one, you'll see it coming: the manuscript structure is your Markdown headings. Chapters and scenes in the binder are the heading outline of your files, there's no second structure to maintain, no drag-and-drop ritual. Restructure the book by editing headings, the binder follows. Episode fourteen's hash-space habit has now organized an entire novel.
Liam: Enter on any binder item opens that file, a chapter opens at its heading. The binder is navigation; the editor is the same editor you've lived in all course, with every power intact.
Jessica: The story-bible side: stand on a character, press Edit Details, and a small accessible form appears, role, goal, motivation, arc, tags. Fill it in, and it saves as front matter, readable metadata at the top of the character's own plain file. Not rows in a hidden database, text in your text.
Liam: Plot threads carry a status field, open, resolved, abandoned, so the dangling-thread audit before your final draft is a browse through one binder group. Research and Brainstorm are simply folders of notes that live with the manuscript instead of scattered across a decade of desktops.
Jessica: And when the draft is done: Compile Manuscript. Every manuscript file, stitched in order, into one document. From there, episode seventeen's export wall: Word for the editor who wants docx, EPUB workflows, DAISY from episode twenty-four, or straight into the audiobook pipeline, your novel, narrated by episode twenty-one's voices, chapters intact.
Liam: Now the combination move for the ambitious: Story Studio plus the Vault. Keep worldbuilding as a vault, notes per character, place, and lore item, linked and backlinked, and the manuscript as a Studio project. Standing in a character's vault note, Show Backlinks lists every scene that mentions them. Your story bible answers questions instead of just storing answers.
Jessica: And the supporting cast from part two all report for duty at book scale: bookmarks that survive restarts holding your place in chapter twelve, snapshots reassembling the whole writing session, versions cut before every major revision, the safety stack of episode thirteen guarding a hundred thousand words the same as it guarded one paragraph. Long-form writing is where those episodes compound.
Liam: Homework. One: take any Markdown file with a few headings, put it in a fresh folder, open Story Studio on it, and hear your headings become a binder. Two: add a character and fill the details form, then open the file as plain text and read the front matter it wrote. Three: Compile, just to feel the whole thing become one document on command.
Jessica: Next episode opens the final part: production and trust. First up, GLOW, the accessibility review system, because the person most affected by inaccessible documents should be the best equipped to never produce one.
Liam: I'm Liam.
Jessica: I'm Jessica. Go write chapter forty. We believe in you.