<?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"
	>

<channel>
	<title>Webdesigninformer.com</title>
	<atom:link href="http://www.webdesigninformer.com/feed" rel="self" type="application/rss+xml" />
	<link>http://www.webdesigninformer.com</link>
	<description>Collecting the best web design feeds</description>
	<pubDate>Fri, 18 May 2012 20:56:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>A Precise CSS3 Color Table</title>
		<link>http://www.webdesigninformer.com/a-precise-css3-color-table</link>
		<comments>http://www.webdesigninformer.com/a-precise-css3-color-table#comments</comments>
		<pubDate>Fri, 18 May 2012 20:56:02 +0000</pubDate>
		<dc:creator>Eric Meyer</dc:creator>
		
		<category><![CDATA[algorithm]]></category>

		<category><![CDATA[art]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[css3]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[light]]></category>

		<category><![CDATA[presentation]]></category>

		<category><![CDATA[respond]]></category>

		<category><![CDATA[ress]]></category>

		<category><![CDATA[rest]]></category>

		<category><![CDATA[table]]></category>

		<category><![CDATA[twitter]]></category>

		<category><![CDATA[type]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[update]]></category>

		<category><![CDATA[web]]></category>

		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/a-precise-css3-color-table</guid>
		<description><![CDATA[ In the course of expanding my documentation of color values, I failed to find a table that listed all 147 SVG-and-CSS3-defined keywords along with the equivalent RGB decimal, RGB percent, HSL, hexadecimal, and (when valid) short-hex values. There were some tables that listed some but not all of those value types, and one that listed all the value types (plus CMYK) along with a few hundred other keywords, but none that listed all of the CSS keywords and value types. And none that I saw used precise values for the RGB percent and HSL types, preferring instead to round off at the expense of some subtle differences in color. So I created my own table, which you can now find in the CSS area of meyerweb . Most of it is dynamically generated, taking a list of keywords and RGB decimal equivalents and then calculating the rest of the values from there. ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://meyerweb.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://meyerweb.com">Eric Meyer</a> <a class="source" href="http://meyerweb.com/eric/thoughts/2012/05/18/aprecise-css3-color-table/">Go to the source</a></p>
<p> <span class="text"> In the course of expanding my documentation of color values, I failed to find a table that listed all 147 SVG-and-CSS3-defined keywords along with the equivalent RGB decimal, RGB percent, HSL, hexadecimal, and (when valid) short-hex values. There were some tables that listed some but not all of those value types, and one that listed all the value types (plus CMYK) along with a few hundred other keywords, but none that listed all of the CSS keywords and value types. And none that I saw used precise values for the RGB percent and HSL types, preferring instead to round off at the expense of some subtle differences in color. So I created my own table, which you can now find in the CSS area of meyerweb . Most of it is dynamically generated, taking a list of keywords and RGB decimal equivalents and then calculating the rest of the values from there. &#8230;</span> <a class="read-rest" href="http://meyerweb.com/eric/thoughts/2012/05/18/aprecise-css3-color-table/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/a-precise-css3-color-table/feed</wfw:commentRss>
		</item>
		<item>
		<title>“This redesign is deliberately over the top.”</title>
		<link>http://www.webdesigninformer.com/%e2%80%9cthis-redesign-is-deliberately-over-the-top%e2%80%9d</link>
		<comments>http://www.webdesigninformer.com/%e2%80%9cthis-redesign-is-deliberately-over-the-top%e2%80%9d#comments</comments>
		<pubDate>Fri, 18 May 2012 15:15:14 +0000</pubDate>
		<dc:creator>Joseph</dc:creator>
		
		<category><![CDATA[blockquote]]></category>

		<category><![CDATA[content]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[layout]]></category>

		<category><![CDATA[technology]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[web]]></category>

		<category><![CDATA[zeldman]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/%e2%80%9cthis-redesign-is-deliberately-over-the-top%e2%80%9d</guid>
		<description><![CDATA[ Jeffrey Zeldman, in a beautifully written piece titled, &#8220; Web Design Manifesto 2012 &#8221;: This redesign is deliberately over the top, but new ideas often exaggerate to make a point. It’s over the top but not unusable nor, in my opinion, unbeautiful&#8230;. We can’t keep designing as we used to if we want people to engage with our content. We can’t keep charging for ads that our layouts train readers to ignore. We can’t focus so much on technology that we forget the web is often, and quite gloriously, a transaction between reader and writer&#8230;]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://cameronmoll.tumblr.com/favicon.ico" alt="" width="16" height="16" /><a class="data">Cameron Moll</a> <a class="source" href="http://cameronmoll.tumblr.com/post/23291281779">Go to the source</a></p>
<p> <span class="text"> Jeffrey Zeldman, in a beautifully written piece titled, &#8220; Web Design Manifesto 2012 &#8221;: This redesign is deliberately over the top, but new ideas often exaggerate to make a point. It’s over the top but not unusable nor, in my opinion, unbeautiful&#8230;. We can’t keep designing as we used to if we want people to engage with our content. We can’t keep charging for ads that our layouts train readers to ignore. We can’t focus so much on technology that we forget the web is often, and quite gloriously, a transaction between reader and writer&#8230;&#8230;</span> <a class="read-rest" href="http://cameronmoll.tumblr.com/post/23291281779">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/%e2%80%9cthis-redesign-is-deliberately-over-the-top%e2%80%9d/feed</wfw:commentRss>
		</item>
		<item>
		<title>Secret src</title>
		<link>http://www.webdesigninformer.com/secret-src</link>
		<comments>http://www.webdesigninformer.com/secret-src#comments</comments>
		<pubDate>Wed, 16 May 2012 18:03:18 +0000</pubDate>
		<dc:creator>Joseph</dc:creator>
		
		<category><![CDATA[adaptive]]></category>

		<category><![CDATA[browsers]]></category>

		<category><![CDATA[html]]></category>

		<category><![CDATA[images]]></category>

		<category><![CDATA[markup]]></category>

		<category><![CDATA[process]]></category>

		<category><![CDATA[responsive]]></category>

		<category><![CDATA[standards]]></category>

		<category><![CDATA[w3c]]></category>

		<category><![CDATA[whatwg]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/secret-src</guid>
		<description><![CDATA[ There&#8217;s been quite a brouhaha over the past couple of days around the subject of standardising responsive images. There are two different matters here: the process and the technical details. I&#8217;d like to address both of them. Ill communication First of all, there&#8217;s a number of very smart developers who feel that they&#8217;ve been sidelined by the WHATWG . Tim has put together a timeline of what happened : Developers got involved in trying to standardize a solution to a common and important problem. The WHATWG told them to move the discussion to a community group. ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://adactio.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://adactio.com">Adactio</a> <a class="source" href="http://adactio.com/journal/5474/">Go to the source</a></p>
<p> <span class="text"> There&#8217;s been quite a brouhaha over the past couple of days around the subject of standardising responsive images. There are two different matters here: the process and the technical details. I&#8217;d like to address both of them. Ill communication First of all, there&#8217;s a number of very smart developers who feel that they&#8217;ve been sidelined by the WHATWG . Tim has put together a timeline of what happened : Developers got involved in trying to standardize a solution to a common and important problem. The WHATWG told them to move the discussion to a community group. &#8230;</span> <a class="read-rest" href="http://adactio.com/journal/5474/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/secret-src/feed</wfw:commentRss>
		</item>
		<item>
		<title>Backgrounds, Shadows, Fonts, and the Cascade</title>
		<link>http://www.webdesigninformer.com/backgrounds-shadows-fonts-and-the-cascade</link>
		<comments>http://www.webdesigninformer.com/backgrounds-shadows-fonts-and-the-cascade#comments</comments>
		<pubDate>Wed, 16 May 2012 14:41:57 +0000</pubDate>
		<dc:creator>Eric Meyer</dc:creator>
		
		<category><![CDATA[code]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[images]]></category>

		<category><![CDATA[results]]></category>

		<category><![CDATA[time]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/backgrounds-shadows-fonts-and-the-cascade</guid>
		<description><![CDATA[ The fact that this: h1 {color: red;} h1 {color: green;} …results in green h1 text, but this: h1 {background: url(red-wave.gif) repeat, url(green-wave.gif) repeat;} …results in a red wavy h1 background does my head in every single time . And it’s the same with text and box shadows, too! In cases where backgrounds or shadows overlap, the first one you write “wins”, by virtue of being “in front of” the background images that are listed after it. I know that font stacks are also done in order of most-to-least preferred, but I don’t see them as being equivalent. The reason is that a font stack is a list of fallbacks—use this face unless it can’t render the glyph or doesn’t exist, in which case try the next one in the list, etc., etc. Multiple background images and multiple shadows, on the other hand, are not a series of fallbacks]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://meyerweb.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://meyerweb.com">Eric Meyer</a> <a class="source" href="http://meyerweb.com/eric/thoughts/2012/05/16/background-shadows-fonts-and-the-cascade/">Go to the source</a></p>
<p> <span class="text"> The fact that this: h1 {color: red;} h1 {color: green;} …results in green h1 text, but this: h1 {background: url(red-wave.gif) repeat, url(green-wave.gif) repeat;} …results in a red wavy h1 background does my head in every single time . And it’s the same with text and box shadows, too! In cases where backgrounds or shadows overlap, the first one you write “wins”, by virtue of being “in front of” the background images that are listed after it. I know that font stacks are also done in order of most-to-least preferred, but I don’t see them as being equivalent. The reason is that a font stack is a list of fallbacks—use this face unless it can’t render the glyph or doesn’t exist, in which case try the next one in the list, etc., etc. Multiple background images and multiple shadows, on the other hand, are not a series of fallbacks&#8230;</span> <a class="read-rest" href="http://meyerweb.com/eric/thoughts/2012/05/16/background-shadows-fonts-and-the-cascade/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/backgrounds-shadows-fonts-and-the-cascade/feed</wfw:commentRss>
		</item>
		<item>
		<title>Defining ‘ch’</title>
		<link>http://www.webdesigninformer.com/defining-%e2%80%98ch%e2%80%99</link>
		<comments>http://www.webdesigninformer.com/defining-%e2%80%98ch%e2%80%99#comments</comments>
		<pubDate>Tue, 15 May 2012 14:07:03 +0000</pubDate>
		<dc:creator>Eric Meyer</dc:creator>
		
		<category><![CDATA[blockquote]]></category>

		<category><![CDATA[cc]]></category>

		<category><![CDATA[code]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[css3]]></category>

		<category><![CDATA[game]]></category>

		<category><![CDATA[geek]]></category>

		<category><![CDATA[google]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[respond]]></category>

		<category><![CDATA[results]]></category>

		<category><![CDATA[space]]></category>

		<category><![CDATA[standards]]></category>

		<category><![CDATA[tags]]></category>

		<category><![CDATA[test]]></category>

		<category><![CDATA[wiki]]></category>

		<category><![CDATA[wikipedia]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/defining-%e2%80%98ch%e2%80%99</guid>
		<description><![CDATA[ I’m working my way through a rewrite of Two Salmon (more on that anon), and I just recently came to the ch unit. Its definition in the latest CSS Values and Units module is as follows: ch unit Equal to the advance measure of the &#8220;0&#8243; (ZERO, U+0030) glyph found in the font used to render it. …and that’s it. I had never heard the term “advance measure” before, and a bit of Googling for font "advance measure" only led me to copies of the CSS Values and Units module and some configuration files for the Panda 3D game engine . ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://meyerweb.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://meyerweb.com">Eric Meyer</a> <a class="source" href="http://meyerweb.com/eric/thoughts/2012/05/15/defining-ch/">Go to the source</a></p>
<p> <span class="text"> I’m working my way through a rewrite of Two Salmon (more on that anon), and I just recently came to the ch unit. Its definition in the latest CSS Values and Units module is as follows: ch unit Equal to the advance measure of the &#8220;0&#8243; (ZERO, U+0030) glyph found in the font used to render it. …and that’s it. I had never heard the term “advance measure” before, and a bit of Googling for font &#8220;advance measure&#8221; only led me to copies of the CSS Values and Units module and some configuration files for the Panda 3D game engine . &#8230;</span> <a class="read-rest" href="http://meyerweb.com/eric/thoughts/2012/05/15/defining-ch/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/defining-%e2%80%98ch%e2%80%99/feed</wfw:commentRss>
		</item>
		<item>
		<title>Regret.</title>
		<link>http://www.webdesigninformer.com/regret</link>
		<comments>http://www.webdesigninformer.com/regret#comments</comments>
		<pubDate>Mon, 14 May 2012 20:18:07 +0000</pubDate>
		<dc:creator>Joseph</dc:creator>
		
		<category><![CDATA[aria]]></category>

		<category><![CDATA[blockquote]]></category>

		<category><![CDATA[law]]></category>

		<category><![CDATA[php]]></category>

		<category><![CDATA[quote]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/regret</guid>
		<description><![CDATA[ Kathryn Schulz, as quoted by Maria Popova : If we have goals and dreams and we want to do our best, and if we love people and we don’t want to hurt them or lose them, we should feel pain when things go wrong. The point isn’t to live without any regrets, the point is to not hate ourselves for having them… We need to learn to love the flawed, imperfect things that we create, and to forgive ourselves for creating them. Regret doesn’t remind us that we did badly — it reminds us that we know we can do better.” ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://cameronmoll.tumblr.com/favicon.ico" alt="" width="16" height="16" /><a class="data">Cameron Moll</a> <a class="source" href="http://cameronmoll.tumblr.com/post/23052027759">Go to the source</a></p>
<p> <span class="text"> Kathryn Schulz, as quoted by Maria Popova : If we have goals and dreams and we want to do our best, and if we love people and we don’t want to hurt them or lose them, we should feel pain when things go wrong. The point isn’t to live without any regrets, the point is to not hate ourselves for having them… We need to learn to love the flawed, imperfect things that we create, and to forgive ourselves for creating them. Regret doesn’t remind us that we did badly — it reminds us that we know we can do better.” &#8230;</span> <a class="read-rest" href="http://cameronmoll.tumblr.com/post/23052027759">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/regret/feed</wfw:commentRss>
		</item>
		<item>
		<title>FF Chartwell, a Chart Font</title>
		<link>http://www.webdesigninformer.com/ff-chartwell-a-chart-font</link>
		<comments>http://www.webdesigninformer.com/ff-chartwell-a-chart-font#comments</comments>
		<pubDate>Thu, 10 May 2012 14:25:00 +0000</pubDate>
		<dc:creator>Joseph</dc:creator>
		
		<category><![CDATA[2009]]></category>

		<category><![CDATA[40]]></category>

		<category><![CDATA[alpha]]></category>

		<category><![CDATA[art]]></category>

		<category><![CDATA[cc]]></category>

		<category><![CDATA[code]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[data]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[knowledge]]></category>

		<category><![CDATA[photoshop]]></category>

		<category><![CDATA[twitter]]></category>

		<category><![CDATA[type]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[update]]></category>

		<category><![CDATA[video]]></category>

		<category><![CDATA[web]]></category>

		<category><![CDATA[data visualization]]></category>

		<category><![CDATA[fonts,]]></category>

		<category><![CDATA[infographics]]></category>

		<category><![CDATA[opentype]]></category>

		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/ff-chartwell-a-chart-font</guid>
		<description><![CDATA[ Earlier today Erik Spiekermann made mention of FF Chartwell , and, at least conceptually, it&#8217;s pretty fantastic. Similar to the way icon fonts replace keyboard characters with icons, FF Chartwell uses alphanumeric characters to generate beautiful charts on the fly. To my knowledge, however, this works only in software programs and can&#8217;t be embedded in web pages. Update: It can be embedded . It&#8217;s possible to embed it, but the current EULA doesn&#8217;t allow it. Demo by Yaron Schoen who says , &#8220;Besides the FOUT which was really hard (impossible?) to remove, it was glorious.&#8221; The family includes &#8220;weights&#8221; for creating bar, line, radar, pie, rose, and ring charts]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://cameronmoll.tumblr.com/favicon.ico" alt="" width="16" height="16" /><a class="data">Cameron Moll</a> <a class="source" href="http://cameronmoll.tumblr.com/post/22778583204">Go to the source</a></p>
<p> <span class="text"> Earlier today Erik Spiekermann made mention of FF Chartwell , and, at least conceptually, it&#8217;s pretty fantastic. Similar to the way icon fonts replace keyboard characters with icons, FF Chartwell uses alphanumeric characters to generate beautiful charts on the fly. To my knowledge, however, this works only in software programs and can&#8217;t be embedded in web pages. Update: It can be embedded . It&#8217;s possible to embed it, but the current EULA doesn&#8217;t allow it. Demo by Yaron Schoen who says , &#8220;Besides the FOUT which was really hard (impossible?) to remove, it was glorious.&#8221; The family includes &#8220;weights&#8221; for creating bar, line, radar, pie, rose, and ring charts&#8230;</span> <a class="read-rest" href="http://cameronmoll.tumblr.com/post/22778583204">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/ff-chartwell-a-chart-font/feed</wfw:commentRss>
		</item>
		<item>
		<title>Homeschool Quizzing for Four Grade Levels</title>
		<link>http://www.webdesigninformer.com/homeschool-quizzing-for-four-grade-levels</link>
		<comments>http://www.webdesigninformer.com/homeschool-quizzing-for-four-grade-levels#comments</comments>
		<pubDate>Tue, 08 May 2012 21:28:50 +0000</pubDate>
		<dc:creator>Joseph</dc:creator>
		
		<category><![CDATA[Fun]]></category>

		<category><![CDATA[art]]></category>

		<category><![CDATA[blogs]]></category>

		<category><![CDATA[book]]></category>

		<category><![CDATA[books]]></category>

		<category><![CDATA[cc]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[history]]></category>

		<category><![CDATA[html]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[music,]]></category>

		<category><![CDATA[pdf]]></category>

		<category><![CDATA[questions]]></category>

		<category><![CDATA[quiz]]></category>

		<category><![CDATA[rest]]></category>

		<category><![CDATA[science]]></category>

		<category><![CDATA[table]]></category>

		<category><![CDATA[test]]></category>

		<category><![CDATA[testing]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[sports]]></category>

		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/homeschool-quizzing-for-four-grade-levels</guid>
		<description><![CDATA[ TL;DR: It&#8217;s challenging. Some of you know we homeschool our four children. Their U.S. grade levels range from 1st to 6th grade. ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://cameronmoll.tumblr.com/favicon.ico" alt="" width="16" height="16" /><a class="data">Cameron Moll</a> <a class="source" href="http://cameronmoll.tumblr.com/post/22670061894">Go to the source</a></p>
<p> <span class="text"> TL;DR: It&#8217;s challenging. Some of you know we homeschool our four children. Their U.S. grade levels range from 1st to 6th grade. &#8230;</span> <a class="read-rest" href="http://cameronmoll.tumblr.com/post/22670061894">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/homeschool-quizzing-for-four-grade-levels/feed</wfw:commentRss>
		</item>
		<item>
		<title>Vendor Tokens</title>
		<link>http://www.webdesigninformer.com/vendor-tokens</link>
		<comments>http://www.webdesigninformer.com/vendor-tokens#comments</comments>
		<pubDate>Tue, 08 May 2012 18:25:02 +0000</pubDate>
		<dc:creator>Eric Meyer</dc:creator>
		
		<category><![CDATA[archive]]></category>

		<category><![CDATA[art]]></category>

		<category><![CDATA[article]]></category>

		<category><![CDATA[code]]></category>

		<category><![CDATA[css]]></category>

		<category><![CDATA[framework]]></category>

		<category><![CDATA[html]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[native]]></category>

		<category><![CDATA[plugin]]></category>

		<category><![CDATA[prefixes]]></category>

		<category><![CDATA[pub]]></category>

		<category><![CDATA[rest]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[web]]></category>

		<category><![CDATA[webkit]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/vendor-tokens</guid>
		<description><![CDATA[ It may be that from the ashes of vendor prefixes will arise a new way forward. As proposed by François Remy , vendor tokens would serve the same basic purpose as prefixes with a different syntactical approach, and with at east a couple of extra benefits. Instead of prefixing properties, you’d instead add vendor tokens to the end of a single declaration, much as you do !important (which of course we never ever use, amirite?). For example, you might write: border-radius: 1em !webkit-draft !moz-draft !o-draft; That’s it. The prefixed alternative, of course, runs to multiple lines and has spawned a whole subindustry of framework plugins and mixins and what-all just to take the repetitive authoring burden off our shoulders. I’ve been contemplating this proposal all morning, and perhaps not too surprisingly I’ve come down in favor of the idea. ]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://meyerweb.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://meyerweb.com">Eric Meyer</a> <a class="source" href="http://meyerweb.com/eric/thoughts/2012/05/08/vendor-tokens/">Go to the source</a></p>
<p> <span class="text"> It may be that from the ashes of vendor prefixes will arise a new way forward. As proposed by François Remy , vendor tokens would serve the same basic purpose as prefixes with a different syntactical approach, and with at east a couple of extra benefits. Instead of prefixing properties, you’d instead add vendor tokens to the end of a single declaration, much as you do !important (which of course we never ever use, amirite?). For example, you might write: border-radius: 1em !webkit-draft !moz-draft !o-draft; That’s it. The prefixed alternative, of course, runs to multiple lines and has spawned a whole subindustry of framework plugins and mixins and what-all just to take the repetitive authoring burden off our shoulders. I’ve been contemplating this proposal all morning, and perhaps not too surprisingly I’ve come down in favor of the idea. &#8230;</span> <a class="read-rest" href="http://meyerweb.com/eric/thoughts/2012/05/08/vendor-tokens/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/vendor-tokens/feed</wfw:commentRss>
		</item>
		<item>
		<title>User Research ain&#8217;t no Magic Bullet</title>
		<link>http://www.webdesigninformer.com/user-research-aint-no-magic-bullet</link>
		<comments>http://www.webdesigninformer.com/user-research-aint-no-magic-bullet#comments</comments>
		<pubDate>Mon, 07 May 2012 19:24:15 +0000</pubDate>
		<dc:creator>andybudd</dc:creator>
		
		<category><![CDATA[art]]></category>

		<category><![CDATA[article]]></category>

		<category><![CDATA[data]]></category>

		<category><![CDATA[design]]></category>

		<category><![CDATA[digital]]></category>

		<category><![CDATA[form]]></category>

		<category><![CDATA[format]]></category>

		<category><![CDATA[forms]]></category>

		<category><![CDATA[ie]]></category>

		<category><![CDATA[isp]]></category>

		<category><![CDATA[learning]]></category>

		<category><![CDATA[light]]></category>

		<category><![CDATA[marketing]]></category>

		<category><![CDATA[process]]></category>

		<category><![CDATA[questions]]></category>

		<category><![CDATA[research]]></category>

		<category><![CDATA[ress]]></category>

		<category><![CDATA[rest]]></category>

		<category><![CDATA[search]]></category>

		<category><![CDATA[skills]]></category>

		<category><![CDATA[table]]></category>

		<category><![CDATA[test]]></category>

		<category><![CDATA[testing]]></category>

		<category><![CDATA[time]]></category>

		<category><![CDATA[ui]]></category>

		<category><![CDATA[usability]]></category>

		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.webdesigninformer.com/user-research-aint-no-magic-bullet</guid>
		<description><![CDATA[ User research is an extremely powerful tool (or set of tools) for understanding customer needs and behaviours. As digital projects grow in size and complexity, the risk of building the wrong thing becomes an increasing danger. So it makes sense to spend a portion of your budget to ensure that you’ve done the due diligence and are investing wisely. Marketing teams have known this for years, so few company’s would dream of launching a product or service without first understanding the market and ensuring product-market fit. However for some reason this hasn’t filtered into the world of digital products]]></description>
			<content:encoded><![CDATA[<p class="meta"><img src="http://www.andybudd.com/favicon.ico" alt="" width="16" height="16" /><a class="data" href="http://www.andybudd.com">Andy Budd</a> <a class="source" href="http://www.andybudd.com/archives/2012/05/user_research_aint_no_magic_bullet/">Go to the source</a></p>
<p> <span class="text"> User research is an extremely powerful tool (or set of tools) for understanding customer needs and behaviours. As digital projects grow in size and complexity, the risk of building the wrong thing becomes an increasing danger. So it makes sense to spend a portion of your budget to ensure that you’ve done the due diligence and are investing wisely. Marketing teams have known this for years, so few company’s would dream of launching a product or service without first understanding the market and ensuring product-market fit. However for some reason this hasn’t filtered into the world of digital products&#8230;</span> <a class="read-rest" href="http://www.andybudd.com/archives/2012/05/user_research_aint_no_magic_bullet/">Read the rest here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.webdesigninformer.com/user-research-aint-no-magic-bullet/feed</wfw:commentRss>
		</item>
	</channel>
</rss>

