<?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: Custom designed solutions</title>
	<atom:link href="http://www.zu.com/live/2009/06/ideas/technology/custom-designed-solutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zu.com/live/2009/06/ideas/technology/custom-designed-solutions/</link>
	<description>blog, ideas, interactive, life</description>
	<lastBuildDate>Thu, 01 Jul 2010 07:39:01 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe Boughner</title>
		<link>http://www.zu.com/live/2009/06/ideas/technology/custom-designed-solutions/comment-page-1/#comment-15994</link>
		<dc:creator>Joe Boughner</dc:creator>
		<pubDate>Mon, 22 Jun 2009 16:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.zu.com/live/?p=1231#comment-15994</guid>
		<description>Your last line nailed it. You must be open to all solutions (that applies on the client and on the agency side).

I&#039;ve worked primarily on the client side. In the past few years I&#039;ve been the lead on five different web development / redesign projects. And I can&#039;t count the number of agencies/firms that tried to sell me on their proprietary CMS of choice. That&#039;s a singluar there. 

While you&#039;ve made a very reasoned argument for custom content management, I can tell you from the client side that many of us are afraid of proprietary solutions because some less-than-reputable colleagues of yours in the agency world have done a good job of building tools that require long-term relationships. The benefit of an open-source framework is that if I&#039;m pissed off at my supplier, I can move the whole project to another supplier. 

As you&#039;ve said, no one solution is going to work for every project. A competent agency will recognize that and make sure they&#039;re aware of a variety of options - open source and proprietary. Good on you for articulating that fact so well.</description>
		<content:encoded><![CDATA[<p>Your last line nailed it. You must be open to all solutions (that applies on the client and on the agency side).</p>
<p>I&#8217;ve worked primarily on the client side. In the past few years I&#8217;ve been the lead on five different web development / redesign projects. And I can&#8217;t count the number of agencies/firms that tried to sell me on their proprietary CMS of choice. That&#8217;s a singluar there. </p>
<p>While you&#8217;ve made a very reasoned argument for custom content management, I can tell you from the client side that many of us are afraid of proprietary solutions because some less-than-reputable colleagues of yours in the agency world have done a good job of building tools that require long-term relationships. The benefit of an open-source framework is that if I&#8217;m pissed off at my supplier, I can move the whole project to another supplier. </p>
<p>As you&#8217;ve said, no one solution is going to work for every project. A competent agency will recognize that and make sure they&#8217;re aware of a variety of options &#8211; open source and proprietary. Good on you for articulating that fact so well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
