Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37882 invoked by uid 500); 26 Apr 2002 09:16:44 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 37871 invoked from network); 26 Apr 2002 09:16:44 -0000 Date: Fri, 26 Apr 2002 05:19:45 -0400 Subject: tracks/titles [was: Re: --- Help with document classification ---] Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v472) From: Diana Shannon To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <20020426055735.B4DBD23CDC@dj.codeconsult.ch> Message-Id: X-Mailer: Apple Mail (2.472) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On April 26, 2002, Bertrand Delacretaz wrote: Very helpful comments, Bert. > 1) Tracks: > it might be worthwile at some point to create "tracks" into the > documentation, task-oriented reading guides. > > For example: if you want to publish static XML to HTML, here's your > reading > list: "FAQ 232, FAQ 321, html publishing how-to, site navigation guide" Do you think these need separate classification, or should they be how-tos (with links to other how-tos), categorized as tracks? > > 2) Master of the Titles: > Document names/titles (and their consistency) are sooo important IMHO to > guide the user to the right place, I think the main title of every > document > should be reviewed by the community or by a designated "Master of the > Titles" > before publishing the document. What if we also added a one-sentence description of the piece, along with title and last modified date, to be returned with search results? Diana --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org