Ian Bicking: the old part of his blog  Decomposing Document
Generation  The Python code documentation systems available
are... scattered. And not very good. And definitely not well
maintained. Lately when I see a hard problem that isn't getting
solved well, I like to think of smaller problems that maybe
could be solved.  Here's a rough outline of what I think a
Python documentation generation system should look like:  I
prefer a system based on static publishing because it's easy to
maintain, and works well with systems like SourceForge. But in
theory pieces of this system could be dynamic.  This bears some
similarity to how PythonDoc is laid out, but it hasn't been
clear to me how that project fits all these pieces together.
Also some portions don't seem pluggable; e.g., it prefers its
own markup. But that might be a misperception.  Created 30 Jun
'06   I think the issue is that you can't really generate useful
documentation from code, so I think any system designed to do so
will be only slightly useful at b