Warning: This is an archived course website that is part of my teaching portfolio, so some links may no longer work. Please contact me with any questions about this site.

Week 13: Finishing Tubes, Starting Usability Testing, and Exam #2

I hope you are enjoying your Thanksgiving break! When we return next week, we will be in the home stretch of the semester, with only six class sessions remaining before finals week. We will need to use our time wisely to make sure that your client projects stay on track. Our in-class exercises will help us accomplish that goal, but your team will need to make solid progress outside of class, too. If you haven’t been meeting regularly as a team, that will need to change during Week 13. By this point, your team should have a solid first draft of your client site, so if you’re behind schedule on that task, now is the time to catch up.

Here’s a quick overview of the coming week:

  • On Monday, we will conclude our discussion of Tubes, so please read pages 227–68 before you come to class. In addition, please read “Into the Vault: The Operation to Rescue Manhattan’s Drowned Internet,” by Dante D’Orazio. (Be sure to watch the embedded video — it’s fascinating!) After we put Tubes to bed, we will jump into usability testing by watching a usability expert conduct a test, then conducting a usability test of our own. You don’t need to do anything specific to prepare for these exercises, but I recommend exploring the “Usability Basics” section of Usability.gov before you come to class.
  • On Wednesday, we will continue our discussion about usability testing and begin drafting the protocols that you will use to test your client site. To prepare for our in-class activities, please read “Super Easy Usability Testing,” by John S. Rhodes, and the “Planning the Project” and “Analyze Current Site” sections of Usability.gov. (Note that each section of Usability.gov contains multiple pages; use the sidebar navigation to work your way through the sections.) Please come to class on Wednesday ready to discuss these readings and put them into practice on your project. Your homework after class on Wednesday will be to complete your usability testing protocol and submit it to me via email.

Finally, a few words about our second exam: Because we have a limited number of class sessions left, I have decided to make this an open-book, open-note (but not open-classmate), take-home exam. In addition, the exam will be optional, which means that you only need to complete the exam if you are unhappy with your score on the first exam. If you are satisfied with your grade on that exam, I will simply duplicate that score for Exam #2. However, if you would like the opportunity to raise your exam grade, you can take home a copy of the exam at the end of class on Wednesday and submit it at the beginning of class on Monday, December 3. (Please note that while a take-home exam is likely to produce higher grades than an in-class exam, a higher grade on Exam #2 is not guaranteed.)

As always, if you have any questions about these plans, or if you want to meet to discuss your team’s progress on the client project, please let me know.

Posted in Weekly Updates
Where am I?
This is the class website for English 4814: Writing for the Web, taught by Quinn Warnick at Virginia Tech in fall 2012.
Worthwhile Reading
The links below are the most recent additions to my collection of bookmarks that are relevant to this course. You can find a complete list of ENGL 4814 bookmarks on Pinboard.

  • CodePen
    Awesome browser-based tool for experimenting with HTML, CSS, and Javascript.
  • What Constitutes Good and Bad Web Design?
    NY Times: "Shoddy Web site design is a curse of modern life. The more dependent we have become on the Internet for information, the likelier we are to suffer from its design deficiencies. Bad design can be infuriating, inconvenient or damaging in any field. But it is especially frustrating in areas like this where many of us find the technology so inscrutable that we tend to blame ourselves for being baffled, because we feel unable to judge whether the design is at fault."
  • wireframe.cc
    Free, minimalist wireframing tool, with templates for desktop, tablet, and phone.
  • Yes, learn basic programming
    Derek Sivers thinks everyone should learn HTML, CSS, and Javascript: "If you heard someone say, 'I have this idea for a song. But I’m not musical, so I need to find someone who will write, perform, and record it for me.' - you’d probably advise them to just take some time to sit down with a guitar or piano and learn enough to turn their ideas into reality."
  • CSS Floats 101
    Another great article from Noah Stokes in A List Apart. This one focuses specifically on one of the trickiest parts of CSS for beginners to master: the float property.
  • CSS Positioning 101
    Noah Stokes's A List Apart article is a great starting point for getting better at CSS positioning. Complete with several examples.
  • Modular Scale
    Handy tool for improving typography on modern, responsive websites. (The linked articles on this page are important, too.)
  • Interactive Guide to Blog Typography
    Great tutorial for improving typography on any website, not just a blog.
  • The Basement
    Great photo essay by Cabel Sasser: "And eventually, you crawl behind a corner, and discover a bundle of conduit. Conduit for every major internet carrier you’ve ever heard of. Oh, right. You had almost forgotten. This building, this basement, is the major internet hub for the entire region."
  • Snow Fall: The Avalanche at Tunnel Creek
    Beautiful interface for this NY Times article. Perfect integration of video, images, and text.
  • Service Learning Survey
    Students: If you worked with a client from the VT Engage program, please take a few minutes to provide the program with some feedback about your experience.
  • SPOT Survey - Fall 2012
    Students: If you haven't completed the SPOT evaluation for this course, please do so during class on Wednesday. I take this feedback very seriously, and I use it to revise my classes each semester, so please be specific about the aspects of the course (and my teaching) that you found successful and unsuccessful.
  • Standards, not Prescriptions
    Nathan C. Ford: "For standardization to truly continue making the web a more stable place, we do not need more anticipatory specifications, we need solutions. Lots of them. Dumb ones, fat ones, smart ones, skinny ones. Let us embrace them all then watch them fight it out in the field. When the strongest emerge, we can adopt them into our specs and wait for the next batch of victors."
  • Into the vault: the operation to rescue Manhattan's drowned internet
    Dante D'Orazio, writing for the Verge: "Hurricane Sandy's storm surge flooded Verizon's downtown office, rendering miles of copper wiring useless."
  • Responsive Design Testing
    Great little tool for seeing what your website looks like at a variety of screen resolutions.
  • Having a Mobile Strategy is Like Having a Laptop Strategy 20 Years Ago
    John Steinberg: "I do not want to download your app. I just want to read the content on the mobile web and possibly share it if I’m engaged. The constant knee-jerk interstitialing of full-screen app download messages every time I load sites is beyond frustrating. Many site owners seems convinced that this frustration, which no doubt dampens the velocity and volume of content sharing, will convert in loyal downloading app users."
  • Google Data Centers
    Photos, video, and history of Google's physical facilities. Obviously one-sided, but interesting nonetheless.
  • Google Throws Open Doors to Its Top-Secret Data Center
    Steven Levy, in Wired: "This is what makes Google Google: its physical network, its thousands of fiber miles, and those many thousands of servers that, in aggregate, add up to the mother of all clouds."
  • Guidelines, Tools and Resources For Web Wireframing
    A nice list of resources about wireframing.
  • Save For Later
    Fascinating report on a Mozilla UX project by Brian Groudan: "All browsers support two functions: searching and revisiting. My research questions whether constructs like bookmarks really are the right model to support revisiting. I worked closely with Mozilla user experience researchers and designers to rethink how Firefox can better offer 'save for later' in the browser."