I've added an Errata section to the wiki at http://coda.wikidev.net and added some notes on the 'Coda Admin and User Manual' before running out of steam. I hope this can at least give an indication of where the documentation has become outdated and misleading. It's not much yet, but it's a start. I've plenty more to add, and should get back to it later in the week. I think there's scope for working Patrick's "Optimizing Coda 6" work into the Admin guide too.
On Monday 11 April 2005 16:28, Patrick Walsh wrote: > I'm really glad the coda team will be updating the documentation. As a > new user, I printed out the user manual, the howto, and a linux journal > article and studied them closely before attempting an install. > Unfortunately, most of the notes I took on reading that documentation > have proved to be outdated and not useful. There are sections that give > steps that are no longer applicable. So I would first recommend > identifying the parts of the manual that are outdated and fixing them. > > Second, there are a lot of implementation decisions to make and a lot > of conflicting advice. A guide to making administrative decisions would > be very helpful. I'm attaching my latest draft of "Optimizing Coda 6" > which puts down in writing some of the important configuration trade > offs and limitations of coda that a new coda admin needs to know before > making any setup decisions. > > I think the coda team should concentrate on precise and accurate > documentation (option a) and leave the howto's and newbie tutorials to > the community. And I promise the community would contribute a lot more > of this if there were an easier way to contribute, such as a wiki. > > Just my two cents.
