I think it's very nice to have an individual file (.scss) that is for the vast majority of typography on the site. Normalize has quite a bit of typography related stuff in it already, so let's remove that and move it to our own typography file. The idea is to stay true to the way Normalize works best, in that we don't set things just to reset them later. Then we tweak a few things to get us on the way.


  1. User Avatar
    Joi Glifberg
    Permalink to comment#

    Hey Chris, seems like this last two screencasts has become in the wrong order, just for your info :)

    • User Avatar
      Huw Rowlands
      Permalink to comment#

      Yesh, same for me Chris?! Number #23 is appearing before #22.
      Although when on #22, clicking the Next Video link takes me to #23.

      Love the vids tho!!

  2. User Avatar
    Gray Ghost Visuals
    Permalink to comment#

    Oh no you didn’t! Totally made me cry when you talked about my ems like that. WAT EVAH!

  3. User Avatar
    Josh Fry
    Permalink to comment#

    Ems are like pre-processors, once you use them you can’t go back and they make life a little better too.

  4. User Avatar
    Devin Dombrowski
    Permalink to comment#

    “… I just want to have a clean slate to start with.”

    See! You too!

    I want to like normalize.css but this is the very reason that I have a mental block with it. I also want to start with a clean slate. Yes it’s true I will set margins on my headers, but I don’t want to have to start that process by “fixing” margins that have already been set. Normalize should NORMALIZE all the margins to zero. Having all the header margins set to the authors choice is not normal.

    Sorry Nicolas. Great respect for you.

    • User Avatar
      Chris Coyier
      Permalink to comment#

      Just try thinking, instead of “normalizing” to zero, “normalize” to whatever margin you want in your actual design.

    • User Avatar
      Devin Dombrowski
      Permalink to comment#

      I’ll try

  5. User Avatar
    Ricardo Diaz
    Permalink to comment#

    The dfn element comment had me laughing. I didn’t know what it meant either then I looked it up after the video. I have to start using that more in my blog.

  6. User Avatar
    Jeff Stone
    Permalink to comment#

    I’m lovin’ this series (and the site of course). I’m a huge CC Fan! Just thought I’d point out that video 23 and 22 are out of order. The content for 23 should come before the content of 22. :)

    Thanks again for such an awesome Site.

Leave a Comment

Posting Code!

You may write comments in Markdown. This makes code easy to post, as you can write inline code like `<div>this</div>` or multiline blocks of code in triple backtick fences (```) with double new lines before and after.

Code of Conduct

Absolutely anyone is welcome to submit a comment here. But not all comments will be posted. Think of it like writing a letter to the editor. All submitted comments will be read, but not all published. Published comments will be on-topic, helpful, and further the discussion or debate.

Want to tell us something privately?

Feel free to use our contact form. That's a great place to let us know about typos or anything off-topic.