Build.

docs/blog/2017/05/05/fixing-drupal-simpletest-docker/index.html

@@ -85,7 +85,7 @@
                 <main class="col-md-9">
                                             <h1>Fixing Drupal SimpleTest issues inside Docker Containers</h1>
 
-<p class="posted">5th May 2017</p>
+<p class="posted text-light">5th May 2017</p>
 
     <p><strong>TL;DR</strong> You need to include the name of your web server container as the <code>--url</code> option to <code>run-scripts.php</code>.</p>
 

docs/blog/2017/05/05/updating-override-node-options-tests/index.html

@@ -84,7 +84,7 @@
                 <main class="col-md-9">
                                             <h1>Updating Override Node Options Tests</h1>
 
-<p class="posted">5th May 2017</p>
+<p class="posted text-light">5th May 2017</p>
 
     <p>Recently, I reviewed <a href="https://www.drupal.org/node/974730">a patch</a> in the <a href="https://www.drupal.org/project/override_node_options">Override Node Options</a> module issue queue. For those not familiar with it, the module adds extra permissions for node options like "authored by" and "published on" which are normally only available to users with the <code>administer nodes</code> permission. What the patch does is to optionally add another set of permissions that enable options for all content types - e.g. "override published option for all node types", in addition to or instead of the content type specific ones.</p>
 

docs/blog/2017/05/15/drupalcamp-bristol-early-bird-tickets-sessions-sponsors/index.html

@@ -85,7 +85,7 @@
                 <main class="col-md-9">
                                             <h1>DrupalCamp Bristol 2017 - Early Bird Tickets, Call for Sessions, Sponsors</h1>
 
-<p class="posted">15th May 2017</p>
+<p class="posted text-light">15th May 2017</p>
 
     <p><img src="/assets/images/blog/drupalcamp-bristol-17-logo.jpg" alt="DrupalCamp Bristol 2017 logo" class="is-centered"></p>
 

docs/blog/2017/05/20/turning-drupal-module-into-feature/index.html

@@ -84,7 +84,7 @@
                 <main class="col-md-9">
                                             <h1>Turning Your Custom Drupal Module into a Feature</h1>
 
-<p class="posted">20th May 2017</p>
+<p class="posted text-light">20th May 2017</p>
 
     <p>Yesterday I was fixing a bug in an inherited Drupal 7 custom module, and I decided that I was going to add some tests to ensure that the bug was fixed and doesn’t get accidentially re-introduced in the future. The test though required me to have a particular content type and fields which are specific to this site, so weren’t present within the standard installation profile used to run tests.</p>