Re: [VOTE] changes to site

[Nicola Ken Barozzi <ni...@apache.org>]

From: "Leo Simons" <le...@apache.org>

> > > Please give your +1s, and Nicola and I will
> > > commit the changes and update the site.
> >
> > +1
>
> 5 of those will do. Nicola, how much of this are
> you willing to handle? Also, what course of action
> seems most sensible to you?
>
> (I tried to figure out what happens to build
> the POI site but got more and more lost...
> I couldn't even find the css files!)
> then I looked at the krysalis CVS and that is
> when I really started scratching my head....)
>
> If possible, I would like to upgrade the cocoon
> used for creating the docs to Centipede first
> without changing the dtds/xsl and stuff, and then
> change the xsl when that is done. Agreed?

Centipede now makes it possibe to use Forrest/Cocoon for the docs without
having to keep it in CVS.
And the DTDs can remain te ones you are using now if you wish.
Are there any special reasons why current xsl sheets are preferred?

Now that Centipede beta1 is out, I can help you use Centipede for the
build...

It's not that I want to push anyone into it, but IMHO it's the easiest
solution.

What do others think?

It's a bit hard for me to write documentation since I mainly wrote the
project, hence I don't really understand what I need to explain.
If you ask questions, I'll be more tha happy to write the answers directly
in the docs.

--
Nicola Ken Barozzi                   nicolaken@apache.org
            - verba volant, scripta manent -
   (discussions get forgotten, just code remains)
---------------------------------------------------------------------


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [VOTE] changes to site

[Leo Simons <le...@apache.org>]

> > If possible, I would like to upgrade the cocoon
> > used for creating the docs to Centipede first
> > without changing the dtds/xsl and stuff, and then
> > change the xsl when that is done. Agreed?
> 
> Centipede now makes it possibe to use Forrest/Cocoon for the docs without
> having to keep it in CVS.
> And the DTDs can remain te ones you are using now if you wish.
> Are there any special reasons why current xsl sheets are preferred?

the ones POI uses are a bit flawed, methinks.

(Jim Cobban sent me this some time ago:
>I have been trying to read the POI web pages, of which you are listed
>as the author.  I find them very difficult to read because they are
>formatted so that they spill off the browser window.  To read a simple
>paragraph I have to keep scrolling back and forth, which is very
>tiring.  Could you please reformat them so they adjust to the size of
>the browser window?  Even if I instruct my browser (Netscape 4.79) to
>reduce the font size the text is still too wide, plus some of the text
>shrinks so much that it becomes hard to read.)

and there are some more tidbits.

I have since figured out you have the xsl sheets jarred up somewhere
within Centipede...I think? Which is okay; I'd just want those fixed.

on the DTDs...well, its just too much of a pain to change all the docs
right away. The pain of writing python scripts :)

Also, Berin's Developing with Avalon is in docbook format; we need to
keep support for that.

> Now that Centipede beta1 is out, I can help you use Centipede for the
> build...
> 
> It's not that I want to push anyone into it, but IMHO it's the easiest
> solution.
> 
> What do others think?

let's start with getting the docs built using Centipede, then think
about moving the rest over as well. Our build system is currently
working rather well, so we shouldn't replace it with something that is
in a beta stage very lightly.

We could, of course, set up two build processes (build-centipede.xml or
somethin'), and then start calling more and more targets in the new
buildfile from the old ones. I'm all for it. I just want to see
something work first =)

- Leo




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>