We are organizing info into spaces, with different branches, very similar to Atlassian's documentation.
We can see that for each version of a product, a complete set of documents also available. So how do you do this? How are these sets of documents organized?
Given that you are writing the documentation for the next version that is not released yet. Where are you keeping the 'development' version of these documents? In the same space but another branch or in another space?
Atlassian provides good tutorials for this: https://confluence.atlassian.com/display/DOC/Developing+Technical+Documentation+on+Confluence+Wiki and specifically the part https://confluence.atlassian.com/display/DOC/Managing+the+Life+Cycle+of+your+Technical+Documentation.
I think you will also find some answers here.
The book was recently taken out of print since it was created for Conf 3.X and 4.X versions, and some things have changed - much of it is all still relevant nonetheless. Worth it to get your hands on this if you are doing a major structuring of your content for product documentation. Sarah was involved in much of the foundational product documentation information architecture build out at Atlassian.
As OBSS , we developed a solution for " Baseline ". You can create baselines of your documents based on a date and time. The created baseline set allows you to easily access document versions of that time.
Here is the link to download Baseline for Confluence . You can also read the documentation of the product.
Thank you for your interest!
Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time! We're looking for people to participate in a remote 1-hr workshop...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs