Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / techpubs / Emerging wiki use – now and future wikis

September 7, 2007 by annegentle

Emerging wiki use – now and future wikis

As you might have seen on The Content Wrangler recently, I wrote a response to JoAnn Hackos’ article, Is there a wiki in your future? and Scott Abel chose the title for my special contribution to his site. I think the title of this blog post – Emerging wiki use – now and future wikis – would have been a better title than “Anne Gentle vs JoAnn Hackos” but unfortunately I learned that his blogging system would cause broken links if he changed the title after I requested a title change. Ah, content management systems, why do they break your heart? 🙂

I do want to make sure that readers know that JoAnn and I are not at odds about wiki use at all – rather, we are both trying to find the best practices for building a wiki that will thrive. My thought on the “vs” in the title is that it is intended to show the polarization on the issues surrounding wikis and technical publications. JoAnn and I have emailed back and forth this week to continue to discuss and find that we are not on opposite sides of the issue.

I’ve happily read the blog entries from other writers that read both articles, with my favorite reference being Sarah O’Keefe’s “eponymous rebuttal” phrase. Subtle and clever, and sent me to m-w.com, so I love it.

  • The Age of… Expertise?
  • Wikis, and the shifting of power
  • Good Question

A neat outcome so far from this article is that I had a discussion with someone who had experienced something similar to JoAnn’s scenario. One of my readers described a situation where he was creating and updating wiki pages, trying to extract and describe an exact algorithm for an online game. Apparently in gaming communities, the developers can be very tight-lipped about the exact way that game play works (weaponry or armor for example), and the challenge to the gamers is to figure out the best strategies based on their experiences with the game. Without arbitration on the wiki (or customer support forum), though, outright content wars ensue and the wiki content about the algorithm becomes untrustworthy.

It’s a fascinating example. I’d like to find more examples related to technical content to find out what arbitration policies would work well. Let me know your experiences in this area – have you had a need for arbitration on your favorite wiki yet?

Related

Filed Under: techpubs, wiki Tagged With: arbitration, community, forums, JoAnn Hackos, Scott Abel, techpubs, The Content Wrangler, wiki, writing

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2025 · WordPress · Log in