<?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"
	>
<channel>
	<title>Comments on: Website Front-end Quality Control Considerations</title>
	<atom:link href="http://marcamos.com/website-front-end-quality-control-considerations/feed/" rel="self" type="application/rss+xml" />
	<link>http://marcamos.com/website-front-end-quality-control-considerations/</link>
	<description>&#60;love&#62;&#60;/love&#62;</description>
	<pubDate>Fri, 21 Nov 2008 03:05:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Ed</title>
		<link>http://marcamos.com/website-front-end-quality-control-considerations/#comment-21</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Mon, 11 Feb 2008 21:51:06 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/website-front-end-quality-control-considerations/#comment-21</guid>
		<description>	&lt;p&gt;Marc,&lt;br /&gt;
Great pointers. This would make a great cheat/reference sheet. Added to my google notebook. &#8211; @pixel8r&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Marc,<br />
Great pointers. This would make a great cheat/reference sheet. Added to my google notebook. &#8211; @pixel8r</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johannes Booy</title>
		<link>http://marcamos.com/website-front-end-quality-control-considerations/#comment-20</link>
		<dc:creator>Johannes Booy</dc:creator>
		<pubDate>Thu, 07 Feb 2008 19:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/website-front-end-quality-control-considerations/#comment-20</guid>
		<description>	&lt;p&gt;Really appreciate the effort. A print version would be great, perhaps a nice type poster to go on the office wall.&lt;/p&gt;

	&lt;p&gt;I am always trying to find the time to write and checklist the testing process. You not only saved me the time, but wrote it in a far more logical and concise manner than what I ever could have done wrote ;)&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Really appreciate the effort. A print version would be great, perhaps a nice type poster to go on the office wall.</p>
<p>I am always trying to find the time to write and checklist the testing process. You not only saved me the time, but wrote it in a far more logical and concise manner than what I ever could have done wrote <img src='http://marcamos.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo</title>
		<link>http://marcamos.com/website-front-end-quality-control-considerations/#comment-19</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Wed, 06 Feb 2008 01:36:22 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/website-front-end-quality-control-considerations/#comment-19</guid>
		<description>	&lt;p&gt;This is a great front-end checklist. I usually view the page with javascript disabled to ensure unobtrusive js &#8216;enhancement&#8217;. Same goes for images and &lt;span class="caps"&gt;CSS&lt;/span&gt;, to make sure the site content holds up.&lt;/p&gt;

	&lt;p&gt;I tend to run through these steps throughout development, as it helps minimize errors and keeps the work on target with where it has to be.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>This is a great front-end checklist. I usually view the page with javascript disabled to ensure unobtrusive js &#8216;enhancement&#8217;. Same goes for images and <span class="caps">CSS</span>, to make sure the site content holds up.</p>
<p>I tend to run through these steps throughout development, as it helps minimize errors and keeps the work on target with where it has to be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Felten</title>
		<link>http://marcamos.com/website-front-end-quality-control-considerations/#comment-18</link>
		<dc:creator>Matt Felten</dc:creator>
		<pubDate>Tue, 05 Feb 2008 21:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/website-front-end-quality-control-considerations/#comment-18</guid>
		<description>	&lt;p&gt;Nice article. I&#8217;m about to create a checklist for when I&#8217;m testing websites before they go live. This stuff will definately be on it.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Nice article. I&#8217;m about to create a checklist for when I&#8217;m testing websites before they go live. This stuff will definately be on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Witwicki</title>
		<link>http://marcamos.com/website-front-end-quality-control-considerations/#comment-17</link>
		<dc:creator>Michael Witwicki</dc:creator>
		<pubDate>Tue, 05 Feb 2008 20:47:38 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/website-front-end-quality-control-considerations/#comment-17</guid>
		<description>	&lt;p&gt;Wow! I can&#8217;t tell you how useful this will be for me. I would love a printable version that I can use as a checklist when QAing.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Wow! I can&#8217;t tell you how useful this will be for me. I would love a printable version that I can use as a checklist when QAing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
