Follow Slashdot stories on Twitter


Forgot your password?

Submission + - How do you manage documentation of your software p 1

Sudheer_BV writes: "How do you manage documentation of your software project? We are a small company with a team of 5 members. We manage several closed source and open source software projects. For some of our projects we want to write and maintain end user and developer documents. We would like to be able to publish the documentation online as well as offer PDF document to our users.

There are various tools out there like DocBook, ReST, mark down, wikis, etc. Which tool do you recommend?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

How do you manage documentation of your software p

Comments Filter:
  • I've not been a fan of wikis for this in the past, but my current company does this rather well. Wiki articles are started by developers as part of the design and coding process, and are monitored by the documentation team (which is small). As features make it to maturity, they are tweaked by the doc team and made available for more comment. When it's time to go live, the doc. team will do a draft edit, attract comments from interested parties, and then publish. At this point - and only at this point -

You are always doing something marginal when the boss drops by your desk.