As we are working with many instances of the software being in different code branches and releases is there a way to keep the Confluence documentation versioning in pace with this?
(In the past I used Subversion in combination with MS folders and Office documents. That worked perfectly well except the merging was cumbersome. Something I expect to be a bit easier with Confluence.)
My team makes and app called Scroll Versions which does this very thing on Server, but it's not on Cloud. :(
That said, we're exploring a Cloud solution now, and if you'd be interested, I'd love to connect you with our user researcher so we can better understand your needs.
Also, in the interim, you could check out how ThinkTilt is using our app Scroll Documents for some light versioning.
Also, some of the content is Server specific, but there are a lot of tips for writing documentation on our guide here: https://www.k15t.com/rock-the-docs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.