Why not use Silverstripe ?

Some earlier mentioned they couldn't update the documentation at doc.silverstripe.com, citing it was labelled 'read only'.

The doc.silverstripe.com wiki is certainly open to anyone to edit, and we'd love for each and everyone to do so when they have constructive and accurate edits to make

If you look at:
http://doc.silverstripe.com/doku.php?do=recent

You will see that a number of people are happily making contributions; it is not a right of the core developers alone

@ Ingo & Sigurd
Thanks for your replies. But a wiki or changing the current docs is not really what I meant. I assume Silverstripe would like feedback/usergenerated documentation, so it needs to be as easy as possible. Personally, editing the docs as Sigurd suggested is a huge hurdle for me and others. I'm not quite that far yet with how Silverstripe works ("constructive and accurate edits" which are open to anyone?) and don't wish to take the time to word everything fully and explain in complete detail, so you're really limiting the user feedback you're getting if you only keep it that way. Sometimes I just have a simple little blurb of code to contribute or a tip/trick, which is what comments were made for.

And you'd be introducing mistakes in the docs (or would have to filter for them which takes time) and there still wouldn't be room for quick little tips/tricks like in the php docs. Using comments makes it simple and easy for users. And that way there is a clear line between usergenerated stuff (possible errors) and the "official" Silverstripe docs.

http://wiki.splitbrain.org/plugin:discussion doesnt appear to be abandoned? Looking at the recent changes theres quite a steady stream of changes / updates to the project. To me that seems like the easiest way to allow comments on the wiki pages. Rather then change the whole wiki software or bring in external sources. The Demo doesn't appear too slow - http://demo.chimeric.de/discussion and most of our pages would hopefully not have this amount of comments.