What you need before you start
You need an editable manuscript, a way to export it, and a real use for the finished file. A short guide for your clients can start in the writing tool you already use. A retail reading edition also needs chapter navigation and a format your distributor accepts. Choose that destination before designing pages.
This walkthrough uses an invented example: a designer turning workshop notes into a website-handoff guide for first-time clients. The finished package contains a reading guide, a file checklist and one task the client can complete unaided. Use the sequence for another topic by replacing the task and source material.
- Writing tool: it must let you change chapter order and edit the text. If someone else will review it, agree on the handoff format first.
- Source folder: keep your original notes, allowed examples, image originals and references outside the only copy of the draft.
- Test reader: find someone with the intended reader's starting knowledge. A colleague who already knows the method may fill in gaps without noticing.
Example: turn scattered notes into a six-chapter ebook
Suppose you have a workshop recording, two onboarding documents, and notes from client calls. The topic is freelance project handoffs. The reader is a designer handing a completed website to a client for the first time. The promised result is a handoff folder the client can use without another call.
- Agree what is being handed over. Produce a deliverables list with a named approver.
- Collect the files. Use a folder example to separate editable sources, finished assets, and instructions.
- Transfer access safely. List accounts and owners; keep passwords out of the ebook and the sample folder.
- Teach the recurring task. Show one annotated example of updating a page, using an interface you can verify.
- Run the acceptance check. Ask the client to find a file and complete that update using only the guide.
- Define what happens next. Record the support period, unresolved issues, and where future requests go.
This is a hypothetical structure, not a tested client outcome. Notice the reusable outputs: the file list becomes the folder structure, and the instructions become the acceptance test. Remove material from the workshop that does not help produce one of those outputs.
How long should the ebook be?
Estimate from the tasks. For this example, six chapters of about 800 words plus 1,200 words of introduction and reference material would total roughly 6,000 words. That is a planning estimate, not a target to pad toward. Add space when a necessary example is missing; cut a chapter when another already answers its question. Page count will change with typography, images, and ebook-reader settings.
Start from a topic, notes, or an existing draft
| You have | First action | Do not do yet |
|---|---|---|
| A topic only | Interview potential readers and collect the decisions or tasks they struggle with. | Generate a long chapter list from the topic alone. |
| Notes, talks, or course material | Sort the material by reader problem, evidence, example, and repeated idea. | Paste everything into a draft and preserve its original order. |
| A rough manuscript | Write a one-line job for every existing chapter and identify missing transitions. | Begin sentence polishing before testing the structure. |
| A finished document | Audit rights, navigation, accessibility, links, and destination-specific format behavior. | Assume a successful export is a validated ebook. |
How to create an ebook in eight steps
- Stage 01
Write the reader promise
Name one reader, the situation they are in now, and the change the book should help them make. A useful promise is observable: the reader can make a decision, complete a task, avoid a mistake, or understand a system after reading.
Keep before continuing: A one-sentence outcome that can reject irrelevant chapters.
- Stage 02
Inventory the source material
Separate what you know from what you need to verify. Gather interviews, notes, original examples, data, citations, permissions, and open questions. Mark anecdotes as anecdotes and claims as claims; they need different editorial treatment.
Keep before continuing: A source map with evidence, examples, and unresolved questions.
- Stage 03
Choose the destination and working format
Decide whether readers will receive a retail ebook, a direct-download document, or another deliverable. This affects navigation, page-dependent design, image treatment, and the final export. Keep an editable master even when the final book will be EPUB or PDF.
Keep before continuing: A declared primary output and an editable source file.
- Stage 04
Build an argument, not a pile of chapter names
Give every chapter a job. Write the question it answers, the new understanding it creates, the evidence or example it needs, and the handoff to the next chapter. If two chapters do the same job, combine them before drafting.
Keep before continuing: A chapter map that shows progression and dependencies.
- Stage 05
Draft in bounded sections
Draft one section against its brief, then compare the result with the source map. Add the author-specific examples while the context is fresh. Leave visible notes where a fact, permission, quote, or demonstration still needs work.
Keep before continuing: A complete draft with uncertainty exposed, not hidden.
- Stage 06
Revise in separate passes
First test the book-level logic. Then check evidence, usefulness, repetition, voice, transitions, and sentence clarity in distinct passes. Mixing all of these at once encourages cosmetic edits while structural problems survive.
Keep before continuing: A manuscript whose claims and sequence have been deliberately reviewed.
- Stage 07
Add only visuals that perform a job
Use a diagram when relationships are hard to explain linearly, a screenshot when interface state matters, and a table when exact comparisons matter. Supply captions or text alternatives according to purpose, and keep licensing records for every asset.
Keep before continuing: A visual plan tied to comprehension, not empty decoration.
- Stage 08
Export, inspect, and correct the artifact
Open the final file outside the writing environment. Use the table of contents, follow links, change text size where the format allows it, inspect page breaks, and test on more than one screen. Fix the source, export again, and repeat until the deliverable, not merely the editor view, works.
Keep before continuing: A tested release candidate and a reusable master manuscript.
Turn source notes into a useful chapter
Take chapter two from the handoff example: collecting the project files. A workshop note might say, “Clients keep asking which logo to use. Send source files and explain the difference.” Copying that sentence into an ebook leaves the reader with the same unanswered question.
1. Decide what the reader must produce
The chapter should leave the client with a folder they can navigate. Its output is a file index with three columns: filename, intended use and whether the client can edit it. This determines the explanation you need; a history of logo design does not.
2. Draft the example before the surrounding advice
| File | Use it for | Editing note |
|---|---|---|
| logo-dark-transparent.png | The approved dark logo on a light background. | Place it at its original proportions; use the source file for design changes. |
| logo-source.svg | Supplying the logo to a designer who needs an editable vector. | Keep the approved original before changing shapes or colors. |
| home-banner.jpg | The website's existing home-page banner. | A replacement needs the same intended crop, not merely the same filename. |
3. Write the explanation around a choice
“To place the logo on a light slide, use logo-dark-transparent.png. To change the logo design, give the designer logo-source.svg. Keep the original files in a separate folder. If you cannot tell which version was approved, ask the project owner before replacing the website asset.”
The paragraph names a situation, a file, a choice and a fallback. Check these instructions against the actual files in your own project. Filenames in this example describe an invented package; they are not a universal naming standard.
4. Look for the missing prerequisite
Give the example to a reader and ask them to choose the file for a light slide. If they ask what a transparent background is, add one small comparison or explain that term. If they select the right file but distort it, add a proportion check. These observations tell you what to write next more reliably than adding a generic “best practices” section.
For AI-assisted drafting, supply the checked file index and the exact reader task as the section brief. The AI writing guide shows how to separate supplied facts from details a model invents.
Ebook publishing checklist
- The title, subtitle, introduction, chapter sequence, and conclusion all promise the same book.
- Every factual claim that matters has been verified against an appropriate source.
- Quotes, images, and third-party material have documented permission or a valid basis for use.
- Headings are structural, not manually enlarged paragraphs, and the hierarchy does not skip without a reason.
- The table of contents matches the final structure and its links work.
- Examples are specific enough for the reader to recognize a good and bad application.
- Images have an editorial purpose, an appropriate text alternative, and a readable caption where needed.
- Front matter, author information, references, and calls to action point to current destinations.
- A final proofread happened after layout or conversion, because conversion can introduce new defects.
Test the download and the instructions separately
A file can open correctly while its instructions fail. Run two checks: can the recipient get and navigate the book, and can they do the promised task using it?
- Send the exact release file. Give the test reader the same link or attachment a customer would receive. An editor preview bypasses possible download, account-access and filename problems.
- Give a task without coaching. For the handoff example: “Find the approved logo for a light presentation slide and explain where you would request a design change.” Ask the reader to narrate where they look.
- Record the first point of confusion. “Could not find the file index” needs a navigation repair. “Found it but chose the wrong logo” needs clearer instructions or an example. “Link opens a permission error” needs a delivery repair.
- Change the cause, then repeat. Adding a longer introduction will not repair a broken permission setting. Fix the index, explanation or link, export again and repeat the failed task with the corrected file.
For EPUB, also enlarge the reading font, follow every chapter link and inspect the widest table. For PDF, open the file on a phone and print a worksheet page if printing is part of the promise. The format guide explains how to diagnose conversion problems.
Deliver a small, understandable package
For a direct download, use descriptive filenames such as website-handoff-guide-v1.pdf and handoff-file-index-v1.pdf. Tell readers which file to open first and which one to complete. Put a working contact or correction link inside the guide, so a forwarded copy still has a way to report errors. When you issue a correction, update both the download and the source manuscript; otherwise the next export can reintroduce the old mistake.
Amazon KDP formats and content requirements
Retailers and distribution services can change accepted inputs and content requirements. If Amazon KDP is one of your destinations, verify the current supported ebook manuscript formats before upload and review the KDP Content Guidelines. Those official pages, not a static checklist, are the source of truth for current platform rules.
- W3C EPUB 3.3: the normative specification for the EPUB format.
- Amazon KDP: supported ebook manuscript file formats: current input-format documentation.
- Amazon KDP Content Guidelines: current platform content guidance.
- W3C WAI image tutorials: purpose-based guidance for accessible images.
Build your first chapter outline
Write the promise at the top of a new document, list the five to eight questions a reader must answer to reach it, and arrange those questions in dependency order. That is the beginning of a working outline. You can develop it with the book outline generator or see how the AI ebook generator organizes the broader workflow.