HTML and CSS Reference
In-Depth Information
other analyst, graphic designer(s), senior Web developer(s), and the client's marketing
representative and related personnel. Common tasks of the Design phase follow:
Choose a Site Organization. As discussed in Chapter 5, common Web site organiza-
tional forms are hierarchical, linear, and random. Determine which is best for the
project site and create a site map (sometimes called a flowchart or storyboard).
Prototype the Design. As a starting point, sketch out the design on paper.
Sometimes it's useful to sketch within an empty browser frame (see the student
files Chapter10/sketch.doc). Often, a graphics application is used to create sample
Web page mock-ups, or wireframes, as page layouts are created. These can be
shown to clients as a prototype, or working model, of the system for approval.
They can also be shown to focus groups for usability testing .
Create a Page Layout Design. The overall layout, or look and feel, of the site
should be designed. The page layout design is used as a guideline for the Home
page and Content page layouts. Items such as the site color scheme, size of logo
graphics, button graphics, and text should be determined. Using the page layout
design and site map, create sample layouts for the Home page and Content pages.
Use a graphic application to create mock-ups of these pages to get a good idea of
how the site will function. If you use a Web authoring tool at this early stage, you
run the risk of your manager or client thinking you already have the site half
done and insisting on early delivery.
Document Each Page. While this may seem unnecessary, lack of content is a fre-
quent cause of Web site project delays. Prepare a content sheet for each page,
such as the one shown in Figure 10.3 (available at Chapter10/contentsheet.doc in
the student files), which describes the functionality of the document, text and
graphic content requirements, source of content, and approver of content.
Figure 10.3
Sample content
Search WWH ::

Custom Search