On 3/11/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> I propose we remove the css dependency as follows:
>
> 1) Add the following one line project.css to each project:
> @import url("http://jakarta.apache.org/style/jakarta.css";);Why not use relative urls? Using absolutes will make it harder to test changes to the css. >From jakarta.apache.org: <link rel="stylesheet" href="/style/style.css" type="text/css"/> > 2) Upload jakarta.css to this location (I've created a suitable one) > which contains our colours and designs (eg. blue headers) Where is jakarta.css going to go in SVN? > Each page in commons will then use the maven-base and maven-theme css > files as per default maven. The jakarta.css file then overrides these as > needed. Thus most users will see no change. Are maven-base and theme css's in svn too? > If the user is running a copy of the website on their own box and they > are offline, then the standard maven colours and design will be used > (eg. grey and red headers). Relative url :) > If we want to update all commons websites, we just update jakarta.css. > > I propose we remove the menus.dtd dependency by just removing it. Users > will just have to click a couple more links to move between components. > IMHO, the simplicity of the resulting design overrides the loss of > functionality. +1. Simplified site, simplified build. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
