added post about notable code

Gemfile.lock

@@ -1,85 +1,52 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    blankslate (2.1.2.4)
-    celluloid (0.16.0)
-      timers (~> 4.0.0)
-    classifier-reborn (2.0.3)
-      fast-stemmer (~> 1.0)
-    coffee-script (2.3.0)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.9.1)
     colorator (0.1)
-    execjs (2.3.0)
-    fast-stemmer (1.0.2)
-    ffi (1.9.6)
-    ffi (1.9.6-x64-mingw32)
-    ffi (1.9.6-x86-mingw32)
-    hitimes (1.2.2)
-    hitimes (1.2.2-x86-mingw32)
-    jekyll (2.5.3)
-      classifier-reborn (~> 2.0)
+    ffi (1.9.10)
+    ffi (1.9.10-x64-mingw32)
+    ffi (1.9.10-x86-mingw32)
+    jekyll (3.1.2)
       colorator (~> 0.1)
-      jekyll-coffeescript (~> 1.0)
-      jekyll-gist (~> 1.0)
-      jekyll-paginate (~> 1.0)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 1.1)
       kramdown (~> 1.3)
-      liquid (~> 2.6.1)
+      liquid (~> 3.0)
       mercenary (~> 0.3.3)
-      pygments.rb (~> 0.6.0)
-      redcarpet (~> 3.1)
+      rouge (~> 1.7)
       safe_yaml (~> 1.0)
-      toml (~> 0.1.0)
-    jekyll-coffeescript (1.0.1)
-      coffee-script (~> 2.2)
-    jekyll-gist (1.1.0)
-    jekyll-paginate (1.1.0)
-    jekyll-sass-converter (1.3.0)
-      sass (~> 3.2)
-    jekyll-sitemap (0.8.0)
-    jekyll-watch (1.2.1)
-      listen (~> 2.7)
-    kramdown (1.6.0)
-    liquid (2.6.2)
-    listen (2.8.5)
-      celluloid (>= 0.15.2)
+    jekyll-sass-converter (1.4.0)
+      sass (~> 3.4)
+    jekyll-sitemap (0.10.0)
+    jekyll-watch (1.3.1)
+      listen (~> 3.0)
+    kramdown (1.10.0)
+    liquid (3.0.6)
+    listen (3.0.6)
       rb-fsevent (>= 0.9.3)
-      rb-inotify (>= 0.9)
+      rb-inotify (>= 0.9.7)
     mercenary (0.3.5)
-    octopress (3.0.0.rc.34)
-      jekyll (~> 2.0)
+    octopress (3.0.12.pre.1)
+      jekyll (>= 2.0)
       mercenary (~> 0.3.2)
       octopress-deploy
       octopress-escape-code (~> 2.0)
       octopress-hooks (~> 2.0)
+      redcarpet (~> 3.0)
       titlecase
-    octopress-deploy (1.1.0)
+    octopress-deploy (1.3.0)
       colorator
-    octopress-escape-code (2.0.6)
-      octopress-hooks (~> 2.0)
-    octopress-hooks (2.6.0)
-      jekyll (~> 2.0)
-    parslet (1.5.0)
-      blankslate (~> 2.0)
-    posix-spawn (0.3.10)
-    pygments.rb (0.6.2)
-      posix-spawn (~> 0.3.6)
-      yajl-ruby (~> 1.2.0)
-    rb-fsevent (0.9.4)
-    rb-inotify (0.9.5)
+    octopress-escape-code (2.1.1)
+      jekyll (~> 3.0)
+    octopress-hooks (2.6.1)
+      jekyll (>= 2.0)
+    rb-fsevent (0.9.7)
+    rb-inotify (0.9.7)
       ffi (>= 0.5.0)
-    redcarpet (3.2.2)
+    redcarpet (3.3.4)
+    rouge (1.10.1)
     safe_yaml (1.0.4)
-    sass (3.4.13)
-    timers (4.0.1)
-      hitimes
+    sass (3.4.21)
     titlecase (0.1.1)
-    toml (0.1.2)
-      parslet (~> 1.5.0)
-    yajl-ruby (1.2.1)
 
 PLATFORMS
   ruby
@@ -92,4 +59,4 @@ DEPENDENCIES
   octopress (~> 3.0.0.rc.12)
 
 BUNDLED WITH
-   1.10.4
+   1.11.1

_config.yml

@@ -9,7 +9,7 @@ url:              http://devopsfortherestof.us
 
 permalink:   /:categories/:title/
 markdown:    kramdown
-highlighter: pygments
+highlighter: pygments.rb
 sass:
   sass_dir: _sass
   style: compressed
@@ -21,7 +21,7 @@ kramdown:
   footnote_nr: 1
   entity_output: as_char
   toc_levels: 1..6
-  use_coderay: false
+  enable_coderay: false
 
 
 # Site owner

_posts/2015-09-05-devign.md

@@ -17,7 +17,7 @@ But before elaborating on the idea mentioned in the video, let's take a step bac
 
 <!--break-->
 
-##An Old Problem##
+## An Old Problem ##
 
 There has always been some level of trouble going from design to implementation. Creatives and technologists think differently, approach problems differently, and follow different processes to get their work done.
 
@@ -29,7 +29,7 @@ So how does all of this play out? Without technologists in place early on to wei
 
 On the other end of things, without designers available during development, the integrity of the creative can suffer, and the effort required to address a pile of visual defects at the end of a project can be monumental.
 
-##Making Matters Worse##
+## Making Matters Worse ##
 
 Just when we thought we had a handle on the situation, when we became used to overlapping the handoffs a bit to get around the limitations of waterfall, the mobile web arrived, and half-measures were no longer good enough. Enter responsive design.
 
@@ -39,7 +39,7 @@ But it's 2015, and <a href="https://24ways.org/2011/collaborative-development-fo
 
 Well for one thing, designers and developers often <strong>can't</strong> work side by side. Many brands work with multiple vendors, and one partner will be charged with design and another with implementation. Even within a single company, teams are often distributed.
 
-##This One Weird Trick##
+## This One Weird Trick ##
 
 It's tempting to think that there's some shortcut that will remove all the challenges of collaboration between design and dev.
 
@@ -49,7 +49,7 @@ But like getting six-pack abs in four weeks, the reality isn't so easy. Question
 
 The <a href="https://www.google.com/trends/explore#q=learn%20to%20code" target="_blank" title="Google Trends analysis of the phrase &quot;learn to code&quot;">rise</a> of the "learn to code" movement is possibly a step in the right direction, since anything that promotes interdisciplinary knowledge sharing will be helpful (you could also teach developers the importance of design, for added effect). But shared understanding alone isn't enough.
 
-##Devops for Design/Dev##
+## Devops for Design/Dev ##
 
 So how can we leverage automation and improve collaboration to ease this constraint?
 
@@ -68,7 +68,7 @@ But to be clear, the point of me putting this out there is not really about tryi
 
 It's more about demonstrating that the <a href="http://itrevolution.com/the-three-ways-principles-underpinning-devops/" target="_blank" title="The Three Ways, IT Revolution Press">ideas behind devops</a> are applicable beyond the world of build/release. The devops toolchain could provide <em>serious</em> value to other disciplines, and it's up to those of us with some exposure to the relevant practices and technologies to help identify these opportunities.
 
-##Enough from Me##
+## Enough from Me ##
 I'll be totally honest&mdash;I'm still trying to hone in on the type of content to highlight for this blog. I really do think that bringing devops to a wider audience could have a <em>huge</em> impact on the way we all work, but I need your help.
 
 <p class="over-to-you">

_posts/2015-09-18-guapo.md

@@ -67,7 +67,7 @@ Finally, we want all of of our building and testing to happen automatically, bot
 
 Not only does this allow us to both emulate very closely the actual server environment locally via Docker, and deploy much more quickly and frequently with Docker, this also makes getting our server set up initially much easier and faster.
 
-##Putting it all together
+## Putting it all together ##
 
 The point of all of this is to hasten the ramp up time for new developers on a project, simplify the build and deployment process, and make testing, code quality, and performance testing inherent to development. Developers can very quickly pull down a code base and have a reliable development environment, testing, and a C.I. environment all setup in a matter of minutes. Even better, the same environment could easily be deployed to a server. Gone are the days where project and environment setup feels like this:
 <figure>

_posts/2015-09-27-agile-dirty-word.md

@@ -67,7 +67,7 @@ As a developer, I've been in similar situations. When scope isn't controlled and
 
 Lucky for me, I think there's little question out there that Agile methodologies pay dividends for development work. I think it's time we share the wealth.
 
-##Over to You##
+## Over to You ##
 
 <p class="over-to-you">
 	Has anyone out there ever followed Agile methodologies during the design phase of a project? I'd love to hear some examples in the comments.

_posts/2016-04-08-devign-update.md

@@ -0,0 +1,28 @@
+---
+layout: post
+title: Development + Design (Update)
+author: joe_morgan
+excerpt: "When I posted about the importance of development and design collaboration, I proposed a hypothetical tool to alleviate the constraints found in responsive workflows. Well, thanks to the Zurb Foundation, that tool is hypothetical no longer."
+tags: [development, design, devops, agile collaboration, responsive design, zurb, notable code]
+comments: true
+---
+
+Back in September of 2015, I wrote about [development and design collaboration](/submission/ "development and design collaboration"). In that post, I referenced [my What's Next Is Now presentation](https://www.youtube.com/embed/F9JRKOPeATo "What's Next Is Now on YouTube") from July of last year, where I talked about a hypothetical tool intended to alleviate constraints found in responsive design workflows.
+
+Unbeknownst to me, it turns out the folks over at [Zurb](http://foundation.zurb.com/ "Zurb") (makers of the excellent Foundation framework) were working on just such a solution: [Notable Code](http://zurb.com/notable/features/code "Notable Code"). TLDR: It's awesome.
+
+<!--break-->
+
+<figure>
+	<img src="/images/notable.png" alt="Screenshot of the Notable Code application" />
+	<figcaption><a href="http://zurb.com/notable/features/code" title="Notable Code">Notable Code by Zurb</a></figcaption>
+</figure>
+
+Launched near the end of last year, Notable had almost everything I was looking for: real-time/persisted collaboration between design and dev, breakpoint-specific feedback, and automatic scrolling, resizing, and focusing to recreate the tester's point of view.
+
+At first, it was limited by the fact that you had to upload your code as HTML to their servers in order to benefit from its incredible collaboration and review benefits. But in more recently, it looks like they've added a browser plugin to allow users to capture live sites. 
+
+## Enough from Me ##
+<p class="over-to-you">
+	Have you used Notable Code? I'd be really interested in hearing your impressions. Leave a comment!
+</p>