Edit online

Since WebHelp output must be published locally, on the same machine where the WebHelp process is running, to publish your files directly to a SharePoint library you need to map a network drive to connect to SharePoint and change your file extensions to .aspx, as described in the steps below.

Using a Script Outside of Oxygen XML Editor/Author

To publish WebHelp Responsive output on a SharePoint site using an Oxygen Publishing Template, follow this procedure:
  1. Map a network drive to connect to your SharePoint library. For more information, see: https://support.microsoft.com/en-us/kb/2616712.
  2. To allow browsers to open your published files (rather than downloading them), you need to change the file extensions from .html to .aspx.
  3. Open the template descriptor file associated with your publishing template and add the args.outext parameter in the parameters section with its value set to .aspx.
    <publishing-template>
        ...
        <webhelp>
            ...                
            <parameters>
                <parameter name="args.outext" value=".aspx"/>
            </parameters>
        </webhelp>
  4. Open the DITA Map WebHelp Responsive transformation scenario.
  5. Click the Choose Custom Publishing Template link and select your template.
  6. Click OK to save the changes to the transformation scenario.
  7. Run the transformation scenario.

Using a Transformation Scenario in Oxygen XML Editor/Author

To publish WebHelp Responsive output on a SharePoint site using a transformation scenario from within Oxygen XML Editor/Author, follow this procedure:
  1. Map a network drive to connect to your SharePoint library. For more information, see: https://support.microsoft.com/en-us/kb/2616712.
  2. To allow browsers to open your published files (rather than downloading them), you need to change the file extensions from .html to .aspx. Fortunately, this can be done in the transformation.
    1. Edit the WebHelp transformation scenario and open the Parameters tab.
    2. Set the args.outext parameter to .aspx.
    3. Run the transformation scenario.