Hi Alexandro, On Tue, Nov 25, 2008 at 12:45 PM, Alexandro Colorado <[EMAIL PROTECTED]> wrote: > [...] > Well I don't mean CSS rounded corners, but image rounded corners like for > example the one used for the cover page info bubble (the one with the gull). > Have it globally accesible through a specific class can save a lot of time > for people designing specific projects. They just need to know the name of > the class and they will have their info bubbles.
This is already in place - e.g. to get the rounded gull box, all you need is a reference to /branding/css/style.css (which is automatically included in the CollabNet 'skeleton') and code like this: <div class="message"> <h2>Title</h2> <p>Some text...</p> </div> The problem is that people are not aware that it is there... > Another one could be butttons for example. The download button is found in /branding/css/home.css... but that's a different story. I see what you mean now, and it is a good point. I will include descriptions of how to do this in the style guide. This could make a good discussion on the NL list - perhaps other projects could share their CSS code with us for some of their interesting design elements? >> So I'm afraid this will be something to look at in the more distant >> future. The other problem is that the Wiki CSS is quite different to >> the OOo homepage, and we can't easily change class names because they >> are generated by MediaWiki. > > I am familiar with both CSS and I understand what you mean. But this is > something that we need to decide, also MediaWiki elements vary greatly from > the page. We could mimic Mediawiki way of doing things in the page? That way > we could have these elements also homogenized. > > One big difference for example is the way the menus are positioned, > Mediawiki give priority to the content while the OOo site gives priority to > the menu. I think Mediawiki is better way to go with this. The original > MonoBook CSS was created by Limi, one of the biggest CSS figures from the > Plone community. I think his CSS structure is superior to the Collabnet > one. You're right: the Wiki organizes its HTML so that the content comes first and the navigation comes second, and this is a much better way of organizing the HTML. I don't see why we couldn't do the same when we go tableless (my optimism is showing when I say 'when' instead of 'if' :) ). OO.org's HTML/CSS structure is more simple and straightforward than MediaWiki's, and that's a good thing IMO so I would be against homogenizing the two in terms of a single stylesheet... but if there's certain things that MediaWiki does better in its HTML/CSS than the OO.org website which we could use, why not use it? The way the MonoBook separates its navbar and content is one example of how the OO.org site can be improved. >> The tabs were just one example; on the >> website we can have those span tags inside, but on the wiki we cannot >> do this without editing core MediaWiki files. >> >>> I would also want to have infoboxes like the ones at yahoo.com portal >>> where >>> you have boxes with tabs that show different content. >> >> Some would argue that this would be information overload, which goes >> against the original motives for the new design. Even if we had these >> tabs, the content would have to be manually updated. What I would like >> to see is a RSS feed link on the homepage, and a link tag in the HTML >> to a RSS feed for OOo updates (e.g. important news, new version >> updates), etc. > > One problem is that the information is presented very plain. They see text > as a wikipage to be exact. For example the original education project (sorry > ericb) looks more like a wikipage than a real site. Compare > http://education.openoffice.org vs http://porting.openoffice.org/mac/ and > you will see what I mean. That's what one would expect from a Mac project :) > The key is that not every Project lead is a web designer and the key of > having a toolkit is for them not to have to become excellent designers. > Instead have a bunch of classes that they can have (if they wish for). It is up to every OOo project to decide how to present their information, but there's nothing stopping us from making different 'widgets' or CSS classes or JavaScripts available to everyone in order to enable them to have better project websites. Of course, what we need are people willing to make these available... something to start discussing on the NL mailing list maybe? Regards, Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
