I've been using jumpbox list of wikis to evaluate some. Here are my initialconclusions (based on comparing the writeup with my requirements):
pmwiki
I particularly like two points from their philosophy:
1. Favor writers over readerstikiwiki
3. Avoid gratuitous features (or "creeping featurism")
TikiWiki is your Groupware/Content Management System solution with a long list of features to help you build a compelling web based community: Wikis, Forums, Blogs, Articles, Image Gallery, Map Server, Link Directory, Translation and i18n. And much more...
Too much
moinmoin
Looks promising.
twikiwiki (Watch the extra w)
TWiki is a flexible, powerful, and easy to use enterprise wiki, enterprise collaboration platform and knowledge management system. It is a Structured Wiki, typically used to run a project development space, a document management system, a knowledge base, or any other groupware tool, on an intranet or on the internet.
Too much
mediawiki, as used by wikipedia
Promising. Slightly too much stuff on the page, but can be configured away.
docuwiki
Specifically designed for creating documentation, however you can't get email notifications when a page changes, which is a showstopper for me.
So that's three to look at. I haven't evaluated them on ease of installation, or maturity of product, or how much support there is, or how widely they are used. More to come...
Update: 17 March 2009 on using mediawiki for documentation
3 comments:
Hi,
It's almost a year since you wrote this. Do you have any more information or knowledge to share on using a wiki for procedures?
Thanks,
Tim
I haven't done any more work on this project, I'm afraid. I hope to pick it up again in the next couple of months, and if I remember I'll post a follow up.
Thanks, Paul. We have MediaWiki and seem pretty well locked to that right now. I'll give it a try and see what comes out.
Post a Comment