RubyGems - jekyll-docs - Versions diffs - 3.3.0 → 3.3.1 - Mend

jekyll-docs 3.3.0 → 3.3.1

Files changed (117) hide show

checksums.yaml +4 -4
data/site/404.html +11 -11
data/site/community/index.html +16 -16
data/site/conduct/index.html +7 -7
data/site/css/screen.css +52 -38
data/site/docs/assets/index.html +25 -17
data/site/docs/collections/index.html +25 -17
data/site/docs/conduct/index.html +29 -18
data/site/docs/configuration/index.html +26 -18
data/site/docs/continuous-integration/index.html +29 -21
data/site/docs/contributing/index.html +27 -19
data/site/docs/datafiles/index.html +26 -17
data/site/docs/deployment-methods/index.html +24 -43
data/site/docs/drafts/index.html +25 -17
data/site/docs/extras/index.html +25 -17
data/site/docs/frontmatter/index.html +27 -19
data/site/docs/github-pages/index.html +42 -27
data/site/docs/history/index.html +93 -19
data/site/docs/home/index.html +25 -17
data/site/docs/index.html +7 -7
data/site/docs/installation/index.html +50 -18
data/site/docs/maintaining/affinity-team-captain/index.html +691 -0
data/site/docs/maintaining/avoiding-burnout/index.html +694 -0
data/site/docs/maintaining/becoming-a-maintainer/index.html +702 -0
data/site/docs/maintaining/index.html +698 -0
data/site/docs/maintaining/merging-a-pull-request/index.html +730 -0
data/site/docs/maintaining/reviewing-a-pull-request/index.html +710 -0
data/site/docs/maintaining/special-labels/index.html +686 -0
data/site/docs/maintaining/triaging-an-issue/index.html +720 -0
data/site/docs/migrations/index.html +25 -17
data/site/docs/pages/index.html +25 -17
data/site/docs/pagination/index.html +25 -17
data/site/docs/permalinks/index.html +25 -17
data/site/docs/plugins/index.html +35 -17
data/site/docs/posts/index.html +25 -17
data/site/docs/quickstart/index.html +23 -15
data/site/docs/resources/index.html +23 -15
data/site/docs/sites/index.html +25 -17
data/site/docs/static-files/index.html +25 -17
data/site/docs/structure/index.html +25 -17
data/site/docs/templates/index.html +39 -30
data/site/docs/themes/index.html +23 -15
data/site/docs/troubleshooting/index.html +27 -19
data/site/docs/upgrading/0-to-2/index.html +25 -17
data/site/docs/upgrading/2-to-3/index.html +26 -18
data/site/docs/upgrading/index.html +26 -15
data/site/docs/usage/index.html +25 -17
data/site/docs/variables/index.html +25 -17
data/site/docs/windows/index.html +31 -19
data/site/feed.xml +17 -14
data/site/github.html +7 -7
data/site/help/index.html +21 -21
data/site/index.html +13 -13
data/site/issues.html +7 -7
data/site/latest_version.txt +1 -1
data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +23 -19
data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +21 -17
data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +23 -19
data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +21 -17
data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +23 -19
data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +23 -19
data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +21 -17
data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +21 -17
data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +23 -19
data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +23 -19
data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +23 -19
data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +23 -19
data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +23 -19
data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +23 -19
data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +23 -19
data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +23 -19
data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +23 -19
data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +23 -19
data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +23 -19
data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +21 -17
data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +21 -17
data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +21 -17
data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +23 -19
data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +23 -19
data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +21 -17
data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +23 -19
data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +21 -17
data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +23 -19
data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +23 -19
data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +23 -19
data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +23 -19
data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +21 -17
data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +23 -19
data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +21 -17
data/site/news/2015/02/26/introducing-jekyll-talk/index.html +21 -17
data/site/news/2015/10/26/jekyll-3-0-released/index.html +21 -17
data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +21 -17
data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +23 -19
data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +23 -19
data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +23 -19
data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +23 -19
data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +21 -17
data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +21 -17
data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +21 -17
data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +21 -17
data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +23 -19
data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +21 -17
data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +21 -17
data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +23 -19
data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +21 -17
data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +21 -17
data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +23 -19
data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +21 -17
data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +26 -22
data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +543 -0
data/site/news/index.html +63 -19
data/site/news/releases/index.html +63 -19
data/site/readme.md +16 -0
data/site/robots.txt +1 -0
data/site/sitemap.xml +217 -146
metadata +16 -6
data/site/freenode.txt +0 -1

data/site/docs/maintaining/triaging-an-issue/index.html ADDED Viewed

@@ -0,0 +1,720 @@
+<!DOCTYPE HTML>
+<html lang="en-US">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width,initial-scale=1">
+  <meta name="generator" content="Jekyll v3.3.1">
+  <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites">
+  <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
+  <link rel="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
+  <link rel="stylesheet" href="/css/screen.css">
+  <link rel="icon" type="image/x-icon" href="/favicon.ico">
+  <!-- Begin Jekyll SEO tag v2.1.0 -->
+<title>Triaging an Issue - Jekyll • Simple, blog-aware, static sites</title>
+<meta property="og:title" content="Triaging an Issue">
+<meta name="description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.">
+<meta property="og:description" content="This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.">
+<link rel="canonical" href="https://jekyllrb.com/docs/maintaining/triaging-an-issue/">
+<meta property="og:url" content="https://jekyllrb.com/docs/maintaining/triaging-an-issue/">
+<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
+<meta property="og:type" content="article">
+<meta property="article:published_time" content="2017-01-20T13:17:57-08:00">
+<meta name="twitter:card" content="summary">
+<meta name="twitter:site" content="@jekyllrb">
+<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
+<script type="application/ld+json">
+{"@context": "http://schema.org",
+"@type": "BlogPosting",
+"headline": "Triaging an Issue",
+"datePublished": "2017-01-20T13:17:57-08:00",
+"description": "This guide is for maintainers. These special people have write access to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.",
+"publisher": {"@type": "Organization",
+"logo": {"@type": "ImageObject",
+"url": "https://jekyllrb.com/img/logo-2x.png"}},
+"url": "https://jekyllrb.com/docs/maintaining/triaging-an-issue/"}</script>
+<!-- End Jekyll SEO tag -->
+  <!--[if lt IE 9]>
+  <script src="/js/html5shiv.min.js"></script>
+  <script src="/js/respond.min.js"></script>
+  <![endif]-->
+</head>
+<body class="wrap">
+  <header>
+  <nav class="mobile-nav show-on-mobiles">
+    <ul>
+  <li class="">
+    <a href="/">Home</a>
+  </li>
+  <li class="current">
+    <a href="/docs/home/">Docs</a>
+  </li>
+  <li class="">
+    <a href="/news/">News</a>
+  </li>
+  <li class="">
+    <a href="/community/">Community</a>
+  </li>
+  <li class="">
+    <a href="/help/">Help</a>
+  </li>
+  <li>
+    <a href="https://github.com/jekyll/jekyll"><span class="hide-on-mobiles">View on </span>GitHub</a>
+  </li>
+</ul>
+  </nav>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
+      <h1>
+        <a href="/">
+          <span class="sr-only">Jekyll</span>
+          <img src="/img/logo-2x.png" width="249" height="115" alt="Jekyll Logo">
+        </a>
+      </h1>
+    </div>
+    <nav class="main-nav unit two-thirds hide-on-mobiles">
+      <ul>
+  <li class="">
+    <a href="/">Home</a>
+  </li>
+  <li class="current">
+    <a href="/docs/home/">Docs</a>
+  </li>
+  <li class="">
+    <a href="/news/">News</a>
+  </li>
+  <li class="">
+    <a href="/community/">Community</a>
+  </li>
+  <li class="">
+    <a href="/help/">Help</a>
+  </li>
+  <li>
+    <a href="https://github.com/jekyll/jekyll"><span class="hide-on-mobiles">View on </span>GitHub</a>
+  </li>
+</ul>
+    </nav>
+  </div>
+</header>
+    <section class="docs">
+    <div class="grid">
+      <div class="docs-nav-mobile unit whole show-on-mobiles">
+  <select onchange="if (this.value) window.location.href=this.value">
+    <option value="">Navigate the docs…</option>
+    <optgroup label="Getting Started">
+  <option value="/docs/home/">Welcome</option>
+  <option value="/docs/quickstart/">Quick-start guide</option>
+  <option value="/docs/installation/">Installation</option>
+  <option value="/docs/usage/">Basic Usage</option>
+  <option value="/docs/structure/">Directory structure</option>
+  <option value="/docs/configuration/">Configuration</option>
+    </optgroup>
+    <optgroup label="Your Content">
+  <option value="/docs/frontmatter/">Front Matter</option>
+  <option value="/docs/posts/">Writing posts</option>
+  <option value="/docs/drafts/">Working with drafts</option>
+  <option value="/docs/pages/">Creating pages</option>
+  <option value="/docs/static-files/">Static Files</option>
+  <option value="/docs/variables/">Variables</option>
+  <option value="/docs/collections/">Collections</option>
+  <option value="/docs/datafiles/">Data Files</option>
+  <option value="/docs/assets/">Assets</option>
+  <option value="/docs/migrations/">Blog migrations</option>
+    </optgroup>
+    <optgroup label="Customization">
+  <option value="/docs/templates/">Templates</option>
+  <option value="/docs/permalinks/">Permalinks</option>
+  <option value="/docs/pagination/">Pagination</option>
+  <option value="/docs/plugins/">Plugins</option>
+  <option value="/docs/themes/">Themes</option>
+  <option value="/docs/extras/">Extras</option>
+    </optgroup>
+    <optgroup label="Deployment">
+  <option value="/docs/github-pages/">GitHub Pages</option>
+  <option value="/docs/deployment-methods/">Deployment methods</option>
+  <option value="/docs/continuous-integration/">Continuous Integration</option>
+    </optgroup>
+    <optgroup label="Miscellaneous">
+  <option value="/docs/troubleshooting/">Troubleshooting</option>
+  <option value="/docs/sites/">Sites using Jekyll</option>
+  <option value="/docs/resources/">Resources</option>
+  <option value="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</option>
+  <option value="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</option>
+    </optgroup>
+    <optgroup label="Meta">
+  <option value="/docs/contributing/">Contributing</option>
+  <option value="/docs/maintaining/">Maintaining Jekyll</option>
+  <option value="/docs/conduct/">Code of Conduct</option>
+  <option value="/docs/history/">History</option>
+    </optgroup>
+  </select>
+</div>
+      <div class="unit four-fifths">
+        <article>
+          <div class="improve right hide-on-mobiles">
+            <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/maintaining/triaging-an-issue.md"><i class="fa fa-pencil"></i>  Improve this page</a>
+          </div>
+          <h1>Triaging an Issue</h1>
+          <p class="note info"><strong>This guide is for maintainers.</strong> These special people have <strong>write access</strong> to one or more of Jekyll’s repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.</p>
+<p>Before evaluating an issue, it is important to identify if it is a feature
+request or a bug. For the Jekyll project the following definitions are used
+to identify a feature or a bug:</p>
+<p><strong>Feature</strong> - A feature is defined as a request that adds functionality to
+Jekyll outside of its current capabilities.
+<strong>Bug</strong> - A bug is defined as an issue that identifies an error that a user
+(or users) encounter when using current Jekyll functionalities.</p>
+<h2 id="feature">Feature?</h2>
+<p>If the issue describes a feature request, ask:</p>
+<ol>
+  <li>Is this a setting? <a href="http://ben.balter.com/2016/03/08/optimizing-for-power-users-and-edge-cases/#settings-are-a-crutch">Settings are a crutch</a> for doing “the right thing”. Settings usually point to a bad default or an edge case that could be solved easily with a plugin. Keep the <img class="emoji" title=":christmas_tree:" alt=":christmas_tree:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f384.png" height="20" width="20" align="absmiddle"> of settings as small as possible so as not to reduce the usability of the product. We like the philosophy “decisions not options.”</li>
+  <li>Would at least 80% of users find it useful? If even a quarter of our users won’t use it, it’s very likely that the request doesn’t fit our product’s core goal.</li>
+  <li>Is there another way to accomplish the end goal of the request? Most feature requests are due to bad documentation for or understanding of a pre-existing feature. See if you can clarify the end goal of the request. What is the user trying to do? Could they accomplish that goal through another feature we already support?</li>
+  <li>Even if 80% of our users will use it, does it fit the core goal of our project? We are writing a tool for making static websites, not a swiss army knife for publishing more generally.</li>
+</ol>
+<p>Feel free to get others’ opinions and ask questions of the issue author, but depending upon the answers to the questions above, it may be out of scope for our project.</p>
+<p>If the request is within scope, prioritize it on the product roadmap with the other maintainers. Apply the appropriate tags and ensure the right people have weighed in to define the feature’s scope and implementation. If you want to be the <em>best ever</em>, submit a PR yourself which adds the feature.</p>
+<h2 id="bug">Bug?</h2>
+<h3 id="reproducibility">Reproducibility</h3>
+<p>If the bug has clear reproduction steps, take a minute to try them. If it helps, write a test in our test suite for the scenario which replicates the problem. Can you reliably replicate the issue?</p>
+<p>If you can’t replicate the issue, post your replication steps which didn’t work and ask for clarification from the issue author.</p>
+<h3 id="supported-platform">Supported Platform</h3>
+<p>Is the author using a supported platform? We support the latest versions of macOS, Ubuntu, Debian, CentOS, Fedora, and Arch Linux.</p>
+<p>You may close the issue immediately if the author cannot reproduce the issue on a supported platform. For Windows-related problems, leave a comment letting the user know that Windows is not officially supported, but that they may absolutely continue using the issue to communicate with folks from <code class="highlighter-rouge">@jekyll/windows</code> to further investigate. Additionally, you can point them to Jekyll Talk (https://talk.jekyllrb.com) as a means of getting support from the community.</p>
+<p>If the user is experiencing issues with GitHub Pages or another hosted platform that we cannot reproduce, please direct them to the platform’s support channel and close the issue.</p>
+<h3 id="what-they-wanted-vs-what-they-got">What they wanted vs. what they got</h3>
+<p>An issue without a clear explanation of what the user got and what they were expecting to get is not an issue we can accurately respond to. If the user doesn’t provide this information, please ask for clarification and apply the <code class="highlighter-rouge">pending-feedback</code> label. This information helps us build test cases such that we do not break the behaviour again in the future. The <code class="highlighter-rouge">pending-feedback</code> label will be removed automatically once the issue author posts a reply.</p>
+<p>Is what they wanted to get something we want to happen? Sometimes a bug report is actually masquerading as a feature request. See the guidance above for handling feature requests.</p>
+<h3 id="staleness-and-automatic-closure">Staleness and automatic closure</h3>
+<p><a href="https://github.com/jekyllbot" class="user-mention">@jekyllbot</a> will automatically mark issues as <code class="highlighter-rouge">stale</code> if no activity occurs for at least one month. <a href="https://github.com/jekyllbot" class="user-mention">@jekyllbot</a> leaves a comment asking for information about reproducibility in current versions. If no one responds after another month, the issue is automatically closed.</p>
+        </article>
+      </div>
+      <div class="unit one-fifth hide-on-mobiles">
+  <aside>
+    <h4>Getting Started</h4>
+    <ul>
+  <li class=""><a href="/docs/home/">Welcome</a></li>
+  <li class=""><a href="/docs/quickstart/">Quick-start guide</a></li>
+  <li class=""><a href="/docs/installation/">Installation</a></li>
+  <li class=""><a href="/docs/usage/">Basic Usage</a></li>
+  <li class=""><a href="/docs/structure/">Directory structure</a></li>
+  <li class=""><a href="/docs/configuration/">Configuration</a></li>
+</ul>
+    <h4>Your Content</h4>
+    <ul>
+  <li class=""><a href="/docs/frontmatter/">Front Matter</a></li>
+  <li class=""><a href="/docs/posts/">Writing posts</a></li>
+  <li class=""><a href="/docs/drafts/">Working with drafts</a></li>
+  <li class=""><a href="/docs/pages/">Creating pages</a></li>
+  <li class=""><a href="/docs/static-files/">Static Files</a></li>
+  <li class=""><a href="/docs/variables/">Variables</a></li>
+  <li class=""><a href="/docs/collections/">Collections</a></li>
+  <li class=""><a href="/docs/datafiles/">Data Files</a></li>
+  <li class=""><a href="/docs/assets/">Assets</a></li>
+  <li class=""><a href="/docs/migrations/">Blog migrations</a></li>
+</ul>
+    <h4>Customization</h4>
+    <ul>
+  <li class=""><a href="/docs/templates/">Templates</a></li>
+  <li class=""><a href="/docs/permalinks/">Permalinks</a></li>
+  <li class=""><a href="/docs/pagination/">Pagination</a></li>
+  <li class=""><a href="/docs/plugins/">Plugins</a></li>
+  <li class=""><a href="/docs/themes/">Themes</a></li>
+  <li class=""><a href="/docs/extras/">Extras</a></li>
+</ul>
+    <h4>Deployment</h4>
+    <ul>
+  <li class=""><a href="/docs/github-pages/">GitHub Pages</a></li>
+  <li class=""><a href="/docs/deployment-methods/">Deployment methods</a></li>
+  <li class=""><a href="/docs/continuous-integration/">Continuous Integration</a></li>
+</ul>
+    <h4>Miscellaneous</h4>
+    <ul>
+  <li class=""><a href="/docs/troubleshooting/">Troubleshooting</a></li>
+  <li class=""><a href="/docs/sites/">Sites using Jekyll</a></li>
+  <li class=""><a href="/docs/resources/">Resources</a></li>
+  <li class=""><a href="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</a></li>
+  <li class=""><a href="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</a></li>
+</ul>
+    <h4>Meta</h4>
+    <ul>
+  <li class=""><a href="/docs/contributing/">Contributing</a></li>
+  <li class=""><a href="/docs/maintaining/">Maintaining Jekyll</a></li>
+  <li class=""><a href="/docs/conduct/">Code of Conduct</a></li>
+  <li class=""><a href="/docs/history/">History</a></li>
+</ul>
+  </aside>
+</div>
+      <div class="clear"></div>
+    </div>
+  </section>
+  <footer>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
+      <p>The contents of this website are <br>© 2017 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
+    </div>
+    <div class="unit two-thirds align-right center-on-mobiles">
+      <p>
+        Proudly hosted by
+        <a href="https://github.com">
+          <img src="/img/footer-logo.png" width="100" height="30" alt="GitHub • Social coding">
+        </a>
+      </p>
+    </div>
+  </div>
+</footer>
+  <script>
+  var anchorForId = function (id) {
+    var anchor = document.createElement("a");
+    anchor.className = "header-link";
+    anchor.href      = "#" + id;
+    anchor.innerHTML = "<span class=\"sr-only\">Permalink</span><i class=\"fa fa-link\"></i>";
+    anchor.title = "Permalink";
+    return anchor;
+  };
+  var linkifyAnchors = function (level, containingElement) {
+    var headers = containingElement.getElementsByTagName("h" + level);
+    for (var h = 0; h < headers.length; h++) {
+      var header = headers[h];
+      if (typeof header.id !== "undefined" && header.id !== "") {
+        header.appendChild(anchorForId(header.id));
+      }
+    }
+  };
+  document.onreadystatechange = function () {
+    if (this.readyState === "complete") {
+      var contentBlock = document.getElementsByClassName("docs")[0] || document.getElementsByClassName("news")[0];
+      if (!contentBlock) {
+        return;
+      }
+      for (var level = 1; level <= 6; level++) {
+        linkifyAnchors(level, contentBlock);
+      }
+    }
+  };
+</script>
+  <!-- Gauges (http://gaug.es/) -->
+  <script>
+    var _gauges = _gauges || [];
+    (function() {
+      var t   = document.createElement('script');
+      t.type  = 'text/javascript';
+      t.async = true;
+      t.id    = 'gauges-tracker';
+      t.setAttribute('data-site-id', '503c5af6613f5d0f19000027');
+      t.src = '//secure.gaug.es/track.js';
+      var s = document.getElementsByTagName('script')[0];
+      s.parentNode.insertBefore(t, s);
+    })();
+  </script>
+  <!-- Google Analytics (http://google.com/analytics) -->
+  <script>
+    !function(j,e,k,y,l,L){j.GoogleAnalyticsObject=y,j[y]||(j[y]=function(){
+    (j[y].q=j[y].q||[]).push(arguments)}),j[y].l=+new Date,l=e.createElement(k),
+    L=e.getElementsByTagName(k)[0],l.src='//www.google-analytics.com/analytics.js',
+    L.parentNode.insertBefore(l,L)}(window,document,'script','ga');
+    ga('create', 'UA-50755011-1', 'jekyllrb.com');
+    ga('send', 'pageview');
+  </script>
+</body>
+</html>