On 15 May 2004, David Crossley wrote: > Derek Hohls wrote: > > Matthew > > > > Obviously have been through the whole process you are in > > the best position to understand this issue. > > > > Is there not some room for an "intemediate" approach - > > a *series* of articles on key topics published in on-line > > magazines - reasonably well-researched and edited; which > > effectively become what would have been chapters in a book. > > Sure, there is room for all sorts of approaches. > > The best approach that i see, is to develop our own Cocoon > documentation (xdocs and wiki) to be those "articles on key topics". > That way it can be a group effort.
i agree, if the on-line information about a product is enough then you dont need a book. think about PHP anyone can live (and build php based web sites) without a "PHP Book", just using google --stavros > > --David > > > As you say, maybe its more for the prestige and > > reputation rather than the money... but it would also serve > > to both bolster Cocoon's status and become the defacto > > documentation for all the new features? > > > > Just my .2c > > Derek > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
