<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title><![CDATA[Content with Style - Comments on Modular CSS]]></title>
    <link>http://www.contentwithstyle.co.uk/feeds/rss/comments/12</link>
    <description><![CDATA[]]></description>
    <pubDate>Thu, 02 Sep 2010 15:00:29 -0400</pubDate>
    <generator>Zend_Feed</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <item>
      <title><![CDATA[Content with Style - Comment #1 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-6</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-6</guid>
      <description><![CDATA[Curious: why would you use the Global Whitespace Reset as a development stylesheet? Why not incorporate it into your typography stylesheet and leave it there?]]></description>
      <content:encoded><![CDATA[Curious: why would you use the Global Whitespace Reset as a development stylesheet? Why not incorporate it into your typography stylesheet and leave it there?]]></content:encoded>
      <pubDate>Wed, 18 May 2005 23:10:12 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #2 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-7</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-7</guid>
      <description><![CDATA[I find that clients have a habit of using tags I never thought they&#8217;d ever need, and leaving the global whitespace reset in guaruntees that if they do, thay&#8217;ll be on the phone. With whitespace left to the browser default on tags that I&#8217;ve not thought of I at least stand a fighting chance of things looking okay until I can fix things properly. I&#8217;m not sure I&#8217;ve explained that too well but do you see what I mean?]]></description>
      <content:encoded><![CDATA[I find that clients have a habit of using tags I never thought they&#8217;d ever need, and leaving the global whitespace reset in guaruntees that if they do, thay&#8217;ll be on the phone. With whitespace left to the browser default on tags that I&#8217;ve not thought of I at least stand a fighting chance of things looking okay until I can fix things properly. I&#8217;m not sure I&#8217;ve explained that too well but do you see what I mean?]]></content:encoded>
      <pubDate>Wed, 18 May 2005 23:36:08 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #3 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-10</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-10</guid>
      <description><![CDATA[nice page<br />
<br />
how to create a 90 degres text for any browser]]></description>
      <content:encoded><![CDATA[nice page<br />
<br />
how to create a 90 degres text for any browser]]></content:encoded>
      <pubDate>Thu, 19 May 2005 23:13:38 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #4 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-11</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-11</guid>
      <description><![CDATA[That looks like a good technique.  I&#8217;ve recently watched <a href="http://www.ficwad.com/skins/kemayo/style.css">the CSS</a> on a website my wife and I are building together balloon out of control, and this looks like a technique that might help make things manageable again.  (It&#8217;s the first time she&#8217;s tried to use CSS, so I hear the frequent cries if &#8220;aaaaaaaaaaaaagh! I hate CSS!&#8221;...)]]></description>
      <content:encoded><![CDATA[That looks like a good technique.  I&#8217;ve recently watched <a href="http://www.ficwad.com/skins/kemayo/style.css">the CSS</a> on a website my wife and I are building together balloon out of control, and this looks like a technique that might help make things manageable again.  (It&#8217;s the first time she&#8217;s tried to use CSS, so I hear the frequent cries if &#8220;aaaaaaaaaaaaagh! I hate CSS!&#8221;...)]]></content:encoded>
      <pubDate>Thu, 19 May 2005 23:33:36 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #5 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-12</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-12</guid>
      <description><![CDATA[I know that feeling! It&#8217;s especially powerful when you have tried and tested sheets on several sites&#8230; Then you can be confident that the basics are right and you can get on with the serious business of making everything look &#8216;proper&#8217;.]]></description>
      <content:encoded><![CDATA[I know that feeling! It&#8217;s especially powerful when you have tried and tested sheets on several sites&#8230; Then you can be confident that the basics are right and you can get on with the serious business of making everything look &#8216;proper&#8217;.]]></content:encoded>
      <pubDate>Fri, 20 May 2005 02:47:38 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #6 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-13</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-13</guid>
      <description><![CDATA[Excellent solution.<br />
Not only can it simplify the process, it also expedites changes as I now don&#8217;t have to search or scroll through lines upons lines of code. I will definitely be looking into modulizing (sp?) our CSS.]]></description>
      <content:encoded><![CDATA[Excellent solution.<br />
Not only can it simplify the process, it also expedites changes as I now don&#8217;t have to search or scroll through lines upons lines of code. I will definitely be looking into modulizing (sp?) our CSS.]]></content:encoded>
      <pubDate>Fri, 20 May 2005 04:40:01 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #7 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-14</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-14</guid>
      <description><![CDATA[One thing to keep in mind with this technique is that you&#8217;re turning one HTTP connection into five. It may be worth it to have manageable code, but load times are always something to consider.]]></description>
      <content:encoded><![CDATA[One thing to keep in mind with this technique is that you&#8217;re turning one HTTP connection into five. It may be worth it to have manageable code, but load times are always something to consider.]]></content:encoded>
      <pubDate>Fri, 20 May 2005 05:37:24 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #8 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-15</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-15</guid>
      <description><![CDATA[You got a duff link there Mike :( My file extensions are .html<br />
<br />
(Nice article! Via Andy Budd)]]></description>
      <content:encoded><![CDATA[You got a duff link there Mike :( My file extensions are .html<br />
<br />
(Nice article! Via Andy Budd)]]></content:encoded>
      <pubDate>Fri, 20 May 2005 09:03:57 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #9 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-16</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-16</guid>
      <description><![CDATA[@ Joshua:<br />
<br />
Having the CSS split into single modules makes sense if U consider that most &#8220;average&#8221; users turn on browser caching (or leave it turned on). <br />
<br />
So once loaded you can have the reusable parts cached and just pull in the changed parts. I like Mikes idea as well, but most times my approach is to split stuff into navigation, header, footer and typography, then exchange the content bit by using wrapper css files with @import.<br />
<br />
Any other thoughts on this?]]></description>
      <content:encoded><![CDATA[@ Joshua:<br />
<br />
Having the CSS split into single modules makes sense if U consider that most &#8220;average&#8221; users turn on browser caching (or leave it turned on). <br />
<br />
So once loaded you can have the reusable parts cached and just pull in the changed parts. I like Mikes idea as well, but most times my approach is to split stuff into navigation, header, footer and typography, then exchange the content bit by using wrapper css files with @import.<br />
<br />
Any other thoughts on this?]]></content:encoded>
      <pubDate>Fri, 20 May 2005 09:56:05 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #10 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-17</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-17</guid>
      <description><![CDATA[Ooops, sorry Malarkey. I&#8217;ll fire my editor. It&#8217;s cured now&#8230;]]></description>
      <content:encoded><![CDATA[Ooops, sorry Malarkey. I&#8217;ll fire my editor. It&#8217;s cured now&#8230;]]></content:encoded>
      <pubDate>Fri, 20 May 2005 12:46:46 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #11 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-21</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-21</guid>
      <description><![CDATA[Pascal:<br />
<br />
True enough, once the CSS is cached it makes no difference. The issue I see is the <em>initial</em> load time. I don&#8217;t think the importance of having the first load happen as quickly as possible can be understated.<br />
<br />
Another issue I see is the duplication of selectors. Having multiple instances of your selectors for every type of rule could add considerably to your overall CSS filesize.<br />
<br />
Both of these issues may be trivial when one considers HTTP pipelining, gzip compression, and all the other means we have to optimize HTTP connections, but if I can shave half a second off my initial load at the cost of less manageable CSS, I will. In the end it&#8217;s one of the thousands of tradeoffs that has to be made when designing a site.]]></description>
      <content:encoded><![CDATA[Pascal:<br />
<br />
True enough, once the CSS is cached it makes no difference. The issue I see is the <em>initial</em> load time. I don&#8217;t think the importance of having the first load happen as quickly as possible can be understated.<br />
<br />
Another issue I see is the duplication of selectors. Having multiple instances of your selectors for every type of rule could add considerably to your overall CSS filesize.<br />
<br />
Both of these issues may be trivial when one considers HTTP pipelining, gzip compression, and all the other means we have to optimize HTTP connections, but if I can shave half a second off my initial load at the cost of less manageable CSS, I will. In the end it&#8217;s one of the thousands of tradeoffs that has to be made when designing a site.]]></content:encoded>
      <pubDate>Fri, 20 May 2005 18:31:16 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #12 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-23</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-23</guid>
      <description><![CDATA[Just make your master css a php file that pulls in the files like includes. <br />
<br />
spidering off 5 connections is a waste of resources.]]></description>
      <content:encoded><![CDATA[Just make your master css a php file that pulls in the files like includes. <br />
<br />
spidering off 5 connections is a waste of resources.]]></content:encoded>
      <pubDate>Sat, 21 May 2005 01:36:12 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #13 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-24</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-24</guid>
      <description><![CDATA[Yeah Non, that&#8217;s a good idea if you want to save on requests. <br />
<br />
The point of the article is more the breaking down of your stylsheets into their functional parts than the recombination. <br />
<br />
The problem with putting everything back together on the server side is that you then can&#8217;t take advantage of client-side caching if you drop in other sheets on specific pages. I normally separate the home page layout from the rest of the layout, for example, because there&#8217;s no point serving it to every page. I also tend to swap layout sheets to switch between 2 column and 1 column page variations etc rather than switching on body id or the like. See my <a href="http://www.contentwithstyle.co.uk/Articles/17/a-css-framework">CSS Framework</a> article&#8230; <br />
<br />
At the end of the day, what you do will depend on the requirements of the project and your personal preferences.]]></description>
      <content:encoded><![CDATA[Yeah Non, that&#8217;s a good idea if you want to save on requests. <br />
<br />
The point of the article is more the breaking down of your stylsheets into their functional parts than the recombination. <br />
<br />
The problem with putting everything back together on the server side is that you then can&#8217;t take advantage of client-side caching if you drop in other sheets on specific pages. I normally separate the home page layout from the rest of the layout, for example, because there&#8217;s no point serving it to every page. I also tend to swap layout sheets to switch between 2 column and 1 column page variations etc rather than switching on body id or the like. See my <a href="http://www.contentwithstyle.co.uk/Articles/17/a-css-framework">CSS Framework</a> article&#8230; <br />
<br />
At the end of the day, what you do will depend on the requirements of the project and your personal preferences.]]></content:encoded>
      <pubDate>Sat, 21 May 2005 13:26:53 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #14 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-30</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-30</guid>
      <description><![CDATA[I use PHP instead, as part of an overall modular design. If you&#8217;re curious, have a look at this section of my article on building modular XHTML pages with PHP:<br />
<br />
http://loadaveragezero.com/vnav/labs/PHP/head.php#code<br />
<br />
Around paragraph seven of that section I explain how I conditionally import the extra stylesheets. You may enjoy also following the link via my signature to this comment as I just added this article to my developer&#8217;s resource DB. ~d]]></description>
      <content:encoded><![CDATA[I use PHP instead, as part of an overall modular design. If you&#8217;re curious, have a look at this section of my article on building modular XHTML pages with PHP:<br />
<br />
http://loadaveragezero.com/vnav/labs/PHP/head.php#code<br />
<br />
Around paragraph seven of that section I explain how I conditionally import the extra stylesheets. You may enjoy also following the link via my signature to this comment as I just added this article to my developer&#8217;s resource DB. ~d]]></content:encoded>
      <pubDate>Mon, 23 May 2005 02:42:42 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #15 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-33</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-33</guid>
      <description><![CDATA[@ Douglas:<br />
Doesn&#8217;t that get to the same point of loosing the client caching again?]]></description>
      <content:encoded><![CDATA[@ Douglas:<br />
Doesn&#8217;t that get to the same point of loosing the client caching again?]]></content:encoded>
      <pubDate>Mon, 23 May 2005 09:19:40 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #16 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-35</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-35</guid>
      <description><![CDATA[Pascal:<br />
<br />
Why would adding link @import elements to the head of your document for each CSS module prevent the browser from caching the stylesheets? The stylesheets themselves aren&#8217;t dynamic.]]></description>
      <content:encoded><![CDATA[Pascal:<br />
<br />
Why would adding link @import elements to the head of your document for each CSS module prevent the browser from caching the stylesheets? The stylesheets themselves aren&#8217;t dynamic.]]></content:encoded>
      <pubDate>Mon, 23 May 2005 10:39:30 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #17 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-36</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-36</guid>
      <description><![CDATA[@douglas:<br />
point! that happens when you post comments before you think about it ;)]]></description>
      <content:encoded><![CDATA[@douglas:<br />
point! that happens when you post comments before you think about it ;)]]></content:encoded>
      <pubDate>Mon, 23 May 2005 10:57:43 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #18 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-42</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-42</guid>
      <description><![CDATA[Actually, to clarify: one style element with one or more @imports.<br />
<br />
On a side note, I recently wrote an article for Digital Web about dynamically generated CSS using PHP. That was the number one reaction by far: but dynamic CSS is slow, the browser doesn&#8217;t cache the results! First of all, unless your host is heavily loaded, generating something simple like CSS with a scripting language like PHP is almost as fast as a static file. And the &#8220;almost&#8221; bit is so trivial that no one would ever notice it unless you happen to run with snails. I&#8217;m even aware of situations when dynamic content is actually faster than a disk file. As far as the caching issue goes, that is trivial to fix.<br />
<br />
Yet one post after another, dynamic CSS is slow! The browser doesn&#8217;t cache it! Sigh. ~d]]></description>
      <content:encoded><![CDATA[Actually, to clarify: one style element with one or more @imports.<br />
<br />
On a side note, I recently wrote an article for Digital Web about dynamically generated CSS using PHP. That was the number one reaction by far: but dynamic CSS is slow, the browser doesn&#8217;t cache the results! First of all, unless your host is heavily loaded, generating something simple like CSS with a scripting language like PHP is almost as fast as a static file. And the &#8220;almost&#8221; bit is so trivial that no one would ever notice it unless you happen to run with snails. I&#8217;m even aware of situations when dynamic content is actually faster than a disk file. As far as the caching issue goes, that is trivial to fix.<br />
<br />
Yet one post after another, dynamic CSS is slow! The browser doesn&#8217;t cache it! Sigh. ~d]]></content:encoded>
      <pubDate>Mon, 23 May 2005 18:26:40 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #19 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-47</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-47</guid>
      <description><![CDATA[My big css problem is:<br />
<br />
to let topstyle format code or not?<br />
(i mean alfabetical ordering&#8230;)]]></description>
      <content:encoded><![CDATA[My big css problem is:<br />
<br />
to let topstyle format code or not?<br />
(i mean alfabetical ordering&#8230;)]]></content:encoded>
      <pubDate>Mon, 23 May 2005 22:24:52 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #20 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-51</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-51</guid>
      <description><![CDATA[Douglas: I think the misunderstanding was going back to Non&#8217;s post. He suggested using PHP to replace @import &#8211; making one long stylesheet to save on server requests. I&#8217;ve got no problem with generating stylesheets server-side, since these newfangled computer-thingies are alarmingly quick, but I&#8217;d favour a method that resulted in several sheets so that the common ones could be cached. <br />
<br />
The key benefit of this technique for me is the reusability though. I use my typo.css and forms.css sheets again and again between projects with only minimal changes. I&#8217;ve also got a tools sheet that contains classes for markupless clearing of floats, accessible hiding and image replacement, which I use over and over.]]></description>
      <content:encoded><![CDATA[Douglas: I think the misunderstanding was going back to Non&#8217;s post. He suggested using PHP to replace @import &#8211; making one long stylesheet to save on server requests. I&#8217;ve got no problem with generating stylesheets server-side, since these newfangled computer-thingies are alarmingly quick, but I&#8217;d favour a method that resulted in several sheets so that the common ones could be cached. <br />
<br />
The key benefit of this technique for me is the reusability though. I use my typo.css and forms.css sheets again and again between projects with only minimal changes. I&#8217;ve also got a tools sheet that contains classes for markupless clearing of floats, accessible hiding and image replacement, which I use over and over.]]></content:encoded>
      <pubDate>Tue, 24 May 2005 00:58:27 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #21 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-53</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-53</guid>
      <description><![CDATA[I wrote a <a href="http://stilbuero.de/blog/2005/05/efficient-reuse-of-modular-style.html">follow-up article regarding modular CSS and efficient reuse</a> for some additional thoughts. I wonder what you guys think. Comments are welcome!]]></description>
      <content:encoded><![CDATA[I wrote a <a href="http://stilbuero.de/blog/2005/05/efficient-reuse-of-modular-style.html">follow-up article regarding modular CSS and efficient reuse</a> for some additional thoughts. I wonder what you guys think. Comments are welcome!]]></content:encoded>
      <pubDate>Tue, 24 May 2005 14:18:29 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #22 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-59</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-59</guid>
      <description><![CDATA[Mike:<br />
<br />
Right, the comments regarding using PHP to generate CSS were an aside. On my site (for the most part) I only use PHP to generate the style element that @imports the various extra stylesheets: forms, tables, code, etc&#8230;very much in keeping with your article.<br />
<br />
I only brought up the topic of caching because as soon as many people hear &#8220;PHP&#8221; and &#8220;CSS&#8221; in the same sentence they all start in on how dynamic CSS is so slow. If done correctly, this is simply not the case. I guess preventing more misinformation was my goal with that post.<br />
<br />
New favicon? heehee, Doug]]></description>
      <content:encoded><![CDATA[Mike:<br />
<br />
Right, the comments regarding using PHP to generate CSS were an aside. On my site (for the most part) I only use PHP to generate the style element that @imports the various extra stylesheets: forms, tables, code, etc&#8230;very much in keeping with your article.<br />
<br />
I only brought up the topic of caching because as soon as many people hear &#8220;PHP&#8221; and &#8220;CSS&#8221; in the same sentence they all start in on how dynamic CSS is so slow. If done correctly, this is simply not the case. I guess preventing more misinformation was my goal with that post.<br />
<br />
New favicon? heehee, Doug]]></content:encoded>
      <pubDate>Tue, 24 May 2005 16:48:07 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #23 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-60</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-60</guid>
      <description><![CDATA[Doug: Ah, my bad &#8211; sorry. I really like the idea of using PHP to just include the stylesheets you&#8217;re going to use on that page. Table styling, especially, gets very weighty very quickly. How do you flag which pages use which sheets? Some clever RegExp/XSL detection? The demo pages use PHP to include the relevent layout stylesheet, although in a very rudimentary way. <br />
<br />
The favicon is nothing to do with me but I like it! It feels like Pascal&#8217;s doing&#8230;]]></description>
      <content:encoded><![CDATA[Doug: Ah, my bad &#8211; sorry. I really like the idea of using PHP to just include the stylesheets you&#8217;re going to use on that page. Table styling, especially, gets very weighty very quickly. How do you flag which pages use which sheets? Some clever RegExp/XSL detection? The demo pages use PHP to include the relevent layout stylesheet, although in a very rudimentary way. <br />
<br />
The favicon is nothing to do with me but I like it! It feels like Pascal&#8217;s doing&#8230;]]></content:encoded>
      <pubDate>Tue, 24 May 2005 16:55:17 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #24 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-61</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-61</guid>
      <description><![CDATA[Yup, new favicon :)]]></description>
      <content:encoded><![CDATA[Yup, new favicon :)]]></content:encoded>
      <pubDate>Tue, 24 May 2005 17:09:06 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #25 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-63</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-63</guid>
      <description><![CDATA[Mike:<br />
<br />
I build each page with a series of modular PHP functions that mirror the structure of an XHTML document. One of which of course creates the head element. All pages use the root.css stylesheet. If I need to pull in more, I simply pass an array of them to the head function: head(array(&#8216;forms&#8217;,&#8217;tables&#8217;));&#8212;same thing with extra Javascript libraries (although I don&#8217;t use them very much, being a server-side kinda guy).<br />
<br />
Pascal:<br />
<br />
Why you little sneak! Actually, if I&#8217;m right and you got the icon from the one I created yesterday then you guys are the first to do this (that I&#8217;m aware of) and it makes me smile to know this. Personally, I use the favicons as a mnemonic tool for my listings in the DB. I can visualize what page I&#8217;m about to visit just before I click through to it. Minor eye candy too. Not sure if my visitors benefit from it or not. If a site I list doesn&#8217;t have one, then I create it. If the owner likes it and uses it, well, that&#8217;s great!]]></description>
      <content:encoded><![CDATA[Mike:<br />
<br />
I build each page with a series of modular PHP functions that mirror the structure of an XHTML document. One of which of course creates the head element. All pages use the root.css stylesheet. If I need to pull in more, I simply pass an array of them to the head function: head(array(&#8216;forms&#8217;,&#8217;tables&#8217;));&#8212;same thing with extra Javascript libraries (although I don&#8217;t use them very much, being a server-side kinda guy).<br />
<br />
Pascal:<br />
<br />
Why you little sneak! Actually, if I&#8217;m right and you got the icon from the one I created yesterday then you guys are the first to do this (that I&#8217;m aware of) and it makes me smile to know this. Personally, I use the favicons as a mnemonic tool for my listings in the DB. I can visualize what page I&#8217;m about to visit just before I click through to it. Minor eye candy too. Not sure if my visitors benefit from it or not. If a site I list doesn&#8217;t have one, then I create it. If the owner likes it and uses it, well, that&#8217;s great!]]></content:encoded>
      <pubDate>Tue, 24 May 2005 17:53:52 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #26 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-64</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-64</guid>
      <description><![CDATA[Nahh, I just think it was missing &#8230;<br />
I have one on my portfolio-domain <a href="http://www.pascalopitz.de">www.pascalopitz.de</a> since ages, but as we just started up there&#8217;s much room for improvement here &#8230;]]></description>
      <content:encoded><![CDATA[Nahh, I just think it was missing &#8230;<br />
I have one on my portfolio-domain <a href="http://www.pascalopitz.de">www.pascalopitz.de</a> since ages, but as we just started up there&#8217;s much room for improvement here &#8230;]]></content:encoded>
      <pubDate>Tue, 24 May 2005 20:51:02 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #27 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-70</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-70</guid>
      <description><![CDATA[All that work for nothing! It must of taken me at least 2 minutes. heehee]]></description>
      <content:encoded><![CDATA[All that work for nothing! It must of taken me at least 2 minutes. heehee]]></content:encoded>
      <pubDate>Wed, 25 May 2005 05:38:07 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #28 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-79</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-79</guid>
      <description><![CDATA[...I&#8217;ve been checking my referrer logs, and noticed that six or seven people have been following that link to my messy CSS per day since I left that comment.  So I felt that mentioning an updated version (on a development server, as the live site hasn&#8217;t been updated since I made the changes).<br />
<br />
To really be in line with the article, I&#8217;d need to shift some rules from the typography stylesheet to the layout sheet.  I just went through my old CSS and did a lot of copy-paste to split things up by type.<br />
<br />
I was slightly surprised to note that there wasn&#8217;t much of a size increse in this.  All the new files together weigh in at about 0.7kb larger than the old monolithic stylesheet.  I was expecting more, considering the selector duplication.]]></description>
      <content:encoded><![CDATA[...I&#8217;ve been checking my referrer logs, and noticed that six or seven people have been following that link to my messy CSS per day since I left that comment.  So I felt that mentioning an updated version (on a development server, as the live site hasn&#8217;t been updated since I made the changes).<br />
<br />
To really be in line with the article, I&#8217;d need to shift some rules from the typography stylesheet to the layout sheet.  I just went through my old CSS and did a lot of copy-paste to split things up by type.<br />
<br />
I was slightly surprised to note that there wasn&#8217;t much of a size increse in this.  All the new files together weigh in at about 0.7kb larger than the old monolithic stylesheet.  I was expecting more, considering the selector duplication.]]></content:encoded>
      <pubDate>Wed, 25 May 2005 21:16:54 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #29 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-80</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-80</guid>
      <description><![CDATA[Of course, I&#8217;d look smarter if I remembered that whole Textile linking thing.<br />
<br />
<a href="http://mundane.kemayo.com/efictionk/skins/kemayo/screen.css">The updated stylesheet</a>]]></description>
      <content:encoded><![CDATA[Of course, I&#8217;d look smarter if I remembered that whole Textile linking thing.<br />
<br />
<a href="http://mundane.kemayo.com/efictionk/skins/kemayo/screen.css">The updated stylesheet</a>]]></content:encoded>
      <pubDate>Wed, 25 May 2005 21:19:06 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #30 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-92</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-92</guid>
      <description><![CDATA[This seems a useful methodology for bringing order to my usual chaos. I have been heading this way but you have set it out really neatly. I have been evolving an Initialisation section for global resets,  hacks and other universal monstrosities. Thanks.]]></description>
      <content:encoded><![CDATA[This seems a useful methodology for bringing order to my usual chaos. I have been heading this way but you have set it out really neatly. I have been evolving an Initialisation section for global resets,  hacks and other universal monstrosities. Thanks.]]></content:encoded>
      <pubDate>Thu, 26 May 2005 23:59:20 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #31 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-96</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-96</guid>
      <description><![CDATA[Very interesting article, but I do not understand one little thing : one time you speak about screen.css, and after about shell.css. What is the difference ?<br />
<br />
Thanks for you answer !]]></description>
      <content:encoded><![CDATA[Very interesting article, but I do not understand one little thing : one time you speak about screen.css, and after about shell.css. What is the difference ?<br />
<br />
Thanks for you answer !]]></content:encoded>
      <pubDate>Fri, 27 May 2005 07:30:33 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #32 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-98</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-98</guid>
      <description><![CDATA[Sorry Sebastien, that&#8217;s typo on my part. They should both read screen.css, which is the container I use to @import my screen media stylesheets. I&#8217;ve also updated the paragraph following that because, reading it back now, I&#8217;m amazed anyone understood it. Cheers!]]></description>
      <content:encoded><![CDATA[Sorry Sebastien, that&#8217;s typo on my part. They should both read screen.css, which is the container I use to @import my screen media stylesheets. I&#8217;ve also updated the paragraph following that because, reading it back now, I&#8217;m amazed anyone understood it. Cheers!]]></content:encoded>
      <pubDate>Fri, 27 May 2005 15:47:22 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #33 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-248</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-248</guid>
      <description><![CDATA[rouping of styles can be done also like this<br />
<br />
screen.css<br />
print.css<br />
alterantestyles.css<br />
<br />
layout.css<br />
nav.css<br />
js_enabled.css<br />
<br />
splash.css<br />
sectionsA.css<br />
sectionsB.css<br />
comments.css<br />
<br />
screen.css<br />
basicstyling.css<br />
iewin.css<br />
ie5mac.css<br />
<br />
It all depends on what styles are you reusing, which styles I can load already, which browsers I target (important !!). <br />
<br />
also when it is cut up in different files, it loads chunk by chunk, although not all chunks are equal loads]]></description>
      <content:encoded><![CDATA[rouping of styles can be done also like this<br />
<br />
screen.css<br />
print.css<br />
alterantestyles.css<br />
<br />
layout.css<br />
nav.css<br />
js_enabled.css<br />
<br />
splash.css<br />
sectionsA.css<br />
sectionsB.css<br />
comments.css<br />
<br />
screen.css<br />
basicstyling.css<br />
iewin.css<br />
ie5mac.css<br />
<br />
It all depends on what styles are you reusing, which styles I can load already, which browsers I target (important !!). <br />
<br />
also when it is cut up in different files, it loads chunk by chunk, although not all chunks are equal loads]]></content:encoded>
      <pubDate>Tue, 27 Sep 2005 10:30:40 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #34 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-249</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-249</guid>
      <description><![CDATA[Yeah, absolutely. How you break up your stylesheets completely depends on what makes sense to you and the project you&#8217;re working on. I go for slightly larger chunks because that&#8217;s how my head works best but if you can keep track of more files then by all means do!<br />
<br />
For example, I like to keep my hacks along with the rules they&#8217;re over-riding so that I don&#8217;t lose track of them, but I also appreciate the advantages of keeping them in separate stylesheets. (I stopped doing that after spending ages trying to debug a sheet only to find that the rule I was grappling with was being reset elsewhere and I didn&#8217;t realise.)]]></description>
      <content:encoded><![CDATA[Yeah, absolutely. How you break up your stylesheets completely depends on what makes sense to you and the project you&#8217;re working on. I go for slightly larger chunks because that&#8217;s how my head works best but if you can keep track of more files then by all means do!<br />
<br />
For example, I like to keep my hacks along with the rules they&#8217;re over-riding so that I don&#8217;t lose track of them, but I also appreciate the advantages of keeping them in separate stylesheets. (I stopped doing that after spending ages trying to debug a sheet only to find that the rule I was grappling with was being reset elsewhere and I didn&#8217;t realise.)]]></content:encoded>
      <pubDate>Wed, 28 Sep 2005 04:30:02 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #35 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-262</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-262</guid>
      <description><![CDATA[Great article Mike, I believe this is the most extensible way to develop and maintain CSS. I hope to apply this in my next little project :)]]></description>
      <content:encoded><![CDATA[Great article Mike, I believe this is the most extensible way to develop and maintain CSS. I hope to apply this in my next little project :)]]></content:encoded>
      <pubDate>Mon, 10 Oct 2005 18:48:57 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #36 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-264</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-264</guid>
      <description><![CDATA[5 connections?  What web server from 1995 are you using that doesn&#8217;t support HTTP 1.1 with persistent connections (Apache &#8220;KeepAlive&#8221;)?<br />
<br />
5 requests perhaps.<br />
<br />
Not the same concept as 5 connections by far.]]></description>
      <content:encoded><![CDATA[5 connections?  What web server from 1995 are you using that doesn&#8217;t support HTTP 1.1 with persistent connections (Apache &#8220;KeepAlive&#8221;)?<br />
<br />
5 requests perhaps.<br />
<br />
Not the same concept as 5 connections by far.]]></content:encoded>
      <pubDate>Tue, 11 Oct 2005 10:48:49 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #37 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-279</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-279</guid>
      <description><![CDATA[Great article]]></description>
      <content:encoded><![CDATA[Great article]]></content:encoded>
      <pubDate>Wed, 26 Oct 2005 17:59:32 -0400</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #38 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-289</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-289</guid>
      <description><![CDATA[You could include extra rules (ie. &#8216;where did i set the padding?&#8217;) as comments in the stylesheet]]></description>
      <content:encoded><![CDATA[You could include extra rules (ie. &#8216;where did i set the padding?&#8217;) as comments in the stylesheet]]></content:encoded>
      <pubDate>Mon, 31 Oct 2005 08:51:22 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #39 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-314</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-314</guid>
      <description><![CDATA[Several issues as conclusion from the comments :<br />
1. 5 connections is bad for clients<br />
2. php is a solution that can minimize 5 connections<br />
3. php wont cache right (why?)<br />
<br />
Now an integration of these comments brings out this idea :<br />
<br />
A php script that will import all 5 stylesheets&#8212;while he&#8217;s importing, also do some basic processing of the styles to combine similar definitions.<br />
<br />
Example :<br />
<br />
1. these tags are in different files :<br />
h1 { font-family: sans-serif; font-size: 10em }<br />
h1 { margin-left: 3em; }<br />
h1 { color: blue; background-color: cyan; }<br />
<br />
2. the php script combines it all into one tag like so :<br />
h1 { font-family: sans-serif; font-size: 10em; margin-left: 3em; color: blue; background-color: cyan; }<br />
<br />
3. the php script sets its time correctly . . . to the last updated css file (if you update color.css last, then that is the time php script should send out)<br />
<br />
This way what will happen is :<br />
1. proper caching will work (right times reported)<br />
2. multiple (5) connections is not an issue<br />
3. css taking too much &#8220;space&#8221;/&#8221;bandwidth&#8221; is not an issue<br />
4. extra connections for style wont happen<br />
5. modular css is still managable!<br />
6. php script is a real easy one, and might be fast (enough) as well&#8230;<br />
<br />
is there anything that I am missing?<br />
anything anyone wants to suggest extra?]]></description>
      <content:encoded><![CDATA[Several issues as conclusion from the comments :<br />
1. 5 connections is bad for clients<br />
2. php is a solution that can minimize 5 connections<br />
3. php wont cache right (why?)<br />
<br />
Now an integration of these comments brings out this idea :<br />
<br />
A php script that will import all 5 stylesheets&#8212;while he&#8217;s importing, also do some basic processing of the styles to combine similar definitions.<br />
<br />
Example :<br />
<br />
1. these tags are in different files :<br />
h1 { font-family: sans-serif; font-size: 10em }<br />
h1 { margin-left: 3em; }<br />
h1 { color: blue; background-color: cyan; }<br />
<br />
2. the php script combines it all into one tag like so :<br />
h1 { font-family: sans-serif; font-size: 10em; margin-left: 3em; color: blue; background-color: cyan; }<br />
<br />
3. the php script sets its time correctly . . . to the last updated css file (if you update color.css last, then that is the time php script should send out)<br />
<br />
This way what will happen is :<br />
1. proper caching will work (right times reported)<br />
2. multiple (5) connections is not an issue<br />
3. css taking too much &#8220;space&#8221;/&#8221;bandwidth&#8221; is not an issue<br />
4. extra connections for style wont happen<br />
5. modular css is still managable!<br />
6. php script is a real easy one, and might be fast (enough) as well&#8230;<br />
<br />
is there anything that I am missing?<br />
anything anyone wants to suggest extra?]]></content:encoded>
      <pubDate>Wed, 02 Nov 2005 13:10:11 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #40 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-318</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-318</guid>
      <description><![CDATA[Hmmmm, that sounds interesting. You&#8217;ll have to make sure that the script combines the rules in the order they are imported (as in your example). It would probably be worth adding whitespace stripping to the final files as well for a bit of added compression.<br />
<br />
The only issue for me is that I use combinations of stylesheets across pages within a site. By that I mean that the home page might have:<br />
@import url(&#8220;typo.css&#8221;);<br />
@import url(&#8220;layout.css&#8221;);<br />
@import url(&#8220;home-layout.css&#8221;);<br />
@import url(&#8220;horizontal-nav.css&#8221;);<br />
@import url(&#8220;skin.css&#8221;);<br />
<br />
While a cotent page might take:<br />
@import url(&#8220;typo.css&#8221;);<br />
@import url(&#8220;forms.css&#8221;);<br />
@import url(&#8220;layout.css&#8221;);<br />
@import url(&#8220;horizontal-nav.css&#8221;);<br />
@import url(&#8220;skin.css&#8221;);<br />
<br />
The idea is to use browser caching to my advantage &#8211; only feeding new sheets as they are required. Your technique wouldn&#8217;t work for all the sites I work on but it would definitely be very useful for some&#8230; <br />
<br />
Good idea!]]></description>
      <content:encoded><![CDATA[Hmmmm, that sounds interesting. You&#8217;ll have to make sure that the script combines the rules in the order they are imported (as in your example). It would probably be worth adding whitespace stripping to the final files as well for a bit of added compression.<br />
<br />
The only issue for me is that I use combinations of stylesheets across pages within a site. By that I mean that the home page might have:<br />
@import url(&#8220;typo.css&#8221;);<br />
@import url(&#8220;layout.css&#8221;);<br />
@import url(&#8220;home-layout.css&#8221;);<br />
@import url(&#8220;horizontal-nav.css&#8221;);<br />
@import url(&#8220;skin.css&#8221;);<br />
<br />
While a cotent page might take:<br />
@import url(&#8220;typo.css&#8221;);<br />
@import url(&#8220;forms.css&#8221;);<br />
@import url(&#8220;layout.css&#8221;);<br />
@import url(&#8220;horizontal-nav.css&#8221;);<br />
@import url(&#8220;skin.css&#8221;);<br />
<br />
The idea is to use browser caching to my advantage &#8211; only feeding new sheets as they are required. Your technique wouldn&#8217;t work for all the sites I work on but it would definitely be very useful for some&#8230; <br />
<br />
Good idea!]]></content:encoded>
      <pubDate>Thu, 03 Nov 2005 06:15:34 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #41 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-321</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-321</guid>
      <description><![CDATA[Great idea ! I love it. I must do that with my next project.]]></description>
      <content:encoded><![CDATA[Great idea ! I love it. I must do that with my next project.]]></content:encoded>
      <pubDate>Mon, 07 Nov 2005 13:57:31 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #42 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-328</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-328</guid>
      <description><![CDATA[thanks for de resource]]></description>
      <content:encoded><![CDATA[thanks for de resource]]></content:encoded>
      <pubDate>Fri, 11 Nov 2005 18:14:05 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #43 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-339</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-339</guid>
      <description><![CDATA[If you&#8217;re going to go to that length, you might as go one step further; parse the CSS, combine it into a single logical file and cache it.<br />
<br />
As an example:<br />
1) First hit to the site, do I have a valid cached copy?<br />
2) If no &#8211; read, parse, optimise, save final product<br />
3) If yes &#8211; send the cached copy<br />
<br />
Using that sort of a method, you wouldn&#8217;t have to read/parse/optimise the files each hit on the site.<br />
<br />
Al.]]></description>
      <content:encoded><![CDATA[If you&#8217;re going to go to that length, you might as go one step further; parse the CSS, combine it into a single logical file and cache it.<br />
<br />
As an example:<br />
1) First hit to the site, do I have a valid cached copy?<br />
2) If no &#8211; read, parse, optimise, save final product<br />
3) If yes &#8211; send the cached copy<br />
<br />
Using that sort of a method, you wouldn&#8217;t have to read/parse/optimise the files each hit on the site.<br />
<br />
Al.]]></content:encoded>
      <pubDate>Wed, 23 Nov 2005 06:25:26 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #44 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-341</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-341</guid>
      <description><![CDATA[Hmm, are we now talkin to optimize the CSS on the fly or on change?<br />
Alistair: If you combine all files for each page into one file you would loose caching of parts, e.g. the navigation.<br />
Evgeny : optimizing the CSS files on the fly or on export and combining multiple blocks into one could bring up problems with selectors and specifity. However, you might wanna check out <a href="http://csstidy.sourceforge.net/">CSSTidy</a> to do what you want to.]]></description>
      <content:encoded><![CDATA[Hmm, are we now talkin to optimize the CSS on the fly or on change?<br />
Alistair: If you combine all files for each page into one file you would loose caching of parts, e.g. the navigation.<br />
Evgeny : optimizing the CSS files on the fly or on export and combining multiple blocks into one could bring up problems with selectors and specifity. However, you might wanna check out <a href="http://csstidy.sourceforge.net/">CSSTidy</a> to do what you want to.]]></content:encoded>
      <pubDate>Wed, 23 Nov 2005 10:09:55 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #45 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-359</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-359</guid>
      <description><![CDATA[Thank you. That&#8217;s EXACTLY what I was looking for.]]></description>
      <content:encoded><![CDATA[Thank you. That&#8217;s EXACTLY what I was looking for.]]></content:encoded>
      <pubDate>Sat, 24 Dec 2005 07:07:32 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #46 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-364</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-364</guid>
      <description><![CDATA[I was absolutley amazed by this tutorial! It makes my life SO much easier <strong>whistles</strong> it&#8217;s easy, and not difficult to implement. I know I&#8217;ll be using modular css from now on!<br />
<br />
I was actually looking for another coding solution to a problem I had when I found this site. My website is skinned, and I would want a tagboard that uses the css of the specific skin (not the regular importing css code that imports from a specified location). I was looking for a code that just imports the stylesheet of the specific skin. I&#8217;ll try looking around this site if you have such a code, but in any case, thanks! :)]]></description>
      <content:encoded><![CDATA[I was absolutley amazed by this tutorial! It makes my life SO much easier <strong>whistles</strong> it&#8217;s easy, and not difficult to implement. I know I&#8217;ll be using modular css from now on!<br />
<br />
I was actually looking for another coding solution to a problem I had when I found this site. My website is skinned, and I would want a tagboard that uses the css of the specific skin (not the regular importing css code that imports from a specified location). I was looking for a code that just imports the stylesheet of the specific skin. I&#8217;ll try looking around this site if you have such a code, but in any case, thanks! :)]]></content:encoded>
      <pubDate>Fri, 06 Jan 2006 23:24:51 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #47 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-365</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-365</guid>
      <description><![CDATA[PS: I&#8217;m sorry for being redundant in my last post :P Again, thanks! :)]]></description>
      <content:encoded><![CDATA[PS: I&#8217;m sorry for being redundant in my last post :P Again, thanks! :)]]></content:encoded>
      <pubDate>Fri, 06 Jan 2006 23:36:59 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #48 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-1879</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-1879</guid>
      <description><![CDATA[1st: Thank you for this article and it]]></description>
      <content:encoded><![CDATA[1st: Thank you for this article and it]]></content:encoded>
      <pubDate>Mon, 08 Jan 2007 19:06:37 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #49 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-1890</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-1890</guid>
      <description><![CDATA[About dynamic CSS being slow, why not use dynamic CSS during development then static CSS in production ?<br />
<br />
I like Daniel&#8217;s approach which uses the best from both worlds: <br />
<a href="http://blog.pixarea.com/index.php/2007/01/07/62-dynamic-css-magic-with-php">PHP-generated CSS magic</a>]]></description>
      <content:encoded><![CDATA[About dynamic CSS being slow, why not use dynamic CSS during development then static CSS in production ?<br />
<br />
I like Daniel&#8217;s approach which uses the best from both worlds: <br />
<a href="http://blog.pixarea.com/index.php/2007/01/07/62-dynamic-css-magic-with-php">PHP-generated CSS magic</a>]]></content:encoded>
      <pubDate>Fri, 12 Jan 2007 13:20:10 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Content with Style - Comment #50 on Modular CSS]]></title>
      <link>http://www.contentwithstyle.co.uk/content/modular-css/#comment-2110</link>
      <guid>http://www.contentwithstyle.co.uk/content/modular-css/#comment-2110</guid>
      <description><![CDATA[Very nice explanation and approach. We&#8217;re considering some similar server side approaches for various reasons.]]></description>
      <content:encoded><![CDATA[Very nice explanation and approach. We&#8217;re considering some similar server side approaches for various reasons.]]></content:encoded>
      <pubDate>Thu, 12 Jul 2007 00:12:03 -0400</pubDate>
    </item>
  </channel>
</rss>
