SILS iSchool

17 Sep 2018

Value Added | daily

Class Schedule

Basics | sessions 01-05

22 AUG | intro
27 AUG | clients
29 AUG | servers
05 Sep | networks
10 Sep | basics lab

Web Development | sessions 06-11

12 Sep | structural layer

 17 Sep  | presentational layer | in practice | 02.02 |  planning  | next session

19 Sep | working with layers
24 Sep | behavior layer
26 Sep | images & design
01 Oct | website lab

Document Markup | sessions 12-14

03 Oct | object layers
08 Oct | tools that read markup
10 Oct | document markup lab

Spreadsheets | sessions 15-19

15 Oct | spreadsheets
17 Oct | formulas & functions
22 Oct | data display
 18 Oct | Fall Break 
24 Oct | database tools
29 Oct | spreadsheets lab

Relational Database | sessions 20-26

31 Oct | relational databases
05 Nov | tables
07 Nov | relationships
12 Nov | input & output
14 Nov | SQL
19 Nov | complex queries
26 Nov | databases lab
 21 Nov | Thanksgiving 

Presentation | sessions 27-30

28 Nov | presentation design
03 Dec | presentation delivery
05 Dec | presentation lab
12 Dec | 0800-1100 | final in class presentation

After you finish task 02.02, start to think about your fuller site.
Keep the users in mind as you design your site.
Ensure that the users are never confused about where they are in your site structure.
Ensure that your design speaks for you.

As you begin to design your website ...

... think about designing it in terms of the user(s) of the site

Take a few minutes and decide on a "theme" for the page(s) you are creating. Decide the structure of the site and what images you will need.

back to top

You want to consider that the development cycle for web sites has four stages

  1. The first stage is to develop content and format in tandem
  2. The second stage is to view the results
  3. Third, to make repairs as necessary. At this time you will either return to the first step to add content, or go to the fourth step
  4. Fourth, publish the page

back to top

Why do we concern ourselves with design issues?

Jakob Nielsen suggests that we have an absolute need for design standards.

Standards ensure that users
  • know what features to expect
  • know how these features will look in the interface
  • know where to find these features on the site and on the page
  • know how to operate each feature to achieve their goal
  • don't have to ponder the meaning of unknown design elements
  • don't miss important features because they overlook a non-standard design element
  • don't get nasty surprises when something doesn't work as expected

You cannot go wrong by following the direction given in the Web Style Guide [linked from every page on the class web site]. But we will review some basic considerations and offer a way to approach the process of designing your web site. The principles are pretty straightforward:

know your audience,
keep it simple,
be fast,
know the rules before you knowingly break them

back to top

Define the purpose and the target audience

What is your intent? what is the message you wish to convey, both in text and in feel?

Who are you trying to reach? who is your target audience?

Think about the audience

  • tailor your look and your content to appeal to this audience
  • consider their needs and their limitations

back to top

Determine the structure of the site by sketching the navigation structure

What is the top level page? This is home page, the page that will open when a user types in the URL of your web site's directory

Are there any second level pages? If so, they are children of the home page

Are there any third level pages? If so, each third level page is a child of the second level page it is subordinate to

  • one might stretch the metaphor by thinking of the home page as the parent, the second level pages as children, the third level pages as grandchildren
  • of course, this means a page might have a parent, some siblings, perhaps some children, even some aunts and uncles, and cousins

A sketch will help you keep the relationships clear

back to top

Determine the content and navigation for each page

What kinds of text, images, or other objects are relevant to the topic of a particular page? Remember, some things add code weight to a page and are thus more slowly loading, but sometimes the object is critical to the message and the load will have to be borne

Within the structure of your web site, plan
to have every page link directly to the home page,
to its parent page,
to its children,
and to its siblings.

Ponder designing a way to place the navigation tools so that they are visually similar
and in the same relative position on each page

back to top

Determine the design of the pages

Don't forget that this are your pages,
so they should represent you in a manner you wish to be represented

how do you plan to lay them out? what objects go where? appropriateness

user expectations: placement

user expectations: consistency

user expectations: usability

back to top

Devise a simple, consistent naming system
for your pages, images, and external files

There are some consistent themes

  • create a main folder for your site on your client
  • create subfolders within the main folder for the various components of your site; store materials for each of the components in their subfolders
  • create a separate subfolder for images

back to top