<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Chase Web Consulting &#187; Tools</title> <atom:link href="http://cdchase.com/category/tools/feed/" rel="self" type="application/rss+xml" /><link>http://cdchase.com</link> <description>Dan Chase helps businesses grow by advising them how to best integrate the web with their daily operations.</description> <lastBuildDate>Sun, 05 Sep 2010 18:57:44 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <item><title>CSS Editing Trials, Tribulations &amp; Tools</title><link>http://cdchase.com/2007/04/24/css-editing-trials-tribulations-tools/</link> <comments>http://cdchase.com/2007/04/24/css-editing-trials-tribulations-tools/#comments</comments> <pubDate>Tue, 24 Apr 2007 11:33:10 +0000</pubDate> <dc:creator>Dan</dc:creator> <category><![CDATA[Tools]]></category> <guid
isPermaLink="false">http://blog.cdchase.com/2007/04/24/css-editing-trials-tribulations-tools/</guid> <description><![CDATA[While working on the new template this weekend, I was having problems with getting the sidebar to do what I asked. Come to find out, there was another section of the CSS file that contained additional information for the #sidebar style. Argh! While I generally liked the concept of separating the different sections of the [...]]]></description> <content:encoded><![CDATA[<p></p><p>While working on the new template this weekend, I was having problems with getting the sidebar to do what I asked. Come to find out, there was another section of the CSS file that contained additional information for the #sidebar style. Argh! While I generally liked the concept of separating the different sections of the stock WordPress CSS file for editing, I&#8217;ve decided after this, that I really <strong>don&#8217;t</strong> like it. My general policy is to keep related items close together as possible, with all the applicable sections in one definition when I can.</p><p>When I complete the design, I am planning on removing all unused definitions for clarity. I thought the idea of starting with the base CSS was a good idea, but, I&#8217;ve clearly had second thoughts on that! It&#8217;s probably a case where if you wrote it yourself, it might make sense, because you would know it well. However, when using someone else&#8217;s code as a starting point, it doesn&#8217;t work as well. We all have our own ways of doing things, no one way is right and the other wrong&#8211;just different.</p><p>While I&#8217;m here, I wanted to point you to one of my favorite tools for editing &amp; validating CSS: <a
href="http://www.topstyle4.com/">TopStyle by Stefan van As</a>, formerly BradSoft &#038; NewsGator Technologies. Sorry, it&#8217;s for Windows users only. The y are also the creators of the NewsGator &amp; FeedDemon news readers &amp; RSS aggregators.</p> ]]></content:encoded> <wfw:commentRss>http://cdchase.com/2007/04/24/css-editing-trials-tribulations-tools/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
