Skip to content
This repository was archived by the owner on Oct 3, 2024. It is now read-only.

Assignment #9: index.html

Emily Stewart edited this page Oct 31, 2015 · 6 revisions

Assignment 9: index.html

Finally, time to start writing basic HTML. Don't worry that your page is unstyled. We want to make sure we get the structure nailed down before we introduce CSS to the project. This assignment will also integrate Git. See this overview to learn more.


Step 1: Create one repository for your group

Within the J4502 organization, create a single repository for your group.

  • Repository name = Project name
  • Public
  • Initialize the repo with a README

Step 2: Create a new branch

Create a new branch off of master. Name it develop.

Note: the master branch should always be in a stable state. Branching helps ensure this.


Step 3: Create a team member section in your project README

Within this section, each group member will add their name to the README.


Step 4: Merge into master

Once everyone has added their name, committed and pushed their changes to develop, one person will pull those changes and merge them into master.


Step 5: Clone the repo to a folder on your computer

I usually make a Sites folder. If using the Github App, it's the "+" symbol and then Clone.


Step 6: Switch back to the develop branch & write the scaffolding

Now, create a separate file (index.html) where you'll add in the global elements that serve as the structure for all of your pages. For instance:

  • <head>
  • <body>
  • <title>
  • <footer>

You should be pushing to Github frequently (e.g., every major "save point"). Overcommitting is much, much better than sporadic commits. Remember: this also serves as a way to see who is contributing and who is not pulling their weight.


Step 7: Break down content and chunk it into code

Let the content guide your decisions on structure. Which parts will be a package? Is there a hero section? CTA? Illustration? You should have all content for the homepage (or primary view) in the source.


Step 8: Validate your markup

Using the W3C Validator, check to make sure your code validates. You will be graded on your ability to write semantic code.


Step 9: Ping Rob & Emily on Slack when ready to review

When you've pushed all your validated code (should be doing this from the get-go), let us know and we'll review it.


Due date: Sunday, November 1, 2015 by 11:59 p.m. (Yes, you'll get an extra hour with Daylight Savings).

Points available: 40

Clone this wiki locally