<?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: Best Practices in Web Development: Part 1</title>
	<atom:link href="http://www.joedolson.com/articles/2008/08/best-practices-in-web-development-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.joedolson.com/articles/2008/08/best-practices-in-web-development-part-1/</link>
	<description>Tips and Commentary on Web Accessibility, Usability, and Search Marketing best practices.</description>
	<pubDate>Wed, 07 Jan 2009 10:50:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe Dolson</title>
		<link>http://www.joedolson.com/articles/2008/08/best-practices-in-web-development-part-1/comment-page-1/#comment-27250</link>
		<dc:creator>Joe Dolson</dc:creator>
		<pubDate>Sat, 13 Sep 2008 17:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=271#comment-27250</guid>
		<description>Thanks for mentioning that, Tedd - it's certainly true! In my own practice, I develop every site on a CMS; I haven't done a static site in years. This is partly because it's easier for the client to take a role in publishing or changing their site, and it's partly because it's easier for ME to manage the site, if that's necessary. As such, it's easy for me to forget how important it is to discuss the client's need for involvement -- my normal plan is to assume they will want to be able to update the site themselves.

In &lt;a href="http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-5/" rel="nofollow"&gt;part 5 of this series&lt;/a&gt;, I do address client training and long-term site management, but bringing this aspect of development into the initial requirements phase is very important.

Thanks!</description>
		<content:encoded><![CDATA[<p>Thanks for mentioning that, Tedd - it&#8217;s certainly true! In my own practice, I develop every site on a <acronym title="Content Management System">CMS</acronym>; I haven&#8217;t done a static site in years. This is partly because it&#8217;s easier for the client to take a role in publishing or changing their site, and it&#8217;s partly because it&#8217;s easier for ME to manage the site, if that&#8217;s necessary. As such, it&#8217;s easy for me to forget how important it is to discuss the client&#8217;s need for involvement&thinsp;&#8212;&thinsp;my normal plan is to assume they will want to be able to update the site themselves.</p>
<p>In <a href="http://www.joedolson.com/articles/2008/09/best-practices-in-web-development-part-5/">part 5 of this series</a>, I do address client training and long-term site management, but bringing this aspect of development into the initial requirements phase is very important.&nbsp;Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedd</title>
		<link>http://www.joedolson.com/articles/2008/08/best-practices-in-web-development-part-1/comment-page-1/#comment-27249</link>
		<dc:creator>tedd</dc:creator>
		<pubDate>Sat, 13 Sep 2008 17:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.joedolson.com/articles/?p=271#comment-27249</guid>
		<description>Great start.

One additional consideration in your "Establishing Site Requirements" should include what are the client's expectations and requirements regarding back-end development, if any.

For example:

Do they want a CMS allowing them to change their site?

Do they want a back-end to add/delete product to their site?

Do they need training for any of this?

All site development should consider if the client is going to be involved and responsible for the end-result of their site.</description>
		<content:encoded><![CDATA[<p>Great start.</p>
<p>One additional consideration in your &#8220;Establishing Site Requirements&#8221; should include what are the client&#8217;s expectations and requirements regarding back-end development, if any.</p>
<p>For example:</p>
<p>Do they want a <acronym title="Content Management System">CMS</acronym> allowing them to change their site?</p>
<p>Do they want a back-end to add/delete product to their site?</p>
<p>Do they need training for any of this?</p>
<p>All site development should consider if the client is going to be involved and responsible for the end-result of their&nbsp;site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
