Due Dates:
Project Introduction: Thursday, July 29, 2010
Project Due Date: Aug 4 before 8:00 PM.
Examples & Grading:
Project 2 Examples: Browse these examples **These may not be the best examples, but they are examples nonetheless
Project 2 Grade Sheet: View the grading rubric
Deliverables:
- Email Professor Glotzbach:
- Zip file containing your entire website.
- Word Document: Table of Contents: Use this template. View a completed old example.
Background
This project is designed to combine and assimilate all of the things that you
have done over the semester. Thus, it will be a site that contains all of the
major features/capabilities of XHTML plus added enhancements via CSS and Javascript.
The content for this final web site can be anything you want, a personal site,
a corporate site, whatever (within reason, and abiding by the rules set for
by Purdue University and the course syllabus). This site cannot be the same
as project 1. However the site must include the following items*:
- All pages must adhere to the standard page setup requirements.
- All pages must validate using XHTML Strict.
- The finished site does not have to be uploaded to your Purdue web account (or other approved location), but it would be good practice for you to do so. If you choose to do this, you can include a link to it in the email you send that contains your zip file.
- There should be a well-designed method of navigation.
- The site should be aesthetically pleasing.
- Should contain visually pleasing graphics, appropriately used
- Usability should be taken into account - the user should be able to
easily navigate the site to find what they are looking for.
- You must read through the Web Design & Usability Basics module
- The entire site must include at least 10 content 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.
- The site must include a identifiable starting "home" page (not a splash page).
- This starting page should be called "index.html"
- This page should contain the main navigation and the main look-and-feel of the website
- This page should not be simply an image with a couple links.
- Rather than using XHTML to define placement and formatting, CSS
must be used to apply specific styles across all the pages in the site.
- It is a best practice to try to define your styles prior to creating pages
(rather than defining your styles as you go).
- Internal and Inline styles are welcome in your CSS, however try
to use external wherever possible.
- The site should include a sufficient number of graphics that are appropriately
designed.
- Of those graphics, the site must contain at least two PNG, two JPG, and two GIF (not animated) graphics (two of
each, appropriately used).
- Tables should be used, where necessary, to assist CSS in page formatting. Tables should not be your primary method of formatting / placement.
- The site must have one data table containing at least 40 cells (however you want to arrange them).
- The table must use CSS to format it.
- The table must have the summary attribute defined for accessibility.
- There must be at least 1 spanning row and 1 spanning column
- There must be at least one form in the site -- not the one you created during the exercises.
- The form must contain at least 10 form elements
- The form should submit either to an email address or to another page.
- Javascript should be used to enhance the site.
- Use Javascript to validate form information:
- Each form field should have some Javascript validation associated with it.
- Check if the email form field has an @ sign, correct ending, etc.
- Check to see if form fields are empty
- etc., etc.
- For more examples of enhancements, see W3
Schools, or Google for examples
- The site should include examples of intermediate to advanced Javascripting,
such as functions, detecting plugins etc.
- There must be at least 1 JavaScript function that is called using an
event handler
- An idea for this is form validation... mentioned above
- The site may include other media assets such as sound, Shockwave, Flash, PHP, etc. 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, raster graphics, CSS or Javascript
is not permitted.
*Note that these specifications are the minimum expected. Simply
completing the minimum requirements for this project will not yield an A for
this project. "A" projects will demonstrate things that are Above and Beyond
these minimum requirements.
*Note that editors can be used on this project. I recommend that you use Adobe Dreamweaver or Expression Web.
Above and Beyond (25% of grade)
- Additional Content Pages beyond 10 (+1 point per additional page)
- Additional scripting beyond the requirements (+2 points per unique piece of
scripting)
- Exceptional use of CSS formatting (positioning, z-index, etc)
- Other criteria can also count towards above and beyond, it depends on the
creativity of the student and the nature of the project.
|