- Do not start this project until you have read these instructions carefully.
- Read these instructions repeatedly until you understand, then begin your project. If something is not clear, ask.
- 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.
This assignment is designed to initiate you into the world of creating web pages using advanced concepts in CSS, employing what you’ve learned thus far and adding your own design sense.
Create and style a one-page web site using the pre-defined content from either of the text files in the content
folder.
Once you’ve settled on a text file, populate index.html
with that file’s content matched with your careful and semantic choice of HTML syntax. (Note: You may not modify the content in any of the .txt
files.)
With the content marked up properly, add styling to the page using CSS. There’s no restriction on what you may do design-wise.
README.md
content/content--arvo-part.txt
content/content--boards-of-canada.txt
content/content--dawn-of-midi.txt
content/content--gy!be.txt
content/content--public-enemy.txt
content/content--ramones.txt
css/reset.css
css/style.css
index.html
img/
- 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 markup in
index.html
. - Place all your styles in
style.css
. - Do not alter or remove the
reset.css
file in thecss
folder. - Do not alter or remove any of the
.gitignore
files. - The only files you may add are images, which, if included, must go in the
img
folder. Ensure each image is under 1MB or smaller. - Leave the inclusion of
reset.css
in thehead
ofindex.html
alone.
Make sure Atom continually reports No errors were found!
in the lower left hand corner as you work. Solve validation issues as you work — don’t let them accumulate. That’s called technical debt. Avoid it!
Item | Points |
---|---|
HTML is W3C-compliant | 25 |
CSS is W3C-compliant | 25 |
Design shows attempt at producing quality work | 25 |
Rules outlined above followed correctly | 25 |
Wednesday, 29 April 2020, at 10:00 PM.
You will need to issue a pull request back into the original repo, the one from which your fork was created for this project. 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.