IT350 - Web and
These past few weeks you’ve learned about how to apply HCI principles, including those of feedback, affordances, memory, and consistency to a website. We have also read about and discussed web site style (in the broad sense) and design.
For this week’s lab, you will redesign the IT350 web site to make it more attractive and functional. When complete, we will have a competition where you judge the results. Winners from each section will receive fabulous prizes, and the grand prize winner (as chosen by the instructors) will have his or her site promoted to official IT350 web site status.
Note that this week you are not using the web pages that you previously created. Instead, create one new folder on your Web drive called "Lab04" (without the quotes) and store your work in that directory.
1. Copy files: download this zipped version of the IT350 web site. Unzip these files into your Lab04 directory. This is not a complete dump of all the IT350 files, so some of your links will be broken. However, verify that you can correctly access the following pages:
2. Split up index.html: You want to divide index.html into at least 3 different “content” pages: index.html (with reduced content) as main page and 2 more content pages. For instance, you might want the course resources to be a separate page, and the course links to be a separate page. For now, you don’t need links between these pages.
3. Create a navigation bar: This should have links to each of your “content” pages that you created above, including a link to index.html, and you probably also want a link for the calendar. Add this navigation bar to index.html. You can place the navigation bar wherever you like, but use CSS to give some reasonable layout and positioning.
4. Add SSI:
5. Rename Lab04/index.html to Lab04/index.shtml.
6. Modify Lab04/index.shtml to include your navigation bar using SSI (instead of having it actually part of index.shtml).
7. Modify all your other content pages, including calendar.html, to also include the navigation bar. You’ll need to rename them to end with .shtml
8. Modify your navigation bar to link to .shtml pages, not the old .html pages.
9. Make sure your SSI site is working properly before you proceed.
10. CSS for different affordances. In class we discussed the important of perceived affordances. One ramification of this is providing affordances for those with disabilities such as blindness or poor vision, for which different fonts or cues for Braille readers are helpful. CSS2 provides different media types to provide this, including those for low resolution devices and Braille readers. For this lab, you will simulate (and learn useful tools to make page printing different from screen display) as follows: add something to your CSS file for the “print” media type that makes printing noticeably different from on-screen view (use Print Preview to verify that this works). Here is an example: http://www.w3.org/TR/CSS2/media.html#at-media-rule
11. Redesign: Now redesign the IT350 web site that you have in your Lab04 directory. Try to make it both more attractive and more functional. You have free rein to change the site in any way, including adding or combining pages, module a few restrictions:
a.) Essentially all the content from the old IT350 web site must be present in the new web site.
b.) You may add new content if you like, or different views of old content (e.g. to show due dates in a different way).
c.) You must make use of CSS and an external stylesheet to apply some styling.
d.) Your final CSS must have the “print” media change discussed above.
e.) The final product must be suitable enough in taste and functionality that it could be used as the official IT350 web site.
Note that the calendar already uses a stylesheet named “calstyle.css” (not the “styles.css” we used before). You can modify this stylesheet if you like or create a new one. You may also change the layout/HTML details of the calendar page, but it should still make use of some stylesheet.
12. Goals: When complete, the IT350 website should exhibit:
· Improved functionality
· Improved appearance
· A consistent look
13. Final tips:
· You are not required to add additional comments to course web pages beyond what is present already.
· Pages that validated before (index.html) must validate in your version. Pages that did not (calendar.html) do not have to validate.
· You must test with more than one browser!
14. Final links: Add a link from your default.htm page to Lab04/index.shtml.
Your web pages must be constructed using Notepad or a similar text-only editor. The use of programs such as Microsoft Word, Microsoft Frontpage, DreamWeaver, ColdFusion, Mozilla Composer, etc. will be considered an honor offense.
NOTE: some of the pages from the IT350 site (the course policy, the labs, lab guidance) were constructed with Microsoft Word. You can modify/re-create these pages if you like (still using a text editor), but it is definitely not required. These files are not included in the ZIP file but you can download them from the web if you like.
For a nominal amount of extra credit do some/all of the following:
1. A floating nav bar with SSI may not mesh well with the parts of calendar.html. Try deleting the “width=95%” that is present in the start of each table in that file.
2. You are not required to make links to things like the Course Policy, Lab Guidance, etc. work (though you can if you want). These are relative links that would work if those files were added to your website, or if your webpage was substituted for the official IT350 web page.
3. IE error: “The XML page cannot be displayed. Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.” If you get this error, try using Firefox instead. If Firefox works fine, then you can blame it on IE bug and proceed. If you want to try and fix it, try deleting all blank space and comments between your DOCTYPE declaration and the start <html> tag. I found this sometimes (but not always) corrects the problem. The problem seems to usually occur when accessing things from the file interface, not when using the web server.