Sent by Nelson_Rodriguez-Pena on 23 July 2003 17:05
Hi,
>> Great idea to put together a methodology. I'd love to see the finished
list.
I agree with that too. I've found that a great way of organizing mi styles
is separating rules in files that have sense as modules, so for example, an
intranet will have:
- login.css: having everything it needs, it shouldn't be much...
Then, entering the main page, I'll load the main styles:
- main.css with the main rules, like BODY, P, Hx, etc. describing
presentational attributes, but *not LAYOUT*;
- layout.css which describes de layout an page distribution of elements,
headers, columns, footer, etc.
- print.css with printing styles.
If other pages use specific styles, they load/call then when needed.
This makes it very easy to modularize and find what you need when editing...
My 2 pesos (which are in fact less than 2 cents...).
regards,
------------------------------------------------------------
Nelson Rodriguez-Pena A.
Web & Multimedia Design & Development
[EMAIL-REMOVED]
------------------------------------------------------------
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
