<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>Jon Hartmann - UX Rule</title>
			<link>http://www.jonhartmann.com/index.cfm</link>
			<description>Technical blog of West Virginia web developer Jon Hartmann, covering ColdFusion, Asp.NET, Javascript, User Interface Design, and current website trends.</description>
			<language>en-us</language>
			<pubDate>Wed, 08 Sep 2010 04:22:05 -0500</pubDate>
			<lastBuildDate>Wed, 07 Oct 2009 13:56:00 -0500</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>jon.hartmann@gmail.com</managingEditor>
			<webMaster>jon.hartmann@gmail.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>jon.hartmann@gmail.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			<itunes:image href="" />
			<image>
				<url></url>
				<title>Jon Hartmann</title>
				<link>http://www.jonhartmann.com/index.cfm</link>
			</image>
			<itunes:explicit></itunes:explicit>
			
			<item>
				<title>UX Rule: Fixed Content Width</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/10/7/UX-Rule-Fixed-Content-Width</link>
				<description>
				
				When you&apos;re laying out a site, one of the most basic questions you can ask is &quot;Do we make this liquid or fixed width?&quot; Do you let your site fill the user&apos;s browser, or do you hold it to a single fixed width? It&apos;s a good question, but let me make a suggestion, nay, let me suggestion a &lt;i&gt;rule&lt;/i&gt;: Always use a fixed width for your content.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Wed, 07 Oct 2009 13:56:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/10/7/UX-Rule-Fixed-Content-Width</guid>
				
			</item>
			
			<item>
				<title>UX Rules: Four Rules for Form Controls</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/2/20/UX-Rules-Four-Rules-for-Form-Controls</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/reset.png&quot; class=&quot;floatTL&quot; alt=&quot;A reset button&quot; /&gt;Time again for another user experience rule, and this time I couldn&apos;t stop at just one. I&apos;ve got four rules for you about forms; one of the most daunting aspects of UX design. You can save yourself some trouble with the following rules:

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Rule 2:&lt;/em&gt; Ditch the Reset button.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 3:&lt;/em&gt; Make your Cancel button look like a link, or make it visually washed out compared to your Submit button.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 4:&lt;/em&gt; Make sure that there is at least a 2em distance between your Submit and your Cancel buttons.&lt;p&gt;
&lt;p&gt;&lt;em&gt;Rule 5:&lt;/em&gt; Submit on the left, Cancel on the right.&lt;p&gt;
&lt;/blockquote&gt;

Read more to see my reasonings and an example.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Fri, 20 Feb 2009 12:46:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/2/20/UX-Rules-Four-Rules-for-Form-Controls</guid>
				
			</item>
			
			<item>
				<title>UX Rule: Notification of Completion</title>
				<link>http://www.jonhartmann.com/index.cfm/2009/2/19/UX-Rule-Notification-of-Completion</link>
				<description>
				
				&lt;img src=&quot;http://www.jonhartmann.com/images/notifications.PNG&quot; class=&quot;floatTL&quot; alt=&quot;Notification bars&quot; /&gt;

So, as I move into exploring the realm of user experience(UX), I&apos;m going to work on building a collection of rules for creating good user experiences. These rules are fast, but they aren&apos;t hard: every situation is different, and although these rules will be starting points, some negotiation may be required. 

&lt;blockquote&gt;
&lt;em&gt;Rule One:&lt;/em&gt; All processing must display a notification to the user.
&lt;/blockquote&gt;

Read more to see my thoughts on when and how to do this.  [More]
				</description>
				
				<category>UX Rule</category>				
				
				<category>User Interface Design</category>				
				
				<pubDate>Thu, 19 Feb 2009 05:29:00 -0500</pubDate>
				<guid>http://www.jonhartmann.com/index.cfm/2009/2/19/UX-Rule-Notification-of-Completion</guid>
				
			</item>
			</channel></rss>