I am on Confluence Cloud. I am currently evaluating Scroll Viewport and Scroll Documents to determine if they are the right solution to publishing our customer help documentation. So right now I have a viewport site at (mysitename).scrollhelp.site and the Content Sources are my Scroll Documents.
The biggest problem so far is that I need links that go between Documents, but those links always need to go to the latest version of any given Document. I can't figure out how to do that.
- As an example: I have a Desktop Site (DS) and a Mobile App (MA). I'm thinking I should have separate Documents for each, because development cycles are different for each. My DS is updated every 6 months, while MA is updated monthly. So I might still be working on DS content when MA content is ready to go live.
- Because DS and MA are integrated, I need to be able to link back and forth between the information (if you're on a help page about the DS, I want to be able to include a link to relevant content on the MA - and vice versa).
- I need for the link to always go to the latest version of the MA content. So whenever someone is reading my DS information and clicks on a link that I included, it goes to whatever is the most current version of that MA link, at the time they click it.
THAT is what I cannot figure out how to do. Every way I try to do this, it seems that the link that I insert in the DS document is always "tied" to the Page ID (the ID of the MA page at the time I was writing the DS content). That's a problem because the Page ID changes on every MA version. A month after I publish the DS content, there's a new version of MA content out there, with a new page ID on everything, and the links on the DS content no longer work (they just start going go to my actual Confluence instance, which I absolutely don't want).
Now, as an example of something that works the way I want - here's a link that was posted several years ago (on another Community Question) and it went to what was, at the time, the latest version of the information:
But today, when you click on that link, you actually end up at the following link, which is the latest version of that information NOW:
I can't puzzle out how to do this on my own site. Hours of Googling leads me to a lot of information about how to do this on a Server instance, but not Cloud.
This issue of needing to link to our latest version is one of our most important concerns, so I am open to changing my back-end architecture (like changing my organization of Documents and Spaces, or even disabling Scroll Documents and managing my versions a more manual way) to make this work how I need it to work.
Please sign in to leave a comment.