The principle
Assets that participate in preview and publication belong to the same lifecycle as the manuscript.
Separate folders create reconciliation work
Which cover is current? Which image belongs after which section? Was the exported PDF built with the latest illustration? External folders make those questions manual.
Project assets give the book a stable context
Cover and illustrations can travel with the portable project and participate in preview and export without requiring a final “collect everything from Downloads” stage.
Screenshot: text and assets in one projectShow manuscript structure, cover and 2–3 illustrations inside the same B-Maker project, with the preview using those assets.
assets/img/bmaker/bmaker-explained-assets-01.webpOwnership becomes easier to reason about
If one project file is the canonical work, the writer knows what to move and back up before changing machines.
Why local-first? · Preview vs export · Why several safety layers?