<?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>FND's Blag &#187; CSS</title>
	<atom:link href="http://fnd.lewcid.org/blog/archive/tag/css/feed" rel="self" type="application/rss+xml" />
	<link>http://fnd.lewcid.org/blog</link>
	<description>Just Another Personal Wobsite</description>
	<lastBuildDate>Thu, 11 Mar 2010 15:19:16 +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>Upgrade-Proof Customization of WordPress Themes</title>
		<link>http://fnd.lewcid.org/blog/archive/5</link>
		<comments>http://fnd.lewcid.org/blog/archive/5#comments</comments>
		<pubDate>Sun, 06 Jan 2008 17:44:54 +0000</pubDate>
		<dc:creator>FND</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[customization]]></category>
		<category><![CDATA[setup]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://fnd.lewcid.org/blog/archive/5</guid>
		<description><![CDATA[I&#8217;m still pretty much a newbie when it comes to WordPress administration. Nevertheless, I have quickly realized that upgrading a theme can erase any custom styling that had been applied. If a theme doesn&#8217;t support custom styling out of the box, and thus requires modification of the original CSS files, this can easily be retrofitted [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m still pretty much a newbie when it comes to WordPress administration.<br />
Nevertheless, I have quickly realized that upgrading a theme can erase any custom styling that had been applied.</p>
<p>If a theme doesn&#8217;t support custom styling out of the box, and thus requires modification of the original CSS files, this can easily be retrofitted by making use of CSS&#8217; <a href="http://www.w3.org/TR/CSS21/cascade.html#at-import"><code>@import</code></a> rule:</p>
<p>Simply create a new file in the theme&#8217;s folder<sup>[1]</sup> (e.g. <code>wp-content/themes/[name-of-theme]/custom.css</code>) and add your CSS code<sup>[2]</sup>(the file should be available from the WordPress admin panel&#8217;s Theme Editor).<br />
Then add the following line to the top of the theme&#8217;s main style sheet:</p>
<pre>@import "custom.css"</pre>
<p>Later, when upgrading the theme &#8212; after making sure that <code>custom.css</code> is not deleted &#8212; all that&#8217;s required is to re-insert the <code>@import</code> code.</p>
<ol class="footnotes"><li id="footnote_0_5" class="footnote">Initially, I wanted to create a central <code>custom.css</code> in the <code>themes</code> parent folder &#8212; unfortunately, that file wouldn&#8217;t show up in the Theme Editor.</li><li id="footnote_1_5" class="footnote">Don&#8217;t forget about CSS <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">specificity</a>; from my experiences, this is often the culprit when a modification doesn&#8217;t seem to take effect.</li></ol>]]></content:encoded>
			<wfw:commentRss>http://fnd.lewcid.org/blog/archive/5/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
