Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,331,646
Community Members
 
Community Events
169
Community Groups

Pull-request style workflow for confluence documentation

Hi Everyone,

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?

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Confluence

Collaboratory Video Series: Confluence Your Way

Hey there, collaborators! We're continuing on with Work and Wellness with a special video series focused on team connection and collaboration, wherever and whenever.  Introducing Confluence ...

153 views 2 10
Read article

Atlassian Community Events