Homework 1
Single Personal Page

As a review and way of launching you back into web development, you are to build a single-page, static-site, that briefly describes you, for your first homework assignment.

This site should;

• be visually appealing, aesthetically
• utilize Mobile-First, Response Web Design (RWD) principles
  • If you need a refresher on Responsive Web Design, look at;
    • the google course
    • or last semesters 341 page
  • Utilize at least two separate break points
• use inter-page linking
• include a “hero image”
  • w3schools hero image info

Optionally, you should also utilize parallax scrolling.

• Parallax scrolling info at w3schools

You should also have at least three sections. At a minimum, this should include;

1. The “hero-image”
2. An information section about yourself
3. At least one additional section that describes something else of interest to you
   • The example site describes this course.

With respect to the file structure, the site should;

• Exist as the top-level of your new repository gh-pages site.
  • i.e. https://YOUR-USERNAME.github.io/YOUR-REPO-NAME/
• In the top-level of your repo directory, you should place the ‘index.html’ document.
• All other resources for this site, along with the weekly ‘readme.md’ response should be located in directory labeled HW-1, which is also in the root level of the main repo directory.
  • This means your directory structure might look something like;

/
├── HW-1
│   ├── imgs
│   │   ├── hero-image-2.jpg
│   │   └── hero-image.jpg
│   ├── readme.md
│   └── style.css
├── README.md
└── index.html

Example

The following are links to a live example of this site and the associated repository.

Note: You are welcome to look at code, snoop around, and see how I solved these problems. You should also examine the repository directory structure to understand what I am asking for “directory structure” - wise.

Embedded iframe Version

Weekly Readme Response

Every homework assignment, you will write a readme document, describing your experience and response to the homework. This will be a standard part of all HW assignments. This can be considered as a technical report, in which you post documentation about how it went and what you did. Ideally something visual, some written thoughts, specifics of what you did, and code. If you are struggling with your problem and can’t get things to work, you should feel free to put your energy into writing about what didn’t work (and vent any frustrations!). This should be considered as a technical report. As such, these reports should be well formed, written with proper grammar/style, and edited. You will be marked down for poor writing.

Your response should be considerably longer than the example readme.md from the above links.

Markdown Assistance

If you do not know, or are wanting a refresher with Markdown please utilize the following resources.

• Markdown info from 120
• GitHub Markdown Cheatsheet

Submission

To submit your homework, copy and paste links to your;

1. active site
   • i.e. https://michaelmusick.github.io/441/
2. Homework repo directory
   • i.e. https://github.com/michaelmusick/441/tree/HW-1/

These should be placed in a new forum post in the “Week 1 HW Forum” on Moodle.