Always link to a "latest" version of an article
M
Maggie Antone
We have different versions of our documentation in our knowledge base (folders with v6.5 and v6.6, for example), and when internal support articles or links from external sources are pointed to our documentation, I would like a way to have the link always point to the most recent version of the documentation. So when we add a version 6.7, for example, those links will automatically go there.
Log In
Mohamed Shakheen
Hi Maggie
Thanks for the context. To make sure we scope this correctly, let me validate one key expectation: when an article is edited and rolled into a newer version, the content will naturally carry forward as part of the versioning workflow.
What we want to confirm is whether your requirement is specifically that any static or links should always resolve only to the latest published version — meaning those links should not continue pointing to, or remain accessible in, older versions.
M
Maggie Antone
Mohamed Shakheen This is correct. I have categories for different versions, but I noticed that I cannot change the slugs to something like "/v6.6/slug-name" since only the "slug-name" is editable. It would be great if we could edit the slug at that /version/name level (following the article breadcrumbs), if that is possible.
I thought about renaming slugs in the "latest" version to "slugname-latest", but I also cannot bulk update slug names to reflect this (and would take a lot of time manually), and when creating a new version, would have to manually rename each slug in the older version when copying over. So having a /latest_version or version_number/slugname setup would be great so we can continue pointing to the most recent version.
As an example, links in a support article that point to the admin guide would need to be manually updated each time we have a new version, otherwise they'd point to an old one. This is what we'd like to avoid.
Let me know if you need any more information, and thank you!