It is strongly recommended that you publish your content using the Publishing Features built into Document! X. When you use the built in Publishing functionality, the location to which your content is published for a given Edition and Version is handled for you automatically and the url used when switching between Editions and Versions in the generated output can be determined automatically.

If you choose not to use the built in Publishing Features, you can still make use of the Editions and Versions functionality, but you will need to provide the url(s) that identify where you will be publishing your content and how it can be navigated to.

Configuring the Content Publishing Location if you are Publishing Content manually

1. Choose the manual publishing option in the Editions and Versions editor

1. Select the Editions and Versions node in the Project Explorer;
2. Right click and select Edit from the Context Menu;
3. The Editions and Versions editor will be opened with the Content Publishing Location page selected;
4. Choose the Define the url of my Published content manually option;
5. The Content Discovery Url and Frame Navigation Url fields will now be enabled.

2. Configure the Content Discovery Url

The Content Discovery Url template is used to determine the url at which a given page can be found when switching between Editions and Versions.

An example Content Discovery Url would be http://www.mycompany.com/help//

The url must always contain a placeholder.

The following placeholders may also be required, depending on your Project configuration:

must appear in the Url template if you have defined one or more Editions;
must appear in the Url template if you have defined one or more Versions;
must appear in the Url template if your Project generates output for multiple Locales.

3. Configure the Frame Navigation Url (if required)

The Frame Navigation Url template is used for Browser Help outputs that use a Frameset for navigation (e.g. the Classic or Material Templates, or custom Templates based upon them). For those outputs, a different url is required as the webframe.html file with a ?topicname.html query string is used to navigate to a specific content page.

An example Frame Navigation Url would be http://www.mycompany.com/help//webframe.html?

The url must always contain a placeholder.

The following placeholders may also be required, depending on your Project configuration:

must appear in the Url template if you have defined one or more Editions;
must appear in the Url template if you have defined one or more Versions;
must appear in the Url template if your Project generates output for multiple Locales.