A maintainable illustrated EPUB has three layers: manuscripts containing references, original image assets, and generated book files. Keep those layers separate. Then a moved picture has a traceable source, a repairable destination, and a new package that can be inspected without becoming the next edition's source.
Start with an asset sheet
For three chapters, three illustrations, and one cover, record the owning chapter, original location, source-relative destination, and purpose of each asset. A map belongs to chapter one, a relationship diagram to chapter two, a photograph to chapter three, and the cover to publication metadata. Give generated package names their own column because an exporter may rename resources.
A common self-publishing mistake is to extract a picture from the finished EPUB and later treat it as the master. It may already be renamed or processed. Return edits to the original asset and use the EPUB for distribution and inspection.
Move one picture to test the design
After the first export, move only the map from images to assets/maps. Inventory its referring manuscripts and occurrences before the move. Afterward, confirm the source points to the new location. Leave the other images and cover untouched so the result has one cause.
Rune Studio's file tree and integrated browser manage local assets. For Markdown image and link destinations in supported txt, text, md, and markdown files, the Mac application can update relative references after moves and renames. Read the changed chapter and search for the complete old destination afterward.
Carry the three layers through export
Choose the three sources on File Selection, define sequence and navigation on Chapter Order, select the cover on Metadata, and read the input summary on Review and Export. The artifact goes to the workspace's EPUB folder. Compare its chapters, used images, cover, and missing-resource result with the asset sheet.
In a before-and-after rebuild, both packages passed their local structural checks, retained seven reading-order entries, and changed after the controlled source edit. In a separate path test, one moved resource caused one destination rewrite and the new reference was readable afterward. These results do not extend to proprietary syntax or web URLs.
Zero missing assets is not a visual review
A map accidentally replaced by a relationship chart still points to a real file, so a missing count cannot detect the semantic error. Open every chapter and compare the visible asset with its alternative text and asset-sheet purpose. Judge resolution and legibility in the intended reader.
Self-production succeeds when the next corrected edition can be rebuilt from the same masters, not merely when one file opens today. Test the three-layer boundary with one moved image before reorganizing the whole book. Rune Studio's supported markup and EPUB scope describe the current Mac boundary.
