You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2007/04/03 04:39:08 UTC
[Vote] Move plugin site.xml up to Maven or Shared
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven pom. This is preferred so that
all submodules of maven can get the standard skin and override it if
they choose.
2. Copy the site.xml over to the shared pom. This is less intrusive
but doesn't cover all submodules that come along.
Vote:
[ X ] Move to Maven Pom
[ ] Copy to shared
Vote is open for 72 hrs.
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Dennis Lundberg <de...@apache.org>.
Brian E. Fox wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so that
> all submodules of maven can get the standard skin and override it if
> they choose.
+1
But I think that we might need to loose a couple of things from it
first. The body part contains links that are not used in the main maven
site, only on other parts of the maven site. The same goes for the
reports menu. I'm not sure about the head section either.
> 2. Copy the site.xml over to the shared pom. This is less intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Maria Odea Ching <oc...@exist.com>.
+1 Move to Maven pom
Brian E. Fox wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so that
> all submodules of maven can get the standard skin and override it if
> they choose.
>
> 2. Copy the site.xml over to the shared pom. This is less intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
>
>
> !DSPAM:602,4611be65165153095511399!
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Patrick Schneider <ps...@gmail.com>.
+1 Move to Maven Pom
On 4/3/07, John Tolentino <jo...@gmail.com> wrote:
>
> +1 [ X ] Move to Maven Pom
>
> On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Currently only plugins get a nice looking skin that matches the main
> > maven.apache.org page because the site.xml exists in the plugin project.
> > Other things like shared get a homely looking default skin. I see two
> > options here:
> >
> >
> >
> > 1. Move the site.xml up to the maven pom. This is preferred so that
> > all submodules of maven can get the standard skin and override it if
> > they choose.
> >
> > 2. Copy the site.xml over to the shared pom. This is less intrusive
> > but doesn't cover all submodules that come along.
> >
> >
> >
> > Vote:
> >
> > [ X ] Move to Maven Pom
> >
> > [ ] Copy to shared
> >
> >
> >
> > Vote is open for 72 hrs.
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by John Tolentino <jo...@gmail.com>.
+1 [ X ] Move to Maven Pom
On 4/3/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so that
> all submodules of maven can get the standard skin and override it if
> they choose.
>
> 2. Copy the site.xml over to the shared pom. This is less intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Andrew Williams <an...@handyande.co.uk>.
apart from the css glitch it seems good.
Andy
On 8 Apr 2007, at 04:12, Brian E. Fox wrote:
> 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:brett@apache.org]
> 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:brett@apache.org]
>> 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: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Brett Porter <br...@apache.org>.
On 08/04/2007, at 1:12 PM, Brian E. Fox wrote:
> 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.
The Maven site overrides this in a custom site.css.
>
> 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.
I don't think those belong there. I'd go with the bottom left of the
page instead (though I don't think the version is appropriate to the
main maven site).
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Vote] Move plugin site.xml up to Maven or Shared
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:brett@apache.org]
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:brett@apache.org]
> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Brett Porter <br...@apache.org>.
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:brett@apache.org]
> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Vote] Move plugin site.xml up to Maven or Shared
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:brett@apache.org]
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Brett Porter <br...@apache.org>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Vote] Move plugin site.xml up to Maven or Shared
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Brett Porter <br...@apache.org>.
On 06/04/2007, at 7:28 AM, Brian E. Fox wrote:
> Binding: +6(Brian, John, Dennis, Brett, Jason, Emmanuel)
> Non-Binding: + 3(Andy,John T, Maria)
John T is a PMC member - is there an out of date reference somewhere
that doesn't list him?
>
> 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?
- Brett
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Monday, April 02, 2007 10:39 PM
> To: Maven Developers List
> Subject: [Vote] Move plugin site.xml up to Maven or Shared
>
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin
> project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so
> that
> all submodules of maven can get the standard skin and override it if
> they choose.
>
> 2. Copy the site.xml over to the shared pom. This is less
> intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [Vote] Move plugin site.xml up to Maven or Shared
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Binding: +6(Brian, John, Dennis, Brett, Jason, Emmanuel)
Non-Binding: + 3(Andy,John T, Maria)
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).
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Monday, April 02, 2007 10:39 PM
To: Maven Developers List
Subject: [Vote] Move plugin site.xml up to Maven or Shared
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven pom. This is preferred so that
all submodules of maven can get the standard skin and override it if
they choose.
2. Copy the site.xml over to the shared pom. This is less intrusive
but doesn't cover all submodules that come along.
Vote:
[ X ] Move to Maven Pom
[ ] Copy to shared
Vote is open for 72 hrs.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Emmanuel Venisse <em...@venisse.net>.
Brian E. Fox a écrit :
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so that
> all submodules of maven can get the standard skin and override it if
> they choose.
+1
Emmanuel
>
> 2. Copy the site.xml over to the shared pom. This is less intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Brett Porter <br...@apache.org>.
I'm in favour of 'moving' it up. I think you'll still need this
site.xml though it'll be mostly empty (maybe add breadcrumbs?). The
TODO's already in there tell that story.
We'll also need to do a maven pom release after that change.
- Brett
On 03/04/2007, at 12:45 PM, Jason van Zyl wrote:
>
> On 2 Apr 07, at 10:39 PM 2 Apr 07, Brian E. Fox wrote:
>
>> Currently only plugins get a nice looking skin that matches the main
>> maven.apache.org page because the site.xml exists in the plugin
>> project.
>> Other things like shared get a homely looking default skin. I see two
>> options here:
>>
>>
>>
>> 1. Move the site.xml up to the maven pom. This is preferred
>> so that
>> all submodules of maven can get the standard skin and override it if
>> they choose.
>>
>
> +1
>
>> 2. Copy the site.xml over to the shared pom. This is less
>> intrusive
>> but doesn't cover all submodules that come along.
>>
>>
>>
>> Vote:
>>
>> [ X ] Move to Maven Pom
>>
>> [ ] Copy to shared
>>
>>
>>
>> Vote is open for 72 hrs.
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Jason van Zyl <ja...@maven.org>.
On 2 Apr 07, at 10:39 PM 2 Apr 07, Brian E. Fox wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin
> project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so
> that
> all submodules of maven can get the standard skin and override it if
> they choose.
>
+1
> 2. Copy the site.xml over to the shared pom. This is less
> intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by John Casey <ca...@gmail.com>.
+1 for moving to the Maven POM
-john
On 4/4/07, Andrew Williams <an...@handyande.co.uk> wrote:
>
> [X] Move to Maven Pom, with the note that extra site.xmls might be
> nice for breadcrumbs and extra links etc.
>
> Andy
>
> On 3 Apr 2007, at 03:39, Brian E. Fox wrote:
>
> > Currently only plugins get a nice looking skin that matches the main
> > maven.apache.org page because the site.xml exists in the plugin
> > project.
> > Other things like shared get a homely looking default skin. I see two
> > options here:
> >
> >
> >
> > 1. Move the site.xml up to the maven pom. This is preferred so
> > that
> > all submodules of maven can get the standard skin and override it if
> > they choose.
> >
> > 2. Copy the site.xml over to the shared pom. This is less
> > intrusive
> > but doesn't cover all submodules that come along.
> >
> >
> >
> > Vote:
> >
> > [ X ] Move to Maven Pom
> >
> > [ ] Copy to shared
> >
> >
> >
> > Vote is open for 72 hrs.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [Vote] Move plugin site.xml up to Maven or Shared
Posted by Andrew Williams <an...@handyande.co.uk>.
[X] Move to Maven Pom, with the note that extra site.xmls might be
nice for breadcrumbs and extra links etc.
Andy
On 3 Apr 2007, at 03:39, Brian E. Fox wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin
> project.
> Other things like shared get a homely looking default skin. I see two
> options here:
>
>
>
> 1. Move the site.xml up to the maven pom. This is preferred so
> that
> all submodules of maven can get the standard skin and override it if
> they choose.
>
> 2. Copy the site.xml over to the shared pom. This is less
> intrusive
> but doesn't cover all submodules that come along.
>
>
>
> Vote:
>
> [ X ] Move to Maven Pom
>
> [ ] Copy to shared
>
>
>
> Vote is open for 72 hrs.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org