<?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>BTN Design Notes</title>
	<atom:link href="http://blog.btndesign.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.btndesign.com</link>
	<description>Notes on Web Design and Development</description>
	<lastBuildDate>Thu, 15 Jul 2010 21:02:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Breaking WordPress Posts into Several Pages</title>
		<link>http://blog.btndesign.com/2010/05/breaking-wordpress-posts-into-several-pages/</link>
		<comments>http://blog.btndesign.com/2010/05/breaking-wordpress-posts-into-several-pages/#comments</comments>
		<pubDate>Tue, 18 May 2010 21:16:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.btndesign.com/?p=31</guid>
		<description><![CDATA[There is a lot of information out there on this subject, but people are still having a hard time with it. The basic are simple enough. In the same way that the  &#60;!&#8211;more&#8211;&#62; tag performs it&#8217;s function of creating a page break for the read more excerpt, the  &#60;!&#8211;nextpage&#8211;&#62; tag performs it&#8217;s function of breaking [...]]]></description>
		<wfw:commentRss>http://blog.btndesign.com/2010/05/breaking-wordpress-posts-into-several-pages/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Typography: let me have fonts!</title>
		<link>http://blog.btndesign.com/2010/05/typography/</link>
		<comments>http://blog.btndesign.com/2010/05/typography/#comments</comments>
		<pubDate>Sun, 16 May 2010 19:41:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Typography]]></category>
		<category><![CDATA[@font-face]]></category>
		<category><![CDATA[Cufon]]></category>
		<category><![CDATA[FLIR]]></category>
		<category><![CDATA[Fonts]]></category>
		<category><![CDATA[sIFR]]></category>

		<guid isPermaLink="false">http://btndesign.com/blog/?p=1</guid>
		<description><![CDATA[<p>For years the standard website fonts have been limited to about a dozen common fonts. Even though a web developer can specify any font to be used in a web site, it will only display properly if the viewer has that particular font loaded on their computer. Because of this requirement, web developers have been limited to that short list of commonly available (web-safe) fonts.</p>
<p>But solutions are now available such as <a href="http://www.w3.org/TR/css3-webfonts/#the-font-face-rule" target="_blank">@font-face</a>,  <a href="http://www.mikeindustries.com/blog/sifr/" target="_blank">SIFR</a>, <a href="http://facelift.mawhorter.net/examples/" target="_blank">FLIR</a>, and <a href="http://cufon.shoqolate.com/generate/" target="_blank">Cufón</a> that are changing that.  Each has its pros and cons, but these are all exciting steps that give the web designer much more flexibility and give the end user a richer viewing experience.</p>]]></description>
		<wfw:commentRss>http://blog.btndesign.com/2010/05/typography/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

