Redesigned Mozilla Website Launching Soon
Thursday October 30th, 2003
Bart Decrem writes: "Thanks to the hard work by Dave Shea, Tristan [Nitot], and, especially for the long last mile, Ben [Goodger], Dawn [Endico], DBaron [David Baron] and Chofmann [Chris Hofmann], we're almost ready to launch the redesigned Mozilla web site, so now's a great time to head over to http://website-beta.mozilla.org/, check out the new site and send feedback to firstname.lastname@example.org."
Update: One of the names that originally appeared in this article has been removed, at that person's own request.
#82 Needs work on the information architecture
Tuesday November 4th, 2003 2:59 AM
You are replying to this message
I think the new website is a big step forward compared to the old one, except on two major issues:
- The lack of a well thoughtout information architecture - The lack of communicating the information architecture to the user.
I feel that on the issues concerning information architecture, the new website represent no big improvement over the current website.
I'll try to give you some examples:
- It's hard to know exactly "where you are" in the information structure. For a user, it's very important to have an idea of "where you are" in an information structure .
Adding a location breadcrumb trail could help solve this issue.
- Inconsistency between the top heading on a page and the corresponding menu-option
When I click on "download" in the top menu i get to a page which says "Products" (in the left column) and "All Mozilla Products" in the main area of the page. The heading on this page should be "Download" as in the menu. Consistency between headings and menu-options are important to help the user keep track of where he is on the site.
- Its hard to know what function the left-hand menu has in relation to the page i'm visiting.
Sometimes the left-menu is just a "short version" of the same options for navigation presented in the page itself: <http://website-beta.mozilla.org/download.html>
But sometimes its more like a fullsize menu and contain more options for navigation than within the page: <http://website-beta.mozilla.org/developer/>
An at other times its used to present links to other sites: <http://website-beta.mozilla.org/sitemap.html>
I would suggest to drop the left-hand menu all together, and present the "context dependant" links within the context of the page [3,4]. Duplicating more or less the same navigation options in both the menu and inside the page like today is only confusing to the users.
 Nielsen, J. (2000). Designing Web Usability: The Practice of Simplicity.
 Instone, K. (2003). Location, Path & Attribute Breadcrumbs. Retrieved 11/03/03 from <http://keith.instone.org/breadcrumbs/>
 Bernard, M., Hull, S., & Drake, D. (2001). Where should you put the links? A comparison of four locations. Usability News 3.2. <http://psychology.wichita…sabilitynews/3S/links.htm>
 Krug, S. (2000). Donít make me think! A Common Sense Approach to Web Usability. New Riders Publishing.