On a related note, would it be possible to push up the site every night using Gump?

Christopher Lenz wrote:
+1

Vincent Massol wrote:

Hi,

It seems to me that our choice of putting the released docs on the
cactus main page and the dev doc in a different directory may not be
optimal.
The problem is that new resources, new news, typo fixes, link fixes, etc
are constantly added to the web site and they only appear in the dev web
site. Thus users are bound not to see these changes, making the site
very static.

Also, I don't believe having a "common" web site between release/dev
versions is solving anything because the changes mentioned above can
affect any page.

I think we have a good solution with our "Doc for: 1.5dev | 1.4.1"
mechanism. However, I propose to switch the locations such that the
default web pages points to the dev version and the user has to click on
the "1.4.1" link to get the release one. The rationale is:
- more "dynamic" web site (more stuff added or corrected are seen by the
user)
- users are aware of new stuff upcoming
- implicitely we promote the use of our the latest and greatest versions
of Cactus (i.e. the dev release)
- this is what is done for most if not all of the other jakarta web
sites

What do you think?

Here's my +1 to this.

Thanks
-Vincent
--
Christopher Lenz
/=/ cmlenz at gmx.de


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to