Class Info
Syllabus 
Schedule
Grading
Peer Review Teams
Website Critiques
Cool Site of the Week

 

Projects
Repurposing
Identity
Final Project
Portfolio
Graduate Paper

 

Resources
Help
Listserv & Archive
Make Your Own
Media
Widgets
351 Community

 

On the Web
All things nonlinear
Information architecture
Webs on the edge

 

 

 

Notes on Posting Links Peeer Review Teams
and Commenting on Websites

When you post a link for a prototype or preview draft of a website project, please include a paragraph about what you are trying to accomplish. You can include any questions you may have that you would like your reviewers to address. This paragraph will help focus your reviewers.

Prototype reviews will typically be done in class in a small group setting. If you miss your group meeting, you may make up the review if you visit your team members’ websites and write comments within one week of the group meeting. Preview responses (which are done on the web outside of class) should also be completed within one week of the preview posting due date.

Here is the seemingly torturous process I would like you to follow in completing your group review session on prototype webs.

Fire up two computer. Go to our community website.

On both computers: In the peer review team block, click on a name, then click on view all blog entries.

Now it gets different.

On one computer: click on the website of the prototype you are discussing.

On the other computer: Start a new comment to the blog entry that announces the prototype url. I would like all comments to be done as comments (this will help me keep track of them). Please type in the names of the people who are there in your group (this is so I will have a record of who attended and can give appropriate credit).

Now the author of the site should talk about what he or she is trying to accomplish, what questions he or she has and what concerns. As a group talk through these issues, and discuss the prototype. Use what you have learned from Krug to talk about the site:

1. Use a clear visual hierarchy.
2. Be consistent, use conventions.
3. Break pages into clearly defined areas.
4. Make it obvious what's clickable.
5. Keep the noise down.

Unless the site is very experimental, the first page should tell you where you are what the site is about and why go on. You should have clear expectations about where the links will take you and why you should click them. The organization of the site should be clear. Click on each of the links that work. Do you know where you are going? Why you are going there? How to get back? The scribe should record the highlights of this conversation in the new comment he or she has started.

Repeat this process for each of the people in your group.

 

 


 

English 351: "Hypertext"
Jim Kalmbach
421H stv 438-7648
kalmbach@ilstu.edu