<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0">
<channel>
	<title>Patterns - Social</title>
	<description>UI design patterns for social experiences</description>
	<link>http://developer.yahoo.net/forum/index.php</link>
	<pubDate>Tue, 09 Feb 2010 20:46:36 -0800</pubDate>
	<ttl>99</ttl>
	<item>
		<title>Discussion Pattern</title>
		<link>http://developer.yahoo.net/forum/index.php?showtopic=556</link>
		<description><![CDATA[Hi All,<br /><br />I would like to ask, whether it would be nice to have a pattern defined for displaying discussions in web pages.<br /><br />The idea came to me when I saw how discussions are indented based on reply in reddit. It seem to be a cool idea instead of quoting feature available in classic forums.<br /><br />I think this should be discussed over here to find out the pros and cons out of various methods.<br /><br /><br />...Pr]]></description>
		<pubDate>Fri, 02 Jan 2009 09:38:54 -0800</pubDate>
		<guid>http://developer.yahoo.net/forum/index.php?showtopic=556</guid>
	</item>
	<item>
		<title>Discussion Pattern</title>
		<link>http://developer.yahoo.net/forum/index.php?showtopic=556</link>
		<description><![CDATA[<!--quoteo(post=1617:date=Jan 2 2009, 09&#58;38 AM:name=prabuinet)--><div class='quote'><div class='quotetop'>QUOTE <cite>(prabuinet &#064; Jan 2 2009, 09&#58;38 AM) <a href="index.php?act=findpost&pid=1617"><{POST_SNAPBACK}></a></cite></div><blockquote class='quotemain'><!--quotec-->Hi All,<br /><br />I would like to ask, whether it would be nice to have a pattern defined for displaying discussions in web pages.<br /><br />The idea came to me when I saw how discussions are indented based on reply in reddit. It seem to be a cool idea instead of quoting feature available in classic forums.<br /><br />I think this should be discussed over here to find out the pros and cons out of various methods.<br /><br /><br />...Pr<!--QuoteEnd--></blockquote></div><!--QuoteEEnd--><br /><br />I think that's a great idea. We've got a comment pattern in the works and the <a href="http://designingsocialinterfaces.com" rel="nofollow" target="ext">social patterns book</a> is also looking at some things related to discussions, but there's no reason why we can't talk about it here as well.<br /><br />Especially the question of indenting as a form of threading.]]></description>
		<pubDate>Fri, 02 Jan 2009 09:38:54 -0800</pubDate>
		<guid>http://developer.yahoo.net/forum/index.php?showtopic=556</guid>
	</item>
	<item>
		<title>Sign-in Continuity</title>
		<link>http://developer.yahoo.net/forum/index.php?showtopic=149</link>
		<description><![CDATA[Great pattern -- I'd like to see it include an additional guideline. Not only should you "return them to the context they were in when they were about to comment" but take additional steps to preserve this context <i>even if there are problems during the sign-in process</i>. I've seen plenty of apps that get the first part right, but assume a seamless, error-free login. Then they have some semi-hard-coded "Return to top of site" behavior as a generic catchall action from the Sign-in Error page. T-mobile, I'm looking in your direction…<br /><br />-- Bryce]]></description>
		<pubDate>Tue, 23 Sep 2008 09:50:48 -0700</pubDate>
		<guid>http://developer.yahoo.net/forum/index.php?showtopic=149</guid>
	</item>
	<item>
		<title>Sign-in Continuity</title>
		<link>http://developer.yahoo.net/forum/index.php?showtopic=149</link>
		<description><![CDATA[Bryce, I agree with you very much on this point; <br /><br /><!--quoteo(post=435:date=Sep 23 2008, 08&#58;50 AM:name=Bryce)--><div class='quote'><div class='quotetop'>QUOTE <cite>(Bryce &#064; Sep 23 2008, 08&#58;50 AM) <a href="index.php?act=findpost&pid=435"><{POST_SNAPBACK}></a></cite></div><blockquote class='quotemain'><!--quotec-->"return them to the context they were in when they were about to comment" but take additional steps to preserve this context <i>even if there are problems during the sign-in process</i>.<!--QuoteEnd--></blockquote></div><!--QuoteEEnd--><br /><br /><br />I'd also add an additional point: <br /><br />    * The sign in flow should take the least amount of steps necessary to the user. Reduce click liability by providing the most used functions first, with options for second used functions directly below. Don't make the user click to sign in - provide the box already, and if the user fails twice, turn the sign in box into an E-mail prompt for lost password while retaining the "sign-up" option the entire time. <br /><br /><img src="http://oakhazelnut.com/interface/Sign-in%20Continuity%20Pattern%20-%20Yahoo!%20Design%20Pattern%20Library.jpg" border="0" class="linked-image" />]]></description>
		<pubDate>Tue, 23 Sep 2008 09:50:48 -0700</pubDate>
		<guid>http://developer.yahoo.net/forum/index.php?showtopic=149</guid>
	</item>
	<item>
		<title>Sign-in Continuity</title>
		<link>http://developer.yahoo.net/forum/index.php?showtopic=149</link>
		<description><![CDATA[These are both excellent suggestions. I plan to review and update the pattern to address these comments.<br /><br /><!--quoteo(post=438:date=Sep 23 2008, 10&#58;59 AM:name=caseorganic)--><div class='quote'><div class='quotetop'>QUOTE <cite>(caseorganic &#064; Sep 23 2008, 10&#58;59 AM) <a href="index.php?act=findpost&pid=438"><{POST_SNAPBACK}></a></cite></div><blockquote class='quotemain'><!--quotec-->Bryce, I agree with you very much on this point; <br /><br /><br /><br /><br />I'd also add an additional point: <br /><br />    * The sign in flow should take the least amount of steps necessary to the user. Reduce click liability by providing the most used functions first, with options for second used functions directly below. Don't make the user click to sign in - provide the box already, and if the user fails twice, turn the sign in box into an E-mail prompt for lost password while retaining the "sign-up" option the entire time. <br /><br /><img src="http://oakhazelnut.com/interface/Sign-in%20Continuity%20Pattern%20-%20Yahoo!%20Design%20Pattern%20Library.jpg" border="0" class="linked-image" /><!--QuoteEnd--></blockquote></div><!--QuoteEEnd-->]]></description>
		<pubDate>Tue, 23 Sep 2008 09:50:48 -0700</pubDate>
		<guid>http://developer.yahoo.net/forum/index.php?showtopic=149</guid>
	</item>
</channel>
</rss><!-- blog1.developer.re2.yahoo.com uncompressed/chunked Tue Feb  9 20:51:58 PST 2010 -->
