Please don’t use MediaWiki It’s WAY more than any average project needs, and I’ve never found it to be user friendly at all, though maybe that’s changed.
If you want login & privileges integration it’s really anyone’s bet at the moment, since that’ll come down to some awesome person making a plugin for it. And this is why Jekyll is an ideal candidate, because the tricky “who gets to edit what?” stuff is left up to GitHub and the lovely concept of pull requests acting as an edit approval queue.
And, why would you want to tie your Discourse privs closely together with your wiki anyhow? In my experience, this sort of sync always turns into a bloody mess. The most trusted users of your forum aren’t necessarily your most avid doc-writers.
If you ask me (I could swear you did, didn’t you?), the most important “bridge” between your Discourse forum and your Wiki is Markdown. Writing docs should come as natural to your users as writing forum posts, which they’re all very used to. And, as often happens, a user writes up a great manual and just slaps it in a new thread, there’s minimal work involved to transfer it to the wiki.
Aaaanywho, I’m always on the lookout for good wikis myself, so here are some other options worth considering:
Used to great effect by many GitHub projects. Much like Jekyll’s Prose, it can be hooked up with [ReadTheDocs] for greater accessibility. Unfortunately it doesn’t support Markdown out of the box afaik, but the syntax is closely related.
node.js wiki. Supports Markdown.
The gist of my personal plan for Discourse + Wiki is this:
- Run the wiki with Jekyll and host its contents on GitHub (but publish through our own site so we can use plugins and possibly web templates we don’t have CC licenses for)
- Create a “Docs Team” on GitHub, and frequently add active docs contributors to this team.
- Hook the [Team API] up with Discourse, so that whoever’s signed up with their GitHub account can get an achievement for being on the Docs Team, and possibly other activities on the docs repository.