Hi Kay, > How is this going to help with propagating/testing the new > headers/footers to the current site????
I've been silent about this... but that is because I first would like to do the preparatory work... among which the removal of the !important statements. If we can do the switching as proposed by Christian we could even disregard tigris.css and inst.css when building our mini site on test.openoffice.org . We could disregard the old nav and footer... So I'm kind of waiting for this before I will jump with full enthusiasm in crafting the header and footer code in .vm files. > yes, Christian did propose this but, again, it doesn't really help with > testing how things will "act" with backloading if you will. It does. We can upload any page to test.openoffice.org and see how it behaves in the new style. (I guess this is what you are referring to?). If we have tested how the code behaves, there is no technical reason why it should not behave as it did at test.openoffice.org at *.openoffice.org > Someone would need to take a look at the parse scrips, but I think at > the very least we need to take Ivan's styles (the *names of them*, for > example), and make them equivalent to what is used by Collabnet, or > something, or disable a LOT of styles currently used for the whole site, > like #banner and #toptabs, which I did to make things work, as far as > they have in tryouts. But we do need new HTML code in the header (especially because of the upper right tabs that allow you not only to search, but also to login and to change language). And inserting new HTML code, that even requires some Collabnet scripting, in the header is the tricky part for which we need some safe place to test... otherwise we might (maybe only temporarily) break the main page. Although we could use hiding of the old elements for the entire website, this is even sloppier than the !important statements imho. I've no problems with e.g. the es.openoffice.org page which uses this technique, but we are now talking about the main site. Next we will be rewriting the entire body using innerHTML on the <body> element... So we will have to do things with the .vm files that are included in every page. But that does involve careful planning. Christian's suggestion helps a lot since we can do the editing in a safe environment. g., Maarten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
