Someone came up with a cool idea to add a universal edit button to make editing wikis easier. It adds a button like for RSS feeds that redirects the browser to the edit page. It’s clever but it aims way too low. If you can get browsers to add an editing button you have an opportunity to either point to an online form or a standalone application that could also edit the page. In other words, Atom Publishing Protocol auto-detection.
Kevin Gamble has an excellent post Enterprise 2.0– working in the open:
A week doesn’t go by where I don’t hear from some administrative group who wants to work in a wiki, but wants their work to be private. When this happens I almost always tell them, “Then a wiki isn’t for you. If you want to collaborate with a small group where no one else can see it use Google Docs.” It’s amazingly common for people to want to work in a private little sandbox until they have everything perfect and then reveal it to the world. The trouble is, this almost entirely eliminates the opportunities for collaboration because people can’t see the content until it’s completed. What’s the value in reviewing and adding to a document that the author already thinks is done?
My open tabs in NetNewsWire have exploded in the last couple of days with really good articles about driving wiki adoption and generally making wiki’s work. First up Making Wikis Work is a pretty good overview of all that is wrong with wikis. It’s odd to think that a technology as young as wikis has legacy cruft but they do.
I’ve been doing a lot of thinking lately about how to make wikis accessible to the common man – in other words, how do we get wikis to spread out of the technical departments and make it not just usable by non-technical people but make them actually want to use it and advocate it. Certainly there’s been a lot of movement in this area and a lot of good progress made, but I suspect there’s a lot more than can be done.