I tried the topbar menu, as looking at http://svn.apache.org/viewvc/maven/skins/tags/maven-fluido-skin-1.0/src/main/resources/META-INF/maven/site.vm?view=markup it seems, that external links are only rendered when using this one. The position change of version and release date were accidentally as I did overwrite the tags without specifying the position. I like to have the time as well, so I see *when* I deployed the site :-).
Personally I think the topbar is confusing and support sticking with the sidebar menu, however that external links are missing is a pity. I now just copy the dav.codehaus.org/images folder to dav.codehaus.org/fluido-preview/images, so your preview should include images :-). I render the ckjm-maven-plugin with and without topbar and sidebar beneath http://mojo.codehaus.org/fluido-preview/ so everyone might take a look :-) Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Wed, Nov 30, 2011 at 21:57, Anders Hammar <[email protected]> wrote: > Regarding the topbar menu and the sidebar menu, I think we should > stick with the old layout of a left sidebar menu and no topbar menu. > We could include the Google Search feature by default. > What do others think? > > Also, what do people think about the current logos in the fluido skin? > I think that the Codehaus logo is fine and the Mojo one is ok, but > could possibly be improved (maybe just switch color). WDYT? > > /Anders > > On Wed, Nov 30, 2011 at 21:47, Anders Hammar <[email protected]> wrote: >> Right, I should have known that. I've been bit by that before. >> >> You've done some additional fluido skin config for the ckjm site, >> right? Added top bar menu and Google search? Also changed where >> publish date and version is displayed. >> >> /Anders >> >> On Wed, Nov 30, 2011 at 21:27, Mirko Friedenhagen >> <[email protected]> wrote: >>> Hello Anders, >>> >>> as all other sites (even for SNAPSHOTs of sandbox plugins) reside >>> directly beneath mojo.codehaus.org and the site plugin replaces >>> http://mojo.codehaus.org in links, you get: >>> >>> <img src="../images/mojo_logo.png" alt="Mojo"> >>> >>> which should probably be ../../images/mojo_logo.png or /images/mojo_logo.png >>> >>> I just site-deployed the site for the sandboxed ckjm-maven-plugin, see: >>> http://mojo.codehaus.org/ckjm-maven-plugin/index.html >>> >>> One thing which seems not to work correctly are external links: I >>> wanted to link to Spirellis' CKJM homepage (see >>> https://fisheye.codehaus.org/browse/~raw,r=15434/mojo/trunk/sandbox/ckjm-maven-plugin/src/site/site.xml) >>> but the link is not rendered at all. >>> >>> I am all for replacing the antique standard skin with the fluido one :-) >>> >>> Regards Mirko >>> -- >>> http://illegalstateexception.blogspot.com/ >>> https://github.com/mfriedenhagen/ >>> https://bitbucket.org/mfriedenhagen/ >>> >>> >>> >>> On Wed, Nov 30, 2011 at 20:58, Anders Hammar <[email protected]> wrote: >>>> 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 <[email protected]> >>>> 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: [email protected] >>>>> >>>>>> To: [email protected] >>>>>> 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 <[email protected]> >>>>>> 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 >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> 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
