B-Maker Explained

Wave 5Planning

Why does a writing app need a publication plan?

Because finishing the text and finishing the work around the text are different projects.

The rule

The manuscript is the product being written. The publication plan is the sequence of work needed to move it from idea to finished deliverable.

A deadline alone is not a plan

“Finish the book by November” says where you want to arrive but not what has to happen next. Research, outline, first draft, editorial revisions, proofreading, layout, cover and publication have different dependencies and often different dates.

Stages make progress inspectable

B-Maker can keep publication stages with start dates, deadlines, milestones, notes and checklist items. Weekly and list views make overdue and upcoming work visible without turning the manuscript tree into a task manager.

The article wizard solves an earlier problem

Before a draft exists, the article wizard can capture the main thesis, reader outcome, target audience, tone, publication channel, editorial requirements, target length, sources, facts, examples and explicit out-of-scope material. Suggested sections become a writing scaffold rather than a generated article you must accept.

The book wizard helps at a different scale

A book needs a longer planning horizon and a structure that can evolve. The wizard and plan do not force you to design the entire project before writing; they give you a place to make commitments once those commitments become useful.

Why keep this in the same project?

Because plans change when the manuscript changes. If the plan lives elsewhere, it quietly becomes stale. Keeping both close reduces coordination work while still separating text structure from workflow state.

Writing has a structure. Publishing has a process.

B-Maker keeps both visible without pretending they are the same thing.

See the workflow Publishing package