Re: Documentation request
Upayavira wrote: Torsten Schlabach wrote: Thank you. Maybe there should be a link to this from the Cocoon site. This might make it more popular. It isn't intended for public consumption. It is intended as a backend system. So, we might publish it on some dev site, but not on the public site - in time, the content of the Daisy site should be uploaded to the public site. The Daisy plugin for Forrest is now "complete" and being used in a (small) production environment. If people start editing in Daisy, Forrest can create the standalone site for cocoon.apache.org and for distributions. You can create a separate navigation document within Daisy (or a site.xml document for Forrest) and use that to define what is made public. In other words, what is in Daisy need not be the publically published materials. Ross
Re: Documentation request
Guys, On 8/12/05, Upayavira <[EMAIL PROTECTED]> wrote: > It isn't intended for public consumption. It is intended as a backend > system. So, we might publish it on some dev site, but not on the public > site - in time, the content of the Daisy site should be uploaded to the > public site. On 8/12/05, Vadim Gritsenko <[EMAIL PROTECTED]> wrote: > Daisy is to edit website content, it still will be published to the main > cocoon.apache.org website - at least, that's the intention. Then let's tackle two problems at once by moving the current website content into Daisy (Bruno has already done most of it) and, after reviewing the current pages, produce a new version of the website through the use of Ross' Daisy-to-Forrest component (if that is more workable than the current procedure as updated on the wiki by Vadim) and repeat this process more frequently than now (maybe once a month, or after a certain number of modifications in Daisy). OTOH I don't see why Daisy should be "hidden" from the general user population. I myself rather see documentation in progress than static, incomplete documentation. The only "warning" we should put up is that it's subject to change, both content and outline. However, the search is very good, so it is very likely people will find what they are looking for. -- Bye, hepabolu
Re: Documentation request
Torsten Schlabach wrote: Note: I'm not sure whether cocoon.apache.org will be the "official cocoon documentation location" It will probably be for anyone interested in reading Cocoon documentation. Unless you remove *any* documentation from the site and make a bold link saying: This site does not have documentation - please go *here*! But what for is a project website if it does not contain the docu? Daisy is to edit website content, it still will be published to the main cocoon.apache.org website - at least, that's the intention. Vadim
Re: Documentation request
Torsten Schlabach wrote: Thank you. Maybe there should be a link to this from the Cocoon site. This might make it more popular. It isn't intended for public consumption. It is intended as a backend system. So, we might publish it on some dev site, but not on the public site - in time, the content of the Daisy site should be uploaded to the public site. Regards, Upayavira
Re: Documentation request
Thank you. Maybe there should be a link to this from the Cocoon site. This might make it more popular. Regards, Torsten > Torsten Schlabach wrote: > >>Where is that DAISY instance and how can I access it? >>Who can access it? Anyone or just Cocoon committers? >> >> > > http://cocoon.zones.apache.org/daisy/ > > Have to run now. > > Bye, Helma > >
Re: Documentation request
Torsten Schlabach wrote: Where is that DAISY instance and how can I access it? Who can access it? Anyone or just Cocoon committers? http://cocoon.zones.apache.org/daisy/ Have to run now. Bye, Helma
Re: Documentation request (was: Re: Bug# 34696 - Website update)
Where is that DAISY instance and how can I access it? Who can access it? Anyone or just Cocoon committers? > Note: I'm not sure whether cocoon.apache.org will be the > "official cocoon documentation location" It will probably be for anyone interested in reading Cocoon documentation. Unless you remove *any* documentation from the site and make a bold link saying: This site does not have documentation - please go *here*! But what for is a project website if it does not contain the docu? Regards, Torsten > Vadim Gritsenko wrote: > >> Torsten Schlabach wrote: >> >>> From the other answers I get the impression that there is a number of >>> people on the Cocoon project who are not aware of the process for the >>> Cocoon site. So maybe someone can find out and document it. >> >> >> http://wiki.apache.org/cocoon/CocoonWebsiteUpdate >> >> Needs some editing re CVS vs SVN, and cocoon-2.2 is not covered, but >> basics are there. >> > Thanks for updating the page Vadim. > > However, there is a more fundamental problem about the documentation: we > know what we want in the end (fabulous documentation on the website) and > what we have now (documentation of various quality scattered over > several places), but what to do in the mean time? > > Holidays have surely erased much of my memory ;-), so I'm trying again > to clarify things for myself. Do please chip in and correct me if I'm > wrong. > I've looked through the archives and tried to retrieve what was > generally agreed on: > > Current state: > documentation of varying quality in wiki, Daisy on Cocoon zone, website > and java docs. > > End result: > extensive, coherent, up-to-date documentation of excellent quality at > the website. Note: I'm not sure whether cocoon.apache.org will be the > "official cocoon documentation location" or the Daisy repository, but > that's a discussion that can be held much later in time. > > In between we need to build one documentation repository and AFAIR we > decided on Daisy on the cocoon zone. To me this means that ALL (yes ALL) > documentation pages need to be moved there, after a reviewing process. > > Bruno has helped out here by moving the doc pages from SVN BRANCHE 2.X > to a separate collection in Daisy. The "only" thing to be done now is > review these pages and move them to the actual documentation set. > Since then (June 17) some time has passed, so I will figure out what > changes have been done to the doc pages in SVN since then and > incorporate them into the Daisy version. I'll assume that updated pages > are worth keeping, so I'll also move them over to the "current" > documentation collection in Daisy. > > Requests: > - PLEASE DO THE UPDATES OF THE DOCUMENTATION IN THE WEBSITE IN DAISY! > - If you want to help, start by checking pages in the "legacy docs" > collection in Daisy and move them to the regular collection. > - Stop updating/adding doc pages in SVN. > > Once this is done, someone (Ross?, Reinhard?) could extract the > information and update cocoon.apache.org for the time being. > > Bye, Helma > > >
