I'm on maternity leave now, but the baby's sleeping so I'm stealthily reading blog comments and catching up a little bit.

Glad to know you all are finding my post and that many other doc teams are discussing the same wants and needs. I'm starting to come around on the idea of wikis for technical documentation, as long as they're properly maintained and structured for easy navigation. I learned about a month ago that a friend and former BMC colleague now works at Motorola (Hi Emily!) and maintains the wiki for the Motorola Q phone at http://www.motoqwiki.com/index.php?title=Motorola_Q_Wiki. When I return I fully intend to interview her and post the Q&A here, so stay tuned. I also wrote about DITA and wiki and the possibilities offered by DITA Storm in this post: http://talk.bmc.com/blogs/blog-gentle/anne-gentle/dita-storm. And, if you haven't seen it yet, take a look at the Microsoft Visual Studio wiki at http://msdnwiki.microsoft.com/en-us/mtpswiki/default.aspx. Plus EBay is using a wiki to help cut down on customer support calls, something our doc should do as often as possible. My comments here. http://talk.bmc.com/blogs/blog-gentle/anne-gentle/ebay-wiki

Anyway, that's a lot of links, but I hope it's helpful. Let us know what your team discovers in your wiki research, especially how customers react. And if anyone from Confluence is reading, let us know your customer's reaction to the wiki.