- Do not edit this file.
- Do not start this project until you have read these instructions carefully.
README.md
content/content--arvo-part.txt
content/content--boards-of-canada.txt
content/content--dawn-of-midi.txt
css/reset.css
img/
This is a pass-or-fail assignment that is designed to refresh your HTML and CSS skills. No JavaScript templating engines may be used.
Create a one-page web site using the pre-defined content from either content--arvo-part.txt
, content--boards-of-canada.txt
, or content--dawn-of-midi.txt
, all of which are in the content
folder.
Start your markup in index.html
and create other .html
as needed. Similarly, start your CSS in css/style.css
. There’s no restriction on what you may do design-wise.
- Log in to GitHub.
- Fork this repo(sitory). See this video on how to carry out this step and step
3
. - Clone your fork, using either the web site or the GitHub Desktop client.
- Checkout your personalized branch, the one with your name and GitHub user handle.
- Only submit files that are required by your project: Do not submit working files, such as
.psd
,.ai
,.indd
, or.sketch
files. - Use lowercase, combined with kebab case, to name folders and files (
do-this
ordo-this.html
); no spaces in folder or file names (not this
); no camel case (notThis
); no snake case (not_this
). - Place all your
.html
files in the root of this repo. - Place all your
.css
files in thecss
folder. - Any images you might use must go in the
img
folder. - Load
reset.css
at the top of your style sheet stack. See the file in thecss
folder. - Do not alter or remove any of the
.gitignore
files.
In the first week of class, you were supposed to install all the linters and validators for HTML, CSS, and JavaScript. The HTML and CSS linters will be needed for this project.
- Stylelint should not generate any errors. Warnings are fine.
- The W3C should not generate any errors, either. Warnings, again, are fine.
10:00 AM on Tuesday, 26 February 2019.
You will need to issue a pull request back into the original repo, the one from which your fork was created. See the Issuing Pull Requests section of this site for help on how to submit your assignment.
Note: This assignment may only be submitted via GitHub. No other form of submission will be accepted.