How do you document your ROS packages?
There are 100s of places where one can put documentation info about their ROS package code: <documentation> strings in package.xmls, Github readme pages (assuming your code is hosted on Github), Github pages of your repos, your project website, ROS wiki pages, tutorials on ROS wiki or your website or wherever else, Sphynx doc generator and other doc tools, man pages, in-code comments, obviously, etc. etc. (of course, many of these are supposed to be used on different levels of detail). It gets especially problematic when your project is separated into multiple subprojects, each hosted in their own repository, which makes it harder to get the big picture.
So, to those few out there that actually have experience documenting their (preferably open-source) code, any hints on how you organize this for huge projects and, if the documentation is not only in one place, how do you maintain it to reflect the ongoing changes in the code?
