Ron Kauffman wrote:
The project is a very large publishing site - thinking of
implementing/organising our new css in either a traditional 1/2 sheets way
or by using basic and custom sheets where the custom sheets define all the
@imports for a section/page.
Using a custom sheet defining the components to be used does introduce an
extra layer of presentation i.e. editing the @import list; but it does
depart from monolithic css organisation.
Has anyone any experience using this type of organisation - if we do not use
it we risk an extremely large css file - perhaps 10k lines. Also if we
proceed we introduce more http requests and bandwidth usage..
Hi Ronald,
This question comes up about once a month on the list, and the answer is
basically always "it's up to you." Organize your style sheets in a way
that makes sense to you and is maintainable by your team, or whoever
might inherit the site, in the future.
Zoe
--
Zoe M. Gillenwater
Design Specialist
UNC Highway Safety Research Center
http://www.hsrc.unc.edu
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
