Text Editor File Trees: Organize Chapters, References, and Images

A useful text editor file tree reflects the decisions you make while writing. Separate reader-facing chapters from research notes, images, and retired drafts. Number the chapter files so their reading order is visible. The result is not merely a tidy folder; it is a shorter route to the next file you need.

Give a long manuscript four entrances

When every asset lives in one directory, chapter-12.md may sit beside a map, a character sheet, an old version, and a cover candidate. Search can still find them, but opening the chapter after chapter twelve becomes a classification task.

A small novel workspace might look like this:

novel/
  manuscript/
    01-opening.md
    02-departure.md
    03-harbor.md
  notes/
    characters.md
    timeline.md
    places.md
  images/
    map-harbor.png
  archive/
    02-departure-old.md

The manuscript directory follows reading order. notes contains material used by the writer. images contains referenced assets. archive keeps a superseded draft out of the active sequence. That last separation reduces the chance of opening and editing the wrong version.

Reserve numbers for narrative order

Two-digit prefixes keep a modest set of chapter names sorted. Avoid applying the same numbering scheme to every note unless those numbers carry a clear meaning. characters.md tells you more than 01-note.md.

Projects with frequent insertions sometimes use wider gaps, such as 010, 020, and 030. Renaming files later may affect relative links and image references, however, so the numbering scheme and the editor’s reference behavior must be considered together.

How Rune Studio fits the folder model

Rune Studio provides a workspace file tree for local folders. Its product documentation also describes updating relative links and Markdown image references when supported text or Markdown files are renamed or moved inside the application.

That automatic behavior is documented, but we did not observe it end to end for this article. The recorded successful change was an explicit search-and-replace operation on a known path string. Do not treat that as proof that every later rename will repair its references automatically. External URLs and anchors within a document are outside the documented automatic-update scope.

Rehearse one move before reorganizing the book

Create a disposable workspace with one chapter, one image, and one Markdown file that refers to the image. Perform the same rename or move you expect to use in the real project. Then open the referring file and inspect both the path text and the rendered result yourself.

Also test the route you actually intend to use. A move performed inside an editor and one performed in the macOS Finder may trigger different behavior. If you cannot confirm reference updates, count the old path with workspace search before the move and search for it again afterward. That gives you a finite list to repair.

Let the tree grow after the need appears

Five chapter files do not require a deep hierarchy. Start with manuscript, notes, images, and archive. Add another level only when a real choice becomes slow—for example, when character notes become numerous enough to deserve their own folder.

This keeps the tree legible. A structure with eight nested directories can hide a file as effectively as a flat folder containing eighty unrelated items.

Use a file tree to reduce the number of decisions between “I need chapter three” and opening it. Keep active prose separate from references and retired drafts, and visually verify references whenever you rename or move a target. The Rune Studio product page provides the current file-management details and download information.

Who prepared this article

Naoya is an independent developer who writes about local writing workflows and explicitly distinguishes documented behavior from completed operational evidence.