Single File Publisher

Overview

The Single File Publisher provides a focused, lightweight workflow for publishing a single DITA/DITAMAP source or a single output package to the target InfoDev servers. It is ideal when you want to quickly publish one document without creating or managing a PubAssist profile.

Key Features

Quick publish workflow — Select a single source or package and publish directly to a target server.
Target selection — Choose dev/stg/tst/prod targets and folder locations for output.
Progress and logs — See real-time progress, stage-by-stage messages, and error details.
Preview output — Optionally preview the output location or generated files before publishing.
Retry and cleanup — Retry failed steps and automatically clean up temporary files when appropriate.

Publishing Quick Steps

Open Single File Publisher — From the main navigation choose Single File Publisher.
Select source — Click Choose file and pick the DITA source, map, or package to publish.
Choose target — Select the target server and destination folder where the output should be published.
Configure options — (Optional) Set publishing options such as build profile, enable preview, or preserve intermediate files.
Start publish — Click Publish to queue and run the publishing process. Monitor progress in the status panel.
Review results — When finished, open logs or the published output to verify successful publishing.

Single File Publisher — Features in Detail

Source Selection

You can select a single source file (DITA, XML, or a transformed output package). If you select a map, the publisher will build the map and its referenced content. The UI validates basic file types and gives a warning for unsupported formats.

Target and Destination

Choose one of the predefined server targets (dev, stg, tst, prod). For each target you can select or type a destination folder. Use the folder browser if available to avoid typographical errors.

Build and Publish Options

Build profile: Select a build/transform profile if your project provides multiple output presets.
Enable preview: Generate the output locally and preview the main HTML/landing page before copying to the remote server.
Preserve intermediate files: Keep temporary files for debugging in case of failures.

Progress and Logs

The publisher displays a progress panel with stage names (transform, copy, deploy), percentage, and a running log. Errors appear inline with details and a suggested next action where available.

Retry and Cleanup

If a publish fails, you can retry the failed stage or restart the publish. The system offers a cleanup option to remove partially uploaded files on the server when a publish fails mid-way.

Troubleshooting

Publish Fails During Transform

Check the transform log for XML well-formedness or validation errors.
Ensure the selected build profile is correct and that required resources are reachable.
Try enabling intermediate file preservation to inspect generated files locally.

Publish Fails During Copy/Deploy

Verify network and VPN connectivity to the target server.
Confirm your account has write permission to the destination folder.
Check server disk space and remote file-locking conditions.
Use the cleanup option to remove partial uploads, then retry.

Unexpected or Missing Output Files

Open the generated output locally (preview) to check whether the build produced expected files.
Check transform warnings for missing resource references (images, topics).

Tips & Best Practices

Prefer using a PubAssist profile when you need repeatable, complex publishes across multiple files or when publishing requires consistent settings.
Use preview mode to confirm output before copying to production servers.
Keep build profiles in source control so team members get the same publish behavior.

Keyboard Shortcuts

Ctrl + O — Open source file dialog (when publisher focused).
P — Start publish (when focus is on the publish button or form).