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é.
signature.asc
Description: This is a digitally signed message part
