There are three parts to this assignment. Two are groupwork, the last one is individual.
OK, so far your group has discussed how you're going to audit your client website. Meet and discuss what changes to your technique you're going to make in light of today's presentations and class discussion. As part of this discussion, create a design for a webpage that will hold the audit information for one of your client's web pages. You should sketch out a design on paper and then one member of your group should create a template based on that design. (At this point, your template doesn't have to be styled, but you should probably include class attributes for various elements in anticipation that you'll eventually be applying CSS to your audit pages.)
The only way to tell if your audit documents will be usable is to test them out on an actual web page. Meet as a group to audit your client's homepage. (The point of doing this as a group is so that you can make changes as necessary to your auditing technique and document template—working together, you're more likely to discover problems, tell the other members of your group about them, and fix them.)
For Tuesday's class, each group will give a brief presentation on the results of auditing your client's homepage. To make this go smoothly, select a spokesperson for your group.
There should be four (4) more entries in your blog before class meets on Tuesday. (They don't have to appear in this order, though.)
Don't forget to use the emacs timestamp function to put an anchor timestamp on each entry. (The emacs command is Ctrl-c b. It will only work when emacs is in HTML-mode.)
[ Return to the CPSCI 107 homepage ]
Brian J. Rosmaita <contact me>