<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Do&#039;s &#38; Don&#039;ts</title>
	<atom:link href="http://webdosanddonts.com/feed" rel="self" type="application/rss+xml" />
	<link>http://webdosanddonts.com</link>
	<description>Tips&#38;Tricks for the modern day web designer</description>
	<lastBuildDate>Wed, 18 May 2011 22:30:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Write effective Loops</title>
		<link>http://webdosanddonts.com/write-effective-loops</link>
		<comments>http://webdosanddonts.com/write-effective-loops#comments</comments>
		<pubDate>Wed, 18 May 2011 22:30:13 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1423</guid>
		<description><![CDATA[Depending on the browser, the method used to write Loops can have a great effect on the performance of a site. Improper writing of loops can slow down pages with lots of queries and running a number of loops in parallel.]]></description>
			<content:encoded><![CDATA[<p>Depending on the  browser, the method used to write Loops can have a great effect on the  performance of a site. Improper writing of loops can slow down pages  with lots of queries and running a number of loops in parallel.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/write-effective-loops/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t use empty image src</title>
		<link>http://webdosanddonts.com/dont-use-empty-image-src</link>
		<comments>http://webdosanddonts.com/dont-use-empty-image-src#comments</comments>
		<pubDate>Mon, 30 Aug 2010 18:18:20 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[img]]></category>
		<category><![CDATA[src]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1350</guid>
		<description><![CDATA[An HTML image, either via &#60;img&#62; tag or JavaScript Image object, that has its src set to an empty string can cause traffic spikes or user state corruption.]]></description>
			<content:encoded><![CDATA[<p>An HTML image, either via <code>&lt;img&gt;</code> tag or JavaScript <code>Image</code> object, that has its <code>src</code> set to an empty string can cause traffic spikes or user state corruption.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-empty-image-src/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ensure quick loading times</title>
		<link>http://webdosanddonts.com/ensure-quick-loading-times</link>
		<comments>http://webdosanddonts.com/ensure-quick-loading-times#comments</comments>
		<pubDate>Wed, 25 Aug 2010 09:28:26 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[loading]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Speed]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1342</guid>
		<description><![CDATA[Even though today&#8217;s internet connection speeds are great, ensuring quick loading times is as important as ever. Optimize your pages and don&#8217;t make your users wait for the website to load.]]></description>
			<content:encoded><![CDATA[<p>Even though today&#8217;s internet connection speeds are great, ensuring quick loading times is as important as ever. Optimize your pages and don&#8217;t make your users wait for the website to load. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/ensure-quick-loading-times/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compose to a vertical rhythm</title>
		<link>http://webdosanddonts.com/compose-to-a-vertical-rhythm</link>
		<comments>http://webdosanddonts.com/compose-to-a-vertical-rhythm#comments</comments>
		<pubDate>Mon, 23 Aug 2010 07:51:47 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[rhythm]]></category>
		<category><![CDATA[Typography]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=695</guid>
		<description><![CDATA[Composing to a vertical rhythm using font size, line height and margin or padding and take your web typography to a new level. Vertical rhythm will help your reader down the page and increase readability.]]></description>
			<content:encoded><![CDATA[<p>Composing to a vertical rhythm using font size, line height and margin or padding and take your web typography to a new level. Vertical rhythm will help your reader down the page and increase readability.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/compose-to-a-vertical-rhythm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don’t use all bold text in your content</title>
		<link>http://webdosanddonts.com/dont-use-all-bold-text-in-your-content</link>
		<comments>http://webdosanddonts.com/dont-use-all-bold-text-in-your-content#comments</comments>
		<pubDate>Tue, 17 Aug 2010 09:27:05 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Beginner]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[bold]]></category>
		<category><![CDATA[Content]]></category>
		<category><![CDATA[Copy]]></category>
		<category><![CDATA[emphasis]]></category>
		<category><![CDATA[Text]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1337</guid>
		<description><![CDATA[Never use all bold text in your content. All bold text is hard to read and the point of the emphasis is lost. To put emphasis on a certain part of the content, use the strong tag.]]></description>
			<content:encoded><![CDATA[<p>Never use all bold text in your content. All bold text is hard to read and the point of the emphasis is lost. To put emphasis on a certain part of the content, use the <code>strong</code> tag.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-all-bold-text-in-your-content/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML5 for Web Designers Mini Review</title>
		<link>http://webdosanddonts.com/html5-for-web-designers-mini-review</link>
		<comments>http://webdosanddonts.com/html5-for-web-designers-mini-review#comments</comments>
		<pubDate>Mon, 16 Aug 2010 08:32:21 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1278</guid>
		<description><![CDATA[I recently read HTML5 for Web Designers by Jeremy Keith. Having spent not much time exploring HTML5 up to that point, I thought the book would be a good start. The outside With just 85 pages and a soft cover, the book was at first a slight disappointment, due to the fact I was not [...]]]></description>
			<content:encoded><![CDATA[<p><img style="float: right; padding: 0 0 20px 20px;" src="http://webdosanddonts.com/wp-content/uploads/2010/08/html5-for-web-designers.png" alt="" /> I recently read <a href="http://books.alistapart.com/product/html5-for-web-designers"><strong>HTML5 for Web Designers</strong> by <strong>Jeremy Keith</strong></a>. Having spent not much time exploring <strong>HTML5</strong> up to that point, I thought the book would be a good start.</p>
<h2 style="display: inline;">The outside</h2>
<p>With just 85 pages and a soft cover, the book was at first a slight disappointment, due to the fact I was not expecting such a <strong>thin book</strong>. The disappointment was short lived though, because a couple of hours into my train trip I was done and happily re-reading my favorite passages. The design of the book is very simple and very effective, as it makes the reader concentrate on its contents.</p>
<h2 style="display: inline;">The inside</h2>
<p>Once you start reading, you find the book is a joy to look at and read. You have to admire the excellent design, which in combination with a great paper quality guarantees <strong>a wonderful reading experience</strong>. But what makes it special is <strong>the way it was written</strong>&#8211;Jeremy Keith makes everything <strong>fun and super easy to understand</strong>. The author takes you on a quick trip from a brief history of markup to how you can use HTML5 <strong>today</strong>. I found myself nodding in acknowledgment several times and literally racing through pages. Simply put, this is one of those books that <strong>leaves you wanting more</strong>. After you are done, you just wish it had 50 extra pages.</p>
<h2 style="display: inline;">Conclusion</h2>
<p>I can recommend <strong>HTML5 for Web Designers</strong> to any of you who want to get familiar with HTML5. While it is not a book that will be your only resource on the topic, it will be <strong>a&nbsp;great introduction</strong> to a standard that is changing the World Wide Web. At $18 plus shipping it is not the cheapest book around, but worth it nevertheless. What I&#8217;d very much like to own is a PDF copy of the book, which is not (yet) available. This way, I would probably use it as a reference and not have to use Google instead.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/html5-for-web-designers-mini-review/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Use the text-transform property to specify the case of letters</title>
		<link>http://webdosanddonts.com/use-the-text-transform-property-to-specify-the-case-of-letters</link>
		<comments>http://webdosanddonts.com/use-the-text-transform-property-to-specify-the-case-of-letters#comments</comments>
		<pubDate>Thu, 12 Aug 2010 09:58:46 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[All-caps]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Semantics]]></category>
		<category><![CDATA[text-transform]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=744</guid>
		<description><![CDATA[As we know, writing in all-caps is a no-no. For all-caps text, you should use the text-transform property (unless you are actually SHOUTING), and the same property shod be applied if you want to use lowercase text. This means that in the content layer, you must use proper structure and semantics, and leave the styling [...]]]></description>
			<content:encoded><![CDATA[<p>As we know, <a href="http://webdosanddonts.com/dont-write-in-all-caps">writing in all-caps is a no-no</a>. For all-caps text, you should use the text-transform property (unless you are actually SHOUTING), and the same property shod be applied if you want to use <em>lowercase</em> text. This means that in the <strong>content layer</strong>, you must use proper structure and semantics, and leave the styling for the <strong>presentation layer</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-the-text-transform-property-to-specify-the-case-of-letters/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Use inline validation in web forms</title>
		<link>http://webdosanddonts.com/use-inline-validation-in-web-forms</link>
		<comments>http://webdosanddonts.com/use-inline-validation-in-web-forms#comments</comments>
		<pubDate>Thu, 12 Aug 2010 09:35:26 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Forms]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=783</guid>
		<description><![CDATA[Use inline validation in forms to provide real-time feedback and enhance the usability. Not only will it make the web forms easier to use, but it will decrease the completion times and errors made and increase the success rate.]]></description>
			<content:encoded><![CDATA[<p>Use inline validation in forms to provide real-time feedback and enhance the usability. Not only will it make the web forms easier to use, but it will decrease the completion times and errors made and increase the success rate.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-inline-validation-in-web-forms/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t put non-ascii characters in URLs</title>
		<link>http://webdosanddonts.com/dont-put-non-ascii-characters-in-urls</link>
		<comments>http://webdosanddonts.com/dont-put-non-ascii-characters-in-urls#comments</comments>
		<pubDate>Thu, 22 Jul 2010 17:30:11 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[ASCII]]></category>
		<category><![CDATA[URL]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1264</guid>
		<description><![CDATA[One thing that is rather common, especially on websites whose content is not in English, is URLs that contain unencoded characters such as space, å, ä, or ö. While this works most of the time it can cause problems.]]></description>
			<content:encoded><![CDATA[<p>One thing that is rather common, especially on websites whose content is not in English, is URLs that contain unencoded characters such as space, å, ä, or ö. While this works most of the time it can cause problems.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-put-non-ascii-characters-in-urls/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Specify unique values for the accesskey attribute</title>
		<link>http://webdosanddonts.com/specify-unique-values-for-the-accesskey-attribute</link>
		<comments>http://webdosanddonts.com/specify-unique-values-for-the-accesskey-attribute#comments</comments>
		<pubDate>Wed, 16 Jun 2010 08:05:01 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[accesskey]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1261</guid>
		<description><![CDATA[If you use accesskeys, make sure the value of the accesskey attribute is unique. If two or more elements share the same accesskey value, browsers will not interpret it consistently.]]></description>
			<content:encoded><![CDATA[<p>If you use <strong>accesskeys</strong>, make sure the value of the accesskey attribute is <strong>unique</strong>. If two or more elements share the same accesskey value, browsers will not interpret it consistently. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/specify-unique-values-for-the-accesskey-attribute/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
