<?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>Monkeyball &#187; Plugin</title>
	<atom:link href="http://www.henrywoodbury.com/category/coding/plugin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.henrywoodbury.com</link>
	<description>A random walk</description>
	<lastBuildDate>Sun, 22 Aug 2010 18:40:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Link Counter</title>
		<link>http://www.henrywoodbury.com/2010/01/link-counter/</link>
		<comments>http://www.henrywoodbury.com/2010/01/link-counter/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 21:14:07 +0000</pubDate>
		<dc:creator>Henry</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Plugin]]></category>

		<guid isPermaLink="false">http://www.henrywoodbury.com/?p=745</guid>
		<description><![CDATA[I&#8217;ve added Link Counter to the WordPress Plugin Repository. Link Counter is a WordPress Plugin that produces a report of targeted links and domains from a blog’s posts and pages. A report for this blog is here.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve added <a href="http://www.henrywoodbury.com/link-counter/">Link Counter</a> to the <a href="http://wordpress.org/extend/plugins/link-counter/">WordPress Plugin Repository</a>. Link Counter is a WordPress Plugin that produces a report of targeted links and domains from a blog’s posts and pages.</p>
<p><a href="http://www.henrywoodbury.com/link-count-for-monkeyball/">A report for this blog is here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.henrywoodbury.com/2010/01/link-counter/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Meta Tagging WordPress</title>
		<link>http://www.henrywoodbury.com/2009/11/meta-tagging-wordpress/</link>
		<comments>http://www.henrywoodbury.com/2009/11/meta-tagging-wordpress/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 17:07:51 +0000</pubDate>
		<dc:creator>Henry</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Plugin]]></category>

		<guid isPermaLink="false">http://www.henrywoodbury.com/?p=635</guid>
		<description><![CDATA[I&#8217;ve just posted a long article on meta tagging WordPress. The article sets out a conceptual framework for a WordPress plugin that will treat meta tagging in content management terms. The goal is to allow blog authors and editors to add the kind of rich meta data to posts and pages that allows something like [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve just posted a long article on <a href="http://www.henrywoodbury.com/meta-tagging-wordpress/">meta tagging WordPress</a>. The article sets out a conceptual framework for a WordPress plugin that will treat meta tagging in content management terms. The goal is to allow blog authors and editors to add the kind of rich meta data to posts and pages that allows something like <a href="http://dd.dynamicdiagrams.com/2009/09/the-times-goes-google-on-us/">artist Jer Thorp&#8217;s visualizations of the <em>New York Times</em></a>.</p>
<p>Development of the actual plugin can now begin.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.henrywoodbury.com/2009/11/meta-tagging-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Safe Signup Form</title>
		<link>http://www.henrywoodbury.com/2009/04/safe-signup-form/</link>
		<comments>http://www.henrywoodbury.com/2009/04/safe-signup-form/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 19:21:59 +0000</pubDate>
		<dc:creator>Henry</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Plugin]]></category>

		<guid isPermaLink="false">http://www.henrywoodbury.com/?p=315</guid>
		<description><![CDATA[I&#8217;ve added Safe Signup Form to the WordPress Plugin Repository. Safe Signup Form is a WordPress Plugin that will forward a form submission to an email address, while preventing most automated attacks. I developed Safe Signup Form using some key functions from Elliot Back&#8217;s WP Hashcash. WP Hashcash is an elegant anti-spam plugin for blocking automated submissions to WordPress [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve added <a href="http://www.henrywoodbury.com/safe-signup-form/">Safe Signup Form</a> to the <a href="http://wordpress.org/extend/plugins/safe-signup-form/">WordPress Plugin Repository</a>. Safe Signup Form is a WordPress Plugin that will forward a form submission to an email address, while preventing most automated attacks.</p>
<p>I developed Safe Signup Form using some key functions from Elliot Back&#8217;s <a href="http://wordpress-plugins.feifei.us/hashcash/"><span style="color: #888888;">WP Hashcash</span></a>. WP Hashcash is an elegant anti-spam plugin for blocking automated submissions to WordPress comments. What I wanted was a signup, contact, or registration form with the same protection &#8212; a mechanism that blocked robots without forcing users to identify a Captcha image or answer an unnecessary question.</p>
<p>The PHP to write and process the form was not hard to develop. I focused most on giving administrators control over the instructional, error, and success messages that create a good user experience.</p>
<p>In the process I made a few tradeoffs. Since the form is called via shortcode rather than a filter, the administration messages are not automaticaly formatted. Administrators can apply HTML code as they see fit or even write javascript or CSS to the form.</p>
<p>This brings up a second tradeoff. Where Elliot Back hooks his javascript call to the WordPress <code>wp_head</code> function, I simply write mine at the end of the form code. His approach is standards compliant. My approach targets the call only where it is required and is common practice for AJAX applications and Google-style widgets.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.henrywoodbury.com/2009/04/safe-signup-form/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
