tags:

views:

687

answers:

9

What wiki software do you use for your software development wiki needs? Looking for something preferably wysiwyg and simple to use. A nice to have would be something that can import office documents (for the non-engineers)

+4  A: 

You should take alook at this pervious question:

http://stackoverflow.com/questions/10961/have-you-used-a-wiki-in-your-project-or-group

GateKiller
+1  A: 

We use MediaWiki mainly because it is the same engine that Wikipedia uses so there is a high likelihood they will be around and actively developed for quite some time. Also if people have any familiarity with a wiki it is usually that one.

N8g
A: 

We've had some success with the wiki built into FogBugz - probably the biggest advantage is that it its nicely featured and doesn't require us to maintain yet more software installations.

John Christensen
A: 

The following answer to a different question sums up the arguments for Confluence pretty well.

http://stackoverflow.com/questions/2639/what-are-some-web-based-knowledge-base-solutions#2712

Luke
+1  A: 

Trac has an integrated Wiki, and works hand-in-hand with Subversion. It doesn't have a ton of features but it's pretty simple to install and has good community support.

pix0r
+2  A: 

I've used both MediaWiki and Twiki, and have been pleased with both. Neither of them is WYSIWYG, but both of them have simple markup syntax. Both allow users to attach documents (though not import them).

The biggest differences that I've noticed between those two:

  1. MediaWiki allows editing document sections, a very nice feature for large documents.
  2. Twiki allows attaching documents directly to specific pages (instead of uploading to the wiki and then linking).
  3. Twiki's table syntax is more intuitive and simpler.

I think either of those would work, but maybe someone else will have something closer to your ideal.

And here's the obligatory Wikipedia link: Comparison of wiki software.

Derek Park
+4  A: 

We too use MediaWiki, mainly because of it's ubiquity. We investigated several editor enhancements to make editing more pleasant. We initially tried the FCKEditor integration, but we found that it had some bugs that were fatal for us - mostly related to munging the original markdown. We finally settled on wikEd which is simple to use via Greasemonkey. It's not WYSIWIG, but it's definitely a step up from the stock editor. For a dev oriented wiki, I'd also recommend the GeSHi syntax higlighter plugin to help make your code snippets pretty.

Mike Ellery
+1  A: 

I guess it really depends on your specific needs, but for a relatively small project, I've had great experiences with Trac. The combination of Subversion integration, issue tracking and a Wiki where we could store technical information of all kinds, proved to be a killer app for us.

onnodb
A: 

We have been using Confluence, we use the templating and forms features to make "standard" status reports easy to created and update. We have also integrated it with Jira to get some project metrics.

Brian Whitlock