+1 for me to.
A few notes might be:
* The Download links could point to anchors on the Acquiring page, to
provide a single gateway.
* In the end, I expect we would have a single Subprojects or Projects
section, instead of two. For subproject labels, I would suggest
dropping "Struts" as understood:
+ Applications
+ BSF Scripting
+ Core
+ EL
+ Flow
+ JavaServer Faces
+ JSF Integration
+ Plugins
+ Sandbox
+ Shale Framework
+ Taglibs
+ Tiles
* At some point, we should move all the documentation under the
subprojects. Taglibs would get the Developer Guides, and most of the
rest would go under Core, the notable exception being the SSL Howto.
As Craig mentioned, ultimately each subproject should build and
maintain its own website.
* As Martin indicated, we should start to revamp the site generally
so that there is a clear separation between Struts the project and the
products of the project. The current Acquiring and Learning pages
could go under Core and replaced with generic versions that included
the other subprojects.
But, if we can at least do the first two things, and sorted out the
TLD business (as Joe mentioned, it's time we moved away from our
homegrown approach), I think we should be able to go with this for
Struts 1.3.0.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
