Is your company moving documentation to a wiki? What process and policy issues should you consider (preferably) before selecting a wiki for documentation? If the choice of a wiki has already been made for you, learn to manage expectations and produce the best outcome for your situation.
Presentation by Janet Swisher at Technical Communication Summit, May 2011
32. Define the publication workflow Print output from a wiki Confluence PDF export MediaWikiPdf Export extension (see wiki.service-now.com for an example)
33. Who stands behind it? IANAL: Consult your attorney for legal advice. Warrantied content (read-only) Unwarrantiedcontent (user-contributed)
34. What can we do with users’ content? IANAL: Consult your attorney for legal advice. Grant a license vs. assign copyright Explicitly stated in terms-of-use Should be irrevocable
35. What can users do with our content? IANAL: Consult your attorney for legal advice. Default: All Rights Reserved Creative Commons Other terms
36. Thanks! Resources I mentioned: http://www.janetswisher.com/?itemid=283 Email me: JMSwisher@gmail.com Follow me: @jmswisher Share your feedback: http://www.surveymonkey.com/stcsummit
Hinweis der Redaktion
Everything you know about content management applies to wikis, too.A wiki is a CMS with specific choices for the core elements.
Tech writer jobs are not at risk, because users are unlikely to take over content production.Don’t consider a wiki to be a failure if the participation level is low.
Connect the two columns in the way that makes sense for your business.
If you have more than one level of review, you don’t really have a wiki. You have a CMS with a web-based editor.
Users have to give you the right to use what they right.