DITA-related options in the conf.json file allow administrators to define the DITAVALs and DITA maps to process, etc.
The following lines show a parameter set for DITA content:
{
...,
"ui": {
...
},
"metadata": {
…
}
},
"khub": {
...
"pafs": {
"connector": [
...
],
"related_links": "all"
}
}
}
The related_links parameter set to all means that the DITA-OT must generate:
- all relationship table links
- one link for the previous topic
- one link for the next topic
- one link for the parent topic
Other options are available for DITA-generated content, such as the following:
- ditamaps to define the DITA maps present in the sent archive that you wish to be processed
- ditaot_max_memory to define the maximum memory used by DITA-OT during the processing of your content
- privateDitavals to define specific private groups that will be assigned to the DITA maps on which the specified DITAVAL will be applied
Fluid Topics v4.1.6 introduces the possibility to manage a DITA-OT version using web services or in the Sources administration interface. With the introduction of this possibility, adding information about a DITA-OT version in the conf.json file is deprecated.