The deterministic publishing engine that produces every output the WebWorks pipeline ships. Author once in Markdown++, Word, FrameMaker, or DITA — publish to every output format, and ship the AI-ready Knowledge Base archive on every Reverb 2.0 build.

Every Reverb 2.0 build produces the published HTML5 helpset and a matching Knowledge Base archive — markdown, one page per topic, with stable landmark IDs, ready to upload to WebWorks Platform. One deterministic pass; two artifacts; no second pipeline to maintain. The same source documents author the help your readers see and the input the AI retrieval layer answers from.
Author with your preferred source document type — Markdown++, Word, FrameMaker, or DITA XML.
Apply your project Stationery and produce every output target — including the matching Knowledge Base archive for AI retrieval — in a single pass.
Ship responsive HTML output, PDF, ePUB, Eclipse Help, and legacy formats — all from the same source project.
Author once and publish to every channel your readers depend on — modern web, print, digital book, in-app help, and the established formats long-running deployments rely on. ePublisher generates each output from the same source project, with shared styling, conditions, and variables across the set.
ePublisher's flagship web output. A responsive HTML5 helpset with full-text search, ARIA accessibility, and an AI-ready Knowledge Base built on every publish — generated from the same source documents your team already maintains.
Explore Reverb 2.0Browser-based online help that drops straight into your web application — collapsible navigation, full-text search, an index, and related-topics links. No server runtime, no portal framework.
Explore Print fidelity · PagedPrint-fidelity paged documents with page layout, headers, footers, and styling defined centrally in the project — applied uniformly across every input source.
Explore Digital book · IDPF standardStandard digital books that open on Adobe Digital Editions, Apple Books, and the e-readers, tablets, and publishing platforms your readers already use.
Explore IDE help · In-appHelp that lives inside the Eclipse IDE — HTML topics, an XML table of contents, and context plug-in mappings the Eclipse Help viewer expects.
Explore Migration on-rampThe migration on-ramp out of binary and proprietary formats. Convert FrameMaker, Word, DITA XML, and AsciiDoc into valid .md files that read in any Markdown tool — without losing structural intent.
Explore Established · CompatibilityHTML Help, Oracle Help, Sun JavaHelp, and WebWorks Help for long-running Windows, Java, and web help deployments — generated from the same source you already maintain.
ExploreOne deterministic pass produces every output target — modern web, print, digital book, in-app help, the established formats, and the Knowledge Files for AI retrieval — with consistent styling, conditions, and variables across the set.
Author in Markdown++, Microsoft Word, Adobe FrameMaker, or DITA XML — or mix all four in the same project. ePublisher applies the same Stationery, conditions, variables, and output targets across every source.
Tailor every aspect of your documentation through project Stationery — style mappings, target configuration, page templates — so output aligns with your design requirements and brand identity.
Define synonyms, set relevance rankings, configure interactive filters, and surface real-time search results in the published help — built into Reverb 2.0 on every publish.
ePublisher AutoMap runs the publishing pipeline unattended — scheduled jobs, CI/CD-driven publishes, and AI-agent-driven workflows all use the same CLI to refresh the help and the Knowledge Base archive on the cadence your team already uses.
From a handful of documents to a multi-thousand-topic library, ePublisher handles the full set in a single project — using local resources, with reproducible build times for any project of any size.
Reverb 2.0 emits Google Analytics GA4 events out of the box — see what readers search for, where they land, and which topics carry the load.
Conversion reports across styles, links, filenames, topics, images, baggage files, and conditions — the state of the whole project at a glance.
The command-line surface for the ePublisher publishing pipeline. Drives scheduled builds, CI/CD-driven publishes, and AI-agent-driven workflows from the same CLI — including refreshing the Knowledge Base archive on every Reverb 2.0 build.
ePublisher comes with people attached — documentation, a real support team, and a community that answers.
The full ePublisher documentation set, published as Reverb 2.0 — with WebWorks Wizard, the AI Assistant, answering questions right inside it.
Open a ticket in the Support Hub and it lands with people who work on the product. Prompt answers from staff, not a tier-one script.
The WebWorks Discord and Study Hall sessions put you in the room with other ePublisher users — and the developers.
Download the trial, or talk to us about Designer, Express, and AutoMap pricing for your team.