News Outline Schedule Tutorials Project Tools Links

Rules to follow for your Project

  1. File Creation Rules:
    1. Your first/main page MUST be named index.html. You may not name your main file index.htm . Similarly, all html files should have the file name extension '.html'. Files with the extension '.htm' will be considered an error, and will result in lost marks.
    2. Your project will consist of six (6) pages - no more, no less. This means your directory will contain, six (6) HTML files. Additional HTML files in your directory at the time of project collection will result in one mark deduction per file, regardless of whether or not those files are actually part of your project. Do not store extra files in your project directory! Note that this includes storing html files in sub-directories of your directory, even if they are not "linked" by the rest of your site - such files will still be counted, and XHTML and CSS errors in them will still result in mark deductions! Similarly, extra CSS files left in your directory will still be marked and errors in them will count towards your CSS mark.
    3. Due to the small size of this project, you may not use frames for your web site. Use of frames in your web site will count as one error in the XHTML section of your project marking. Any errors present due to or related to frames used in the project will be deducted for in addition to this, including failure to use a cookie in all HTML files, and excess numbers of files.
    4. You must place your files in your main directory! Do not create sub-directories to place your HTML files in, they should all be in your main directory for this project - it is not large enough to justify using sub-directories for your HTML files.
    5. All images and personal files must be in your 60-270 directory. If it's yours, it should be in your directory. No images or stylesheet files may be linked in from outside sources.
    6. The purpose of the project is to learn client side scripting (Javascript) techniques - do not use server side scripts! Any dynamic content on your site should be provided through client side scripting.
    7. All file names MUST be in lower case letters. Similarly, you should not include spaces or punctuation marks in your file names - no '&', '?', '!', '@', ',' or any other non-letter/number. These characters interfere with the web server, and will be penalized as XHTML errors.
  2. Content Rules:
    1. The University of Windsor's policies on plagiarism, and on the Unacceptable Use of Computing Resources (as detailed on the class website, and in the undergraduate calendar) will be strictly followed for the project, midterms, and the final examination. Plagiarism includes copying text, content, or programming code from other web sites, books, or brochures, and claiming it as your own. You are required to develop your own content, and each sentence must be in your own wording. Plagiarism is considered a very serious offense, and will result in a failing mark on whatever work the student plagiarized. The content of your web site must be in your own words.
    2. You may use material from your own project from 60-205 as a base for your project for this course. However, if you do, please bear in mind that you must modify it extensively to fulfill the requirements for this project. Especially as the requirements for the two projects are very different from each other.
    3. Every page must have a title in the browser window title bar.
    4. A complete page is a page with at least 7 to 8 lines of content "text" and at least one picture and a back link. Spelling, grammar and coherency count! Text must be normal size full screen 7 to 8 lines in order to qualify (7 big letters on 7 lines doesn't work). A page lacking sufficient content will lose one mark (up to a maximum of 5 marks).
    5. Minimize the use of animated gifs. One or two maximum in one browser frame at a time.
    6. Any type of advertising, pornography, or nudity whatsoever is unacceptable unless agreed upon by the Professor.
    7. Every page has an image and a back link. Marks will be deducted each time an image or a back link is missing. Pay attention to these deductions, as they can quickly add up!
    8. Proof read your work! After uploading the files to the web server, take your disk out of the computer, and then go to each page in your site, and click on each link to make absolutely sure that they work correctly!
  3. Coding Rules:
    1. The use of the <font> tag in your project is forbidden. One of the major sections of the project is the use of stylesheets to set colours, fonts, and placement, and these should be used to set any and all colours in your site. Also note that you should not be using the background, bgcolor, text, link, alink, and vlink attributes on the body tag, or any other tags, as this should also be done through stylesheets. Each use of one of these forbidden items will count as one error in the CSS section of your project's marks.
    2. Your site must be Browser independent. It must work equally well under Google Chrome, Firefox 9, or Internet Explorer 9. This means that your site should not present JavaScript errors, regardless of the web browser used to view it. Selecting one browser and programming for it only is not acceptable. When marking projects, if there is a pop-up or other notice which instructs the viewer to use a specific browser, a three (3) mark deduction will be applied to your javascript marks, regardless of whether the site works in all browsers or not.
    3. Displaying popups such as window.alert() and window.prompt() is forbidden in your project, and will result in penalization in the Usability section of the marking.
    4. If Java, flash, or other non-W3C-standard web extensions are used, you must ensure that they work perfectly, and in a way that does not violate the W3C Content Accessibility Guidelines, or marks will be deducted for those problems. Note that Flash and Java can not be used to fulfill project requirements, so a site which relies too heavily on them will not receive as good a mark as it could have otherwise.
    5. NO FLASHING/BLINKING ANYTHING! 2 marks will be deducted per use of blink tags or stylesheet attributes! It should also be noted that the blink tag is not part of the XHTML standard.
    6. When using images on your page, the use of height and width parameters to re-size your image is FORBIDDEN! Only re-sizing the image to thumbnail size using Paint Shop Pro or another graphics editor is acceptable.
    7. A page of two and a half screens or longer MUST have properly made internal anchors and links.
  4. Marking Conditions:
    1. Pages will be marked at 1024x768 resolution at full screen, with the default font size set to 16 point. This setting is available on most of the computers in the Computer Center, so it should be easy to gain access to a computer to test your site on at those settings. Note that this does not mean that you must set your own fonts to 16 point, only that when we are marking projects, it will be the default on the browsers used.
    2. The HTML Coding section of your project marking will be done through the w3c XHTML validator - please remember to verify each page individually, as the validator only checks one HTML file at a time.
    3. Your project will also be expected to have Level "A" conformance to the w3c's Web Content Accessibility Guidelines version 2.0, which are outlined at http://www.w3.org/TR/WCAG20/.
    4. Tables and images that scroll off the screen to the right will be penalized.
    5. Projects will be looked at in Google Chrome, Firefox 9, and Internet Explorer 9.
  5. Important Reminders:
    1. All XHTML tags and attribute names MUST be in lower case letters. This is the most common, and hardest to spot error when typing in XHTML files - if the validator tells you a tag or attribute does not exist, and you're sure it does, check to make sure you didn't accidentally capitalize something.
    2. Watch the order of tags while closing, and make sure that all tags which are opened are also closed. Marking of XHTML coding will be done with the XHTML validator at http://validator.w3.org in XHTML 1.0 Transitional mode. If your site uses frames, your frameset page should validate with the XHTML 1.0 Frameset mode instead.
    3. Make sure you aren't missing quote marks around attribute values (anywhere you use something="something")
    4. As a page is a full body it can not be dismembered. It will always have a HEAD and a BODY in that order. Also, you should have only ONE body per page. The only exception to this is with framed pages, where the HTML file will have a FRAMESET instead of a BODY, but you also should not be using frames in your project.
    5. Beware of Microsoft Smart-Quotes! They are added into text files created with MS-Word, and are NOT part of any valid character set used on the internet - as such they will create errors in the validator, and will cost you marks! See the main project page for instructions on how to remove smart-quotes from your file if you have accidentally added them.