A good plan for a Web site considers the type of content and the expectations that site visitors will have about how that content should be organized. Project-specific Web sites, for example, can be modeled on existing paper-based project management systems. You could begin diagramming a site map by taking the file directory you already use to categorize project information. If you can “flatten” the site hierarchy without losing its logical structure, people will find the information they want in fewer steps.

	above, a "flat" structure below, a "deep" structure

A complex Web site will necessarily have a deeper structure than a simple one does. But always keep in mind how frustrating it can be to sift through page after page to find something hidden many levels deep. The shortest, most direct route from the entry page to the desired infor mation should always be the goal. Try drawing storyboards of each page on 3- by 5-inch index cards, so that you can experiment with different navigational schemes to track a visitor’s progress through a site.

The site map does not have to be fixed and unchanging. It is more like a living ecosystem, where old pages die and new ones take their place. Because Web sites tend to grow incrementally, you have to remain vigilant that the underlying structure you established does not get lost. The ease of making changes means that a Web site need never be considered finished. After a Web site’s launch, test the effectiveness of its structure and adjust if necessary. Rearranging the elements in a Web site is easy, but always keep your plan in mind.

Information is easiest to use when it is presented in small pieces. A Web page can be of any length, but consider the advantage of breaking up material into easily absorbed and logical segments. Instead of placing an entire specification on one page, for example, place each CSI section on a separate page. Think about the smallest chunks of information your viewers need at a time, and divide your Web site accordingly. Be consistent, so that readers know what to expect when they ask for the next chunk. It’s a balancing act: if too little information is provided, the viewer will become frustrated. No one wants to wait for another page to load just to read another paragraph. On the other hand, readers find it annoying to have to scroll through long blocks of text and graphics to find a link to needed information. Keep in mind that, on-line, the threshold of frustration is low, and the attention span is short.

Next month: Interface Design