Examples of Wiki sites using Drupal?

My site uses wikitools: TheEmpowerment.com

Julian who wrote wikitools is a friend of mine actually and he's a genius! Also check out the diff module he wrote.

I am using book pages for my content with straight HTML and clean-url aliases instead of wiki [pagename] syntax. He's working on a version of wikitools that will allow this to support automatic page creation instead of 404 errors when you follow links to non-existant pages at root instead of under the /wiki/ path.
The expandable navigation on the left is all courtesy of the book menu combined with the Javascript Tools Active Menu.

Here's an excerpt from Why Drupal WYSIWYG Makes Wiki Obsolete & How To Convert, a work-in-progress article.

Like many wiki operators, I was piling up articles with no end in sight.

The higher I built my tower of babel, the more I wondered if I had chosen the strongest foundation to build upon. As content increased, the strain on the system did too. More articles made it more painful to rebuild and convert if my wiki collapsed.

The MediaWiki system had been chosen for a couple reasons:

1. Easy Editability: Wikipedians like myself are familiar with its markup language, which is easier to use than HTML
2. Collaborative Wiki Culture: Wikipedia culture has developed elaborate and clever ways of dealing with large-scale problems through cultural processes that take its simple page editing scheme and category tracking to new organizational heights. Most of these processes aren't hard-coded into the MediaWiki software at all. Wikipedia runs mostly on informal policies and practices that Wikipedians have developed through trial and error.
3. Community Momentum: MediaWiki enoys a large install base and the ongoing development efforts of the Wikipedia organization.

I created my wiki and saw that it was good. But in biting the apple of Knowledge of MediaWiki Good and Evil, I discovered a pile of problems that set my article tower teetering:

1. MediaWiki Is Hostile Towards HTML: As an experienced designer, I found it frustrating sometimes not being allowed to use full HTML without hacks. I used an extension called ABSHTML to allow snippets of code to go unmolested by MediaWiki's parser and this worked for a while.
2. Markup Is Still Painful: Even Wiki's simple markup is a pain to teach would-be contributors with a lot more knowledge to share than time to invest learning how.
3. MediaWiki Layout Is Simplistic: MediaWiki is designed for long, sprawling encyclopedia article in a single column. As a designer, I hacked it into multiple columns by making templates called {{2coltop}}, {{2colmid}} and {{2colend}} that injected ABSHTML-wrapped table tags. Editing this became annoying quickly.
4. MediaWiki Editability Is Inverse To Article Size: The bigger and more complex an article gets, the less fun it is to edit. I find myself hunting through markup language when what I really want to is think and write about ideas.
5. Wiki Culture Is No Substitute For Code: As great as Wikipedian collaborative culture is, it's not a replacement for the ability to provide hard-coded user experiences that follow explicitly programmed paths and workflows.
6. Wiki Culture Is Alien To Outsiders: Wiki culture alienates newcomers because cultural processes are not easily discoverable and require editors to learn to apply hand-written markup conventions. For example, Wikipedia has no comment boxes, only a convention of hand-editing comments onto discussion pages followed by --~~~ which produces a username timestamp signature.
7. MediaWiki has no menu system: I built my own horizontal hierarchical menu system in MediaWiki out of embedded templates. Some other wiki engines have menuing systems built in, but this is a laughable problem to have.

The hunt was on for a replacement to MediaWiki. I needed something with all of MediaWiki's amazing features that transcended its weaknesses.

Then I met Drupal.
Drupal Weighs In

Anything wiki can do Drupal can do better.

1. Ultimate Editability: Drupal's integrated TinyMCE WYSIWYG editor continues to amaze me. The wonders never cease.
2. Modular Extensions Encode Culture: Drupal can be enhanced with modules and configurations that enable workflows that automate Wiki's informal cultural processes.
3. Tsunami Momentum: Drupal is sweeping everything before it. Countless groups like IBM, The Onion and others are adopting and extending Drupal, contributing huge improvements to its codebase.

I've been using the liquid wiki project on my site and it is working great. Plus it has hierarchical IDs which are really cool.

Here is the main page:
http://www.xequae.com/wiki/Main_Page

Here is an example of how I'm using hierarchical wiki IDs. It really helps to categorize things the way I want.
http://www.xequae.com/wiki/Muppets/Palisades/6_inch/

I'm also using it on my site at work, which is here:
http://tech.aph.org/mm/wiki/Main_Page

One of the things I like best about wikis in Drupal is you get all the other functionality in Drupal to go along with the wiki. In each case the wiki is just one part of my site.

XeQUae
----
http://www.xequae.com