Good practices with multiple versions and ditavals
Posted: Fri Dec 02, 2022 12:13 pm
Hello,
I have a documentation that is regularly updated. We already have more than ten versions available and we support it with ditavals.
The problem is that the more versions we have, the more ditavals we have and this makes the document more difficult to read and maintain.
I created a subject scheme map to streamline the process and centralize the profiling attributes. However, there are still challenges, among others with links where we can end up with a long list of declarations like here:
Thus, is there a way to support and streamline the maintenance of numerous versions? Are the ditavals the best way to distinguish the publications, and would there be a way to make xrefs like shown above more easy to maintain (using keydef for instance)?
What's your opinion?
I have a documentation that is regularly updated. We already have more than ten versions available and we support it with ditavals.
The problem is that the more versions we have, the more ditavals we have and this makes the document more difficult to read and maintain.
I created a subject scheme map to streamline the process and centralize the profiling attributes. However, there are still challenges, among others with links where we can end up with a long list of declarations like here:
Code: Select all
<p>The <uicontrol>Vocabularies</uicontrol> interface of the Back Office is displayed for the
<xref href="https://link3.1" format="html"
scope="external" product="3.1">tenant</xref>
<xref href="https://link3.2" format="html"
scope="external" product="3.2">tenant</xref>
<xref href="https://link3.3" format="html"
scope="external" product="3.3">tenant</xref>
<xref href="https://link3.4" format="html"
scope="external" product="3.4">tenant</xref>
<xref href="https://link3.5" format="html"
scope="external" product="3.5">tenant</xref>
<xref href="https://link3.6" format="html"
scope="external" product="3.6">tenant</xref>
<xref href="https://link3.7" format="html"
scope="external" product="3.7">tenant</xref>
<xref href="https://link3.8" format="html" scope="external" product="3.8">tenant</xref>
<xref href="https://link3.9" format="html" scope="external" product="3.9">tenant</xref>
<xref href="https://link3.10" format="html" scope="external" product="3.10">tenant</xref> corresponding to the portal as follows:</p>
<image href="../images/bo-setup-vocabularies.png" placement="break" scale="60">
<alt>Vocabularies interface in the Back Office</alt>
</image>
What's your opinion?