Hiding page elements based on viewer’s actions?

Question

Hello all,

First post and I’m guessing like a lot of members here I joined after my company introduced me to their Confluence Server project (I already worked out we’re on Server, not Cloud). So far it’s been great. I’m loving being able to capture thoughts, full blown processes and track projects on Confluence. Inevitably though, I have a question...

I’m hoping this is as easy a question to answer as it is to ask - can you hide or reveal elements of a Confluence page based upon a user’s actions? In this case I’m thinking of a radio button or checkbox selection.

The general idea is that with a single page I can create an upgrade guide for multiple versions of our software. The various steps in the upgrade might be relevant to one or more versions of the software. If we created a set of radio buttons at the top of the page (one for each version of the software) then the reader could make a selection to indicate which version they are interested in upgrading. The tagged upgrade steps on the rest of the page could then be rendered visible or invisible based on their tags.

There seems to be the ability to hide and reveal page contents based on user ID or priority (as discussed here and elsewhere community.atlassian.com/t5/Confluence-questions/hide-content-on-a-page/qaq-p/172703) but that’s not quite what I’m after.

Obviously if my search-fu is weak then simply point me to the correct answer rather than repeating it. Failing that, any advice would be most welcome!

Thanks in advance,

Andy

Andy Phillips_ugro8b · Answer

Thanks for the clarification Matt. It seems like this is a superset of the functionality we need at this time, plus I'm really after streamlining the maintenance process. The audience experience (in this specific case) is a secondary benefit. The audience is already savvy enough to navigate the existing pages but if I could have merged those pages into a single reactive one for the benefit of the authors, that would have really helped them. I guess it is a slightly unusual case in that a lot of our pages are very similar, hence the emphasis on maintenance simplification. Thanks again for the suggestion though,

Andy

Matt Reiner _K15t_ · Answer

Hey @Andy Phillips

That's how Scroll Versions handles multiple versions of the content, yes. But this is all handled in the background automatically. So you could just create a new version, update/add/remove pages in the page, and then users can easily switch to the version they'd like to see.

Andy Phillips_ugro8b · Answer

Hello,

Thanks to you both for the suggestions. Sorry for the delayed reply but I've had a chance to review the two pages provided. After a brief inspection it looks like one would essentially create individual pages and present the relevant page as the user makes a selection. Is that correct?

Thanks,

Andy