<?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: Baking websites with out a development team.</title>
	<atom:link href="http://www.duncanbrown.me.uk/2008/08/15/baking-websites-with-out-a-development-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.duncanbrown.me.uk/2008/08/15/baking-websites-with-out-a-development-team/</link>
	<description>The personal blog of Duncan Brown</description>
	<lastBuildDate>Wed, 01 Feb 2012 07:30:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan Baker</title>
		<link>http://www.duncanbrown.me.uk/2008/08/15/baking-websites-with-out-a-development-team/comment-page-1/#comment-7947</link>
		<dc:creator>Dan Baker</dc:creator>
		<pubDate>Thu, 13 May 2010 13:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.duncanbrown.me.uk/?p=16#comment-7947</guid>
		<description>Cake is certainly an interesting project. While I don&#039;t use it regularly, I find that every time I come back to it I&#039;m more impressed by it&#039;s flexibility.
 In my opinion, the perfect environment to work in is somewhere in between a CMS and a ground-up design. When you start building large websites for customers, you&#039;ll find that the customer&#039;s would usually like to be able to manage the content themselves... You&#039;re not totally stuck between a rock and a hard place in this situation though, because you can pull-apart the open-source CMS&#039;s and make them into what you want. Take Magento, for example. Magento is an e-commerce CMS built on the Zend PHP framework. It&#039;s very very powerful and it can do pretty much everything you&#039;d want an ecommerce site to do but the customer will often have requirements that are beyond the scope of Magento&#039;s abilities. No problem! You&#039;ve got the Zend framework right there! It&#039;s entirely Model-View-Controller based, so it&#039;s pretty straight forward to find the piece of code you need to modify. Heck, you can even poke and prod the object from outside of Magento and that really does remove the limits.
BTW, on the front-end side of things, Magento uses jQuery and I honestly don&#039;t know how anybody writes JS without jQuery selectors now. They&#039;re so powerful!</description>
		<content:encoded><![CDATA[<p>Cake is certainly an interesting project. While I don&#8217;t use it regularly, I find that every time I come back to it I&#8217;m more impressed by it&#8217;s flexibility.<br />
 In my opinion, the perfect environment to work in is somewhere in between a CMS and a ground-up design. When you start building large websites for customers, you&#8217;ll find that the customer&#8217;s would usually like to be able to manage the content themselves&#8230; You&#8217;re not totally stuck between a rock and a hard place in this situation though, because you can pull-apart the open-source CMS&#8217;s and make them into what you want. Take Magento, for example. Magento is an e-commerce CMS built on the Zend PHP framework. It&#8217;s very very powerful and it can do pretty much everything you&#8217;d want an ecommerce site to do but the customer will often have requirements that are beyond the scope of Magento&#8217;s abilities. No problem! You&#8217;ve got the Zend framework right there! It&#8217;s entirely Model-View-Controller based, so it&#8217;s pretty straight forward to find the piece of code you need to modify. Heck, you can even poke and prod the object from outside of Magento and that really does remove the limits.<br />
BTW, on the front-end side of things, Magento uses jQuery and I honestly don&#8217;t know how anybody writes JS without jQuery selectors now. They&#8217;re so powerful!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

