background research to try to gather the
various past threads and docs. Perhaps this will help us to
bring the Cocoon documentation back to life.
In the past we had the sources for the docs in xml format
and then processed by Apache Forrest to generate the html pages.
A few years ago we moved
cycle.
Cheers, Alfred.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Freitag, 16. März 2012 10:46
To: dev@cocoon.apache.org
Subject: Website management [WAS Re: resurrect the Cocoon documentation]
Hi all,
yesterday, while looking
this work, just explain and guide.
I have done some background research to try to gather the
various past threads and docs. Perhaps this will help us to
bring the Cocoon documentation back to life.
In the past we had the sources for the docs in xml format
and then processed by Apache Forrest
. Perhaps this will help us to
bring the Cocoon documentation back to life.
In the past we had the sources for the docs in xml format
and then processed by Apache Forrest to generate the html pages.
A few years ago we moved to using the Daisy CMS to store/edit
all content for 2.1 and 2.2 versions
TL;DNR
Use the Apache CMS for at least our top-level docs
and the stalled 2.1 and 2.2 docs.
However, i cannot actually do this work, just explain and guide.
I have done some background research to try to gather the
various past threads and docs. Perhaps this will help us to
bring the Cocoon
Thorsten Scherler wrote:
On Fri, 2009-12-04 at 12:09 +0100, Reinhard Pötz wrote:
...
See
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs/src/docbkx/reference/
You can generate the documentation yourself by invoking 'mvn site' from
the base directory of the cocoon-docs
On Fri, 2009-12-04 at 12:09 +0100, Reinhard Pötz wrote:
...
See
http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs/src/docbkx/reference/
You can generate the documentation yourself by invoking 'mvn site' from
the base directory of the cocoon-docs module.
I tried that but I
Matt Whipple wrote:
Reinhard Pötz wrote:
Matt Whipple wrote:
Jos Snellings wrote:
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
I stumbled upon the HTML deliverable of that on
Currently there is an initialisation problem.
Anyway, Reinhard, you had a great table of contents. That is a good way
to get started: what nodes are missing? That way, we may fill in the
gaps, whilst trying our best to preserve unity of presentation writing
style
All docbook, I guess?
Jos
On
Jos Snellings wrote:
Currently there is an initialisation problem.
Anyway, Reinhard, you had a great table of contents. That is a good way
to get started: what nodes are missing? That way, we may fill in the
gaps, whilst trying our best to preserve unity of presentation writing
style
All
What editor do you use?.
(I mostly use XMLMind)
On Fri, 2009-12-04 at 12:09 +0100, Reinhard Pötz wrote:
Jos Snellings wrote:
Currently there is an initialisation problem.
Anyway, Reinhard, you had a great table of contents. That is a good way
to get started: what nodes are missing? That
Jos Snellings wrote:
What editor do you use?.
(I mostly use XMLMind)
yes, either XMLMind or I use use a schema-aware editor.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the
Jos Snellings wrote:
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
I stumbled upon the HTML deliverable of that on
http://people.apache.org/~reinhard/c3-ref/html/ after sending my email.
I'd think it would be
Yes, that would be it...
agreed.
On Tue, 2009-12-01 at 06:23 -0500, Matt Whipple wrote:
Jos Snellings wrote:
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
I stumbled upon the HTML deliverable of that on
Matt Whipple wrote:
Jos Snellings wrote:
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
I stumbled upon the HTML deliverable of that on
http://people.apache.org/~reinhard/c3-ref/html/ after sending my email.
Reinhard Pötz wrote:
Matt Whipple wrote:
Jos Snellings wrote:
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
I stumbled upon the HTML deliverable of that on
I'm a recent transplant to Cocoon (and Java), in particular because
Cocoon 3 appears as though it is/will be closely in line with my own
perspective on web application development. I'm interested in
contributing to the development of the framework itself, but likely
won't be able to produce
The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs
The cocoon community will be delighted at some good documentation.
Talking about community I fear such as an active community is to be
reestablished, so I think we'd better
Robby Pelssers wrote:
My ICLA has just been sent to secret...@apache.org.
Happy to contribute,
Robby
Thanks, i see that it is now recorded in SVN.
-David
@David
My ICLA has just been sent to secret...@apache.org.
Happy to contribute,
Robby
-Original Message-
From: David Crossley [mailto:cross...@apache.org]
Sent: Friday, September 18, 2009 5:10 AM
To: dev@cocoon.apache.org
Subject: Re: editing rights Cocoon documentation for user
On Sep 16, 2009, at 8:55 AM, Robby Pelssers wrote:
Can you grant editing rights to useraccount ‘robbypelssers’ for the
cocoon documentation?
Done
Vadim
Vadim Gritsenko wrote:
Robby Pelssers wrote:
Can you grant editing rights to useraccount ?robbypelssers? for the
cocoon documentation?
Done
Thanks for helping Cocoon, Robby.
Would you please also send in a Contributor License Agreement
http://apache.org/licenses/#clas
-David
Hi,
Can you grant editing rights to useraccount 'robbypelssers' for the
cocoon documentation?
Cheers,
Robby Pelssers
design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: https://issues.apache.org/jira/browse/COCOON-1680
Project: Cocoon
Issue Type: Improvement
Components
integration
OSGi-based Cocoon documentation
---
Key: COCOON-1826
URL: https://issues.apache.org/jira/browse/COCOON-1826
Project: Cocoon
Issue Type: Task
Components: - OSGi integration
Reporter
[EMAIL PROTECTED] wrote:
Author: bruno
Date: Thu Mar 8 11:00:50 2007
New Revision: 516147
URL: http://svn.apache.org/viewvc?view=revrev=516147
Log:
Modified the sitemaptags2daisy tool so that documents are added to a block-dependent collection (cdocs- +
block name) instead of the fixed
Hi Reinhard, Helma and others,
A big thanks (again!) for your work on the documentation.
With my sceptical hat on, I took a quick glimpse at
http://cocoon.zones.apache.org/dev-docs/, and found myself actually pretty
surprised by the refreshing new look. :)
But I hope you don't mind if I add
Arje Cahn wrote:
Hi Reinhard, Helma and others,
A big thanks (again!) for your work on the documentation.
With my sceptical hat on, I took a quick glimpse at
http://cocoon.zones.apache.org/dev-docs/, and found myself actually pretty
surprised by the refreshing new look. :)
But I hope you
Arje Cahn said the following on 6/11/06 16:29:
News on the homepage: excellent!! I love it. It would be better if we
could have the date presented as part of the title:
# 10/18/06: News Management in our Docs smallsubmitted by Ross
Gardler, 10/18/06 9:59:32 PM/small
I tend to disagree on
2006/11/3, Reinhard Poetz [EMAIL PROTECTED]:
2 weeks ago, Arje posted a long list of things that need to be improved with our
website and documentation. I can't say that all the things are resolved but
Helma and I have made good progress:
Thanks for your effort - it's really a big step
Andreas Hochsteger wrote:
May I get some karma to edit the docs in Daisy?
My username is 'ahochsteger'.
done
--
Reinhard Pötz Independent Consultant, Trainer (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
2006/11/5, Reinhard Poetz [EMAIL PROTECTED]:
Andreas Hochsteger wrote:
May I get some karma to edit the docs in Daisy?
My username is 'ahochsteger'.
done
Thanks!
Just trying to get familiar with Daisy now ... looks really good to me, BTW!
--
Andreas
Great work!
Is there any possibility to change the order of the navigation items,
for example, if you look at:
http://cocoon.zones.apache.org/dev-docs/core-modules/core/2.2/
The first main topic is about blocks and further down the list is the
core. I think this should be the other way round,
Carsten Ziegeler wrote:
Great work!
Thank you :-)
Is there any possibility to change the order of the navigation items,
for example, if you look at:
http://cocoon.zones.apache.org/dev-docs/core-modules/core/2.2/
The first main topic is about blocks and further down the list is the
core. I
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Great work!
Thank you :-)
Is there any possibility to change the order of the navigation items,
for example, if you look at:
http://cocoon.zones.apache.org/dev-docs/core-modules/core/2.2/
The first main topic is about blocks and further
2 weeks ago, Arje posted a long list of things that need to be improved with our
website and documentation. I can't say that all the things are resolved but
Helma and I have made good progress:
- Following the split up of Cocoon (the code) we also split up the
documentation into much
[ http://issues.apache.org/jira/browse/COCOON-1826?page=all ]
Reinhard Poetz updated COCOON-1826:
---
Summary: OSGi-based Cocoon documentation (was: Documentation)
use a more specific name
OSGi-based Cocoon documentation
Bruno Dumon wrote:
OTOH, having the docs
split up between a lot of little maven-sites might lessen the overview.
Because of the nature of Daisy this shouldn't become a problem:
- we can have one navigation document which is a collection of all
block navigation docs
- we have Daisy books
Bruno Dumon wrote:
On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote:
hepabolu wrote:
Finally, adding the proposed plugin can always be added later without
loosing the effort of the current setup.
ok, that's right. Anyway, I can't do it myself now but if somebody is
interested, I
On Tue, 2006-03-07 at 09:06 +0100, Reinhard Poetz wrote:
Bruno Dumon wrote:
OTOH, having the docs
split up between a lot of little maven-sites might lessen the overview.
Because of the nature of Daisy this shouldn't become a problem:
- we can have one navigation document which is a
As written in my mail Status of block development
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I propose
a change in the Cocoon documentation creation:
We have put a lot of work into the Mavenization of the Cocoon build system. As
you might know, Maven provides
Reinhard Poetz schrieb:
As written in my mail Status of block development
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I
propose
a change in the Cocoon documentation creation:
We have put a lot of work into the Mavenization of the Cocoon build system.
As
you
Carsten Ziegeler wrote:
Reinhard Poetz schrieb:
As written in my mail Status of block development
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I propose
a change in the Cocoon documentation creation:
We have put a lot of work into the Mavenization of the Cocoon build
Carsten Ziegeler said the following on 06-03-2006 17:49:
I'm more than +1 for getting the reports Maven provides for us on our
website. I'm not
sure if we need a plugin for the daisy docs or if just linking from the
maven generated site is enough. Whatever works best.
Let's do this one step at
hepabolu wrote:
Finally, adding the proposed plugin can always be added later without
loosing the effort of the current setup.
ok, that's right. Anyway, I can't do it myself now but if somebody is
interested, I can help. Maybe some of the Daisy gurus here can comment on the
idea itself?
hepabolu schrieb:
Carsten Ziegeler said the following on 06-03-2006 17:49:
I'm more than +1 for getting the reports Maven provides for us on our
website. I'm not
sure if we need a plugin for the daisy docs or if just linking from the
maven generated site is enough. Whatever works best.
Reinhard Poetz wrote:
As written in my mail Status of block development
(http://marc.theaimsgroup.com/?l=xml-cocoon-devm=114165989221631w=2) I
propose a change in the Cocoon documentation creation:
We have put a lot of work into the Mavenization of the Cocoon build
system. As you might
On Mon, 2006-03-06 at 18:39 +0100, Reinhard Poetz wrote:
hepabolu wrote:
Finally, adding the proposed plugin can always be added later without
loosing the effort of the current setup.
ok, that's right. Anyway, I can't do it myself now but if somebody is
interested, I can help. Maybe
help a lot.
New design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: http://issues.apache.org/jira/browse/COCOON-1680
Project: Cocoon
Type: Improvement
Components: - Documentation
[ http://issues.apache.org/jira/browse/COCOON-1680?page=all ]
Jörg Heinicke reassigned COCOON-1680:
-
Assign To: Cocoon Developers Team
New design/ layout proposal for Cocoon documentation
. if there are rules on that. It would surely free
up space.
Keep up the good work.
New design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: http://issues.apache.org/jira/browse/COCOON-1680
Project
[
http://issues.apache.org/jira/browse/COCOON-1680?page=comments#action_12357153
]
Upayavira commented on COCOON-1680:
---
Keep the feather, in some form, but _much_ smaller.
New design/ layout proposal for Cocoon documentation
be better then current one. Probably PRC
should have it...
New design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: http://issues.apache.org/jira/browse/COCOON-1680
Project: Cocoon
Type
Attachments: asf20051107.zip, screenshot.gif
I made new design/ layout proposal for Cocoon documentation. Just one html
and screen css. I understand you need to modernize site (see Upayavira
comment for COCOON-1679). This is my try, I hope you like it.
There are two layouts user can choose
[ http://issues.apache.org/jira/browse/COCOON-1680?page=all ]
Milan Andrejevic updated COCOON-1680:
-
Attachment: screenshot.gif
version 2
New design/ layout proposal for Cocoon documentation
[ http://issues.apache.org/jira/browse/COCOON-1680?page=all ]
Milan Andrejevic updated COCOON-1680:
-
Attachment: asf20051108.zip
version 2
New design/ layout proposal for Cocoon documentation
, modern, but still
connected to the 'Cocoon' brand, with the logo, maybe with colours, etc.
So, be wild. Then we'll let this community restrain you. But if you start
restrained, I'm scared we'll end up with something boring :-(
New design/ layout proposal for Cocoon documentation
New design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: http://issues.apache.org/jira/browse/COCOON-1680
Project: Cocoon
Type: Improvement
Components: - Documentation
Reporter: Milan
[ http://issues.apache.org/jira/browse/COCOON-1680?page=all ]
Milan Andrejevic updated COCOON-1680:
-
Attachment: screenshot.gif
screenshot
New design/ layout proposal for Cocoon documentation
compatible with user expectations.
I like it that the search bar is less prominent but as a whole I find the top
block very cluttered. Is it possible to reduce the left image with the feather?
New design/ layout proposal for Cocoon documentation
structure for top
menu(s) and sidebar menu you would like to have.
I assume they are used for keyboard shortcuts?
Yes you assume right.
New design/ layout proposal for Cocoon documentation
Key: COCOON-1680
URL: http
David Crossley wrote:
Ross Gardler wrote:
hepabolu wrote:
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
We have always needed this, but not possible with the
current setup of the project publishing mechanism
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
Several reasons:
- frequent updates show users that there is concern about their
documentation wishes. We might even write documentation that answers
FAQs and point
hepabolu wrote:
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
Several reasons:
- frequent updates show users that there is concern about their
documentation wishes. We might even write documentation that answers
hepabolu wrote:
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
snip what=details of proposal/
All sounds great, in fact, most of the automated publishing side an be
done by the ForrestBot. See http
Ross Gardler wrote:
hepabolu wrote:
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
We have always needed this, but not possible with the
current setup of the project publishing mechanism at apache.org
Le 26 juil. 05, à 00:53, Mark Leicester a écrit :
...I've found that http://cocoon.zones.apache.org/daisy/ seems to be
down. Can anyone advise on the status?..
For some reason most services were stopped on the zone, I have
restarted them.
FYI zone admins, here's what I had to do:
(as
Bertrand Delacretaz wrote:
Le 26 juil. 05, à 00:53, Mark Leicester a écrit :
...I've found that http://cocoon.zones.apache.org/daisy/ seems to be
down. Can anyone advise on the status?..
For some reason most services were stopped on the zone, I have restarted
them.
Probably because
Le 26 juil. 05, à 11:15, Upayavira a écrit :
...Probably because Helios was restarted to get access to additional
storage. We need to have init scripts in place if we don't have
already...
I thought we had for Daisy, but apparently not. And the disappearing of
/var/run/apache2 is
Hi all,
After an absence from things Cocoon for a few weeks, I've just popped
back to a little more documenting, but I've found that
http://cocoon.zones.apache.org/daisy/ seems to be down. Can anyone
advise on the status?
Cheers,
Mark
As explained in a private mail to Sebastien, I've taken up the
http://www.cocoondev.org/handbook site that Steven graciously set up for me. I
intend to work on the mid-level tutorial that was the initial goal for the
Cocoon In Action project.
Doing it in Daisy is much easier for me, since it
Linden H van der (MI) wrote:
As explained in a private mail to Sebastien, I've taken up the http://www.cocoondev.org/handbook site that Steven graciously set up for me. I intend to work on the mid-level tutorial that was the initial goal for the Cocoon In Action project.
Doing it in Daisy is much
As explained in a private mail to Sebastien, I've taken up the
http://www.cocoondev.org/handbook site that Steven
graciously set up for me. I intend to work on the mid-level
tutorial that was the initial goal for the Cocoon In Action project.
Doing it in Daisy is much easier for me, since
On 12 May 2005, at 14:01, Sylvain Wallez wrote:
Linden H van der (MI) wrote:
As explained in a private mail to Sebastien, I've taken up the
http://www.cocoondev.org/handbook site that Steven graciously set up
for me. I intend to work on the mid-level tutorial that was the
initial goal for the
or later.
This means that the pages of this handbook can be included in the
official Cocoon documentation by simply adding links in the existing
site definition. It will be included with the Cocoon skin and navigation
and therefore the integration is seemless.
This plugin is curently
Great! Thanks for the offer, but let's wait until there is more than one
or two pages of information.
Bye, Helma
-Original Message-
From: Ross Gardler [mailto:[EMAIL PROTECTED]
Sent: Thursday, 12 May, 2005 14:48
To: dev@cocoon.apache.org
Subject: Re: Cocoon documentation (was: RE
Linden H van der (MI) wrote:
As explained in a private mail to Sebastien, I've taken up the http://www.cocoondev.org/handbook site that Steven graciously set up for me. I intend to work on the mid-level tutorial that was the initial goal for the Cocoon In Action project.
Doing it in Daisy is much
David Crossley wrote:
Here is one thing that i cannot grasp yet:
How will the automatically generated Sitemap Component Documentation
(i.e. the old /userdocs/) fit in with these static repositories?
Currently we need to run 'build docs' to prepare them, then do 'forrest'.
David Crossley wrote:
Reinhard Poetz wrote:
Last week Upayavira and I spent some time to overhaul the structure of the
two
document repositories:
- http://brutus.apache.org/docs/build/cocoon-doco-2-2/
- http://brutus.apache.org/docs/build/cocoon-doco-global/
We think that it covers all Cocoon
Reinhard Poetz wrote:
David Crossley wrote:
Here is one thing that i cannot grasp yet:
How will the automatically generated Sitemap Component Documentation
(i.e. the old /userdocs/) fit in with these static repositories?
Currently we need to run 'build docs' to prepare them, then do
Upayavira wrote:
David Crossley wrote:
Here is one thing that i cannot grasp yet:
How will the automatically generated Sitemap Component Documentation
(i.e. the old /userdocs/) fit in with these static repositories?
Currently we need to run 'build docs' to prepare them, then do 'forrest'.
David Crossley wrote:
Upayavira wrote:
David Crossley wrote:
Here is one thing that i cannot grasp yet:
How will the automatically generated Sitemap Component Documentation
(i.e. the old /userdocs/) fit in with these static repositories?
Currently we need to run 'build docs' to prepare them, then
Upayavira wrote:
David Crossley wrote:
Upayavira wrote:
David Crossley wrote:
Here is one thing that i cannot grasp yet:
How will the automatically generated Sitemap Component Documentation
(i.e. the old /userdocs/) fit in with these static repositories?
Currently we need to run 'build docs' to
Reinhard Poetz wrote:
Upayavira wrote:
David Crossley wrote:
[snip]
The trouble that i have with the new documentation proposal is that
docs sources are moving to another part of the repository, so how
will 'build docs' be able to access them? I suppose that assumed default
relative
Reinhard Poetz wrote:
Last week Upayavira and I spent some time to overhaul the structure of the
two
document repositories:
- http://brutus.apache.org/docs/build/cocoon-doco-2-2/
- http://brutus.apache.org/docs/build/cocoon-doco-global/
We think that it covers all Cocoon relevant
Last week Upayavira and I spent some time to overhaul the structure of the
two
document repositories:
- http://brutus.apache.org/docs/build/cocoon-doco-2-2/
- http://brutus.apache.org/docs/build/cocoon-doco-global/
We think that it covers all Cocoon relevant topics and is a good starting point
to
Andreas Kuckartz wrote:
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have
to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or not, but in this case
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
Bertrand Delacretaz wrote:
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or
Actually, and I'm not joking, I think we should have a hero plate on our
web page and put the name and have a nomination!... some ego stimulation
goes a lng way... h
Wow, employee^H^H^H^H^H^H^H^Hcommitter of the month! Now that would
feel like working at McDonald's :-)
--
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
...
tell you what. forget about it for now. Think about going dynamic and
later we'll find a way to make a persistent copy of that (either via
forrest or simply by wget or something)
+1
Forrest - pardon my rudeness - sucks as a static site
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation system.
I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Cheers,
Andreas
Andreas Kuckartz wrote:
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation system.
I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Nothing or as less as the use of
- Daisy,
- Hippo CMS (if it is really OS
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had thought that that was to be a
Andreas Kuckartz wrote:
Look at http://wiki.apache.org/cocoon/CocoonDocumentationSystem and find all
my
requirements. I'm sure that all six options are good enough but as *I* have to
do it, I'll take the road that's the fastest for *me*.
There was a misunderstanding on my side. I had thought that
On 18 Jan 2005, at 09:59, Reinhard Poetz wrote:
Andreas Kuckartz wrote:
Nicola Ken Barozzi wrote:
Forrest - pardon my rudeness - sucks as a static site generation
system. I can't wait to have it shine as a dynamic system :-)
What prevents the use of Apache Lenya ?
Nothing or as less as the use of
Le 18 janv. 05, à 09:59, Reinhard Poetz a écrit :
...as *I* have to do it, I'll take the road that's the fastest for
*me*...
+1, whoever does the work gets to decide (and later the community
decides to use the stuff or not, but in this case I'm not worried ;-)
-Bertrand
smime.p7s
Description:
to provide a 24/7 support.
Maybe my attempt will fail, don't know. Maybe somebody else will jump in then, I
don't know. Maybe it's the start of a new area in Cocoon documentation, who knows.
I think it will be very hard to combine both
editorial and technical/logistical work.
I'll concentrate
. Maybe it's the start of a new area in
Cocoon documentation, who knows.
I think Cocoon needs better documentation, not a new area. ;-)
What I fail to understand is your apparent eagerness to get going, yet
you want to focus first on rebuilding things which are already readily
accessible. IMHO
my attempt will fail, don't know. Maybe somebody else
will jump in then, I don't know. Maybe it's the start of a new area in
Cocoon documentation, who knows.
I think Cocoon needs better documentation, not a new area. ;-)
meant era ;-)
What I fail to understand is your apparent eagerness to get
1 - 100 of 165 matches
Mail list logo
