documentation is a drag to write, but I have good experiences letting the users of the system writing the documentation. This way they get all the stuff out of the way only programmers think a user needs to know And only write down the sutff they need foor their daily jobs.

I certainly wasn’t pointing the finger at just FarCry! I think many times we get wrapped up in the application and forget the simple things like a basic readme.txt.

Unfortunately, FarCry is not just a CMS, but a framework designed to build web applications. Many prominent members of the FarCry community spend their time writing bespoke CMS solutions and other web applications. Typically these solutions are delivered complete with documentation — but its not necessarily documentation that is relevant or can be distributed.

One of my jobs for the Fortress release is to provide better hooks to existing documentation — of which there is lots. But as you say its currently a bit overwhelming in terms of where you start as a someone new to the framework.

So it looks like the only option is to write the documentation in parallel to the app. Ugh. Like anyone has time to write anything other than code. Not gonna work.

I like your suggestion. Get the users to write it. Adobe kinda halfway tried that with Livedocs. I think it was half a solution, the missing ingredient was someone on the Adobe side willing to maintain the docs and revise them in line with user comments. It would have made sense to offer a threaded discussion model as part of the view.