<?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: A Custom CMS vs. Pre-Packaged Solutions</title>
	<atom:link href="http://www.leecoursey.net/blog/2007/02/11/a-custom-cms-vs-pre-packaged-solutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.leecoursey.net/blog/2007/02/11/a-custom-cms-vs-pre-packaged-solutions/</link>
	<description>Project &#38; Development Notes</description>
	<lastBuildDate>Sun, 15 Jan 2012 12:34:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: bofe</title>
		<link>http://www.leecoursey.net/blog/2007/02/11/a-custom-cms-vs-pre-packaged-solutions/comment-page-1/#comment-3</link>
		<dc:creator>bofe</dc:creator>
		<pubDate>Mon, 12 Feb 2007 21:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.leecoursey.net/blog/archives/10#comment-3</guid>
		<description>One thing you&#039;re neglecting is that some prepackaged CMSes cost money. Not all of them are free/open source.

I&#039;ve been down this road thousands of times, so I&#039;ll add some of my war-torn input:

- Only dealing with one organization/site? Go with a prepackaged.

- Dealing with a ton of sites with similar, specific needs? Go custom.

It really depends on your org needs and cost/benefit. Why does your org. need a CMS? What benefit is having &quot;current&quot; easy to update content going to have on your business&#039; bottom line? 

Anyway... Take care.</description>
		<content:encoded><![CDATA[<p>One thing you&#8217;re neglecting is that some prepackaged CMSes cost money. Not all of them are free/open source.</p>
<p>I&#8217;ve been down this road thousands of times, so I&#8217;ll add some of my war-torn input:</p>
<p>- Only dealing with one organization/site? Go with a prepackaged.</p>
<p>- Dealing with a ton of sites with similar, specific needs? Go custom.</p>
<p>It really depends on your org needs and cost/benefit. Why does your org. need a CMS? What benefit is having &#8220;current&#8221; easy to update content going to have on your business&#8217; bottom line? </p>
<p>Anyway&#8230; Take care.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

