Anton Kurakin
RUEN
B-Maker Explained

ViewsStructure vs status

If there is already a tree, why have a board?

Because the order of the book and the state of the work are different dimensions.

B-Maker manuscript board
The distinction

The tree answers “where does this belong in the manuscript?” The board answers “what is happening with it now?”

The tree should remain structural

Chapter 4 belongs after Chapter 3 even if Chapter 4 happens to be the thing you are rewriting today. Moving sections in the tree changes the book itself.

The board is operational

Draft, rewrite, edit, ready: these states cut across book order. A board makes progress, bottlenecks, character filters, and plotline filters visible without asking you to reorganize the manuscript.

Why not encode status in folder names?

Because then workflow information contaminates book structure. “Needs edit / Chapter 4” is useful today and meaningless in the final manuscript.

Screenshot: same manuscript, two questionsSide-by-side: structural tree in book order and board grouped by Draft / Rewrite / Ready. Use the same chapter titles in both views.assets/img/bmaker/bmaker-explained-tree-board-01.webp

Use each view for one job

If you are deciding sequence, hierarchy, or where a section belongs, use the tree. If you are deciding what to work on, what is blocked, or what still needs revision, use the board.

Collections vs search · Several views workflow