Moving On...
After a little research into the matter, I think I'm going to utilize the google app engine to serve up a static web page that I will be either manually generating, or creating with a web page editor... In either case, it will be free and only serve the purposes of aggregating information about Hieroglyph. It sounds fairly easy to setup, and I'm quite familiar with Python in case I ever want to play around with some cloud computing applications.
I've also been looking into documentation generators. I have never been fond of generated documentation, but I think it is something that will help clarify many questions without too much interaction on my part. Since I have never used any of these things, I would appreciate any hints on what you think think works and what doesn't. It will be a huge undertaking to reformat all of my comments to match a tool, and I don't want to use up all of my development time for nothing!
I am also preparing to start work on a compute shader based particle system. Right now I am reviewing the CS based particle system samples in the DXSDK and looking around the web for any examples (I haven't found any yet...). So far, the NBodyGravityCS11 sample is all that I have to go on.
One quick link before I go - MSDN has a preview of what the June DXSDK is changing up here. I found the PIX changes to be a nice, and was pleasantly surprised to see that they have added debugging functions to HLSL... Can you call a printf() from all 1024x768 pixel shader invocations???
I'd suggest you look into doxygen. It's defacto standard for documenting C/C++ code. Easy one-time setup. Documentation generation is as easy as running a single command. When finished you just copy the output html folder to your webserver. The comment format is also quite simple and non-intrusive (compared to e.g. the .Net documenting format which uses xml tags).
Martin