I think we are talking about two sets of messages here:

1. the admin messages, like the "settings saved" or the "do not edit default templates"messages
2. the end user messages, like "your content has been added" in the CS, gallery etc.

For the first set this stylesheet might not be the right place, since we'll need them only with admin on. For the second set a webgui.css or whatever is certainly a good idea.

There are also some inline styles in the templates that could make their way into this stylesheet, e.g. admin styles in the shortcut template. And perhaps even non admin inline styles.

I also agree on you idea of the compressed, "min", version.

This is how I see it:

1. where the messages can be found
2. the different kinds of messages (error, info, warning, settings saved, etc.)
3. a design for each type of message
4. rules for the use of html and css for the messages

I'd suggest we start by making an inventory as we go along towards the nov 15th deadline. This does not have to be done by then, but lets post lists of these kind of messages in this thread. Or am I jumping to a decision too soon?

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