<?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 &#187; Advanced</title>
	<atom:link href="http://webdosanddonts.com/category/level/advanced/feed" rel="self" type="application/rss+xml" />
	<link>http://webdosanddonts.com</link>
	<description>Tips&#38;Tricks for the modern day web designer</description>
	<lastBuildDate>Thu, 22 Jul 2010 17:30:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Use CSS for generating purely presentational content</title>
		<link>http://webdosanddonts.com/use-css-for-generating-purely-presentational-content</link>
		<comments>http://webdosanddonts.com/use-css-for-generating-purely-presentational-content#comments</comments>
		<pubDate>Wed, 09 Jun 2010 11:42:09 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[CSS]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1256</guid>
		<description><![CDATA[The content property was introduced in CSS 2.1 to add generated content to the :before and :after pseudo-elements. Given that IE 8 also now supports content, we really are getting to the point where can use this CSS feature in our production work. Just be sure to use it only in appropriate circumstances, and be [...]]]></description>
			<content:encoded><![CDATA[<p>The <code>content</code> property was introduced in CSS 2.1 to add generated content to the <code>:before</code> and <code>:after</code> pseudo-elements. Given that IE 8 also now supports <code>content</code>, we really are getting to the point where can use this CSS feature in our production work. Just be sure to use it only in appropriate circumstances, and be mindful of the accessibility implications that generated content still has.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-css-for-generating-purely-presentational-content/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use progressive enhancement instead of graceful degradation</title>
		<link>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation</link>
		<comments>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation#comments</comments>
		<pubDate>Wed, 24 Mar 2010 21:08:49 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[graceful degradation]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[progressive enhancement]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=1094</guid>
		<description><![CDATA[It can be said that both progressive enhancement and graceful degradation try to do the same thing: keep our products useful to every user. Progressive enhancement is a more sophisticated and at the same time stable way of assuring that but it takes more time and effort. Graceful degradation can be used more easily as [...]]]></description>
			<content:encoded><![CDATA[<p>It can be said that both progressive enhancement and graceful degradation try to do the same thing: keep our products useful to every user. Progressive enhancement is a more sophisticated and at the same time stable way of assuring that but it takes more time and effort. Graceful degradation can be used more easily as a patch for an already existing product; it means harder maintenance later on, but requires less initial work.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-progressive-enhancement-instead-of-graceful-degradation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don’t use HTTP based resources on a HTTPS page</title>
		<link>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page</link>
		<comments>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page#comments</comments>
		<pubDate>Sun, 07 Mar 2010 20:35:27 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Optimization]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=944</guid>
		<description><![CDATA[Internet Explorer interrupts the download and displays a confirmation dialog whenever it detects the use of mixed content on a secure page. In IE 7 and ealier, this dialog would cause annoyance to users but generally didn’t cause any other significant problems because most users would click on the Yes button and allow non-secure content [...]]]></description>
			<content:encoded><![CDATA[<p>Internet Explorer interrupts the download and displays a confirmation dialog whenever it detects the use of mixed content on a secure page.</p>
<p>In <strong>IE 7 and ealier</strong>, this dialog would cause annoyance to users but generally didn’t cause any other significant problems because most users would click on the <strong>Yes button</strong> and allow non-secure content to be downloaded. However, the wording in the <strong>IE 8</strong> version of this dialog has changed and to download the content a user would now have to click on the <strong>No button</strong>.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-http-based-resources-on-a-https-page/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t use protocol relative paths to CSS files</title>
		<link>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files</link>
		<comments>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files#comments</comments>
		<pubDate>Wed, 24 Feb 2010 18:53:03 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[IE]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[Performance]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=942</guid>
		<description><![CDATA[Internet Explorer 7 &#038; 8 will download stylesheets twice if the http(s) protocol is missing.]]></description>
			<content:encoded><![CDATA[<p>Internet Explorer 7 &#038; 8 will download stylesheets twice if the http(s) protocol is missing.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/dont-use-protocol-relative-paths-to-css-files/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Get familiar with CSS escape sequences</title>
		<link>http://webdosanddonts.com/get-familiar-with-css-escape-sequences</link>
		<comments>http://webdosanddonts.com/get-familiar-with-css-escape-sequences#comments</comments>
		<pubDate>Sat, 02 Jan 2010 11:38:43 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Escape]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=901</guid>
		<description><![CDATA[Escape sequences are useful because they allow style sheet authors to represent characters that would normally be ignored or interpreted differently by traditional CSS parsing rules.]]></description>
			<content:encoded><![CDATA[<p>Escape sequences are useful because they allow style sheet authors to represent characters that would normally be ignored or interpreted differently by traditional CSS parsing rules.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/get-familiar-with-css-escape-sequences/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Learn when to use GET and POST</title>
		<link>http://webdosanddonts.com/learn-when-to-use-get-and-post</link>
		<comments>http://webdosanddonts.com/learn-when-to-use-get-and-post#comments</comments>
		<pubDate>Mon, 23 Nov 2009 20:54:58 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Addressability]]></category>
		<category><![CDATA[GET]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[POST]]></category>
		<category><![CDATA[URI]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=774</guid>
		<description><![CDATA[HTTP GET promotes URI addressability so, designers should adopt it for safe operations such as simple queries. POST is appropriate for other types of applications where a user request has the potential to change the state of the resource (or of related resources).]]></description>
			<content:encoded><![CDATA[<p>HTTP GET promotes URI addressability so, designers should adopt it for <a href="http://www.w3.org/2001/tag/doc/whenToUseGet.html#safe">safe operations</a> such as simple queries. POST is appropriate for other types of applications where a user request has the potential to change the state of the resource (or of related resources).</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/learn-when-to-use-get-and-post/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use the optgroup element for hierarchical select options</title>
		<link>http://webdosanddonts.com/use-the-optgroup-element-for-hierarchical-select-options</link>
		<comments>http://webdosanddonts.com/use-the-optgroup-element-for-hierarchical-select-options#comments</comments>
		<pubDate>Sat, 24 Oct 2009 11:38:39 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[optgroup]]></category>
		<category><![CDATA[select]]></category>
		<category><![CDATA[Semantics]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=726</guid>
		<description><![CDATA[Grouping of options in HTML select element should be achieved using optgroup element in combination with label attribute.]]></description>
			<content:encoded><![CDATA[<p>Grouping of options in HTML <code>select</code> element should be achieved using <code>optgroup</code> element in combination with <code>label</code> attribute.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/use-the-optgroup-element-for-hierarchical-select-options/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimize the title tags</title>
		<link>http://webdosanddonts.com/optimize-the-title-tags</link>
		<comments>http://webdosanddonts.com/optimize-the-title-tags#comments</comments>
		<pubDate>Thu, 17 Sep 2009 08:20:03 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[Intermediate]]></category>
		<category><![CDATA[Optimization]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Title]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=501</guid>
		<description><![CDATA[Optimization of the title tags is a very important item in the SEO to-do list. Keep your title tags concise and consistent while using relevant keywords. Try not to go over 70 characters and create unique titles for each page.]]></description>
			<content:encoded><![CDATA[<p>Optimization of the title tags is a very important item in the SEO to-do list. Keep your title tags concise and consistent while using relevant keywords. Try not to go over 70 characters and create unique titles for each page. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/optimize-the-title-tags/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avoid CSS expressions</title>
		<link>http://webdosanddonts.com/avoid-css-expressions</link>
		<comments>http://webdosanddonts.com/avoid-css-expressions#comments</comments>
		<pubDate>Thu, 17 Sep 2009 08:04:40 +0000</pubDate>
		<dc:creator>Bojan</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Don'ts]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Expression]]></category>
		<category><![CDATA[JS]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Speed]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=394</guid>
		<description><![CDATA[While JavaScript expressions in CSS have their upsides, they are very resource intensive. That will affect the speed of the website because the expressions are frequently evaluated by the browser, causing the site to be sluggish.]]></description>
			<content:encoded><![CDATA[<p>While JavaScript expressions in CSS have their upsides, they are very resource intensive. That will affect the speed of the website because the expressions are frequently evaluated by the browser, causing the site to be sluggish. </p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/avoid-css-expressions/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Consider using Diagnostic styling</title>
		<link>http://webdosanddonts.com/consider-using-diagnostic-styling</link>
		<comments>http://webdosanddonts.com/consider-using-diagnostic-styling#comments</comments>
		<pubDate>Wed, 02 Sep 2009 09:06:13 +0000</pubDate>
		<dc:creator>Siniša</dc:creator>
				<category><![CDATA[Advanced]]></category>
		<category><![CDATA[Do's]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[Validation]]></category>

		<guid isPermaLink="false">http://webdosanddonts.com/?p=681</guid>
		<description><![CDATA[Using Diagnostic Styling can help you reveal specific problems within an HTML document.]]></description>
			<content:encoded><![CDATA[<p>Using <a title="Diagnostic Styling" href="http://meyerweb.com/eric/thoughts/2007/09/07/diagnostic-styling/">Diagnostic Styling</a> can help you reveal specific problems within an HTML document.</p>
]]></content:encoded>
			<wfw:commentRss>http://webdosanddonts.com/consider-using-diagnostic-styling/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
