Kelemen Viktor wrote:
> Dear All!
>
> I've just read the following: CSS Coding standards v0.2 by Andy Peatling
> (http://www.cssdev.com/docs/css_guidelines.pdf)
>
> It describes a special file structure which has to do with
> global.css <- structure.css, text.css, theme.css and so on
>
> My question is that: is this method is usefully and fundamental or just
> fancy?
>
> is there better article?
>
> Thanks in advance
> Viktor
I use a similar approach and find it very useful.
On my current project I have a stylesheets.css importing layout.css,
typography.css, and presentation.css.
I differ from Andy in that I prefer to have items described, as far as
possible, in only one place. Presentation is the exception, in that all
the elements it describes have some kind of layout or typographical
information attached to them - but everything static relating to text,
including metrics like padding and margin, go into typography.css.
However, whereas nearly all my typographic elements have colour by
default and that is something I define in typography.css, context can
change this and I will do things like [.members p.em {color:red} .public
p.em {color:blue}] in presentation.css.
At the end of the day this stuff has to be highly personal, because
everyone works in different ways and finds different attitudes easier to
deal with.
For my part I find it fantastic for large files because any positioning
problem will be to do with layout.css, text will be controlled by
typography.css and contextual colours etc will be in presentation.css.
Regards,
Barney
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7 information -- 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/
