You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi, I'm Elaine, and I wanted to share something we've been working on that I think a lot of you will be really happy to see.
Those of you who've been using Confluence for over a year may remember that the page tree used to live in the space sidebar. As part of a larger initiative aiming to improve your navigation in Confluence and across Atlassian products, we removed page tree from the sidebar and rolled it up with the Pages tab in the second half of last year:
We’ve since learnt that this change didn’t accomplish what it had been meant to and changed direction accordingly. As a first step in our latest iteration, we're bringing the page tree back to the sidebar:
Because of other dependent product changes, this wasn't as simple as reverting a change, and instead required us to rebuild a lot of this functionality. We've been rolling it out slowly and gradually because we want to make sure that it works without any errors.
Thank you for being so patient with this. We're really excited to get it out and hope you find it as useful as we do for getting around Confluence. We've been gradually rolling out this change so expect to see it on your Confluence instance in the coming weeks if you haven't already. If you have any question or feedback, please feel free to comment here.
Cheers,
Elaine
Yes, it's hard to imagine navigating the space without page tree in the sidebar! Why would you even need a sidebar if not for page tree navigation? We are not on a current version and had not yet experienced this. Very glad to see it's being fixed. Thanks for listening to users. (Sometimes it pays to stay on an older version. . . )