<?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: The folly of the agency-built CMS</title>
	<atom:link href="http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/feed/" rel="self" type="application/rss+xml" />
	<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/</link>
	<description>Resources for web creators</description>
	<lastBuildDate>Mon, 30 Apr 2012 14:13:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Smad</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-340</link>
		<dc:creator>Smad</dc:creator>
		<pubDate>Fri, 22 Jan 2010 12:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-340</guid>
		<description>Nice insight to someone who wishes to develop their in-house CMS.  There are numerous CMS out there that gives what you want.  It all depends on what features that you are looking for to management your site for the next 2-4 years.  That planning is required for any agency to identify the right CMS solution be it open source or commercial ones to manage their site. </description>
		<content:encoded><![CDATA[<p>Nice insight to someone who wishes to develop their in-house CMS.  There are numerous CMS out there that gives what you want.  It all depends on what features that you are looking for to management your site for the next 2-4 years.  That planning is required for any agency to identify the right CMS solution be it open source or commercial ones to manage their site. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-339</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-339</guid>
		<description>The chance to illustrate a post with a big pair of tits was just too good to pass up ;) </description>
		<content:encoded><![CDATA[<p>The chance to illustrate a post with a big pair of tits was just too good to pass up <img src='http://webdeveloper2.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Kelleher</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-338</link>
		<dc:creator>Lee Kelleher</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:18:51 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-338</guid>
		<description>Can&#039;t believe no one has mentioned how cold the room must have been in the &quot;My CMS can kick your CMS&#039;s ass&quot; photo! </description>
		<content:encoded><![CDATA[<p>Can&#039;t believe no one has mentioned how cold the room must have been in the &quot;My CMS can kick your CMS&#039;s ass&quot; photo! </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-337</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 13 Jan 2010 16:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-337</guid>
		<description>I just realised that there&#039;s another point I should have covered.  
 
When the developer of an Agency CMS (inevitably) leaves the company, unless they have given an extensive handover or written good documentation (like THAT ever happens!) - The developer who takes his/her place has to learn the system from scratch. 
 
For third-party CMSs it&#039;s not hard to recruit somebody who already has experience using the system - minimising the cost of switching developers or adding developers to the team. </description>
		<content:encoded><![CDATA[<p>I just realised that there&#039;s another point I should have covered.  </p>
<p>When the developer of an Agency CMS (inevitably) leaves the company, unless they have given an extensive handover or written good documentation (like THAT ever happens!) &#8211; The developer who takes his/her place has to learn the system from scratch. </p>
<p>For third-party CMSs it&#039;s not hard to recruit somebody who already has experience using the system &#8211; minimising the cost of switching developers or adding developers to the team. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Houston</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-336</link>
		<dc:creator>Chris Houston</dc:creator>
		<pubDate>Wed, 13 Jan 2010 15:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-336</guid>
		<description>Hi Dave, 
 
I run a development agency and we build 99% of our client sites on the Umbraco framework, I agree with your article, there are still companies out there who insist on building their own bespoke solutions, but that just makes us more competitive :) 
 
Chris </description>
		<content:encoded><![CDATA[<p>Hi Dave, </p>
<p>I run a development agency and we build 99% of our client sites on the Umbraco framework, I agree with your article, there are still companies out there who insist on building their own bespoke solutions, but that just makes us more competitive <img src='http://webdeveloper2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Chris </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Rydberg</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-335</link>
		<dc:creator>Henrik Rydberg</dc:creator>
		<pubDate>Wed, 13 Jan 2010 10:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-335</guid>
		<description>Thanks. 
 
I think I should point out that developing Bildy and supporting it&#039;s users is our main business, not a side project :) </description>
		<content:encoded><![CDATA[<p>Thanks. </p>
<p>I think I should point out that developing Bildy and supporting it&#039;s users is our main business, not a side project <img src='http://webdeveloper2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-334</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 13 Jan 2010 10:20:03 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-334</guid>
		<description>That sounds like a familiar situation. My only problem with Umbraco is the need to use XSLT for templates. It&#039;s not a problem for me, having a development background, but it can be problematic when front-end developers need to make changes to markup. Without any XSLT experience it can still fall to the developer to be a middle-man in the deployment process. 
 
Having said that, I&#039;ve not investigated the new MVC-based version of Umbraco yet. It would be nice if there was a choice to create views using a templating engine such as &lt;a href=&quot;http://nvelocity.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;nVelocity&lt;/a&gt;. </description>
		<content:encoded><![CDATA[<p>That sounds like a familiar situation. My only problem with Umbraco is the need to use XSLT for templates. It&#039;s not a problem for me, having a development background, but it can be problematic when front-end developers need to make changes to markup. Without any XSLT experience it can still fall to the developer to be a middle-man in the deployment process. </p>
<p>Having said that, I&#039;ve not investigated the new MVC-based version of Umbraco yet. It would be nice if there was a choice to create views using a templating engine such as <a href="http://nvelocity.sourceforge.net/" rel="nofollow">nVelocity</a>. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-333</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 13 Jan 2010 10:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-333</guid>
		<description>Thanks for your comments, I&#039;d not seen &lt;a href=&quot;http://thebildy.com/&quot; rel=&quot;nofollow&quot;&gt;Bildy&lt;/a&gt; before but it looks like an excellent solution, I&#039;ll investigate just as soon as I&#039;ve finished wrestling with the latest bodged CMS that&#039;s been dropped on me. </description>
		<content:encoded><![CDATA[<p>Thanks for your comments, I&#039;d not seen <a href="http://thebildy.com/" rel="nofollow">Bildy</a> before but it looks like an excellent solution, I&#039;ll investigate just as soon as I&#039;ve finished wrestling with the latest bodged CMS that&#039;s been dropped on me. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Rydberg</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-332</link>
		<dc:creator>Henrik Rydberg</dc:creator>
		<pubDate>Wed, 13 Jan 2010 10:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-332</guid>
		<description>Very good thoughts. 
 
Developers in agencies often need to answer very specific design decisions that are new and out of the standards. They know that you quickly run into trouble, trying to bend old standards into something completely different. So the question becomes: compromise on the design, do bending despite the inevitable problems or just make the solution. Doesn&#8217;t take much to guess the right answer. 
 
As interaction designer working with many agencies, I&#039;ve seen this come down too many times. As the author points out, it&#039;s not a safe road to take. Each custom solution add future burden with upkeep and inevitable updates &#8212;something agencies rarely have any budgets. 
 
To solve this, we created Bildy &lt;a href=&quot;http://thebildy.com&quot; rel=&quot;nofollow&quot;&gt;http://thebildy.com&lt;/a&gt; With Bildy, developers can drop in their own UI for content management and then code the functionality and look that they want. Assuming nothing means that you have custom data which you can turn into anything: HTML for sites, XML for Flash or JSON for Ajax. You&#039;ll a have solid foundation and fast tools to make that unique design a reality &#8211;without hacking. 
 
As Dave points out: you really should build upon some framework or product, what ever that might be. When upkeep and updates are taken care for you, you&#039;re not digging your own grave. </description>
		<content:encoded><![CDATA[<p>Very good thoughts. </p>
<p>Developers in agencies often need to answer very specific design decisions that are new and out of the standards. They know that you quickly run into trouble, trying to bend old standards into something completely different. So the question becomes: compromise on the design, do bending despite the inevitable problems or just make the solution. Doesn&rsquo;t take much to guess the right answer. </p>
<p>As interaction designer working with many agencies, I&#039;ve seen this come down too many times. As the author points out, it&#039;s not a safe road to take. Each custom solution add future burden with upkeep and inevitable updates &mdash;something agencies rarely have any budgets. </p>
<p>To solve this, we created Bildy <a href="http://thebildy.com" rel="nofollow">http://thebildy.com</a> With Bildy, developers can drop in their own UI for content management and then code the functionality and look that they want. Assuming nothing means that you have custom data which you can turn into anything: HTML for sites, XML for Flash or JSON for Ajax. You&#039;ll a have solid foundation and fast tools to make that unique design a reality &ndash;without hacking. </p>
<p>As Dave points out: you really should build upon some framework or product, what ever that might be. When upkeep and updates are taken care for you, you&#039;re not digging your own grave. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Shallcross</title>
		<link>http://webdeveloper2.com/2010/01/the-folly-of-the-agency-built-cms/#comment-331</link>
		<dc:creator>Adam Shallcross</dc:creator>
		<pubDate>Wed, 13 Jan 2010 09:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://webdeveloper2.com/?p=1252#comment-331</guid>
		<description>Good post.  Here at The CogWorks we used to use our own .NET based CMS which we were about to try and develop further. 
 
We then came across Umbraco about 18 months ago, found out it did everything we wanted ours to do and more...so needless to say we ditched our CMS within minutes :) 
 
We took the decision to solely concentrate on Umbraco development for every project no matter what size the client or project and it has been a great decision so far. 
 
As far as we are concerned, there&#039;s no need to waste resources building your own CMS when you can use a platform like Umbraco and spend the budget building better applications instead of standard CMS functionality that&#039;s already there and freely available. </description>
		<content:encoded><![CDATA[<p>Good post.  Here at The CogWorks we used to use our own .NET based CMS which we were about to try and develop further. </p>
<p>We then came across Umbraco about 18 months ago, found out it did everything we wanted ours to do and more&#8230;so needless to say we ditched our CMS within minutes <img src='http://webdeveloper2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>We took the decision to solely concentrate on Umbraco development for every project no matter what size the client or project and it has been a great decision so far. </p>
<p>As far as we are concerned, there&#039;s no need to waste resources building your own CMS when you can use a platform like Umbraco and spend the budget building better applications instead of standard CMS functionality that&#039;s already there and freely available. </p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: webdeveloper2.com @ 2012-05-17 20:08:18 by W3 Total Cache -->
