Web Design



index
Disabled back button Next Section
printable version




Section 0: Module Objectives or Competencies
Course Objective or Competency Module Objectives or Competency
The student will be able to explain the differences between web-based systems and conventional systems. The student will be able to explain how considerations such as a quality site design plan contribute to the success of a web-based system.
The student will be able to explain how considerations such as the purpose and intended audience contribute to the success of a web-based system.
The student will be able to explain how considerations such as site structure contribute to the success of a web-based system.
The student will be able to explain how considerations such as page design contribute to the success of a web-based system.


Section 1: Introduction

While few people realize how much work goes into planning and developing a good design plan, the overall design of a website is critical to its success.

A psychology professor at Carleton University found that Internet users judge whether they like or dislike a website in one twentieth of a second based on the web site's "visual appeal."

Further, several studies have shown that the quality of page design is an indicator of credibility.



Section 2: Primary Considerations

When designing a web site, it is absolutely essential to remember your purpose and your audience.


Purpose

The purpose of the site should serve to remind you that functionality is at least as important as appearance.

Some examples of web site purposes include

These links discuss purpose:


Audience

Defining the audience is a key step in the website planning process.

Considering the characteristics of the audience will allow an effective website to be created that will deliver the desired content to the target audience.

These links discuss audience:



Section 3: Site Structure

Site structure is a larger aspect of design that will often be decided by the purpose.

You could think of the structure of a website as how it would look if you printed every single page and arranged them on the floor of a room.

There are a few main structures:

Most complex web sites share aspects of all four types of information structures. Users are likely to use any web site in a free-form "web-like" manner, just as most reference books are used.

However, the nonlinear usage patterns typical of web surfers do not absolve the designer of the need to organize the content and present it within a clear, consistent structure that complements the design goals for the site.

Here is For more on sites structures, see the following;



Section 4: Page Design

For any website the first design consideration should be usability.

When it comes to actually designing pages, there are literally hundreds of things that could be discussed, but we'll cover only the most important aspects of page design.


Layout

Make sure important content is placed toward the top of pages, as some users are lazy and may not feel like scrolling down to find what they're looking for.

  • Think of the top of your pages as prime real estate, don't waste it with non-essential content that could just as easily be placed in the body of the page.

Jakob Nielsen’s 2006 study on user scrolling (in Prioritizing Web Usability) revealed that only 23% of visitors scroll on their first visit to a website.

  • This means that 77% of visitors won't scroll; they'll just view the content above the fold (i.e., the area of the page that is visible on the screen without scrolling down).
  • What's more, the percentage of users who scroll decreases with subsequent visits, with only 16% scrolling on their second visit.
  • This data highlights just how important it is to place your key content on a prominent position, especially on landing pages.

This doesn't mean you should cram everything in the upper area of the page, just that you should make the best use of that area.

  • Crowding it with content will just make the content inaccessible; when the user sees too much information, they don't know where to begin looking.

Also consider page size and layout.

  • Try to avoid text that crowds the edges of the browser window.
  • Remember white space! (More on this later...)

Fonts

Some sites look best with a certain font, but it's not guaranteed that all site visitors will have that font installed.


Colors

Subtle things like color choice can end up making a big difference on the overall design of a page.

According to an article from a web design business, research reveals that when humans assess an item like a web page, between 62% and 90% of that assessment is based on color alone.


White Space

White space is the empty space between paragraphs, pictures, buttons, and other items on the page.

White space also makes content more readable.


Consistency

The selected design should be used consistently.

Sites need to be externally consistent, that is, consistent with general practice.

Sites also should be internally consistent: standards and conventions should be established and applied throughout all the content.

Consistency should apply to (at least) the following:


Form Fields

Form fields can be a source of annoyance for users.

And always provide guidance for user input.

Best Practices and Usability for Online Forms


Resolution

There is no one best screen size to design for.

Guidelines:

What are the best screen sizes for responsive web design in 2022? has a useful discussion.


Browser Compatibility

Your site should be able to be displayed correctly for all users.

Remember that just because you use Chrome, Edge, or Firefox doesn't mean everyone else does.

Use a site like Top Compatibility Testing Tools to learn more about testing compatibility.


Accessibility

Accessibility is a general term used to describe the degree to which a product, device, service, or environment is available to as many people as possible.

Remember to make your site accessible to users with disabilities, such as blind users using screen readers, blind users using Braille readers, low-vision users using screen magnifiers, and motor-impaired users.

Here are some examples of things you can do to increase access:

Follow the Web Content Accessibility Guidelines.

Links


Miscellaneous

Other small things will distinguish a great website from a good one.



Section 5: Things to Beware

Too Many Videos or Images

Videos and images, while useful, should not be overdone.

As we established earlier, users judge the page quickly, but also users will only wait about 5 seconds for a page to load before moving on.

Another hint is to set the height and width attributes.


Pop-ups and Pop-unders

Useless pop-ups are the scourge of the Internet.


Plug-ins

Pages with unique plug-ins might discourage users from sticking around.

  • It goes to back to purpose – if the purpose of the site is to host some videos you've made, then obviously visitors are going to be required to have QuickTime or Flash to view them.
  • Investigate alternatives, like the new HTML5 tags.

Flash Intros

On the subject of Flash, avoid long Flash intros.

  • While your Flash intro may be the coolest thing out there, your visitors may not want to watch it every time they visit.
  • At the very least, include an option that allows visitors to skip the intro.
  • Remember that Flash is not supported on iPads or iPhones.
  • (examples)

Applets

Java applets fall into the "don't use them, unless" category.

  • Don't use them unless the purpose of your website necessitates it.
  • Remember, just because you can do something doesn't mean that you should.

Disguised Links

One last thing – users should be able to distinguish a link from text based on either color or underlining.


Miscellaneous

Animated gifs? Let's see...

Following the theme of "Things to Beware", you might want to take time to read these:

For your viewing pleasure, take a peek at these cautionary sites:



Section 6: Development Stacks

A tech stack is broadly divided into the client side (front end) and server side (back end).

Developer Skills.
Front-end and back-end skills

Front-end Developer

Front-end development refers to the client side, that is, a web-site's interactive features.

Front-end developers must be adept at three main languages: HTML, CSS, and JavaScript programming.

Back-end Developer

Back-end development refers to the server-side development.

Back-end developers also create and maintain the entire back end of a system, which consists of the core application logic, databases, data and application integration, API and other back-end processes.

Full-stack Developer

A full stack developer can work cross-functionally on the full stack of technology, i.e. both the front end and back end.


Comparison

Here are some figures detailing the differences between front-end and back-end developers:

Developer Skills.
Brief front-end and back-end tools

Front and back end tools.
Detailed front-end and back-end tools

Front-End vs Back-End.
Front-end vs. back-end


Section 7: Resources
contrast example
original colors
new colors
whiteSpace
whiteSpace