<?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 Top Ten Mistakes of Web CMS Projects &#8211; and How to Avoid Them</title>
	<atom:link href="http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 18 May 2012 01:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Fabrice Talbot</title>
		<link>http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/comment-page-1/#comment-232</link>
		<dc:creator>Fabrice Talbot</dc:creator>
		<pubDate>Tue, 26 Feb 2008 02:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=382#comment-232</guid>
		<description>&lt;p&gt;Hi Mickael,
&lt;/p&gt;
&lt;p&gt;
That&#8217;s a very good checklist. From my consulting experience implementing Tridion CMS system, two issues come over and over:
&lt;br /&gt;
- migration issue (#6)
&lt;br /&gt;
- lack of functional design (#5)
&lt;/p&gt;
&lt;p&gt;
I saw many clients migrating unstructured content to (XML-based) structured content, thinking that a tool could just do it fine. This is raely the case and. IMHO, clients need to plan time to clean-up their dataset prior to migration.
&lt;/p&gt;
&lt;p&gt;
As for the lack of functional design, well.. there is as simple solution. Hire functional consultants who know very well the software and can map your CM process correctly. This is a safe investment on the long run that will ensure you get the best out of your CMS!
&lt;/p&gt;
&lt;p&gt;
Fabrice
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi Mickael,
</p>
<p>
That&#8217;s a very good checklist. From my consulting experience implementing Tridion CMS system, two issues come over and over:<br />
<br />
- migration issue (#6)<br />
<br />
- lack of functional design (#5)
</p>
<p>
I saw many clients migrating unstructured content to (XML-based) structured content, thinking that a tool could just do it fine. This is raely the case and. IMHO, clients need to plan time to clean-up their dataset prior to migration.
</p>
<p>
As for the lack of functional design, well.. there is as simple solution. Hire functional consultants who know very well the software and can map your CM process correctly. This is a safe investment on the long run that will ensure you get the best out of your CMS!
</p>
<p>
Fabrice</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Bachana</title>
		<link>http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/comment-page-1/#comment-231</link>
		<dc:creator>Joseph Bachana</dc:creator>
		<pubDate>Mon, 18 Feb 2008 21:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=382#comment-231</guid>
		<description>&lt;p&gt;Mike,
&lt;/p&gt;
&lt;p&gt;
Thanks for this article.
&lt;/p&gt;
&lt;p&gt;
With regard to #4 above, there&#8217;s two ways to look at that. If a company has an application stack that is a certain flavor (J2EE/Java, .NET, LAMP) and resources to go along with it, why would they look at a different stack? Unless the requirements for a solution are overwhelmingly a match, this doesn&#8217;t make sense for most organizations. There&#8217;s no right answer, it is just what fits best at a company. Of course if the organization doesn&#8217;t have a homogeneous development and infrastructure environment, there may be some room to explore the different solutions independent of stack.
&lt;/p&gt;
&lt;p&gt;
The other way to look at this &#8216;do your homework&#8217; point is around costs. Companies that are in &#8216;hunger&#8217; mode&#8212;akin to going to the supermarket when hungry when looking for a CMS&#8212;will convince themselves money is no object when they buy a CMS. However, if they don&#8217;t have a real budget&#8212;not just implementation but total costs over a period of time (TCO), then an expensive solution is going to wear them down with ongoing service (and maintenance) costs.
&lt;/p&gt;
&lt;p&gt;
Thanks again, -Joe B
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Mike,
</p>
<p>
Thanks for this article.
</p>
<p>
With regard to #4 above, there&#8217;s two ways to look at that. If a company has an application stack that is a certain flavor (J2EE/Java, .NET, LAMP) and resources to go along with it, why would they look at a different stack? Unless the requirements for a solution are overwhelmingly a match, this doesn&#8217;t make sense for most organizations. There&#8217;s no right answer, it is just what fits best at a company. Of course if the organization doesn&#8217;t have a homogeneous development and infrastructure environment, there may be some room to explore the different solutions independent of stack.
</p>
<p>
The other way to look at this &#8216;do your homework&#8217; point is around costs. Companies that are in &#8216;hunger&#8217; mode&#8212;akin to going to the supermarket when hungry when looking for a CMS&#8212;will convince themselves money is no object when they buy a CMS. However, if they don&#8217;t have a real budget&#8212;not just implementation but total costs over a period of time (TCO), then an expensive solution is going to wear them down with ongoing service (and maintenance) costs.
</p>
<p>
Thanks again, -Joe B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Lindknud</title>
		<link>http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/comment-page-1/#comment-230</link>
		<dc:creator>Christian Lindknud</dc:creator>
		<pubDate>Fri, 08 Feb 2008 06:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=382#comment-230</guid>
		<description>&lt;p&gt;Yes indeed, thank you for sharing this list with us.
&lt;/p&gt;
&lt;p&gt;
These things always seem so obvious when you read through them (we are about to start the same process) but don&#8217;t let that fool you.
&lt;/p&gt;
&lt;p&gt;
We&#8217;ve already shared this list as a starting reminder in our (4 person) project team!&#160;  &lt;img src=&quot;http://thecontentwrangler.com/images/smileys/wink.gif&quot; width=&quot;19&quot; height=&quot;19&quot; alt=&quot;wink&quot; style=&quot;border:0;&quot; /&gt;
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Yes indeed, thank you for sharing this list with us.
</p>
<p>
These things always seem so obvious when you read through them (we are about to start the same process) but don&#8217;t let that fool you.
</p>
<p>
We&#8217;ve already shared this list as a starting reminder in our (4 person) project team!&nbsp;  <img src="http://thecontentwrangler.com/images/smileys/wink.gif" width="19" height="19" alt="wink" style="border:0;" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: free softwares expert</title>
		<link>http://thecontentwrangler.com/2008/01/31/the_top_ten_mistakes_of_web_cms_projects_and_how_to_avoid_them/comment-page-1/#comment-229</link>
		<dc:creator>free softwares expert</dc:creator>
		<pubDate>Wed, 06 Feb 2008 09:50:01 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=382#comment-229</guid>
		<description>&lt;p&gt;Nice list.....
&lt;br /&gt;
As a worker in Balicamp, a software company. I find several mistakes that my team did. Like ignoring &#8220;Simple is better&#8221;
&lt;/p&gt;
&lt;p&gt;
But mistakes makes a good experience.
&lt;br /&gt;
Thank&#8217;s for sharing your knowledge here.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Nice list&#8230;..<br />
<br />
As a worker in Balicamp, a software company. I find several mistakes that my team did. Like ignoring &#8220;Simple is better&#8221;
</p>
<p>
But mistakes makes a good experience.<br />
<br />
Thank&#8217;s for sharing your knowledge here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

