This book provides practical, proven advice for encouraging adoption of your wiki project and growing it into a useful collaboration tool or vibrant online community
Gives wiki users a toolbox of thriving wiki patterns, which enable newcomers to avoid making common mistakes or fumbling around for the solutions to the same problems as their predecessors
Explains the major stages of wiki adoption and explores patterns that apply to each stage
Presents concrete, proven examples of techniques that have helped people grow vibrant collaborative communities and change the way they work for the better
Reviews the overall process, including setting up initial content, encouraging people to contribute, dealing with disruptive elements, fixing typos and broken links, making sure pages are in their correct categories, and more
Table of contents
- About the Author
1. Grassroots is Best
- 1.1. Wiki?
- 1.2. The Wikipedia Factor
- 1.3. You Can Do It!
- 1.4. Wiki Patterns and Wikipatterns.com
- 1.5. References
- 1a. Case Study: LeapFrog
2. Your Wiki Isn't (Necessarily) Wikipedia
- 2.1. Brief History of Wikipedia
- 2.2. Nature Compares Accuracy of Wikipedia and Britannica
- 2.3. The All-Virtual Wiki Community versus Wiki that Mirrors Physical Community
- 2.4. Why Mischief Doesn't Happen in an Organization's Wiki
- 2.5. How Will Your Wiki Be Used?
- 2.6. References
- 2a. Case Study: Johns Hopkins University
3. What's Five Minutes Really Worth?
- 3.1. What Happened to Knowledge Management?
- 3.2. Something Wiki This Way Comes
3.3. What Makes a Wiki a Wiki?
- 3.3.1. Basic Structure
- 3.3.2. The Enterprise Wiki: Spaces and Pages
- 3.3.3. Editing Pages and Creating Content
- 3.3.4. Folksonomy
- 3.3.5. Recent Changes
- 3.3.6. Balancing Trust and Control: Why Wikis Have Succeeded Where Others Have Failed
- 3.3.7. How Atlassian Uses a Wiki to Increase Transparency and Decrease Distance
- 3.3.8. User-generated Templates
- 3.3.9. Extending Wikis
- 3.4. Back-office to Front-office
- 3.5. References
- 3a. Case Study: Sun Microsystems
4. 11 Steps to a Successful Wiki Pilot
4.1. 11 Steps to a Successful Pilot
- 4.1.1. 1. Establish a Time Frame
- 4.1.2. 2. Make It Representative
- 4.1.3. 3. Keep It Compact
- 4.1.4. 4. Choose Participants Carefully
- 4.1.5. 5. Seek or Be Sought?
- 4.1.6. 6. Wiki with a Purpose
- 4.1.7. 7. Define House Rules
- 4.1.8. 8. Personal Spaces
- 4.1.9. 9. Never an Empty Page
- 4.1.10. 10. Make It a Magnet
- 4.1.11. 11. Be Firm and Think Long Term
- 4.2. What's My Role in Wikipatterns.com?
- 4.3. References
- 4.1. 11 Steps to a Successful Pilot
- 4a. Case Study: Red Ant
4b. Case Study: A Conversation with a WikiChampion: Jude Higdon
- 4b.1. 1. Why did you choose a wiki?
- 4b.2. 2. What type of wiki are you using?
- 4b.3. 3. How are you using the wiki?
- 4b.4. 4. Looking at Wikipatterns.com, what patterns are in use on your wiki?
- 4b.5. 5. What changes have you seen as a result of using a wiki?
5. Drive Large-Scale Adoption
- 5.1. Develop a Wiki Use Policy
- 5.2. Work in Phases
- 5.3. Explain Why People Should Use the Wiki
- 5.4. Use Pilot Cases as Examples
- 5.5. Offer Training and Support
- 5.6. Apply Patterns
- 5.7. "It's on the wiki"
- 5a. Case Study: JavaPolis
- 5b. Case Study: A Conversation with a WikiChampion: Jeff Calado
- 6. Prevent (or Minimize) Obstacles
- 6a. Case Study: Kerrydale Street
- 7. Inspirational Bull****
- 7a. Case Study: Constitution Day
7b. Case Study: Peter Higgs: Using a Wiki in Research
- 7b.1. Objectives of the National Mapping Research Project Wiki
- 7b.2. Sophisticated handling of Users, Groups and Access Permissions
- 7b.3. Collaboration
- 7b.4. Ease of Use: The Thin End of the Wedge
- 7b.5. Addressing the "Why Nots?"
- 7b.6. Getting It Accepted into a Corporate Environment
- 7b.7. How Are We Using the Wiki?
- 7b.8. The Wiki as eResearch Infrastructure
- 7b.9. Conclusions
A. Questions & Answers
- A.1. Someone else can change what I wrote?
- A.2. When someone else edits a page, how do I see what changes they made?
- A.3. Can the wiki notify me when a page is changed?
- A.4. What if I don't like what someone else wrote? Can I just delete it?
- A.5. What if someone puts a contribution into a wiki page, and then somebody else just deletes it, puts something completely different in, another person just deletes that, and puts yet another different contribution in. Doesn't there still have to be some moderator?
- A.6. If the debate on a wiki page does get "hot," can you somehow shut off editing?
- A.7. Can everyone see what I put on the wiki? What if some material is sensitive or confidential?
- A.8. How do I give people access to it/restrict access?
- A.9. How can I control the wiki and approve edits?
- A.10. How do I know the content on the wiki is correct?
- A.11. Is there a grammarian or controller?
- A.12. So what should I do first?
- A.13. What would I put on the wiki?
- A.14. Can it handle images and other file types?
- A.15. Can I get content out of the wiki, say, when I'm done drafting a document?
- A.16. How do I get people to switch from email to use the wiki?
- A.17. Is it ok to work locally, (i.e. offline on my own computer) on content that will go in the wiki?
- A.18. What if you read what someone wrote on a wiki page and find a grammatical error or can't tell what the person wants to say?
- A.19. What would motivate someone to contribute to a wiki? Seems like they get less credit than they'd get for sending an email, where everyone sees they sent it?
- A.20. What would you say is the biggest difference between the wiki and content management systems when used for project management?
- A.21. Isn't this just another enterprise IT project with a lot of promise but little chance of success?
- A.22. What about IT? Won't they say "No" to adding yet another tool they have to support?
- A.23. How do I convince others to use the wiki?
- A.24. What's the advantage of constructing knowledge on a wiki?
- A.25. How do you encourage context-building and conversation about the changes that occur on the wiki?
- A.26. Can using a wiki help make conversations and collaboration more inclusive, especially of those who are more reluctant to speak up in a face-to-face meeting?
- Title: Wikipatterns
- Release date: December 2007
- Publisher(s): Wiley
- ISBN: 9780470223628
You might also like
AWS Certified Solutions Architect Official Study Guide
Validate your AWS skills. This is your opportunity to take the next step in your career …
Kubernetes: Up and Running, 2nd Edition
Kubernetes radically changes the way applications are built and deployed in the cloud. Since its introduction …
5 Key Areas for Tech Leaders to Watch in 2020
Our annual analysis of the O'Reilly online learning platform reveals Python's continued dominance and important shifts …
Kubernetes in Action
Kubernetes in Action teaches you to use Kubernetes to deploy container-based distributed applications. You'll start with …