Bertrand
Good points - I think if we first agree on what the real problem
is then it will easier to find a solution for it. Here's my
first draft:
Problem:
* Users cannot get quickly started with Cocoon
Causes (?)
1. The existing Cocoon documentation is poorly written
2. The existing Cocoon documentation is poorly structured
3. There are gaps in the existing Cocoon documentation
4. Some of the existing Cocoon documentation is located
in more than one site
5. ...(other issues related to installation/file size etc etc)
Not all of these causes demand the same solution - where
do we need to focus effort first??
>>> [EMAIL PROTECTED] 27/01/2003 12:47:25 >>>
Derek Hohls wrote:
> Bertrand
>
> I think you are making the same point as me... just proposing
> a different solution. I still feel that if we are using a system that
> is based on the philisopy of "write once, publish anywhere" we
> should be able to create documents in one place and have them
> published in more than one place in more than one style.
Why not - the problem IMHO is the content, and how easy/hard it is to
access it.
>. . .
> PS we need to avoid creating more jargon - I always think of NCC
> as part of the Starship Enterprise 's call sign (there, that gives *my*
> age away!)
Yes, agreed. If I got it right your ultimate aim is to improve the
tutorial part of the Cocoon docs, so there's no need for a new acronym.
-Bertrand
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
>>> [EMAIL PROTECTED] 27/01/2003 12:47:25 >>>
Derek Hohls wrote:
> Bertrand
>
> I think you are making the same point as me... just proposing
> a different solution. I still feel that if we are using a system that
> is based on the philisopy of "write once, publish anywhere" we
> should be able to create documents in one place and have them
> published in more than one place in more than one style.
Why not - the problem IMHO is the content, and how easy/hard it is to
access it.
>. . .
> PS we need to avoid creating more jargon - I always think of NCC
> as part of the Starship Enterprise 's call sign (there, that gives *my*
> age away!)
Yes, agreed. If I got it right your ultimate aim is to improve the
tutorial part of the Cocoon docs, so there's no need for a new acronym.
-Bertrand
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.
"The CSIR exercises no editorial control over E-mail messages and/or
attachments thereto/links referred to therein originating in the
organisation and the views in this message/attachments thereto are
therefore not necessarily those of the CSIR and/or its employees.
The sender of this e-mail is, moreover, in terms of the CSIR's Conditions
of Service, subject to compliance with the CSIR's internal E-mail and
Internet Policy."
