Site review:

Written by Adrian Holovaty on August 6, 2002, the site of The Daily Herald in Provo, Utah, makes up for its substandard design with a handful of innovative, mostly database-driven features. Some thoughts:

  • The site looks and reads like a blog, and that's a good thing. The home page and section fronts simply list all stories in their section (from what I can tell, the home page serves as a replica of the print edition's front page), with a headline, byline, date, short blurb and a few links: "Read More", "comments?", an icon for a printer-friendly version and an icon for "send this story to a friend". Can they get more blog-like? I thought it was a blog the first time I visited the home page. It might not be sexy, but its usability is outstanding.
  • The horizontal navigation bar is a list of the days of the week, starting with Sunday. The current day is highlighted, and the other days are linked to their respective content, which means a user always has seven days' worth of content immediately accessible. It's simple to use, but, because the days are always listed from Sunday to Saturday, the days get counter-intuitive. For example, when I visited the site today, Monday was bolded; but clicking the Tuesday link, which is directly to the right of the Monday link, took me to last Tuesday's content. It's obvious that a news site can't print tomorrow's news, but the way this navigation is presented suggests that.
  • As far as I can tell, most of the content on this site is from the print edition. Therefore I assume the site doesn't change much throughout the day. Why, then, is auto-refresh set on the home page and every section front? (See my previous post on this topic.)
  • Users are encouraged to post comments on each story; comments are embedded at the end of each article. This is a great move on the site's part, a feature that other news Web sites wouldn't touch with a ten-foot pole. My only beef is that a user has to click "Post a comment" to get a new page that prints the article all over again (strangely, in a different font size), without the previous comments and with a form for posting. Why not put the form right on the first page, right under the other comments? Clicking to bring up another page is an unnecessary step.
  • All the photos on seem to be in a database, which leads to some pretty cool -- but possibly controversial -- stuff. Photos in articles are only thumbnail versions; clicking on a photo brings you to a larger version with caption. From that page, you can click "previous image" or "next image" to get another image from that particular issue. (What determines "previous" or "next"? Probably just the order in which they were entered into the database.) It's a cool, sticky way to get people clicking. Plus, "back to thumbnail view" takes you to a thumbnail page of all the photos in that particular issue -- again, in no significant order. Thus, at a glance, you can see all the photos from a single day. (Everything's powered by an open-source PHP script that anyone can download.)

    It's a very cool feature, but it presents some journalistic pitfalls. Namely, by lumping all an issue's photos and comics together on a single page, the chance of inappropriate combinations is high. I pondered this possibility this evening, and, sure enough, on today's photo index page, an obituary photo of a dead man sits directly next to a photo of a Navy SEAL aiming a gun. Utterly tasteless:

Screenshot of site, with obit photo next to gun photo

  • In addition, from the photo detail page, it would be nice to see which story a photo goes with. Cross-linking stories and photos can't be too difficult.
  • Users can also easily navigate the photo archives using a breadcrumb navigation scheme at the top of the photo detail pages. One example of computer logic winning over human logic, though: On the year index pages, month names are listed alphabetically instead of chronologically. It made me do a double-take, several times.
  • The site's staff page is a model to be followed. Each staff member gets an extended bio, photo and list of favorite links. That's followed by an e-mail address and a link to a Web-based contact form for people who don't have e-mail access. Then, to top it off, a phone number. Some sites don't want you to contact their reporters. Others, like this one, are much friendlier.
  • Finally, there's a slick handheld version -- and its story pages double as the printer-friendly versions for the normal Web stories. Great reuse of content.


Posted by Gary Love on August 6, 2002, at 6:46 a.m.:

Hmmm...I don't agree with ya on the usability of the weblog format, but I did enjoy the "Most Read ___ Story" feature beside each story. I'm fond of anything that gives readers a hint of what might be a hidden gem within the rest of the paper.

Posted by Chris Heisel on August 6, 2002, at 2:15 p.m.:

While I certainly think a site needs to be a part of, and re-inforce, your brand, this may be a little too close to the paper for comfort:

See it yourself...

L.A. Lakers play-by-play man Chick Hearn, who coined the phrases "air ball," "ticky-tack foul" and "slam dunk" during nearly 50 years as a broadcaster, died Monday in Los Angeles. See story on B1.

This story appeared in The Daily Herald on page A1.

Posted by Adrian on August 6, 2002, at 5:38 p.m.:

Oooh, I forgot to mention that "Most Read Story" feature. I agree -- features such as that one are just plain cool.

I also neglected to point out the "Read other stories by this author" links on the right side of story pages. Another great database innovation, something that's been done before but still hasn't entered the mainstream. And it's so easy to set up if you've got a database-driven site!

Posted by Drew Mitchell on August 27, 2002, at 12:09 a.m.:

Another site that uses "Read other stories by this author" and "Today's Most Read" - the Herald-Journal in Spartanburg, S.C.

Posted by Adrian on August 27, 2002, at 6:14 a.m.:

I appreciate the pointer, Drew...It's a pity, though, that the Herald-Journal site relies solely on JavaScript for "Recent stories by this writer". Clicking that link submits a form, of all things, when it could just be a plain text link with the appropriate query string in the URL. Not only does that make this feature inaccessible to browsers with JavaScript disabled, it's also just plain inefficient.

The solution lies in putting the author's name in the URL like so: For example, this page should use this URL for the "recent stories" link.

Comments have been turned off for this page.