Where I work we've found that we write vastly more internal documentation within our team since we started using a Wiki, specifically, TWiki.
If you haven't used one, it's a web-based collaboration tool. A bit different from a blogging system (it doesn't have the data-based approach, for one thing); more free-form.
It's simplicity itself, since you just type into a web form (much like the one I'm typing into now) with a few special codes that get converted into HTML. What else? It's free as in speech and beer, and as it's mainly just a Perl script, it'll run just about everywhere.
The key thing is to get people to use it, and somehow it caught on at our place. We've now got the best-documented forthcoming release I've ever known.
Getting the user documentation written, of course, will be another matter.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
branchandroot
A possible solution?
Date: 2003-01-23 17:48 (UTC)If you haven't used one, it's a web-based collaboration tool. A bit different from a blogging system (it doesn't have the data-based approach, for one thing); more free-form.
It's simplicity itself, since you just type into a web form (much like the one I'm typing into now) with a few special codes that get converted into HTML. What else? It's free as in speech and beer, and as it's mainly just a Perl script, it'll run just about everywhere.
The key thing is to get people to use it, and somehow it caught on at our place. We've now got the best-documented forthcoming release I've ever known.
Getting the user documentation written, of course, will be another matter.