Simon Levy wrote:
> I have a few questions about how to layout and organise your CSS
> files
>
> A)
Both, in fact: all, methods are equal. Choose the one that suits you and
seems to be best for maintenance - also by others if you're not the only
one involved.
You can find more "best practices" advocated than you can keep track of,
and they are all "conditional" in that they suit a person or a
working-group. Besides, these "best practices" tend to change - constantly.
No method fits all situations anyway, so I think 'efficiency' is the
keyword here.
> B) What are the advantages/disadvantages of having multiple CSS files
> broken down into navigation.css, common.css, main.css, list.css etc
> and using the @import
Breaking it up may ease re-use of certain parts on other sections /
sites. It very much depends on your strategies, and if you get the
individual parts wrong you may end up creating a gigantic mess.
Personally, I tend to separate my stylesheets into 'basic layout',
'link-styles', 'print-styles', 'general screen-styles', 'SSR styles',
'projection styles', and maybe also a separate hack-sheet or two for
buggy IE-versions. I then @import them into the 'basic layout'
stylesheet(s) as required by each design.
Each set of styles / stylesheet targets its own media through an
@media wrapper, so future conflicts are avoided.
This means I often only have to create a new 'basic layout' stylesheet,
and re-use a suitable set of versions from previous creations. Suits
_me_ just fine, but may not be liked by others.
Again: 'efficiency' is the keyword.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
