See also: WikiSpace, DreamWiki, WikiAsPim, DigitalPalace
So I've recently been doing some thinking about content and knowledge management as I've been migrating a couple MoinMoin wiki's to Drupal. I thought I was totally gung ho about the change but as I've started to actually use my new Drupal's I've started to realize that there are some things I *really* miss about my wiki's. I am not a programmer of any significant skill so I realize that this could easily come across as whining from a user but that's not my intention. Anyway here goes ...
My initial introductions to CMS' that I actually used was wiki's. Coming from a computer security point of view it was stunning to me that a totally open system could survive on the internet. I've seen freshly installed Linux boxes be rooted within minutes of being connected to the Internet ... the idea that an open web environment could not only exist but survive and prosper was totally bizarre to me. Honestly it totally restored my faith in humanity and I set my first one up as a personal experiment to see how it worked and then shortly afterwards implemented one as the primary knowledgestore for Personal Telco.
Over the next year I came to love my wiki's, their ease of use, dedication to clean and simple UI's and inate inertwingliness. However the more I wanted to use it, the more I wanted to use it for. I got more and more frustrated with wiki developers disinterest in growing wiki technology into what *I* wanted 
Disinterest is the wrong way to put it. Besides practical limitations like available time, each developer of course has his own priorities. Besides that, you are the only advocate for your own ideas (unless you find other people wanting the same), so also you are reponsible to bring your point across. Don't need to be a programmer for that.
-- JürgenHermann 2003-03-22 03:35:06 You are of course correct. Most of this talking is for my own benifit, I meant no disprect towards your efforts, it should be obvious that I like Moin an awful lot
-- Adam.
I found Drupal from Dries' posting to the P2PJ list a while ago and have been keeping an eye on it since. Something about it's module design and "everything is a node (except comments :-)" make me think that it could either evolve into what I was looking for.
As best as I can tell I want three core things from a CMS:
- Manage technical documentation and stories/essays etc.
- Keep a diary/journal/blog
- Manage personal data (photos, contacts, bookmarks etc).
Here's what I like about Wiki's:
- Wiki markup allows you to do enter data in an almost stream of consiousness fasion. It's more convenient then HTML (no closing tags). When all you want to do is slap up a quick thought, little hassles get bigger.
- Automatic/accidental linking builds interlinking of pages beautifully. When you're trying to build up a personal knowledge repository this is a really cool thing.
- Pages are expected to grow, change and evolve.
Wiki management/indexing traditions: Refactoring, Usemod:SoftSecurity, BackLinks, RecentChanges, TitleIndex, WordIndex etc.
What I've discovered is that now when I need to write something I'll write it in a wiki page before I'll write it any other way. That's a pretty good recommendation in my books. I write wiki pages before text, word, HTML pages.
What I like about Drupal:
- Blogs are really cool. Sometimes you just want to write your thoughts down, you don't want to have to figure out a page name for it etc. I saw a blogger say once when discussion wiki's that "Blogs are for people who want to write, wiki's are for people who want to wiki".
drupal good ...
blogs, themes, TrackBack, comments taxonomy *rocks*
moin good ...
'click to edit' wiki syntax wiki words (ease of linking, accidental linking) belief that simple is better
drupal bad ...
taxonomy shouldn't be an admin preference
moin bad ...
this preoccupation with keeping things the "way they were" slashclone presentation is *very* useful there's no good way to blog very hard to "blog" poor categorization features hard to extend ... (ie. queue).