In a world where SaaS solutions are increasingly popular, users often look for documentation about the latest version of a product.
They can manually select the latest version of a document while consulting it in the Reader page as follows:
However, it would be easier if links to documents would always open to the latest version, unless specifically configured to point to an earlier version. To make this happen, administrators need a way to ensure that links to the latest version of the documentation remain stable throughout all future product releases.
Overview of the solution
To implement the solution, an administrator with the
KHUB_ADMIN role must configure a Vocabulary, configure an Enrich and Clean rule for that Vocabulary, and define Pretty URL templates.
The procedure requires the administrator to access the following tabs of the Administration interface:
- Vocabularies to create a list of synonyms.
- Enrich and Clean to configure a rule.
- Pretty URL to configure templates.
Configure a vocabulary
In the Vocabularies administration interface, an administrator can define Latest as a synonym for the latest version of your product as follows:
Prepare a CSV file based on the following example, keeping only
3.11with the value corresponding to latest version of your product.
Upload the file in the Vocabularies administration interface. The following image shows the result after Antidot's technical content team uploaded their file to
Select Reprocess in the Vocabularies administration interface to apply the new synonym to all content in the Knowledge Hub.
afs:langmetadata in the CSV file before uploading it.
Configure an Enrich and Clean rule
In the previous step, an administrator configured
Latest as synonyms. If they do not configure an Enrich and Clean rule, Fluid Topics will display both
Latest alongside each other. Configuring a rule is necessary in order for the value
Latest to replace the value
Define Pretty URL templates
To complete the process, the administrator must configure at least one Pretty URL template with a metadata requirement set to the original value for which
Latest is a synonym.
In order to get the most out of Pretty URLs, it is best to create at least one other Pretty URL template for content that is not the latest version. This is similar to Step 1, but without the metadata requirement.
This example travels back in time to when Fluid Topics version 3.10 was released. For the occasion, Antidot's technical content team had to configure
doc.fluidtopics.com so that the Pretty URL to the latest version of a document would be
doc.fluidtopics.com/r/<document_title>, while the Pretty URL to a previous version of the document would be
Here is how we made this happen:
- In the Vocabularies administration interface, download the file corresponding to the
- Delete the value
3.9and replace it with the value
- Upload the updated file in the Vocabularies administration interface.
- In the Enrich and Clean administration interface, make sure there is a rule for the
Latest Versionvocabulary and that the checkboxes are cleared.
- In the Pretty URL administration interface, update the metadata requirement for the
ft:titletemplate by replacing the
FT_Version = 3.9metadata requirement with a
FT_Version = 3.10metadata requirement.