<?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: Clients: things you need for a site launch</title>
	<atom:link href="http://www.jhuskisson.com/articles/clients-things-you-need-for-a-site-launch/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jhuskisson.com/articles/clients-things-you-need-for-a-site-launch</link>
	<description>Nottingham freelance UK PHP, Magento, Wordpress developer</description>
	<lastBuildDate>Sun, 14 Mar 2010 10:10:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carlos Hermoso</title>
		<link>http://www.jhuskisson.com/articles/clients-things-you-need-for-a-site-launch/comment-page-1#comment-52107</link>
		<dc:creator>Carlos Hermoso</dc:creator>
		<pubDate>Tue, 13 Jan 2009 00:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/jhuskisson-dot-com/articles/clients-things-you-need-for-a-site-launch#comment-52107</guid>
		<description>Good post. Keep up the good work</description>
		<content:encoded><![CDATA[<p>Good post. Keep up the good work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.jhuskisson.com/articles/clients-things-you-need-for-a-site-launch/comment-page-1#comment-44577</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 09 Oct 2008 13:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://localhost/jhuskisson-dot-com/articles/clients-things-you-need-for-a-site-launch#comment-44577</guid>
		<description>A pretty good list this.  Thanks for sharing :)

One problem we&#039;ve had crop up on several occassions is that clients believe their content is ready until they actually see it on their website, and then ask for changes.  Sometimes this is easy enough to deal with, but sometimes the changing and checking can really make things drag out.

I guess your &quot;timeline&quot; is where this issues is best addressed, but I also think that for any project of a reasonable size, there are going to be phases and checkpoints that need to be passed along the way.  Building these checkpoints in, and getting clients to clearly sign them off is a really important if the project is going to be enjoyable and not a headache.</description>
		<content:encoded><![CDATA[<p>A pretty good list this.  Thanks for sharing :)</p>
<p>One problem we&#8217;ve had crop up on several occassions is that clients believe their content is ready until they actually see it on their website, and then ask for changes.  Sometimes this is easy enough to deal with, but sometimes the changing and checking can really make things drag out.</p>
<p>I guess your &#8220;timeline&#8221; is where this issues is best addressed, but I also think that for any project of a reasonable size, there are going to be phases and checkpoints that need to be passed along the way.  Building these checkpoints in, and getting clients to clearly sign them off is a really important if the project is going to be enjoyable and not a headache.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
