"we all know what sort of interface you end up with when its designed by committee"
Do you think the Style Guide was written by one person at Acorn? If more than one, then it was designed by exactly the mechanism you are criticising.
That minor technicality aside, another benefit to having the Style Guide online, which is one of allowing people who haven't forked out for the C Tools or the PRMs to read it - such as end users. There is a benefit to them reading it, since they then have the opportuniy to find out precisely *why* we've done this, that or the other in our programs. This doesn't necessarily have to be in the wiki format; simply having the PDF online would be sensible. However, having it in a more easily updatable form is better - Steve has already reminded me that there is additional information on the Iyonix website that is SG related; ideally all of this should be in one place, instead of split out into a main document and disparate supplemental notes.