Proper documentation should be a priority. I've put this off for GHAR because I wasn't sure how the specifications were going to change. I'll try to be more responsible (and responsive- sorry to anyone who sent me email recently and got either a terse or no response) on this front.
We all understand that things happening in one's offline life take precedence. Or at least I hope so- certainly I do. It would be smarter to know what's going to change before writing up documentation on it, so.... yeah. 
Definitely with Loose on this. "We understandz". But Joe, I'm sure we all would love for you to hang out on the forum a bit more, so it's good to hear you saying that you intend to.
+1. After lurking for a year or so, yeah, I miss the people who contributed what I'm reading, playing, dreaming up improvements for, and making notes on. But I also realize that people have offline needs too. No worries.
Also, it definitely makes sense to postpone documentation for a prototype-ish thing like GHAR. Documentation is always a difficult thing. Personally I like specifications-based approach to development, as well-formed design specs can adequately serve as documentation, besides helping to structure and organize coding. Of course that doesn't work so well for making non-technical user docs... Arghh, I digress again.
As I've offered, I can take a shot at trying to translate technical into non-technical, or at the least be a person who lets the technical folks know when something isn't coming through. Let me know what you need processed.
