Docs & Guides

eBooks

Collect deeper guides for teams planning content automation, creative operations, and API-based rendering.

Read the Docs

eBooks workflow

eBooks is set up for teams that need repeatable, template-driven output instead of one-off manual design work.

  • Connect long-form guides to uploaded assets, approved templates, and API-safe render jobs.
  • Keep all remote image dependencies blocked so production renders use controlled assets only.
  • Use idempotency keys when the same request can be retried by an automation tool.

What this page covers

Collect deeper guides for teams planning content automation, creative operations, and API-based rendering.

  • Use guides for planning before implementation.
  • Share workflow requirements with design and engineering.
  • Turn recommendations into testable acceptance criteria.

Production checklist

Before using this workflow in a campaign, validate the template, expected dimensions, asset ownership, and output access path.

  • Render the same payload three times and compare output hashes for deterministic behavior.
  • Confirm local fonts are present in the approved whitelist before launch.
  • Monitor completed and failed jobs from the logs page during rollout.