TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Folks who've worked on wikis - please share your experiences around publishing product documentation as a wiki.
> There certainly are benefits, but what are the risks of using a wiki? For example, do the publicly visible comments impact customer satisfaction?
> How do you manage user feedback? What aspects should a feedback management plan cover?
> Who provides the support? Tech Support? Tech Writers? Programmers?
> What kind and volume of feedback do you receive? Are you able to address every comment on every page across releases?
> What happens to all the comments when the wiki/product moves to the next release? Should there be a point at which the comments can be archived?
> Is your wiki completely public? Limited access for customers?
> What space do you use to publish your wiki?
In your response, please add a line about your product domain and the approximate number of pages that your wiki has. Any stories around Atlassian's Confluence would especially help.
Thanks very much!
Regards
Ayesha
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW
