As part of MOJO-1786, I've changed to the maven-fluido-skin in mojo-parent and deployed a new snapshot. Also, I've published an example mojo's site to: http://mojo.codehaus.org/fluido-preview/jboss-packaging-maven-plugin/
I have absolutely no clue why the logos have been removed...:-) /Anders On Wed, Nov 30, 2011 at 18:41, Robert Scholte <rfscho...@codehaus.org> wrote: > I agree, it shouldn't look like a collection of homepages ;) > The only thing I can think of is replacing one of the banner images. > @Christopher, do you have concrete examples of you suggestion? > > -Robert >> Date: Wed, 30 Nov 2011 09:31:32 +0100 >> From: and...@hammar.net > >> To: dev@mojo.codehaus.org >> Subject: Re: [mojo-dev] Using the new maven-fluido-skin for mojos >> >> Regarding allowing each mojo to have their own skin, I'm not in favor >> of that. I think that all our mojos should have the same documentation >> look 'n' feel. >> >> /Anders >> On Tue, Nov 29, 2011 at 22:26, Christopher Hunt <hu...@internode.on.net> >> wrote: >> > +1 to upgrade the MOJO to use this as a default set of skins. They look >> > great. >> > >> > In addition I feel that it would be nice to let plugin authors skin >> > their pages in different ways; perhaps via a vote. >> > >> > On 29/11/2011, at 7:48 PM, Anders Hammar wrote: >> > >> >> 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 >> >> >> >> >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe from this list, please visit: >> > >> > http://xircles.codehaus.org/manage_email >> > >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
