Hi all, The How-To page seems dedicated to collabnet more than actual styling. I was thinking of making a page called Style Guide (which would reside at http://wiki.services.openoffice.org/wiki/Website/Style_Guide) and then having 3 main sections in that page - Header, Body and Footer, which would go through much of the CSS and provide well commented documentation of most of the classes/ids, with a few diagrams to show the nesting of divs, etc.
André, since we're changing stylesheets (getting rid of portions of tigris/inst and removing all !important declarations), this should make the new why.openoffice.org design more viable, no? Is there anything in particular that needs to be taken into consideration to make that work? Regards, Ivan. On Mon, Mar 10, 2008 at 10:32 PM, André Wyrwa <[EMAIL PROTECTED]> wrote: > Hi, > > > On Tue, 2008-03-04 at 13:49 +0100, :murb: [maarten brouwers] wrote: > > Hi John, > > > > > Excellent idea. The wiki is the right place for this, so people can add > > > information as they discover it. There's the beginnings of a 'website > > > how-to' here: http://wiki.services.openoffice.org/wiki/Website/how-to > > > > I second that it is an excellent idea. I'm not so sure, however, whether > > the tone is right though of the current how-to. It reads a bit negative > > (boo collabnet/CMS), while it has serious advantages as well. Comments > > about breaking nicely formatted pages miss the point of a CMS (I read here > > nicely formatted as in nice colours chosen, custom styling etc.). I would > > rather discourage people to do custom formatting on a page. If you play > > nicely along with the rules of the CMS, it is easy creating pages. We > > should promote standards based pages, using semantic html, and prepare and > > explain some custom constructs like e.g. the campaign construct that is > > used in the test website, see e.g. the new main page or > > http://test.openoffice.org/help/ > > awesome comment on an awesome posting. > > Whouhouuu...things get so sensible and constructive around OOo these > days. ;-) > > > > ps. Ivan, I think we should make it a class, so that in principle more > > campaign boxes can be used on a page... (not that this is necessarily a > > good thing... but...) > > I think it is generally a good policy to reserve ideas for elements > which are 100% unique...whatever may come. Moreover, it is sensible to > use classes for everything styling and keep ids out of that, since that > creates a layer of flexibility between styling and javascipted accessing > of elements through their id. > > André. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
