Fix build, add featured images, schedule posts

_includes/footer.html

@@ -1,11 +1,10 @@
 <footer>
 	<div class="container">
 		<ul class="footer-menu">
-			<li><a href="" title="">About the Blog</a></li>
-			<li><a href="" title="">Jobs</a></li>
-			<li><a href="" title="">Contact</a></li>
-			<li><a href="" title="">Legal Information</a></li>
-			<li><a href="" title="">Data Protection</a></li>
+			<li><a href="https://www.signavio.com/jobs/" title="Career Opportunities at Signavio">Jobs</a></li>
+			<li><a href="https://www.signavio.com/contact/" title="Contact form">Contact</a></li>
+			<li><a href="https://www.signavio.com/legal-info/">Legal Information</a></li>
+			<!-- <li><a href="" title="">Data Protection</a></li> -->
 		</ul>
 	</div>
 </footer>

_posts/2017-01-01-json-type-information.md → _posts/2017-02-15-json-type-information.md

@@ -4,6 +4,9 @@ description: "Pros and cons of different ways to indicate JSON types"
 author: Peter Hilton
 tags: JSON, data types
 layout: article
+image:
+  feature: /2017/json.png
+  alt: "Representing typed data in JSON format"
 ---
 
 [JSON](https://en.wikipedia.org/wiki/JSON), specified by [RFC7159](https://tools.ietf.org/html/rfc7159) has taken over from [XML](https://en.wikipedia.org/wiki/XML) as data format of choice for web service [API](https://en.wikipedia.org/wiki/Application_programming_interface)s.
@@ -101,10 +104,12 @@ For the next step you can specify each JSON object’s type in a special inline
 You can probably avoid name clashes by using an underscore prefix, calling it `_type`.
 
 ```json
-"price" : {
-  "_type" : "Money",
-  "currency" : "EUR",
-  "amount" : 10.00
+{
+  "price" : {
+    "_type" : "Money",
+    "currency" : "EUR",
+    "amount" : 10.00
+  }
 }
 ```
 
@@ -119,11 +124,13 @@ You can keep your serialisation code relatively clean by separating the object
 This also allows the parser to read the type before reading the value using a type-specific parser.
 
 ```json
-"price" : {
-  "type" : "Money",
-  "value" : {
-    "currency" : "EUR",
-    "amount" : 10.00
+{
+  "price" : {
+    "type" : "Money",
+    "value" : {
+      "currency" : "EUR",
+      "amount" : 10.00
+    }
   }
 }
 ```
@@ -136,13 +143,15 @@ Instead of using the type and value name as a property name and object value, yo
 In this approach, the array holds the same pair of values as the object in the previous approach, but transforms the `type` and `value` properties to anonymous array items.
 
 ```json
-"price" : [
-  "@Money",
-  {
-    "currency" : "EUR",
-    "amount" : 10.00
-  }
-]
+{
+  "price" : [
+    "@Money",
+    {
+      "currency" : "EUR",
+      "amount" : 10.00
+    }
+  ]
+}
 ```
 
 This probably only makes sense if you use a programming language with tuples, and you’re used to pairs of values.
@@ -155,10 +164,12 @@ You can separate the type name and object value more neatly by using the type na
 This example uses a `@` prefix for the type name, to make the JSON more human-readable.
 
 ```json
-"price" : {
-  "@Money" : {
-    "currency" : "EUR",
-    "amount" : 10.00
+{
+  "price" : {
+    "@Money" : {
+      "currency" : "EUR",
+      "amount" : 10.00
+    }
   }
 }
 ```
@@ -171,12 +182,14 @@ You can extend the previous approach by mixing multiple types, so you can repres
 This example represents the same model, with the addition that `Money` subclasses (extends) `Number`.
 
 ```json
-"price" : {
-  "@Number" : {
-    "amount" : 10.00
-  },
-  "@Money" : {
-    "currency" : "EUR",
+{
+  "price" : {
+    "@Number" : {
+      "amount" : 10.00
+    },
+    "@Money" : {
+      "currency" : "EUR"
+    }
   }
 }
 ```

_posts/2017-01-08-introduce-markdown-poi.md → _posts/2017-02-22-introduce-markdown-poi.md

@@ -1,9 +1,12 @@
 ---
-title: "How to transform Markdown to a Word document with Apache POI"
+title: "Transforming Markdown to Word with Apache POI"
 description: "Using Pegdown and JSoup to generate Apache POI’s XWPF format"
 author: Stefan Herz
 tags: document, data transformation, Microsoft Word, Apache POI, JSoup, Pegdown
 layout: article
+image:
+  feature: /2017/word-basic-text-formats.png
+  alt: "Basic text formatting in a Word document"
 ---
 
 ## Introducing a way to transform Markdown to a Word document

_scss/_settings.scss

@@ -1,4 +1,4 @@
-@import '../_gems/ruby/2.2.0/gems/susy-2.2.12/sass/susy';
+@import '../_gems/ruby/2.3.0/gems/susy-2.2.12/sass/susy';
 
 // Susy defaults setting
 

index.html

@@ -4,7 +4,7 @@
 <div class="container">
 	<div class="blog-intro">
 		<h1>Signavio Tech Blog</h1>
-		<p>Some short explanation about this blog</p>
+		<p>Ideas, techniques and other stories from Signavio’s engineering team.</p>
 	</div>
 	<div class="grid">
 		<div class="grid-item-sizer"></div>