<?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>tuts Archives - Keith Devon</title>
	<atom:link href="https://keithdevon.com/category/tuts/feed/" rel="self" type="application/rss+xml" />
	<link>https://keithdevon.com/category/tuts/</link>
	<description>UK-based WordPress developer</description>
	<lastBuildDate>Thu, 16 Apr 2015 10:17:52 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.1.10</generator>
	<item>
		<title>How (and why) to use Schema.org on your WordPress website</title>
		<link>https://keithdevon.com/schema-on-your-wordpress-website/</link>
					<comments>https://keithdevon.com/schema-on-your-wordpress-website/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Thu, 16 Apr 2015 10:17:52 +0000</pubDate>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[tuts]]></category>
		<category><![CDATA[schema]]></category>
		<category><![CDATA[semantics]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Theme Development]]></category>
		<category><![CDATA[WordPress]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1234</guid>

					<description><![CDATA[<p>Search engines have a big problem. There is so much data out there and it’s hard to work out what is what. Humans are great at inferring the context of web content, but this is much more difficult for Google, Bing, Yahoo!, etc.. That’s why the biggest search engines have come together to create a [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/schema-on-your-wordpress-website/">How (and why) to use Schema.org on your WordPress website</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/schema-on-your-wordpress-website/feed/</wfw:commentRss>
			<slash:comments>8</slash:comments>
		
		
			</item>
		<item>
		<title>How to test your WordPress website performance</title>
		<link>https://keithdevon.com/how-to-test-your-wordpress-website-performance/</link>
					<comments>https://keithdevon.com/how-to-test-your-wordpress-website-performance/#respond</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Mon, 13 Apr 2015 15:34:50 +0000</pubDate>
				<category><![CDATA[resources]]></category>
		<category><![CDATA[tuts]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1232</guid>

					<description><![CDATA[<p>Website speed matters. Nobody likes browsing a slow website. If your site is slow, your visitors are more likely to leave and go to a competitor&#8217;s website. It&#8217;s not just your users who like speedy websites, Google does too. Today I recorded a video showing you two ways to test your website performance. Both methods [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/how-to-test-your-wordpress-website-performance/">How to test your WordPress website performance</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/how-to-test-your-wordpress-website-performance/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Add links to WordPress custom excerpts</title>
		<link>https://keithdevon.com/add-links-wordpress-custom-excerpts/</link>
					<comments>https://keithdevon.com/add-links-wordpress-custom-excerpts/#respond</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Thu, 15 Jan 2015 11:03:44 +0000</pubDate>
				<category><![CDATA[code]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[tuts]]></category>
		<category><![CDATA[Theme Development]]></category>
		<category><![CDATA[WordPress]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1221</guid>

					<description><![CDATA[<p>By default custom excerpts don&#8217;t have a &#8216;read more&#8217; link of any kind. I wanted my custom excerpts to look the same as my dynamically generated ones. It&#8217;s a simple code change:</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/add-links-wordpress-custom-excerpts/">Add links to WordPress custom excerpts</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/add-links-wordpress-custom-excerpts/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Using variables with WordPress translation functions</title>
		<link>https://keithdevon.com/using-variables-wordpress-translation-functions/</link>
					<comments>https://keithdevon.com/using-variables-wordpress-translation-functions/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Sun, 14 Sep 2014 16:45:50 +0000</pubDate>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tuts]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1183</guid>

					<description><![CDATA[<p>Today I wanted to be able to pass a custom field variable to the WordPress localization (l10n) functions. The custom field is a select field, so all the possible outputs are known. WordPress uses PO and MO files for translations. These are generated by scanning the site for __() and _e() functions, with a programme [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/using-variables-wordpress-translation-functions/">Using variables with WordPress translation functions</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/using-variables-wordpress-translation-functions/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Setting up domains on WP Engine</title>
		<link>https://keithdevon.com/setting-domains-wp-engine/</link>
					<comments>https://keithdevon.com/setting-domains-wp-engine/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Thu, 04 Sep 2014 14:54:26 +0000</pubDate>
				<category><![CDATA[resources]]></category>
		<category><![CDATA[tuts]]></category>
		<category><![CDATA[CNAME]]></category>
		<category><![CDATA[domains]]></category>
		<category><![CDATA[IP address]]></category>
		<category><![CDATA[WP Engine]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1177</guid>

					<description><![CDATA[<p>Add domains to install Log in to my.wpengine.com Click on the install name Click on ‘Domains’ Click ‘Add domain’ Add the non-www version of the domain Click ‘Add domain’ Add the www version of the domain Change DNS at registrar Log in to my.wpengine.com Click on the install name Note the IP Address and CNAME [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/setting-domains-wp-engine/">Setting up domains on WP Engine</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/setting-domains-wp-engine/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Full screen background images</title>
		<link>https://keithdevon.com/full-screen-background-images/</link>
					<comments>https://keithdevon.com/full-screen-background-images/#respond</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Fri, 22 Aug 2014 13:46:53 +0000</pubDate>
				<category><![CDATA[articles]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[resources]]></category>
		<category><![CDATA[tuts]]></category>
		<category><![CDATA[background image]]></category>
		<category><![CDATA[CSS]]></category>
		<guid isPermaLink="false">https://keithdevon.com/?p=1170</guid>

					<description><![CDATA[<p>I&#8217;m putting this here for my own sanity. If I had £1 for every time I&#8217;ve tried to solve this issue! The goal here is to have a background image that covers the whole of the browser window. Ideally we want it to scale, stay centred, and keep it&#8217;s correct proportions. My go-to article on [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/full-screen-background-images/">Full screen background images</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/full-screen-background-images/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>IE Compatibility view issues</title>
		<link>https://keithdevon.com/ie-compatibility-view-issues/</link>
					<comments>https://keithdevon.com/ie-compatibility-view-issues/#respond</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Thu, 15 Aug 2013 11:35:21 +0000</pubDate>
				<category><![CDATA[tuts]]></category>
		<guid isPermaLink="false">http://keithdevon.wpengine.com/?p=1085</guid>

					<description><![CDATA[<p>I&#8217;ve run into issues a few times recently with Internet Explorer&#8217;s &#8216;Compatibility view&#8217;. Some of my standards compliant web pages were being broken by having this view enabled. I found a solution via this stackoverflow page. If you add the following to your &#60;head&#62; it will force IE to disable compatibility view: &#60;meta http-equiv="X-UA-Compatible" content="IE=edge" [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/ie-compatibility-view-issues/">IE Compatibility view issues</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/ie-compatibility-view-issues/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Passing variables to get_template_part() in WordPress</title>
		<link>https://keithdevon.com/passing-variables-to-get_template_part-in-wordpress/</link>
					<comments>https://keithdevon.com/passing-variables-to-get_template_part-in-wordpress/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Thu, 31 Jan 2013 12:32:01 +0000</pubDate>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tuts]]></category>
		<guid isPermaLink="false">http://keithdevon.wpengine.com/?p=1041</guid>

					<description><![CDATA[<p>This morning I needed to pass a variable to a file that I was including using the WordPress get_template_part function. I was fiddling around with global variables when I thought there must be a better way. There is. Locate and include You can use the WordPress locate_template function within PHP&#8217;s include(). It&#8217;s done like this: include(locate_template('your-template-name.php')); [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/passing-variables-to-get_template_part-in-wordpress/">Passing variables to get_template_part() in WordPress</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/passing-variables-to-get_template_part-in-wordpress/feed/</wfw:commentRss>
			<slash:comments>55</slash:comments>
		
		
			</item>
		<item>
		<title>The PHP ternary operator</title>
		<link>https://keithdevon.com/the-php-ternary-operator/</link>
					<comments>https://keithdevon.com/the-php-ternary-operator/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Tue, 09 Oct 2012 10:03:25 +0000</pubDate>
				<category><![CDATA[code]]></category>
		<category><![CDATA[tuts]]></category>
		<category><![CDATA[PHP]]></category>
		<guid isPermaLink="false">http://keithdevon.wpengine.com/?p=969</guid>

					<description><![CDATA[<p>In my quest to master PHP, I&#8217;m going to start investigating some of the bits I&#8217;m unfamiliar with, and blogging about them. This morning, I was reading through the excellent &#8220;Professional WordPress Plugin Development&#8221; by Brad Williams, Ozh Richards and Justin Tadlock (I&#8217;ve made a resolution to read a bit every couple of days). In [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/the-php-ternary-operator/">The PHP ternary operator</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/the-php-ternary-operator/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>Custom Post Types</title>
		<link>https://keithdevon.com/custom-post-types/</link>
					<comments>https://keithdevon.com/custom-post-types/#comments</comments>
		
		<dc:creator><![CDATA[Keith Devon]]></dc:creator>
		<pubDate>Sat, 19 Nov 2011 19:35:20 +0000</pubDate>
				<category><![CDATA[tuts]]></category>
		<category><![CDATA[Custom post types]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress London]]></category>
		<category><![CDATA[wpldn]]></category>
		<guid isPermaLink="false">http://keithdevon.wpengine.com/?p=622</guid>

					<description><![CDATA[<p>Last night I gave a presentation at the WordPress London meetup. I talked about custom post types in WordPress, something that has really excited me since WordPress 3. I&#8217;ve included the video, a rough transcript of the presentation and the slides at the bottom. What we&#8217;ll cover What are custom post types When to use [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://keithdevon.com/custom-post-types/">Custom Post Types</a> appeared first on <a rel="nofollow" href="https://keithdevon.com">Keith Devon</a>.</p>
]]></description>
		
					<wfw:commentRss>https://keithdevon.com/custom-post-types/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
