Manage versions at the article level
under review
Bianca Ragsdale
Currently, my company has 2 versions of our product (let's say "Release" and "Beta"), and we have a separate support site version for each in Document360. However, we’d prefer to have 1 support site, and allow readers to select their product version for each article. A lot of content is the same for both versions, so right now we’re copying/pasting, which takes up time and could lead to errors.
Here are more details for my request:
- Add ability for reader to toggle between article versions
- Add ability for author to toggle between article versions
- This is a stretch, but it would be great to add conditional text directly to an article, and have the content the user sees change based on the version they select. That way you only need to manage 1 article.
- Changing the article version should change the last part of the URL. This will help with tracking page visits.
For example, the same article in 2 versions looks like this:
- domain/docs/widget
- domain/beta/docs/widget
Instead, it should look like this:
- domain/widget
- domain/widget/beta
Log In
K
Kristina Ejstes-Svensson
Representing a company in the same situation:
With several products documented in the same knowledge base, and with end customers using different versions of each product, there is a need for an enhanced forking solution, also visible on the readers' side. Where an article can be forked and have more than one published version at a time, labeled in an intuitive way in both the editors' mode and the readers' view.
I assume the easiest way today is to copy the massive x7.1 content to a new folder/category named x7.2 and continue updating there. However, this will no longer be a "one source web solution easy to maintain" and it will definitely cause an unwanted strain on the Document360 storage environments.
Thiru
under review
Thiru
Bianca Ragsdale thank you very much for such a detailed request. We will evaluate this scenario and keep you posted for updates.
Abby Dong
This would be a huge improvement to our current content management processes. We're also copy-pasting between versions. I'd like to add to this the ability to label versions. We use this for releases, so we have a current-state version, and a release version (v2.1 and v2.1.1, etc) for things we know are upcoming and want to get ahead of on documenting. This is something the current forking ability sort of supports, but lacks some functionality for more advanced content processes.