Sent by Arlen Walker on 23 July 2003 19:07
I see it as hugely dependent upon the project, so a fixed order isn't
always suitable.
In general terms, I proceed from general to specific. HTML tags first,
then IDs. All specific styles for the ID follow each individual ID.
Classes follow the HTML tags that they are used on.
For example:
body styles
p styles
classes used to modify p styles
section id styles
id p styles
classes used only to modify id p styles
As I explain it, I realize it seems complex, but it's been quite simple
for me to use. And it makes it easy for me to find the style I'm
looking for, without worrying about what happens when another style is
added before a given one. Since the file itself proceeds from general to
specific, later styles should not be overridden by earlier ones. It also
helps me stay aware of the rules of cascade.
Of course, the other thing I try to do is limit the number of styles. If
the stylesheet is getting too complicated for me to find my way around
easily, then the design is too complex, and it's time to simplicate. ;{>}
OTOH, there's a part of me that notes a milestone in the development of
this list; that we've started to focus on methodologies rather than the
actual task of CSS. And I think there's a Kat grinning right along with
me. Platonic commentary, anyone? (And yes, that's an obscure joke that
doesn't need to be commented upon on list, nor will it be explained, as
it is far off-topic.)
Have fun,
Arlen
-----
In God We Trust, all others must supply data
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
