Consider an original volunteer handbook with sections for opening the room, welcoming visitors, and closing for the evening. Its website also has a navigation bar and a signup form. Readers need the instructions in their ebook library, but those website controls do not belong between the handbook's chapters.
Prepare a reading copy of the HTML
Keep the website source unchanged. Make a separate handbook.html containing the handbook text, its headings, and the images that explain an instruction. Remove site navigation, cookie notices, signup controls, and duplicate mobile navigation from this reading copy.
The opening structure might be:
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Visitor-room volunteer handbook</title>
</head>
<body>
<h1>Opening the room</h1>
<p>Collect the room key from the reception desk.</p>
<h1>Welcoming visitors</h1>
<p>Show visitors where to leave wet umbrellas.</p>
<h1>Closing for the evening</h1>
<p>Return the room key to the reception desk.</p>
</body>
</html>
These are fictional instructions for a conversion fixture. Replace them with the actual approved procedure. Use heading levels to express chapters and subsections; changing a paragraph's font size does not give it that structure.
Create the ebook from the source folder
After installing Pandoc through its official installation instructions, open a terminal in the folder containing the reading copy and run:
pandoc handbook.html -o handbook.epub --toc --metadata title="Visitor-room volunteer handbook" --metadata lang=en-US
This is a command for your local installation, not a generated ebook attached to this article. The explicit metadata identifies the publication; do not fill an author field with a person who did not author or approve it.
If an instruction refers to images/key-return.jpg, retain that image in the matching folder and review any resource warnings from the conversion. Open the resulting book and inspect that exact instruction. A completed command is not sufficient evidence that every diagram was included.
Pandoc reads HTML into its document representation and writes an ebook. Expect to review formatting rather than preserve every web-specific style. A wide scheduling grid may need to become a list of shifts; a chart that only appears after JavaScript runs needs a deliberate static image or a text explanation.
Use calibre when you prefer a conversion window
An installed calibre application provides another route. Add the local HTML file, select its library entry, and use Convert books with EPUB as the output format. Review the title, author, and table-of-contents settings before conversion. Calibre's conversion documentation explains how its input, structure detection, and output stages relate.
For a handbook spread across linked HTML files, prepare a clear starting file and retain its dependent files together. Calibre's conversion behavior for linked documents needs inspection: a navigation link that belongs to the website should not quietly add unrelated pages to the book. Review the resulting chapter list, rather than assuming the converter knows where your handbook ends.
Pick one route, inspect its output, and correct the source or settings responsible for any problem.
Read the EPUB as a book
Open it in the reading application your recipients use. Select the closing chapter from the contents, increase the font size, and confirm the key-return instruction remains in order. Check each essential image, any link back to a source, and the transition between chapters.
Look for repeated headings, website menus that slipped into the text, and images that communicate an instruction without a useful text alternative. A converter can produce a file that opens while still producing a poor handbook.
The EPUB format explanation covers why reflow differs from fixed pages. Keep the final EPUB for the ebook-reading task and retain the source HTML with its supporting files. When an instruction changes, update that source, regenerate the book, and replace the distributed edition through your normal handbook process.