On 27 November 2011 11:40, Simone Tripodi <[email protected]> wrote: > 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 > commons.
The changes I did for Commons are actually needed on other ASF projects. For example, they are also used on HttpComponents. The problem is that the Maven site generation is not flexible enough, particularly for multi-component projects. > I don't see other solution ATM than forking the skin if we intend to Does the skin involve more than just CSS changes? If not, then it would be easy enough to replace the Commons CSS with the updated version if people agree with the new look. Note: this is another restriction of Maven site generation - AFAIK it's not possible to change the template independently of the CSS. > 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 > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > > On Sun, Nov 27, 2011 at 1:51 AM, sebb <[email protected]> wrote: >> On 26 November 2011 21:07, Simone Tripodi <[email protected]> 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] http://maven.apache.org/skins/maven-fluido-skin/ >>> [2] http://people.apache.org/~simonetripodi/digester >>> [3] https://gist.github.com/1396291 >>> >>> http://people.apache.org/~simonetripodi/ >>> http://simonetripodi.livejournal.com/ >>> http://twitter.com/simonetripodi >>> http://www.99soft.org/ >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
