> On Wed, 2002-03-27 at 17:13, Leo Simons wrote: > > It has been brought up by many people that there > > is no common way of organising subproject websites. > > I propose we draft a set of guidelines (_not_ > > rules) on a general structure. > > http://jakarta.apache.org/turbine/maven/ > > There's a sample structure there, with lots of documentation and the > printable pages issue is dealt with.
I'm aware of that. Not going into the html / css it uses, I think it does not address the issues mentioned in my last post (it addresses some others _really_ well though). If a decision is made that maven will be the basis for jakarta-site3, I'm more than happy to instead direct this discussion toward maven and focus my 'creative energy' there, ie sending patches to address those issues. Since different people will have different things to say about what will be site3 (a discussion which hasn't happened just yet), I was keeping this discussion tool-independent. ie Maven: "Maven's primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time." me: "My primary goal atm is to improve the experience of both developers and users that visit the avalon site. As parts of the problem with that site are inherited from problems with the main site, I will try to address those problems first." cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
