The deciding move behind the search “how to make reflowable EPUB” is not another feature: design body meaning with headings, paragraphs, and reading order rather than page numbers. The controlled case is one practical nonfiction chapter with three headings, one short table, and one image. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for heading structure, paragraphs, image reference, spine order, type-size change. The excluded range is stated separately: fixed-layout comics, print PDF, and Japanese vertical layout.
Decision: Design body meaning with headings, paragraphs, and reading order rather than page numbers
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove heading structure, type-size change, or the stages between them.
The article-specific evidence card has these fields: heading structure, paragraphs, image reference, spine order, type-size change. Do not count the following excluded range as evidence: fixed-layout comics, print PDF, and Japanese vertical layout.
The exact sample and its return path
Use a three-section nonfiction sample with one image and deliberately remove meaning that depends on fixed page numbers. Structure it with headings and paragraphs, give the image alternative text and a relative reference, generate a reflowable EPUB, and vary viewport and type size in Previewer. Reading order must survive those changes.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to design body meaning with headings, paragraphs, and reading order rather than page numbers. 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.
Five actions from source to result
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. Find fixed-page assumptions. Attach the observed heading structure evidence to this step.
- 2. Move meaning into headings and paragraphs. Attach the observed paragraphs evidence to this step.
- 3. Add alternative text and a relative image reference. Attach the observed image reference evidence to this step.
- 4. Generate a reflowable EPUB. Attach the observed spine order evidence to this step.
- 5. Change viewport and type size in Previewer. Attach the observed type-size change 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.
- Heading structure — expected state: written before the run; hold the row if meaning depends on page breaks.
- Paragraphs — expected state: written before the run; hold the row if essential information exists only inside an image.
- Image reference — expected state: written before the run; hold the row if reading order breaks after type-size changes.
- Spine order — expected state: written before the run; hold the row if meaning depends on page breaks.
- Type-size change — expected state: written before the run; hold the row if essential information exists only inside an image.
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. Meaning depends on page breaks; return to the named source.
- 2. Essential information exists only inside an image; preserve the failed artifact.
- 3. Reading order breaks after type-size changes; change only the responsible condition.
Separate product scope from your result
Current product documentation covers capabilities relevant when you need to preserve manuscript order and metadata, generate EPUB 3, and inspect the resulting structure. That scope can justify a trial, but it does not show that one practical nonfiction chapter with three headings, one short table, and one image passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you design body meaning with headings, paragraphs, and reading order rather than page numbers. Use another tool or destination check for the excluded range stated here: fixed-layout comics, print PDF, and Japanese vertical layout.
Conclusion
For the search phrase “how to make reflowable EPUB,” the conclusion is to design body meaning with headings, paragraphs, and reading order rather than page numbers. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for heading structure, paragraphs, image reference, spine order, type-size change.
Begin here: mark every fixed-page dependency in a three-section sample. If meaning depends on page breaks, 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.
