<?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>Sat, 22 Nov 2008 02:01:35 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[OpenSourceCommunity.org: What do you think makes a good CMS?]]></title>
      <guid>http://www.phpdeveloper.org/news/8103</guid>
      <link>http://www.phpdeveloper.org/news/8103</link>
      <description><![CDATA[<p>
On his blog today, <i>Stoyan</i> <a href="http://www.phpied.com/good-php-cms/">points out</a> a topic he's started over on the OpenSourceCommunity.org site - <a href="http://opensourcecommunity.org/2007/06/21/what-do-you-think-makes-good-cms">What do you think makes a good CMS?</a>.
</p>
<blockquote>
This year's <a href="http://www.packtpub.com/award">Packt Publishing awards</a> for the best Open Source CMS are on their way, starting middle of July. I've been selected as a judge in the PHP CMS category. [...] How can one judge something as diverse and liquid as a CMS? Content management comes in all different shapes, some systems focus on solving some problems and they do a better job than another CMS that mainly tackles different types of problems.
</blockquote>
<p>
He <a href="http://opensourcecommunity.org/2007/06/21/what-do-you-think-makes-good-cms">shares the experiences</a> he's had with CMS and companies that have rolled their own in the past as well as a small list of things that he's thinking about making "the standard" for the CMSes to be judged by. Also included is a lengthy list of requirements that he sees that need to be included for any decent CMS to move to the next level.
</p>]]></description>
      <pubDate>Fri, 22 Jun 2007 09:26:00 -0500</pubDate>
    </item>
  </channel>
</rss>
