Throughout the rest of the term we’ll be working on the design of a complete independent website. The subject matter independent project website is completely your choice.
humans.txt file. (See an example humans.txt file).320px all the way to ~2500px.This website is to prove that you—by yourself—can do everything we covered in class. Look back over all the assignments from the term, determine what kernel of knowledge they were trying to teach you, and see if you can implement it in this website.
There should be a significant example of everything we’ve learned this term in this website. Leave the impression that you’re confident with what we’ve learned and can apply everything.
header, header nav, header nav li, header nav amain, h2, div, img, footer, section or articlemain.csscolor or background-color hover state on the navigation<title> & <h1> for everything HTML pageCSS requirements are really open—just make sure the CSS is valid & indented properly.
250kB and maximum dimensions of 2500pxfavicon.ico & favicon-196.pngIn class, week 14, we will be doing lots of peer testing—most of the website needs to be complete by then.
Each person will be assigned a tool and will be required to test everybody’s websites.
Below is the rubric of expectations for this project. You will be assigned a letter grade based on your standing within the rubric.
| 0 points | 1 points | 2 points | 3 points | |
|---|---|---|---|---|
| Knowledge | Poor understanding of material | Partial understanding of material | Demonstrates full understanding of material | Demonstrates excellent understanding of material |
| Responsiveness | Not responsive | Works on some screens | Responsive but with lots of awkwardness | Looks great on all screen sizes |
| Semantics | Very little HTML | Basic HTML tags chosen | Good variety and appropriate HTML tags chosen | Excellent demonstration of HTML tags and correct use |
| Design | Very little design | Basic design implemented | Cohesive design implementation | Excellent design implementation |
| Accessibility | Not accessibile | Some accessibility but doesn’t work well with certain situations | Some minor accessibility problems | Works really well under all the standard accessibility tests |
| Performance | Doesn’t come close to passing the performance budget requirements | One or two performance budget requirements are not met | Just passes the performance budget requirements | Surpasses the performance budget requirements |
| Home page | Missing or incomplete | Started but severely lacking | Complete but with poor text or bad responsiveness—not quite perfect | Complete, amazing content, responsive, designed well—amazing |
| Page 2 | Missing or incomplete | Started but severely lacking | Complete but with poor text or bad responsiveness—not quite perfect | Complete, amazing content, responsive, good use of tables—fantastic |
| Page 3 | Missing or incomplete | Started but severely lacking | Complete but with poor text or bad responsiveness—not quite perfect | Complete, amazing content, responsive, logical—super |
| Code quality | Missing or incomplete | Poorly done, rushed, no semantics, bad accessibility | Decent: semantics, indentation & accessibility | Perfect: semantics, indentation & accessibility |
| Git & commits | Bad commit messages | Decent messages | Good messages | Excellent and descriptive commit messages |
| Markbot | Not handed in with Markbot | — | — | Handed in with Markbot |
Drop this folder into your Markbot application. Make sure to fix all the errors. And submit for grades using Markbot.
When you submit to Progressinator, you’ll see a grey checkmark that shows the project was handed in. You’ll still have to write a Request for Grade and the teacher will still be grading it personally.