HTML5 id205BE700XO1
The HTML5 output is generated in a flat folder hierarchy. This implies that the folder structure used by the content in the repository is not replicated in the HTML5 output. The entire content is published in HTML5 output format and saved in a single folder. The file names are also replaced with the UUIDs of the files in the generated output. The only file that doesn’t have a UUID-based filename is the index.html file.
You can create the HTML preset in two ways:
From the Web Editor: In the Repository panel, open the DITA map file in Map View, then in the Output tab, select the + icon to create an output preset, and then select HTML5 from the type drop-down in the Add preset dialog.
In the Web editor the configurations have been organized under General and Advanced tabs:
General
The General tab contains the following configurations:
- Output Path
- DITA-OT Command Line Arguments
- File Name
- Apply Conditions Using (If the conditions are defined for a map)
- Use Baseline (If a baseline is created for a map)
- Post Generation Workflow
Advanced
The Advanced tab contains the following configurations:
- Transformation Name
- Retain temporary files
- File Properties
For details, refer to HTML5 configuration.
From the map dashboard
To open output presets for PDF, click on a DITA map file from the Assets UI, then click on Output Presets, and then click on the HTML5 option. In the Map dashboard, click Edit on the top to update the various configurations, and then click Save.
HTML5 configuration
The following options are available for the HTML5 output:
* None applied: Select this option if you do not want to apply any condition on the published output.
* DITAVal file: Select DITAVal file(s) to generate personalized content. You can select multiple DITAVal files using the browse dialog or by typing file path. Use the cross icon near the file name to remove it. DITAVal files are evaluated in the order specified, so the conditions specified in the first file take precedence over the matching conditions specified in later files. You can maintain the file order by adding or deleting files. If the DITAVal file is moved to some other location or is deleted, it is not automatically deleted from the map dashboard. You need to update the location in case files are moved or deleted. You can hover over the file name to see the path in the AEM repository where the file is stored. You can only select DITAVal files and an error is displayed if you have selected any other file type. FrameMaker Publishing Server doesn’t support multiple DITAVAL files.
* Condition preset: Select a condition preset from the drop-down to apply a condition while publishing the output. The option is visible if you have added a condition present in the Condition Presets tab of the DITA map console. To know more about condition preset, see Use condition presets.
You can select multiple DITAVAL files using the browse dialog or by typing file path. Use the cross icon near the file name to remove it. DITAVAL files are evaluated in the order specified, so the conditions specified in the first file take precedence over the matching conditions specified in later files. You can maintain the file order by adding or deleting files. You need to update the location in case files are moved or deleted. You can hover over the file name to see the path in the AEM repository where the file is stored. You can only save DITAVAL files. An error is displayed if you have selected any other file.
Note: FrameMaker Publishing Server doesn’t support multiple DITAVAL files.
xhtml
. For a list of transformations available in DITA-OT, see DITA-OT transformations (output formats) in OASIS DITA-OT User Guide.Note:If you do not provide a file name, then the DITA map’s title is used to generate the final HTML5 output file name. If the map does not have a title, then the DITA map’s file name is used to name is the final HTML5 output. The file name is sanitized using the rules configured in the system to handle any invalid character.
Note:For more information about creating a custom post-output generation workflow, see Customize post-output generation workflow in Install and configure Adobe Experience Manager Guides as a Cloud Service.
After generating the output, select the Download temporary files icon to download the ZIP folder containing the temporary files.
Note: If file properties are added during generation, the output temporary files also include a metadata.xml file containing those properties.
If you deselect this option, the output is generated in a nested folder hierarchy, and the entire folder structure is replicated.
See Work with Baseline for more detail.
Note: You can also pass on the metadata to the output using DITA-OT publishing. For more details see, Pass on the metadata to the output using DITA-OT.
Parent topic:Understanding the output presets