<?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>Jackfig</title>
	<atom:link href="http://www.jackfig.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jackfig.com</link>
	<description>Seattle Web Design and Digital Media Communication</description>
	<lastBuildDate>Wed, 29 Feb 2012 18:40:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Case Study #2: Wired Magazine</title>
		<link>http://www.jackfig.com/web-style-case-study-wired-magazine/</link>
		<comments>http://www.jackfig.com/web-style-case-study-wired-magazine/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 20:16:07 +0000</pubDate>
		<dc:creator>ron</dc:creator>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Wired]]></category>

		<guid isPermaLink="false">http://www.jackfig.com/?p=25</guid>
		<description><![CDATA[A news site is the candidate for our second case study. The Google home page (our first candidate) was an easier analysis by the sheer nature of its singular function. Obviously, Wired News is more intricate, as are most news sites. For example, the New York Times is vast and complex (relating directly to its [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.jackfig.com/wp-content/uploads/2008/09/wired-case-study.jpg"><img src="http://www.jackfig.com/wp-content/uploads/2008/09/wired-case-study-185x300.jpg" alt="" title="Wired Case Study" width="185" height="300" class="alignleft size-medium wp-image-363" /></a>A news site is the candidate for our second case study. The <a href="http://www.google.com/">Google</a> home page (our first candidate) was an easier analysis by the sheer nature of its singular function. Obviously, <a href="http://www.wired.com/" title="Wired">Wired News</a> is more intricate, as are most news sites. For example, the <a href="http://www.nytimes.com/" title="New York Times">New York Times</a> is vast and complex (relating directly to its expansive news coverage, as compared to Wired&#8217;s focus on tech-oriented news) and would result in a much more intricate analysis.  For our purposes, Wired is a good place to start. The Wired News site has also been recently redesigned, giving us the rare opportunity to do an evaluation while our subject is still piping hot.</p>
<ul class="elements">
<li><strong>1. Identity</strong>It is still a rarity to see a site, particularly a news site, without it&#8217;s identifying logo at the top of the page.  There is no exception with Wired. One unusual feature about the logo position: they move it to accomodate the Sponsor Units.  This is both an unobtrusive method of ad placement and a clever use of real estate.</li>
<li><em class="notes">Web design notes</em>: White space is always useful to provide distinction among dissimilar Units.  The uninitiated might have a bit of confusion with the Identity and Sponsor Cases being intertwined.  For instance, the updated Wired home page displays a Sprint ad.  A user might think Sprint is the actual site they&#8217;re visiting or that Wired is a Sprint subsidiary. It is not utterly critical to the experience, but such confusion should always be avoided.</li>
<li><strong>2. Impact</strong>The folks at Wired have created a hierarchy of news Units that correspond to the level of importance they&#8217;ve placed on these stories: lead at the top, then three sub-levels of news Units.  How do we know that?  It&#8217;s not only the spatial arrangement of these items, but their headlines and images.  As you move down the page, the headlines decrease in size, allowing you to scan and categorize the news units: feature or lead stories, secondary features, tabbed items (latest blog posts), etc.  You&#8217;ve got four levels of news units, and it&#8217;s yours to decide how far you&#8217;d like to browse through them.  Negotiating this page from top to bottom becomes a pleasant exercise in scannability.</li>
<li>One of the nice features further down the page is the &#8220;prologue&#8221; for the tabbed items.  Though the headlines are helpful clues to a story a prologue  supplements the more obscure headlines.</li>
<li><em class="notes">Web design notes</em>: Though the large headlines for the lead stories jump from the Web page, is it necessary to dedicate such space to them?  The largest ones are 2.8em.  It would be understandable if this were an accessibilty issue, but a smaller size would suffice.  No text decoration is needed for the headlines &#8211; a user will know that simple standalone phrases will likely be a link &#8211; a mouseover will take care of any amibiguity.</li>
<li>The Georgia serif font is a familiar remnant from print days and are just as readable in this context. Many news sites have begun to use serif fonts in their redesigns.</li>
<li><strong>3. Navigation</strong> The first Navigation Case is cleverly and distinctly placed.  It dissects the Impact Case with a bold contrasting color, giving a nod to the lead stories while still making it easily located by the user.  The top level categories give credence to the implied user task and gives transparency to the site&#8217;s information architecture.</li>
<li> The second Navigation Case at the bottom of the page, could also be considered a Courtesy Case, simply by its locale and redundancy of some of the links in the first Navigation Case.  But there are some very helpful links connected to common user tasks on the site.  These might be considered secondary, to the first Navigation Case, but giving them top-level navigation (rather than within a dropdown menu) flags them as important items.</li>
<li><strong>4. Search</strong>Wired adds a helpful dropdown that enables the user to search via section.  This gives the user a level of omniscience regarding the site contents.  Helping to filter the contents also gives the user control and eliminates the feeling that you&#8217;re just stumbling into a big pile of irrelevant search results.</li>
<li><strong>5. Feature</strong>The Feature Case is a &#8220;Visit Our Sister Sites&#8221; promotion of sites within the Conde Nast conglomerate.  It doesn&#8217;t really serve the user as much as it serves the business and, therefore, identifies it as a Feature.</li>
<li><strong>6. Supplemental</strong>These discrete Units entitle the reader to a peek at upcoming news or current interesting events as a supplement to the Impact Case. Because of their standalone placement, they are given emphasis with the other competing page elements.  The subtle but eye-catching border also helps.</li>
<li><strong>7. Sponsor</strong>Only one area has been dedicated to a Sponsor Case, integrated with the Identity Case. It appears custom-made to fit in with the logo, allowing the design of the site to reign over a what could have been blaring banner ad. The Web user if often sacrificed for commerce (as we know so well in daily life), but this is a subtle integration that still has an effect and draws attention.</li>
<li><strong>8. Admin</strong>There are two Admin Cases on this page. The first is the ubiquitous copyright, user agreement and privacy policy.  A site that doesn&#8217;t have this info easily seen is, of course, likely to not be covering those bases. But those that do give the user pause about any type of plagiaristic intent or other nefarious intentions.</li>
<li>The second is located to the right, below the Supplement. Or is this Admin a Feature Case?  This was a tough call because the subscription links (already offered in two other areas of the page) are business-driven, but there are Admin elements also offered, such as RSS Feeds and FAQ&#8217;s.  So we&#8217;ll leave it as so.  If the Quick Links hadn&#8217;t been there, we&#8217;d call this a Feature Case.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.jackfig.com/web-style-case-study-wired-magazine/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Case Study #1: Google</title>
		<link>http://www.jackfig.com/google-web-style-case-study/</link>
		<comments>http://www.jackfig.com/google-web-style-case-study/#comments</comments>
		<pubDate>Thu, 21 Feb 2008 17:59:00 +0000</pubDate>
		<dc:creator>ron</dc:creator>
				<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Google]]></category>

		<guid isPermaLink="false">http://www.jackfig.com/?p=19</guid>
		<description><![CDATA[Land on the home page and you have only one option: search (simple and, therefore, highly usable). That&#8217;s why Google is our very first case study. This austere offering is the opportunity for a simple site deconstruction using style objects or style &#8220;Cases.&#8221; 1. IdentityTypically the company logo is the primary, or only, unit within [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.jackfig.com/wp-content/uploads/2008/02/google-case-study.jpg"><img src="http://www.jackfig.com/wp-content/uploads/2008/02/google-case-study-300x225.jpg" alt="" title="Google Case Study" width="300" height="225" class="alignleft size-medium wp-image-361" /></a>Land on the home page and you have only one option: search (simple and, therefore, highly <a href="http://en.wikipedia.org/wiki/Usability">usable</a>). That&#8217;s why <a href="http://www.google.com/" title="Google">Google</a> is our very first case study.  This austere offering is the opportunity for a simple site deconstruction using style objects or style &#8220;Cases.&#8221;</p>
<ul class="elements">
<li><strong>1. Identity</strong>Typically the company logo is the primary, or only, unit within the Identity Case, as we see here. Sometimes you will see a tagline and/or a photo. Google has such name recognition, though, those additional units are extraneous. Even the Supra-Elements (i.e., the page title and browser title) simply offer &#8220;Google&#8221;.</li>
<li><em class="notes">Web design notes</em>: a few people might consider drop shadows on logos somewhat of a relic nowadays, leftover from an earlier era. Not that drop shadows aren&#8217;t still used in many thoughtful ways, but it really doesn&#8217;t lend any mystique to the logo. Might we see a new rendering of it one day soon? Who cares as long as we find what we&#8217;re looking for.  Right?</li>
<li><strong>2. Impact</strong>What does this page want the visitor to do? Search! The Units within, a textbox and two buttons &#8220;Google Search&#8221; and &#8220;I&#8217;m Feeling Lucky,&#8221; are all you&#8217;ll ever need to get by on this site. Simple.</li>
<li>The only question here: doesn&#8217;t the &#8220;I&#8217;m Feeling Lucky&#8221; text for the right button seem a bit esoteric? I&#8217;ve rarely used it and I wonder what is the ratio of users to the &#8220;Google Search&#8221; button. Once you&#8217;ve used it, you get it. But it requires an extra step for the user to understand its purpose.</li>
<li><strong>3. Navigation</strong>These Navigation Cases are two dissimilar units separated not only by space, but objective. The left is a filter for finding more specific Google-hosted content; the right for personalized Google pages. A fine use of navigation: grouping links by their use case.</li>
<li> <strong>4. Search</strong>Search isn&#8217;t a standalone Unit, because the Impact of the page is centered on a search action.</li>
<li><strong>5. Feature</strong>The Feature Case in Google&#8217;s example is, again, about as simple as it can get. It is company-centered, more so than user-centered, as the linked pages are geared toward Google&#8217;s commerce. Though there are certainly users who desire access to the pages, this case isn&#8217;t necessarily helpful to the critical component of the page, the Impact Case.</li>
<li>The only item of note is the &#8220;About Google&#8221; link. &#8220;About&#8221; links are generally of a Courtesy or Supplemental nature. In this instance its placed with the Feature Units. If you visit the landing page for that link, its clear why its place there: it&#8217;s quite a promotional page for Google.</li>
<li><strong>6. Supplemental</strong>The three links to the right of the search box are there for a singular purpose: to enhance the search process. A Supplemental Case is normally used to either supplement the Impact Case or a component of the user experience of the site. For instance, a &#8220;News and Events&#8221; Supplemental Case doesn&#8217;t always help along the Impact Case of a page, but it&#8217;s a nudge to the user that the site&#8217;s owners are thinking of them and what they might want to see that&#8217;s new or interesting.</li>
<li><em class="notes">Web design notes</em>: Google uses the default blue link color consistently throughout its site. It tends to change a bit in the deeper search pages, but, due to the simplicity of the home page, it&#8217;s not necessary to use much styling on disparate links. Their division by purpose and space is enough to distinguish them. The same goes with the Supplemental Case: though the font&#8217;s a bit smaller, they merely need to have proximity to the search box for the user to understand their purpose.</li>
<li><strong>7. Sponsor</strong>There is no Sponsor Case on this page.</li>
<li><strong>8. Admin</strong>There are two Admin Cases here, both very typical. The top right one offers user login and settings. The bottom: ©2007 Google. Nothing unusual. In fact, most usual.</li>
<li><em class="notes">Web design notes</em>: The smaller, lighter colored font gives it understated emphasis.</li>
</ul>
<p>I chose to analyze the Google Web site because of its simplistic design, as well as its very recognizable interface.  Although this isn&#8217;t the best execution of the Style Cases because of the lack of content, they can be easily inferred from the page.</p>
<p>I&#8217;d offer only a couple of suggestions in style changes:</p>
<p>The &#8220;About Us&#8221; link could perhaps be in a discrete Courtesy Case, but that&#8217;s fairly minor.  The &#8220;I&#8217;m Feeling Lucky&#8221; button text is hazy in meaning (and, therefore, in purpose?)  Otherwise, this Web page is a solid example of how to infer Style Elements effectively.</p>
<p>And don&#8217;t worry, we&#8217;re going to have plenty of examples where a Web page doesn&#8217;t align with the Style Elements, and we&#8217;ll decide if that is good or bad.   All of these case studies will be to prove or disprove that every Web site is the same and that we all use these Elements, understood or not.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jackfig.com/google-web-style-case-study/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

