Class of Sep 22 notes

Most sites are producer and creator determined. Created to looks good.
They should be user usefull.
For the customers.

We want to look what users want to do, what they need to do, and how they do that.

Factor are people, who is it for, as well as who is it done by.

The emphesis of this course is not how it looks like, and how it works,
but what users will do.

The audience is different: project to project.


We've got to go to other people, to ask how they would use the website.
Create user scenario.

Case study.
screen resolution
1000x680
that proportion (or size) can beacame emplate for the scematics
If something is below the fold we schold show it in the schematics.

Develope:
1. Concept
2. Proposal
3. User scenario
4. Task analysis
5. Information architecture - sitemap
6. Schematics
7. Comps (comprehensive graphics)
8. HTML - assembly

Grasroots Website

Information

a. developing information
Users - who are the primary users of the web site. (amd who they are not)
I.e. the water charity
likely : - sponsors
- founders
- donors
- volunteers
- press/media/journalism
- partners (other organizations)


Next step is to give them a characteristics. We need to get profiles of potential users.
"what are you looking for if yu are one of the sponsors?"
"what I would want to know?"
i want to see how many project they run, maybe have annual report, waht the progress is, who the other donors are.

Ones we establish user scenarios into tasks, starting working on the landing level.

You don't want to ask user to click more than 3 times to get somewhere. Design web site to have only 2-3 levels. More click was in web sites of 2nd generation, now we have 4th generation of web sites.

The most important things needs to be on the to of the screen, not below default (seen screen).

TASK ANALYSIS

Website archtecture