<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Real World Freelance (Front-end Development)</title>
	<link>http://theshieldsdesign.com/blog/2006/11/24/real-world-freelance-front-end-development/</link>
	<description>XHTML/CSS and other interesting Articles</description>
	<pubDate>Mon, 01 Dec 2008 20:09:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Dan Shields Weblog &#187; Blog Archive &#187; CSS, Web Standards (What you need to know!!)</title>
		<link>http://theshieldsdesign.com/blog/2006/11/24/real-world-freelance-front-end-development/#comment-50</link>
		<author>Dan Shields Weblog &#187; Blog Archive &#187; CSS, Web Standards (What you need to know!!)</author>
		<pubDate>Tue, 28 Nov 2006 04:46:57 +0000</pubDate>
		<guid>http://theshieldsdesign.com/blog/2006/11/24/real-world-freelance-front-end-development/#comment-50</guid>
					<description>[...] This is exactly what I was discussing in my previous article Real World Freelance (Front-end Development). In an ideal world we would be able to meet our standards but in the real world with budgets, timelines, and what is in the scope of work between those two, your going to have to settle with what you feel is best for the site and its users. If the client says there is not budget or everything that you sell them on, they say go ahead, more power to you but this is very rare at least from my side of the table. Perfection is not when there’s nothing to add, but when there’s nothing to take away When producing markup for a standards-friendly site, it’s all too easy to stick to the table-based way of doing things and create an over-abundance of container elements. While at first it may seem like common sense to force the markup into the design, doing so misses the point of standards-friendly production. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is exactly what I was discussing in my previous article Real World Freelance (Front-end Development). In an ideal world we would be able to meet our standards but in the real world with budgets, timelines, and what is in the scope of work between those two, your going to have to settle with what you feel is best for the site and its users. If the client says there is not budget or everything that you sell them on, they say go ahead, more power to you but this is very rare at least from my side of the table. Perfection is not when there’s nothing to add, but when there’s nothing to take away When producing markup for a standards-friendly site, it’s all too easy to stick to the table-based way of doing things and create an over-abundance of container elements. While at first it may seem like common sense to force the markup into the design, doing so misses the point of standards-friendly production. [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
