Web Information Architecture Deliverables > Net Web Sitemap
2/2004
There are two types of web sitemaps used in Web design and development. The first kind is what users are common to seeing on websites; a link to a "site map" that contains a comprehensive list of sections or pages on the site. Although these types of site maps arent as popular as they used to be, they are still very common. On some sites these sitemaps have been replaced by "a-z indexes" which list site content alphabetically.
The site maps that information architects are most concerned with are very different. These sitemaps document a website's structure and organization. They define the major sections, subsections, and pages. The document usually looks similar to a work breakdown structure (WBS) used in project management. However in this instance the tree structure shows web contnet rather then deliverables or work packages.
Combining a detailed site map and illustrative wireframes creates a valuable document that can guide programming and future requirements. In some cases such a document has become the default requirments document for systems my group is building.
There is no standard best practice for creating sitemaps. I happen to prefer to use Visio - as do many others. Visio allows you to easily lay out page hierarchys and create connections between them. But wireframes could also be created in Word, Power Point, Excel, by hand, or any other method you find helpful.
Site maps can be constructed in a wide variety of formats, but the general structure and principles remain relatively consistent.
I Recommend