<?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/"
		xmlns:xhtml="http://www.w3.org/1999/xhtml"
	>
<channel>
	<title>Comments on: Progressive enhancement</title>
	<atom:link href="http://www.flexewebs.com/semantix/progressive-enhancement/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flexewebs.com/semantix/progressive-enhancement/</link>
	<description>Guidelines for developing quality user interfaces</description>
	<lastBuildDate>Wed, 09 Jun 2010 07:32:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Grant</title>
		<link>http://www.flexewebs.com/semantix/progressive-enhancement/comment-page-1/#comment-5757</link>
		<dc:creator>Jason Grant</dc:creator>
		<pubDate>Fri, 05 Feb 2010 18:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.flexewebs.com/semantix/?p=58#comment-5757</guid>
		<description>David your thinking is good. &#039;Content is king&#039; as Google will tell us. Your visitors are not coming to your site for a gradient on your button (unless that&#039;s the content your are offering on a design discussion/tutorial site or something like that).

The idea is to make sure that everyone can access your content (including Google bot) without any issues.

Making sure you have nice, clear, semantic mark up in place is a great first step. Add some look and style via CSS and finish off with JS behaviours.</description>
		<content:encoded><![CDATA[<p>David your thinking is good. &#8216;Content is king&#8217; as Google will tell us. Your visitors are not coming to your site for a gradient on your button (unless that&#8217;s the content your are offering on a design discussion/tutorial site or something like that).</p>
<p>The idea is to make sure that everyone can access your content (including Google bot) without any issues.</p>
<p>Making sure you have nice, clear, semantic mark up in place is a great first step. Add some look and style via CSS and finish off with JS behaviours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hucklesby</title>
		<link>http://www.flexewebs.com/semantix/progressive-enhancement/comment-page-1/#comment-5756</link>
		<dc:creator>David Hucklesby</dc:creator>
		<pubDate>Fri, 05 Feb 2010 18:39:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.flexewebs.com/semantix/?p=58#comment-5756</guid>
		<description>Interesting. As I develop websites as a hobby, I never considered how others develop a site. But I have wondered about all those &quot;PSD to XHTML&quot; tutorials. This seems backwards to me.

For me, web design begins with content - text, images, whatever. Then comes markup - first the semantic bit, then the (few) structural elements. Only after this do I consider fonts, styles, decoration, and even processing. Adding enhancements that not everyone can see develops naturally from this process.

As I say, I am not a pro. Perhaps I am thinking more as a magazine editor than a web developer?</description>
		<content:encoded><![CDATA[<p>Interesting. As I develop websites as a hobby, I never considered how others develop a site. But I have wondered about all those &#8220;PSD to XHTML&#8221; tutorials. This seems backwards to me.</p>
<p>For me, web design begins with content &#8211; text, images, whatever. Then comes markup &#8211; first the semantic bit, then the (few) structural elements. Only after this do I consider fonts, styles, decoration, and even processing. Adding enhancements that not everyone can see develops naturally from this process.</p>
<p>As I say, I am not a pro. Perhaps I am thinking more as a magazine editor than a web developer?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->