I moved the site stuff up to the main maven pom. I staged the maven main site here: http://people.apache.org/~brianf/maven/
I think this is pretty good. I also staged a shared component to see how it looks by inheriting the info here: http://people.apache.org/~brianf/enforcer/ The problem is that the shared component page now is setting class="externalLink" for most of the links in the header. This class has extra right padding and messes it up. I'm not familiar enough yet with the site and related tech to know how to fix this. It seems like changing the skin isn't what we want, somehow we need to tell site not to make these externalLinks. Also, the plugin and shared sites should have the version and published date as they currently do. However when you add the breadcrumbs, you can't seem to force them to be on the far left. I think the version and published date should be to the right of the breadcrumbs to make everything consistent. Pointers? -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Saturday, April 07, 2007 10:04 PM To: Maven Developers List Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared Makes sense. Another option is to have those links in the bottom of the left nav on every site too. I'm not against either of those solutions, as long as the links section isn't too bloated. I can certainly see the merits in consistency of the header section. - Brett On 08/04/2007, at 11:56 AM, Brian E. Fox wrote: > I agree they may be irrelevant for most plugins. However, the more > consistent the header, the more tied together everything feels. I > actually am always jumping around from section to section (almost > always > a maven.apache.org page open in a tab already) and it's nice to have > those links right there all the time. > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 07, 2007 9:47 PM > To: Maven Developers List > Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared > > I definitely agree with the breadcrumbs on the left. I don't mind > where the publish date goes as long as it's consistent (maybe bottom > is more suitable/traditional). > > For the links, I find them to be too noisy with all the subprojects. > On the main site these were put into the left nav. I think these > links are intended to be used for contextual links - how often are > you on a plugin site and decide to go to Continuum? So maybe the main > site contains those links (though I'd be happy to aggregate > frameworks under one link to a subpage), but the plugin sites just > link to the things relevant to that plugin (eg, the release site > links to the scm site, as does continuum, etc). The breadcrumbs > really look after the main navigation from there. > > WDYT? > > On 06/04/2007, at 11:03 PM, Brian E. Fox wrote: > >> >>> >>> I will make the changes and stage the main site before pushing it >>> out. >>> >>> What are we doing with the links that are present on plugins but >>> not on >>> the main site? It seems to me that they should be the same in both >>> locations (either with or without). >> >>> I think it makes sense for them to be the same. What's the delta? >> >> The plugins (not the plugins list page, but the plugins themselves) >> page >> has all the maven tech on the right (Maven 1.x |Maven 2.x | Maven 2.x >> Plugins | Continuum | SCM | Wagon | JXR | Doxia). It does not have >> the >> "cookies" or "track marks" in the top left. They have the Last >> Published >> on the left. >> Example: http://maven.apache.org/plugins/maven-resources-plugin/ >> >> The main maven pages do not list and of the maven tech stuff. The >> Published date is on the right instead. On the left are the track >> marks >> "Apache > Maven" >> Example: http://maven.apache.org/ >> >> >> It would make the most sense to me is to have track marks on all >> pages >> in the top left followed by the publish date. Then have the maven- >> tech >> on the top right. This presents a consistent navigation experience >> throughout the entire site. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
