LIS 523 - Assignments

Reports and prepostings are due by 9 am on Wednesdays. There are no reports or prepostings due in the first week. Comments should be submitted by the end of the day on Thursdays. For more details on postings, see LIS 523 - Discussions Online.
  1. Comment (due September 6): briefly introduce yourself. What is your background in relation to Web design? For example, what other related courses have you already taken? What do you hope to get out of this course?

  2. Preparation: read on principles of good Web site design and criteria for evaluating the design of Web sites.
    Report (due September 12): choose an existing Web site and evaluate it in no more than 600 words.
    Preposting (due September 12): post the URL and a one paragraph summary of your evaluation in the online discussion.
    Comment (due September 13): post brief comments on two of the sites examined by other students and at least one comment on what you found in your reading.

  3. Preparation: read on defining the audience for a site and developing site objectives.
    Report and preposting (due September 19): post a preliminary set of objectives for the Web site that you propose to develop for the term project.
    Comment (due September 20): post brief comments or questions on the sets of objectives posted by two other students. Post also a comment on what you think information architecture is or whether the term is a useful one.

  4. Preparation: investigate HTML exporting capabilities of and any other office application software to which you may have access.
    Report (due September 26): do the lab.
    Comment (due September 27): post a comment on how well performs at producing Web pages and also a comment on when the method of simple exporting from office applications would or would not be suitable.

  5. Preparation: read on classification, file naming conventions, and content management.
    Report/preposting (due October 3): Post a brief description of a scheme for file naming and organization that you think might work well for your proposed site.
    Comment (due October 4): post comments or questions on the file naming and organization schemes suggested by two other students and also a comment on features that you would like to see available in content management software.

  6. Preparation: read on graphics formats and options for Web pages.
    Report (due October 10): do the GIMP exercise.
    Preposting (due October 10): post a comment on how you see graphics being used on your proposed site.
    Comment (due October 11): post comments or questions on the comments posted for this week by two other students.

  7. Preparation: read on color theory and page wireframes.
    Report (due October 17): produce a higher fidelity wireframe for the home page of your proposed site using Draw or other drawing software.
    Preposting (due October 17): upload a copy of your wireframe to your Web area and post its URL; post a suggested color scheme for your site with a brief explanation for your choice.
    Comment (due October 18): post comments or questions on the wireframes and/or color schemes of two other students.

  8. Preparation: read on style sheets.
    Report (due October 24): do the Balthisar Cascade exercise.
    Preposting (due October 24): post an idea for a possible addition to stylesheet capabilities that is not currently supported by browsers.
    Comment (due October 25): post comments or questions on the ideas posted by two other students.

  9. [Research week - no assignment.]

  10. Preparation: read on options for dynamic page content and scripting.
    Report (due November 7): do the JavaScript lab exercise.
    Preposting (due November 7): post what you think would be a good method for providing dynamic content on a site and why.
    Comment (due November 8): post comments or questions on the preposted comments of two other students.

  11. Preparation: read on site search engines and site indexes.
    Report (due November 14): do the XRefHT32 exercise.
    Preposting (due November 14): suggest an additional feature for XRefHT32.
    Comment (due November 15): post a comment or question on the suggestions of two other students.

  12. Preparation: read on accessibility standards for Web sites and on structure diagrams.
    Report (due November 21): produce a structure diagram for your proposed site.
    Preposting (due November 21): upload a copy of your structure diagram to your Web area and post its URL; post a brief comment relating to how you will address accessibility issues.
    Comment (due November 22): post comments or questions on the structure diagrams of two other students; post a further comment on site accessibility (for example, a response to a comment on this topic by another student).

  13. Preparation: read on other special considerations in Web site design (such as multilingual sites) and on architecture style guides.
    Report (due November 28): submit a mini architecture style guide (no more than 500 words) for your proposed site. This mini guide should deal only with the following topics: how the site is organized, why, how the architecture should be extended with site growth, and what are the guidelines for adding content and, if an index is included, for introducing new indexing terms.
    Preposting (due November 28): post a comment on one or more of the decisions that you made regarding the architecture style of your proposed site.
    Comment (due November 29): comment on the architecture decisions of two other students.

  14. Preparation: finish up any readings that you have not yet completed for the course.
    Preposting (due December 5): upload your completed site (10-25 pages) and post the URL of the home page; post a couple of points on decisions that you made in the design process.
    Comment (due December 6): post comments on the finished sites of two other students.


Last updated April 24, 2007.
This page maintained by Prof. Tim Craven
E-mail (text/plain only):
Faculty of Information and Media Studies
University of Western Ontario,
London, Ontario
Canada, N6A 5B7