<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: WordPress Documentation Informal and Unofficial Roadmap</title>
	<atom:link href="http://jacobsantos.com/2007/programming/wordpress-documentation-informal-and-unofficial-roadmap/feed/" rel="self" type="application/rss+xml" />
	<link>http://jacobsantos.com/2007/programming/wordpress-documentation-informal-and-unofficial-roadmap/</link>
	<description>Rumblings, rants, essays, stories by Jacob Santos about Web Site Development, Persistent Browser-Based Games, personal journal, and Programming.</description>
	<lastBuildDate>Wed, 08 Feb 2012 15:54:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3-aortic-dissection</generator>
	<item>
		<title>By: Jacob Santos</title>
		<link>http://jacobsantos.com/2007/programming/wordpress-documentation-informal-and-unofficial-roadmap/comment-page-1/#comment-28888</link>
		<dc:creator>Jacob Santos</dc:creator>
		<pubDate>Tue, 01 Jan 2008 07:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.santosj.name/programming/wordpress-documentation-informal-and-unofficial-roadmap/#comment-28888</guid>
		<description>Dude, Ptah, yeah. Go for it, pick a file, any file and I&#039;ll just follow your lead man.

Pick a file you are comfortable with and start away. I would also say that there are already tickets available. If you search for &quot;phpdoc&quot; at &lt;a href=&quot;http://trac.wordpress.org&quot; rel=&quot;nofollow&quot;&gt;WordPress Trac&lt;/a&gt; keyword, that you&#039;ll find some open tickets that already have patches ready for editing.

There is a standard, &lt;a href=&quot;http://codex.wordpress.org/Inline_Documentation&quot; rel=&quot;nofollow&quot;&gt;Inline Documentation&lt;/a&gt; and would be very happy if it was followed. At this moment, the class methods do not have the &quot;function_name() - &quot; before the short description, on the functions do. At the moment. 

The class standard is unfinished, but the majority of the current documentation is without the function standard. That could be fixed, but I&#039;m going to leave it out and keep the functions with the function name first before the short description.</description>
		<content:encoded><![CDATA[<p>Dude, Ptah, yeah. Go for it, pick a file, any file and I&#8217;ll just follow your lead man.</p>
<p>Pick a file you are comfortable with and start away. I would also say that there are already tickets available. If you search for &#8220;phpdoc&#8221; at <a href="http://trac.wordpress.org" rel="nofollow">WordPress Trac</a> keyword, that you&#8217;ll find some open tickets that already have patches ready for editing.</p>
<p>There is a standard, <a href="http://codex.wordpress.org/Inline_Documentation" rel="nofollow">Inline Documentation</a> and would be very happy if it was followed. At this moment, the class methods do not have the &#8220;function_name() &#8211; &#8221; before the short description, on the functions do. At the moment. </p>
<p>The class standard is unfinished, but the majority of the current documentation is without the function standard. That could be fixed, but I&#8217;m going to leave it out and keep the functions with the function name first before the short description.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ptah Dunbar</title>
		<link>http://jacobsantos.com/2007/programming/wordpress-documentation-informal-and-unofficial-roadmap/comment-page-1/#comment-28886</link>
		<dc:creator>Ptah Dunbar</dc:creator>
		<pubDate>Tue, 01 Jan 2008 07:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.santosj.name/programming/wordpress-documentation-informal-and-unofficial-roadmap/#comment-28886</guid>
		<description>I feel your pain about a well written doc for wordpress.
I&#039;m a web developer getting into wordpress and while the codex answered a lot of my questions, it also left a lot of them unanswered.
All the functions and template tags aren&#039;t up-to-date in the codex and that leaves us developers digging everywhere for some documentation.

If you need any help with the process, I&#039;m willing to step up to the plate.</description>
		<content:encoded><![CDATA[<p>I feel your pain about a well written doc for wordpress.<br />
I&#8217;m a web developer getting into wordpress and while the codex answered a lot of my questions, it also left a lot of them unanswered.<br />
All the functions and template tags aren&#8217;t up-to-date in the codex and that leaves us developers digging everywhere for some documentation.</p>
<p>If you need any help with the process, I&#8217;m willing to step up to the plate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Documentation Informal and Unofficial Roadmap &#171; WordPress Function Documentation Progress</title>
		<link>http://jacobsantos.com/2007/programming/wordpress-documentation-informal-and-unofficial-roadmap/comment-page-1/#comment-28883</link>
		<dc:creator>WordPress Documentation Informal and Unofficial Roadmap &#171; WordPress Function Documentation Progress</dc:creator>
		<pubDate>Tue, 01 Jan 2008 06:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.santosj.name/programming/wordpress-documentation-informal-and-unofficial-roadmap/#comment-28883</guid>
		<description>[...] WordPress Documentation Informal and UnofficialÂ Roadmap   Originally appeared on SantosJ.name. [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress Documentation Informal and UnofficialÂ Roadmap   Originally appeared on SantosJ.name. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

