AI-Ready Documentation — End to End

AI-ready documentation, line by line.

From AI-friendly source authoring to an AI Assistant that answers from your own content, in your published help and on your website. One pipeline, four layers, your documentation answering your users' questions.

static.webworks.com / docs / epublisher / latest / help
WebWorks Wizard answering a setup question inside the live ePublisher help, with step-by-step instructions and numbered citations.
WebWorks Wizard · The AI Assistant answering in our own live docs

The pipeline · 01–04

AI-readiness has layers. We ship all of them.

AI-assisted help takes four layers: a source format AI models can read, the publishing engine that builds your help, a cloud service that retrieves answers from your own documentation, and the published page that hosts the chat. WebWorks ships all four.

publishing.md Markdown++
<!--#publishing-intro-->
# Publishing Your First Project

ePublisher converts your source documents into a fully indexed
help system in a single pass. To publish a project:

- Open your project in ePublisher Designer
- Select your target from the **Targets** panel
- Click **Publish** to generate the output

<!--condition:reverb-2-->
For Reverb 2.0 targets, confirm your Assistant ID is set under
**AI integration** in Target Settings before publishing.
<!--/condition-->
Layer 01 · Source format

Markdown++. The source AI reads fluently.

Markdown++ extends CommonMark with invisible directives for structured authoring — and stays plain text end to end, the format AI language models read most fluently. Every Markdown++ file is a valid Markdown file. The 1.0 specification is open under the MIT license.

Explore Markdown++
Layer 02 · The publishing engine

ePublisher. The engine that ties it together.

ePublisher is the publishing engine. Author in FrameMaker, Word, DITA, or Markdown++, and one deterministic pass produces every output format — and, on every Reverb 2.0 build, the matching Knowledge Files the AI retrieval layer answers from. Enabling AI-assisted help becomes a configuration change in your existing pipeline, not a new platform to deploy.

01 · Source

Author in your format

FrameMaker, Word, DITA, or Markdown++. ePublisher handles the source structure your team already writes in.

02 · Build

Generate the helpset

A single pass produces both the Reverb 2.0 HTML output and the matching Knowledge Files for upload to Platform.

03 · Output

Ship AI-ready help

Deploy the helpset to your hosting. The AI Assistant in the help calls Platform and returns annotated answers from your own documentation.

Explore ePublisher
Layer 03 · AI infrastructure

WebWorks Platform. Where the AI lives.

The cloud service behind the AI Assistant. Platform hosts the Knowledge Bases ePublisher generates, imports your website too, and runs a fresh search for every question. You configure Assistants and their Instructions in Platform; your help and your website invoke what's set up.

Discover WebWorks Platform
ePublisher Generates Knowledge Files alongside Reverb 2.0 output.
Platform Hosts the Assistant. Runs fresh per-query retrieval. Returns annotated answers.
Reverb 2.0 Renders the chat surface alongside topic pages.
Knowledge Files Assistant ID Annotated answers

The same Assistant runs on any website with one line of script. Meet the AI Assistant

Layer 04 · Published experience

The AI Assistant. What end users see.

Inside Reverb 2.0 published help, the AI Assistant is the specialist — same page, no separate login. Every question runs a fresh retrieval against your published documentation, and answers cite the specific topics they came from. On your website, the same Assistant works as the generalist.

AI Assistant · Help Center ● Online
How do I configure the Assistant ID for my Reverb 2.0 target?
Reverb 2.0 reads the Assistant ID from your project's Target Settings[1]. Open the Targets panel in ePublisher Designer, select your Reverb 2.0 target, and paste the ID into the Assistant ID field under AI integration[2].
Where do I find the Assistant ID in Platform?
In Platform, open Assistants from the left navigation. Each assistant card shows its ID under the title[3]. Click the copy icon to copy it to your clipboard, then paste it into the Reverb 2.0 target settings in ePublisher.
In practice

Customers shipping with WebWorks.

"I have been using ePublisher to produce Online Help since 2001 as an employee and independent consultant. ePublisher's intuitive WYSIWYG interface and customizable output make it my top choice. Support is prompt, helpful, and goes the extra mile. ePublisher Express allows clients to make minor updates themselves. Overall, ePublisher simplifies documentation projects with its ease of use, flexibility, and outstanding service"

Tammy · Independent Consultant

"...so we ran the user guide through ePublisher Express and in less than 5 minutes had a deliverable Help system. This was done without any adjustments to the FM book. With my demanding schedule these days, I couldn't be happier that I made the decision change to WebWorks ePublisher...."

Pamela · Technical Writer
Trusted across industries
WebWorks customer logos
Get started

Ready to ship AI-ready documentation?

Start with the source format, the publishing pipeline, or the Platform service that hosts your Assistants. Every layer interoperates, and you can adopt them in any order — or start with the AI Assistant on the website you already have.

Talk to WebWorks Put the AI Assistant on your website