Web Design
Web Design
• The nature of the content. A web site designed for students should look
drastically different than one designed for retirees. A site designed to
convince alumni to donate should look different than one that is to be used as
reference material for graduate students. The content drives the design for a
site.
• The economy (budget, time, and scale of the project). Keep in mind
that there are always limiting factors on what you can accomplish. You may
not have the funding or the time to put together a “perfect” site. Also,
remember that the scale of the project should play a factor in allocating
resources – for example, a site devoted to a graduation party should not be
given as much time and effort as the complete redesign of the department’s
main web site.
• The amount and type of visuals included. Don’t forget to factor in the
costs and time needed to obtain the photographs and other visual elements
(buttons, line art, etc.) that you may want to employ on your site.
• Making the site easy to use. If you need to take a class in order to
understand how to use the site, you probably should re-think the way the site
has been put together. Items should be located where visitors expect them
to be. Visitors expect web sites to be flawless and to do what they want. Be
sure to test the site out with people similar to your target audience and
implement their suggestions for improvement (even if it means adding days
or weeks to the project). The biggest mistake in web design is building a site
for the designer, not the target audience.
• Using a uniform look and feel. Most people come to a web site via a
search engine such as Google. More often than not, the search engine dumps
a visitor onto a secondary or tertiary page, not the main page for the site. If
the subsequent pages do not contain the look and feel of the main pages,
visitors may become confused and think they’ve gone to the wrong site (and
may leave).
Ideally, try to skip the problems of Generations 1-3 by planning your site carefully.
1. The “Ad-hoc” Process. The ad-hoc process occurs when a designer hastily
puts a site together, often creating it on-the-fly, without much forethought or
planning. It generally occurs when a designer is told that the site needs to be
put together immediately, and there isn’t enough time to do any planning.
• Very small web sites. If your site will only have 3 or 4 web
pages, there isn’t a big need to do a lot of user testing or other
planning. There just isn’t enough content to justify weeks of
preparation.
That said, generally there are many problems and pitfalls of using the ad-hoc
process:
• Since they are hastily put together, designers often forget that
the site even exists after awhile. For this reason, sites designed
in this way often contain old content that doesn’t get updated,
contains errors, and uses dated design and techniques.
They also usually end up taking less time overall to create and maintain.
The pages that follow will describe the steps you need to take in order to
design using this methodical, well-thought-out process.
1. Consider your organization’s mission. Why are you designing this site?
How will the site enhance the mission?
2. Define the target audience. Who are the types of people that will be
coming to your site? How old are they? What type of educational, socio-
economic, ethnic, gender-based backgrounds do they have?
o Deciding who will maintain the site once it’s gone live. Do you
need to hire a full-time designer? Will you outsource the
upkeep?
4. Gather the content from subject matter experts (SMEs). The person
designing the web site likely isn’t the same person who is writing the policies,
history, or other informational pieces that will go on the site. The designer
will need to contact these subject matter experts and gather the content from
them.
6. Sketch your web site on paper first. Don’t try to code your site until you
know how you want it to look. Use a flowchart to help you decide how
visitors will go from one page to another.
7. Think about the actual HTML, PDF, graphic, sound, and other files you
will need in the site. Where will they be placed? How will visitors access
them? Will visitors need special tools to use them (e.g., Flash)? Is there a
way to provide similar information that doesn’t require special tools?
8. Organize the files logically, so that the development team can understand
the hierarchy of the web pages.
• User screen sizes. 88% of users are using a display with 1024x768
pixels. Sites using a fixed-pixel length content box of 800 pixels or
less risk alienating users who have larger monitors.
http://www.w3schools.com/browsers/browsers_display.asp
Influences of Content
• The content drives how the web site looks. Sites designed for students
look different than sites designed for staff, which look different from sites
designed for potential faculty. Sites designed for current employees look
different than sites designed for potential clients. Sites designed to get
people to purchase items look different than sites designed to provide
information
• Have non-affiliated people review content for clarity. Did what you put
on the site make sense? Are all instructions listed on the site clear? Make
sure someone checks your site for spelling, grammar, and factual errors.
Fresh eyes often see things you miss!
• Key benefits:
• Disadvantages:
o Time spent on web site can’t be used for other things. For
example, if an admin is working on the web site, it means he or she
cannot be working on the budget, organizing meetings, filing papers,
filling out forms, or other administrative work.
o Must have staff expertise. You can’t design a web site if you don’t
understand HTML, CSS, or graphic design.
• Key benefits:
o You don’t need an in-house expert to create the web site. This
frees up local staff to do other jobs.
o Start-up fees are upfront. Most designers charge a flat rate for
designing the site. They may charge an hourly fee to update or
maintain the site, however.
• Disadvantages:
Remember, there are no generic people. Try to envision a real person accessing
your site, preferably someone similar to the type of person who would use your site.
• Most users absorb data visually. Don’t put too much information on a
page. Limit the number of items in a group of choices. People can absorb
around 5-7 disparate ideas at once; if you have more than 10 topics on a
page, you’re running the risk that people won’t read your site.
• Most users will not expend effort to remember things about how your
site works. Don’t force visitors to remember how to navigate/use the site.
If a user needs to take a class in order to use your site, you probably need to
think about re-designing it to make it simpler to use.
• Many people have poor eyesight. Use lots of white space. Use high
contrast between the text and the background. Use larger fonts.
Otherwise…
Without a progress bar or other browser feedback, users generally will go about
other business – look at sites in other windows, talk on the phone, etc. Designers
must provide some sort of indication as to how much longer the download will take,
if the wait will be more than 10 seconds.
• To look cool.
• To look cool!
• To draw attention.
• To maintain attention.
• To enhance information.
• To inform or educate.
Be sure to:
• Proofread for grammar -- fresh eyes may catch things you miss!
Vincent Flander’s Web Pages That Suck: Learn good design by looking at poorly
designed web sites
http://www.webpagesthatsuck.com/
Web Site Optimization Analyzer: Analyze time it takes for web site to load
http://www.websiteoptimization.com/services/analyze/
Books
• HTML & XHTML: The Complete Reference by Thomas Powell (ISBN: 0-07-222942-X)