From dev-return-73796-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Mon May 02 14:37:51 2005 Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 25226 invoked from network); 2 May 2005 14:37:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 May 2005 14:37:49 -0000 Received: (qmail 7601 invoked by uid 500); 2 May 2005 14:39:11 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 7522 invoked by uid 500); 2 May 2005 14:39:10 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 7506 invoked by uid 99); 2 May 2005 14:39:10 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from odoko.co.uk (HELO odoko.co.uk) (80.68.92.132) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 02 May 2005 07:39:10 -0700 Received: from elfriedeholmes.demon.co.uk ([80.177.165.206] helo=[10.0.0.3]) by odoko.co.uk with asmtp (Exim 4.34) id 1DSc6F-0000Vr-No for dev@cocoon.apache.org; Mon, 02 May 2005 15:40:43 +0100 Message-ID: <42763B34.1040808@upaya.co.uk> Date: Mon, 02 May 2005 15:37:40 +0100 From: Upayavira User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator References: <20050502061119.E4F6D29C@ajax.apache.org> <90a75eb105050207261e0d0277@mail.gmail.com> In-Reply-To: <90a75eb105050207261e0d0277@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Geoff Howard wrote: > Upayavira, > > As I've only been able to marginally follow the new 2.2 docs strategy > (especially because there have been several I think over time!) :) I > wasn't sure what to do with this doc in 2.2. I also am not clear how > much of it will be accurate in 2.2. > > I'll try to take a look at some point and come up with a logical place > for it. I have the link to the new docs on brutus, but poking around, > things seem pretty rough still. Where is the current authoritative > menu structure? Well, the simplest thing to do is to create a folder in trunk/src/documentation/src/content/xdocs, say, called c21-custom-installer. Copy the meta-meta.xml and comments_en.xml from any other folder (change the legacy filename in meta), and add your own content_en.html file for the content of your page. Basically, if you create a page prefixed with c21, that says that the page has not yet been converted from Cocoon 2.1, and needs to be verified and confirmed in terms of functionality with Cocoon 2.2. Which means it is _perfectly_ safe to copy your page (as HTML, preferably, although content_en.xml should still work) into the 2.2 repos without worrying whether it will work or not on 2.2. Worrying about that will be someone else's job! Thanks, Regards, Upayavira