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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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