Perfect, I will be working towards something like that.
Patrick Paul
Jeremias Maerki wrote:
Sorry, I got the wrong impression. Since it's a CMS I thought you
suggested we use that. But you're right. The tab structure like Lenya
has it is exactly what we need. I think we'll end up with the following
tabs:
- Home
- 0.20.5
- 1.0dev
- Development
(It's probably best to collapse "Development" and "Design" into one tab.
Too many tabs are not ideal. If anyone has better ideas, please bring'em
up.
On 27.08.2005 15:57:02 Patrick Paul wrote:
I was talking about their website (with the two tabs for the different
versions) , not their product.
Patrick
Jeremias Maerki wrote:
Uh, oh. Sorry, but I don't think we'll do that. We don't even have the
infrastructure for a Lenya installation and I wouldn't want to rewrite
our whole website just now. That would distract me too much at this
stage of development. Even the Lenya project uses Forrest for their
website. :-)
On 27.08.2005 04:31:55 Patrick Paul wrote:
Ok, so from what I understand you want to do, I think that what the
Lenya project did looks good.
http://lenya.apache.org/
What do you think ?
Patrick Paul
Jeremias Maerki wrote:
While we're at it: In preparation for the first release we need to start
thinking about a refactoring of our website. Since FOP 0.20.5 will
probably stay the preferred productive version for some time and FOP
Trunk is substantially different, I'd like to propose doing a version
split like Forrest [1] have done. That would involve factoring out the
version-dependent docs into a separate tab (or something like that), so
we can have info for both versions side-by-side for the time being. I
think stuff like embedding info would become too complicated and
unreadable if we tried to put everything in the same place.
If anyone would like to take the lead here, I'd be grateful. Otherwise,
I will squeeze it in somewhere.
[1] http://forrest.apache.org
Jeremias Maerki
Jeremias Maerki
Jeremias Maerki
