First - congrats on this bold (and not so bold - logical and smart) step.
Here's a few more..
* Watch this Webinar - Still relevant on process, strategy, approaches.
* Review the plugins by K15t - - one of two likely will become critical to your new Confluence Product Doc process.
* Convince of single purpose license, maybe - though not mandatory, having a Confluence system dedicated to your product doc allows you alot more control over your process, plugin conflicts, or even collaboration conflicts.
* Product Doc Translation needs, in Confluence - For the moment, follow @appfusions on twitter (or email @appfusions.com">email@example.com) - since we have a great plugin for this coming VERY SOON - which will save Enterprise corps who have translations with docs many many $1000s..
(will update with link when avail - ETA mid-May latest - accepting Beta customers now)
Never look back.
Confluence for product documentation is the way of the future - but actually its here NOW! :)
i would try for the answers regarding "technical documentation". Common basis is to provide a hierarchy of pages to allow treelike search inside the pages.
Bottom line : I think it is a question of style : Do you provide a given structure via a tree-style navigation or do you link and tag your articles, but keep the hiearchy low. Since people are used to browsing books, I would suggest
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork? We've compiled a list here, along with...
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