Learn CSS Grid by Jen Simmons

Jen Simmons:

I am starting to see a bunch of simple introductions, link-baity false-narratives, and weirdly-wrong ideas to creep into the conversation about CSS Grid. They are not as helpful. Frequently they are actually wrong. Let’s please share the best work with each other — not exclusively work done by men because it seems more respectable / more authoritative / more bro-awesome! And especially, let’s not pass around the work published by people who simply copied Rachel’s work, badly, with mistakes.

Jen compiles a spectacular list of suprisingly mostly-free resources to learn all about CSS Grid. You can also keep an eye on the Grid Layout tag, since I’m trying to write as I learn how to use it. If you’re on the fence about learning it, please don’t be! CSS Grid is an amazing tool and will soon make our lives so much easier, opening up new creative opportunities for our layouts.

Star Wars: The Clone Wars, Season 1 | Retake

Familiar but animated characters everywhere — some liked, some not. The Clone Wars series brings us the great Obi-wan Kenobi, the mediocre Anakin Skywalker, and the terrible, awful, Jar Jar Binks — the worst thing to come from George Lucas mind. On this episode of Retake, Tim and TJ will analyze the first season of Star Wars: The Clone Wars.

You know how much I love to talk about Star Wars. This time, TJ Draper and I sit down to talk about The Clone Wars, a excellent TV series from 2008 you should definitely watch.

Under the Weather

Hello Dear Reader,

This past week was a sucky one for me. I got a cold. You know how it is when you get sick. You don’t want to do anything but sleep. Well, that was basically my week.

I’m feeling better now, so you’ll see some new writing on the site. I’m playing catch up so, you’ll see some stories from last week I wasn’t able to get to.

Hope you’re having a great day, and as always, thank you for reading.

Creating a Microblog with Jekyll

This post is part of a series on Microblogging with Jekyll.

I wanted to get away from Twitter. If you don’t get why, that’s ok. It’s not the point of this post. I want to talk about creating a microblog. What’s a microblog? In essence, it’s a place where you write small tweet-like posts, except the content lives on a server you pay for. You are in control.

Jekyll makes it easy to setup a microblog. I recently created my own microblog, and made videos about it. There’s a part one and part two. I thought I’d show you how I made mine. It’s not the only way, it’s just one way. Let’s get started.

Create the Collection

First, we’ll create a collection to hold all of our microblog posts.

# _config.yml

    output: true
    permalink: /microblog/:year/:month/:slug/

This bit of code declares our new microblog collection, outputs the documents we put in it, and defines our permalink structure to use the :slug instead of the :title since our microblog posts won’t have a :title.

Create a Page for the Microblog

Now we’ll create a page to display our posts. We’ll call it microblog.html.

layout: page
title:  Microblog
permalink: /microblog/
<section class="microblog-posts">
  {% for post in site.microblog reversed %}
    <div class="microblog-post">
      {{ post.content }}
      <footer class="microblog-post__footer">
        <small><time datetime="{{ post.date | date_to_xmlschema }}"><a href="{{ post.url }}" title="Permalink to Microblog post">{{ post.date | date: "%a, %b %d, %Y at %I:%M%P" }}</time></a></small>
  {% endfor %}

Our microblog posts will now display in reverse chronological order (newest at the top), with the date displayed like this: Wed, Mar 29, 2017 at 04:25pm. Sweet.

Create Layout for Each Microblog Post

Now we’ll create a layout for our individual posts. We’ll name it microblog-post.html in the _layouts folder. As with all of these names, you can choose to call them whatever you’d like.

layout: default

<div class="microblog-post--single">
  {{ content }}
  <footer class="microblog-post__footer">
    <small><time datetime="{{ page.date | date_to_xmlschema }}"><a href="{{ page.url }}" title="Permalink to Microblog post">{{ page.date | date: "%a, %b %d, %Y at %I:%M%P" }}</time></a> by Timothy B. Smith</small>

I wanted to display each microblog post with large text and in the center of the page. The .microblog-post--single class will allow us to do just that.

Write Styles for the Posts

Now let’s create a new SCSS file for our microblog styles called microblog.scss.

// -------------------------------
// -------------------------------

.microblog-post:not(:last-of-type) {
  border-bottom: 1px solid #eee;
  padding-bottom: 1rem;
  margin-bottom: 1rem;
  p:last-of-type {
    margin: 0;
  img {
    margin: 1rem 0;
    max-width: 450px;

.microblog-post--single {
  margin: 6rem auto 0;
  max-width: 1000px;
  text-align: center;
  p {
    font-size: 2rem;
    line-height: 1.4;
    margin: 0;
  img {
    margin: 1rem auto;
    max-width: 450px;

.microblog-post__footer {
  color: lighten(#555, 20%);
  font-size: .9rem;
  padding-top: .5rem;
  a {
    color: inherit;

This will style our list of microblog posts, the date that we published them on, and the individual permalink pages of each post. If you want to see these styles in action, take a look at my microblog.

Creating the Feed

Now let’s make an RSS feed so people can subscribe to our microblog. It’s just like any other RSS feed, except each entry doesn’t have a <title>. We’ll call it microblog.xml.

<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <link rel="hub" href="https://pubsubhubbub.appspot.com"/>
  <title>Tim Smith’s Microblog</title>
  <subtitle>By Timothy B. Smith</subtitle>
  <link href="https://ttimsmith.com/microblog"/>
  <link type="application/atom+xml" rel="self" href="https://ttimsmith.com/microblog.xml"/>
  <updated>{{ site.time | date_to_xmlschema }}</updated>
  <rights>Copyright © 2008–{{ site.time | date: "%Y" }} Timothy B. Smith</rights>
    <name>Timothy B. Smith</name>
  {% for post in site.microblog reversed %}

    <id>https://ttimsmith.com{{ post.id }}</id>
    <link type="text/html" rel="alternate" href="http://ttimsmith.com{{ post.url }}"/>
    <published>{{ post.date | date_to_xmlschema }}</published>
    <updated>{{ post.date | date_to_xmlschema }}</updated>
      <name>Timothy B. Smith</name>
    <content type="html">
        {{ post.content }}
  {% endfor %}

Things I Haven’t Figured Out Yet

Cross-Posting Efficiently

The way posts appear on other social media is inconsistent. If I use an inline link, it won’t appear elsewhere. Also, since I’m using FeedPress to do the cross-posting, it’s not immediate.

Automate the Creation of Files

I want to easily create a new post with the right file name format, and have it auto-increase the number. For example, I could automatically create a post called 2017-02-16-01.md with the next one being 2017-02-16-02.md and so one. This is simple to do on my mac, but how would you do this on iOS? Problems like this are what come about with database-less systems.

Publishing from iOS

This is really tough. Jekyll has no API that I can hook into to publish posts and upload images. I almost feel that this completely disqualifies Jekyll as a viable solution for the microblog, but I’m giving it a shot for now. I may have to… use… WordPress. 😱


This is one of the ways to create a basic microblog. I’m sure there are things I haven’t thought of yet, which I’ll have to address down the road. Are you microblogging? What are you using for yours? Have you solved some of the problems I haven’t fixed yet? I’d love to hear all about it! Send an email to tim@theboldreport.net.

CSS Tip: Use :not to Save Time and Lines of Code

I saw this tweet from Matt Griffin:

Finally started making my life easier by using :not(:last-of-type) rather than overriding with a separate :last-of-type rule. Huzzah!

Mind. Blown.

mind blown

Why didn’t I think of this earlier? This small thing saves so much time and lines of code. Let me explain. Let’s say you’re styling a list of posts.

<!-- This is what your html would look like -->
<ul class="posts">
  <li class="post">
    <a href="/link-to-post/" title="Permalink to post">
      <h2>Post Title</h2>
      <small>Thurs, Feb 16, 2017<small>

This is how I foolishly used to style this. Foolishly I tell you!

.posts {
  list-style: none;
  margin: 0;
  padding: 0;

.post {
  border-bottom: 1px solid #eee;
  margin-bottom: .5rem;
  padding-bottom: .5rem;
  &:last-child {
    border-bottom: 0;
    margin-bottom: 0;
    padding-bottom: 0;

Lots of code just to space each post evenly, except for the last one. This is what :not was made for!

.post:not(:last-of-type) {
  border-bottom: 1px solid #eee;
  margin-bottom: .5rem;
  padding-bottom: .5rem;

We’ve eliminated five lines of code here. Just imagine how much you’d save by using this throughout your code base! I made a CodePen for you to see this in action.

Hope this helps! If you have questions, send me an email to tim@theboldreport.net.

It Isn’t Millennials Who Are Entitled

Rachel Hosie writes on some thoughts from author and motivational speaker Brian Sinek:

And another problem is that we’ve been brought up to focus on having a healthy work/life balance - “the message is correct, but it seems to have been exaggerated and misinterpreted,” Sinek explains.

He believes the pendulum has swung too far the other way - while older generations may have felt chained to their desks, many millennials leave work on the dot of 5pm every day and refuse to answer work calls or emails over the weekend. This attitude is one of the reasons we have a reputation for entitlement.

I’ll be honest, I’m writing about this one just to tell you how utterly and fantastically stupid this is. If as my employer, you expect me to work outside of normal business hours on a consistent basis, the one who is entitled is you.

Employers can’t get away with abuse that used to be considered “part of the job” and the problem is with millennials? As is true with any person of any generation, respecting employees and their time will certainly result in a dedicated and hard-working workforce.

Wait, You Don’t Control Your Calendar? | Signal v. Noise

Jason Fried on controlling your calendar:

As many people know — and as I didn’t — in most companies people don’t really control their own time. Everyone can see everyone else’s calendar, and people can pick away at each other’s time.

“Ah, an opening! Let me grab it before someone else does!”

“There’s a gap… Fill it!”

“Someone blocked out 4 hours to themselves? Oh good! That means they’re available and not stuck in meetings… I can hit them up then.”

Almost every place that I’ve worked for had no respect for my time. If you get a calendar invite, you better damn well accept that invite. Anything short of that felt like insubordination. And here’s the thing: lots of managers theoretically understand that interrupting someone’s day with meetings makes them unproductive.

The problem comes in practice. “Meetings helps us all get on the same page.” Yea, well we could do that in Slack or Basecamp. Next excuse. “There’s nothing like face-to-face time to talk things out.” Uhhh… yea there is. Hours of productive time where I can actually do the work you pay me for.

But hey! What do I care? I don’t work full-time anymore. Thankfully, this type of crap doesn’t stress me out these days.

Code Smells in CSS Revisited by Harry Roberts

Harry Roberts:

Way back in 2012, I wrote a post about potential CSS anti-patterns called Code Smells in CSS. Looking back on that piece, I still agree with all of it even four years later, but I do have some new things to add to the list. Again, these aren’t necessarily always bad things, hence referring to them as code smells: they might be perfectly acceptable in your use case, but they still smell kinda funny.

Lots to learn here. I feel horrible saying this, but I’m guilty. I’m guilty of at least two of these. I know, embarrassing. But hey! Can’t let it get me down, we’re all trying to improve.

A real easy one to get better with is minimizing the amount of shorthand syntax you use. Harry focuses on background, but margin and padding should be avoided too unless you’re doing it intentionally.

// Don't do this!
.class-name {
  background: #fff;
  margin: 0 0 10px;
  padding: 0 0 0 5px;

// Do this!
.class-name {
  background-color: #fff;
  margin-bottom: 10px;
  padding: 5px 10px; // You're doing something specific with this one.

Something small like this can save so much time. Really though, all of Harry’s tips will save you, your co-workers, or whoever else maintains the code you write, a lot of time.

CSS Grid Layout Terminology, Explained by Ire Aderinokun

Ire Aderinokun:

CSS Grid Layout introduces a lot of new concepts; there are 17 new properties to learn, and many more new terms to understand. This can make getting started with CSS Grid Layout difficult, as new terms reference other terms and you can get into a spiral of confusion. So, here are the basic concepts and terminology of CSS Grid Layout, explained.

Yep, the learning curve might be steep to learn this, but it’s important to do it. As Ire goes through the different properties, it’s easy to see how amazing CSS Grid is, and how much it will simplify our life. Don’t wait till “it’s more widely supported.” Learn it now, and the investment will be worth it. CSS Grid is coming.

This next part confused me, but after thinking about it more, it made sense.

.outlined {
  grid-area: outlined;
  border: 2px solid purple;

.grid-container {
  display: grid;
  grid-template-areas: "outlined outlined ."
                       "outlined outlined ." 
                       ". . ."; // The last one is empty because it's not part of the outlined grid area.
  grid-template-columns: 100px 100px 100px;
  grid-template-rows: 100px 100px 100px;

Each outlined corresponds to the first and second column, and the first and second row thereby creating a 200px×200px square. I’ve created a CodePen if you want to play around with it.

See the Pen ggBYzE by Tim Smith (@timothybsmith) on CodePen.

Version 5.1.0

Notes on the latest release

I’ve been doing some work on the site, and wanted to loop you in.

Bug Fixes

  • Update protocol on gravatar images (#168)
    Gravatar images were using http instead of https and that weakens the security of the site.
  • Update Bold Report avatar image in head (#171)
    There’s an image that the site passes to Twitter and Facebook when you share something, I’d completely forgotten to update this image with the new orange color.

Development Fixes

  • Switch to Google Analytics tracking code (#170)
    Previously, I was using a service called Segment to serve the analytics I wanted to use. I didn’t get much value from using what is essentially a middleman. I was using Google Analytics with Segment, and now I’m just using Google Analytics straight from Google.
  • Add jTag templates (#172) Since been removed.
    I was really excited to find Brett Terpstra’s jTag and thought it would be the ideal solution for me. I played around with it, and unfortunately I couldn’t get it to work. I’ve filled an issue, and hope Brett is able to look into it.

Site Enhancements

  • Redesign the Topics Page (#169)
    When I worked on version five, I didn’t really pay much attention to the topics page. I decided to revisit this page, and put it in the main navigation. I think topics will help you find more about topics you’re interested in. Working on this page reminded me how much content there is on here about a wide variety of topics.
  • Typogrify (#173)
    I found this great Jekyll plugin called jekyll-typogrify which gives you access to some great filters. One of them allows me to style all caps differently. For example, I can now write CSS, HTML, RSS, etc. without ruining the flow of the line. But that’s only one of the awesome filters it comes with. If you use Jekyll I highly recommend you check it out.

  • Add share buttons (#174)
    For a long time I’ve decided to refrain from having sharing buttons at the bottom of posts. I foolishly felt I was standing for some “moral highground.” I realized I didn’t understand what that so-called highground even meant. Plus, I was reading something on someone’s site the other day, and was frustrated without an easy way to share. So I’ve added sharing buttons. Share away!

If you normally, read via your RSS reader, I encourage you to visit the site today. Send me an email, and tell me what you think.