Generating/creating library documentation?

First, I apologize if this is in the wrong place; I wasn't sure where this should go, but 'Other Software Development' seemed the closest fit.

Anyway, I wanted to ask what (if anything) people are using to create/generate library documentation. The library I created for a shield I've designed is fairly large and still in active development. I would really like to avoid having to maintain both the code and docs in parallel; it's too easy for them to get hopelessly out of sync. Out of habit, I've used the standard JavaDoc/EpyDoc-style comments, but the tools that generate HTML from those produce practical but ugly pages which are confusing to casual users. Ultimately, I'd like the documentation to look more like the Arduino/Processing references.

So, can anyone recommend any tools or techniques? If no 'pretty' doc generator exists, I'm tempted to build my own using docutils (http://docutils.sourceforge.net/), but that's a significant project unto itself. I'm also interested in any tips on maintaining code and docs without automatic generation, should it come to that.

Thanks!

some people write the documentation after the code stabilizes ...

Doxygen is probably the easiest, and makes the least mess of the source code.
I'm pretty sure it's available for Windows as well as Linux.

Will