Just because Web sites are easy to build these days, that doesn't mean it's easy to build a quality Web site that meets your business objectives. Before developing your next Web site, or redesigning an existing site, download this Internet.com eBook to guide you through the process and plan your project, whether you're developing a site in-house or outsourcing the project. Register now for your free Internet.com membership to download your complimentary eBook. Membership will also give you access to: eBook library         Whitepapers         Webcasts Newsletters         WinDrivers

Top 10 Articles Web Developer's Virtual Library: Encyclopedia of Web Design Tutorials, Articles and Discussions JavaScript Tutorial for Programmers Design JavaScript Tutorial for Programmers - Objects JavaScript Tutorial for Programmers - JavaScript Grammar JavaScript Tutorial for Programmers - Versions of JavaScript Cascading Style Sheets JavaScript Tutorial for Programmers - Embedding JavaScript JavaScript Tutorial for Programmers - Functions Authoring JavaScript

Domain Name Lookup Search to find the availability of a domain name. Just enter the complete domain name with extension (.com, .net, .edu)

Group controls that have similar functions together

For the right-side navigation bar, most of the links direct users to areas of content on the site, not to the site's auxiliary navigation tools. For the bottom navigation bar, most of the links direct users to areas of site navigation, not areas of site content. However, there is some overlap.. The right-side navigation bar includes links to navigational pages on the site, namely "Search" and "Site Maps." The bottom navigation bar includes links to areas of the content on the site, namely the "Index" and "Library." For the user who is thinking that the function of right-side navigation bar is to provide access to the major content areas of the site and the function of the bottom navigation bar is to provide access to navigation pages, this overlap is confusing.

Many of the navigation tables as they now exist are largely in alphabetical order. Alphabetical organization schemes work well in a phone book, when a user knows what they're looking for. But in situations where users are browsing instead of performing known-item searching, other organization schemes such as grouping by topic or task are more appropriate.

Recommendations:

• Segment elements in categories, rather than organizing all lists alphabetically. Group like elements together. Most sites generally break down into two types of entities, the content itself, and information about the content. Such information about the content (called meta-information) should be grouped together, and remain distinct from the content-related categories. So in Stars.com, meta-information elements such as "Home," "Search," "About the WDVL," and "Feedback" should be grouped together. The actual content of the site: the descriptions of remote resources and the local content should also be grouped together.

• Group content areas by users' needs. Currently the site is grouped largely by subject (e.g., "Authoring", "Internet"). It may make more sense to group content according to the way users use the information. For example, all the articles could go under a single heading, as could all of the "Bookmarks" and "Pictures", since users tend to utilize different types of content in different contexts.

Choose precise labels that make sense to your audience

Recommendations:

• Choose precise labels so their meanings are not ambiguous, and do so with the least number of words possible. In the case of "Index" a better choice would have been "Encyclopedia" or "The Webmaster's Encyclopedia."

• Be aware that the way you label content may have different meanings to different audiences. For example, we're librarians. In the real world, we're used to finding the reference area in the library. But we were confused in Stars.com to find the "Library" in "Reference."

Provide contextual information for labels and for the site as a whole

The feedback form is one of the best we've ever seen, because it provides the Webmaster with context to help resolve problems; it notes what page the user was on, and the platform and browser being used. It is somewhat ironic that the feedback form provides context for the Webmasters, but the Webmasters sometimes do not provide context for the users.

Recommendations:

• Make the main page more like the overview. Provide context for the sea of labels, by including less labels, but more descriptive information about what each of the groupings contains.

• Let each page frame user expectations about what they will find on the page. Provide at least a phrase or a sentence that describes what is available on the page.