Class Site

Your class site will serve as documentation for all of your work this semester. This final compilation will be due a week after the final class, Thursday May 19 @ 5:00pm EST.

Organize your class site so that it includes a link to each project and exercise. (Some exercises required adding features directly onto your class site, so you do not need a separate link for those. Other exercises may have built upon each other; please link to the final result of your experimentations as well as any intermediary versions you may have.) If there is any other technical experimentation and draft code, those should live in its own directly.

You might also include alternate drafts / planning documents that you experimented before developing the final version of your website. (Links to Figma are great, but please do not link to any working documents such as .psd or .ai files as they can be too heavy to manage on Github.)

As you organize / reorganize your Github repository, make sure to double check that all links, including assets such as fonts and images, are properly linked. Make sure your images are optimized for web. There should be no broken links. You should verify everything on your live site. Any improvements made to your websites since the critiques will also be considered in the evaluation.

Your Github Repository structure may look something like this:

myname-webtype
	├ index.html
	├ style.css
	├ script.js
	│
	└ projects
	│	│
	│	└ project-1
	│	│	├ index.html
	│	│	└ style.css
	│	│
	│	└ project-2
	│	│	└ variablefont.glyphs
	│	│
	│	└ project-3
	│	│	├ index.html
	│	│	├ font.woff2
	│	│	├ style.css
	│	│	└ script.js
	│	│	
	│	└ project-4
	│	│	├ index.html
	│	│	├ style.css
	│	│	├ script.js
	│	│	└ images
	│	│		├ img1.png
	│	│		├ img2.png	
	│	|		...
	└ exercises
	│	│
	│	└ layouts
	│	│	├ index.html
	│	│	└ style.css
	│	│
	│	└ modular-type
	│	│	├ index.html
	│	│	...
	│	│
	│	└ apis
	│	│	├ index.html
	│	│	...
	...
	└ archive
	│	├ test1.html
...