added support for drafts

Author: flyingfisch

_layouts/category_index.html

@@ -5,7 +5,8 @@
 <main class="post-list">
     <h1>Category: {{ page.category }}</h1>
 
-    {% for post in site.categories[page.category] %}
+    {% assign published_posts = site.categories[page.category] | where: "published", "true" %}
+    {% for post in published_posts %}
     <article class="post">
         <div class="post-info">
             {% if post.author %}<strong>Author:</strong> {{ post.author }}<br>{% endif %}

_posts/2015-04-25-welcome.md

@@ -1,22 +1,21 @@
 ---
 title: Welcome
-date: 2015-04-25 18:44:00 +0000
+date: 2015-04-25T18:44:00.000Z
 categories:
-- announcement
+  - announcement
 layout: post
+published: true
 ---
 
 ![laptop](/assets/laptop.jpg)
 
 Welcome to my blog. I am a frontend .NET web developer (mainly ASP.net MVC with C#).
 At home I use Linux exclusively and code in Python, Haskell, PHP (with the excellent
-[Laravel][1] framework), or any other language that fits the bill.
+[Laravel](http://laravel.org/) framework), or any other language that fits the bill.
 
 I plan to post about programming mainly, but I may also post on other topics as well.
 Stay tuned -- or don't (I won't hate you).
 
 ## P.S.
 
 "Expositus" is Latin for "open" and "accessible".
-
-  [1]:http://laravel.org/

_posts/2015-05-08-css-pseudo-elements-kung-fu.md

@@ -1,40 +1,40 @@
 ---
 title: Pseudo-Element Kung-Fu
-date: 2015-05-08 00:00:00 +0000
+date: 2015-05-08T00:00:00.000Z
 categories:
-- css
-- programming
-- web
+  - css
+  - programming
+  - web
 layout: post
+published: true
 ---
 
 I recently found that the `content` property can contain cooler stuff than just
 strings. For instance, you can show the `href` of a link in a cool popup with
 absolutely no JS:
 
-~~~css
+```css
 content: attr(href);
-~~~
+```
 
 <p data-height="378" data-theme-id="6851" data-slug-hash="YXypBV" data-default-tab="result" data-user="flyingfisch" class='codepen'>See the Pen <a href='http://codepen.io/flyingfisch/pen/YXypBV/'>Pure CSS link hover popup</a> by flyingfisch (<a href='http://codepen.io/flyingfisch'>@flyingfisch</a>) on <a href='http://codepen.io'>CodePen</a>.</p>
 <script async src="//assets.codepen.io/assets/embed/ei.js"></script>
 
 This allows us to show popups without JS as well, like so:
 
-~~~markup
+```markup
 <span class="popup" data-popuptext="This is a CSS-only popup!">Hover!</span>
-~~~
+```
 
-~~~css
+```css
 span.popup:hover:after {
     content: attr(data-popuptext);
 }
-~~~
+```
 
 And of course a live demo with the full source:
 
 <p data-height="268" data-theme-id="6851" data-slug-hash="oXbBXz" data-default-tab="result" data-user="flyingfisch" class='codepen'>See the Pen <a href='http://codepen.io/flyingfisch/pen/oXbBXz/'>Pure CSS hover popup</a> by flyingfisch (<a href='http://codepen.io/flyingfisch'>@flyingfisch</a>) on <a href='http://codepen.io'>CodePen</a>.</p>
 <script async src="//assets.codepen.io/assets/embed/ei.js"></script>
 
 That's all I've got, have fun messing around with `content`!
-

_posts/2015-05-17-using-rest-internally.md

@@ -1,27 +1,28 @@
 ---
 title: Using REST Inside Programs
-date: 2015-05-17 00:00:00 +0000
+date: 2015-05-17T00:00:00.000Z
 categories:
-- programming
-- web
+  - programming
+  - web
 layout: post
+published: true
 ---
 
-Rich Hickey proposed an interesting idea in his [keynote at RailsConf 2012][1].
+Rich Hickey proposed an interesting idea in his [keynote at RailsConf 2012](https://www.youtube.com/watch?v=rI8tNMsozo0).
 The idea, if I understand correctly, is that if serialization is good between
 servers as a way to separate concerns, then why don't we do it between different
 sections of code on the same server?
 
 Using REST between different code blocks seems like a good idea, but serialization seems a bit useless
 in my humble opinion, since it only seems to add complexity to the program.
 
-I decided to write a little [proof-of-concept][2] for this program in Python.
+I decided to write a little [proof-of-concept](https://github.com/flyingfisch/python-rest-poc/commits?author=flyingfisch) for this program in Python.
 There is a module `rest.py` which currently contains one class: `CRUD`. `CRUD`
 has four built-in functions: `create()`, `read()`, `update()`, and `delete()`.
 
 Here is the documentation for each of the built-in functions:
 
-~~~python
+```python
 create(object)
 """
 Creates a new object.
@@ -49,12 +50,12 @@ Deletes object from list.
 Keyword arguments:
 objectId -- Key of object to delete
 """
-~~~
+```
 
 The built-in commands operate on an internal list `_objects`, accessible through
 `read()`. Here is a simple example using the default methods.
 
-~~~python
+```python
 from rest import CRUD
 
 # A dictionary entry class
@@ -86,9 +87,6 @@ Dictionary.Delete(0)
 
 # Print the (empty) dictionary out to the terminal
 print(Dictionary.read())
-~~~
+```
 
 Not sure how useful this is going to be, but it was fun to code up!
-
-  [1]:https://www.youtube.com/watch?v=rI8tNMsozo0
-  [2]:https://github.com/flyingfisch/python-rest-poc/commits?author=flyingfisch

_posts/2015-05-25-building-a-modern-website-part-0.md

@@ -1,12 +1,13 @@
 ---
 title: 'Building a Modern Website: Part 0'
-date: 2015-05-25 00:00:00 +0000
+date: 2015-05-25T00:00:00.000Z
 categories:
-- frontend
-- design
-- tutorial
-- modern-website-series
+  - frontend
+  - design
+  - tutorial
+  - modern-website-series
 layout: post
+published: true
 ---
 
 This is the first of a [3-post series](/modern-website-series/) series on building a modern website. The demo website is a fictional sailing club's homepage. This post covers the mockup process and building the header. The next part will go into the navigation bar and body text.
@@ -27,7 +28,6 @@ Since this is going to be responsive, we need to have a mobile layout as well.
 <figcaption>Wireframe for mobile layout.</figcaption>
 </figure>
 
-
 # Colors
 
 The colors for this site are going to be blue and white. I got the exact shades straight from the [Tango project's color palette](http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines#Color_Palette).
@@ -43,25 +43,25 @@ The first thing I like to do before actually designing the site is find a font t
 
 Here is the `link` tag for the fonts, we're just going to add it into the header. Although there are other methods of using Google Fonts, the `link` tag has the best browser support.
 
-~~~markup
+```markup
 <link href="http://fonts.googleapis.com/css?family=Montserrat:400,700|Alegreya:400,400italic,700,700italic" rel="stylesheet" type="text/css">
-~~~
+```
 
 We will also be using [Normalize.css](https://necolas.github.io/normalize.css/) which basically gives you a starting point that looks the same across all browsers. Since we want to override it's styles with ours we put it's link tag first. Our `head` tag should look something like this now:
 
-~~~markup
+```markup
 <head>
     <title>R. S. Sailing Club</title>
 
     <link href="http://fonts.googleapis.com/css?family=Montserrat:400,700|Alegreya:400,400italic,700,700italic" rel="stylesheet" type="text/css">
     <link href="/css/normalize.css" rel="stylesheet" type="text/css">
     <link href="/css/style.css" rel="stylesheet" type="text/css">
 </head>
-~~~
+```
 
 We're going to be using [SASS](http://sass-lang.com/) for the stylesheets, but don't worry, I'll explain any nuances we come across in the project. For now, just think of it as CSS with extra features. Here is our stylesheet so far:
 
-~~~scss
+```scss
 html, body {
     width: 100%;
     height: 100%;
@@ -79,17 +79,17 @@ body {
 h1, h2, h3, h4, h5, h6 {
     font-family: 'Montserrat', sans-serif;
 }
-~~~
+```
 
 # Designing the header
 
 Now that the fonts have been selected, we can start on the header. The markup for now is pretty simple.
 
-~~~markup
+```markup
 <header>
     <h1>R. S. Sailing Club</h1>
 </header>
-~~~
+```
 
 Now let's get into the CSS. We want the background of the header to be dark blue, and the font should be white. Here is the site so far:
 
@@ -104,45 +104,45 @@ This is probably a good time to go over a couple important SASS features: variab
 
 Variables names start with a `$`, and can contain any information you can put in a property. For example:
 
-~~~scss
+```scss
 $my-border: 2px solid black;
 
 div {
     border: $my-border;
 }
-~~~
+```
 
 That compiles to this CSS:
 
-~~~css
+```css
 div {
     border: 2px solid black;
 }
-~~~
+```
 
 # Nested Selectors
 
 If you want to select an element inside another element, you can nest the selectors. Here is an example:
 
-~~~scss
+```scss
 header {
     h1 {
         color: #fff;
     }
 }
-~~~
+```
 
 This compiles to:
 
-~~~css
+```css
 header h1 {
     color: #fff;
 }
-~~~
+```
 
 You can also use the `&` to select the parent element, like this:
 
-~~~scss
+```scss
 a {
     color #000;
     text-decoration: none;
@@ -151,19 +151,16 @@ a {
         text-decoration: underline;
     }
 }
-~~~
+```
 
 Which compiles into this CSS:
 
-~~~css
+```css
 a {
     color: #000;
     text-decoration: none;
 }
 a:hover {
     text-decoration: underline;
 }
-~~~
-
-
-
+```

_posts/2015-05-28-tolkien-ipsum.md

@@ -1,9 +1,10 @@
 ---
 title: Announcing Tolkien Ipsum
-date: 2015-05-28 00:00:00 +0000
+date: 2015-05-28T00:00:00.000Z
 categories:
-- announcement
+  - announcement
 layout: post
+published: true
 ---
 
 I built a little website that generates Lord of the Rings themed Lorem Ipsum. You can [check it out live](http://tolkienipsum.cloudapp.net/) or view the source on [GitHub](https://github.com/flyingfisch/tolkienIpsum).