-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I saw the update to the wiki re: TLP and the 'working on a new logo' - have to say "cool!" to that one. I had actually talked to someone about gen'ing a few so we could look at an update [TLP + maturity of the project... little face lift :-)]
In thinking about maven[2], TLP, the current Tapestry site and the stated objective of breaking Tapestry up into 'sub-projects' - what do you think about having a tapestry-site component/project? I was over in maven-land looking at their site and from what I saw (and I was there long enough to submit a patch to part of the site before we went down the 'documentation' road :-)) I liked the idea of a "more high-level" site with each 'component' generating its own site under the project. To illustrate: site/ News <-- This would require tapestry-site to be updated Releases <-- Nothing under this heading would -------- Current 4.0 3.0 Then when 4.X has another release, all that documentation is generated from the 4.X release and updated under that one link on the main site - no changes need to be made at the project site level. (currently 3.0.3 is hardcoded into the overall tapestry site so a new 3.X release mandates a change to both the 3.X documentation as well as the tapestry site itself. Just a thought... Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEPmX7aCoPKRow/gARAgssAJ9Il5VB1nerH+gO++pDoI2flFUYZQCfZncJ +2plofcp1v1I4OhpxnYVPos= =TaAw -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
