Text Editors for Manuscripts: Keep Drafts and Reference Notes Side by Side

When you place reference notes beside a manuscript, do not begin with the entire story bible. Build a one-scene reference card containing only the constraints needed for the passage you are drafting. Keep the prose on one side and that card on the other. The smaller reference surface reduces the need to dig through folders without surrounding the draft with unrelated facts.

A reference card for chapter eight

If chapter eight takes place in a harbor warehouse, the card might contain:

• characters present: Minato and Rei;
• time: thirty minutes after the previous chapter;
• location: second floor, windows on the east wall;
• Minato’s voice: no honorific speech;
• information withheld in this chapter: the shipper’s identity.

Those five facts answer likely questions during the scene. The full timeline and character files remain available when deeper evidence is needed, but they do not occupy the immediate writing surface.

Add a source pointer to each summarized item, such as “timeline.md — before chapter 8.” A concise card should not become a second, untraceable authority.

Order the card by the writing moment

Reference material is often organized like an encyclopedia. A scene is written in a different order. Put participants first, then time and place, then voice constraints, and finally information that must remain hidden. The eye encounters each item near the moment it becomes useful.

That ordering is a general editorial practice. It can be used with paper notes, separate windows, or any editor with a split view.

The Rune Studio arrangement

Rune Studio supports multiple panes and moving tabs between panes. In a small test folder, a manuscript and a reference file were placed left and right with distinct tabs and font-size values.

Keep the chapter in the writing pane and the scene card in the reference pane. Give the manuscript a width that supports continuous reading and the card enough room to show its short list. Rune Studio does not detect contradictions or insert reference facts into the draft. The writer still decides which source is authoritative and how a constraint affects the prose.

Consult at three deliberate points

Looking at the reference after every sentence can be as disruptive as searching for it. Check time and place at the scene opening, voice before the first exchange, and withheld information after the scene is complete. These three moments preserve long stretches of drafting while catching the most expensive continuity errors.

If a new fact emerges during composition, mark it as a candidate on the card. Decide after the scene whether it belongs in the canonical character or timeline document. Updating every note immediately creates a new kind of tab switching and can leave multiple sources disagreeing.

If the right pane still requires searching

The card is too large. Remove facts unrelated to the current scene or add a precise pointer to the underlying source. If the card is too thin to resolve a question, add the missing constraint rather than reopening an entire archive each time.

This workflow suits fiction and other long-form writing where continuity matters. It does not replace a citation manager, a spreadsheet for dense structured data, or a diff tool for exact revisions. The goal is simply to keep the next necessary constraint visible beside the passage it governs.

Try it for one scene. The Rune Studio product page lists the current layout features and download options.

Writer

Naoya is an independent developer who studies small, repeatable arrangements for long-form text production.