Projects and Publishing
Project
A .wep (ePublisher Designer) or .wrp (ePublisher Express) file recording your source documents, styles, and output targets. The two file formats are identical.
Stationery
A project used as a reusable template. Traditionally a .wxsp file saved from Designer; since 2026.1 an AutoMap job can also use a Designer project or another Express project directly as its stationery. A project used as stationery does not bundle its format files, so ePublisher Designer must be installed on the machine that builds from it.
Origin
The file a project or job takes its formatting from and stays linked to — a stationery, a Designer project, or another Express project. Synchronization compares against the origin. Not to be confused with the Platform's Origin Domains setting, which is an unrelated list of the web domains permitted to load the AI Assistant.
Output target
A named format configuration in a project or stationery that produces one output — for example, a target named Web Help configured as WebWorks Reverb 2.0. Target names may vary from team to team while the format stays the same, which is why federation matches on format, never on target name.
Group
A named set of source documents in a project or job — the authoring unit. In composable Reverb 2.0 output, one group's output is one parcel, and the group name is its identity in a federation.
Job
A .waj file — an AutoMap automation recipe: which project or stationery to use, which documents and groups to publish, which output targets to build, and where to deploy. For more information, see Scheduling and Integrating Processes with AutoMap.
Composition job
A .wacj file that assembles a site from its members' deployed output at a shared destination, without rebuilding them. For more information, see Federated Parcel Composition.
Launcher
The version-independent WebWorks.AutoMap.exe in the ePublisher program folder that scheduled tasks invoke; it starts the installed AutoMap version and relays its output.
Workspace
A set of AutoMap jobs that belong together, such as the jobs for one product or one release line: a jobs folder, a staging folder, and destinations that every job in the workspace can deploy to by name. The AutoMap Administrator shows one workspace at a time, and switching changes only what it shows. The Default workspace is the job folder and staging folder in the AutoMap preferences. Not to be confused with the conversion workspace. For more information, see Organizing Jobs into Workspaces.
Workspace settings file
The automap-workspace.xml file in a workspace's jobs folder that saves the workspace's destinations, so they travel with the jobs, for example into version control. It holds no credentials and can reference a separate deploy settings file. A job finds it by looking in its own folder and then the folders above it. For more information, see Workspace Destinations.
Evaluation workspace
The shared Quantum Sync Trial workspace that an interactive AutoMap installation sets up in Public Documents, with evaluation Stationery, source documents, and three ready-to-run jobs. Reset Evaluation Materials in the AutoMap preferences restores it. For more information, see Trying ePublisher AutoMap with the Quantum Sync Trial.
Conversion workspace
The temporary folders under `%TEMP%WebWorks` where ePublisher converts source documents while it generates output. It is not an AutoMap workspace. For more information, see Folders to Exclude.
Word session
One run of the hidden Microsoft Word that ePublisher starts to apply a project's settings to Word documents. The Documents per Word session setting on the Input Configurations tab of the Project Settings window (default 10) sets how many document conversions a session handles before ePublisher restarts Word; a document converted again for PDF output counts again. Word is also restarted before a retry and after a conversion that failed or needed a retry. For more information, see Input Configurations Tab (Project Settings Window).