<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

    <title type="text">Viget Labs : Master Blog Feed</title>
    <subtitle type="text">FourLabs Blog: Viget Labs:</subtitle>
    <link rel="alternate" type="text/html" href="http://www.viget.com/blog/" />
    <link rel="self" type="application/atom+xml" href="http://www.viget.com/site/atom/" />
    <updated>2012-02-06T22:35:20Z</updated>
    <rights>Copyright (c) 2012, Khanh Stenberg</rights>
    <generator uri="http://expressionengine.com/" version="1.6.2">ExpressionEngine</generator>
    <id>tag:viget.com,2012:02:06</id>


    <entry>
      <title>Snowshoes, Laser Tag, and Bicycles</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/snowshoes-laser-tags-and-bikes/" />
      <id>tag:viget.com,2012:blog/24.2347</id>
      <published>2012-02-06T17:26:00Z</published>
      <updated>2012-02-06T22:35:20Z</updated>
      <author>
            <name>Khanh Stenberg</name>
            <email>khanh.stenberg@viget.com</email>
                  </author>

      <category term="General"
        scheme="http://www.viget.com/blog/category/general/"
        label="General" />
      <content type="html"><![CDATA[

                 <p>After a busy holiday season filled with <a href="http://www.viget.com/blog/its-cold-warm-up-with-vigetreats/" target="_blank">Vigetreats</a> and <a href="http://www.flickr.com/photos/viget/sets/72157628430327101/" target="_blank">fun</a> it was already time for another TTT. It proved to be yet another successful quarter as <a href="http://www.flickr.com/photos/viget/6771891337/in/set-72157629057289537" target="_blank">Andy</a> shared the financials and we all talked about what makes Viget a great place, but more importantly, how to make it even better. After all the business talk was out of the way each office took the rest of the afternoon to do some seriously awesome things.</p>
<p>We've only had snow at one of our offices this year so the Boulder team took advantage of it and went snowshoeing at <a href="http://eldora.com/" target="_blank">Eldora Mountain Resort</a>.</p>
<p>They bundled up for the 30 degree weather and 20-40mph winds, and trekked the 2 mile trail called Lakes Loop.</p>
<p><a href="http://www.flickr.com/photos/viget/6727578725/in/set-72157628944760693/" target="_blank"><img alt="team boulder" height="300" src="http://farm8.staticflickr.com/7141/6727578725_cecfe75fb6.jpg" width="200" /></a>&nbsp;<a href="http://www.flickr.com/photos/viget/6727580219/in/set-72157628944760693/" target="_blank"><img alt="showshoeing" height="300" src="http://farm8.staticflickr.com/7165/6727580219_3c60eeda61.jpg" width="200" /></a></p>                 <p>They stopped a few times along the way to play in the snow. They built a snowkid and at times, acted like kids.</p>
<p><a href="http://www.flickr.com/photos/viget/6727582431/in/set-72157628944760693/" target="_blank"><img alt="vigeman" height="300" src="http://farm8.staticflickr.com/7015/6727582431_e3413d76ec.jpg" width="200" /></a><a href="http://www.flickr.com/photos/viget/6727583303/in/set-72157628944760693/" target="_blank"><img alt="snowball" height="300" src="http://farm8.staticflickr.com/7157/6727583303_78468ebfdb.jpg" width="200" /></a></p>
<p>Overall, the new Colorado transplants did an awesome job of braving the weather and altitude.</p>
<p>It's no secret that we love to play&nbsp;<a href="http://www.flickr.com/photos/viget/sets/72157625207959226/" target="_blank">paintball</a> at Viget so we knew that laser tag would be no different. Falls Church ventured out to <a href="http://shadowlandadventures.com/chantilly_banquet_rooms_halls_maryland_virginia_md_va.php" target="_blank">Shadowland Adventures</a> in Chantilly, VA for an afternoon of laser-filled fun. They were briefed, <a href="http://www.flickr.com/photos/viget/6766593731/in/set-72157629042717777" target="_blank">suited up</a>, and got their game faces on.</p>
<p><a href="http://www.flickr.com/photos/viget/6766593241/in/set-72157629042717777" target="_blank"><img alt="Game faces" height="266" src="http://farm8.staticflickr.com/7032/6766593241_b5e233e618.jpg" width="400" /></a></p>
<p>They <del>ran around aimlessly shooting each other</del> played 4 rounds, each with different rules, but with one common goal - shoot as many people as possible and not get hit.</p>
<p><a href="http://www.flickr.com/photos/viget/6766594541/in/set-72157629042717777" target="_blank"><img alt="Steve about to shoot Andy" height="266" src="http://farm8.staticflickr.com/7157/6766594541_d02934984e.jpg" width="400" /></a></p>
<p>They play with absolutely no mercy.</p>
<p><a href="http://www.flickr.com/photos/viget/6766600237/in/set-72157629042717777" target="_blank"><img alt="Team shooting Rob" height="266" src="http://farm8.staticflickr.com/7148/6766600237_77632287ce.jpg" width="400" /></a></p>
<p>Durham's event was just 0.4 miles down the road from the office at <a href="http://www.sevenstarscycles.com/" target="_blank">Seven Stars Cycle</a> bicycle shop.  After the quarterly meeting and a quick game of Pong, they skipped hand-in-hand down Rigsbee Avenue in one big Vige-Parade. After a thorough lesson of changing a flat tire and basic bike anatomy, the team got to try their hands at changing their own flat tires. </p>
<p><a href="http://www.flickr.com/photos/viget/6771906203/in/set-72157629057289537/" target="_blank"><img alt="The guys change a flat tire" height="300" src="http://farm8.staticflickr.com/7026/6771906203_cbe1a94d1d.jpg" width="200" /></a><a href="http://www.flickr.com/photos/viget/6771908081/in/set-72157629057289537/" target="_blank"><img alt="Accomplished" height="300" src="http://farm8.staticflickr.com/7020/6771908081_daca5190bd.jpg" width="200" /></a></p>
<p>Then, teams of four were challenged to build a kid's bike from scratch with virtually no directions and guidance.  Each team elected 2 contestants for a relay race on the obstacle course, which consisted of a wheelie over a 2x4, up a steep incline, and then a final slalom through cement posts.</p>
<p><a href="http://www.flickr.com/photos/viget/6771911705/in/set-72157629057289537/" target="_blank"><img alt="Ready to race" height="266" src="http://farm8.staticflickr.com/7156/6771911705_bb608f5c38.jpg" width="400" /></a></p>
<p>In the end, we're not sure who won. However, the real winners will be the 3 lucky families that receive these bikes through Viget's donation to <a href="http://www.umdurham.org/" target="_blank">Urban Ministries</a> in downtown Durham. The day finished up with a few drinks and more pong at <a href="http://motorcomusic.com/" target="_blank">Motorco</a>.&nbsp;<a href="http://www.viget.com/about/team/zrobbins/" target="_blank">Zach</a> captured some of the best moments of Durham's event, especially the final relay race, which you can watch <a href="http://vimeo.com/35998924" target="_blank">here</a>.</p>
<p><img alt="Racing Team" height="266" src="http://farm8.staticflickr.com/7153/6771912417_ee474b997c.jpg" width="400" /></p>
      ]]></content>
    </entry>

    <entry>
      <title>Pep Rallies for Projects</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/pep-rallies-for-projects/" />
      <id>tag:viget.com,2012:blog/24.2346</id>
      <published>2012-01-31T14:48:00Z</published>
      <updated>2012-01-31T17:38:57Z</updated>
      <author>
            <name>Kevin Powers</name>
            <email>kevin.powers@viget.com</email>
                  </author>

      <category term="General"
        scheme="http://www.viget.com/blog/category/general/"
        label="General" />
      <content type="html"><![CDATA[

                 <p>Most new projects are inherently exciting; but, you can't always (nor should you) rely on the freshness of work to crystallize enthusiasm and optimism amongst your team. And that's important. Equal to getting a contract signed and the right boxes checked is knowing that your team is looking forward to the next several months working with this new client. Somewhere between setting up Basecamp and planning the kick-off meeting, take a moment to think of clever, fun ways to make the start of your project unique and inspiring.</p>                 <p style="text-align: left;">One approach we have used recently at Viget: <strong>Fields Trips</strong>. Having been awarded some really exciting new work, we sent our project teams on a topical afternoon excursion. The Falls Church team ventured down to the <a href="http://nationalzoo.si.edu/" target="_blank">National Zoo</a>, while our Durham folks took a behind-the-scenes tour of the <a href="http://lemur.duke.edu/" title="Duke Lemur Center" target="_blank">Duke Lemur Center</a>. The trip was, of course, related to the upcoming project -- but it wasn't a working event, per se. The goal for this activity was two-fold:</p>
<ol>
<li><strong>Get the team excited about the work and client</strong></li>
<li><strong>Get the team excited about the team</strong></li>
</ol>
<p><img alt="Panda at the National Zoo" height="356" src="http://www.viget.com/uploads/image/viget-zoo-panda.jpg" title="Panda at the National Zo" width="455" />
<img alt="Viget Team at the National Zoo" height="356" src="http://www.viget.com/uploads/image/viget-zoo-team.jpg" title="Viget Team at the National Zoo" width="455" /></p>
<p>The latter point is another area that is often overlooked. Team dynamics are just as critical to helping or hurting a project. Getting your team outside of the office and into a social setting (beyond happy hours) can go a long way toward fostering camaraderie and commitment.</p>
<p style="text-align: left;"><img alt="Duke Lemur Center" height="550" src="http://www.viget.com/uploads/image/viget-lemur.jpg" title="Duke Lemur Center" width="455" /></p>
<p>Another tactic we used to get folks excited about this new work: <strong>Shared Workspace</strong>. This depends on your office set up, but try carving out a dedicated space in which the team can work and make it their own. We told our team the space was theirs for the next several months and they could even decorate it as they see fit. There are rumors walls will be painted sometime soon.</p>
<p>While certainly more fun than, say, creating a budget sheet, these activities should still be viewed through a productive lens. But if you can lay the foundation of shared excitement early on, you'll be surprised how much that pays off down the line.</p>
      ]]></content>
    </entry>

    <entry>
      <title>Picking the Perfect Palette</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/inspire/picking-the-perfect-palette/" />
      <id>tag:viget.com,2012:inspire/8.2344</id>
      <published>2012-01-23T15:45:00Z</published>
      <updated>2012-01-23T19:27:37Z</updated>
      <author>
            <name>Mark Steinruck</name>
            <email>mark.steinruck@viget.com</email>
                  </author>

      <category term="General"
        scheme="http://www.viget.com/blog/category/general/"
        label="General" />
      <content type="html"><![CDATA[

                 <p>I recently visited a friend who was having some rooms painted. The walls of the living room looked like a patchwork quilt with daubs of various paint colors all over the wall. "I can't make up my mind," my friend said in response to the giant grin on my face.</p>
<p>My friend's dilemma is typical when starting a new project. Whether you're painting a room or designing a website, it can be a challenge to select the perfect color combination. Rather than getting into the process of color selection, I'm going to focus on some resources and techniques that can help make the job a little easier.</p>                 <h3><a href="http://kuler.adobe.com/" title="kuler">kuler</a></h3>
<p><img alt="Kuler" height="300" src="http://www.viget.com/uploads/image/color/kuler.jpg" title="Kuler" width="438" /></p>
<p>Kuler is an amazing tool by Adobe that allows you to explore, create, and share color palettes. The growing community of designers that have embraced kuler has made it a rich resource for inspiration. </p>
<p>Take some time to dig into the Create section. It takes a little practice to use the interface, but it's worth the effort. There's also an option to upload an image and select five individual points in the photo to generate your palette. Then you can then save, tag, and share your palette with the entire community. </p>
<p>Both Photoshop and Fireworks include <em>kuler</em> as an extension. You can perform many of the same functions in the panel, including searching by keyword. It can be found in both applications under Window &gt; Extensions. </p>
<p>&nbsp;</p>
<h3><a href="http://www.colourlovers.com/" title="ColourLovers">COLOURlovers</a></h3>
<p><img alt="Colourlovers" height="300" src="http://www.viget.com/uploads/image/color/colourlovers.jpg" title="Colourlovers" width="438" /></p>
<p>This is also a great community site that has expanded beyond just color palettes. It now covers patterns, pattern templates, trends, and shapes, and it has lots of discussions and articles to fuel your creativity. The site says there are over 1.9 million user-created palettes in its database. That ought to keep you busy for a while.</p>
<p>I like searching palettes by keyword because I can quickly narrow down a few that fit my project. Sign up for an account, and there are great tools that allow you to interact with the community by creating and sharing your own color explorations. </p>
<p>&nbsp;</p>
<h3><a href="http://www.pinterest.com" title="Pinterest">Pinterest</a></h3>
<p><img alt="Pinterest" height="300" src="http://www.viget.com/uploads/image/color/pinterest.jpg" title="Pinterest" width="438" /></p>
<p>Okay, hang with me here. Pinterest is a little trendy, yes. And yes, there's a chance that you'll see a lot that you're not the least bit interested in. But in terms of finding a large variety of inspiration that is precisely related to a keyword or topic, I haven't found anything else that matches it. Trying doing a search for "warm color," and you'll end up with a menagerie of images like crayons, clothing, paintings, rooms, wedding cakes, wallpaper, flowers, and even some pre-defined color palettes. You may leave the site with more inspiration than just colors. </p>
<p>&nbsp;</p>
<h3>Photoshop + The Mosaic Filter</h3>
<p><img alt="Mosaic" height="583" src="http://www.viget.com/uploads/image/color/mosaic.jpg" title="Mosaic" width="438" /></p>
<p>After pulling some photo inspiration, I might click around using the eye dropper in Photoshop in an attempt to create a winning combination. Sometimes that works, but using the eye dropper tool, even set to 101 by 101 average, can sometimes be difficult. I like to see the colors side-by-side, so there has to be an easier way. </p>
<p>The Mosaic filter in Photoshop is the key. Open your image and adjust the pixel dimensions based on the number of color options you want to see. The larger the pixel dimensions, the greater the number of color swatches you'll get. I like to keep the largest measurement (height or width) between 500-1000 pixels. Any more than that, and you might as well just use the eye dropper tool. Now go to Filter &gt; Pixelate &gt; Mosaic and adjust the cell size. Remember that the larger the blocks are, the less color detail you'll get. (Sometimes this is a good thing.)</p>
<p>Note: I looked for a way to replicate this effect in Fireworks, but the filter options are limited. If anyone knows of a way to do it, please leave a comment. </p>
<p>These are just a few of the many tools and techniques at our disposal. I'd love to hear what works for you. </p>
<p>&nbsp;</p>
      ]]></content>
    </entry>

    <entry>
      <title>&#45;webkit&#45;transform: kill&#45;the&#45;flash</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/inspire/webkit-transform-kill-the-flash/" />
      <id>tag:viget.com,2012:inspire/8.2340</id>
      <published>2012-01-19T16:24:00Z</published>
      <updated>2012-01-20T20:33:59Z</updated>
      <author>
            <name>Dan Tello</name>
            <email>dan.tell@viget.com</email>
                  </author>

      <category term="CSS"
        scheme="http://www.viget.com/blog/category/css/"
        label="CSS" />
      <content type="html"><![CDATA[

                 <p>This issue has been popping up all over the place lately. When hovering over elements with certain css3 transform properties set on the hover state, Chrome and Safari sporadically flash. Unless you're into causing seizures, this effect is probably not what you're going for.</p>
<p>To prevent the infamous black flash in Chrome and white flash in Safari, you need to set any element you plan on transforming in the future (like on :hover or with an added class) in 3d space from the start.</p>
<p>For Example:</p>
<pre>.item {
  -webkit-transform: translateZ(0);
}

.item:hover {
  -webkit-transform: scale(1.5);
}
</pre>
<p><strong>-webkit-transform: translate3d(0, 0, 0)</strong> will accomplish the same thing. The flash seems to occur when the browser switches to gpu accelerated rendering for an element. Thus, by giving the element a gpu accellerated property from the get-go, the browser does not have to switch in and out of rendering modes, and the flash is prevented.</p>
<p><strong>There is a downside.</strong></p>
<p>In Chrome, <em>without this fix</em>, if there is text inside of the element you are transforming, the text nicely re-renders when the transformation is done. <em>With the translateZ(0) fix</em>, the text is rasterized and stretched, causing things to get fuzzy. So say you scale some text up to 1.5 percent &mdash; you'll get something like this:</p>
<p><img height="196" src="http://www.viget.com/uploads/image/transform-downside.jpg" width="237" /></p>
<p><em>-webkit-</em><em>transform: scale(1.5) WITH the fix.</em></p>
<p>&nbsp;<img height="196" src="http://www.viget.com/uploads/image/transform-original.jpg" width="237" /></p>
<p><em>-webkit-transform: scale(1.5) WITHOUT the fix.</em></p>
<p>As you can see in the second image, the text properly re-renders when the transform is complete (in Chrome), where as the second image with the translateZ fix does not.&nbsp;Ultimately, translateZ does seem to be the lesser of 2 evils for now. <del>The good news is, that as of Chrome&nbsp;17.0.963.26 dev, I'm not seeing the flashing issue at all. Hopefully that means it's been addressed, and that the public release and Safari will soon follow suit.</del></p>                 
      ]]></content>
    </entry>

    <entry>
      <title>What is fb_xd_fragment and how can I make it go away from Google Analytics?</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/engage/fb-xd-fragment-how-can-i-make-it-go-away/" />
      <id>tag:viget.com,2012:engage/17.2339</id>
      <published>2012-01-13T14:00:00Z</published>
      <updated>2012-01-13T15:42:31Z</updated>
      <author>
            <name>Paul Koch</name>
            <email>paul.koch@viget.com</email>
                  </author>

      <content type="html"><![CDATA[

                 <p>Recently I was troubleshooting why <strong>?fb_xd_fragment=</strong> was getting appended to the end of a bunch of URLs in Google Analytics. With a little bit of googling, the source of the problem wasn&rsquo;t tough to find--it happens when a visitor using Internet Explorer clicks a Facebook &lsquo;Like&rsquo; button on your page.</p>
<p>Surprisingly, though, all of the <a href="http://www.catonthecouch.com/blog/2011/05/22/hiding-fb_xd_fragment-from-google-analytics/">highly</a> <a href="http://www.google.com/support/forum/p/Google%20Analytics/thread?tid=4092c51dede5579f&amp;hl=en">ranking</a> <a href="http://www.designerstalk.com/forums/help-me/61295-fb_xd_fragment.html">results</a> in Google give a GA solution that&rsquo;s flat-out wrong. Here&rsquo;s why:</p>                 <p>In a test we ran, clicking a Like button on /pageA showed two line items in Analytics:</p>
<ul>
<li>/pageA : 1 pageview (1 unique)</li>
<li>/pageA?fb_xd_fragment= : 4 pageviews (1 unique)</li>
</ul>
<p>PageA is a single page, so we want it to show up on a single line in GA. We also didn&rsquo;t view the page 5 total times -- so a fix needs to be made.</p>
<p>Other folks suggest that you exclude the fb_xd_fragment query parameter in your profile settings. The problem with this method: it doesn&rsquo;t exclude the entire page. Instead, it just strips off the parameter from the end of the URL and condenses the two URLs to a single line item. In doing this, it also sums their pageviews, which will give you wrong &lsquo;pageview&rsquo; and &lsquo;average-pages-per-visit&rsquo; data.</p>
<p>Since the page with the query parameter isn&rsquo;t a real view, don&rsquo;t just strip it -- exclude that page (and its corresponding metrics) entirely. This correct solution is equally as quick -- just go to Settings &gt; Filters &gt; New Filter and add the following Exclude filter (hover for a larger view):</p>
<p><img onmouseout="this.src='http://www.viget.com/uploads/image/fbxd.png';" onmouseover="this.src='http://www.viget.com/uploads/image/fbxd-lg.png';" src="http://www.viget.com/uploads/image/fbxd.png" /></p>
<p>Now you&rsquo;ll only see that single page and pageview, get more accurate data, and avoid&nbsp;<a href="http://www.youtube.com/watch?v=2F4uhUnvzZQ">getting duped</a>!</p>
<p>&nbsp;</p>
      ]]></content>
    </entry>

    <entry>
      <title>You Might Make a Great UX Designer At Viget If&#8230;</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/advance/you-might-make-a-great-ux-designer-at-viget-if/" />
      <id>tag:viget.com,2012:advance/12.2338</id>
      <published>2012-01-10T14:52:00Z</published>
      <updated>2012-01-10T16:07:36Z</updated>
      <author>
            <name>Laura Sweltz</name>
            <email>laura.sweltz@viget.com</email>
                  </author>

      <category term="General"
        scheme="http://www.viget.com/blog/category/general/"
        label="General" />
      <category term="UX"
        scheme="http://www.viget.com/blog/category/ux/"
        label="UX" />
      <content type="html"><![CDATA[

                 <p>&nbsp;</p>
<p>When I was a kid, I never thought to myself, "Man, when I grow up, I want to be a UX designer &hellip; " &nbsp;I'm not sure that the title even existed then. &nbsp;Yet, here I am, many years later, working as one at Viget. &nbsp;The different paths people take before they eventually determine this is the proper field for them are too numerous to count. &nbsp;While UX designers (or whatever official title is cool this week) come from all different backgrounds and educations, I think there are certain qualities many of them have that lead them down this particular path in the first place. &nbsp;These are qualities that I see in both myself and my fellow UX designers here at Viget. &nbsp;If you possess these qualities, you could be a good fit here, too. &nbsp;&nbsp;</p>
<h4>You might make a great UX designer at Viget if &hellip;</h4>                 <h5><strong><em>You enjoy people watching.</em></strong></h5>
<p>
Do you have an eagerness to understand the internal and external triggers that make people do what they do? &nbsp;Are you intrigued by human behavior? &nbsp;At the end of the day, we are designing for users. &nbsp;We need to have an understanding of human behavior and a desire to understand what people want to do and why. &nbsp;If you're not interested in that sort of thing, UX is not for you. &nbsp;</p>
<h5><strong><em>You like to make things better.</em></strong></h5>
<p>
When you see something that&rsquo;s poorly designed, does it drive you crazy? &nbsp;Are you constantly thinking of ways that you could improve the design of the things around you? &nbsp;A desire to make things more efficient and easier to use is important. &nbsp;</p>
<h5><strong><em>You communicate well. &nbsp;</em></strong></h5>
<p>
Whether you're speaking with your best friend or a stranger, you should be comfortable and capable of understanding what people are talking about and explaining things to them in a way that they can understand.&nbsp;</p>
<h5><strong><em>You are a quick and capable learner. &nbsp;</em></strong></h5>
<p>
You can dive head first into a new subject and learn about it quickly. &nbsp;Doing this doesn't even feel like work, because you're a curious individual who considers it fun to have the opportunity to learn something new. &nbsp;</p>
<h5><strong><em>You like to get to the root of a problem. &nbsp;</em></strong></h5>
<p>
Do you enjoy helping your friends figure out exactly what the cause of an issue is, in order to help them determine the best course of action? &nbsp;Are you the first one to break out a pros/cons list or a mind map to help them organize their thoughts? &nbsp;(By the way, I consider these to be perfectly acceptable social activities -- just ask my friends.) &nbsp;Problem solving is an important aspect of UX. &nbsp;We need to be able to help a client or our internal team define a problem so that we can come up with the proper solution. &nbsp;</p>
<h5><strong><em>You like to organize things.</em></strong></h5>
<p>
This doesn't necessarily mean that your desk isn't cluttered or that you can always find everything you&rsquo;re looking for, but having a natural inclination to bring order to things is important. &nbsp;As a UX designer, you need to be able to organize information in way that makes the consumption of that information easy for users. &nbsp;You also need to be able to bring order to the information overflow that comes at the beginning of a project when you start to meet with clients and stakeholders, review existing content, and conduct research.&nbsp;</p>
<h5><strong><em>You don't shy away from sketching. &nbsp;</em></strong></h5>
<p>
This doesn't mean that you are Picasso. &nbsp;If the farthest your sketches have gone are to your mom's fridge, that's perfectly okay. &nbsp;But, you should feel comfortable grabbing a pen or a dry erase marker, sketching out an idea, and sharing it with people.</p>
<h5><strong><em>You&rsquo;re happy to take the lead.</em></strong></h5>
<p>
You&rsquo;re not afraid to take charge of a meeting -- large or small. &nbsp;Whether it&rsquo;s through leading group exercises or simply just guiding the discussion, you are able to run an effective meeting.</p>
<h5><strong><em>You are able to balance the needs of many.</em></strong></h5>
<p>
Are you able to take the varying desires and needs of several people and bring the group to a consensus? &nbsp;Whether it's the needs of the client or business, the internal team, or the users, you should be able to help define solutions that you can stand behind as a designer, and that also meet the needs and please the various members of the team. &nbsp;This is not an easy task, but it is one that you must be able to handle.</p>
<h5><strong><em>You're a team player.</em></strong></h5>
<p>
You appreciate and understand the importance of the various parts of the web design process. &nbsp;You are able to work well with others and are excited to have the chance to collaborate &nbsp;-- whether it&rsquo;s with a visual designer, developer, project manager, or any other member of the team.</p>
<h5><strong><em>You want to help make the web great.</em></strong></h5>
<p>
Possessing these qualities is important, but it&rsquo;s equally as important to have an interest in and understanding of web technologies, as well as the desire and ability to craft experiences for the web.</p>
<p>&nbsp;</p>
<p>If you feel like you have the combination of the qualities above and a desire to create delightful online experiences, you might fit in well here at Viget. &nbsp;We&rsquo;re always looking for fresh talent to bring on board, whether you&rsquo;re a seasoned pro or just starting out. &nbsp;Think you have what it takes? &nbsp;Check out our <a href="http://www.viget.com/careers/ux-designer/" title="Viget - UX Designer" target="_blank">full-time</a> and <a href="http://www.viget.com/careers/summer-2012-user-experience-intern/" title="Viget - UX Internship" target="_blank">internship</a> opportunities. &nbsp;We&rsquo;d love to talk to you. &nbsp;</p>
      ]]></content>
    </entry>

    <entry>
      <title>Tips for Writing Better Bug Reports</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/extend/tips-for-writing-better-bug-reports/" />
      <id>tag:viget.com,2012:extend/4.2335</id>
      <published>2012-01-06T12:20:00Z</published>
      <updated>2012-01-06T14:21:06Z</updated>
      <author>
            <name>Josh Korr</name>
            <email>josh.korr@viget.com</email>
                  </author>

      <category term="Tips and Tricks"
        scheme="http://www.viget.com/blog/category/tips_and_tricks/"
        label="Tips and Tricks" />
      <content type="html"><![CDATA[

                 <p>Though we might wish otherwise, bugs (or, more generally, defects) are a fact of life in software&nbsp;development.&nbsp;Unfortunately for developers, so are unhelpful and infuriating bug reports.</p>
<p>Bad bug reports waste time and money while everyone goes back and forth to clarify the necessary details. Perhaps worse, bad bug reports tug at&nbsp;developers' sanity and can put strain on the team dynamic.</p>
<p>I know this from experience -- not as a&nbsp;developer, but as a bug reporter who has infuriated plenty of developers in my time as a product/project manager. Because I love my&nbsp;dev colleagues, I've tried hard to improve my bug reporting. Here are some tips I've come up with along the way for writing better bug reports:</p>
<ul>
<li>The first step is changing how you think about experiencing bugs, so you can report them in sufficient detail.</li>
<li>Next, be as specific as possible in providing that detail.</li>
<li>Finally, always try to reproduce a bug before you report it.</li>
</ul>
<p>Let's look at each of those tips in depth.</p>                 <h3>Tip No. 1: Change Your Mental Process</h3>
<p>The two most common, but least helpful, bug reports are "X is broken" and "X is not working." These are unhelpful because they don't provide enough detail to understand what the problem is -- "broken" and "not working" could mean any number of things -- and don't explain how the user arrived at this unspecified problem.</p>
<p>This type of bad bug report is unfortunately common because our default mental process when encountering a bug -- or any life experience, for that matter -- is different from the mental process needed to write a good bug report.</p>
<p>The act of experiencing a bug can be broken down into three parts:</p>
<ul>
<li>Steps: The specific series of steps or actions that the user took up until encountering the problem.</li>
<li>Expected result: What the user expected would occur after the step that immediately preceded the problem.</li>
<li>Actual result: What actually occurred after that final step/action.</li>
</ul>
<p>Any good bug report should provide details on all three parts.&nbsp;The problem for bug report recipients is that people don't mentally experience bugs in those terms.</p>
<p>Mentally, we elide the multiple discrete steps that make up any experience, whether in the real world or on a computer. We think, "I turned on the car," rather than, "I inserted the key into the ignition, depressed the brake, and turned the key three clicks to start the engine." We say, "I checked my email," rather than, "I typed 'www.gmail.com' into the web address bar; then I entered my username and password, checked 'Stay signed in', and clicked the 'Sign in' button; then I clicked the 'Important' subnav link in the left sidebar."</p>
<p>Describing experiences in the latter way sounds weird at first, like you're being overly literal or robotic. But if you want to write better bug reports, you must train yourself to think in this way. Without all of these discrete, specific details, it's difficult to accurately diagnose and fix a bug.</p>
<p>The steps&nbsp;are important to document because a problem may be different depending on the steps a user took before encountering it, and because the details allow the bug fixer to try to reproduce the problem exactly as the reporter experienced it. For example, a client recently reported that a particular URL was redirecting users to the site homepage when viewed on a mobile device. I tested by entering the URL in mobile browsers' address bars but could not reproduce the redirect. It turned out the client experienced the bug not after entering the URL in the mobile browser address bar, but rather after scanning a QR code. Knowing those details about the steps taken made it easy to figure out that the issue was with the QR code, not with the underlying URL.</p>
<p>The expected result is important to document so the bug fixer can determine whether the bug is in fact occurring as the reporter described and&nbsp;can tell when the bug is fixed. And the actual result is important to document&nbsp;so the bug fixer knows what problem to look for, and because the actual result may be an error message that includes key information for diagnosing the bug.</p>
<h3>Tip No. 2: Be Specific</h3>
<p>Once you've started to think of a bug encounter in terms of these three distinct parts, the most important thing you can do is be specific when reporting each part.</p>
<p>To illustrate this, consider&nbsp;a sort of non-software bug report that you've probably encountered in some fashion: your grandparents call and tell you, "I turned on the TV and it didn't work."</p>
<p>Here are some possible scenarios this vague report could be describing:</p>
<ul>
<li>Grandpa pressed the TV's "on" button and the TV did not turn on.&nbsp;Problem: TV is not plugged in.</li>
<li>Grandma pressed the TV remote control's "on" button and the TV did not turn on. Problem: the remote's batteries are out of juice.</li>
<li>Grandma pressed the DVD player remote's "on" button and the TV did not turn on. Problem: Grandma's using the wrong remote.</li>
<li>Grandpa successfully turned on the TV but the screen is black. Problem: cable box is not turned on.</li>
<li>Grandpa successfully turned on the TV but there's no sound. Possible problems: TV is on mute; sound system is not plugged in or not turned on; Grandpa is not watching a "talkie" like he thought.</li>
</ul>
<p>From the original report, it's impossible to tell which scenario your grandparents have encountered. If Grandpa were more specific about the three parts of the "bug" experience, you would have a much easier time diagnosing the problem.</p>
<p>Turning back to software, here are some ways to be specific in bug reports to avoid the grandparents scenario:</p>
<ul>
<li>Break down the experience into granular steps
<ul>
<li>Again, you need to retrain your mental process to identify the discrete steps you took before encountering the bug. Be reasonable -- you don't have to start with "I woke up this morning and had coffee" -- but thorough.</li>
</ul>
</li>
<li>List URLs
<ul>
<li>Because different people refer to pages in different ways -- sometimes by the page's title, sometimes by an idiosyncratic personal nickname for the page -- it's always best to include the URL of any page you refer to in a bug report. It's okay to also include the page name (or whatever you call the page), but always couple that with the page's URL.</li>
</ul>
</li>
<li>Provide user account details, if any
<ul>
<li>If a site has multiple user roles, a bug may be specific to a particular user role. So if you were logged in when you experienced the bug, provide login details. If you don't want to share your password, at least provide the account email/username.</li>
</ul>
</li>
<li>Provide screenshots
<ul>
<li>Screenshots are a super-helpful supplement to written details. Sometimes it's extra helpful to annotate the screenshot (or just circle the relevant portion, if it's not obvious) using <a href="http://skitch.com/" target="_blank">Skitch</a> or a similar tool.</li>
</ul>
</li>
<li>Provide error details
<ul>
<li>If the bug included an error message, provide as much of the error text as possible. You can provide a screenshot, cut-and-paste text, or a link to the relevant page on a bug-tracking site, if your site is using <a href="http://airbrakeapp.com/pages/home" target="_blank">Airbrake</a> or a similar tool.</li>
</ul>
</li>
<li>Provide browser and operating system details</li>
</ul>
<p>You don't have to provide all of these details for every bug report; browser and OS can be more important to provide for front-end issues, for example, and screenshots aren't always needed if your other details are sufficient. But the more details you routinely provide, the more your&nbsp;developers will thank you.</p>
<h3>Tip No. 3: Try to Reproduce</h3>
<p>It's also helpful to try to reproduce a bug before you submit a bug report. For one thing, sometimes random glitches just happen -- maybe an update was being deployed right as you were doing something; maybe your browser crapped out on you. Sometimes you may actually be doing it wrong.</p>
<p>When you do come across a persistent bug, reproducing it will help you be specific about the three steps.&nbsp;When you experience a bug the first time, chances are you don't remember exactly what you did leading up to the bug. Trying to reproduce the bug lets you take solid notes on the exact steps and grab screenshots if needed.</p>
<h3>Anatomy of a Bug Report</h3>
<p>Let's look at a sample (made up) bug report. First, the bad versions: "The Viget.com Extend blog is not working," or "The links on Extend blog posts are broken."</p>
<p>Now here's a more helpful version of these bug reports:</p>
<blockquote>
<p>Overview: The headlines on all posts on the Viget.com Extend blog index page appear to be linked to www.viget.com rather than to the individual blog post page.</p>
<p>Tested browser and OS: Chrome&nbsp;16.0.912.63, Mac OSX</p>
<p>Steps to reproduce:</p>
<ul>
<li>Went to www.viget.com/extend</li>
<li>Clicked the "Preventing Broken Windows" headline</li>
<li>Expected result: I am taken to the "Preventing Broken Windows" blog post page (www.viget.com/extend/preventing-broken-windows/)</li>
<li>Actual result: I was taken to www.viget.com</li>
</ul>
</blockquote>
<p>I usually add an overview at the top of my bug reports, to provide some immediate context and a summary of what I think the issue is. Sometimes the overview is a little vague and other times it repeats part of the steps to reproduce, but that's okay as long as the steps are sufficiently detailed. (I tend to leave out the overview if the bug is discrete and obvious.)</p>
<p>If the report includes user roles, I list those details either separately above the steps to reproduce, or as the first step.</p>
<h3>Sweat the Details, Not the Format</h3>
<p>The exact format of your bug reports isn't important; you can figure out what works best for you and your&nbsp;devs. The important thing is that you start thinking about experiencing bugs in a different way, and that you respect your developers' time enough to try to reproduce a bug and collect sufficient details yourself before sending over the bug report.</p>
<p>Now let's hear your tips for writing better bug reports!</p>
      ]]></content>
    </entry>

    <entry>
      <title>Lenovo Blogs and Social: A New Connection for Those Who &#8220;Do&#8221;</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/lenovo-blogs-and-social-a-new-connection-for-those-who-do/" />
      <id>tag:viget.com,2012:blog/24.2282</id>
      <published>2012-01-03T13:17:00Z</published>
      <updated>2012-01-03T15:16:32Z</updated>
      <author>
            <name>Jillian Kuhn</name>
            <email>jillian.kuhn@viget.com</email>
                  </author>

      <category term="Clients"
        scheme="http://www.viget.com/blog/category/clients/"
        label="Clients" />
      <category term="Site Launches"
        scheme="http://www.viget.com/blog/category/site_launches/"
        label="Site Launches" />
      <content type="html"><![CDATA[

                 <p style="text-align: left;">2011 was a banner year for Lenovo. This international tech company was crowned the #3 global PC maker, rolled out a snazzy new brand campaign (have you seen its&nbsp;<em><a href="http://youtu.be/Cs-y2M1xGyA" title="Lenovo YouTube For Those Who Do campaign">For Those Who Do</a></em>&nbsp;ads?), <em>and</em> partnered with Viget to launch the new Lenovo <a href="http://blog.lenovo.com/" title="Lenovo Blogs and Social: A New Connection for Those Who &quot;Do&quot;">Blogs</a>&nbsp;and <a href="http://social.lenovo.com/" title="Lenovo Social">Social</a> pages.</p>
<p style="text-align: left;"><strong><img alt="Lenovo Social homepage" height="348" src="http://www.viget.com/uploads/image/LenovoSocial.png" title="Lenovo Social homepage" width="430" /></strong></p>
<p style="text-align: center;"><em>The new Lenovo Social homepage&nbsp;</em></p>
<p>Our goal for this redesign was to centralize Lenovo's existing blogs and social media in an engaging, navigable, and branded way, using one easily maintainable CMS. This would solve a few of the old sites' big problems:</p>
<ol>
</ol>                 <ol>
<li>Their dated designs no longer aligned with the brand's message or high-tech look.</li>
<li>It was difficult to make quick edits to the site and to manage so many authors.</li>
<li>The Blogs section was divided into nine separate, ambiguously-named blogs, making it difficult for users to find relevant content.</li>
</ol>
<p>The new Blogs and Social pages solve problem #1 through a gorgeous look and feel that really matches the brand. Check out the new <a href="http://blog.lenovo.com/" title="Lenovo Blog homepage">Blogs</a>&nbsp;homepage as an example:</p>
<p style="text-align: left;"><img alt="Lenovo Blog homepage" height="348" src="http://www.viget.com/uploads/image/LenovoBlogs.png" title="Lenovo Blog homepage" width="430" /></p>
<p style="text-align: left;">To tackle problem #2, we built the site using the&nbsp;<a href="http://expressionengine.com/" title="ExpressionEngineCMS">ExpressionEngine</a>&nbsp;CMS.&nbsp;Now, the Lenovo team can quickly jump in to the back-end of the site to manage blog content, and each contributing author gets his own account with unique permissions to access the content areas relevant to him. We also set up easily curated social media feeds and different languages for Lenovo's worldwide audience.</p>
<p>We addressed problem #3 by reorganizing the Blogs structure. We created a new tagging schema that de-compartmentalizes blog topics and makes it easier for users to find content. Now, users can click through all blog posts in one place; plus, they can filter by topics, products, recency, or popularity.</p>
<p><img alt="Lenovo Blog popular topics" height="47" src="http://www.viget.com/uploads/image/LenovoTaggingSchema.png" title="Lenovo Blog popular topics" width="430" /></p>
<p><span>Such a high-tech, high-energy company needs a web site that can keep up with it, and the new&nbsp;Lenovo&nbsp;</span><a href="http://blog.lenovo.com/" title="Lenovo Blogs and Social: A New Connection for Those Who &quot;Do&quot;">Blogs</a><span>&nbsp;and&nbsp;</span><a href="http://social.lenovo.com/" title="Lenovo Social">Social</a><span>&nbsp;pages are certainly up to the task! We hope they serve Lenovo well, and many thanks to Erik, Nano, and the rest of the team for a fun, successful project!</span></p>
      ]]></content>
    </entry>

    <entry>
      <title>Background&#45;clip, Text&#45;shadow, &amp; Gradients; Oh My!</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/inspire/background-clip-text-shadow-gradients/" />
      <id>tag:viget.com,2011:inspire/8.2331</id>
      <published>2011-12-29T13:00:00Z</published>
      <updated>2012-01-02T18:45:41Z</updated>
      <author>
            <name>Trevor Davis</name>
            <email>trevor.davis@viget.com</email>
            <uri>http://www.viget.com/about/team/tdavis</uri>      </author>

      <category term="CSS"
        scheme="http://www.viget.com/blog/category/css/"
        label="CSS" />
      <category term="Tips and Tricks"
        scheme="http://www.viget.com/blog/category/tips_and_tricks/"
        label="Tips and Tricks" />
      <content type="html"><![CDATA[

                 <p>I&rsquo;ve had a couple of designs recently where I have been able to play around with <strong>background-clip: text</strong> in combination with text-shadow and gradients, and I wanted to share my experience.</p>
<p>Before we get too far, <strong>background-clip: text</strong> is not supported in all browsers. I believe it is still only supported in Webkit browsers, so make sure you have sufficient fallbacks. The demos on this page will also only show up with all the fanciness in webkit, so I&rsquo;ll wait for you to switch over.</p>
<p>Okay, ready?</p>                 <h3>First example: background-clip + text-shadow</h3>
<p>
<img alt="Background clip end result" height="100" src="http://viget.com/uploads/file/background-clip/bg-clip-demo-1.png" width="365" /></p>
<p>The image above is an example of the heading I needed to create. It has a gradient over the text and a box shadow behind it. Since these headings were going to be custom controlled by the CMS, we didn't want them to be images. CSS3 to the rescue!</p>
<p>First, we start by adding a CSS3 gradient as the background.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/9yAys/6/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  background-image: -webkit-gradient(linear, 50% 0%, 50% 100%, color-stop(0%, #ffffff), color-stop(100%, #91a9cb));
  background-image: -webkit-linear-gradient(#ffffff,#91a9cb);
}</pre>
<p>Next, we add background-clip and a text fill color. This is also a good opportunity to add a fallback text color for browsers that don&rsquo;t support <strong>background-clip: text</strong>.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/9yAys/10/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  background-image: -webkit-gradient(linear, 50% 0%, 50% 100%, color-stop(0%, #ffffff), color-stop(100%, #91a9cb));
  background-image: -webkit-linear-gradient(#ffffff,#91a9cb);
  -webkit-background-clip: text;
  -webkit-text-fill-color: transparent;
  color: #fff;
}</pre>
<p>We are looking pretty good so far, now we just needed to add a text-shadow.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/9yAys/11/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  background-image: -webkit-gradient(linear, 50% 0%, 50% 100%, color-stop(0%, #ffffff), color-stop(100%, #91a9cb));
  background-image: -webkit-linear-gradient(#ffffff,#91a9cb);
  -webkit-background-clip: text;
  -webkit-text-fill-color: transparent;
  color: #fff;
  text-shadow: 6px 6px 9px rgba(0, 0, 0, 0.33);
}</pre>
<p>Doesn&rsquo;t look exactly as we wanted. It might be hard to tell, but since we set the text to have a transparent fill-color, the text-shadow bleeds through. I then decided that this would be a good opportunity to use a data attribute &amp; generated content to duplicate the text and position it behind the gradiated text.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/9yAys/15/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>&lt;h1 data-text="Oh heeey!"&gt;Oh heeey!&lt;/h1&gt;</pre>
<pre>h1 {
  background-image: -webkit-gradient(linear, 50% 0%, 50% 100%, color-stop(0%, #ffffff), color-stop(100%, #91a9cb));
  background-image: -webkit-linear-gradient(#ffffff,#91a9cb);
  -webkit-background-clip: text;
  -webkit-text-fill-color: transparent;
  color: #fff;
  position: relative;
}
h1:after {
  background: none;
  content: attr(data-text);
  left: 0;
  position: absolute;
  text-shadow: 6px 6px 9px rgba(0, 0, 0, 0.33);
  top: 0;
  z-index: -1;
}</pre>
<p>That looks pretty great and has fallback for other browsers. Success!</p>
<h3>Second example: background-clip + generated content</h3>
<p>
<img alt="Background clip end result" height="100" src="http://viget.com/uploads/file/background-clip/bg-clip-demo-2.png" width="359" /></p>
<p>In this example, we flip what we did in the first and use background-clip on the generated content. This image above shows what we need the end result to look like.</p>
<p>First, we just style how we want the heading to look.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/N6f6m/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  color: #fff;
  font: 52px/52px Georgia, Times, serif;
  text-transform: uppercase;
}</pre>
<p>Next, let&rsquo;s use generated content and add a background image.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/N6f6m/1/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>&lt;h1 data-text="Hey buddy!"&gt;Hey buddy&lt;/h1&gt;</pre>
<pre>h1 {
  color: #fff;
  font: 52px/52px Georgia, Times, serif;
  position: relative;
  text-transform: uppercase;
}
h1:after {
  background: url(images/structure/bg-heading-diag.png);
  content: attr(data-text);
  color: transparent;
  left: 4px;
  position: absolute;
  top: 4px;
  z-index: -1;
}</pre>
<p>Then, let&rsquo;s add background-clip to that bro.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/N6f6m/2/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  color: #fff;
  font: 52px/52px Georgia, Times, serif;
  position: relative;
  text-transform: uppercase;
}
h1:after {
  background: url(images/structure/bg-heading-diag.png);
  -webkit-background-clip: text;
  content: attr(data-text);
  color: transparent;
  left: 4px;
  position: absolute;
  top: 4px;
  z-index: -1;
}</pre>
<p>Finally, since <strong>background-clip: text</strong> doesn&rsquo;t work in non-webkit browsers, we will need to add some sort of check to test if it&rsquo;s webkit or not. When I previously checked, there was no way of testing if a certain value was supported for a property, so I just rolled with the <a href="http://api.jquery.com/jQuery.browser/">jQuery browser object</a>.</p>
<pre>if($.browser.webkit) {
  $('html').addClass('webkit');
}</pre>
<p>Then, we just need to modify the styling of our generated content a bit to have a solid color for non-webkit browsers.</p>
<p>
<iframe frameborder="0" src="http://jsfiddle.net/trevor_davis/N6f6m/4/embedded/result" style="width: 100%; height: 300px;"></iframe></p>
<pre>h1 {
  color: #fff;
  font: 52px/52px Georgia, Times, serif;
  position: relative;
  text-transform: uppercase;
}
h1:after {
  color: #948972;
  content: attr(data-text);
  left: 2px;
  position: absolute;
  top: 2px;
  z-index: -1;
}
.webkit h1:after {
  background: url(images/structure/bg-heading-diag.png);
  -webkit-background-clip: text;
  color: transparent;
  left: 4px;
  top: 4px;
}</pre>
<p>And that&rsquo;s it! Just a few tricks I&rsquo;ve come across while playing with this stuff on some projects. Let me know if you all have any other tricks with <strong>background-clip</strong>.</p>
      ]]></content>
    </entry>

    <entry>
      <title>How Google Turned SEO Upside Down in 2011</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/engage/how-google-turned-seo-upside-down-in-2011/" />
      <id>tag:viget.com,2011:engage/17.2333</id>
      <published>2011-12-22T18:38:00Z</published>
      <updated>2011-12-22T19:50:03Z</updated>
      <author>
            <name>Zach Robbins</name>
            <email>zach.robbins@viget.com</email>
                  </author>

      <content type="html"><![CDATA[

                 <p><img alt="Google Panda" height="140" src="http://www.viget.com/uploads/image/google-panda.jpeg" style="float: left;" title="Google Panda" width="140" />In April of this year, Google began updating their search algorithms with something called "Panda." These effects have been more fully integrated throughout the year. In the world of SEO, this update represents a greater movement towards human accessibility and usability and away from machine oriented language (such as meta tags, keywords, etc.).</p>
<p>Panda utilizes thousands of ratings from human quality raters that provide answers to simple questions on the quality of the websites they visit. These questions include anything from "Would you trust this website to prescribe pharmaceutical drugs to your children?" and "Were you engaged by the content on this site?" to "Would you ever revisit this site?" These questions focus on visual design, user experience, and original content, more so than any other algorithms have previously measured. Based on the quality raters' answers to these questions, Google determined trends that re-ranked thousands of websites. These re-rankings hurt thousands of "content and link farms" which used traditional SEO tricks to boost rankings. Specifically, these sites suffered due to the following qualities:</p>
<ol>
<li><strong>Template footprint leaving a low ratio of original content&nbsp;</strong></li>
<li><strong>Empty content pages which exist simply to link to other pages&nbsp;</strong></li>
<li><strong>Overlapping and redundant articles&nbsp;</strong></li>
<li><strong>High advertisement ratio&nbsp;</strong></li>
<li><strong>Affiliate links and auto generated content</strong></li>
</ol>
<p>On the flipside, these re-rankings benefited well-designed and usable sites that decreased user confusion and were designed from a human point of view.</p>
<p>A practical example is Google's new functionality to block all results from a certain site. This allows them to track the meaning of bounces off search results. They can then use public users' own "quality ratings" by taking into account the amount of blocks any site has received, relevant to certain keywords.</p>
<p style="text-align: center;"><img alt="Panda Results" height="85" src="http://www.viget.com/uploads/image/panda-result.png" title="Panda Results" width="400" /></p>
<p style="text-align: left;">As Panda becomes more sophisticated and robust, SEO is becoming less focused on writing and designing for machines, and more focused on <strong>writing and designing for humans</strong>. Viget fully believes this is a great change for the web community and embraces the ways in which new algorithms will rank websites.</p>
<p><strong>Bottom line</strong>: make sure your users are having great experiences, or it'll come back to bite you in search rankings.</p>                 
      ]]></content>
    </entry>

    <entry>
      <title>Reframing UX: It&#8217;s About Designing Products</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/advance/reframing-ux-its-about-designing-products/" />
      <id>tag:viget.com,2011:advance/12.2330</id>
      <published>2011-12-16T21:42:00Z</published>
      <updated>2011-12-20T13:24:18Z</updated>
      <author>
            <name>Josh Korr</name>
            <email>josh.korr@viget.com</email>
                  </author>

      <category term="Product Design"
        scheme="http://www.viget.com/blog/category/product-design/"
        label="Product Design" />
      <category term="UX"
        scheme="http://www.viget.com/blog/category/ux/"
        label="UX" />
      <content type="html"><![CDATA[

                 <p>I'm in awe of my Viget colleagues, as I am of extraordinarily creative people generally. But I'm especially in awe of my user experience colleagues, and it took me a while to figure out why.</p>
<p>I blame the user experience community for this -- I think UX sells itself short.</p>
<p>Before I came to Viget, user experience seemed to me to be defined by its relationship to visual design and by its deliverables (wireframes, site maps, content inventory, etc.). But user experience at its core is not about visual design, wireframes, or content strategy as ends to themselves. User experience is about defining and designing products.</p>                 <h3>An idea is not a product</h3>
<p>The fundamental cause of poor web development is that people too often fail to realize an idea is not a product.</p>
<p>In the real world, we intuitively understand that an idea for a physical product is different from the product itself. Someone has to define the specific physical attributes, the features, the intended audience, the intended ways people will use the product -- all the stuff that comes before the product is manufactured.</p>
<p>Because web products are made of bits, and because the core tools of web design and development are available to anyone, it can be easy to think these steps aren't needed. Have an idea? Boom -- go build it.</p>
<p>But to be successful, a web product idea should go through all the same phases as a physical product before (and while) being built. That's what the user experience process is: all the stuff that turns an idea into a real web product.</p>
<h3>Reframing wireframes</h3>
<p>Wireframes, content strategy, etc., are of course important parts of that process. But they're important insofar as they constitute elements of holistic product design.</p>
<p>For example, wireframes don't just represent where things go on a page; they're not merely precursors to the visual design. They represent -- after all the brainstorming and sketching (if you're new school) or the requirements writing (if you're old school); after the audience profiling, information architecting, market research, and logic-trail exploring, if you do those sort of things -- which features will actually be built, and what the user will actually use.</p>
<p>What the user will use, plus the background functionality and processes that support this use but might be communicated outside wireframes, define what the product is. So I think of wireframes less as blueprints for visual design and more as blueprints for the product design -- blueprints embedded with all the thought and process that came before the UXer opened OmniGraffle (or another preferred wireframing/prototyping tool).</p>
<h3>Creativity and UX</h3>
<p>What really amazes me about the best UX designers is how effortlessly they do all of the above.</p>
<p>It's incredible to watch <a href="http://www.viget.com/about/team/lsweltz" target="_blank">Laura</a> or <a href="http://www.viget.com/about/team/kvigneault" target="_blank">KV</a> listen to a client's ideas, to user interviews, to internal brainstorms -- and then, often in real-time, filter and mentally transmogrify all of that into coherent, awesome, well-defined features and products. (I know the rest of our UX team is just as awesome, but I've only gotten to work with Laura and KV so far.)</p>
<p>That mental transmogrification has the same surreal alchemical quality that I see when our designers conjure up incredible mood boards and design comps out of little more than a client's free-associative, often ill-defined, feelings. It's pure creativity in action.</p>
<p>That's another way that I think UX is misunderstood. Because UX deliverables are usually (and purposely) not what we think of as visual art -- indeed, they often seem to involve cold logic and information processing -- UXers aren't necessarily seen as creative in the same way a visual designer is. But there's as much creativity and inspiration in the mental product design process as in any other artistic endeavor.</p>
<p>Deliverables document the results of that internal creative process (and of the external product design process), but the creative process itself is the unheralded heart of web product design.</p>
<p>So I'd encourage my UX colleagues, and the UX community at large, to reframe what they do and why they're so important. You guys know you're the heart of web product design. I wish there were a clearer way to let everyone else know that, too.</p>
      ]]></content>
    </entry>

    <entry>
      <title>Product Design and Development: Reshaping RoundPegg</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/product-design-and-development-reshaping-roundpegg/" />
      <id>tag:viget.com,2011:blog/24.2329</id>
      <published>2011-12-15T18:38:00Z</published>
      <updated>2011-12-15T19:39:12Z</updated>
      <author>
            <name>Jason Sperling</name>
            <email>jason.sperling@viget.com</email>
                  </author>

      <category term="Clients"
        scheme="http://www.viget.com/blog/category/clients/"
        label="Clients" />
      <content type="html"><![CDATA[

                 <p>We love working with entrepreneurs to make innovative ideas a reality. Earlier this summer we met the folks at <a href="http://roundpegg.com" target="_blank">RoundPegg</a>, a Boulder-based <a href="http://www.techstars.com" target="_blank">TechStars</a> alum, and were immediately excited by their vision: to optimize the hiring process and human interactions within the workplace through a combination of science and technology.</p>
<p>Although there's already a number of technology companies (<a href="http://www.gild.com/" target="_blank">Gild</a>, <a href="http://branchout.com/" target="_blank">BranchOut</a>, <a href="http://www.topprospect.com/" target="_blank">Top Prospect</a>, <a href="http://recruiting.jobvite.com/index_b.php" target="_blank">Jobvite</a>, <a href="http://www.jibe.com/" target="_blank">Jibe</a>, <a href="http://www.linkedin.com" target="_blank">LinkedIn</a>) focused on addressing human resources challenges, RoundPegg provides a unique and powerful tool set that we were happy to help expand and enhance. (Check out these quick video introductions to two of RoundPegg's tools: <a href="http://www.roundpegg.com/products-hire-guide.html" target="_blank">pre-hire assessments</a> and <a href="http://www.roundpegg.com/products-culture-gap.html" target="_blank">company culture surveys</a>.)</p>
<p>Last week RoundPegg launched the update to its product that we helped design and develop. Here's a closer look at the process.</p>                 <p>First, our user experience team worked with RoundPegg to update, design, and develop the user interface of its core product. We began by reviewing the existing application, use cases, and new product goals.</p>
<h3>Before</h3>
<p><img src="http://www.viget.com/uploads/image/RoundPegg-03_thumb.jpg" width="420" /></p>
<p><br />From there, our UX designers created wireframes for key screens of the application, working hand-in-hand with the RoundPegg team to ensure business goals were met and that the new interface would be supported by the back-end application.</p>
<h3>Wireframe Example</h3>
<p><img alt="RoundPegg Moodboard" src="http://www.viget.com/uploads/image/roundpegg-wireframes-r3-2.png" width="420" /></p>
<p><br />In parallel, our design team explored a new visual direction for the product. Because RoundPegg had an existing brand, the new user interface design had to maintain a cohesive overall feel while also establishing a fresh new visual language. Our visual design work began with two mood boards where we explored colors, typography, tone, and other visual themes.</p>
<h3>Moodboard Example</h3>
<p><img src="http://www.viget.com/uploads/image/roundpegg-moodboard-1.jpg" width="420" /></p>
<p><br />Once the general visual language was finalized, we moved into designing visual comps for the screens we had wireframed. We completed visual design by creating a style guide so the RoundPegg team could easily extend the new visual design across the platform.</p>
<h3>Design Comp Example</h3>
<p><img src="http://www.viget.com/uploads/image/roundpegg_2_thumb.jpg" width="420" /></p>
<p>With well-thought-out interface design in hand, we began HTML/CSS/JavaScript build-out of key pages and a style guide. The final set of deliverables was a nicely assembled package of pages ready to be integrated with the Ruby back-end and a new visual design with accompanying style guides to make it easy for RoundPegg's team to use in the future.</p>
<p>Working with the RoundPegg team has been great. We're excited to see their continued growth and evolution!</p>
<div><br /></div>
<p>&nbsp;</p>
      ]]></content>
    </entry>

    <entry>
      <title>It’s Cold. Warm Up With Vigetreats.</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/its-cold-warm-up-with-vigetreats/" />
      <id>tag:viget.com,2011:blog/24.2328</id>
      <published>2011-12-13T15:38:00Z</published>
      <updated>2011-12-16T22:32:03Z</updated>
      <author>
            <name>Brian Wynne Williams</name>
            <email>brian.williams@viget.com</email>
            <uri>http://www.viget.com/about/team/bwilliams</uri>      </author>

      <category term="General"
        scheme="http://www.viget.com/blog/category/general/"
        label="General" />
      <content type="html"><![CDATA[

                 <p>At Viget, we consider ourselves craftsmen (or, craftswomen as the case may be).  We spend all year crafting digital stuff: web products, mobile apps, online campaigns.  All cool work that we love -- but, other than an occasional <a href="http://www.flickr.com/photos/viget/6522819487/in/set-72157622860941993">awesome t-shirt</a>&nbsp;--&nbsp;it's all 1s and 0s.  Sometimes it's nice to hold things.</p>
<p>Years ago, we decided it would be fun to come together once each year as a team and get crafty in the more literal sense by making something with our bare hands to share with family and friends around the holidays.  With <a href="http://vigorbalm.com">VigorBalm</a>, a holiday tradition was born.  Each winter since, we start by brainstorming ideas for the Viget holiday project.  This year, ideas included magnets, snow globes, and superballs; but, we settled on a holiday favorite everyone shares: hot cocoa (with marshmallows of course).</p>
<p><a href="http://www.flickr.com/photos/viget/6496998265/in/set-72157628348162219"><img alt="Vigetreats" height="293" src="https://lh3.googleusercontent.com/o4zX8zIFJ-xYVUImDX1hBBTxa_CK1p08y1ufdFhH2SeKxeUmSEC0y_SHhy6XdTN2d4DkEIYYd4O7UY8RDepmr86GfYXlg2oSoccjpQjleRnTt8Tokho" width="440" /></a></p>                 <p>It's our version of the old corporate holiday card, so we always custom-design one of those to include in the package.</p>
<p><a href="http://www.flickr.com/photos/viget/6496997525/in/set-72157628348162219"><img alt="Vigetreats Card" height="293" src="https://lh3.googleusercontent.com/ochK7DRYqj8cRGmdzQsbNsb_yNQT42itNIGP4EKZQg4A594piKdmqVV79qO8b-sFS8XWEQsepRemmq1NmQweun0cOvn1Z0Ibvsu0-_cGIQxDTW_Z5z4" width="440" /></a></p>
<p>I'm not sure what we like more, sharing the end result with all our family and friends, or the process of hanging out and making them.  With our Boulder office in full swing, this year production was split across <a href="http://www.flickr.com/photos/viget/6482530179/in/set-72157628348162219">three</a> <a href="http://www.flickr.com/photos/viget/6482563965/in/set-72157628348162219">separate</a> <a href="http://www.flickr.com/photos/viget/6482541065/in/set-72157628348162219">offices</a>.</p>
<p><a href="http://www.flickr.com/photos/viget/6482569869/in/set-72157628348162219"><img alt="Vigetreats Production" height="293" src="https://lh3.googleusercontent.com/suqhQBY3_FhrP5vBcI-eH65ElKKIrJXVplq85ba9i7nLlJ0WcmedYHmHo69lkYk8Mm_D7RrXkg-Ar_7SIDLZ79md9gQ-CiVn9EQqVfT-WvV0SbunBRQ" width="440" /></a></p>
<p><a href="http://www.flickr.com/photos/viget/6482560937/in/set-72157628348162219"><img alt="Tubes!" height="293" src="http://farm8.staticflickr.com/7004/6482560937_8e069b3e1d.jpg" width="440" /></a></p>
<p>For more photos and a couple of sweet videos about the process and end result, check out <a href="http://vigetreats.com">vigetreats.com</a>.  As always, we made a few extra -- who should get one?  Email a mailing address (and a reason) to <a href="mailto:please@vigetreats.com">please@vigetreats.com</a> and we'll do our best to make it happen (while supplies last).</p>
<p><a href="http://www.flickr.com/photos/viget/6496998945/in/set-72157628348162219/"><img alt="Vigetreat, boxed and ready" height="640" src="http://farm8.staticflickr.com/7159/6496998945_a15f1a0e4c_z.jpg" width="427" /></a></p>
<p>Happy holidays, from all of us at Viget!</p>
      ]]></content>
    </entry>

    <entry>
      <title>You Know You&#8217;re a Good Viget Intern Candidate If&#8230;</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/blog/you-know-youre-a-good-viget-intern-candidate-if/" />
      <id>tag:viget.com,2011:blog/24.2324</id>
      <published>2011-12-09T12:00:00Z</published>
      <updated>2011-12-09T16:32:45Z</updated>
      <author>
            <name>Emily Bloom</name>
            <email>emily.bloom@viget.com</email>
            <uri>http://www.viget.com/about/team/ebloom</uri>      </author>

      <category term="Recruiting"
        scheme="http://www.viget.com/blog/category/recruiting/"
        label="Recruiting" />
      <content type="html"><![CDATA[

                 <p>We recently posted the descriptions of our <a href="http://www.viget.com/careers/">2012 Summer Internships</a>. Each internship description explains the tangible requirements for earning a spot, but I thought I'd follow up with some less-obvious thoughts on who should apply. Here are some things that are likely true of our ideal intern candidates.</p>
<p><strong>EVIDENCE THAT YOU'RE A COMPETENT ADULT:</strong></p>
<ol>
<li><em>You put Ikea furniture together like a champ.</em> Not because we make interns build our furniture for us (well, maybe just a desk or two), but because you're the kind of person who is willing to sit down on the floor with a screwdriver and a booklet of useless instructions, and bust out some elbow grease.</li>
<li><em>You -- not your parents -- are doing your internship search</em>. Parents are great and we'd admire you if you seek their wisdom before making big life decisions. But at Viget we are all fully-functioning, autonomous people who like dreaming our own dreams and making our own plans.</li>
<li><em>Flat tire? W-2 Form? Broken iPhone? No problem.</em> You've been around the block and know a few things. What you haven't seen before, you can figure out.</li>
</ol>
<p><strong>PIECES OF WISDOM YOU'VE DISREGARDED:</strong></p>                 <ol>
<li><em>Don't close any doors. </em>Broad horizons are nice, but if you know what you love and what you're good at, you may have to invest in those things at the exclusion of others. We're looking for people who have already mastered technical skills and who are clear on how they want to start their career.</li>
<li><em>Everything in moderation.</em> Alcohol? Sure. TV watching? Maybe. But some things are best done to the extreme, especially while you're young. We want our interns to be passionate and relentless in their pursuits.</li>
<li><em>Follow your heart.</em> In most academic and professional situations, we think a level head will serve you better than a bleeding heart. While passion and determination have a big place at Viget, so does mature, grounded, rational thinking. (Then again, if your heart leads you to Viget ... by all means, follow it!)</li>
</ol>
<p><strong>TRUTHS YOU HOLD TO BE SELF-EVIDENT:</strong></p>
<ol>
<li><em>Hard work is good work.</em> Things that come easily are often fun, but nothing feels better than putting in some serious effort.</li>
<li><em>Getting straight A's is possible, but not always worthwhile.</em> We're looking for high achievers, but you should be mature enough to know that there's more to life than grades. What activities keep you from that 4.0? We'll be interested to hear about them.</li>
<li><em>Only boring people get bored.</em> You're the kind of person who is creative, curious, and productive in almost any situation. When you land a Viget internship and you're surrounded by smart people working on interesting projects, you'll be blissfully overwhelmed by how much there is to learn and do.</li>
</ol>
<div><br /></div>
<div>We're looking forward meeting the Summer 2012 interns -- you should hurry up and <a href="http://www.viget.com/careers/">apply</a>!</div>
      ]]></content>
    </entry>

    <entry>
      <title>Some Lesser Known Features of LESS</title>

<link rel="alternate" type="text/html" href="http://www.viget.com/inspire/some-lesser-known-features-of-less/" />
      <id>tag:viget.com,2011:inspire/8.2325</id>
      <published>2011-12-08T13:09:00Z</published>
      <updated>2012-01-05T12:52:50Z</updated>
      <author>
            <name>Jeremy Frank</name>
            <email>jeremy.frank@viget.com</email>
                  </author>

      <category term="CSS"
        scheme="http://www.viget.com/blog/category/css/"
        label="CSS" />
      <category term="Development"
        scheme="http://www.viget.com/blog/category/development/"
        label="Development" />
      <content type="html"><![CDATA[

                 <p>For the last year or so, <a href="http://lesscss.org/">LESS</a> has gained a lot of traction in the front-end development community, particularly among designers. LESS extends CSS with dynamic functionality and organizational features, which provide a lot of power and efficiency to designers and developers. However, it's not the only CSS pre-processor player out there. The other major one is <a href="http://sass-lang.com/">Sass</a>, which is very similar, and both are solid options to consider.</p>
<p>Many of the <a href="http://coding.smashingmagazine.com/2011/09/09/an-introduction-to-less-and-comparison-to-sass/">review articles</a> out there do a good job of providing an in-depth look at syntax and general usage, but I'd like to take a different angle&mdash;highlight one difference that isn't written about all that much, and present a few features of LESS that have have proved very valuable on recent projects.</p>                 <h3>No Barriers</h3>
<p>One difference that isn't discussed much is that the barrier of entry is very low for LESS. Sass requires Ruby, and the Sass gem must be installed to get up and running. While not a huge list of requirements (especially for Mac users, since Ruby is already installed), this can potentially put off those who are not comfortable with the command line. With LESS, there are no dependencies, and there is nothing to install. To get LESS up and running, just download less.js from <a href="http://lesscss.org">lesscss.org</a>, and add two lines of code to your markup:</p>
<pre>&lt;link rel="stylesheet/less" type="text/css" href="styles.less"&gt;
&lt;script src="less.js" type="text/javascript"&gt;&lt;/script&gt;
</pre>
<p><em>* Note the rel attribute of the link tag.</em></p>
<p>BOOM! You're all set. Write regular CSS in your .less file(s), start using variables and mixins, and you are good to go. Once your site is ready for deployment, compile to CSS<sup>1</sup>, and replace the above lines with a reference to the compiled CSS file.</p>
<h3>Live Browser Updates</h3>
<p>LESS has a built-in &ldquo;watch&rdquo; feature that auto-reloads the CSS in the browser without reloading the entire browser window<sup>2</sup>. There's no need to install any third-party directory watcher apps for this to work. To enable this while developing, add the following lines to your markup:</p>
<pre>&lt;script type="text/javascript" charset="utf-8"&gt;
  less.env = "development";
  less.watch();
&lt;/script&gt;</pre>
<h3>Implicit Mixins FTW</h3>
<p>In other words, any class defined in your .less files can be used as a mixin. Combine this with LESS's already super-simple mixin syntax, and you've got a winner! Using HTML5 Boilerplate's .ir class as an example, you can reference the .ir class as if it were a mixin, instead of adding the classes to your markup.</p>
<pre>.ir { display: block; border: 0; text-indent: -999em; overflow: hidden; background-color: transparent; background-repeat: no-repeat; text-align: left; direction: ltr; }
.heading {
  .ir;
  background-image: url(image.png);
  height: 50px;
  width: 150px;
}</pre>
<div class="notification">
<p class="no_bottom"><em>Note:</em>&nbsp;While implicit mixins are super simple to use, if you decide to use them, do so with caution! This can lead to property/value duplication and code bloat.</p>
</div>
<h3>Namespaces</h3>
<p>Namespaces allow for bundling groups of mixins together for organizational purposes. The example on the LESS site isn't a great one, so here's an example for CSS3 gradients.</p>
<pre>#gradient {
  .horizontal (@startColor: #555, @endColor: #333) {
    background-color: @endColor;
    background-repeat: repeat-x;
    /* browser prefixed gradients here */
    background-image: linear-gradient(left, @startColor, @endColor);
  }
  .vertical (@startColor: #555, @endColor: #333) {
    background-color: @endColor;
    background-repeat: repeat-x;
    /* browser prefixed gradients here */
    background-image: linear-gradient(@startColor, @endColor);
  }
  .directional (@startColor: #555, @endColor: #333, @deg: 45deg) {
    background-color: @endColor;
    background-repeat: repeat-x;
    /* browser prefixed gradients here */
    background-image: linear-gradient(@deg, @startColor, @endColor);
  }
}
.box1 {
  #gradient &gt; .horiontal;
}
.box2 {
  #gradient &gt; .vertical(#ccc,#aaa);
}</pre>
<h3>Continuing From Here</h3>
<p>So, how have <em>you</em> used LESS recently? Which features or techniques have been valuable to you? If you want to check out some other resources, be sure to look at <a href="http://markdotto.com/bootstrap/">Preboot</a>, <a href="http://twitter.github.com/bootstrap/">Twitter Bootstrap</a>, and <a href="http://incident57.com/less/">Less.app</a>.</p>
<p>&nbsp;</p>
<p><sup>1</sup> <em>The easiest way to compile to CSS is via the command line or with Less.app. You can also compile with node.js.</em></p>
<p><sup>2</sup>&nbsp;<em>This only works when browsing files on the local filesystem, and in a browser other than Chrome (because of a known issue in Chrome with loading local JavaScript files).</em></p>
      ]]></content>
    </entry>


</feed>
