The useful question behind “make an ebook for beginners” has one working answer: start with a text-led reflowable book whose content survives type-size changes. The controlled case is a short three-heading book with no page-position promise. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for reflow suitability, body structure, navigation, metadata, regeneration. The excluded range is stated separately: fixed-layout books, comics, and print-faithful design.
Decision: Start with a text-led reflowable book whose content survives type-size changes
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove reflow suitability, regeneration, or the stages between them.
The article-specific evidence card has these fields: reflow suitability, body structure, navigation, metadata, regeneration. Do not count the following excluded range as evidence: fixed-layout books, comics, and print-faithful design.
Keep this case tied to its source
Start with a three-heading, text-led book whose layout may reflow when the reader changes type size. Record heading structure, navigation, metadata, and reading order, generate the EPUB, and repeat after one heading edit. Do not promise fixed page positions, reproduce a print layout, or repair only the generated package.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to start with a text-led reflowable book whose content survives type-size changes. 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.
Run order and evidence
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. Limit the first book to reflowable content. Attach the observed reflow suitability evidence to this step.
- 2. Divide the body under three headings. Attach the observed body structure evidence to this step.
- 3. Record metadata and reading order. Attach the observed navigation evidence to this step.
- 4. Generate and change the reader type size. Attach the observed metadata evidence to this step.
- 5. Rename one heading in source and rebuild. Attach the observed regeneration evidence to this step.
What each row must prove
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Reflow suitability — expected state: written before the run; hold the row if fixed page positions are promised.
- Body structure — expected state: written before the run; hold the row if a print layout is copied unchanged.
- Navigation — expected state: written before the run; hold the row if only the generated package receives the correction.
- Metadata — expected state: written before the run; hold the row if fixed page positions are promised.
- Regeneration — expected state: written before the run; hold the row if a print layout is copied unchanged.
Do not hide these blockers
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. Fixed page positions are promised; return to the named source.
- 2. A print layout is copied unchanged; preserve the failed artifact.
- 3. Only the generated package receives the correction; change only the responsible condition.
A product check without a performance claim
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 short three-heading book with no page-position promise passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you start with a text-led reflowable book whose content survives type-size changes. Use another tool or destination check for the excluded range stated here: fixed-layout books, comics, and print-faithful design.
Start with the smallest revealing case
For the search phrase “make an ebook for beginners,” the conclusion is to start with a text-led reflowable book whose content survives type-size changes. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for reflow suitability, body structure, navigation, metadata, regeneration.
Begin here: outline a three-heading reflowable sample. If fixed page positions are promised, 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.
