commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <>
Subject Re: [discuss] adopt a new skin for commons sites
Date Sun, 27 Nov 2011 11:40:30 GMT
While the l'n'f can be easily changed - it is just a matter of assign
styles - not all strict commons customizations are not included in the
skin, since it is a general skin with the purpose to serve not only

I don't see other solution ATM than forking the skin if we intend to
apply it, but after all the effort I already put on it, this is
something I don't want to be involved ATM, I want to come back
developing code and not doing the designer for a while.

Let's keep the old skin

On Sun, Nov 27, 2011 at 1:51 AM, sebb <> wrote:
> On 26 November 2011 21:07, Simone Tripodi <> wrote:
>> Hi all guys,
>> at Maven we have just released a new skin[1], I quickly did an
>> experiment and applied it on my beloved digester, deploying the site
>> on my personal [2] ASF space.
>> WDYT? Is there any chance to have it applied here at commons?
>> It would involve a little modification to the parent pom[3].
>> Any feedback would me much more than appreciated, many thanks in advance!
> The Commons Logo and link are not working.
> I had to add some special code to the Velocity template to get round
> bugs in Maven site generation.
> The logo and link use a dummy url suffix to ensure that they are not
> converted into relative URLs. You have to remove the following from
> the end of the URLs:
> .remove.invalid
> There's similar trickery for the image processing.
> As a temporary hack I suggest you manually fix the output so at least
> we can see what it *should* look like.
> Having said that, I find the page a bit harder to read, because the
> introduction takes up far too much space.
> Also, the RHS links are missing. We need to provide a links to
> ApacheCon and the ASF.
> And the trademark notices at the bottom are missing. These are also required.
> I spent a lot of time getting that working (again, because of
> deficiencies in Maven site generation).
>> Simo
>> [1]
>> [2]
>> [3]
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message