This is not open access like the wiki, so if you want to contribute either post your submissions to this forum or, if you intend to do a lot, ask me to set-up a user account for you.
I'm currently hashing out a good structure for the documentation itself which I intend to try and perfect in the next few days. Comments and opinions to this end would be greatly appreciated at this stage, less so when people start to write information into that structure. So speak now or forever hold your peace, well, at least until the next update.
Even if you don't fancy getting down to writing the nuts and bolts stuff, we really need case studies. This is just a short feature about how you applied CMSMS to solve a problem, how well it worked (including shortcomings), what did the old system ran on (if at all), what other solutions/CMSs you tried (if any), what the client said (if you weren't the client), how you customised it, etc. These really help people figure out if CMSMS is right for them, help give designers and users more ideas and will help some of the guys coding to see how it's working for people other than themselves in more detail.
As well as written contributions we also need a good CMSMS template that makes sense for a documentation book, so if web/graphic design is more your forte than writing you can help too.
We also need someone to take lots of screenshots and save them (gif usually results in nice and tiny file sizes) of sections of the admin area, plug-ins, individual buttons in the editor, etc. So if you're no writer or web-designer you can still help by providing those but please make sure they are logically named as there will be lots of them by the time we're done.
If you're more into coding then we need a previous/next/up link tag to put at the bottom of each page to make the navigation more book-like, and if you can think of anything else that might make CMSMSs documentation that bit better then get to it - I've got a few ideas in progress so perhaps I'll post those in a few days when I've thought more about it.
Also, if you're a bit nifty with another language (usually because it's your first), let me know and perhaps we can get a bit of a rolling translation effort in progress. I'll have to look more into it's co-ordination as of yet, as I can imagine the documentation is going to be rather in limbo for the next few weeks and I don't want to see translation work having to be done twice and other frustrating things.
Thanks for the help in advance guys, let's see if team documentation can beat the fine gentlemen coders to 1.0
