<%@LANGUAGE="VBSCRIPT" %> <% Response.CacheControl = "no-cache" %>
Project #1

Due Dates:

Project Introduction: Thursday, June 18th, 2009
Thumbnails Due: Monday, June 22nd, 2009 - Midnight
Color Comp: Friday, June 26th, 2009 - Midnight
Audience Analysis & Site Map Due: Wednesday, July 1st, 2009 - Midnight
Project Due Date: Friday, July 10th, 2009 - Midnight

Examples & Grading:

Project 1 Grade Sheet: View the grading rubric

Deliverables:

Zip file containing (each in their own folder):

  1. One page Audience Analysis
  2. Thumbnails (minimum of 6 interations of the site design... more is better).
  3. Color Comp (Not a splash page. Depending on the site, more than one may be required).
  4. Site Map (flowchart of site files and directory structure)
  5. Entire content of the site

Background & Requirements

The goal of Project 1 is to create a web site that demonstrates proficiency with XHTML and raster graphics. The site may include other media assets such as sound or Shockwave components if you so wish to include them. However, the percentage of these elements should not be greater than 10%. Thus a multimedia introduction to your site with Flash or other media is fine, but designing more than 10 percent of the site around any technology other than XHTML and raster graphics is not permitted.

In addition to the specifications below, you will be required to upload your web site to your Purdue account. This will require that you web enable your Purdue account and properly upload your site to the server. For information about web enabling your account, visit http://ics.purdue.edu. For information about viewing your account and other accounts, visit http://web.ics.purdue.edu. Approximately 5 percent of your project grade will be based upon whether you have uploaded your site correctly. Make sure you provide the proper URL for your site on the Project TOC page. Even though you will be uploading your project to the web, you must still turn in a CD-R with a self-created, digitally created, self-adhesive CD label attached to it.

When uploading to the Purdue web server, you must check the following:

  • Case-sensativity. The Purdue University web server is case-sensitive, but your windows development machine in Knoy is not. If you have the page named foo.html but linked as Foo.html, the page will not be found when it is uploaded to the Purdue web server. This also happens often with image names.
  • Sometimes uploading files to a UNIX-based operating system automatically capitalizes the first letter of your files. You may need to check that none of your filenames were changed during the upload.
  • Check your permissions on all files. If any one file does not have the correct permissions, it will not be viewable on the Purdue web server, even though the rest of the files appear to be working fine.
  • Refer to exercise 1, points 2 and 3 for additional help in getting your site displaying correctly using your web account.

The site that you create can be about any topic you wish (within reason & abiding by Purdue guidelines) but it must contain the following specifics*:

  • The site must be aesthetically pleasing and should display an effective navigation scheme.
  • The site must be efficiently and effectively designed (as far as download times are concerned, also arrangement of back-end/file structure)
  • The site must include a starting "home" page with the filename being "index.html". Not a splash page that only has an image and a couple links. The starting home page should look like the rest of the pages in your site, but it would essentially welcome the user in some fashion.
  • The site must include a minimum of 7 content pages. (Content pages do not include headers, footers, or menu pages).
    • A content page is defined as: a page that has enough "content" to fill the entire browser window when the browser window is opened to an appropriate size (at least 800 pixels wide by 600 pixels tall).
    • A page that only has a large image on it does not count as a content page.
    • A content page can contain all text. It can also be a page with an image and some text surrounding it... or any combination thereof.
  • Content pages in the site should be table-formatted pages.
  • The site should not be done entirely in frames, however, a portion of the site requires that you show competency in either (a) creating frames pages or (b) using an iframe, as stated below. (you have to complete one or the other, you do not have to complete both).
    • If creating frames, it is OK to use a target of _blank for this such that the frames portion loads in a new window.
    • If creating frames, you must have one frameset document with 3 links that target a frame and load content into that frame.
    • If using an iframe, you would place that into your site where appropriate.
    • If using an iframe, you must have at least 3 links that target the iframe and load content into that iframe.
  • The site must include 1 data table of sufficient length (at least 7 x 7 [or other combination consisting of at least 49 data cells]).
  • A navigation structure should exist and there must be at least 3 targeted links (these can either be links that target a specific frame or links that target a specific window for loading).
  • The site should include at least one self-created animated GIF.
  • The site must contain one image map (preferably on the home page)
  • The site must also contain at least one PNG, one JPG, and one GIF (not animated) graphic (one of each, appropriately used).
  • The site must include both intrasite and extrasite links.
  • The site must include at least one email link.
  • At least one content page should utilize a target/name anchor set (an link that sends the user somewhere else in the same document).
  • The site must include at least one form, containing at least 5 form elements, that sends data to an email address.
*Note that these specifications are the minimum expected. "A" projects will demonstrate things that are over-and-above these minimum requirements.

Note: This project is to be done by hand/hard-coding. No editors! Use of an unapproved editor will result in an automatic zero (0) as a grade for the project!