Antechinus eBook Wizard: Master eBook Creation in Minutes

Antechinus eBook Wizard Essentials: Workflow, Best Practices, and Export Settings

Overview

Antechinus eBook Wizard is a fictional (or niche) eBook production tool focused on streamlining manuscript-to-published-book workflows. Below is a practical, prescriptive guide covering a typical end-to-end workflow, recommended best practices to avoid common pitfalls, and concise export settings for popular eBook platforms (EPUB, Kindle MOBI/AZW3, PDF).


Workflow (step-by-step)

  1. Prepare source manuscript

    • Use a clean, consistent source (preferably DOCX or Markdown).
    • Apply semantic styles (Heading 1–3, Normal, Blockquote, Caption) rather than manual formatting.
  2. Import into Antechinus

    • Import DOCX/Markdown. Let the wizard map styles automatically; verify mapping for headings, captions, and lists.
  3. Structure and metadata

    • Check/assign front matter: title page, copyright, dedication, contributor list.
    • Enter metadata: Title, Author, Publisher, ISBN, Language, Publication Date (use today’s date if publishing now: February 8, 2026).
    • Add keywords and categories for discoverability.
  4. Apply template and typography

    • Choose a template that matches genre (fiction, non-fiction, textbook).
    • Set base font family and size (serif 11–12pt for body; sans-serif for manuals).
    • Configure line-height (1.2–1.4) and paragraph spacing; avoid manual line breaks.
  5. Images, tables, and media

    • Use high-resolution images (300 dpi for print/PDF; 150–300 px for EPUB).
    • Optimize images (JPEG for photos, PNG for line art) and compress (keep visual quality).
    • Use captions and alt text for accessibility.
  6. Chapters, navigation, and TOC

    • Ensure consistent heading levels to auto-generate TOC.
    • Create a navigable NCX/HTML TOC for e-readers and a detailed PDF TOC for print.
  7. Accessibility & validation

    • Add alt text for all images and semantic HTML for lists/tables.
    • Run accessibility checks (reading order, headings, language declaration).
  8. Proof and test

    • Use previewer to test on multiple reading scenarios (mobile, tablet, large font).
    • Export test EPUB and load into Calibre, Kindle Previewer, and a native device app.
    • Fix any layout or reflow issues.
  9. Finalize metadata and covers

    • Design cover at correct dimensions (see Export Settings).
    • Embed metadata and ensure ISBN and rights information are correct.
  10. Export and publish

  • Export to required formats (EPUB, AZW3, PDF).
  • Run final validation (EPUBCheck for EPUB).
  • Upload to distribution platforms (KDP, Apple Books, Draft2Digital) following each platform’s specific requirements.

Best Practices (concise)

  • Semantic styling: Use styles, not manual fonts/spacing.
  • Single-source truth: Keep master file in one format (DOCX or Markdown) and regenerate outputs from it.
  • Image optimization: Resize and compress before importing.
  • Consistent headings: Prevent TOC and navigation issues.
  • Accessibility: Alt text, language tags, and proper reading order.
  • Version control: Save iterative versions (v1_manuscript.docx).
  • Backup: Export backups of final EPUB/PDF and source files.
  • Test widely: Preview on multiple readers and with large-font reflow.
  • Style guide: Follow a brief style guide (hyphenation, em/en dashes, ellipses, punctuation around quotes).

Export Settings (recommended)

EPUB (reflowable)

  • MIME: EPUB 3.2 compatible
  • Base font embedding: subset common web fonts; rely on system fonts for readers.
  • Images: max width 1600 px; 150–300 dpi; compress to web-optimized sizes.
  • CSS: responsive, avoid fixed widths; use rem/em for scalable text.
  • Navigation: HTML TOC + NCX fallback.
  • Metadata: Dublin Core fields populated; cover image embedded.
  • Validation: Run EPUBCheck (no fatal errors).

Kindle (AZW3 / KF8)

  • Container: AZW3 preferred for advanced formatting; MOBI legacy only if required.
  • Fonts: Embed fonts if specific typography is essential (be mindful of file size).
  • Images: max width 1400–1600 px; compress.
  • CSS: avoid unsupported properties; test in Kindle Previewer.
  • TOC: HTML TOC and NCX; ensure Kindle conversion maps headings properly.

PDF (print-ready)

  • Page size: Choose Trim size (e.g., 6”×9”) or A4 as required.
  • Resolution: 300 dpi for images; CMYK if sending to print.
  • Fonts: Embed all fonts.
  • Bleed: Add 3 mm/0.125” bleed if printing to edge.
  • Margins: Ensure inner gutter allowance for bound books.
  • Output intent: Include PDF/X or press-ready settings if sending to a printer.

Cover specs

  • EPUB cover: 1600×2560 px (minimum 1400×2000), RGB, JPEG/PNG.
  • Kindle cover (KDP): 2560×1600 px recommended, RGB, JPEG, <50MB.
  • Print cover: Full wrap with spine — use exact PDF with bleed and spine measurements based on page count.

Quick checklist before publishing

  • Metadata complete and accurate (ISBN, date: February 8, 2026).
  • EPUBCheck passed; Kindle Previewer shows no errors.
  • Cover meets platform specs.
  • Images optimized and alt-texted.
  • Final proof read on at least two devices.
  • Backups of source and exported files stored.

If you want, I can convert this into a printable checklist or a template workflow file (DOCX or Markdown).

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *