The Lorem Ipsum Blog Page

Practice with HTML5, CSS3 and responsive design while building a blog page.

Scroll down...




This first assignment is meant to get you to explore a few of the new tools you've learned over the past few lessons. This assignment is intended to be fairly straightforward and to build up muscle memory as much as anything else. The end-of-unit projects will be much more involved.

For this assignment, you'll build a very basic "blog" page but one which utilizes the HTML5 semantic elements and some new CSS3 features. The page will have two different form factors -- one for wide screens, and another for narrow screens. This is practice is called responsive design.

Large Screens

HTML5 Blog Mockup Wide Click for a larger version

Smaller Screens

HTML5 Blog Mockup Narrow Click for a larger version

You'll get to practice with the Git workflows that we'll use throughout the course as well.

Getting Started

  1. Fork and clone the Project Repo on Github. See How to fork if you need a refresher.
  2. Add your name to the README file, commit the change, and push to your fork.
  3. Set up a basic index.html file for HTML
  4. Create a styles.css file for styles
  5. Be sure to link to the stylesheet in the <head> of your HTML document
  6. On to the main event!

Quick tip: If you have an ad blocker installed, it may not show the ad unit you're trying to create (especially if it has a suspicious class name like ad-content)! You can get around this by using an incognito window (which has no extensions running) or just disabling the blocker for your page.

Your Task

Your job is to produce the mockups included above. You'll start by building the basic structure of the wide page and then implementing the changes necessary to make the page degrade gracefully to a narrower form factor.

Don't worry about producing perfectly beautiful code the first run through. You will refactor it afterward.

Wide Version

  1. Start by building out the HTML structure of the page. Use the HTML5 semantic tags where possible. Fill in the background colors of the sections as in the mockup (roughly) so you can keep track of where everything is. It'll be easiest to just think of the wide version for now.
  2. Fill in the text of the elements. Tip: Type lorem and then hit Tab in Sublime text to generate a Lorem Ipsum paragraph
  3. Now start applying styles so the elements are positioned on the page properly.
    1. Assume that the maximum container width in the mockup is 990px (though obviously the navbar exceeds it).
    2. Assume the navbar is fixed to the top of the screen (e.g. always there no matter how far you scroll down).
    3. Assume that the ad box height is fixed at some value (this is really just to give you some experience vertically centering something).
    4. Note that the 3 articles will be of differing lengths (heights), but there will always be 3 of them.
    5. Don't forget a CSS reset
  4. Apply any basic element stylings (and the rounded corners).
  5. Commit to Github (frequently).

Narrow Version

  1. Set up media queries so the page operates like the one in the second mockup.
  2. Play with it to make sure the element layouts behave as expected when you cross the breakpoint.
  3. Commit to Github.
  4. Finally, refactor and clean up redundancies in your styles or markup. Try to conform to the best practices we covered earlier. Now is when you aim for good-looking code.

Finishing Up

  1. When you're finished with all tasks, push your changes up to your fork (aka $ git push origin master).
  2. To submit your assignment, create a pull request from your fork to the main upstream repository. See below if you need a refresher on how it's done.



The solution will be available here on Github once you've submitted your pull request.

Pull Request Refresher

Here's a quick refresher of how to submit a pull request. You'll do this about 100 times during the course so it'll very quickly become second nature.

  1. Go to your fork and click the green "Pull Request" button:

    Beginning the pull request from your fork

  2. Examine the files that will be submitted. If you don't see this screen, make sure you were actually on your fork in step 1:

    Examining the files on your fork that will be pull requested

  3. Title, add any clarifying comments, and submit your pull request:

    Titling, Commenting and Submitting your Pull Request

Pull request 300 Octocat 300

Sign up to track your progress for free

There are ( ) additional resources for this lesson. Check them out!

There are no additional resources for this lesson just yet!

Sorry, comments aren't active just yet!

Next Lesson: Project Walkthrough: Building Facebook