<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>HCL 2.0 &#187; Design</title>
	<atom:link href="http://blogs.law.harvard.edu/hcl20/category/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/hcl20</link>
	<description>\"The Web is unlocked--resistance is futile.\"</description>
	<lastBuildDate>Tue, 11 Sep 2007 19:45:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
		<item>
		<title>Design</title>
		<link>http://blogs.law.harvard.edu/hcl20/2007/05/04/design/</link>
		<comments>http://blogs.law.harvard.edu/hcl20/2007/05/04/design/#comments</comments>
		<pubDate>Fri, 04 May 2007 17:28:32 +0000</pubDate>
		<dc:creator>hcl20</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://blogs.law.harvard.edu/hcl20/2007/05/04/design/</guid>
		<description><![CDATA[NOTES
Web page design is evolving as users change the way they approach information online. 

If the site needs to employ “user education” before it can be navigated, then it doesn’t work
Design of site should support work model of user
Sites use should be self evident
Users should immediately know what it is about, why it is there, [...]]]></description>
			<content:encoded><![CDATA[<p><font size="3" face="Times New Roman"><strong>NOTES</strong></font></p>
<p><font size="3" face="Times New Roman">Web page design is evolving as users change the way they approach information online. </font></p>
<ul><font size="3" face="Times New Roman"></p>
<li>If the site needs to employ “user education” before it can be navigated, then it doesn’t work</li>
<li>Design of site should support work model of user</li>
<li>Sites use should be self evident</li>
<li>Users should immediately know what it is about, why it is there, how to use it</li>
<li>Visual clutter forces people to think too hard</li>
<li>Create “sticky” content that keeps users on site until they find what they need</li>
<p></font></ul>
<p><font size="3" face="Times New Roman"> SEE presentation Infomation Design for the New Web by Ellyssa Kroski &#8211; <a href="http://infotangle.blogsome.com/">http://infotangle.blogsome.com/</a></font></p>
<p><font size="3" face="Times New Roman"> <strong>Main points of talk</strong><strong>Users:</strong></font></p>
<ul><font size="3" face="Times New Roman"></p>
<li>People are changing the way they consume info</li>
<li>Homepage should me less cluttered, more like flickr, Google</li>
<li>Today’s pages need to be SIMPLE, SOCIAL, OFFER ALTERNATIVE NAVIGATION</li>
<li>Choice overload frustrates people</li>
<li>Web applications: necessary features only, less is more</li>
<li>NO software, manuals, registration = Do it yourself model</li>
<li>Users have LOW LEARNING CURVE</li>
<p></font></ul>
<p><font size="3" face="Times New Roman"> <strong>Graphic design:</strong></font></p>
<ul><font size="3" face="Times New Roman"></p>
<li>everything is beta</li>
<li>style should respond to changes; clean, simple</li>
<li>eliminate unnecessary elements</li>
<li>centered design</li>
<li>rounded edges</li>
<li>san serif and lower case fonts to be comfortable, casual</li>
<li>large font to point out main purposes</li>
<li>strong colors, not monochromatic</li>
<li>simple icons</li>
<li>white space</li>
<li>simple icons</li>
<p></font></ul>
<p><font size="3" face="Times New Roman"> <strong>Navigation:</strong></font></p>
<ul><font size="3" face="Times New Roman"></p>
<li>obvious</li>
<li>set apart</li>
<li>persistent</li>
<p></font></ul>
<p><font size="3" face="Times New Roman"> <strong>User interface:</strong></font></p>
<ul><font size="3" face="Times New Roman"></p>
<li>AJAX</li>
<li>Large tabs</li>
<li>Drag and drop functionality</li>
<li>Auto complete functionality</li>
<li>Mapping</li>
<li>Previews (SNAP technique)</li>
<p></font></ul>
<p><font size="3" face="Times New Roman"><strong>QUESTIONS</strong></font></p>
<p><font size="3" face="Times New Roman">How can the HCL home page be designed to accommodate two audiences (students, staff/faculty) with different bu sometimes overlapping information needs?</font></p>
<p><font size="3" face="Times New Roman"> How can the HCL site be further refined to serve research and instruction needs?</font></p>
<p><font size="3" face="Times New Roman"> Could you be comfortable with an HCL site that is in perpetual beta?</font></p>
<p><font size="3" face="Times New Roman"> What is the best way to involve stakeholders in the ongoing development of the HCL web site?  In the develoment of online resources, like research guides?</font></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.law.harvard.edu/hcl20/2007/05/04/design/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license>
	</item>
	</channel>
</rss>
