<?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>weedygarden.net</title>
	<atom:link href="http://weedygarden.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://weedygarden.net</link>
	<description>My new Web site</description>
	<lastBuildDate>Mon, 14 May 2012 14:51:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>A Case for RESS</title>
		<link>http://weedygarden.net/2012/05/a-case-for-ress/</link>
		<comments>http://weedygarden.net/2012/05/a-case-for-ress/#comments</comments>
		<pubDate>Fri, 11 May 2012 15:13:23 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Notre Dame]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://weedygarden.net/?p=293</guid>
		<description><![CDATA[On the new ND.edu we used a combination of server-side detection, media queries and javascript to determine content. We made the decision that not all content needed to be initially loaded for mobile devices, and instead made it available through (&#8230;)<p><a href="http://weedygarden.net/2012/05/a-case-for-ress/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2012/05/a-case-for-ress/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Hi-res/Retina Display CSS Sprites</title>
		<link>http://weedygarden.net/2012/04/hi-res-retina-display-css-sprites/</link>
		<comments>http://weedygarden.net/2012/04/hi-res-retina-display-css-sprites/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 18:31:45 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://weedygarden.net/?p=278</guid>
		<description><![CDATA[My 2010 article about hi-res background images gave a pretty simple example of how to replace a background image with a 2x version for the fancy hi-res devices that are hitting the markets. In this example, I&#8217;ll show you how (&#8230;)<p><a href="http://weedygarden.net/2012/04/hi-res-retina-display-css-sprites/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2012/04/hi-res-retina-display-css-sprites/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple Feed Caching with PHP</title>
		<link>http://weedygarden.net/2012/04/simple-feed-caching-with-php/</link>
		<comments>http://weedygarden.net/2012/04/simple-feed-caching-with-php/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 23:24:54 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[PHP]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://weedygarden.net/?p=275</guid>
		<description><![CDATA[The latest version of ND.edu makes use of A LOT of external data sources. To make sure the site runs reliably, even in the case of an outage by one of the external feeds, I put together a fairly simple (&#8230;)<p><a href="http://weedygarden.net/2012/04/simple-feed-caching-with-php/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2012/04/simple-feed-caching-with-php/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>iOS 5.1 Position Fixed Bug</title>
		<link>http://weedygarden.net/2012/04/ios5-position-fixed-bug/</link>
		<comments>http://weedygarden.net/2012/04/ios5-position-fixed-bug/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 15:46:07 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Notre Dame]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=257</guid>
		<description><![CDATA[While building the most recent ND.edu, I ran into a little iOS 5.1 bug (at least I think it&#8217;s a bug). One of the features of the site is a menu with &#8220;position:fixed&#8221;. Another feature is we load a number (&#8230;)<p><a href="http://weedygarden.net/2012/04/ios5-position-fixed-bug/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2012/04/ios5-position-fixed-bug/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>CSS3 Multi-column lists</title>
		<link>http://weedygarden.net/2012/04/css3-multi-column-lists/</link>
		<comments>http://weedygarden.net/2012/04/css3-multi-column-lists/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 23:23:05 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=229</guid>
		<description><![CDATA[Over the past couple of months, our group over at the @NDWebTeam has been redesigning the main ND.edu website. What we quickly realized is that ND.edu has a lot of lists. And since part of our design process was to (&#8230;)<p><a href="http://weedygarden.net/2012/04/css3-multi-column-lists/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2012/04/css3-multi-column-lists/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Emergency Notifications: Getting the word out at Notre Dame</title>
		<link>http://weedygarden.net/2011/12/emergency-notifications-getting-the-word-out-at-notre-dame/</link>
		<comments>http://weedygarden.net/2011/12/emergency-notifications-getting-the-word-out-at-notre-dame/#comments</comments>
		<pubDate>Thu, 29 Dec 2011 18:33:15 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Notre Dame]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=207</guid>
		<description><![CDATA[Back in November, Chas Grundy wrote about our emergency procedure for ND.edu. When we implemented this feature for ND.edu, we based the functionality on a single-source file. This gave the ability to update the message on both ND.edu and emergency.nd.edu (&#8230;)<p><a href="http://weedygarden.net/2011/12/emergency-notifications-getting-the-word-out-at-notre-dame/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2011/12/emergency-notifications-getting-the-word-out-at-notre-dame/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HighEdWeb 2011 Slides and Notes</title>
		<link>http://weedygarden.net/2011/11/highedweb-2011-slides-and-notes/</link>
		<comments>http://weedygarden.net/2011/11/highedweb-2011-slides-and-notes/#comments</comments>
		<pubDate>Wed, 02 Nov 2011 01:22:22 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[Conference]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=202</guid>
		<description><![CDATA[Last week I attended HighEdWeb which took place in Austin, TX. This was my first trip to this conference, and perhaps feeling a little over-ambitious, I co-presented a talk with programmer extraordinaire Jeremy Friesen titled &#8220;Feeding the Beast&#8221;, which was (&#8230;)<p><a href="http://weedygarden.net/2011/11/highedweb-2011-slides-and-notes/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2011/11/highedweb-2011-slides-and-notes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accessibility Basics: Access Keys</title>
		<link>http://weedygarden.net/2011/09/accessibility-basics-access-keys/</link>
		<comments>http://weedygarden.net/2011/09/accessibility-basics-access-keys/#comments</comments>
		<pubDate>Fri, 30 Sep 2011 23:55:13 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=197</guid>
		<description><![CDATA[As developers, there&#8217;s a number of things we should be sure to include into each site we build to help with accessibility. One of the most basic of these is access keys. Access Keys Access keys are a very simple (&#8230;)<p><a href="http://weedygarden.net/2011/09/accessibility-basics-access-keys/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2011/09/accessibility-basics-access-keys/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Educating Our Clients About Responsive Web Design</title>
		<link>http://weedygarden.net/2011/08/educating-our-clients-about-responsive-web-design/</link>
		<comments>http://weedygarden.net/2011/08/educating-our-clients-about-responsive-web-design/#comments</comments>
		<pubDate>Sat, 27 Aug 2011 01:52:00 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Notre Dame]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=190</guid>
		<description><![CDATA[A couple days ago in a post-meeting chat I mentioned to my Project Manager Extraordinaire @GtownNick, that I&#8217;d like to extend our development time on custom sites by a couple of hours so we could spend a little more time (&#8230;)<p><a href="http://weedygarden.net/2011/08/educating-our-clients-about-responsive-web-design/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2011/08/educating-our-clients-about-responsive-web-design/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Consuming Remote XML as JSONP</title>
		<link>http://weedygarden.net/2011/01/consuming-remote-xml-as-jsonp/</link>
		<comments>http://weedygarden.net/2011/01/consuming-remote-xml-as-jsonp/#comments</comments>
		<pubDate>Tue, 11 Jan 2011 14:52:23 +0000</pubDate>
		<dc:creator>Erik Runyon</dc:creator>
				<category><![CDATA[AgencyND]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://www.weedygarden.net/?p=163</guid>
		<description><![CDATA[It&#8217;s All About Sharing Content One of the basic tenets behind the internet is sharing data. Initially, that was primarily done with HTML. But with the rise of web applications, sometimes plain HTML just won&#8217;t do. That&#8217;s where API&#8217;s and (&#8230;)<p><a href="http://weedygarden.net/2011/01/consuming-remote-xml-as-jsonp/">Read the rest of this entry &#187;</a></p>]]></description>
		<wfw:commentRss>http://weedygarden.net/2011/01/consuming-remote-xml-as-jsonp/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

