(snip)
We can bring the existing docs with svn:externals so the urls will
remain untouched. Old docs will still be available, but with the old
view. In time, we can move them to the new look or phase them out and
replace them with a link to the full archive.
I don't think this is a good plan.
We need a new maven skin that resemble the new look *before* we can
mix the environments. I don't like having some pages with a skin and
some other pages with another skin: we already have this "difference"
between website and wiki and we want to fix this, not to make the
issue bigger.
I explained this also in IRC, but I didn't understand the feeling of
the other people from that meeting, so I can't tell you if this will
be a blocker or not.
My concerns:
- Have uniform skin between cms and mvn generated pages.
- Have on all pages the left menu which has 3 parts: the suproject
links, the reports links and the top james links (about, download, asf).
- Have on all pages the same top menu with the list of projects.
James projects and its subprojects are really difficult for a newbie (we
ship end product, libraries,...), so we need to be as crystal-clear as
we can with our publications.
Thx, Eric
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
