Wow! Another thought inspired by <is:uri cite="http://www.catb.org/~esr/writings/cathedral-bazaar/">The Cathedral and The Bazaar</is:uri>, by Eric S. Raymond. This time, <is:uri title="lessons 3 and 2">http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s02.html</is:uri>. If you are not a <is:thing>geek</is:thing>, this post contains <a href="/libertus/2006/07/07/developing-outreach-2/?outreach=non-geek#content">Outreach links especially for you</a>. <is:search>What is Outreach</is:search>? What <is:word>outreach</is:word> <is:search cite="outreach sucks">isn't</is:search>.

<!--more--><h3>Narrative</h3>

Now that <q>libertus</q> is hosted on a server under my complete control, I can pick and choose (and even <a href="/libertus/2006/05/19/introducing-blog-ram-thing/#php-with-tidy-on-ubuntu">compile</a>) the components and services I want available to the blog. I am very fond of <a href="/outreach/">Outreach v0.4</a>. As a piece of experimental and education code, it has served its purpose well, without fail, for many months. It has even evolved a primitive sense of style.

It's time to throw it away and start again. This time, I have available the <is:concept level="non-geek">Turing complete</is:concept> <is:product level="non-geek" cite="W3C XSLT" title="eXtensible Stylesheet Language Transformation, a web standard">XSL</is:product> and the handy, if quirky, <is:product level="non-geek" cite="W3C HTML Tidy">HTML Tidy</is:product>. Outreach is a <is:product level="non-geek" cite="W3C XML Namespaces" title="eXtensible Markup Language Namespaces, a web standard">XML namespace</is:product>, nothing more. The Outreach plugin for <is:product>WordPress</is:product> is nothing more than a simple but highly-specific <is:product level="non-geek" cite="W3C XML" title="eXtensible Markup Language, a web standard">XML</is:product> document transformation, implemented using <is:thing level="non-geek">regular expressions</is:thing> and some crafty <is:product level="non-geek">PHP</is:product>.

Outreach 2 shall be a plugin for WordPress that transforms post and comment content using XSLT to implement the same well-defined (with <is:thing level="non-geek" title="Document Type Definition, perhaps the scariest web standard of them all!">DTD</is:thing>, perhaps) set of XML tags and their current behaviour, primaily the automatic generation of indirect links.

Additionally, I would like to offer a broader choice of entry <is:word level="non-geek">syntaxes</is:word> than <is:product level="non-geek" cite="W3C XHTML" title="eXtensible Hypertext Markup Language, a web standard">XHTML</is:product> and <is:thing level="non-geek">plain text</is:thing>. I like <is:product>Markdown syntax</is:product> but don't like <is:product cite="Markdown Plugin for WordPress">the WordPress plugin that implements it</is:product><sup title="abuse of md5()">*</sup>. I am also interested by the <is:thing cite="wiki syntax">syntax used</is:thing> on <is:thing level="non-geek" title="a form of content management system suited to collaborative, community-driven content creation, and websites that uses same">wikis</is:uri> such as <is:uri cite="http://wikipedia.org" title="the free on-line encyclop&oelig;dia, built from public contributions, funded by donation">the sublime Wikipedia</is:uri>, especially [[postname]], which I intend to use to ease the process of constructing internal links.

<h3>Requirements</h3>

<ol>
<li><a href="#"></a>Re-engineer Outreach Content Filter Using XSLT</li>
<li><a href="#"></a>Re-engineer Outreach Plugin for WordPress</li>
<li><a href="#"></a>Implement XHTML Validation With HTML Tidy</li>
<li><a href="#"></a>Explore Markdown and Wiki Syntaxes</li>
<li><a href="#"></a>Test Locally</li>
<li><a href="#"></a>Prepare Customised PHP</li>
<li><a href="#"></a>Install Customised PHP on <q>libertus</q></li>
<li><a href="#"></a>Install Outreach 2 on <q>libertus</q></li>
<li><a href="#"></a>Integration Testing</li>
<li><a href="#"></a>Launch</li>
</ol>