B-Maker Explained

StructureOutput

Why keep sections that the reader will never see?

Because the project needs working structure that the finished book may not need.

The principle

The structure that helps the author work and the structure that belongs in the exported book are related, but not identical.

Some sections belong to the project, not the book

Research, Drafts, Published articles, discarded material, notes for the editor or temporary assembly sections may remain useful for months. Deleting them just to produce a clean export destroys context.

Hide a heading when the content belongs but the label does not

An internal section name such as “Transition material” may help navigation without being something a reader should encounter as a printed heading.

Exclude a section when the whole branch is working material

A Published archive can stay searchable inside the project while remaining outside the current book. The same applies to research branches and alternative material.

Screenshot: project structure vs book outputShow a manuscript tree containing Research, Drafts and Published. Mark one heading as hidden and one branch as excluded, while a preview/export panel contains only the reader-visible book.assets/img/bmaker/bmaker-explained-structure-output-01.webp

This avoids destructive cleanup before export

The project can remain rich and useful while the deliverable stays clean. You do not need to dismantle the workspace every time you produce a book file.

Preview vs export · Why a publishing package? · Articles to book workflow