Return-Path: Mailing-List: contact cocoon-docs-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-docs@xml.apache.org Received: (qmail 66667 invoked from network); 6 Jul 2002 05:11:10 -0000 Received: from ptolemy.goulburn.net.au (203.28.11.5) by daedalus.apache.org with SMTP; 6 Jul 2002 05:11:10 -0000 Received: (qmail 29422 invoked from network); 6 Jul 2002 05:11:20 -0000 Received: from max-02-019.goulburn.net.au (203.28.11.208) by ptolemy.goulburn.net.au with SMTP; 6 Jul 2002 05:11:20 -0000 Subject: Re: WebServiceProxyGenerator Docs From: David Crossley To: cocoon-docs@xml.apache.org In-Reply-To: <020d01c22447$43b21f20$6502a8c0@IIVANOV2> References: <020d01c22447$43b21f20$6502a8c0@IIVANOV2> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 06 Jul 2002 15:11:18 +1000 Message-Id: <1025932279.2182.1096.camel@ighp> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 22 Ivelin Ivanov wrote: > Diana, > > Can this article fit somewhere in the online documentation? > > http://cocoonhive.org/2002_06_30_cocoon_archive.html#78577876 > > At least until a good soul like Heidi writes a decent HOWTO ;) Yes please. You are the publisher, so there should be no problems with you modelling a cocoon doc on that. It seems that a short doc in userdocs/generators/ would be a good start. Others can then follow with a howto doc. Aside: I am brewing a posting to cocoon-docs about ways to ensure that anyone who develops a Cocoon facility must accompany it with at least a basic doc. --David