<?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>Wed, 22 May 2013 03:28:27 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Symfony Blog: A simple CMS for symfony]]></title>
      <guid>http://www.phpdeveloper.org/news/8299</guid>
      <link>http://www.phpdeveloper.org/news/8299</link>
      <description><![CDATA[<p>
The symfony blog has <a href="http://www.symfony-project.com/weblog/2007/07/17/a-simple-cms-for-symfony.html">posted a look</a> at a common problem developers face when working up content-heavy sites - which is the way to go, a CMS or an application in a framework?
</p>
<blockquote>
Like us, you probably met this case several times: A client has to choose a tool for his website, which is a mix of content managed in the backend, and specific features in the frontend. The choice is between an open-source CMS and an open-source framework.
</blockquote>
<p>
There's <a href="http://www.symfony-project.com/weblog/2007/07/17/a-simple-cms-for-symfony.html">talk of advantages and disadvantages</a> for both and, finally, a common solution that combines the two - a CMS created in symfony. Fortunately, some developers saw ahead enough to create one in the form of a symfony plugin - <a href="http://trac.symfony-project.com/trac/wiki/sfSimpleCMSPlugin">sfSimpleCMSPlugin</a> (<a href="http://trac.symfony-project.com/trac/wiki/sfSimpleCMSPlugin">screenshot</a>).
</p>]]></description>
      <pubDate>Fri, 20 Jul 2007 13:46:00 -0500</pubDate>
    </item>
  </channel>
</rss>
