Why a Wiki?

Good question. Normally I use Drupal, an open source content management system - but sometimes a Wiki is better. There are a few things that I consider before tossing a project on either Drupal or a Wiki:

• Is the content going to change very frequently, or is it write once read many? If the content will be changing frequently, the Wiki makes sense. If the content is more static, then a content management system is usually more appropriate.
• Is it a blog? Blogs don't do so well on Wikis. Content Management Systems like Drupal are awesome for blogs.
• Is the content going to be atomized or will it be in chunks? Atomized data suits a content management system. Chunks are what wikis eat for breakfast, lunch and dinner. Wikis and Content Management Systems do not blow chunks.
• Wikis are better suited for collaborative works. Content management systems are also good at certain types of collaborative works, but they can get messy when dealing with more than one page.
• Wikis are easy to use; content management systems can be a pain when it comes to non-experts trying to figure out how to move forward. Wikis let more people focus on content rather than having to focus on how things work.
• Wikis are cool to have around even when you're not actively using them because, more often than not, you might encounter something and think, 'If I had a wiki…'. Well, now I do.