The practical route for the query “EPUB editing checklist” is specific: inspect body, navigation, cover reference, and spine as separate outputs of one edit pass. The controlled case is a copied EPUB project with one body edit, chapter rename, and replacement cover. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for body revision, nav chapter name, cover reference, spine order, regeneration. The excluded range is stated separately: direct repair of an existing EPUB, Japanese vertical layout, and reader-specific cover display.
Decision: Inspect body, navigation, cover reference, and spine as separate outputs of one edit pass
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove body revision, regeneration, or the stages between them.
The article-specific evidence card has these fields: body revision, nav chapter name, cover reference, spine order, regeneration. Do not count the following excluded range as evidence: direct repair of an existing EPUB, Japanese vertical layout, and reader-specific cover display.
Use the topic-specific specimen
In one copied project, change a body character and chapter name in source, replace the cover setting, and generate under a new ID. Inspect body text, nav title, cover reference, spine order, and unintended retention of the old cover. Success in one row cannot cancel stale navigation or a missing image reference.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to inspect body, navigation, cover reference, and spine as separate outputs of one edit pass. Name the source, working copy, and delivered or reopened result so that another editor can locate each one without relying on a filename such as final.
Do the work without changing the baseline
Use the following product-independent sequence on the named sample. It is an acceptance method, not a claim that Rune Studio has already completed this particular case.
- 1. Edit one character and chapter name in source. Attach the observed body revision evidence to this step.
- 2. Select the replacement cover. Attach the observed nav chapter name evidence to this step.
- 3. Generate under a new ID. Attach the observed cover reference evidence to this step.
- 4. Inspect body, nav, and cover reference. Attach the observed spine order evidence to this step.
- 5. Check spine order and stale cover resources. Attach the observed regeneration evidence to this step.
Inspect these fields independently
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Body revision — expected state: written before the run; hold the row if body changes but navigation keeps the old name.
- Nav chapter name — expected state: written before the run; hold the row if the cover exists without a reference.
- Cover reference — expected state: written before the run; hold the row if the old cover remains unintentionally.
- Spine order — expected state: written before the run; hold the row if body changes but navigation keeps the old name.
- Regeneration — expected state: written before the run; hold the row if the cover exists without a reference.
Three failures that invalidate the run
A second pass is meaningful only when its source and changed condition remain identifiable. Keep the earlier result and append the retest instead of replacing the failed row.
- 1. Body changes but navigation keeps the old name; preserve the failed artifact.
- 2. The cover exists without a reference; change only the responsible condition.
- 3. The old cover remains unintentionally; return to the named source.
A product check without a performance claim
Current product documentation covers capabilities relevant when you need to reduce handoffs between source editing, preview, metadata, navigation, cover, and EPUB export. That scope can justify a trial, but it does not show that a copied EPUB project with one body edit, chapter rename, and replacement cover passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you inspect body, navigation, cover reference, and spine as separate outputs of one edit pass. Use another tool or destination check for the excluded range stated here: direct repair of an existing EPUB, Japanese vertical layout, and reader-specific cover display.
First task
For the search phrase “EPUB editing checklist,” the conclusion is to inspect body, navigation, cover reference, and spine as separate outputs of one edit pass. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for body revision, nav chapter name, cover reference, spine order, regeneration.
Begin here: create five result rows for one copied project. If body changes but navigation keeps the old name, stop at that row and return to its source. Check the Rune Studio product page for the current Mac feature scope before applying the same acceptance card to a product trial.
