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
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.
we love confluence, but we have to constantly fight to keep 'what is documented officially' from 'being polluted by stuff that is not yet well organized'.
You probably know the situation yourselves, someone creates some page but then never finishes it, or it has many TBD sections, and over time, it's just not clear anymore, what part of the internal documentation is official and useful, and what is not. This again erodes confidence in the documentation in the first place.
How do you all solve this problem?
I imagine some sort of git-like workflow whereby anyone can create 'forks' (new versions/updates) of a page, and then commit it back, is then reviewed (has to be reviewed) by one or more page owners. This way, there's a clear gatekeeper defined, while still allowing anyone to contribute.
Is this possible with confluence?
Are there good alternative solutions to this?