Designing for the Web:
Best Practice for Web Layout & Design

You may print this page if you feel the need.  But we will be updating it as needed; so the online copy will always be most up-to-date.


Browser Compatibility Across Platforms

[ back to top ]

Different browsers, operating systems, and computer hardware are just that; they are different.  Each design team has their own language and menu structure (Refresh vs. Reload, Favorites vs. Bookmarks, Save as... vs. Save Page As..., Tools vs. Options).

Be mindful of this when authoring.  Either be generic enough that most users will be able to follow, or note the browser/OS/etc. when giving directions (e.g.: In your Firefox browser, from the File menu, select "Save Page As...").

Not everyone has the same size monitor.  Not all computers have mice.  And, like browsers, the different operating systems have different tools and nomenclatures.

When you author, you should be prepared to test your pages using different browsers and different operating systems.  On campus, we are lucky; we have both Macintosh computers and Windows machines in the labs that we can use to look at our pages.

And remember that users may set their local display to override your font/sizes, some users will use text-only browsers, and some users will use screen readers to hear your content.

Note that I said most users.  You will not please all of the people all of the time; but this is no excuse to design only for Internet Explorer on a Windows machine.

Questions?  What operating system and web browser do you use/prefer?

Exercise: Under what circumstances could you see yourself designing for only one browser on one platform?


General Layout & Design Principles

[ back to top ]

Remember what the focus of your page is and who your audience is; be sure that everything on the page supports the communication of that goal to that audience.  Everything else I say in this lecture is contained in this simple yet far-reaching sentence; your care for all your users, their varying skills and challenges, your use of color, links, layout, content, all of it is concerned primarily with your goal and your audience.

  1. Before you start typing, plan out your site.
    • I like to sketch my pages on paper; I include layout features, placement of images, text and links.
    • How many pages do you need?  One big page or several small ones?
      • How will this impact printability, download time, scanability, maintainability? 
      • Your content and your users' needs guide you in all this.
  2. Weigh your content and place it accordingly, on your page(s).
    • Our eyes typically are drawn, first, to the top left of a page; we scan left to right, top to bottom.
  3. Just as in printed media, exemplary spelling and grammar are very important. 
    • Your readers will judge you, your department, product, argument, etc. based on your style, word choice and accuracy.
    • You might find it useful to pick up a copy of Strunk & White's The Elements of Style:
      http://en.wikipedia.org/wiki/The_Elements_of_Style
  4. Be clear, consistent and brief. 
    • Pages should provide enough contrast to make them easily readable.
    • Don't vary the position of navigation on your pages, without good reason.
    • Beyond the quality of your content, remember that internet users are notoriously impatient.  Few will read very far to see if you will make sense, or bring a tangent back around to the point.
  5. Design for scanability.
    • Use text style (bold, color, lists, etc.), graphics and layout to simplify browsing. 
    • When you do use larger blocks of text, don't assume browsers will read all your carefully crafted content.
    • As in journalism, try to make your first sentence in each paragraph encapsulate the idea (thesis) of the paragraph.
  6. Don't overuse emphasis.
    • If your entire page is bold, how can your users distinguish what is more important from what is less important?
  7. 508 compliance and the Americans with Disabilities Act:
    • Screen readers read pages left to right, top to bottom.
    • Contrast is also important, considering certain colors (red/green colorblindness).
    • I'll talk more specifically about accessibility, below.

Exercise: Discuss these two web sites; what are their strengths; what are their weaknesses?
http://library.csusm.edu/
http://www.csusm.edu/HR/

Questions?  What medium will you use to plan your website before you begin?  Will you have long pages or many pages?  Will it be an image-heavy site or more text?  Why?


Links

[ back to top ]

Like everything on the page, a link should serve the goal/audience of the page.

Hyperlinks provide much of the dynamism of the web.  Considering that all content is linier (we only see one thing at a time); being able to jump from one resource to their next interest and, perhaps, back gives your users a freedom to personalize the way they experience your content.  Consider how hypertext differs from a novel, a movie, or reading a play with footnotes.

  • While many of the best practices we talk about today will highlight the similarity to for-print-media; links are a huge difference.  Are they a blessing or a curse?

    Exercise:
    How do you think allowing access to content via hyper-media (instead of printed-media) could be a blessing or a curse?
     
  • You can link to just about anything: text, hypertext, images, sounds, movies, third party files (Excel, Word, PDF, PowerPoint, Flash, etc...).

When creating links, try to make the linked text describe the linked resource. 

  • Consider these options:
    More information can be found in our course catalogue.
    For more information, click here, for our course catalogue.

    The first example aids users in scanning your text.  And screen readers, which allow users to jump from one hyperlink to the next, are also benefited by being able to read link text that is related to the linked resource.

For portability, it is best to use relative links instead of fully justified links. 
[Draw: garrett/electures/DesigningForTheWebSp07/index.html linking to garrett/electures/WebPublishingWithFrontPageSp07/index.html]

  • ../WebPublishingWithFrontPageSp07/index.html
  • http://www.csusm.edu/garrett/electures/WebPublishingWithFrontPageSp07/index.html

    Exercise: How do you think each of these examples would work if I moved the electures directory?

Questions?  Would it be a good idea to link every word in a block of text, so that users could easily get a definition of each, as needed?


Effective Navigation

[ back to top ]

Navigation should be driven by the content and by user need.  What does that mean?

Clear and consistent navigation is a must.  Users don't want to hunt around on your page for the link to the information they are looking for.

  1. Navigation provides users with a logical map of your site. 
    • When you first plan your site, be sure to include the logic of your linking structure.
    • Think of what information logically goes together and where a user may want to go to next, from each of your pages.
    • Navigation structure need not reflect file structure (but you might want it to).
  2. Often it is best to place navigation where users expect it:
    • Vertical navigation, along the left edge of your page
    • Horizontal navigation at the top (but sometimes also the bottom) of your page
      Question: Why would you place navigation at the bottom or right side of a page?
  3. Often times the navigation of your home page is unique; but child pages are usually consistent amongst themselves.  The key is to have a consistent design.
  4. Contact information is an important thing to include on each page.
    • Whether it's a footer with your information or a link to a contact page/form.

Look at http://www.csusm.edu/ and note top level and secondary level inconsistencies; but also note secondary level consistency.  One of the major challenges in this very content rich site is providing navigation for important elements without overwhelming users.

Questions?  What challenges might you face with navigation and long pages; what about with many short pages?  How many links do you think is optimal for a navigation bar?


Images

[ back to top ]

Though links are more unique to hypermedia, it was images that spurred the web to be what it is today.  Just like in print-media, images add richness to web pages.  And, like most things, they can be an asset or a drawback to your site.

Be mindful of your users' needs when including images in your pages.

  • File size constraints: the larger the size of the image file, the longer the download/display time.
    • Many web authoring applications give you an estimate of how long your page will take to download/display.
    • Don't use the IMG tag height and width to shrink the display of an image.  The time it takes the image to download is based on the file size, not the display size of the image.  It's best to use a program that will actually allow you to scale the image (not just its display size).
    • Cropping images is a great way to do two things:
      • focus the image on its subject, to better direct the users' attention
      • and to reduce the file size
  • Display size constraints: an image that is larger than the user's monitor will cause the page to scroll, left to right (I don't recommend this).
    • Image width is also an issue when printing.
    • Consider using thumbnails that link to larger versions of your image.
Question: What image editing software do you plan to use?

Generally, we see two types of images on the web: GIFs and JPEGs (or JPGs). 

  • The .gif format is best used for line-art, black and white scans, screen shots, etc. and the .jpeg/.jpg format is best used for photos (or art that has fine gradations of color).  Using the correct image type effects file-size and download time.

    Question: Which image type do you plan on using most and why?

Images are great!  But like emphasis, if you use too many images your pages will look cluttered and it will be hard for users to differentiate what is more important.

 508 compliance

  • Adding (ALTernative) ALT information is not only the law, it's the right thing to do.
  • The key to providing good ALT text is to communicate, with words, all that is demonstrated by the image.  Whatever you want your sighted users to gather from the image, your non-sighted users must also get.

Exercise: Consider an image, and think of what your ALT information for that image would be; please share this with the class.

Resources: http://www.picresize.com/
(I Googled: image sizing and cropping program free)


Color

[ back to top ]

Color, like emphasis, should be used to draw users' attention to important information, and to work with images to improve your overall presentation, as it serves the goal of your page.

You can change the color of the entire page background, a portion of the page (using tables and/or CSS); text, and link colors can also be changed.  Here is an example of a page that has different colors.

Exercise: Consider the example above.  What does this tell us about the priority that is placed on global colors (for the document) vs. local colors (for table cells and individual words)?  What is the order of precedence?

Color should not distract a user; it should not make your pages a riot of color (unless your pages are supposed to look like a circus act).  And, even when you are working on a project that should be brightly colored, color should serve your goal.  http://www.ringling.com/

Generally, when I choose color, I consider the graphics I will use in the site, and pick similar colors or shades.  Most authoring tools have an "eye dropper" tool, that allows you to select colors from a graphic; this allows you to sample the color of an image and to pick colors and shades that are complementary.

Color, unlike graphics, is rendered mathematically; so it saves on download time.  Used with graphics, it can accent without being a performance hit.

Exercise: Consider http://www.csusm.edu and look for where color has been used instead of (or with) graphics.

Color is dependant on the monitor your users have and its display varies based on operating system.  remember to test your page(s) using different hardware and software.

Web colors are expressed, in the code, in hexadecimal.  Hex value is based on a color's Red-Green-Blue (RGB) value.  But most authoring tools have a color pallet you can choose from.  Wikipedia has a pretty good explanation of hex: http://en.wikipedia.org/wiki/Hexadecimal [but give the class a quick run down of hex, associating it with RGB values]

Resources:

Questions?  Will you images and color together in your site?  What colors, if any will you use and why?


META Information

[ back to top ]

So far we have been talking about content that is displayed on the page.  But some important information is not displayed anywhere in the <BODY> of the page.  META tags are contained in the page <HEAD> section.

Meaning "after" or "with", this is the data that comes with what is displayed for the users.

META data is most commonly used by scripts (that expire content) and spiders (that catalogue it).

Here are a few common META tags:

  • <META name="description" content="Everything you wanted to know about META tags, from function to placement and syntax.">
    • Used by search engines to describe your page.
  • <META name="keyword" content="synonyms, and, alternate words, go here">
    • Keywords used by search engines to index your document in addition to words from the title and document body.
  • <META HTTP-EQUIV="expires" CONTENT="Wed, 26 Feb 2007 08:21:57 GMT">
    • A script could use this tag to expire content on the date.
  • <META HTTP-EQUIV="refresh" CONTENT="3;URL=http://www.csusm.edu/">
    • After three seconds, the users is redirected to the URL.
  • <META NAME="robots" CONTENT="NOINDEX,NOFOLLOW">
    • This would stop spiders from indexing and from following links on the page

Other information besides META tags is contained in the <HEAD> section of the code.  Here's an important one:  <TITLE>Designing for the Web</TITLE>

Questions?


Cascading Style Sheets (CSS)

[ back to top ]

Used to define layout and stylistic elements on a page (or pages), CSS separate content from the presentation of the content.  As the name suggests there can be different, cascading layers that govern layout and style.

Authors of web pages can use external style sheets that govern all content or internal style sheets that govern blocks of content (or both, with the internal trumping the external, just as we saw in the priority of color in HTML).

CSS can allow the same page to be presented in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser or screen reader) and on braille-based, tactile devices.

Advantages of using CSS include:

  • Presentation information for an entire website or collection of pages can be held in one place, and can be updated quickly and easily.
  • Different users can have different style sheets: for example a large text alternative for visually-impaired users, or a layout optimized for small displays for mobile phones.
  • The document code is reduced in size and complexity, since it does not need to contain presentational markup.

Exercise: How do you imagine using CSS can help you author 508 compliant documents.

I drew heavily from: http://en.wikipedia.org/wiki/Css

Questions?


Problematic Web Design

[ back to top ]

You've all seen web pages that were well designed and others that were poorly designed.

[Discuss tables, frames, text-only versions and 508 compliance]

Exercise: Consider blinking and scrolling text; what's the difference between drawing attention and stealing the show?

Content that requires a plug-in (does everyone know what I mean by "plug-in"?): You must balance having the cool content vs. sending the user off to get the needed software, install it, (often they need to) restart their browser, return to your page, to see the content (though Firefox is very good about compressing the last two steps).

Exercise: Why might you type out a full URL in one of your pages (as I have above), as opposed to just linking text to the destination?

Questions?  What are some problematic designs that you've seen, that we did not cover?  Please be prepared to share one example with the class.


Forms

[ back to top ]

Web forms allow us to take information from browsers and "do things" with it via a script. This allows an additional level of dynamism in our web sites and the browsers' experiences.

Before you begin, consider the data you want the browser to submit. Web forms have several possible form fields, like the: text box, scrolling text box, option/radio button, check box, drop down menu... and a few more we won't cover today. [talk about each fields logical application]

The kind of data you want to gather will dictate the form field(s) you choose.

Via the script that processes the form data-pairs, you can write the data to a file (separated, text, HTML, etc.), send it via email, write it to a database, etc. 

There are many scripting languages you could use to process form data, depending on the operating system you run your web server on.

There are sites that have graphical user interfaces (GUIs) to help you make forms, then they also host your form(s).
http://www.ipetitions.com/
http://www.surveymonkey.com/

Questions?  Do you plan to use web-forms?  If so, how will you process the form data?


Really Simple Syndication (RSS)

[ back to top ]

RSS is a family of web feed formats used to publish frequently updated digital content, such as blogs, news feeds or podcasts.

Programs known as feed readers or aggregators can check a list of feeds on behalf of a user and display any updated articles that they find.  Here's an example email you might receive from a RSS enabled web forum.

The result is that users that subscribe to specific feeds need not (re)visit a site and check to determine if updates have been made.  Their aggregator will "push" any new content to the user, as it becomes available.

I drew heavily from: http://en.wikipedia.org/wiki/RSS

Exercise: What might you use an RSS feed to keep track of?

Questions?


Please fill out the evaluation for this course.


[ Designing for the Web ] [ Front Page 2003 ] [ Dreamweaver 8 ]
[
More Advanced Front Page 2003 ] [ Introduction to Photoshop CS3 ]


This page http://www.csusm.edu/garrett/electures/DesigningForTheWebSp07/index.html
maintained by Garrett Collins (garrett@csusm.edu)
for IITS, User Support Services

Last updated Wednesday, February 13, 2008 09:26:05 AM