<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: CSS organization tip 1: Flags</title>
	<atom:link href="http://stopdesign.com/archive/2005/05/03/css-tip-flags.html/feed" rel="self" type="application/rss+xml" />
	<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html</link>
	<description>Stopdesign is the creative outlet of Douglas Bowman.</description>
	<lastBuildDate>Tue, 04 May 2010 11:39:03 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Justin Peters</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3248</link>
		<dc:creator>Justin Peters</dc:creator>
		<pubDate>Sun, 26 Jun 2005 00:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3248</guid>
		<description>I use Homesite for most of my authoring and I find this trick handy. I label blocks of CSS like this:

/* &lt;navigation&gt; */

...css goes here...

/* &lt;/navigation&gt; */

Homesite treats the comments as tags and I can use ctrl+m to quickly jump to the bottom of a category to add new styles.

BTW: Does anyone know if there&#039;s a comparable feature in BBEdit -- a keyword shortcut to jump to a closing tag?  It&#039;s one of those handy shortcuts I&#039;ve gotten really used to and miss when using BBEdit.


-Justin</description>
		<content:encoded><![CDATA[<p>I use Homesite for most of my authoring and I find this trick handy. I label blocks of CSS like this:</p>
<p>/* &lt;navigation&gt; */</p>
<p>&#8230;css goes here&#8230;</p>
<p>/* &lt;/navigation&gt; */</p>
<p>Homesite treats the comments as tags and I can use ctrl+m to quickly jump to the bottom of a category to add new styles.</p>
<p>BTW: Does anyone know if there&#8217;s a comparable feature in BBEdit &#8212; a keyword shortcut to jump to a closing tag?  It&#8217;s one of those handy shortcuts I&#8217;ve gotten really used to and miss when using BBEdit.</p>
<p>-Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3247</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Sat, 04 Jun 2005 20:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3247</guid>
		<description>This is great, but if the file you are working on didn&#039;t follow this standard and you don&#039;t feel like scrolling...the DOM Inspector is godsent.</description>
		<content:encoded><![CDATA[<p>This is great, but if the file you are working on didn&#8217;t follow this standard and you don&#8217;t feel like scrolling&#8230;the DOM Inspector is godsent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Stenquist</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3246</link>
		<dc:creator>Jared Stenquist</dc:creator>
		<pubDate>Fri, 03 Jun 2005 00:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3246</guid>
		<description>This is a great tip. Glad I found it. Keep them coming!

- Jared Stenquist</description>
		<content:encoded><![CDATA[<p>This is a great tip. Glad I found it. Keep them coming!</p>
<p>- Jared Stenquist</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jauhari</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3245</link>
		<dc:creator>Jauhari</dc:creator>
		<pubDate>Wed, 25 May 2005 09:15:46 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3245</guid>
		<description>This really helpfull for me, it&#039;s more easy to understood by me ;)

Thanks</description>
		<content:encoded><![CDATA[<p>This really helpfull for me, it&#8217;s more easy to understood by me ;)</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Johansson</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3244</link>
		<dc:creator>Roger Johansson</dc:creator>
		<pubDate>Tue, 24 May 2005 09:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3244</guid>
		<description>The dashes won&#039;t prevent validation, but internal stylesheets that contain double dashes should be wrapped in CDATA sections in XHTML documents sent as application/xhtml+xml. More info here: &lt;a href=&quot;http://devedge-temp.mozilla.org/viewsource/2003/xhtml-style-script/index_en.html&quot; rel=&quot;nofollow&quot;&gt;Properly Using CSS and JavaScript in XHTML Documents&lt;/a&gt; and &lt;a href=&quot;http://www.456bereastreet.com/archive/200501/the_perils_of_using_xhtml_properly/&quot; rel=&quot;nofollow&quot;&gt;The perils of using XHTML properly&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The dashes won&#8217;t prevent validation, but internal stylesheets that contain double dashes should be wrapped in CDATA sections in XHTML documents sent as application/xhtml+xml. More info here: <a href="http://devedge-temp.mozilla.org/viewsource/2003/xhtml-style-script/index_en.html" rel="nofollow">Properly Using CSS and JavaScript in XHTML Documents</a> and <a href="http://www.456bereastreet.com/archive/200501/the_perils_of_using_xhtml_properly/" rel="nofollow">The perils of using XHTML properly</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron S</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3243</link>
		<dc:creator>Ron S</dc:creator>
		<pubDate>Mon, 23 May 2005 15:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3243</guid>
		<description>Oh come on guys, it&#039;s a nice thing, but is this really new?</description>
		<content:encoded><![CDATA[<p>Oh come on guys, it&#8217;s a nice thing, but is this really new?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3242</link>
		<dc:creator>Kris</dc:creator>
		<pubDate>Wed, 18 May 2005 08:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3242</guid>
		<description>I group elements in sets as well, but I never put generic elements halfway across the document. That is asking for trouble. To go with the cascading nature of CSS instead of against it, one should start with generic elements and work down to more specific instances of elements.</description>
		<content:encoded><![CDATA[<p>I group elements in sets as well, but I never put generic elements halfway across the document. That is asking for trouble. To go with the cascading nature of CSS instead of against it, one should start with generic elements and work down to more specific instances of elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Douglas Bowman</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3241</link>
		<dc:creator>Douglas Bowman</dc:creator>
		<pubDate>Tue, 17 May 2005 18:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3241</guid>
		<description>@Miki: &lt;cite&gt;Note that if you use an embedded style sheet, the multiple hyphens will prevent the page from validating as XHTML.&lt;/cite&gt;

I don&#039;t think this is true. The dashes &lt;strong&gt;should not&lt;/strong&gt; prevent any (X)HTML docuement from validating. To ensure this, I created a &lt;a href=&quot;http://stopdesign.com/examples/css/comment-labels/&quot; rel=&quot;nofollow&quot;&gt;quick example&lt;/a&gt; to &lt;a href=&quot;http://validator.w3.org/check?uri=http://stopdesign.com/examples/css/comment-labels/&quot; rel=&quot;nofollow&quot;&gt;test&lt;/a&gt;.

No errors.</description>
		<content:encoded><![CDATA[<p>@Miki: <cite>Note that if you use an embedded style sheet, the multiple hyphens will prevent the page from validating as XHTML.</cite></p>
<p>I don&#8217;t think this is true. The dashes <strong>should not</strong> prevent any (X)HTML docuement from validating. To ensure this, I created a <a href="http://stopdesign.com/examples/css/comment-labels/" rel="nofollow">quick example</a> to <a href="http://validator.w3.org/check?uri=http://stopdesign.com/examples/css/comment-labels/" rel="nofollow">test</a>.</p>
<p>No errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miki</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3240</link>
		<dc:creator>Miki</dc:creator>
		<pubDate>Tue, 17 May 2005 18:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3240</guid>
		<description>Note that if you use an embedded style sheet, the multiple hyphens will prevent the page from validating as XHTML.

This is something to consider even if you use external stylesheets, you might end up, for various reasons, embedding the external stylesheet, manually or through a script.

Not that I think validating is the key issue, but just so you know.</description>
		<content:encoded><![CDATA[<p>Note that if you use an embedded style sheet, the multiple hyphens will prevent the page from validating as XHTML.</p>
<p>This is something to consider even if you use external stylesheets, you might end up, for various reasons, embedding the external stylesheet, manually or through a script.</p>
<p>Not that I think validating is the key issue, but just so you know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gonzalez</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3239</link>
		<dc:creator>David Gonzalez</dc:creator>
		<pubDate>Tue, 17 May 2005 15:29:57 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3239</guid>
		<description>Great Tip!, I do use flags in the CSS files I do, yet I never organized them, I have to try that! :)</description>
		<content:encoded><![CDATA[<p>Great Tip!, I do use flags in the CSS files I do, yet I never organized them, I have to try that! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Parham Baghestani</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3238</link>
		<dc:creator>Parham Baghestani</dc:creator>
		<pubDate>Mon, 16 May 2005 09:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3238</guid>
		<description>Very Very Good technique</description>
		<content:encoded><![CDATA[<p>Very Very Good technique</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David McDonald</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3237</link>
		<dc:creator>David McDonald</dc:creator>
		<pubDate>Sat, 14 May 2005 16:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3237</guid>
		<description>Nice technique, Doug.

You can also do a similar thing with an undocumented feature in Topstyle, called &lt;a href=&quot;http://nick.typepad.com/topstyletips/2004/11/bookmarks_no_wa.html&quot; rel=&quot;nofollow&quot;&gt;bookmarks&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Nice technique, Doug.</p>
<p>You can also do a similar thing with an undocumented feature in Topstyle, called <a href="http://nick.typepad.com/topstyletips/2004/11/bookmarks_no_wa.html" rel="nofollow">bookmarks</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jekyll</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3236</link>
		<dc:creator>jekyll</dc:creator>
		<pubDate>Fri, 13 May 2005 16:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3236</guid>
		<description>Since I started learning CSS based upon a Blogger template of yours (thanks!), I&#039;ve continued to use your commenting/structure/organizational method, which I not only like but also thought was flagged already. Searching for &quot;/* rde&quot; isn&#039;t good enough for you?! ;)</description>
		<content:encoded><![CDATA[<p>Since I started learning CSS based upon a Blogger template of yours (thanks!), I&#8217;ve continued to use your commenting/structure/organizational method, which I not only like but also thought was flagged already. Searching for &#8220;/* rde&#8221; isn&#8217;t good enough for you?! ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marien</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3235</link>
		<dc:creator>Marien</dc:creator>
		<pubDate>Fri, 13 May 2005 15:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3235</guid>
		<description>If i have a large css file i just put all the rules in one line! This is what works best for me.
So in stead of this:
#nav {
float:left;
width:182px;
border-top:1px solid #911;
}
i  do this:
#nav {float:left;width:182px;border-top:1px solid #911;}

This reduces the number of lines dramaticly.And al your id&#039;s and classes are nicely directly above/under each other...
Topstyle pro has a handy style sweeper which does it automaticly, if you want to do it with it existing css files.
And for the ordering i try to use the ordering of the html file ;-)</description>
		<content:encoded><![CDATA[<p>If i have a large css file i just put all the rules in one line! This is what works best for me.<br />
So in stead of this:<br />
#nav {<br />
float:left;<br />
width:182px;<br />
border-top:1px solid #911;<br />
}<br />
i  do this:<br />
#nav {float:left;width:182px;border-top:1px solid #911;}</p>
<p>This reduces the number of lines dramaticly.And al your id&#8217;s and classes are nicely directly above/under each other&#8230;<br />
Topstyle pro has a handy style sweeper which does it automaticly, if you want to do it with it existing css files.<br />
And for the ordering i try to use the ordering of the html file ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Ho</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3234</link>
		<dc:creator>Andrew Ho</dc:creator>
		<pubDate>Fri, 13 May 2005 10:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3234</guid>
		<description>Ah, so simple.  Thank you for that.  I&#039;ve had this problem for ages, and never found a good way to resolve it.

--  Andy</description>
		<content:encoded><![CDATA[<p>Ah, so simple.  Thank you for that.  I&#8217;ve had this problem for ages, and never found a good way to resolve it.</p>
<p>&#8211;  Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hink</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3233</link>
		<dc:creator>hink</dc:creator>
		<pubDate>Thu, 12 May 2005 01:56:18 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3233</guid>
		<description>&lt;em&gt;Can anyone recommend a good resource which descibes how to begin laying out a stylesheet for a site redesign?&lt;/em&gt;

I would love to help out, L.i.CSS, but I am not sure what you need.  I have always started with the premise that markup comes first, and thus informs the style, while at the same time giving it boundaries.  If you are looking to redesign your website from the ground up, you should probably start by determining what content on your site needs to stay, what parts will change, and then begin to lay out the new structure, using &lt;a href=&quot;http://www.molly.com/2005/02/27/the-meaning-of-semantics/&quot; rel=&quot;nofollow&quot;&gt;semantically correct&lt;/a&gt; and &lt;em&gt;valid&lt;/em&gt; markup. This last bit is key. If you get stuck at this point, and you need a creative nudge, do what every other designer does upon seeing something they like:

&lt;em&gt;View Page Source.&lt;/em&gt; ;)

Here are a couple of resources I would recommend:

&lt;a href=&quot;http://css.maxdesign.com.au/listamatic/&quot; rel=&quot;nofollow&quot;&gt;Listamatic&lt;/a&gt;   to sort out your navigation -- I recall my own  headslapping epiphany when I realized how easily I could do away with the tangle of divs spans and anchors I called  a navbar.

Dave Shea&#039;s &lt;a href=&quot;http://www.mezzoblue.com/css/cribsheet/&quot; rel=&quot;nofollow&quot;&gt;CSS Crib Sheet&lt;/a&gt; is a good checklist of fundamentals.

Good luck, and remember: Validate, Validate, Validate! :)</description>
		<content:encoded><![CDATA[<p><em>Can anyone recommend a good resource which descibes how to begin laying out a stylesheet for a site redesign?</em></p>
<p>I would love to help out, L.i.CSS, but I am not sure what you need.  I have always started with the premise that markup comes first, and thus informs the style, while at the same time giving it boundaries.  If you are looking to redesign your website from the ground up, you should probably start by determining what content on your site needs to stay, what parts will change, and then begin to lay out the new structure, using <a href="http://www.molly.com/2005/02/27/the-meaning-of-semantics/" rel="nofollow">semantically correct</a> and <em>valid</em> markup. This last bit is key. If you get stuck at this point, and you need a creative nudge, do what every other designer does upon seeing something they like:</p>
<p><em>View Page Source.</em> ;)</p>
<p>Here are a couple of resources I would recommend:</p>
<p><a href="http://css.maxdesign.com.au/listamatic/" rel="nofollow">Listamatic</a>   to sort out your navigation &#8212; I recall my own  headslapping epiphany when I realized how easily I could do away with the tangle of divs spans and anchors I called  a navbar.</p>
<p>Dave Shea&#8217;s <a href="http://www.mezzoblue.com/css/cribsheet/" rel="nofollow">CSS Crib Sheet</a> is a good checklist of fundamentals.</p>
<p>Good luck, and remember: Validate, Validate, Validate! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Jones</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3232</link>
		<dc:creator>Stuart Jones</dc:creator>
		<pubDate>Thu, 12 May 2005 00:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3232</guid>
		<description>Can anyone recommend a good resource which descibes how to begin laying out a stylesheet for a site redesign?

I&#039;m used to programming and html, but I can&#039;t seem to get my head around the concepts required to design a site layout based on CSS so that it&#039;s easy to change the look and feel by modifying the style sheet. Do people usually start with a complete style sheet and then tweak it? Does the stylesheet get designed before the HTML or do you build the stylesheet as you code the HTML and see what you need?

It would seem that to really allow the stylesheet to drive the look and feel, that the stylesheet would come first and be in a clearly understood structure, Then the HTML coded to use the appropriate ids/tags?

My site is pretty dated and I want to snaz it up and simplify the HTML :D

Lost in CSS - San Francisco</description>
		<content:encoded><![CDATA[<p>Can anyone recommend a good resource which descibes how to begin laying out a stylesheet for a site redesign?</p>
<p>I&#8217;m used to programming and html, but I can&#8217;t seem to get my head around the concepts required to design a site layout based on CSS so that it&#8217;s easy to change the look and feel by modifying the style sheet. Do people usually start with a complete style sheet and then tweak it? Does the stylesheet get designed before the HTML or do you build the stylesheet as you code the HTML and see what you need?</p>
<p>It would seem that to really allow the stylesheet to drive the look and feel, that the stylesheet would come first and be in a clearly understood structure, Then the HTML coded to use the appropriate ids/tags?</p>
<p>My site is pretty dated and I want to snaz it up and simplify the HTML :D</p>
<p>Lost in CSS &#8211; San Francisco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hink</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3231</link>
		<dc:creator>hink</dc:creator>
		<pubDate>Wed, 11 May 2005 22:47:55 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3231</guid>
		<description>= &lt;em&gt;Another option for organizing your CSS might be to&lt;br /&gt;= group rules by objects. So all your headers are together, &lt;br /&gt;= all your lists are together, all your different image &lt;br /&gt;= classes are together√¢‚Ç¨¬¶&lt;/em&gt;
&lt;br /&gt;&lt;br /&gt;
This seems like a good idea, from an organizational standpoint, but at least in my case, it works against me.
I have noticed over the years that I use a sort of vertical, peripheral look-ahead when skimming style sheets, and a selector like
&lt;br /&gt;
html&gt;body #content div.subcontent:first-child .entry-header h3 {

}
&lt;br /&gt;
completely throws me for a loop.</description>
		<content:encoded><![CDATA[<p>= <em>Another option for organizing your CSS might be to<br />= group rules by objects. So all your headers are together, <br />= all your lists are together, all your different image <br />= classes are together√¢‚Ç¨¬¶</em></p>
<p>This seems like a good idea, from an organizational standpoint, but at least in my case, it works against me.<br />
I have noticed over the years that I use a sort of vertical, peripheral look-ahead when skimming style sheets, and a selector like<br />
<br />
html>body #content div.subcontent:first-child .entry-header h3 {</p>
<p>}<br />
<br />
completely throws me for a loop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shaun O'Connell</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3230</link>
		<dc:creator>Shaun O'Connell</dc:creator>
		<pubDate>Wed, 11 May 2005 17:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3230</guid>
		<description>Hi all,

I&#039;ve adopted a node-tree approach to writing out my CSS.
Chances are, you&#039;re looking at well-indented and easy to read HTML, why not mimic this structure in your CSS?

e.g.:
&lt;code&gt;
&lt;div class=&quot;content&quot;&gt;
&lt;p&gt;Lorem &lt;b&gt;Ipsum&lt;/b&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/code&gt;
could easily be represented in the CSS as:
&lt;code&gt;
div.content {/* rules for this node go here */}
&#160;&#160;div.content p {/* rules for this node go here */}
&#160;&#160;&#160;&#160;div.content p b {/* rules for this node go here */}
&lt;/code&gt;

I create two disctinct sections, a general section and this node-tree section using indenting.  It means you need to keep all your CSS properties in one line so you can truly see the hierarchy of markup nodes, but I&#039;d rather sideways-scroll to get to a property than vertically scroll and potentially not see the node hierarchy.

I reset the indenting in the CSS for important sections such as the &quot;Event Zone&quot; and use lines of comments to break these sections out.

Thoughts?
Shaun</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>I&#8217;ve adopted a node-tree approach to writing out my CSS.<br />
Chances are, you&#8217;re looking at well-indented and easy to read HTML, why not mimic this structure in your CSS?</p>
<p>e.g.:<br />
<code><br />
&lt;div class="content"&gt;<br />
&lt;p&gt;Lorem &lt;b&gt;Ipsum&lt;/b&gt;&lt;/p&gt;<br />
&lt;/div&gt;<br />
</code><br />
could easily be represented in the CSS as:<br />
<code><br />
div.content {/* rules for this node go here */}<br />
&nbsp;&nbsp;div.content p {/* rules for this node go here */}<br />
&nbsp;&nbsp;&nbsp;&nbsp;div.content p b {/* rules for this node go here */}<br />
</code></p>
<p>I create two disctinct sections, a general section and this node-tree section using indenting.  It means you need to keep all your CSS properties in one line so you can truly see the hierarchy of markup nodes, but I&#8217;d rather sideways-scroll to get to a property than vertically scroll and potentially not see the node hierarchy.</p>
<p>I reset the indenting in the CSS for important sections such as the &#8220;Event Zone&#8221; and use lines of comments to break these sections out.</p>
<p>Thoughts?<br />
Shaun</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JT</title>
		<link>http://stopdesign.com/archive/2005/05/03/css-tip-flags.html#comment-3229</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Wed, 11 May 2005 15:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://70.32.90.75/?p=255#comment-3229</guid>
		<description>here are my rules:
- use the cascade to avoid duplicating css rules, eg. declare the base font in the body selector
- classes can often be avoided by using contextual selectors, eg. &quot;div#content p&quot; instead of &quot;p.content&quot;, this makes your HTML more efficient
- use headings in the stylesheet
- if your stylesheet is still too long to be manageable due to the complexity of your site, separate into different stylesheets, eg. main.css, nav.css, lists.css, and use @import to bring them into the main stylesheet.</description>
		<content:encoded><![CDATA[<p>here are my rules:<br />
- use the cascade to avoid duplicating css rules, eg. declare the base font in the body selector<br />
- classes can often be avoided by using contextual selectors, eg. &#8220;div#content p&#8221; instead of &#8220;p.content&#8221;, this makes your HTML more efficient<br />
- use headings in the stylesheet<br />
- if your stylesheet is still too long to be manageable due to the complexity of your site, separate into different stylesheets, eg. main.css, nav.css, lists.css, and use @import to bring them into the main stylesheet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
