Hi Ivan,
#main a { ... }
#main p { ... }
#main h1 { ... }
and so on, so that it does not interfere with other custom stylings if
we just did
a { ... }
p { ... }
h1 { ... }
Actually I prefer to do it the other way around... just style the a's,
the p's without any exception, and /only/ change it when needed. Not
requiring such specific css makes it easier for e.g. Alexandro to simply
link to the stylesheet without having to worry too much about the html
below it. Simple example:
You wanted to have the 'wiki' style headings. If we would define them as
#main h1, then Alexandro has to make sure that the wiki also has a block
element surrounding all h1's with an id set to main. It's much easier
not to require this.
What is your argument for the specific styling? You can always override
them later...
Not sure btw. where I once read it... but I read somewhere that, and I
like that myself, that it is a good idea to style standard html elements
first, then classes, then ID's... maybe you can separate the classes and
ID's in items that position stuff (e.g. header, footer) and other
elements like special header styles...
and so on. For all the other pages, maybe we could get rid of the
content div altogether and apply the same margins/padding to the main
table since the main table's doing the same job as the content div.
We could do that... but on the other hand... the wiki doesn't require a
table, so we might end up in a situation that the styling again requires
a table... (not sure whether this is a serious concern, but still ...
g.,
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
