<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Code Poet &#187; Mobile</title>
	<atom:link href="http://build.codepoet.com/category/mobile/feed/" rel="self" type="application/rss+xml" />
	<link>http://build.codepoet.com</link>
	<description>Because you make things with WordPress</description>
	<lastBuildDate>Thu, 23 May 2013 15:04:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='build.codepoet.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Code Poet &#187; Mobile</title>
		<link>http://build.codepoet.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://build.codepoet.com/osd.xml" title="Code Poet" />
	<atom:link rel='hub' href='http://build.codepoet.com/?pushpress=hub'/>
		<item>
		<title>Twitter Bootstrap Framework</title>
		<link>http://build.codepoet.com/2013/03/05/twitter-bootstrap-framework/</link>
		<comments>http://build.codepoet.com/2013/03/05/twitter-bootstrap-framework/#comments</comments>
		<pubDate>Tue, 05 Mar 2013 15:51:02 +0000</pubDate>
		<dc:creator>Michael Pick</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Theme Dev]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[Twitter bootstrap]]></category>
		<category><![CDATA[WP Arena]]></category>

		<guid isPermaLink="false">http://build.codepoet.com/?p=1952</guid>
		<description><![CDATA[Pull your development up by WP Arena's WordPress-flavored Twitter bootstrap framework.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=1952&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
				<content:encoded><![CDATA[<p class="intro">Sometimes just getting started can be the toughest part of putting a theme together. And sometimes getting started means getting a head start. There&#8217;s no shame in using a framework to speed those early stages along, and there are a bunch of helpful <a href="http://twitter.github.com/bootstrap/">Twitter Bootstrap</a>-flavored frameworks for WordPress that can help get things underway when you&#8217;re stuck staring at a blank text file.</p>
<p><strong>Quick Overview</strong><br />
In <a href="http://wparena.com/how-to/twitter-bootstrap-frameworks-to-develop-a-wordpress-themes/">this roundup of the best and brightest offerings</a> for WordPress designer-developers looking to put <a href="http://twitter.github.com/bootstrap/">Twitter Bootstrap</a> to use, WP Arena supplies plentiful options and alternatives for you to check out if you could use a head start on the front end of your beautiful WP-powered website.</p>
<p><small>Image based on &#8220;<a href="http://www.flickr.com/photos/elwillo/6969277459/">These boots are made for walking Project 365(4) Day 28</a>&#8221; by Keith Williamson, <a href="http://creativecommons.org/licenses/by/2.0/deed.en_GB">CC-BY-2.0</a>.</small></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/newcodepoet.wordpress.com/1952/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/newcodepoet.wordpress.com/1952/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=1952&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://build.codepoet.com/2013/03/05/twitter-bootstrap-framework/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>43.062096 141.354376</georss:point>
		<geo:lat>43.062096</geo:lat>
		<geo:long>141.354376</geo:long>
		<media:thumbnail url="http://newcodepoet.files.wordpress.com/2013/02/twitterbootstrap.jpg?w=150" />
		<media:content url="http://newcodepoet.files.wordpress.com/2013/02/twitterbootstrap.jpg?w=150" medium="image">
			<media:title type="html">TwitterBootstrap</media:title>
		</media:content>

		<media:content url="http://2.gravatar.com/avatar/5d7ec9ab95a1269c34a1c5871fb00ade?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">Michael Pick</media:title>
		</media:content>
	</item>
		<item>
		<title>Lindsay Watt Interview</title>
		<link>http://build.codepoet.com/2013/02/28/lindsay-watt-interview/</link>
		<comments>http://build.codepoet.com/2013/02/28/lindsay-watt-interview/#comments</comments>
		<pubDate>Thu, 28 Feb 2013 14:24:27 +0000</pubDate>
		<dc:creator>Krista</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[Lindsay Watt]]></category>
		<category><![CDATA[locations]]></category>
		<category><![CDATA[Placeling]]></category>
		<category><![CDATA[plugins]]></category>

		<guid isPermaLink="false">http://build.codepoet.com/?p=2010</guid>
		<description><![CDATA[Meet Lindsay Watt, co-founder of Placeling -- a location-based WordPress plugin.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=2010&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
				<content:encoded><![CDATA[<p class="intro">Meet <a href="https://www.placeling.com/users/lindsayrgwatt">Lindsay Watt</a>, WordPress developer extraordinaire and co-founder of <a href="https://www.placeling.com/">Placeling</a> &#8212; a plugin that allows bloggers to add location-based data to their sites.</p>
<h3>How did you get into developing with and for WordPress?</h3>
<p>I&#8217;ve been a WordPress user for almost five years. One of the most common things I&#8217;ve found myself writing about was places I&#8217;d visited (My first post was actually about an awkwardly <a href="http://lindsayrgwatt.com/blog/2008/06/err-lingus/">incorrect map on an in-flight magazine</a>). I don&#8217;t think there&#8217;s any better way than blogging to permanently capture the great places we visit and experiences we have.</p>
<h3>What is Placeling?</h3>
<p>About 18 months ago I co-founded <a href="https://www.placeling.com/">Placeling</a>, where we were originally focused on helping people create social city guides. Local WordPress bloggers probably know more about cities than anyone else, so we wanted to build a plugin to bring Placeling&#8217;s location capabilities to WordPress. That was the first time that I said &#8220;it&#8217;s time to move beyond being a WordPress blogger and become a developer.&#8221; And since then we&#8217;ve just kept on shipping.</p>
<p>At Placeling we&#8217;re now focused on extending WordPress into a location-based publishing platform. That means letting people see nearby places mentioned on your site and making it friendly on mobile. WordPress stared as a blogging tool, became a CMS, and it&#8217;s evolving into an app platform. If it&#8217;s going to do mobile apps properly, it&#8217;s going to need to take advantage of location. Let&#8217;s say that you&#8217;re a developer and your client is a small coffee chain. They want a store finder. And they want it to be mobile: people should look on the site on their phone and be able to see nearby stores. Traditionally, this was challenging to do (you need to geocode each place, put them on a map, get the user&#8217;s current location and then do a nearby search), but Placeling makes it effortless.</p>
<p>Now, you just create a WordPress post or page for every location and tag them with a location using Placeling&#8217;s free plugin. Placeling automatically creates a map for you and each post will be a pin on that map. Plus, it&#8217;s mobile friendly; a &#8220;nearby&#8221; button will show readers the nearest location.</p>
<p>No short codes. No custom Google Maps keys or queries. You can literally do this in 5 minutes &#8211; in fact, <a href="https://www.youtube.com/watch?v=70AVzOMNw_Q">here&#8217;s a video</a> showing how.</p>
<p>Another use case is for local bloggers &#8212; foodies, fashionistas, mom bloggers, travellers &amp; locals. I live in Vancouver, BC, Canada and there are a ton of great food writers. However, there&#8217;s no easy way for me to say &#8220;what places do my favorite bloggers recommend in this neighborhood?&#8221; Placeling solves this.</p>
<p>Our plugin lets these bloggers automatically create a map of all the places they recommend and I can see their nearby recommendations on my phone. I can literally sit in the restaurant and easily find out which dishes they recommend. (Here&#8217;s an <a href="http://lindsayrgwatt.com/blog/placeling-map/">example on my personal site</a>.)</p>
<p>We&#8217;re also experimenting with how we can send local bloggers more traffic. We&#8217;ve a new site called <a href="http://www.thelocalread.com">The Local Read</a> where we take links to posts that come in via the plugin and aggregate them into a weekly email for people who live nearby (you can opt out and we don&#8217;t store your posts on our servers). The goal is to get great local blog content in front of more people and get more traffic to local bloggers.</p>
<h3>What&#8217;s best piece of advice?</h3>
<p>My single best piece of advice for WordPress developers is &#8220;wow your early users.&#8221; We&#8217;ve spent a lot of time reaching out to our early adopters, literally emailing every single one of them to ask what they&#8217;d like. We&#8217;ve also pushed plugin updates in a matter of hours when someone has found a bug. As a result we&#8217;ve a number of users who are evangelists for us and recommend us to their colleagues.</p>
<h3>You&#8217;ve requested a lot of feedback from your users &#8212; what have you learned from that feedback about how to improve Placeling &#8212; improvements that otherwise may not have been discovered?</h3>
<p>Asking our users for feedback has helped us really understand what&#8217;s important to them and why. For example, Placeling puts a footer at the bottom of your posts to show what location they correspond to. Frankly, the footer was a bit of an afterthought for us: We were focused on how to actually get the plugin to link your post to a map and pin it. We quickly got a lot of feedback from our users about what the footer looked like and what they wanted it to do. We hadn&#8217;t thought too much about the footer at all &#8212; and our users quickly let us know what we needed to know. (And we were able to quickly push an update that made them happy.) There are no shortage of things you can do at a startup; if you listen to your users you get a great signal to help you prioritize.</p>
<h3>What&#8217;s in store for Placeling? Can you give a sneak peak into any new features you&#8217;re working on? </h3>
<p>What&#8217;s next for us is figuring out more ways to drive traffic to local bloggers. For example, here in Vancouver we have bloggers who write about history, urban issues, food, shopping and what to do with your family. Why can&#8217;t these people be my guides to the city? When I want something to do, why can&#8217;t all their great posts come together to suggest an itinerary for me? When I visit another city, why don&#8217;t the best blog posts about where to go immediately appear?</p>
<p>I guarantee that there&#8217;s a WordPress blogger out there who has written about dozens of places that you would love to visit &#8212; dozens even in your own home town &#8212; but you&#8217;ve no way of discovering them or having them appear as you&#8217;re on the go.</p>
<p>These are big problems and we&#8217;re working on them. 2013&#8242;s going to be a great year!</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/newcodepoet.wordpress.com/2010/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/newcodepoet.wordpress.com/2010/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=2010&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://build.codepoet.com/2013/02/28/lindsay-watt-interview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>0.000000 0.000000</georss:point>
		<geo:lat>0.000000</geo:lat>
		<geo:long>0.000000</geo:long>
		<media:thumbnail url="http://newcodepoet.files.wordpress.com/2013/02/lindsaywatt.png?w=150" />
		<media:content url="http://newcodepoet.files.wordpress.com/2013/02/lindsaywatt.png?w=150" medium="image">
			<media:title type="html">lindsaywatt</media:title>
		</media:content>

		<media:content url="http://0.gravatar.com/avatar/6eb9aa374b5b9b87bbfc09c2cf876162?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">kristastevens</media:title>
		</media:content>
	</item>
		<item>
		<title>Rolling up our responsive sleeves</title>
		<link>http://build.codepoet.com/2012/12/20/responsive-sleeves/</link>
		<comments>http://build.codepoet.com/2012/12/20/responsive-sleeves/#comments</comments>
		<pubDate>Thu, 20 Dec 2012 17:12:47 +0000</pubDate>
		<dc:creator>Krista</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Ethan Marcotte]]></category>
		<category><![CDATA[fluid grids]]></category>
		<category><![CDATA[media queries]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[responsive web design]]></category>

		<guid isPermaLink="false">http://build.codepoet.com/?p=1643</guid>
		<description><![CDATA[Watch Rolling up Our Responsive Sleeves -- a video of Ethan Marcotte's June 2012 AEA presentation. <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=1643&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
				<content:encoded><![CDATA[<p class="intro">We can all agree that responsive web design is the most important advance in designing for the web since we all abandoned tables in favor of CSS for layout. Now, here&#8217;s a chance to take your responsive chops to the next level. Pro tip: you might also be interested in our free ebook, <a href="http://build.codepoet.com/2012/05/11/wordpress-meet-responsive-design/">WordPress Meet Responsive Web Design</a>.</p>
<p><strong>Quick Overview</strong><br />
<a href="http://aneventapart.com/news/post/marcotte2012RWD">In this video of his An Event Apart presentation</a>, recorded on June 18th, 2012, Ethan covers how to use fluid grids and media queries to handle trickier elements of designing responsively, including advertising, complex layouts, deep navigation patterns, third-party media, and more. Allow the man who coined responsive web design back in 2010 with his <a href="http://www.alistapart.com/articles/responsive-web-design/">canonical A List Apart article</a>, to take you to the next level of designing a user experience that works, regardless of the size of the user&#8217;s viewport.</p>
<p><small>Image based on <a href="http://www.flickr.com/photos/robin24/5554306438/">Ripple</a> by robin_24, <a href="http://creativecommons.org/licenses/by/2.0/deed.en">CC-BY-2.0</a>.</small></p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/newcodepoet.wordpress.com/1643/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/newcodepoet.wordpress.com/1643/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=1643&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://build.codepoet.com/2012/12/20/responsive-sleeves/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<georss:point>0.000000 0.000000</georss:point>
		<geo:lat>0.000000</geo:lat>
		<geo:long>0.000000</geo:long>
		<media:thumbnail url="http://newcodepoet.files.wordpress.com/2012/12/recursion.jpg?w=150" />
		<media:content url="http://newcodepoet.files.wordpress.com/2012/12/recursion.jpg?w=150" medium="image">
			<media:title type="html">Responsive</media:title>
		</media:content>

		<media:content url="http://0.gravatar.com/avatar/6eb9aa374b5b9b87bbfc09c2cf876162?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">kristastevens</media:title>
		</media:content>
	</item>
		<item>
		<title>Your website stinks on mobile by Stuart Robson</title>
		<link>http://build.codepoet.com/2012/08/21/your-website-stinks-on-mobile-by-stuart-robson/</link>
		<comments>http://build.codepoet.com/2012/08/21/your-website-stinks-on-mobile-by-stuart-robson/#comments</comments>
		<pubDate>Tue, 21 Aug 2012 17:40:46 +0000</pubDate>
		<dc:creator>Krista</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[responsive web design]]></category>

		<guid isPermaLink="false">http://build.codepoet.com/?p=898</guid>
		<description><![CDATA[Testing tough love courtesy of Stuart Robson. <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=898&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></description>
				<content:encoded><![CDATA[<p class="intro">People are coming to your site from every sort of device under the sun: iPhones ancient and shiny new, iPads, tablets, Blackberries, and we haven&#8217;t even covered the litany of Android devices they&#8217;re using to see your content. Are you ready for a little web dev tough love from Stuart Robson? Step right up.</p>
<p><strong>Quick Overview</strong><br />
<a href="https://twitter.com/StuRobson">Stuart Robson</a> says you need to step up your game. Yes. You! (Me?) YES! If you&#8217;re building websites these days and hope to maintain a semblance of personal dignity, you need to test on any mobile device you can get your hands on. Grab your granny&#8217;s flip phone. Snag your brother&#8217;s Blackberry. Instead of tweeting &#8220;Poopin&#8217;&#8221; when he leaves it unattended, check out your site, take some notes, and then get to work.</p>
<div class="attribution">“<a href="http://www.flickr.com/photos/rwkphotography/3586837876/">(Old) Blackberry</a>” &#8211; © 2008 rwkvisual &#8211; made available under <a href="http://creativecommons.org/licenses/by/2.0/deed.en">Attribution 2.0 Generic</a></div>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/newcodepoet.wordpress.com/898/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/newcodepoet.wordpress.com/898/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=build.codepoet.com&#038;blog=36198572&#038;post=898&#038;subd=newcodepoet&#038;ref=&#038;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://build.codepoet.com/2012/08/21/your-website-stinks-on-mobile-by-stuart-robson/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:thumbnail url="http://newcodepoet.files.wordpress.com/2012/07/mobile1.jpg?w=150" />
		<media:content url="http://newcodepoet.files.wordpress.com/2012/07/mobile1.jpg?w=150" medium="image">
			<media:title type="html">mobile</media:title>
		</media:content>

		<media:content url="http://0.gravatar.com/avatar/6eb9aa374b5b9b87bbfc09c2cf876162?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">kristastevens</media:title>
		</media:content>
	</item>
	</channel>
</rss>
