In my explorations of ContentManagementSystems I've discovered that even though I get very frustrated with the limitations of most WikiSoftware, I keep coming back to them because they do more right than anything else. In an attempt to distill what is important about wiki to the Drupal MailList I wrote the below text. -- AdamShand

Trying to boil it down, the key concept of Wiki (which means "quick" in Hawaiian) is that the barriers to creating content should be as minimal as possible.

Thus a "true wiki" has these characteristics (this is a simplification and probably up for debate but ... ):

When actually talking about wiki's it becomes confusing. Along with being a CMS system there's a psuedo zen philosophy that tends to go along with them, for a classic example see the mind wipe pages which happened on the original wiki:

Now as far as what Wiki's have to do with Drupal I see three things that I think Drupal could learn and benefit from wiki:

  1. Lowered barriers to entry. I love that wiki invites people to participate, you don't have to create an account you don't have to jump through any hoops to participate. You just click "edit". This does mean that you should have good soft security measures in place (primarily revision control).
  2. Increasing intertwingliness (I have no idea how you're supposed to conjugate that word :-). Using normal CMS's systems it's laborious to constantly interlink and interconnect your content. Wiki's make this easy, and in fact it happens without even thinking about it. I think the glossary module is a great step in this direction.
  3. Easier data entry. I find HTML distracting when I'm trying to write, and I don't like that I have to worry about things like closing tags in my entries in order to generate valid HTML.


CategorySoftware

WhatIsImportantAboutWiki (last edited 2006-07-12 19:34:52 by zhejiang)