| summary | time | deliverables | download |
|---|---|---|---|
Create a wireframe/prototype for a confectionery website—showing what you learned this term. |
10 hours |
1 HTML file, 1 CSS file, images |
- Fork this repository.
- Create an interative wireframe/prototype for a confectionery website.
The name of the company must be either:
- Beau’s Bonbons
- Coco’s Chocolatiers
- It should have real text content—that you have to write yourself.
- Greys can be used for everything if you’d like. If you choose to use colours make sure they’re nicely designed and consistent.
- Placeholder images are good—there’s a bunch of different sizes and shapes in the “images” folder.
- The website should obviously be fully responsive: working on screensizes from
320pxall the way to~2500px. - There’s also a bunch of images that you can download and use in the site as extra—but the layout is the most important thing. If the images are there but the site isn’t responsive you’ll lose grades.
- Run it through Markbot and make sure it passes all the checks.
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’ve confident with what we’ve learned and can apply everything.
header,header nav,header h1,header li,header nav amain,h2,div,section,img.img-flex,footer- A Google Font
- CSS boilerplate:
cssviewport,borderbox,textsize - Standard media query widths:
25em,38em,60em,90em - Standard text sizes & line heights:
100%/1.3,110%/1.4,120%/1.5,130%/1.5 margin,padding,position: absolute,position: relative,display: block,display: inline-block,display: flex- A
background-colororcolorhover state for the navigation links
In class, week 15, we will be doing lots of peer testing—most of the website needs to be complete by then.
Each person will be assigned a browser or validator and will be required to test everybody’s websites.
See the example website mockups in the “example-website” folder for a better idea of what’s expected.
If your website looks exactly like this you’ll receive a 0.
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 |
| Styling | Very little CSS | Basic CSS implemented | Good variety and appropriate CSS implementations | Excellent demonstration of different CSS functionality and implementations |
| 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 for grading 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.