<?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: Lessons Learned from Implementing Content Management Systems</title>
	<atom:link href="http://www.emediastrategist.com/blog/lessons-learned-from-implementing-a-content-management-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emediastrategist.com/blog/lessons-learned-from-implementing-a-content-management-system/</link>
	<description>Personal blog of Eric Shanfelt, Online Business Strategist</description>
	<lastBuildDate>Wed, 06 Jul 2011 13:57:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Frank</title>
		<link>http://www.emediastrategist.com/blog/lessons-learned-from-implementing-a-content-management-system/comment-page-1/#comment-28869</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Wed, 14 Nov 2007 01:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.emediastrategist.com/blog/?p=66#comment-28869</guid>
		<description>There&#039;s one thing I might add here Eric:

&lt;strong&gt;Your CMS is not the be all and end all&lt;/strong&gt; -- The emedia environment is vibrant and changing. To be best able to take advantage of opportunities that arise, you want a system that is malleable. Be careful of a system that is so locked down that changes to it are difficult to make (and be especially careful if you can&#039;t modify the system yourself in some basic areas).  In particular, you want to be able to launch pilot programs and test efforts that don&#039;t require ripping the guts out of your system. You want to have a balance between adding your standard content efficiently, but yet be able to modify it at the level of your production team, or through additional add-on programming (depending on the degree of the change). The ability to react quickly (and in-house) will often be the difference of whether you can meet both your readers&#039; and your vendors&#039; needs.</description>
		<content:encoded><![CDATA[<p>There&#8217;s one thing I might add here Eric:</p>
<p><strong>Your CMS is not the be all and end all</strong> &#8212; The emedia environment is vibrant and changing. To be best able to take advantage of opportunities that arise, you want a system that is malleable. Be careful of a system that is so locked down that changes to it are difficult to make (and be especially careful if you can&#8217;t modify the system yourself in some basic areas).  In particular, you want to be able to launch pilot programs and test efforts that don&#8217;t require ripping the guts out of your system. You want to have a balance between adding your standard content efficiently, but yet be able to modify it at the level of your production team, or through additional add-on programming (depending on the degree of the change). The ability to react quickly (and in-house) will often be the difference of whether you can meet both your readers&#8217; and your vendors&#8217; needs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

