ePublisher · Express

ePublisher Express.

A lightweight publishing seat that runs an existing Stationery without modifying it. Express scales the publishing seats on a documentation team without paying for design surface that only one or two team members need.


Introducing · 01

Introducing ePublisher Express.

Express runs the same publishing pipeline as ePublisher Designer — the same Stationery, the same conditions and variables, the same output targets — from a smaller, focused publishing surface. Native support for Adobe FrameMaker, Microsoft Word, Markdown++, and DITA XML means Express publishes directly from the source files the rest of your team already maintains. Output is bit-identical to a Designer-driven build given the same source and Stationery.

Why Express · 02

Why ePublisher Express?

01 · Scales the publishing seats

Express adds publishing capacity on a documentation team without paying for design surface that only one or two team members need. The Designer seat owns the Stationery; Express seats run it.

02 · Bit-identical output

Express runs the same pipeline as Designer. Given the same source documents and the same Stationery, the output is bit-identical — the seat the build runs from does not change what is shipped.

03 · Native source integration

Author in Adobe FrameMaker, Microsoft Word, Markdown++, or DITA XML — Express publishes from the same source files the rest of your team already maintains, with no intermediate export step.

04 · Reports on every build

Built-in reports on style usage, hyperlink integrity, 508 compliance issues, and broken cross-references — generated as part of the build so problems surface before content ships.

Key features · 03

Key features.

01 · Stationery compatibility

Express uses the same project Stationery the Designer seat authored — the same style mappings, conditions, variables, and output targets, without the design surface.

02 · Build reports

Each publish emits reports on style usage, hyperlink accuracy, and compliance issues — surfacing structural problems before they reach a reader.

03 · Table format handling

Tables retain source styling or follow target-specific overrides defined in the Stationery — consistent across web, print, and the rest of the output set.

04 · Configurable UI

UI elements can be enabled or disabled per team — Express seats see only the surface they need to run an existing pipeline.

05 · Same engine, smaller surface

Express does not include the design surface; it generates outputs from a project that Designer has already configured. The pipeline is identical.

Get started · 04

Add publishing seats without paying for design surface.

Express seats run the Stationery the Designer seat already authored. The pipeline is the same; the output is the same; the per-seat cost is lower for team members who do not need the design surface.

Contact WebWorks