Sunday, March 04, 2007

Content plan

Content Development Plan

Who: The content manager for the site development will be responsible for assigning all content development, scheduling and enforcing content freezes, and developing a post-release content update schedule. The content manager will designate which editorial staff may enter or alter content in the content management system.

What: The initial site content will include browsable lists of media companies at different tiers of influence, ownership information for media outlets, and links to various informative media-focused blogs and other sites. Each searchable media outlet has an individual surfaceable page with a logo, name, what company owns it, what companies it owns. There will be a link to a printer-friendly version. Web 2.0 features: There will be an RSS feed on the home page, to surface timely media information quickly. There will be a list of search terms ranked by popularity on the home page.

When: It should take an estimated 80-120 work-hours to complete the initial content release and 400 work-hours to populate the database; quarterly database updates will take 24-40 work-hours. These updates will be released on the nearest weekday on or before the 15th of January, April, July, and October.

Where: Content files will be located in the UW file system on UW servers, and site content will be maintained on TheyOwn.net via a content management system yet to be determined.

Why: To provide timely content that meets the project's stated goals and objectives.

How: Initially, the ownership information and other static content will be researched and input by temporary data entry staff. Content updates will be performed every three months, either by paid staff or by student interns. Blogs will be refreshed at least twice per week by faculty members.

Privacy Policy

Privacy Policy

TheyOwn.net respects the privacy of Web users. We make all reasonable efforts to protect your personal information and to not intrude on your email and Web space without your continued permission.

We monitor our systems and networks, and collect standard access logs to them. We never use our access logs for anything but our own administrative purposes. We never open those logs or the results of our monitoring to anyone other than our administrators.

We use IP addresses to analyze trends, administer the site, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information, except within blog comments. To discourage harassment of users, we log all individual comments with the IP address of the writer. We do not make that information public, however.

Our sites contain links to other sites. We are not responsible for the privacy policies of these sites.

No part of TheyOwn.net is intended to attract anyone under 13 years of age. We do not collect information from anyone we know to be under 13.

We offer email newsletters and updates for those interested in what's new on our site. We ask for email addresses so that we can send these to readers, but we do not sell, rent or share user information or mailing lists. We also intend to challenge any subpoena or other legal process seeking access to our mailing list, access logs, or any other user information. We do not require your actual name, nor do we enhance our mailing lists by linking them to other databases.

We don't intend to change our privacy policy, but we do reserve the right to change it at any time. Changes will not go into effect until the posted privacy policy is modified.

If you have questions about our privacy policy, please contact us.


Thursday, March 01, 2007

Personae nos. 1 and 2


Marcus Grady, age 20 -- student journalist, activist

Marcus Grady is a second-year student at Shoreline Community College near Seattle. He hopes to enter UW or Evergreen State next year. He graduated from Ingraham High in 2004, and lives at home with his parents and two brothers in the Greenwood neighborhood of Seattle. Marcus worked mainly as a warehouse temp for one year after high school in order to buy a car and save a little money. Now he works 15 hours per week at the Greenwood branch of the Seattle Public Library and delivers pizza on Friday and Saturday evenings for a few hours to help cover his school expenses, buy gas, and have some spending money.

He is interested in public policy and journalism, writes and edits for the Shoreline Community College newspaper, and is a dedicated student activist. Marcus led a successful effort to keep an independent coffeehouse on campus rather than allowing a Seattle's Best Coffee store to open in its place, and often participates in campus peace actions. He hasn't totally made up his mind yet about the 2008 presidential candidates, but he is eager to learn more about Barack Obama and has donated $25 to his campaign.

Marcus uses the Web daily to get news, research his course papers, fact-check stories for the school paper, and support and promote his activism (with MoveOn and MySpace especially), as well as to keep in touch with his friends from high school, download music, and plan his social life. He has tried Second Life, but he is an extrovert and finds it a somewhat frustrating way to interact, so he has decided that for now he'd rather spend his time and money elsewhere. He did meet an old girlfriend through Facebook, but isn't dating anyone right now. He accesses the Internet at home (where he has DSL access), at school, and occasionally at work. On weekends, when he's not working, he hangs out with friends, usually listening to music at their houses or going to occasional raves.

Marcus's brother is legally blind, and Marcus himself is color-blind, so he is very aware of ADA guidelines for the Web and is somewhat impatient with sites that depend on color graphics for navigation.



LaRee Ediger, age 25 -- public television producer

LaRee graduated from UW in 2004 in communications with a concentration in journalism; she did an internship at Scripps News Service in the summer before her senior year, and won the Excellence in Journalism award for an opinion article that was printed in the Post-Intelligencer. She started as an assistant and fact-checker at KNPB, the public TV station in Reno, three months after graduation (after attending a two-week journalism workshop in London and spending four weeks traveling around Scandinavia). In the intervening three years, LaRee has worked up to the position of producer. She produces a weekly talk show on arts, politics and humanities, “One on One,” and has co-produced occasional special features. She loves her job, though she does not plan to stay in Reno for more than another two years.

LaRee has a blog where she discusses her hobbies (cooking, bicycling, and walking her Labradoodle) and her aspirations to work at a cable channel like A&E, THC, or Discovery. She is very comfortable using the Web to address her work needs and some of her personal and social needs. She met her best friend Karleen through a Craigslist ad asking for weekend cycling partners, and has met a few guys through Nerve.com—though she met her current boyfriend, Jack, on a ski weekend nearly five months ago.

LaRee has bookmarked several journalism sites like Columbia Journalism Review, the Pew Center, and Poynter Online, and refers to them often—sometimes for work-related research, sometimes for career advice. She is currently making about $34,000 per year, and has set herself the goal of having a $50K salary in three years. She would like to become a vice-president of production of a cable channel in the next ten years.

Tuesday, February 20, 2007

Week 7 readings

Give Customers Short Paths to What They Want” by Moira Dorsey

(aka the “three clicks” (or the “well, duh”) paper)

Forrester found that on a site with a flat navigation structure, where important content is three or fewer clicks from the home page, users get where they want to be faster and with fewer errors. This has been a standard practice in web design since the last millennium, right? Obviously it's much easier to design this way if your site has a limited number of purposes (e.g., if all you do is sell widgets or allow users to post pictures and text). One important point: if your site is content-rich in a way that means that not all your content is surfaceable in two or three clicks, your search box needs to be obvious and your search engine good. It took me six clicks to get to the MCDM website from the UW homepage by selecting links, but only two when I searched on “MCDM.”


Web Page Layout” by James Kalbach and Tim Bosenick

The Kalbach and Bosenick paper was interesting (and not just because it used RH nav for its own table of contents). At first I had some difficulty parsing the two hypotheses, but finally understood them thus:

  1. LH navigation will be faster than RH overall, BUT

  2. RH navigation will be initially slower, but will speed up as the tasks progress until there is essentially no speed difference between RH and LH navigation

From looking at their chart of results, it appears at first glance that these two somewhat contradictory hypotheses were borne out in their experiment, but Kalbach and Bosenick claim that there is in fact no difference between the two navigation schemes. The difference for Task 1 and Task 2 looks significant until you look at the standard deviations—and you have to give those more than a cursory look, because it turns out that nearly a third of the participants were unable to find an e-mail link (task 1) and a physical address (task 2) listed on the site within the three-minute limit. Users who were unable to complete a task in three minutes were not counted as data points; this cuts the number of points used for these calculations down sharply. Three minutes is roughly five sigma from the mean, and it seems bizarre for so many users to have ended up so far outside of that limit. It's impossible to know whether this stemmed from a design problem on the site or a problem with the way the study was conducted (I'm guessing site problem, though).

I find it hard to understand why they used such a small study population in the first place. When they remove the slow people, they're left with ~20 data points, which would make me nervous if it were my study. I'm not a statistician, have never played one on TV, but have taken a couple of statistics classes, which means I know just enough to make me want to know more about the sampling. The findings themselves seem reasonable, however.

The discussion section brings up a number of interesting points regarding how people scan a site. The Audi site is extremely spare, with a short right-hand menu, black-and-white graphics, and plenty of white space, which may well have contributed to the lack of difference in the outcomes. It would be very interesting to conduct a similar but more complex study with longer navigation menus. I think the main point here should really be that if you stick to good design principles throughout your site, it doesn't matter so much what your navigation scheme is as long as it is consistent and clean.


Evolution of Web Site Design Patterns”

This is a very long, data-heavy paper, and difficult to treat critically in detail. Basically, the authors examined 1500 sites over the period 2000-2003 for 157 interface factors in order to determine whether website design has evolved towards better usability and accessibility. Examples of some of the these factors are number of links per page, average number of words included in a text link, font style and size, and number of HTML errors per page.

One problem the authors note is that much of the enormous amount of web design guidance available is confusing and contradictory. They grouped sites according to their rating by Webby Award judges in order to assess practices. Interestingly, after examining a number of highly-rated sites, the authors recommended that the Webby committee adopt a more rigorous evaluation procedure.

Overall, for the period 2000-2003, the authors found some improving trends, some disappointing trends, and a fairly shocking number of accessibility problems. One thing that's not made clear in the paper is whether the increase in HTML errors and the decrease in accessibility is due to the increase in the number of HTML-inexperienced web authors, using web interface tools that may not have been well designed.




Tuesday, February 13, 2007

Main points from book

Important points from Carrie Bickner's Web Design on a Shoestring:

  • Planning saves money
  • Use resources at hand
  • Have a clear focus
  • Dare to do less

Friday, February 09, 2007

Web Design on a $hoestring

I'm reading Web Design on a $hoestring by Carrie Bickner, which (in spite of the cutesy dollar sign) is straightforward and intelligently written, not just a list of dorky money-saving tips. Bickner addresses low-cost strategies in the areas of usability, content, design, CMS, web standards, domains, and web hosting. The book is part of the estimable New Riders "Voices That Matter" series (along with another book I seriously considered reviewing, The User Is Always Right: A Practical Guide to Creating and Using Personas for the Web, but rejected due to its length and narrower focus). More when I'm finished...

Monday, February 05, 2007

Group 1 discussion from last week, and updates

Group 1 members (with links to their blogs):

Barrie (me)
Belle
Kevin
Magnus
Ragan

We spent the last half-hour of class on Jan. 30 trying to get our arms around the team project, finally agreeing to each go away and look at sites with a critical eye in order to apply some good design principles to the concept. (See my previous post; Belle and Ragan have also posted on this topic already.) We had some minor who-does-what discussion, with little resolution (other than my volunteering to be point person), but we agreed that a site map would be a good tool to work on early.

Sunday, February 04, 2007

Model sites for TheyOwn.net planning

I decided to look not just at media sites, but at sites I sometimes or often use for information, since TheyOwn will be an information site.

slashdot.org

This is a wide-ranging news aggregation site for those interested in open-source software and the many areas that it touches. It has the following standard features that work well on any information site:

Site identification in upper left corner

Search box in upper right corner

Login link below header—clicking on the link causes a login box to appear on the page

Left gutter main navigation, secondary top navigation

Center of page is given to current articles. Right gutter contains links to recent tags, as well as articles from the previous two days.


wikipedia.org

This wiki-encyclopedia is a major source of information for many, and the entries are usually updated concurrently with breaking news. It's a particularly usable and readable site, due in part to the following:

Navigation, search, and toolbox features are labeled in left gutter

Articles, discussion, wiki tools, and page history are tabbed at the top for easy access

Large default font size!

Obvious links

On a side note, the site is supported by a public foundation and has a link above the fold to donate—a good feature for any nonprofit site to emulate.


Democracy Now!

This site has excellent content, but some of the design elements look cluttered and there is too much “fine print.” Also, it's not clear what is clickable text and what is not. Positive elements include:

Clean, obvious archive search box and digest subscription box;

Well-placed, well-labeled “donate” button;

Good use of thumbnail graphics.