posted Oct 13, 2009 12:58 AM by Chad Meisinger
[
updated May 19, 2010 12:56 PM by joy robinson
]
Project Due Date: Monday 5/17Description and Requirements This project will be a foray into web design. You will select a technology to use and design a website accordingly. Technology Options include: - Photoshop/In-design (or other graphics layout program)
- XHTML/CSS
- Other options exist, let me know if you have something else in mind
In either case, you will be adhering to standards-based web design. You will be creating valid, well-formed XHTML 1.0 strict web pages: consider doing your resume or curriculum vitae, and other items from your professional portfolio. For XHTML/CSS All pages should be styled via two stylesheets in CSS: one for screen (media="screen") and one for print (media="print"). For this project, you will style with advanced selectors and properties to control typography, color, and positioning for screen and print presentation.
Your pages should:
- Display appropriate (though it doesn’t have to be the same) across the following Browsers: Firefox, Chrome, Opera, and IE.
- Be uploaded to the Depaul hosting site or to another commercial site
- Validate against to section A508 accessibility rules
Your XHTML must:
- Use the XHTML 1.0 Strict DOCTYPE
- Be semantically correct using valid, structural tags (e.g., headers, paragraphs, and lists) and class/id attributes
- Be hand-written and original; do not use Dreamweaver's WYSIWYG editor or any pre-made templates
- Not use tables, except for tabular data
- Validate against the W3C Markup Validation Service
Your CSS files must:
- NOT use hacks (use conditional comments instead)
- Use only valid CSS 1, 2, and widely-supported 3 selectors, properties, and attributes
- Be linked to your XHTML pages via the <style> tag in the head area (no inline styles via the style="" attribute) using the appropriate media attribute value.
- Be hand-written and original; do not use of Dreamweaver's CSS property dialog boxes or any pre-made templates
- Validate against the W3C CSS Validation Service
Goals - Learn to choose appropriate materials to represent yourself
- Learn to hand code HTML to be both semantically and structurally correct*
- Use CSS to control both layout and design of webpages*
- Learn to develop your site in a baseline browser, to test in other browsers, and use conditional comments to address the oddities of Internet Explorer
* depending on your choice of technology Deliverables- Project proposal (due Monday)
- All your website files (XHTML, CSS, etc.) documents posted on the wiki
- Your website viewable through a publicly accessible URL (URL submitted to the Roster page)
- A self-critique memo that evaluates your project and your progress in the class to this point uploaded to your page on the wiki
- An in-progress and final presentation of your project
Presentations and Milestones Be prepared to display project twice; once while in progress on either week 6 or 7 for 5 to 10 minutes; and then the final version on 5/26 for 5 - 10 minutes or less. Below are the milestones you should achieve by the beginning of each class. Use the information below as a guide. It should also be an indicator of what you will present for your status update. (Of course, if there is some more pressing issue, go with that.) | Time | Progress | Presentations | Week 4 4/21 | Select and Gather materials, prepare and revise texts, Layout website pages
| none | Week 5 4/28
| XHTML structure complete; CSS typography | none | Week 6 5/5 | XHTML and CSS combined and tweaking | Status report | Week 7 5/12 | More tweaking: propagation of pages | Status report | Week 8 5/19 |
| none | Week 9 5/26 | Project due: Monday 5/24. Recall you can comment and make changes up through your Wed presentation | Everyone 5mins |
GradingYour grade will be largely based on your self evaluation contained in your self-critique memo in reference to your own skills and where you started in this class. Thus, everyone must present evidence of the material they have learned and how they have managed to work thought Project 1.
That said, here are some baseline issues that successful
projects should address:
- Turning in all Project Deliverables (see list above)
- Effective writing and suitable materials for building one’s
Web identity
- Validating against the W3C validators
- Meaningful, accurately descriptive XHTML structure (semantically based)
- Inclusion of development materials (scans of sketchbook,
screen shots) that lead to final project
- Contacting instructor for help with troubles encountered
(BEFORE project turn-in date)
Here is the grading rubric to assist you.
|
|