The shortest useful answer to the search phrase “how to make an ebook” is this: separate source, reading order, metadata, navigation and cover, generation, and reader verification. The controlled case is a 20,000-word three-chapter story with one cover and a small metadata sheet. A pass must demonstrate this outcome: move a three-chapter book from frozen source to reader check through six visible checkpoints. The excluded range is stated separately: retailer setup, pricing, tax, and fixed-layout production are outside this guide.
Decision: Separate source, reading order, metadata, navigation and cover, generation, and reader verification
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove source identity, reader display, or the stages between them.
The article-specific evidence card has these fields: source identity, reading order, metadata, navigation and cover, EPUB structure, reader display. Do not count the following excluded range as evidence: retailer setup, pricing, tax, and fixed-layout production are outside this guide.
The exact sample and its return path
Use a 20,000-word three-chapter story with one cover and a small metadata sheet. The decisive fields are source identity, reading order, metadata, navigation and cover, EPUB structure, reader display; keep the three stop conditions visible throughout the run.
This case addresses the failure behind the search: building the cover or contents before deciding which manuscript controls the book. 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.
Operation order
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. Freeze a copied manuscript set. Attach the observed source identity evidence to this step.
- 2. Assign chapter IDs and reading order. Attach the observed reading order evidence to this step.
- 3. Record metadata navigation and cover separately. Attach the observed metadata evidence to this step.
- 4. Generate and inspect nav and spine. Attach the observed navigation and cover evidence to this step.
- 5. Change one sentence and regenerate before two reader checks. Attach the observed EPUB structure evidence to this step.
Acceptance fields
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Source identity — expected state: written before the run; hold the row if the editable source is ambiguous.
- Reading order — expected state: written before the run; hold the row if navigation and spine order disagree.
- Metadata — expected state: written before the run; hold the row if the second build loses the correction or settings.
- Navigation and cover — expected state: written before the run; hold the row if the editable source is ambiguous.
- EPUB structure — expected state: written before the run; hold the row if navigation and spine order disagree.
- Reader display — expected state: written before the run; hold the row if the second build loses the correction or settings.
Stop conditions and repair routes
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. The editable source is ambiguous; return to the named source.
- 2. Navigation and spine order disagree; preserve the failed artifact.
- 3. The second build loses the correction or settings; change only the responsible condition.
Rune Studio as a bounded candidate
Current product documentation covers capabilities relevant when you need to keep manuscript, order, metadata, navigation, cover, and colophon in one production record. That scope can justify a trial, but it does not show that a 20,000-word three-chapter story with one cover and a small metadata sheet passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you separate source, reading order, metadata, navigation and cover, generation, and reader verification. Use another tool or destination check for the excluded range stated here: retailer setup, pricing, tax, and fixed-layout production are outside this guide.
Conclusion
For the search phrase “how to make an ebook,” the conclusion is to separate source, reading order, metadata, navigation and cover, generation, and reader verification. The result is accepted only when the record establishes this outcome: move a three-chapter book from frozen source to reader check through six visible checkpoints.
Begin here: label the three chapters and create an empty six-row production card. If the editable source is ambiguous, 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.
