Hi, >> change style, still text > > Well - might be still text, but not very readable text. > >> current styling is broken > > Yes. > (...) > > It is not about removing text. It is about "defacing" the whole site. > > Sure it isn't as problematic as messing around with the structure > itself, but still one should be aware of that.
My stance is, we can't make it worse than it is already... > The other problem to be aware of is: Our changes will most likely be > binned when/if OOo should upgrade to a newer version of CEE... True... but maybe we can design the style as such that we can simply disregard/overwrite/revert to old styles when this would happen... And aside from that, Louis has ideas about migrating to another project management tool... > Don't get me wrong: I'm all in favor of cleaning it up. > But cleaning it up the last time was a very hard process, despite having > a staging server at hand. Admittedly we were changing the structural > layout of the site, but still there were problems where I didn't thought > there could be any (exactly because the css is so damn broken) If I remember correctly, it was hard because we decided to stick with inst.css, or was it tigris.css, as it came with collabnet... If you look at netbeans.org , you'll neither one of these style sheet files are linked from any of their pages anymore. Oh, how much I would love this approach for the openoffice.org site as well... but let's take small steps, by at least removing the !important statements. g., Maarten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
