It looks like my last post on documentation (or the lack thereof) has gathered some feedback (Hello Rigel :) so I just wanted to clarify a few points. Firstly, having previously edited books on programming, I find it very hard to read any technical material without a highly critical eye. I find myself getting frustrated when I see simple mistakes, shortcuts, and general sloppiness in articles. I experience similar pain in my day job when I encounter documentation written by others, and often have to stop myself from grabbing that documentation and helping to fix it when I'm supposed to...
I was tinkering about with Community Server yesterday to see what it was all about - it looks like a nice enough product, and it should be quite customisable, but finding out how to customise it will be another matter. It seems that much of the documentation is targeted at the day-to-day admins who will use the internal configuration options and settings to get the site looking and working the way they want it to, but when it comes to development-level customisation, where's the information I need? The clue turns out to be on the front page of the default...