Rogier,

We do have moderator powers, but it's not possible to merge threads in WebGUI unfortunately.  We can perform other functions like editing posts, making threads sticky, and locking threads. 

Great Rory. There has been some discussion about this already, let me fill you in.

If we use a css framework we will use it for page layouts, but probably also for some other assets that need some kind of layout to make sense like the collaboration or the wiki.

These requirements already came up in previous discussion about frameworks:

• validating html & css
  
• html should be semantic
• html should be clean (not too many divs)
  
• user friendly for designers (easy to edit, expand, override)
  

My idea was to make a shortlist of two or three frameworks. Then implement each one into three page layout templates (e.g. single page, side by side, one over three) to be able to compare them.

This sound good to you?

Rogier | United Knowledge
www.unitedknowledge.nl · www.webgui-help.nl

 I'm working on the frameworks and really think we're not gonna find anything that would match our exact criteria. The two most important reasons for this are the semantics issue and the user friendliness. With these two problems and keeping in mind that we want to use the frameworks only in page-layouts and specific assets, I'd like to suggest to create or "loan" some kind of reset.css which handles crossbrowser problems.

Wait, do you mean an actual reset css like yui reset?

For the layout I think it's best if we created our own set of classes to position the elements. What do you guys think?

I agree.

Having that said, I'm going to create 3 layouts with 2 different frameworks. The frameworks I've chosen are:

• YUI
• BlueTripCSS

If someone has burning ideas,suggestions,etc. to add another one or not try any of these frameworks, don't hesitate to let me know.

 

I checked out YUI css some time ago to see if it could be made to validate. It can, and I have a validating grids.css that we could base our own css on.

Also, this package contains page layouts loosely based on YUI. Maybe you want to use it, maybe not.

Good job so far, just one question: which others did you research and why did you choose these two?

Rogier | United Knowledge
www.unitedknowledge.nl · www.webgui-help.nl

I think that a reset.css would be very beneficial.  I have actually already started research on this for an article that I want to write for Design Squid (part of the staff blog).  The issue that I have been working on is that a standard reset.css will override user-entered styles that come in from the rich text editors.  But yes, I will be attempting to put together some sort of reset.css, and would be happy to post updates here as I work on the research to get everyone's input.

I don't think we should force users to use a reset.css file. Reset css usually has nothing to do with positioning; it could be a part of a theme, but not of the default templates.

Moreover, people usually have their own preferences; they use their own reset, or Eric Meyers or some other, or maybe they don't want to use one at all.

So as far as I'm concerned, it's a no for reset.css.

Having said that, your welcome to post your research here. I would be interested in reading it and giving some feedback.

Btw when will a reset.css override styles from the editor?

Rogier | United Knowledge
www.unitedknowledge.nl · www.webgui-help.nl