Hi Ioan,
Also keep in mind the information on trademarks and branding on
http://www.apache.org/foundation/marks/pmcs.html, especially the
'website navigation links' section.
We also need links (per subproject) to the maven generated reports
(javadoc,...) which need the same look&feel and (top/side) menus
(example:
http://james.apache.org/jsieve/main/dependency-convergence.html). The
list of reports can change from a subproject to another one.
Thx, Eric
On 05/11/2012 10:35 AM, Ioan Eugen Stan wrote:
Hi,
2012/5/11 Eric Charles<[email protected]>:
(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.
We currently don't have any of these. The layout changes when you move
from project to project because each project has it's own site that it
inherits. There is no common parent for all projects.
The top menu is also different from project to project: different
ordering and different sizes in CSS and even missing elements. For
example http://james.apache.org/jspf/index.html is missing home,
mailbox, project. Just click on all top menu entries and you will see
for yourself.
A solution for this is to move the mvn site templates to svn:externals
(to skin project maybe) and import them in every project. This way we
might solve the uniformity issue.
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.
Indeed, very confusing and my opinion is that having the sidebar
change that much with every project is creating even more confusion.
We should strive for uniform pages but I don't know what support
maven site has for template inheritance, so it might not be possible.
I will look into it.
@Stefano: We might not loose browser editing. I'm not sure but I think
the bookmarklet will resolve the source that generated the page even
if it's not markdown formatted, by looking at which reg-exp from
path.pm it matches.
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]
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
