RubyGems - jekyll-docs - Versions diffs - 3.8.5 → 3.9.0 - Mend

jekyll-docs 3.8.5 → 3.9.0

Files changed (143) hide show

checksums.yaml +4 -4
data/site/404.html +5 -4
data/site/docs/assets/index.html +22 -21
data/site/docs/code_of_conduct/index.html +8 -7
data/site/docs/collections/index.html +44 -43
data/site/docs/conduct/index.html +8 -7
data/site/docs/configuration/index.html +68 -67
data/site/docs/continuous-integration/buddyworks/index.html +10 -9
data/site/docs/continuous-integration/circleci/index.html +13 -12
data/site/docs/continuous-integration/index.html +8 -7
data/site/docs/continuous-integration/travis-ci/index.html +32 -31
data/site/docs/contributing/index.html +34 -33
data/site/docs/datafiles/index.html +24 -23
data/site/docs/deployment-methods/index.html +30 -29
data/site/docs/drafts/index.html +11 -10
data/site/docs/extras/index.html +9 -8
data/site/docs/frontmatter/index.html +8 -7
data/site/docs/github-pages/index.html +19 -18
data/site/docs/history/index.html +674 -645
data/site/docs/home/index.html +8 -7
data/site/docs/includes/index.html +44 -43
data/site/docs/installation/index.html +16 -15
data/site/docs/maintaining/affinity-team-captain/index.html +11 -10
data/site/docs/maintaining/avoiding-burnout/index.html +8 -7
data/site/docs/maintaining/becoming-a-maintainer/index.html +9 -8
data/site/docs/maintaining/index.html +8 -7
data/site/docs/maintaining/merging-a-pull-request/index.html +23 -22
data/site/docs/maintaining/releasing-a-new-version/index.html +19 -18
data/site/docs/maintaining/reviewing-a-pull-request/index.html +10 -9
data/site/docs/maintaining/special-labels/index.html +14 -13
data/site/docs/maintaining/triaging-an-issue/index.html +12 -11
data/site/docs/migrations/index.html +9 -8
data/site/docs/pages/index.html +12 -11
data/site/docs/pagination/index.html +25 -24
data/site/docs/permalinks/index.html +33 -32
data/site/docs/plugins/index.html +57 -56
data/site/docs/posts/index.html +37 -36
data/site/docs/quickstart/index.html +18 -17
data/site/docs/resources/index.html +9 -8
data/site/docs/sites/index.html +8 -7
data/site/docs/static-files/index.html +14 -13
data/site/docs/structure/index.html +8 -7
data/site/docs/support/index.html +9 -8
data/site/docs/templates/index.html +44 -43
data/site/docs/themes/index.html +63 -62
data/site/docs/troubleshooting/index.html +48 -47
data/site/docs/upgrading/0-to-2/index.html +51 -50
data/site/docs/upgrading/2-to-3/index.html +35 -34
data/site/docs/upgrading/index.html +11 -10
data/site/docs/usage/index.html +15 -14
data/site/docs/variables/index.html +8 -7
data/site/docs/windows/index.html +29 -28
data/site/feed.xml +45 -41
data/site/help/index.html +7 -6
data/site/index.html +7 -6
data/site/jekyllconf/index.html +9 -8
data/site/latest_version.txt +1 -1
data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +16 -10
data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +18 -12
data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +19 -13
data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +20 -14
data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +19 -13
data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +16 -10
data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +18 -12
data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +18 -12
data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +21 -15
data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +19 -13
data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +16 -10
data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +25 -19
data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +17 -11
data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +17 -11
data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +16 -10
data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +18 -12
data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +17 -11
data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +17 -11
data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +17 -11
data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +20 -14
data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +16 -10
data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +16 -10
data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +21 -15
data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +18 -12
data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +17 -11
data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +24 -18
data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +23 -17
data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +22 -16
data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +16 -10
data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +18 -12
data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +16 -10
data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +16 -10
data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +16 -10
data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +16 -10
data/site/news/2015/02/26/introducing-jekyll-talk/index.html +16 -10
data/site/news/2015/10/26/jekyll-3-0-released/index.html +21 -15
data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +20 -14
data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +18 -12
data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +21 -15
data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +21 -15
data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +17 -11
data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +18 -12
data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +16 -10
data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +17 -11
data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +17 -11
data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +16 -10
data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +22 -16
data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +17 -11
data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +17 -11
data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +16 -10
data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +20 -14
data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +17 -11
data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +16 -10
data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +42 -36
data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +17 -11
data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +18 -12
data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +17 -11
data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +21 -15
data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +26 -20
data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +25 -19
data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +18 -12
data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +21 -15
data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +17 -11
data/site/news/2017/10/19/diversity-open-source/index.html +18 -12
data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +18 -12
data/site/news/2018/01/02/jekyll-3-7-0-released/index.html +21 -15
data/site/news/2018/01/25/jekyll-3-7-2-released/index.html +26 -20
data/site/news/2018/02/19/meet-jekyll-s-new-lead-developer/index.html +16 -10
data/site/news/2018/02/24/jekyll-3-7-3-released/index.html +22 -16
data/site/news/2018/05/01/jekyll-3-8-1-released/index.html +19 -13
data/site/news/2018/05/19/jekyll-3-8-2-released/index.html +17 -11
data/site/news/2018/06/05/jekyll-3-8-3-released/index.html +19 -13
data/site/news/2019/07/02/jekyll-3-8-6-released/index.html +623 -0
data/site/news/index.html +263 -218
data/site/news/releases/index.html +261 -216
data/site/philosophy.html +1 -1
data/site/sitemap.xml +61 -57
data/site/team/index.html +7 -6
data/site/tutorials/convert-site-to-jekyll/index.html +97 -96
data/site/tutorials/custom-404-page/index.html +16 -15
data/site/tutorials/home/index.html +10 -9
data/site/tutorials/navigation/index.html +102 -101
data/site/tutorials/orderofinterpretation/index.html +32 -31
data/site/tutorials/using-jekyll-with-bundler/index.html +19 -18
data/site/tutorials/video-walkthroughs/index.html +8 -7
metadata +10 -24

data/site/docs/continuous-integration/circleci/index.html CHANGED

@@ -3,7 +3,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.8.5">
+  <meta name="generator" content="Jekyll v3.9.0">
   <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="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.5.0 -->
+  <!-- Begin Jekyll SEO tag v2.6.1 -->
 <title>CircleCI | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.8.5" />
+<meta name="generator" content="Jekyll v3.9.0" />
 <meta property="og:title" content="CircleCI" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Building, testing, and deploying your Jekyll-generated website can quickly be done with CircleCI, a continuous integration &amp; delivery tool. CircleCI supports GitHub and Bitbucket, and you can get started for free using an open-source or private repository." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/circleci/" />
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
 <meta property="og:type" content="article" />
-<meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
+<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
 <meta name="twitter:card" content="summary" />
+<meta property="twitter:title" content="CircleCI" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"CircleCI","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/continuous-integration/circleci/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/circleci/"},"description":"Building, testing, and deploying your Jekyll-generated website can quickly be done with CircleCI, a continuous integration &amp; delivery tool. CircleCI supports GitHub and Bitbucket, and you can get started for free using an open-source or private repository.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
+{"url":"https://jekyllrb.com/docs/continuous-integration/circleci/","headline":"CircleCI","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"Building, testing, and deploying your Jekyll-generated website can quickly be done with CircleCI, a continuous integration &amp; delivery tool. CircleCI supports GitHub and Bitbucket, and you can get started for free using an open-source or private repository.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/circleci/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
   <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
     <div class="meta hide-on-mobiles">
       <ul>
         <li>
-          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
+          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
         </li>
         <li>
           <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -309,7 +310,7 @@
 <h2 id="2-dependencies">2. Dependencies</h2>
-<p>The easiest way to manage dependencies for a Jekyll project (with or without CircleCI) is via a <a href="http://bundler.io/gemfile.html">Gemfile</a>. You’d want to have Jekyll, any Jekyll plugins, <a href="#html-proofer">HTML Proofer</a>, and any other gems that you are using in the <code class="highlighter-rouge">Gemfile</code>. Don’t forget to version <code class="highlighter-rouge">Gemfile.lock</code> as well. Here’s an example <code class="highlighter-rouge">Gemfile</code>:</p>
+<p>The easiest way to manage dependencies for a Jekyll project (with or without CircleCI) is via a <a href="http://bundler.io/gemfile.html">Gemfile</a>. You’d want to have Jekyll, any Jekyll plugins, <a href="#html-proofer">HTML Proofer</a>, and any other gems that you are using in the <code class="language-plaintext highlighter-rouge">Gemfile</code>. Don’t forget to version <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> as well. Here’s an example <code class="language-plaintext highlighter-rouge">Gemfile</code>:</p>
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="n">source</span> <span class="s1">'https://rubygems.org'</span>
@@ -319,11 +320,11 @@
 <span class="n">gem</span> <span class="s1">'html-proofer'</span>
 </code></pre></div></div>
-<p>CircleCI detects when <code class="highlighter-rouge">Gemfile</code> is present is will automatically run <code class="highlighter-rouge">bundle install</code> for you in the <code class="highlighter-rouge">dependencies</code> phase.</p>
+<p>CircleCI detects when <code class="language-plaintext highlighter-rouge">Gemfile</code> is present is will automatically run <code class="language-plaintext highlighter-rouge">bundle install</code> for you in the <code class="language-plaintext highlighter-rouge">dependencies</code> phase.</p>
 <h2 id="3-testing">3. Testing</h2>
-<p>The most basic test that can be run is simply seeing if <code class="highlighter-rouge">jekyll build</code> actually works. This is a blocker, a dependency if you will,  for other tests you might run on the generate site. So we’ll run Jekyll, via Bundler, in the <code class="highlighter-rouge">dependencies</code> phase.</p>
+<p>The most basic test that can be run is simply seeing if <code class="language-plaintext highlighter-rouge">jekyll build</code> actually works. This is a blocker, a dependency if you will,  for other tests you might run on the generate site. So we’ll run Jekyll, via Bundler, in the <code class="language-plaintext highlighter-rouge">dependencies</code> phase.</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">dependencies</span><span class="pi">:</span>
   <span class="na">post</span><span class="pi">:</span>
@@ -332,7 +333,7 @@
 <h3 id="html-proofer">HTML Proofer</h3>
-<p>With your site built, it’s useful to run tests to check for valid HTML, broken links, etc. There’s a few tools out there but <a href="https://github.com/gjtorikian/html-proofer">HTML Proofer</a> is popular amongst Jekyll users. We’ll run it in the <code class="highlighter-rouge">test</code> phase with a few preferred flags. Check out the <code class="highlighter-rouge">html-proofer</code> <a href="https://github.com/gjtorikian/html-proofer/blob/master/README.md#configuration">README</a> for all available flags, or run <code class="highlighter-rouge">htmlproofer --help</code> locally.</p>
+<p>With your site built, it’s useful to run tests to check for valid HTML, broken links, etc. There’s a few tools out there but <a href="https://github.com/gjtorikian/html-proofer">HTML Proofer</a> is popular amongst Jekyll users. We’ll run it in the <code class="language-plaintext highlighter-rouge">test</code> phase with a few preferred flags. Check out the <code class="language-plaintext highlighter-rouge">html-proofer</code> <a href="https://github.com/gjtorikian/html-proofer/blob/master/README.md#configuration">README</a> for all available flags, or run <code class="language-plaintext highlighter-rouge">htmlproofer --help</code> locally.</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">test</span><span class="pi">:</span>
   <span class="na">post</span><span class="pi">:</span>
@@ -341,7 +342,7 @@
 <h2 id="complete-example-circleyml-file">Complete Example circle.yml File</h2>
-<p>When you put it all together, here’s an example of what that <code class="highlighter-rouge">circle.yml</code> file could look like:</p>
+<p>When you put it all together, here’s an example of what that <code class="language-plaintext highlighter-rouge">circle.yml</code> file could look like:</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">machine</span><span class="pi">:</span>
   <span class="na">environment</span><span class="pi">:</span>
@@ -680,7 +681,7 @@
   <footer>
   <div class="grid">
     <div class="unit one-third center-on-mobiles">
-      <p>The contents of this website are <br />&copy;&nbsp;2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
+      <p>The contents of this website are <br />&copy;&nbsp;2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
     </div>
     <div class="unit two-thirds align-right center-on-mobiles">
       <p>

data/site/docs/continuous-integration/index.html CHANGED

@@ -3,7 +3,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.8.5">
+  <meta name="generator" content="Jekyll v3.9.0">
   <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="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.5.0 -->
+  <!-- Begin Jekyll SEO tag v2.6.1 -->
 <title>Continuous Integration | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.8.5" />
+<meta name="generator" content="Jekyll v3.9.0" />
 <meta property="og:title" content="Continuous Integration" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Continuous Integration (CI) enables you to publish your Jekyll generated website with confidence by automating the quality assurance and deployment processes. You can quickly get started using CI with one of the providers below:" />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/" />
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
 <meta property="og:type" content="article" />
-<meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
+<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
 <meta name="twitter:card" content="summary" />
+<meta property="twitter:title" content="Continuous Integration" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Continuous Integration","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/continuous-integration/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/"},"description":"Continuous Integration (CI) enables you to publish your Jekyll generated website with confidence by automating the quality assurance and deployment processes. You can quickly get started using CI with one of the providers below:","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
+{"url":"https://jekyllrb.com/docs/continuous-integration/","headline":"Continuous Integration","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"Continuous Integration (CI) enables you to publish your Jekyll generated website with confidence by automating the quality assurance and deployment processes. You can quickly get started using CI with one of the providers below:","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
   <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
     <div class="meta hide-on-mobiles">
       <ul>
         <li>
-          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
+          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
         </li>
         <li>
           <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -605,7 +606,7 @@
   <footer>
   <div class="grid">
     <div class="unit one-third center-on-mobiles">
-      <p>The contents of this website are <br />&copy;&nbsp;2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
+      <p>The contents of this website are <br />&copy;&nbsp;2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
     </div>
     <div class="unit two-thirds align-right center-on-mobiles">
       <p>

data/site/docs/continuous-integration/travis-ci/index.html CHANGED

@@ -3,7 +3,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.8.5">
+  <meta name="generator" content="Jekyll v3.9.0">
   <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="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.5.0 -->
+  <!-- Begin Jekyll SEO tag v2.6.1 -->
 <title>Travis CI | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.8.5" />
+<meta name="generator" content="Jekyll v3.9.0" />
 <meta property="og:title" content="Travis CI" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="You can easily test your website build against one or more versions of Ruby. The following guide will show you how to set up a free build environment on Travis, with GitHub integration for pull requests." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/travis-ci/" />
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
 <meta property="og:type" content="article" />
-<meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
+<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
 <meta name="twitter:card" content="summary" />
+<meta property="twitter:title" content="Travis CI" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Travis CI","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/continuous-integration/travis-ci/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/travis-ci/"},"description":"You can easily test your website build against one or more versions of Ruby. The following guide will show you how to set up a free build environment on Travis, with GitHub integration for pull requests.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
+{"url":"https://jekyllrb.com/docs/continuous-integration/travis-ci/","headline":"Travis CI","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"You can easily test your website build against one or more versions of Ruby. The following guide will show you how to set up a free build environment on Travis, with GitHub integration for pull requests.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/travis-ci/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
   <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
     <div class="meta hide-on-mobiles">
       <ul>
         <li>
-          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
+          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
         </li>
         <li>
           <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -307,21 +308,21 @@ The following guide will show you how to set up a free build environment on
   <li>Find the repository for which you’re interested in enabling builds.</li>
   <li>Flick the repository switch on so that it turns blue.</li>
   <li>Optionally configure the build by clicking on the gear icon. Further
-configuration happens via your <code class="highlighter-rouge">.travis.yml</code> file. More details below.</li>
+configuration happens via your <code class="language-plaintext highlighter-rouge">.travis.yml</code> file. More details below.</li>
 </ol>
 <h2 id="2-the-test-script">2. The Test Script</h2>
-<p>The simplest test script simply runs <code class="highlighter-rouge">jekyll build</code> and ensures that Jekyll
+<p>The simplest test script simply runs <code class="language-plaintext highlighter-rouge">jekyll build</code> and ensures that Jekyll
 doesn’t fail to build the site. It doesn’t check the resulting site, but it
 does ensure things are built properly.</p>
 <p>When testing Jekyll output, there is no better tool than <a href="https://github.com/gjtorikian/html-proofer">html-proofer</a>.
 This tool checks your resulting site to ensure all links and images exist.
-Utilize it either with the convenient <code class="highlighter-rouge">htmlproofer</code> command-line executable,
+Utilize it either with the convenient <code class="language-plaintext highlighter-rouge">htmlproofer</code> command-line executable,
 or write a Ruby script which utilizes the gem.</p>
-<p>Save the commands you want to run and succeed in a file: <code class="highlighter-rouge">./script/cibuild</code></p>
+<p>Save the commands you want to run and succeed in a file: <code class="language-plaintext highlighter-rouge">./script/cibuild</code></p>
 <h3 id="the-html-proofer-executable">The HTML Proofer Executable</h3>
@@ -333,8 +334,8 @@ bundle <span class="nb">exec </span>htmlproofer ./_site
 </code></pre></div></div>
 <p>Some options can be specified via command-line switches. Check out the
-<code class="highlighter-rouge">html-proofer</code> README for more information about these switches, or run
-<code class="highlighter-rouge">htmlproofer --help</code> locally.</p>
+<code class="language-plaintext highlighter-rouge">html-proofer</code> README for more information about these switches, or run
+<code class="language-plaintext highlighter-rouge">htmlproofer --help</code> locally.</p>
 <p>For example to avoid testing external sites, use this command:</p>
@@ -343,7 +344,7 @@ bundle <span class="nb">exec </span>htmlproofer ./_site
 <h3 id="the-html-proofer-library">The HTML Proofer Library</h3>
-<p>You can also invoke <code class="highlighter-rouge">html-proofer</code> in Ruby scripts (e.g. in a Rakefile):</p>
+<p>You can also invoke <code class="language-plaintext highlighter-rouge">html-proofer</code> in Ruby scripts (e.g. in a Rakefile):</p>
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">#!/usr/bin/env ruby</span>
@@ -351,15 +352,15 @@ bundle <span class="nb">exec </span>htmlproofer ./_site
 <span class="no">HTMLProofer</span><span class="p">.</span><span class="nf">check_directory</span><span class="p">(</span><span class="s2">"./_site"</span><span class="p">).</span><span class="nf">run</span>
 </code></pre></div></div>
-<p>Options are given as a second argument to <code class="highlighter-rouge">.new</code>, and are encoded in a
+<p>Options are given as a second argument to <code class="language-plaintext highlighter-rouge">.new</code>, and are encoded in a
 symbol-keyed Ruby Hash. For more information about the configuration options,
-check out <code class="highlighter-rouge">html-proofer</code>’s README file.</p>
+check out <code class="language-plaintext highlighter-rouge">html-proofer</code>’s README file.</p>
 <h2 id="3-configuring-your-travis-builds">3. Configuring Your Travis Builds</h2>
 <p>This file is used to configure your Travis builds. Because Jekyll is built
 with Ruby and requires RubyGems to install, we use the Ruby language build
-environment. Below is a sample <code class="highlighter-rouge">.travis.yml</code> file, followed by
+environment. Below is a sample <code class="language-plaintext highlighter-rouge">.travis.yml</code> file, followed by
 an explanation of each line.</p>
 <p><strong>Note:</strong> You will need a Gemfile as well, <a href="https://docs.travis-ci.com/user/languages/ruby/#Dependency-Management">Travis will automatically install</a> the dependencies based on the referenced gems:</p>
@@ -370,7 +371,7 @@ an explanation of each line.</p>
 <span class="n">gem</span> <span class="s2">"html-proofer"</span>
 </code></pre></div></div>
-<p>Your <code class="highlighter-rouge">.travis.yml</code> file should look like this:</p>
+<p>Your <code class="language-plaintext highlighter-rouge">.travis.yml</code> file should look like this:</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">language</span><span class="pi">:</span> <span class="s">ruby</span>
 <span class="na">rvm</span><span class="pi">:</span>
@@ -425,8 +426,8 @@ irrelevant.</p>
 </code></pre></div></div>
 <p>Travis allows you to run any arbitrary shell script to test your site. One
-convention is to put all scripts for your project in the <code class="highlighter-rouge">script</code>
-directory, and to call your test script <code class="highlighter-rouge">cibuild</code>. This line is completely
+convention is to put all scripts for your project in the <code class="language-plaintext highlighter-rouge">script</code>
+directory, and to call your test script <code class="language-plaintext highlighter-rouge">cibuild</code>. This line is completely
 customizable. If your script won’t change much, you can write your test
 incantation here directly:</p>
@@ -434,7 +435,7 @@ incantation here directly:</p>
 <span class="na">script</span><span class="pi">:</span> <span class="s">jekyll build &amp;&amp; htmlproofer ./_site</span>
 </code></pre></div></div>
-<p>The <code class="highlighter-rouge">script</code> directive can be absolutely any valid shell command.</p>
+<p>The <code class="language-plaintext highlighter-rouge">script</code> directive can be absolutely any valid shell command.</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># branch whitelist, only for GitHub Pages</span>
 <span class="na">branches</span><span class="pi">:</span>
@@ -446,13 +447,13 @@ incantation here directly:</p>
 <p>You want to ensure the Travis builds for your site are being run only on
 the branch or branches which contain your site. One means of ensuring this
 isolation is including a branch whitelist in your Travis configuration
-file. By specifying the <code class="highlighter-rouge">gh-pages</code> branch, you will ensure the associated
+file. By specifying the <code class="language-plaintext highlighter-rouge">gh-pages</code> branch, you will ensure the associated
 test script (discussed above) is only executed on site branches. If you use
 a pull request flow for proposing changes, you may wish to enforce a
 convention for your builds such that all branches containing edits are
-prefixed, exemplified above with the <code class="highlighter-rouge">/pages-(.*)/</code> regular expression.</p>
+prefixed, exemplified above with the <code class="language-plaintext highlighter-rouge">/pages-(.*)/</code> regular expression.</p>
-<p>The <code class="highlighter-rouge">branches</code> directive is completely optional. Travis will build from every
+<p>The <code class="language-plaintext highlighter-rouge">branches</code> directive is completely optional. Travis will build from every
 push to any branch of your repo if leave it out.</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">env</span><span class="pi">:</span>
@@ -460,11 +461,11 @@ push to any branch of your repo if leave it out.</p>
   <span class="pi">-</span> <span class="s">NOKOGIRI_USE_SYSTEM_LIBRARIES=true</span> <span class="c1"># speeds up installation of html-proofer</span>
 </code></pre></div></div>
-<p>Using <code class="highlighter-rouge">html-proofer</code>? You’ll want this environment variable. Nokogiri, used
+<p>Using <code class="language-plaintext highlighter-rouge">html-proofer</code>? You’ll want this environment variable. Nokogiri, used
 to parse HTML files in your compiled site, comes bundled with libraries
 which it must compile each time it is installed. Luckily, you can
 dramatically decrease the install time of Nokogiri by setting the
-environment variable <code class="highlighter-rouge">NOKOGIRI_USE_SYSTEM_LIBRARIES</code> to <code class="highlighter-rouge">true</code>.</p>
+environment variable <code class="language-plaintext highlighter-rouge">NOKOGIRI_USE_SYSTEM_LIBRARIES</code> to <code class="language-plaintext highlighter-rouge">true</code>.</p>
 <div class="note warning">
   <h5>Be sure to exclude <code>vendor</code> from your
@@ -476,11 +477,11 @@ environment variable <code class="highlighter-rouge">NOKOGIRI_USE_SYSTEM_LIBRARI
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="nv">vendor</span><span class="pi">]</span>
 </code></pre></div></div>
-<p>By default you should supply the <code class="highlighter-rouge">sudo: false</code> command to Travis. This command
+<p>By default you should supply the <code class="language-plaintext highlighter-rouge">sudo: false</code> command to Travis. This command
 explicitly tells Travis to run your build on Travis’s <a href="https://docs.travis-ci.com/user/workers/container-based-infrastructure/#Routing-your-build-to-container-based-infrastructure">container-based
  infrastructure</a>. Running on the container-based infrastructure can often times
 speed up your build. If you have any trouble with your build, or if your build
-does need <code class="highlighter-rouge">sudo</code> access, modify the line to <code class="highlighter-rouge">sudo: required</code>.</p>
+does need <code class="language-plaintext highlighter-rouge">sudo</code> access, modify the line to <code class="language-plaintext highlighter-rouge">sudo: required</code>.</p>
 <div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">sudo</span><span class="pi">:</span> <span class="no">false</span>
 </code></pre></div></div>
@@ -491,9 +492,9 @@ does need <code class="highlighter-rouge">sudo</code> access, modify the line to
 your Gemfile. Run bundle install elsewhere and add the updated Gemfile.lock
 to version control.”</em></p>
-<p><strong>Workaround:</strong> Either run <code class="highlighter-rouge">bundle install</code> locally and commit your changes to
-<code class="highlighter-rouge">Gemfile.lock</code>, or remove the <code class="highlighter-rouge">Gemfile.lock</code> file from your repository and add
-an entry in the <code class="highlighter-rouge">.gitignore</code> file to avoid it from being checked in again.</p>
+<p><strong>Workaround:</strong> Either run <code class="language-plaintext highlighter-rouge">bundle install</code> locally and commit your changes to
+<code class="language-plaintext highlighter-rouge">Gemfile.lock</code>, or remove the <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> file from your repository and add
+an entry in the <code class="language-plaintext highlighter-rouge">.gitignore</code> file to avoid it from being checked in again.</p>
 <h3 id="questions">Questions?</h3>
@@ -814,7 +815,7 @@ fix or <a href="https://jekyllrb.com/help/">ask for help</a> if you run into tro
   <footer>
   <div class="grid">
     <div class="unit one-third center-on-mobiles">
-      <p>The contents of this website are <br />&copy;&nbsp;2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
+      <p>The contents of this website are <br />&copy;&nbsp;2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT&nbsp;License</a>.</p>
     </div>
     <div class="unit two-thirds align-right center-on-mobiles">
       <p>

data/site/docs/contributing/index.html CHANGED

@@ -3,7 +3,7 @@
 <head>
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.8.5">
+  <meta name="generator" content="Jekyll v3.9.0">
   <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="preconnect" href="https://fonts.gstatic.com/" crossorigin>
@@ -11,9 +11,9 @@
   <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.5.0 -->
+  <!-- Begin Jekyll SEO tag v2.6.1 -->
 <title>Contributing | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.8.5" />
+<meta name="generator" content="Jekyll v3.9.0" />
 <meta property="og:title" content="Contributing" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/contributing/" />
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
 <meta property="og:type" content="article" />
-<meta property="article:published_time" content="2018-12-01T11:24:20-08:00" />
+<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
 <meta name="twitter:card" content="summary" />
+<meta property="twitter:title" content="Contributing" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Contributing","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/contributing/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/contributing/"},"description":"Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@type":"BlogPosting","@context":"http://schema.org"}</script>
+{"url":"https://jekyllrb.com/docs/contributing/","headline":"Contributing","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/contributing/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
   <!--[if lt IE 9]>
@@ -72,7 +73,7 @@
     <div class="meta hide-on-mobiles">
       <ul>
         <li>
-          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.8.5">v3.8.5</a>
+          <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
         </li>
         <li>
           <a href="https://github.com/jekyll/jekyll">GitHub</a>
@@ -310,7 +311,7 @@
   <li>Comment on some of the project’s <a href="https://github.com/jekyll/jekyll/issues">open issues</a>. Have you experienced the same problem? Know a work around? Do you have a suggestion for how the feature could be better?</li>
   <li>Read through <a href="https://jekyllrb.com/docs/home/">the documentation</a>, and click the “improve this page” button, any time you see something confusing, or have a suggestion for something that could be improved.</li>
   <li>Browse through <a href="https://talk.jekyllrb.com/">the Jekyll discussion forum</a>, and lend a hand answering questions. There’s a good chance you’ve already experienced what another user is experiencing.</li>
-  <li>Find <a href="https://github.com/jekyll/jekyll/issues">an open issue</a> (especially <a href="https://github.com/jekyll/jekyll/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted">those labeled <code class="highlighter-rouge">help-wanted</code></a>), and submit a proposed fix. If it’s your first pull request, we promise we won’t bite, and are glad to answer any questions.</li>
+  <li>Find <a href="https://github.com/jekyll/jekyll/issues">an open issue</a> (especially <a href="https://github.com/jekyll/jekyll/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted">those labeled <code class="language-plaintext highlighter-rouge">help-wanted</code></a>), and submit a proposed fix. If it’s your first pull request, we promise we won’t bite, and are glad to answer any questions.</li>
   <li>Help evaluate <a href="https://github.com/jekyll/jekyll/pulls">open pull requests</a>, by testing the changes locally and reviewing what’s proposed.</li>
 </ul>
@@ -338,7 +339,7 @@
 <p>Many small changes can be made entirely through the github.com web interface.</p>
 <ol>
-  <li>Navigate to the file within <a href="https://github.com/jekyll/jekyll"><code class="highlighter-rouge">jekyll/jekyll</code></a> that you’d like to edit.</li>
+  <li>Navigate to the file within <a href="https://github.com/jekyll/jekyll"><code class="language-plaintext highlighter-rouge">jekyll/jekyll</code></a> that you’d like to edit.</li>
   <li>Click the pencil icon in the top right corner to edit the file</li>
   <li>Make your proposed changes</li>
   <li>Click “Propose file change”</li>
@@ -352,13 +353,13 @@
 <h3 id="submitting-a-pull-request-via-git-command-line">Submitting a pull request via Git command line</h3>
 <ol>
-  <li>Fork the project by clicking “Fork” in the top right corner of <a href="https://github.com/jekyll/jekyll"><code class="highlighter-rouge">jekyll/jekyll</code></a>.</li>
-  <li>Clone the repository locally <code class="highlighter-rouge">git clone https://github.com/&lt;you-username&gt;/jekyll</code>.</li>
-  <li>Create a new, descriptively named branch to contain your change ( <code class="highlighter-rouge">git checkout -b my-awesome-feature</code> ).</li>
+  <li>Fork the project by clicking “Fork” in the top right corner of <a href="https://github.com/jekyll/jekyll"><code class="language-plaintext highlighter-rouge">jekyll/jekyll</code></a>.</li>
+  <li>Clone the repository locally <code class="language-plaintext highlighter-rouge">git clone https://github.com/&lt;you-username&gt;/jekyll</code>.</li>
+  <li>Create a new, descriptively named branch to contain your change ( <code class="language-plaintext highlighter-rouge">git checkout -b my-awesome-feature</code> ).</li>
   <li>Hack away, add tests. Not necessarily in that order.</li>
-  <li>Make sure everything still passes by running <code class="highlighter-rouge">script/cibuild</code> (see <a href="#running-tests-locally">the tests section</a> below)</li>
-  <li>Push the branch up ( <code class="highlighter-rouge">git push origin my-awesome-feature</code> ).</li>
-  <li>Create a pull request by visiting <code class="highlighter-rouge">https://github.com/&lt;your-username&gt;/jekyll</code> and following the instructions at the top of the screen.</li>
+  <li>Make sure everything still passes by running <code class="language-plaintext highlighter-rouge">script/cibuild</code> (see <a href="#running-tests-locally">the tests section</a> below)</li>
+  <li>Push the branch up ( <code class="language-plaintext highlighter-rouge">git push origin my-awesome-feature</code> ).</li>
+  <li>Create a pull request by visiting <code class="language-plaintext highlighter-rouge">https://github.com/&lt;your-username&gt;/jekyll</code> and following the instructions at the top of the screen.</li>
 </ol>
 <h2 id="proposing-updates-to-the-documentation">Proposing updates to the documentation</h2>
@@ -369,7 +370,7 @@
 <p>You can find the documentation for jekyllrb.com in the <a href="https://github.com/jekyll/jekyll/tree/master/docs">docs</a> directory. See the section above, <a href="#submitting-a-pull-request">submitting a pull request</a> for information on how to propose a change.</p>
-<p>One gotcha, all pull requests should be directed at the <code class="highlighter-rouge">master</code> branch (the default branch).</p>
+<p>One gotcha, all pull requests should be directed at the <code class="language-plaintext highlighter-rouge">master</code> branch (the default branch).</p>
 <h3 id="updating-fontawesome-iconset-for-jekyllrbcom">Updating FontAwesome iconset for jekyllrb.com</h3>
@@ -379,19 +380,19 @@
 <ol>
   <li>Go to <a href="https://icomoon.io/app/">https://icomoon.io/app/</a>.</li>
-  <li>Click <code class="highlighter-rouge">Import Icons</code> on the top-horizontal-bar and upload the existing <code class="highlighter-rouge">&lt;jekyll&gt;/docs/icomoon-selection.json</code>.</li>
-  <li>Click <code class="highlighter-rouge">Add Icons from Library..</code> further down on the page, and add ‘Font Awesome’.</li>
+  <li>Click <code class="language-plaintext highlighter-rouge">Import Icons</code> on the top-horizontal-bar and upload the existing <code class="language-plaintext highlighter-rouge">&lt;jekyll&gt;/docs/icomoon-selection.json</code>.</li>
+  <li>Click <code class="language-plaintext highlighter-rouge">Add Icons from Library..</code> further down on the page, and add ‘Font Awesome’.</li>
   <li>Select the required icon(s) from the Library (make sure its the ‘FontAwesome’ library instead of ‘IcoMoon-Free’ library).</li>
-  <li>Click <code class="highlighter-rouge">Generate Font</code> on the bottom-horizontal-bar.</li>
-  <li>Inspect the included icons and proceed by clicking <code class="highlighter-rouge">Download</code>.</li>
+  <li>Click <code class="language-plaintext highlighter-rouge">Generate Font</code> on the bottom-horizontal-bar.</li>
+  <li>Inspect the included icons and proceed by clicking <code class="language-plaintext highlighter-rouge">Download</code>.</li>
   <li>Extract the font files and adapt the CSS to the paths we use in Jekyll:
     <ul>
-      <li>Copy the entire <code class="highlighter-rouge">fonts</code> directory over and overwrite existing ones at <code class="highlighter-rouge">&lt;jekyll&gt;/docs/</code>.</li>
-      <li>Copy the contents of <code class="highlighter-rouge">selection.json</code> and overwrite existing content inside <code class="highlighter-rouge">&lt;jekyll&gt;/docs/icomoon-selection.json</code>.</li>
-      <li>Copy the entire <code class="highlighter-rouge">@font-face {}</code> declaration and only the <strong>new-icon(s)’ css declarations</strong> further below, to update the
-  <code class="highlighter-rouge">&lt;jekyll&gt;/docs/_sass/_font-awesome.scss</code> sass partial.</li>
-      <li>Fix paths in the <code class="highlighter-rouge">@font-face {}</code> declaration by adding <code class="highlighter-rouge">../</code> before <code class="highlighter-rouge">fonts/FontAwesome.*</code> like so:
-  <code class="highlighter-rouge">('../fonts/Fontawesome.woff?9h6hxj')</code>.</li>
+      <li>Copy the entire <code class="language-plaintext highlighter-rouge">fonts</code> directory over and overwrite existing ones at <code class="language-plaintext highlighter-rouge">&lt;jekyll&gt;/docs/</code>.</li>
+      <li>Copy the contents of <code class="language-plaintext highlighter-rouge">selection.json</code> and overwrite existing content inside <code class="language-plaintext highlighter-rouge">&lt;jekyll&gt;/docs/icomoon-selection.json</code>.</li>
+      <li>Copy the entire <code class="language-plaintext highlighter-rouge">@font-face {}</code> declaration and only the <strong>new-icon(s)’ css declarations</strong> further below, to update the
+  <code class="language-plaintext highlighter-rouge">&lt;jekyll&gt;/docs/_sass/_font-awesome.scss</code> sass partial.</li>
+      <li>Fix paths in the <code class="language-plaintext highlighter-rouge">@font-face {}</code> declaration by adding <code class="language-plaintext highlighter-rouge">../</code> before <code class="language-plaintext highlighter-rouge">fonts/FontAwesome.*</code> like so:
+  <code class="language-plaintext highlighter-rouge">('../fonts/Fontawesome.woff?9h6hxj')</code>.</li>
     </ul>
   </li>
 </ol>
@@ -410,13 +411,13 @@
 <h4 id="documentation">Documentation</h4>
-<p>If your contribution changes any Jekyll behavior, make sure to update the documentation. Documentation lives in the <code class="highlighter-rouge">docs/_docs</code> folder (spoiler alert: it’s a Jekyll site!). If the docs are missing information, please feel free to add it in. Great docs make a great project. Include changes to the documentation within your pull request, and once merged, <code class="highlighter-rouge">jekyllrb.com</code> will be updated.</p>
+<p>If your contribution changes any Jekyll behavior, make sure to update the documentation. Documentation lives in the <code class="language-plaintext highlighter-rouge">docs/_docs</code> folder (spoiler alert: it’s a Jekyll site!). If the docs are missing information, please feel free to add it in. Great docs make a great project. Include changes to the documentation within your pull request, and once merged, <code class="language-plaintext highlighter-rouge">jekyllrb.com</code> will be updated.</p>
 <h4 id="tests">Tests</h4>
 <ul>
   <li>
-    <p>If you’re creating a small fix or patch to an existing feature, a simple test is more than enough. You can usually copy/paste from an existing example in the <code class="highlighter-rouge">tests</code> folder, but if you need you can find out about our tests suites <a href="https://github.com/thoughtbot/shoulda/tree/master">Shoulda</a> and <a href="https://github.com/rspec/rspec-mocks">RSpec-Mocks</a>.</p>
+    <p>If you’re creating a small fix or patch to an existing feature, a simple test is more than enough. You can usually copy/paste from an existing example in the <code class="language-plaintext highlighter-rouge">tests</code> folder, but if you need you can find out about our tests suites <a href="https://github.com/thoughtbot/shoulda/tree/master">Shoulda</a> and <a href="https://github.com/rspec/rspec-mocks">RSpec-Mocks</a>.</p>
   </li>
   <li>
     <p>If it’s a brand new feature, create a new <a href="https://github.com/cucumber/cucumber/">Cucumber</a> feature, reusing existing steps where appropriate.</p>
@@ -427,13 +428,13 @@
 <ul>
   <li>
-    <p>Jekyll uses the <a href="https://github.com/bbatsov/rubocop">Rubocop</a> static analyzer to ensure that contributions follow the <a href="https://github.com/styleguide/ruby">GitHub Ruby Styleguide</a>. Please check your code using <code class="highlighter-rouge">script/fmt</code> and resolve any errors before pushing your branch.</p>
+    <p>Jekyll uses the <a href="https://github.com/bbatsov/rubocop">Rubocop</a> static analyzer to ensure that contributions follow the <a href="https://github.com/styleguide/ruby">GitHub Ruby Styleguide</a>. Please check your code using <code class="language-plaintext highlighter-rouge">script/fmt</code> and resolve any errors before pushing your branch.</p>
   </li>
   <li>
     <p>Don’t bump the Gem version in your pull request (if you don’t know what that means, you probably didn’t).</p>
   </li>
   <li>
-    <p>You can use the command <code class="highlighter-rouge">script/console</code> to start a REPL to explore the result of
+    <p>You can use the command <code class="language-plaintext highlighter-rouge">script/console</code> to start a REPL to explore the result of
 Jekyll’s methods. It also provides you with helpful methods to quickly create a
 site or configuration. <a href="https://github.com/jekyll/jekyll/blob/master/script/console">Feel free to check it out!</a></p>
   </li>
@@ -453,17 +454,17 @@ site or configuration. <a href="https://github.com/jekyll/jekyll/blob/master/scr
 <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>script/cibuild
 </code></pre></div></div>
-<p>If you are only updating a file in <code class="highlighter-rouge">test/</code>, you can use the command:</p>
+<p>If you are only updating a file in <code class="language-plaintext highlighter-rouge">test/</code>, you can use the command:</p>
 <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>script/test <span class="nb">test</span>/blah_test.rb
 </code></pre></div></div>
-<p>If you are only updating a <code class="highlighter-rouge">.feature</code> file, you can use the command:</p>
+<p>If you are only updating a <code class="language-plaintext highlighter-rouge">.feature</code> file, you can use the command:</p>
 <div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>script/cucumber features/blah.feature
 </code></pre></div></div>
-<p>Both <code class="highlighter-rouge">script/test</code> and <code class="highlighter-rouge">script/cucumber</code> can be run without arguments to
+<p>Both <code class="language-plaintext highlighter-rouge">script/test</code> and <code class="language-plaintext highlighter-rouge">script/cucumber</code> can be run without arguments to
 run its entire respective suite.</p>
 <h2 id="a-thank-you">A thank you</h2>
@@ -791,7 +792,7 @@ run its entire respective suite.</p>
   <footer>
   <div class="grid">
     <div class="unit one-third center-on-mobiles">
-      <p>The contents of this website are <br>© 2018 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
+      <p>The contents of this website are <br>© 2020 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>