<?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"
	>
<channel>
	<title>Comments on: Using The WordPress Sandbox and The Blueprint CSS Framework Together</title>
	<atom:link href="http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/</link>
	<description>J. Michael Wender - Graphic Artist, Web Developer, Coder</description>
	<pubDate>Fri, 04 Jul 2008 13:30:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-1213</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 01 Jul 2008 13:18:42 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-1213</guid>
		<description>@James Gross - Glad you found this tutorial useful. Regarding your question about using a custom CSS file that can override the 4 base css files:

As an advanced step: I  generally follow this process:
&lt;ol&gt;
&lt;li&gt;The file &lt;em&gt;2c-l.css&lt;/em&gt; controls the layout for your Sandbox theme. By default, style.css in Sandbox calls this file via &lt;em&gt;@import&lt;/em&gt;. I generally start with one of the Sandbox layouts by opening it, copying the CSS and creating a layout section in style.css. Then I can delete the &lt;em&gt;@import&lt;/em&gt; for the layout and remove the /sandbox-layouts/ folder from my theme.&lt;/li&gt;
&lt;li&gt;Since this tutorial has you importing &lt;em&gt;screen.css&lt;/em&gt; at the top of &lt;em&gt;style.css&lt;/em&gt;, you can override any declaration in &lt;em&gt;screen.css&lt;/em&gt; by simply redeclaring the CSS you want to override (keep in mind you can use &lt;em&gt;!important&lt;/em&gt; at the end of specific attributes in your CSS declarations to force an override).&lt;/li&gt;
&lt;/ol&gt;

Finally, if you want to get rid of &lt;em&gt;screen.css&lt;/em&gt; all together, you can just copy and paste the CSS from that file directly into &lt;em&gt;style.css&lt;/em&gt; (i.e. the default stylesheet used by all WP themes). However, I wouldn't recommend doing that as the reason why I have written the tutorial this way is to allow you the option of upgrading Blueprint should a new version be released in the future.</description>
		<content:encoded><![CDATA[<p>@James Gross - Glad you found this tutorial useful. Regarding your question about using a custom CSS file that can override the 4 base css files:</p>
<p>As an advanced step: I  generally follow this process:</p>
<ol>
<li>The file <em>2c-l.css</em> controls the layout for your Sandbox theme. By default, style.css in Sandbox calls this file via <em>@import</em>. I generally start with one of the Sandbox layouts by opening it, copying the CSS and creating a layout section in style.css. Then I can delete the <em>@import</em> for the layout and remove the /sandbox-layouts/ folder from my theme.</li>
<li>Since this tutorial has you importing <em>screen.css</em> at the top of <em>style.css</em>, you can override any declaration in <em>screen.css</em> by simply redeclaring the CSS you want to override (keep in mind you can use <em>!important</em> at the end of specific attributes in your CSS declarations to force an override).</li>
</ol>
<p>Finally, if you want to get rid of <em>screen.css</em> all together, you can just copy and paste the CSS from that file directly into <em>style.css</em> (i.e. the default stylesheet used by all WP themes). However, I wouldn&#8217;t recommend doing that as the reason why I have written the tutorial this way is to allow you the option of upgrading Blueprint should a new version be released in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Gross</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-1207</link>
		<dc:creator>James Gross</dc:creator>
		<pubDate>Mon, 30 Jun 2008 05:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-1207</guid>
		<description>Thank you for the sensible combination of these two great frameworks. I followed your directions and yes it seems to have worked. 

Just a note to add to the information here, my css editor, Skybound Stylizer, picked up 4 css sheets for editing. They are print.css, style.css, screen.css, and 2c-l.css. 

Question: Is there any mechanism to just work on a custom.css file that can overide these 4 base css files? (I guess I could always upload and original, if my css changes get to far off track.)

Thanks, James</description>
		<content:encoded><![CDATA[<p>Thank you for the sensible combination of these two great frameworks. I followed your directions and yes it seems to have worked. </p>
<p>Just a note to add to the information here, my css editor, Skybound Stylizer, picked up 4 css sheets for editing. They are print.css, style.css, screen.css, and 2c-l.css. </p>
<p>Question: Is there any mechanism to just work on a custom.css file that can overide these 4 base css files? (I guess I could always upload and original, if my css changes get to far off track.)</p>
<p>Thanks, James</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-809</link>
		<dc:creator>james</dc:creator>
		<pubDate>Sat, 03 May 2008 18:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-809</guid>
		<description>cool, the site looks good, i will post here when i get my new project up.</description>
		<content:encoded><![CDATA[<p>cool, the site looks good, i will post here when i get my new project up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-807</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 03 May 2008 12:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-807</guid>
		<description>@james - BTW: The template I'm running right now is an example of the very technique that I describe in this tutorial. ;)</description>
		<content:encoded><![CDATA[<p>@james - BTW: The template I&#8217;m running right now is an example of the very technique that I describe in this tutorial. <img src='http://michaelwender.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-806</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 03 May 2008 12:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-806</guid>
		<description>@ james - For the second snippet in the post, there should be two dashes to indicate the closing of the html conditional statement. I have corrected that error.

Also, regarding the single quotes in the second snippet: In every instance where there is a single quote, it should be the standard single quote character found to the right of the semicolon key on a QWERTY keyboard. However, after a thorough investigation, I found that WordPress or the Syntax Highlighting plugin was translating the second set of single quotes into "closing curly single quotes." I even checked the database and found that I have the data in there correctly; however, as it gets rendered, the quotes get incorrectly translated somewhere.

SO, to fix this I used double quotes in the call to bloginfo(); -- now the code is syntacticly correct although not syntactically preferred (i.e. it would be preferred to use single quotes because there is no need to parse the text found in the function call).

Finally, I've added a third snippet which shows what your body tag should  look like after adding the "container" tag.

Cheers!</description>
		<content:encoded><![CDATA[<p>@ james - For the second snippet in the post, there should be two dashes to indicate the closing of the html conditional statement. I have corrected that error.</p>
<p>Also, regarding the single quotes in the second snippet: In every instance where there is a single quote, it should be the standard single quote character found to the right of the semicolon key on a QWERTY keyboard. However, after a thorough investigation, I found that WordPress or the Syntax Highlighting plugin was translating the second set of single quotes into &#8220;closing curly single quotes.&#8221; I even checked the database and found that I have the data in there correctly; however, as it gets rendered, the quotes get incorrectly translated somewhere.</p>
<p>SO, to fix this I used double quotes in the call to bloginfo(); &#8212; now the code is syntacticly correct although not syntactically preferred (i.e. it would be preferred to use single quotes because there is no need to parse the text found in the function call).</p>
<p>Finally, I&#8217;ve added a third snippet which shows what your body tag should  look like after adding the &#8220;container&#8221; tag.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-805</link>
		<dc:creator>james</dc:creator>
		<pubDate>Sat, 03 May 2008 07:27:49 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-805</guid>
		<description>gr. the comment engine snipped the last bit of the code. email me if it isnt clear what needs to be changed. thanks!</description>
		<content:encoded><![CDATA[<p>gr. the comment engine snipped the last bit of the code. email me if it isnt clear what needs to be changed. thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-804</link>
		<dc:creator>james</dc:creator>
		<pubDate>Sat, 03 May 2008 07:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-804</guid>
		<description>I am just getting started on this, and i am glad to find your snippets of code here, but i think you used an emdash instead of two hyphens in the  and, i dont know if it matters, but you used ’ instead of ' in ’template_directory’. so really the code should read:

&#60;link rel="stylesheet" href="/blueprint/print.css" type="text/css" media="print" /&#62;

&lt;!--[if IE]&#62;&#60;link rel="stylesheet" href="/blueprint/ie.css" type="text/css" media="screen, projection" /&#62;&#60;![endif]--&gt;

And just for the sake of clarity, my body tag now looks like:

&#60;body class=" container"&#62;

thanks for the good work, seeing the code on here gave me the guts to try it out myself. please post more as you integrate these two very cool tools.</description>
		<content:encoded><![CDATA[<p>I am just getting started on this, and i am glad to find your snippets of code here, but i think you used an emdash instead of two hyphens in the  and, i dont know if it matters, but you used ’ instead of &#8216; in ’template_directory’. so really the code should read:</p>
<p>&lt;link rel=&#8221;stylesheet&#8221; href=&#8221;/blueprint/print.css&#8221; type=&#8221;text/css&#8221; media=&#8221;print&#8221; /&gt;</p>
<p><!--[if IE]&gt;&lt;link rel="stylesheet" href="/blueprint/ie.css" type="text/css" media="screen, projection" /&gt;&lt;![endif]--></p>
<p>And just for the sake of clarity, my body tag now looks like:</p>
<p>&lt;body class=&#8221; container&#8221;&gt;</p>
<p>thanks for the good work, seeing the code on here gave me the guts to try it out myself. please post more as you integrate these two very cool tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-795</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 28 Apr 2008 12:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-795</guid>
		<description>Adam, thanks for commenting. Furthermore, I'm just happy that one of my commenters has used the word "reticent" in his comment. ;)</description>
		<content:encoded><![CDATA[<p>Adam, thanks for commenting. Furthermore, I&#8217;m just happy that one of my commenters has used the word &#8220;reticent&#8221; in his comment. <img src='http://michaelwender.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Kayce</title>
		<link>http://michaelwender.com/2008/04/15/using-wordpress-sanbox-and-blueprint-css/#comment-787</link>
		<dc:creator>Adam Kayce</dc:creator>
		<pubDate>Fri, 25 Apr 2008 18:51:06 +0000</pubDate>
		<guid isPermaLink="false">http://michaelwender.com/?p=681#comment-787</guid>
		<description>Interesting; I've been reticent to dive into the Sandbox or Blueprint... and yet, there's a keen method to this madness.

I've been investigating various frameworks, and these two seem to be champs (one of my own sites uses The Morning After, too, so I'm semi-familiar w/ Blueprint). Putting the two together just may be the best of both worlds... if, I can figure out all the classes and stuff!

Breathe... patience... and give it time. That's what I'm telling myself. Good stuff, though. Thanks for the merge.</description>
		<content:encoded><![CDATA[<p>Interesting; I&#8217;ve been reticent to dive into the Sandbox or Blueprint&#8230; and yet, there&#8217;s a keen method to this madness.</p>
<p>I&#8217;ve been investigating various frameworks, and these two seem to be champs (one of my own sites uses The Morning After, too, so I&#8217;m semi-familiar w/ Blueprint). Putting the two together just may be the best of both worlds&#8230; if, I can figure out all the classes and stuff!</p>
<p>Breathe&#8230; patience&#8230; and give it time. That&#8217;s what I&#8217;m telling myself. Good stuff, though. Thanks for the merge.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
