The fluido skin is indeed an improvement compared to the current skin.Sure we 
have to check our logos / images. Also I'd prefer to have a way to mark site as 
deprecated for retired plugins by adding a warning bar, change colors / 
background. Does this mean we have to tweak/expand the skin especially for the 
mojo pages?Our mojo's have often a much slower release-cycle compared to 
Maven-plugins, so this might result in a scattered looking website. It would be 
great if we could apply this skin to all plugin-pages with ease to get a 
uniform looking site as much as possible.Sure, this might take a week or so of 
site-deployments, but I think it's worth it. -Robert > From: ol...@apache.org
> Date: Tue, 29 Nov 2011 09:53:08 +0100
> To: dev@mojo.codehaus.org
> Subject: Re: [mojo-dev] Using the new maven-fluido-skin for mojos
> 
> +1 from me.
> 
> BTW Not tested with our current logos.
> 
> Something to do IMHO. As for maven projects, old logos was not good so
> I have changed to use others (thanks @brett for the tip) with this
> skin see: http://people.apache.org/~olamy/maven/scm/
> 
> 
> 
> 2011/11/29 Anders Hammar <and...@hammar.net>:
> > An new skin, maven-fluido-skin [1], was recently released by the
> > Apache Maven project. For the JAXB mojo, a patch submitter requested
> > us to use that as he needs it for the documentation part.
> >
> > Should we use that for our mojos? Should we use a consistent skin for all 
> > mojos?
> >
> > Here's an example of using the new skin for a plugin:
> > http://mybatis.org/maven-migration-plugin/
> >
> > /Anders
> >
> > [1] http://maven.apache.org/skins/maven-fluido-skin/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> >    http://xircles.codehaus.org/manage_email
> >
> >
> 
> 
> 
> -- 
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
                                          

Reply via email to