<?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>Red Pill: Shiny New Toy's Blog &#187; css</title>
	<atom:link href="http://shinynewtoy.com/blog/tag/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://shinynewtoy.com/blog</link>
	<description>Causes dizziness and other side effects</description>
	<lastBuildDate>Mon, 19 Jul 2010 16:38:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>CSS Housekeeping</title>
		<link>http://shinynewtoy.com/blog/2008/10/28/css-housekeeping/</link>
		<comments>http://shinynewtoy.com/blog/2008/10/28/css-housekeeping/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 16:45:00 +0000</pubDate>
		<dc:creator>J.J.</dc:creator>
				<category><![CDATA[web]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[firefox]]></category>

		<guid isPermaLink="false">http://shinynewtoy.com/blog/2008/10/28/css-housekeeping/</guid>
		<description><![CDATA[Even the most accomplished web builders are guilty of bloated CSS files.&#160; Any developer or designer that tells you that their CSS file is 100% streamlined is probably fibbing.&#160; Especially if you&#8217;re discussing a CSS file for a site that recently launched.&#160; You wouldn&#8217;t believe how easy it is for a CSS file end up [...]]]></description>
			<content:encoded><![CDATA[<p>Even the most accomplished web builders are guilty of bloated CSS files.&#160; Any developer or designer that tells you that their CSS file is 100% streamlined is probably fibbing.&#160; Especially if you&#8217;re discussing a CSS file for a site that recently launched.&#160; You wouldn&#8217;t believe how easy it is for a CSS file end up with tons of unused classes and selectors during the iterative steps as a project nears completion and launch.</p>
<p>Why does this matter?&#160; The biggest reason would be page load times.&#160; If you have a number of unused id and class definitions in your CSS file, they&#8217;re doing nothing but adding time to your page loads.</p>
<p>So what&#8217;s the best way to keep that CSS file feeling tip-top?&#160; Enter <a href="http://www.sitepoint.com/dustmeselectors/">Sitepoint&#8217;s Dust Me Selectors extension for FIrefox</a>.&#160; What it does is scan your CSS and XHTML and provide you a report of used and unused selectors in your CSS file.&#160; You can set it to run for a single page or your entire site.</p>
<p>I recently ran this on the CSS file for Red Pill and found out (much to my horror) that there were more unused classes and ID&#8217;s than there were selectors in use.&#160; So using the report that the Dust Me Selectors extension, I started going through our CSS file and making changes.&#160; Helpful hint, best to comment out lines in your CSS file carefully.&#160; The report you are given provides you line numbers to go straight to, but if you’re deleting lines from your CSS file, the line numbers will change, and the report becomes less of a utility and more of a treasure map.</p>
]]></content:encoded>
			<wfw:commentRss>http://shinynewtoy.com/blog/2008/10/28/css-housekeeping/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five days, five new features: Adding the superfooter on Day 3</title>
		<link>http://shinynewtoy.com/blog/2008/10/15/five-days-five-new-features-adding-the-superfooter-on-day-3/</link>
		<comments>http://shinynewtoy.com/blog/2008/10/15/five-days-five-new-features-adding-the-superfooter-on-day-3/#comments</comments>
		<pubDate>Wed, 15 Oct 2008 20:27:44 +0000</pubDate>
		<dc:creator>J.J.</dc:creator>
				<category><![CDATA[blogs]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://shinynewtoy.com/blog/2008/10/15/five-days-five-new-features-adding-the-superfooter-on-day-3/</guid>
		<description><![CDATA[Significant changes to Red Pill’s layout today as I added a superfooter to bottom of the blog design. In my opinion, superfooters are an underrated design element.&#160; So many blogs just load up on their sidebars that it ends up taking focus away from the content within a post. On some blogs – tags, recent [...]]]></description>
			<content:encoded><![CDATA[<p>Significant changes to Red Pill’s layout today as I added a superfooter to bottom of the blog design. In my opinion, superfooters are an underrated design element.&#160; So many blogs just load up on their sidebars that it ends up taking focus away from the content within a post. On some blogs – tags, recent comments, and a blogroll just aren’t that imporant to your readers.&#160; But that doesn’t mean those features don’t have a role.&#160; It’s just a question of where do they play that role.&#160; Superfooters help fix address this by providing real estate out of the way of the blog post.</p>
<p>So here’s how I added the 3 column superfooter onto Red Pill.&#160; All it takes us some clever CSS that blends up ID and CLASS selectors.</p>
<p>Here’s how I did it.</p>
<p>First, define a ID selector for the area in which the 3 columns will go</p>
<p>div #superfooter-columns {   <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; margin: 0 auto;    <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; width: 730px;    <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; font-size: 1.1em;&#160;&#160;&#160; <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; width: 730px;    <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; clear:both;    <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; text-align:left;    <br />&#160;&#160;&#160;&#160;&#160;&#160;&#160; z-index:1;    <br />&#160;&#160;&#160; }</p>
<p>&#160;</p>
<p>Then, add a class that will be used on each column</p>
<p>#superfooter-columns .footercol {   <br />&#160;&#160;&#160; float:left;    <br />&#160;&#160;&#160; overflow:hidden;    <br />&#160;&#160;&#160; position:relative;    <br />}</p>
<p>Then, add some css for each column – A, B, and C</p>
<p>#superfooter-columns #footercol_a {   <br />&#160;&#160;&#160; margin: 0;    <br />&#160;&#160;&#160; width:229px;    <br />&#160;&#160;&#160; padding: 10px 2.5px 30px 10px;    <br />} </p>
<p>#superfooter-columns #footercol_b {   <br />&#160;&#160;&#160; margin: 0;    <br />&#160;&#160;&#160; width:229px;    <br />&#160;&#160;&#160; padding: 10px 2.5px 30px 10px;    <br />} </p>
<p>#superfooter-columns #footercol_c {   <br />&#160;&#160;&#160; margin: 0;    <br />&#160;&#160;&#160; width:229px;    <br />&#160;&#160;&#160; padding: 10px 2.5px 30px 10px;    <br />}</p>
<p>&#160;</p>
<p>Adjust the widths and padding appropriately for your site layout.&#160; Once you have that basic skeleton in place you can start filling the divs in your XHTML with the content you want.&#160; I’ll talk about the features I stuck into the superfooter in tomorrow’s post</p>
]]></content:encoded>
			<wfw:commentRss>http://shinynewtoy.com/blog/2008/10/15/five-days-five-new-features-adding-the-superfooter-on-day-3/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
