<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 20 Jun 2013 01:26:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Kevin van Zonneveld's Blog: 7 Steps to better PEAR documentation]]></title>
      <guid>http://www.phpdeveloper.org/news/12001</guid>
      <link>http://www.phpdeveloper.org/news/12001</link>
      <description><![CDATA[<p>
<i>Kevin van Zonneveld</i> has posted <a href="http://kevin.vanzonneveld.net/techblog/article/7_steps_to_better_pear_documentation/">seven steps</a> that you can follow to help the documentation for your PEAR class come out better and be more useful in the end.
</p>
<blockquote>
If you've written a <a href="http://pear.php.net/">PEAR</a> package, it's probably a good idea to submit some end user documentation. Here's how to do it.
</blockquote>
<p>
He explains what it is (XML in CVS, easily convertible with phpd) and how the process flows - save the current docs, add your own, build locally and submit to CVS. Here's his tips to help things go smoothly/turn out better:
</p>
<ul>
<li>Gather the prerequisites
<li>Save current documentation
<li>Try building the docs
<li>Write your own XML docs
<li>ReBuild peardoc
<li>Commit your XML
<li>(There is no seventh step - you're done!)
</ul>]]></description>
      <pubDate>Mon, 23 Feb 2009 11:11:55 -0600</pubDate>
    </item>
  </channel>
</rss>
