Some thoughts:
a.) Approach I was advocating was to use commons-site.jsl to control navigation creation and ordering so that includes did not need to be present in individual projects.
b.) approach I believe your working on uses dtd includes directly into navigation.xmls of subprojects.
c.) Currently we have a hybrid of these two approaches, 1.) Includes into each navigation.xml 2.) enforcement on ordering in commons-site.jsl
Is this what we want? Can it be made more transparent to the sub-projects by not using includes at that level?
[X] stable top level navigation.
[ ] agreed includes in all subproject sites (single include strategy).
[ ] backup of current toplevel site.
[ ] fresh rebuild and publish of mavenized top-level site (under jakarta.apache.org/commons).
[ ] fresh rebuild and publish of all sub-project sites.
-Mark
Stephen Colebourne wrote:
Looks good, although I thought that we now had a single include strategy for subprojects.
Stephen
----- Original Message ----- From: "Mark R. Diggory" <[EMAIL PROTECTED]>
Whats our current status on the the top level site? I think its obvious that we have at reached a LCD (least common denominator) on the navigation for the time being. So I'm going to break down things into a list of steps to get through for migration of the "commons" toplevel to the mavenized site.
[X] stable top level navigation. [ ] agreed includes in all subproject sites. [ ] backup of current toplevel site. [ ] fresh rebuild and publish of mavenized top-level site. [ ] fresh rebuild and publish of all sub-project sites.
I think its important to get the top-level site in place fist before verifying all the lower level sites are correctly rendered, this is because all links currently lead back to http://jakarta.apache.org/commons and it difficult to do things like link checking because the old site always ends up in the navigation
stream.
On that note, do we have any solid "linkchecking" tools available to verify the integrity of the site?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
