Return to Process

Sitemap Development: Site-View

Sitemap creation (or flowcharting) is important to the overall understanding of site structure and content organization. It shows a high-level view of the site, should show main areas of content and HTML pages within each section. This document is a living and evolving part of the site architecture process. It is also the start of naming/labeling the sections within a site and determining global navigation.

Establish Naming Standards

Creating the sitemap is a good way for the producer to estab- lish clear naming standards for all team members to follow. Usually, I create two sets of names for site sections and pages. They are HTML names and numeric names.

Descriptive Naming

Abbreviations or intuitive naming is based on the HTML page’s content or section.

• cooking.html
• dining.html
• editorspicks.html

Numeric Naming

Having a ‘code’ for each section of the site helps to organize pages beneath each section. It allows you to imme- diately see where the content fits into the overall structure of a site.

• 1.0 = homepage
• 1.1 = secondary page
• 2.0 = sectionA
• 2.1 = sectionA_sub

Keep it Updated!

It is important to keep the sitemap as updated as possible and to have the client sign off on each version created. Think of this as a blueprint for building a house. Each change in scope and structure (including deletion of pages) affects the development process, and most importantly – budget. Keeping an updated sitemap circulating will help all members of the project stay “on the same page” during all phases of the project.

Wireframe Development: Page-View

Wireframing Contnet

The creation of content layout into a non-design oriented wireframe is usually the responsibility of the project manager or producer. While designers can be solicited for input,it is important that the content for the site be identi- fied and organized prior to the design phase.

Information Architecture (IA)

“[information architecture is]“…creating consistent and functional systems for navigation, graphics, page layout and title languages so that the user knows where to go, what to do, and encourages them to return.” – Web Review, Peter Monville

IA Objectives

1. Connect User with Content
2. Create Comfort
3. Promote Learnability

Summary: Phase 2

Site architecture is created. Navigation and technology are addressed and clarified. Naming conventions are defined.Wireframes are created for high-level pages.

• Content Outline Completed
• Sitemap Created
• Naming Conventions Set
• Wireframes Completed for 1st and 2nd level pages
• User Tasks Defined

*Keep sitemap updated!

A backbone is created for the rest of the project to build on and we move to Phase 3.

top