hepabolu wrote:
Guys,
I don't know if a vote for this is required, but I'd like to have
consensus/feedback, before I do something drastic.
As written earlier today there are gaps in the current version of the
website, e.g. FAQs are missing. What I'd like to do is restore the
current
Ross Gardler wrote:
I'll test the Forrest plugin on the Daisy docs today.
I'm not sure why my first version never made it to the list, so here it
goes again:
I want the first new version of the website to be as it was when the
reported missing docs were there, i.e. the old navigation
hepabolu wrote:
Ross Gardler wrote:
I'll test the Forrest plugin on the Daisy docs today.
I'm not sure why my first version never made it to the list, so here it
goes again:
I want the first new version of the website to be as it was when the
reported missing docs were there, i.e. the
Ross Gardler wrote:
So, if you can run the Daisy-to-Forrest export, can you use the old
navigation structure documents or should I be rewriting these in Daisy?
Yes, just tell me which version of the navigation document you want me
to use. In fact this goes for any focuments, by default it
hepabolu wrote:
Ross Gardler wrote:
So, if you can run the Daisy-to-Forrest export, can you use the old
navigation structure documents or should I be rewriting these in Daisy?
Yes, just tell me which version of the navigation document you want me
to use. In fact this goes for any
Ross Gardler wrote:
Ah, I see I misunderstood your question. The Forrest plugin can use the
old site.xml files or new ones defined in Daisy or even a mix of the two
(i.e. new ones imported into the old ones).
More on this when I have an iniital demo working. In the first instance
I'll use
Guys,
I don't know if a vote for this is required, but I'd like to have
consensus/feedback, before I do something drastic.
As written earlier today there are gaps in the current version of the
website, e.g. FAQs are missing. What I'd like to do is restore the
current content of the website
hepabolu wrote:
Guys,
I don't know if a vote for this is required, but I'd like to have
consensus/feedback, before I do something drastic.
As written earlier today there are gaps in the current version of the
website, e.g. FAQs are missing. What I'd like to do is restore the
current
hepabolu wrote:
Guys,
I don't know if a vote for this is required, but I'd like to have
consensus/feedback, before I do something drastic.
As written earlier today there are gaps in the current version of the
website, e.g. FAQs are missing. What I'd like to do is restore the
current
hepabolu wrote:
Guys,
I don't know if a vote for this is required, but I'd like to have
consensus/feedback, before I do something drastic.
As written earlier today there are gaps in the current version of the
website, e.g. FAQs are missing. What I'd like to do is restore the
current
Il giorno 11/ago/05, alle 17:15, hepabolu ha scritto:
Now that I've got my commit rights working I will try to focus on the
documentation. However, I've already found out that updating the
website is not a simple thing to do, so it might get down to me
patching the content and bugging others to
Helma,
However, I've already found out that updating the
website is not a simple thing to do, so it might get down to me
patching the content and bugging others to do the actual update, in
which case it means that you need to be patient some more.
I am a committer in the Lenya project and I
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
All,
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
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.
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
Dear all,
is there a process for updating the Cocoon website?
The above mentioned bug for example is sitting there since January. I
think someone (a committer) should actually either decide that website
updates does not make sense / neeeds more work / whatever or apply the
patch.
AFAIK there is
Torsten Schlabach wrote:
Dear all,
is there a process for updating the Cocoon website?
The above mentioned bug for example is sitting there since January. I
think someone (a committer) should actually either decide that website
updates does not make sense / neeeds more work / whatever or apply
Sylvain Wallez wrote:
[EMAIL PROTECTED] wrote:
On Mon, 28 Mar 2005, Carsten Ziegeler wrote:
Antonio Gallardo wrote:
Hi:
We released 2.1.7 - congrats! :-)
But, our site is outdated.
Yes, I will not have time to update the site in the next week - can
someone else please update? And take care
Antonio Gallardo wrote:
Hi:
We released 2.1.7 - congrats! :-)
But, our site is outdated.
Yes, I will not have time to update the site in the next week - can
someone else please update? And take care that @version@ and @date@ are
properly replaced as Joerg reported?
Thanks
Carsten
--
On Mon, 28 Mar 2005, Carsten Ziegeler wrote:
Antonio Gallardo wrote:
Hi:
We released 2.1.7 - congrats! :-)
But, our site is outdated.
Yes, I will not have time to update the site in the next week - can
someone else please update? And take care that @version@ and @date@ are
[EMAIL PROTECTED] wrote:
On Mon, 28 Mar 2005, Carsten Ziegeler wrote:
Antonio Gallardo wrote:
Hi:
We released 2.1.7 - congrats! :-)
But, our site is outdated.
Yes, I will not have time to update the site in the next week - can
someone else please update? And take care that @version@
Antonio Gallardo wrote:
Hi:
How often the cocoon website is updated? Is the site automatically updated?
I ask because I saw there are 2 cvs.
cocoon-2.1 and cocoon-site.
Please explain.
Best Regards,
Antonio Gallardo.
cocoon-2.1 contains the XDocs files for the 2.1 part, cocoon-site the
XDocs
Hi:
How often the cocoon website is updated? Is the site automatically updated?
I ask because I saw there are 2 cvs.
cocoon-2.1 and cocoon-site.
Please explain.
Best Regards,
Antonio Gallardo.
Le Mercredi, 24 sep 2003, à 07:34 Europe/Zurich, Antonio Gallardo a
écrit :
How often the cocoon website is updated? Is the site automatically
updated?
I ask because I saw there are 2 cvs.
IIUC (but I've never done it) updates are manual, see
25 matches
Mail list logo
