From AI-friendly source authoring to in-output chat backed by your own published documentation. One pipeline, three layers, your documentation answering your users' questions.

AI-assisted help has three moving parts: a source format AI models can read, a published help page that hosts the chat, and a cloud service that retrieves answers from your own documentation. WebWorks ships all three — and the publishing engine that ties them together.
<!--#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-->
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++The cloud service for AI-assisted help. Platform hosts the Knowledge Bases generated by ePublisher and runs fresh per-query retrieval for every end-user question. Documentation teams configure Assistants and the customer prompt in Platform; the published help just invokes what's set up.
Discover WebWorks PlatformIn-output AI integration. Reverb AI chat ships inside Reverb 2.0 published help — same page, no separate login. Every question runs a fresh retrieval against your published documentation, and answers include annotation links back to specific topics in the help.
See Reverb 2.0ePublisher is the publishing engine. Where it fits in the AI-readiness story: every Reverb 2.0 build also generates a matching set of Knowledge Files for upload to Platform — one markdown page per HTML page, sharing the helpset's landmark IDs. Enabling AI-assisted help becomes a configuration change in your existing pipeline, not a new platform to deploy.
FrameMaker, Word, DITA, or Markdown++. ePublisher handles the source structure your team already writes in.
A single pass produces both the Reverb 2.0 HTML output and the matching Knowledge Files for upload to Platform.
Deploy the helpset to your hosting. Reverb AI chat invokes the Platform Assistant and returns annotated answers from your own documentation.
"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"
"...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...."

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.
Talk to WebWorks