<?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: Web Standards Survival Handbook Part One</title>
	<atom:link href="http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/feed/" rel="self" type="application/rss+xml" />
	<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/</link>
	<description>the personal blog of Stuart Colville covering modern web development techniques and best practices</description>
	<pubDate>Thu, 20 Nov 2008 14:23:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: ashley</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-12193</link>
		<dc:creator>ashley</dc:creator>
		<pubDate>Tue, 17 Oct 2006 11:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-12193</guid>
		<description>Those that do adopt web standards can expect to see a much better user expierence and hopefully better results in the search engines soon, for people who are disabled I heard that Google is launching an assessable search or atleast it is in the Google labs.Web Standards are great when you are dealing with the people but for programmers and such it is not a big deal for who cares about the search bots or the others on the web when your just storing your ideas or times about life on the web?</description>
		<content:encoded><![CDATA[<p>Those that do adopt web standards can expect to see a much better user expierence and hopefully better results in the search engines soon, for people who are disabled I heard that Google is launching an assessable search or atleast it is in the Google labs.Web Standards are great when you are dealing with the people but for programmers and such it is not a big deal for who cares about the search bots or the others on the web when your just storing your ideas or times about life on the web?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-151</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-151</guid>
		<description>Had a little problem with this page on Friday night, so appologies to anyone who couldn't see this page. It was Friday the 13th after all. Everything should be ok now.</description>
		<content:encoded><![CDATA[<p>Had a little problem with this page on Friday night, so appologies to anyone who couldn&#8217;t see this page. It was Friday the 13th after all. Everything should be ok now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cerebral</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-156</link>
		<dc:creator>Cerebral</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-156</guid>
		<description>Your article exactly fits my current situation, so much in fact that it's somewhat resting. I've got the workmate who shares interest, we've got a css guidelines document. Some people begin to change their table-old style habits, some not yet. By letting each one make the transition at its own pace and helping them when possible, I hope we'll soon go in the same direction.</description>
		<content:encoded><![CDATA[<p>Your article exactly fits my current situation, so much in fact that it&#8217;s somewhat resting. I&#8217;ve got the workmate who shares interest, we&#8217;ve got a css guidelines document. Some people begin to change their table-old style habits, some not yet. By letting each one make the transition at its own pace and helping them when possible, I hope we&#8217;ll soon go in the same direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-160</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-160</guid>
		<description>@Cerebral: Sounds like you're moving forward. Although it can be slow progress do hang in there, when the team starts putting out quality sites you can be proud of what you started.</description>
		<content:encoded><![CDATA[<p>@Cerebral: Sounds like you&#8217;re moving forward. Although it can be slow progress do hang in there, when the team starts putting out quality sites you can be proud of what you started.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc McHale</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-161</link>
		<dc:creator>Marc McHale</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-161</guid>
		<description>I work during the day for a local government IT Services department.  Pushing the case the web standards has taken some time, but now the managers can see the benifits, everything is being led from there.

It takes time, and at times can be frustrating, but I assure you, when a website with 750,000 pages needs an overhaul, you will soon wish it was done with standards in the first place!

When you can sell it to someone that it would take less than half the time to update a site that big with a new look if it was written with standards in mind, then you dont really need to say much more!  The fact that you could add to that, easier compatibility across browsers/platforms and devices with stylesheets alone and decreased bandwidth overhead, along with lower maintenance effort, it all of a sudden becomes a no brainer!

Its hards work, but boy is it worth it!</description>
		<content:encoded><![CDATA[<p>I work during the day for a local government IT Services department.  Pushing the case the web standards has taken some time, but now the managers can see the benifits, everything is being led from there.</p>
<p>It takes time, and at times can be frustrating, but I assure you, when a website with 750,000 pages needs an overhaul, you will soon wish it was done with standards in the first place!</p>
<p>When you can sell it to someone that it would take less than half the time to update a site that big with a new look if it was written with standards in mind, then you dont really need to say much more!  The fact that you could add to that, easier compatibility across browsers/platforms and devices with stylesheets alone and decreased bandwidth overhead, along with lower maintenance effort, it all of a sudden becomes a no brainer!</p>
<p>Its hards work, but boy is it worth it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: emmanuel</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-162</link>
		<dc:creator>emmanuel</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-162</guid>
		<description>Loads of good advice here - I tend to push developers to use xml, and completely separate content from the actual code.

the standard you set up is about how you build the xml, instead of how you render the code.

And in this case, backend developers don't have to worry about web standards. You just have to make sure that they follow the xml standard you have set up. One person can then handle all front end stuff (XSL, CSS, javascript).</description>
		<content:encoded><![CDATA[<p>Loads of good advice here - I tend to push developers to use xml, and completely separate content from the actual code.</p>
<p>the standard you set up is about how you build the xml, instead of how you render the code.</p>
<p>And in this case, backend developers don&#8217;t have to worry about web standards. You just have to make sure that they follow the xml standard you have set up. One person can then handle all front end stuff (XSL, CSS, javascript).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-163</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://dev.muffinresearch.co.uk/archives/2006/01/12/web-standards-survival-handbook-part-one/#comment-163</guid>
		<description>@Emmanuel: That's a really good point, and I can see that could really come in handy for larger development teams.

From my perspective our team (of 7) tends to not be as specialized. As a result we handle everything, including both front and backend coding so it becomes important that everyone understands web standards.</description>
		<content:encoded><![CDATA[<p>@Emmanuel: That&#8217;s a really good point, and I can see that could really come in handy for larger development teams.</p>
<p>From my perspective our team (of 7) tends to not be as specialized. As a result we handle everything, including both front and backend coding so it becomes important that everyone understands web standards.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
