<?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>JstnRyan &#187; Web Dev</title>
	<atom:link href="http://jstnryan.com/category/webdev/feed/" rel="self" type="application/rss+xml" />
	<link>http://jstnryan.com</link>
	<description>Web Coder, Techno DJ, rave lighting designer, dish washer, and otherwise &#039;jack of all trades&#039;</description>
	<lastBuildDate>Thu, 06 Oct 2011 09:38:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Use META tags delicately</title>
		<link>http://jstnryan.com/use-meta-tags-delicately/</link>
		<comments>http://jstnryan.com/use-meta-tags-delicately/#comments</comments>
		<pubDate>Thu, 14 Oct 2010 10:14:50 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=521</guid>
		<description><![CDATA[Twitter user benschwarz just announced an attractive new facelift for the W3C HTML5 spec for authors. The new design uses em units which (on my screen) renders to a body width of about 640 pixels wide. Save for a naughty fieldset which strays outside of its yard, everything fits within this tight column, making for [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/use-meta-tags-delicately/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preserving HTTP/HTTPS in .htaccess RewriteRules</title>
		<link>http://jstnryan.com/preserving-http-https-in-htaccess-rewriterules/</link>
		<comments>http://jstnryan.com/preserving-http-https-in-htaccess-rewriterules/#comments</comments>
		<pubDate>Thu, 26 Aug 2010 04:30:52 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=446</guid>
		<description><![CDATA[When performing URL rewrites with .htaccess files, if your resources are available from both an unsecured (http://) and a secured (https://) connection, your first instinct might be to write a rule for each. For example, this snippet will remove the leading "www." from the domain name over both HTTP and HTTPS: RewriteCond %{HTTPS} !=on RewriteCond [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/preserving-http-https-in-htaccess-rewriterules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Developers Are Fucking Hypocrites</title>
		<link>http://jstnryan.com/web-developers-are-fucking-hypocrites/</link>
		<comments>http://jstnryan.com/web-developers-are-fucking-hypocrites/#comments</comments>
		<pubDate>Thu, 24 Jun 2010 11:15:52 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=387</guid>
		<description><![CDATA[This post, and the related CSS code to target the iPhone 4&#8217;s browser, came through my Twitter stream multiple times today. Thomas Maier writes about targeting the Mobile Safari browser with CSS media queries on his blog. I think the things Apple are doing, and the advances they are making in the mobile phone and [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/web-developers-are-fucking-hypocrites/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Why this webpage is shouting at me!!</title>
		<link>http://jstnryan.com/why-this-webpage-is-shouting-at-me/</link>
		<comments>http://jstnryan.com/why-this-webpage-is-shouting-at-me/#comments</comments>
		<pubDate>Sun, 20 Jun 2010 11:07:14 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=380</guid>
		<description><![CDATA[Buzzwords and 'buzz-concepts' travel through the web development community like the plague. After using the table element for page layout became faux pax everybody was so quick to jump on the bandwagon that there&#8217;s no arguing the point anymore &#8212; even in the off-case that it might just be appropriate. It&#8217;s such a widespread &#8217;social [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/why-this-webpage-is-shouting-at-me/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Dealing with legacy browsers &amp; The irony of the &#8216;Universal Internet Explorer 6 CSS&#8217;</title>
		<link>http://jstnryan.com/dealing-with-legacy-browsers-and-the-irony-of-the-universal-internet-explorer-6-css/</link>
		<comments>http://jstnryan.com/dealing-with-legacy-browsers-and-the-irony-of-the-universal-internet-explorer-6-css/#comments</comments>
		<pubDate>Sun, 13 Dec 2009 11:52:29 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=355</guid>
		<description><![CDATA[<p>A long winded article with an appropriately long winded title about my search for an appropriate method to easily style for legacy browsers, and the joy and disappointment I felt when I finally found one.</p>

<p>I cover everything from my distaste for add-ons like IE6 Update, to how I think Andy Clarke forgot a crucial step in creating his 'Universal Internet Explorer 6 CSS' base style sheet (however fantastic it may be).</p>]]></description>
		<wfw:commentRss>http://jstnryan.com/dealing-with-legacy-browsers-and-the-irony-of-the-universal-internet-explorer-6-css/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A[nother] brief argument against sIFR</title>
		<link>http://jstnryan.com/another-brief-argument-against-sifr/</link>
		<comments>http://jstnryan.com/another-brief-argument-against-sifr/#comments</comments>
		<pubDate>Sat, 12 Dec 2009 09:55:45 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=344</guid>
		<description><![CDATA[In my previous rant about sIFR I discussed how regressive (and ironic?) I think it is that in an attempt to further rich type use on the web, designers are utilizing a technique which (in certain circumstances) destroys the very experience they are trying to enhance. Not only did I find other sources describing the [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/another-brief-argument-against-sifr/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Custom image suffixes in WordPress</title>
		<link>http://jstnryan.com/custom-image-suffixes-in-wordpress/</link>
		<comments>http://jstnryan.com/custom-image-suffixes-in-wordpress/#comments</comments>
		<pubDate>Sat, 28 Nov 2009 11:22:23 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=312</guid>
		<description><![CDATA[<p>When uploading an image to the Media Gallery, WordPress automatically creates a large, medium, and thumbnail sized version of that image depending on metrics which can be specified in WordPress' 'Settings > Media' screen. Unfortunately the filenames of the resulting images include both the width and height of the image as a suffix, making it difficult to predict the resultant file name.</p>

<p>With a little hacking of the WordPress core, it is possible to specify definite suffixes for these resized images, making it much easier to reference them later, especially without having to search the Media Gallery.</p>]]></description>
		<wfw:commentRss>http://jstnryan.com/custom-image-suffixes-in-wordpress/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Farewell old friend, GeoCities</title>
		<link>http://jstnryan.com/farewell-old-friend-geocities/</link>
		<comments>http://jstnryan.com/farewell-old-friend-geocities/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 07:00:55 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Nonsense]]></category>
		<category><![CDATA[Personal]]></category>
		<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=290</guid>
		<description><![CDATA[<p>GeoCities is scheduled for lethal injection today, and despite not having used it for over a decade or more, I'm still sad to see it go.</p>

<p>Even though GeoCities' modus operandi was making it easy to have your own web page, it still required <em>some</em> skill &#8212; especially if you wanted to make it look good. (By no means did most of the pages on GeoCities look good.) Additionally, web technologies of the time were much simpler, much easier to get a hold of. To craft a nice page, you needed only to have something to say, and to know a bit about HTML.</p>

<p>Nowadays the barrier for entry to get content on the Internet is so minimal it's a non-issue. With a few clicks a person could install a CMS with pre-built templates, or use a WYSIWYG HTML editor that automatically spits out the proper markup. Despite that, most people's creations still don't look good. Along with these advancements in publishing aides, web technologies have also advanced. In fact they've reproduced, and advanced to the point where it is now a daunting (if not impossible) task to keep up with them all.</p>

<p>For a lot of people, GeoCities was reminiscent of 'the good old days,' and I'm no exception. Without GeoCities to help kick start my interest in web publishing, I would probably not have pursued it as far as I have.</p>

<p>To remember, and say thanks, this is my tribute to GeoCities.</p>]]></description>
		<wfw:commentRss>http://jstnryan.com/farewell-old-friend-geocities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nesting rules in CSS style sheets</title>
		<link>http://jstnryan.com/nesting-rules-in-css-style-sheets/</link>
		<comments>http://jstnryan.com/nesting-rules-in-css-style-sheets/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 13:41:55 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=282</guid>
		<description><![CDATA[<p>I really like complaining about CSS.</p>

<p>On the one hand, CSS is an amazingly simple way to separate style from content, which has a really shallow (rather, relatively shallow) learning curve. On the other hand, it is my opinion that the way in which CSS directives are structured is terrible.</p>

<p>In my quest to create overly verbose style sheets, I can't help but to dream up better ways of formatting CSS rules. Taking cues from other, similarly structured programming languages I think CSS should be revised to allow for more advanced rule nesting.</p>]]></description>
		<wfw:commentRss>http://jstnryan.com/nesting-rules-in-css-style-sheets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Is Google getting creative?</title>
		<link>http://jstnryan.com/is-google-getting-creative/</link>
		<comments>http://jstnryan.com/is-google-getting-creative/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 09:29:51 +0000</pubDate>
		<dc:creator>Justin Ryan</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Web Dev]]></category>

		<guid isPermaLink="false">http://jstnryan.com/?p=273</guid>
		<description><![CDATA[Google&#8217;s homepage has always been a model of minimalist design. Even in earlier revisions, the Google homepage included only the most basic of elements &#8212; the logo, search query input box, the search and "Feel Lucky" buttons, and perhaps a few links. Occasionally elements would come and go, but the interface retained its simplicity. Google [...]]]></description>
		<wfw:commentRss>http://jstnryan.com/is-google-getting-creative/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

