ePublisher AutoMap.
The command-line automation layer that runs ePublisher publishing pipelines unattended. Schedule large jobs, drive CI/CD builds, and refresh the Reverb 2.0 helpset and Knowledge Base archive on the cadence your team already uses — including from an AI agent.
Introducing ePublisher AutoMap.
ePublisher AutoMap is the command-line surface for the ePublisher publishing pipeline. It supports both
Designer projects (.wep) and Express projects (.wrp); recent enhancements include
--skip-reports for faster CI/CD builds on large projects. Scheduled and CI/CD-driven runs
republish the help and refresh the matching Knowledge Base archive on the cadence your team already uses —
with email notifications when jobs finish, and pre- and post-generation script hooks where deeper integration
is required.
Why ePublisher AutoMap?
AutoMap is what makes "AI-ready output as a byproduct of every publish" practical without a human in the publishing seat. Scheduled and CI/CD-driven runs republish the help and refresh the Knowledge Base archive on the cadence the team already uses.
AutoMap's CLI shape — explicit project file, target name, output directory, optional flags — is operable by automation and by AI agents alike. The publishing pipeline becomes part of the AI-driven authoring loop.
AutoMap drives both Designer projects (.wep) and Express projects (.wrp) — the same engine, the same Stationery, the same output set. Recent additions include --skip-reports for faster CI/CD builds on large projects.
Works with nearly any version control or content management system. Pre-generation and post-generation scripts handle source retrieval, asset staging, and post-build deployment.
The publishing pipeline an AI agent can drive.
AutoMap's strategic positioning beyond CI/CD is as the publishing-pipeline surface that AI agents can natively operate. Agents draft Markdown++; agents publish via AutoMap; the resulting Reverb 2.0 helpset and Knowledge Files refresh on agent-driven cadence. No GUI in the loop; no human in the seat; the output is the same build a human triggers from Designer.
Documentation teams that author in Markdown++ have a source format that AI agents can read, interpret, and modify directly. Plain text in, plain text out — no XML overhead, no proprietary binary format.
An agent that has authored or modified a Markdown++ source can invoke AutoMap to publish it — running the same pipeline a human triggers from Designer. Explicit project file, target name, output directory, optional flags.
A WebWorks Claude Code skill pack — public on GitHub — teaches an AI agent how to traverse ePublisher projects, run AutoMap pipelines, customize outputs, and apply WebWorks conventions. Ready-to-use AI tooling for ePublisher today.
quadralay/webworks-claude-skillsKey features.
Generate all or selected output targets from a single AutoMap invocation — Reverb 2.0 helpset, Knowledge Base archive, PDF, ePUB, Eclipse Help, and the rest of the project Stationery configures.
Built-in script editor with environment variables for pre-generation source retrieval and post-generation deployment — the publishing pipeline integrates cleanly with the build environment around it.
A complete command-line interface drives every operation. AutoMap runs on developers’ machines, in GitHub Actions, in Jenkins, and in any CI/CD environment that can invoke a Windows binary.
Take the publishing seat out of human hands.
Scheduled builds, CI/CD-driven publishes, and AI-agent-driven workflows all use the same AutoMap CLI. Talk to us about pricing for your team.
Contact WebWorks