| summary | time | deliverables | Demo |
|---|---|---|---|
This repository contains the full code of the summary model of the personal portfolio, this code is subject to the intellectual property license so its reproduction is prohibited |
589 hours |
HTML file, 12 CSS files, images, js file, ejs file, php file, rubi file, md file |
Host and status page: →
header,header nav,header h1,header li,header nav amain,h2,div,section,img,footermodules.css,grid.css,type.css,main.cssAnd many of the expected classes- A Google Font
- At least 1
background-image - A
background-colororcolorhover state for the navigation links - A
<form>that submits to Formspree - All images are compressed & smushed
- Passes the standard performance budget: 1000ms, < 15 assets, < 800 kB
- Passes all our accessibility requirements
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 |
| Modularity | Modular CSS not used | Some basic modular CSS used | Lots of modular CSS | Modular CSS used to its full potential |
| Forms | No form | Non-functioning form | Functional but ugly form | Good looking and functional form |
| Performance | Doesn’t pass the performance budget | — | Passes the performance budget | Exceeds the expectations of the performance budget |
| Accessibility | Very poor & no accessibility | Simple accessibility details implemented | Good accessibility but clearly not optimized | Excellent accessibility with clear VoiceOver testing & improvements |
| Text content | Fake content only | Some real content, some fake | All real content but with lots of errors | Real content, well written, no grammar or spelling errors |
| 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 to Canvas using Markbot.
When you submit, Markbot will give you 1 or F—that’s just so you know that it was handed in on Canvas. You’ll still have to write a Request for Grade and the teacher will still be grading it personally.