There are seven different main areas of the site beyond the homepage. So, I hired seven different illustrators to do designs. This is the first one we are going to dig into and get implemented into the site. It's the the gallery section of the site and it's done by Erica Sirotich.

We jigger around the HTML and CSS to make room for the header up top, which we do essentially with padding.

We do some resizing with Photoshop to get the illustration just the size we want it. Pretty darn big, for now, but we'll likely do some smarter stuff in the future for loading appropriately sized header graphics for the screen size at hand.

One little feel-good trick we employ is to add a bunch of bottom margin to the page-wrap, so the end of the page has some blank texture at the bottom which gives a finality to the design (at least for now, until we deal with the footer).

We finish up with the Gallery header nicely in place, but we have a little work to do on it yet adding in the little blue people illustrations that Erica did as part of this illustration.


  1. Wesley
    Permalink to comment#

    Hi Chris. Loving the screencast and redesign.

    I came across this method for hiding text without using text indent or minus top/left values.

    I think I remember reading that if you use the text indent or minus values the browsers still renders a box to the required size (-9999) just of the screen view but the below code dosen’t.

    font: 0/0 a;<br/>
    text-shadow: none;<br/>
    color: transparent;

  2. CWSpear
    Permalink to comment#

    Compass has a cool feature that you can use image-url('image-name-with-no-path.png') instead of basic url() for images so if the path changes, you only have to change it in the config.rb.

    (They have one for other stuff too, including fonts (i.e. font-url(), but that path doesn’t seem to be defined be default in config.rb, but you can add it.)

Leave a Comment

Posting Code

We highly encourage you to post problematic HTML/CSS/JavaScript over on CodePen and include the link in your post. It's much easier to see, understand, and help with when you do that.

Markdown is supported, so you can write inline code like `<div>this</div>` or multiline blocks of code in triple backtick fences like this:

  function example() {
    element.innerHTML = "<div>code</div>";

We have a pretty good* newsletter.