Justin Erenkrantz wrote:
--On Wednesday, November 6, 2002 11:37 PM -0800 Scott Sanders <[EMAIL PROTECTED]> wrote:

On Wed, Nov 06, 2002 at 11:26:12PM -0800, Scott Sanders wrote:

Here it is:

http://cvs.apache.org/~sanders/

Also, I put up a version with the avalon-tigris skin by Peter.

It is at http://cvs.apache.org/~sanders/avalon/


The avalon-tigris skin is much nicer in text-only browsers, so +1 to that alternative.

Actually I prefer the Forrest version in Lynx.

_Here is the Avalon-Tigris version_

Apache Commons Project (p1 of 2)

   Apache Commons

   Home | Projects

   Info
   Index
   Resolution
   Who we are
   License
   Projects

Apache Commons Project

     * Welcome
     * Commons is...
     * Commons is NOT...
     * Mailing Lists


_This is the Forrest one_
Apache Commons Project Apache Commons Project (p1 of 3)


   Apache Commons site
   _______________ Search
   the Apache Commons site
   Home
   Projects


* Info + Index + Resolution + Who we are + License + Projects


Apache Commons Project

   [printer.gif]
   print-friendly
   version
     * Welcome
     * Commons is...
     * Commons is NOT...
     * Mailing Lists


The rest of the text is basically the same.

And, I would recommend that we commit both the forrest source and the generated html to CVS.

+1 for now.
Now Forrest does not delete the build dir as it did before, so we can just commit ./build/site/** dirs also


We *must* have the source version-controlled as I'm not going to be modifying forrest-marked-up text myself - that contradicts forrest's original purpose.

Why may I ask?

Anyway, we are working on both wiki-like editing and in-browser editing, so it won't be an issue in the near future :-)

IMHO, 'forrestbot' or any other automated rebuild solution isn't acceptable. People suggested remote cronjobs which are insecure (you'd have to leave your SSH key unencrypted if its automated!) and that should be avoided at all costs. So, I do think that the generated source must also reside in CVS as well so that we can have a staging area for commons.apache.org and not need to run forrest (aka java) on daedalus.

The process would be a bit different.

We would run Forrest cron job on another server, and publish it there.
Daedalus synchs his version from that other server (ie pull, not push).

Oh, BTW, please run the site through validator.w3.org before deploying. It doesn't look like the avalon-tigris skin is too far off from compliance though. -- justin

It still needs tweaking, this is a prototype ATM.

--
Nicola Ken Barozzi                   [EMAIL PROTECTED]
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------



Reply via email to