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/structure/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>Directory structure | 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="Directory structure" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Jekyll is, at its core, a text transformation engine. The concept behind the system is this: you give it text written in your favorite markup language, be that Markdown, Textile, or just plain HTML, and it churns that through a layout or a series of layout files. Throughout that process you can tweak how you want the site URLs to look, what data gets displayed in the layout, and more. This is all done through editing text files; the static web site is the final product." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/structure/" />
 <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="Directory structure" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Directory structure","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/structure/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/structure/"},"description":"Jekyll is, at its core, a text transformation engine. The concept behind the system is this: you give it text written in your favorite markup language, be that Markdown, Textile, or just plain HTML, and it churns that through a layout or a series of layout files. Throughout that process you can tweak how you want the site URLs to look, what data gets displayed in the layout, and more. This is all done through editing text files; the static web site is the final product.","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/structure/","headline":"Directory structure","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":"Jekyll is, at its core, a text transformation engine. The concept behind the system is this: you give it text written in your favorite markup language, be that Markdown, Textile, or just plain HTML, and it churns that through a layout or a series of layout files. Throughout that process you can tweak how you want the site URLs to look, what data gets displayed in the layout, and more. This is all done through editing text files; the static web site is the final product.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/structure/"},"@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>
@@ -746,7 +747,7 @@ product.</p>
   <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/support/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>Support | 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="Support" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Getting Help" />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/support/" />
 <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="Support" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Support","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/support/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/support/"},"description":"Getting Help","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/support/","headline":"Support","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":"Getting Help","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/support/"},"@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>
@@ -311,7 +312,7 @@
 <h2 id="report-a-bug">Report a bug</h2>
 <ul>
-  <li>If you think you’ve found a bug within a Jekyll plugin, open an issue in that plugin’s repository — First <a href="https://rubygems.org/">look for the plugin on rubygems</a> then click on the <code class="highlighter-rouge">Homepage</code> link to access the plugin repository.</li>
+  <li>If you think you’ve found a bug within a Jekyll plugin, open an issue in that plugin’s repository — First <a href="https://rubygems.org/">look for the plugin on rubygems</a> then click on the <code class="language-plaintext highlighter-rouge">Homepage</code> link to access the plugin repository.</li>
   <li>If you think you’ve found a bug within Jekyll itself, <a href="https://github.com/jekyll/jekyll/issues/new">open an issue</a>.</li>
 </ul>
@@ -630,7 +631,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/templates/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>Templates | 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="Templates" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Jekyll uses the Liquid templating language to process templates. All of the standard Liquid tags and filters are supported. To make common tasks easier, Jekyll even adds a few handy filters and tags of its own, all of which you can find on this page. Jekyll even lets you come up with your own tags via plugins." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/templates/" />
 <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="Templates" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Templates","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/templates/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/templates/"},"description":"Jekyll uses the Liquid templating language to process templates. All of the standard Liquid tags and filters are supported. To make common tasks easier, Jekyll even adds a few handy filters and tags of its own, all of which you can find on this page. Jekyll even lets you come up with your own tags via plugins.","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/templates/","headline":"Templates","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":"Jekyll uses the Liquid templating language to process templates. All of the standard Liquid tags and filters are supported. To make common tasks easier, Jekyll even adds a few handy filters and tags of its own, all of which you can find on this page. Jekyll even lets you come up with your own tags via plugins.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/templates/"},"@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>
@@ -738,18 +739,18 @@ you come up with your own tags via plugins.</p>
 </table>
 </div>
-<h3 id="options-for-the-slugify-filter">Options for the <code class="highlighter-rouge">slugify</code> filter</h3>
+<h3 id="options-for-the-slugify-filter">Options for the <code class="language-plaintext highlighter-rouge">slugify</code> filter</h3>
-<p>The <code class="highlighter-rouge">slugify</code> filter accepts an option, each specifying what to filter.
-The default is <code class="highlighter-rouge">default</code>. They are as follows (with what they filter):</p>
+<p>The <code class="language-plaintext highlighter-rouge">slugify</code> filter accepts an option, each specifying what to filter.
+The default is <code class="language-plaintext highlighter-rouge">default</code>. They are as follows (with what they filter):</p>
 <ul>
-  <li><code class="highlighter-rouge">none</code>: no characters</li>
-  <li><code class="highlighter-rouge">raw</code>: spaces</li>
-  <li><code class="highlighter-rouge">default</code>: spaces and non-alphanumeric characters</li>
-  <li><code class="highlighter-rouge">pretty</code>: spaces and non-alphanumeric characters except for <code class="highlighter-rouge">._~!$&amp;'()+,;=@</code></li>
-  <li><code class="highlighter-rouge">ascii</code>: spaces, non-alphanumeric, and non-ASCII characters</li>
-  <li><code class="highlighter-rouge">latin</code>: like <code class="highlighter-rouge">default</code>, except Latin characters are first transliterated (e.g. <code class="highlighter-rouge">àèïòü</code> to <code class="highlighter-rouge">aeiou</code>)<span class="version-badge" title="This feature is available starting version 3.7.0">3.7.0</span>
+  <li><code class="language-plaintext highlighter-rouge">none</code>: no characters</li>
+  <li><code class="language-plaintext highlighter-rouge">raw</code>: spaces</li>
+  <li><code class="language-plaintext highlighter-rouge">default</code>: spaces and non-alphanumeric characters</li>
+  <li><code class="language-plaintext highlighter-rouge">pretty</code>: spaces and non-alphanumeric characters except for <code class="language-plaintext highlighter-rouge">._~!$&amp;'()+,;=@</code></li>
+  <li><code class="language-plaintext highlighter-rouge">ascii</code>: spaces, non-alphanumeric, and non-ASCII characters</li>
+  <li><code class="language-plaintext highlighter-rouge">latin</code>: like <code class="language-plaintext highlighter-rouge">default</code>, except Latin characters are first transliterated (e.g. <code class="language-plaintext highlighter-rouge">àèïòü</code> to <code class="language-plaintext highlighter-rouge">aeiou</code>)<span class="version-badge" title="This feature is available starting version 3.7.0">3.7.0</span>
     <h2 id="tags">Tags</h2>
   </li>
   <li><a href="#includes">Includes</a></li>
@@ -760,12 +761,12 @@ The default is <code class="highlighter-rouge">default</code>. They are as follo
 <h3 id="includes">Includes</h3>
-<p>If you have small page snippets that you want to include in multiple places on your site, save the snippets as <em>include files</em> and insert them where required, by using the <code class="highlighter-rouge">include</code> tag:</p>
+<p>If you have small page snippets that you want to include in multiple places on your site, save the snippets as <em>include files</em> and insert them where required, by using the <code class="language-plaintext highlighter-rouge">include</code> tag:</p>
-<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span><span class="na">footer</span><span class="p">.</span><span class="na">html</span><span class="w"> </span><span class="p">%}</span>
+<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span>footer.html<span class="w"> </span><span class="p">%}</span>
 </code></pre></div></div>
-<p>Jekyll expects all <em>include files</em> to be placed in an <code class="highlighter-rouge">_includes</code> directory at the root of your source directory. In the above example, this will embed the contents of <code class="highlighter-rouge">_includes/footer.html</code> into the calling file.</p>
+<p>Jekyll expects all <em>include files</em> to be placed in an <code class="language-plaintext highlighter-rouge">_includes</code> directory at the root of your source directory. In the above example, this will embed the contents of <code class="language-plaintext highlighter-rouge">_includes/footer.html</code> into the calling file.</p>
 <p>For more advanced information on using includes, see <a href="../includes">Includes</a>.</p>
@@ -773,13 +774,13 @@ The default is <code class="highlighter-rouge">default</code>. They are as follo
 <p>Jekyll has built in support for syntax highlighting of over 60 languages
 thanks to <a href="http://rouge.jneen.net">Rouge</a>. Rouge is the default highlighter
-in Jekyll 3 and above. To use it in Jekyll 2, set <code class="highlighter-rouge">highlighter</code> to <code class="highlighter-rouge">rouge</code>
-and ensure the <code class="highlighter-rouge">rouge</code> gem is installed properly.</p>
+in Jekyll 3 and above. To use it in Jekyll 2, set <code class="language-plaintext highlighter-rouge">highlighter</code> to <code class="language-plaintext highlighter-rouge">rouge</code>
+and ensure the <code class="language-plaintext highlighter-rouge">rouge</code> gem is installed properly.</p>
 <p>Alternatively, you can use <a href="http://pygments.org">Pygments</a> to highlight
 your code snippets. To use Pygments, you must have Python installed on your
-system, have the <code class="highlighter-rouge">pygments.rb</code> gem installed and set <code class="highlighter-rouge">highlighter</code> to
-<code class="highlighter-rouge">pygments</code> in your site’s configuration file. Pygments supports <a href="http://pygments.org/languages/">over 100
+system, have the <code class="language-plaintext highlighter-rouge">pygments.rb</code> gem installed and set <code class="language-plaintext highlighter-rouge">highlighter</code> to
+<code class="language-plaintext highlighter-rouge">pygments</code> in your site’s configuration file. Pygments supports <a href="http://pygments.org/languages/">over 100
 languages</a></p>
 <p>To render a code block with syntax highlighting, surround your code as follows:</p>
@@ -791,7 +792,7 @@ end
 <span class="p">{%</span><span class="w"> </span><span class="nt">endhighlight</span><span class="w"> </span><span class="p">%}</span>
 </code></pre></div></div>
-<p>The argument to the <code class="highlighter-rouge">highlight</code> tag (<code class="highlighter-rouge">ruby</code> in the example above) is the
+<p>The argument to the <code class="language-plaintext highlighter-rouge">highlight</code> tag (<code class="language-plaintext highlighter-rouge">ruby</code> in the example above) is the
 language identifier. To find the appropriate identifier to use for the language
 you want to highlight, look for the “short name” on the <a href="https://github.com/jayferd/rouge/wiki/List-of-supported-languages-and-lexers">Rouge
 wiki</a>
@@ -806,8 +807,8 @@ or the <a href="http://pygments.org/docs/lexers/">Pygments’ Lexers page</a>.</
 <h4 id="line-numbers">Line numbers</h4>
-<p>There is a second argument to <code class="highlighter-rouge">highlight</code> called <code class="highlighter-rouge">linenos</code> that is optional.
-Including the <code class="highlighter-rouge">linenos</code> argument will force the highlighted code to include line
+<p>There is a second argument to <code class="language-plaintext highlighter-rouge">highlight</code> called <code class="language-plaintext highlighter-rouge">linenos</code> that is optional.
+Including the <code class="language-plaintext highlighter-rouge">linenos</code> argument will force the highlighted code to include line
 numbers. For instance, the following code block would include line numbers next
 to each line:</p>
@@ -824,61 +825,61 @@ end
 stylesheet. For an example stylesheet you can look at
 <a href="https://github.com/mojombo/tpw/tree/master/css/syntax.css">syntax.css</a>. These
 are the same styles as used by GitHub and you are free to use them for your own
-site. If you use <code class="highlighter-rouge">linenos</code>, you might want to include an additional CSS class
-definition for the <code class="highlighter-rouge">.lineno</code> class in <code class="highlighter-rouge">syntax.css</code> to distinguish the line
+site. If you use <code class="language-plaintext highlighter-rouge">linenos</code>, you might want to include an additional CSS class
+definition for the <code class="language-plaintext highlighter-rouge">.lineno</code> class in <code class="language-plaintext highlighter-rouge">syntax.css</code> to distinguish the line
 numbers from the highlighted code.</p>
 <h2 id="links">Links</h2>
 <h3 id="link">Linking to pages</h3>
-<p>To link to a post, a page, collection item, or file, the <code class="highlighter-rouge">link</code> tag will generate the correct permalink URL for the path you specify. For example, if you use the <code class="highlighter-rouge">link</code> tag to link to <code class="highlighter-rouge">mypage.html</code>, even if you change your permalink style to include the file extension or omit it, the URL formed by the <code class="highlighter-rouge">link</code> tag will always be valid.</p>
+<p>To link to a post, a page, collection item, or file, the <code class="language-plaintext highlighter-rouge">link</code> tag will generate the correct permalink URL for the path you specify. For example, if you use the <code class="language-plaintext highlighter-rouge">link</code> tag to link to <code class="language-plaintext highlighter-rouge">mypage.html</code>, even if you change your permalink style to include the file extension or omit it, the URL formed by the <code class="language-plaintext highlighter-rouge">link</code> tag will always be valid.</p>
-<p>You must include the file’s original extension when using the <code class="highlighter-rouge">link</code> tag. Here are some examples:</p>
+<p>You must include the file’s original extension when using the <code class="language-plaintext highlighter-rouge">link</code> tag. Here are some examples:</p>
 <div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_collection/name-of-document.md<span class="w"> </span><span class="p">%}</span>
-<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_posts/<span class="mi">2016</span>-<span class="mi">07</span>-<span class="mi">26</span>-name-of-post.md<span class="w"> </span><span class="p">%}</span>
+<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_posts/2016-07-26-name-of-post.md<span class="w"> </span><span class="p">%}</span>
 <span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>news/index.html<span class="w"> </span><span class="p">%}</span>
 <span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>/assets/files/doc.pdf<span class="w"> </span><span class="p">%}</span>
 </code></pre></div></div>
-<p>You can also use the <code class="highlighter-rouge">link</code> tag to create a link in Markdown as follows:</p>
+<p>You can also use the <code class="language-plaintext highlighter-rouge">link</code> tag to create a link in Markdown as follows:</p>
 <div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>[Link to a document](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_collection/name-of-document.md<span class="w"> </span><span class="p">%}</span>)
-[Link to a post](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_posts/<span class="mi">2016</span>-<span class="mi">07</span>-<span class="mi">26</span>-name-of-post.md<span class="w"> </span><span class="p">%}</span>)
+[Link to a post](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>_posts/2016-07-26-name-of-post.md<span class="w"> </span><span class="p">%}</span>)
 [Link to a page](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>news/index.html<span class="w"> </span><span class="p">%}</span>)
 [Link to a file](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">link</span><span class="w"> </span>/assets/files/doc.pdf<span class="w"> </span><span class="p">%}</span>)
 </code></pre></div></div>
-<p>(Including <code class="highlighter-rouge">{{ site.baseurl }}</code> is optional — it depends on whether you want to preface the page URL with the <code class="highlighter-rouge">baseurl</code> value.)</p>
+<p>(Including <code class="language-plaintext highlighter-rouge">{{ site.baseurl }}</code> is optional — it depends on whether you want to preface the page URL with the <code class="language-plaintext highlighter-rouge">baseurl</code> value.)</p>
 <p>The path to the post, page, or collection is defined as the path relative to the root directory (where your config file is) to the file, not the path from your existing page to the other page.</p>
-<p>For example, suppose you’re creating a link in <code class="highlighter-rouge">page_a.md</code> (stored in <code class="highlighter-rouge">pages/folder1/folder2</code>) to <code class="highlighter-rouge">page_b.md</code> (stored in  <code class="highlighter-rouge">pages/folder1</code>). Your path in the link would not be <code class="highlighter-rouge">../page_b.html</code>. Instead, it would be <code class="highlighter-rouge">/pages/folder1/page_b.md</code>.</p>
+<p>For example, suppose you’re creating a link in <code class="language-plaintext highlighter-rouge">page_a.md</code> (stored in <code class="language-plaintext highlighter-rouge">pages/folder1/folder2</code>) to <code class="language-plaintext highlighter-rouge">page_b.md</code> (stored in  <code class="language-plaintext highlighter-rouge">pages/folder1</code>). Your path in the link would not be <code class="language-plaintext highlighter-rouge">../page_b.html</code>. Instead, it would be <code class="language-plaintext highlighter-rouge">/pages/folder1/page_b.md</code>.</p>
-<p>If you’re unsure of the path, add <code class="highlighter-rouge">{{ page.path }}</code> to the page and it will display the path.</p>
+<p>If you’re unsure of the path, add <code class="language-plaintext highlighter-rouge">{{ page.path }}</code> to the page and it will display the path.</p>
-<p>One major benefit of using the <code class="highlighter-rouge">link</code> or <code class="highlighter-rouge">post_url</code> tag is link validation. If the link doesn’t exist, Jekyll won’t build your site. This is a good thing, as it will alert you to a broken link so you can fix it (rather than allowing you to build and deploy a site with broken links).</p>
+<p>One major benefit of using the <code class="language-plaintext highlighter-rouge">link</code> or <code class="language-plaintext highlighter-rouge">post_url</code> tag is link validation. If the link doesn’t exist, Jekyll won’t build your site. This is a good thing, as it will alert you to a broken link so you can fix it (rather than allowing you to build and deploy a site with broken links).</p>
-<p>Note you cannot add filters to <code class="highlighter-rouge">link</code> tags. For example, you cannot append a string using Liquid filters, such as <code class="highlighter-rouge">{% link mypage.html | append: "#section1" %} </code>. To link to sections on a page, you will need to use regular HTML or Markdown linking techniques.</p>
+<p>Note you cannot add filters to <code class="language-plaintext highlighter-rouge">link</code> tags. For example, you cannot append a string using Liquid filters, such as <code class="language-plaintext highlighter-rouge">{% link mypage.html | append: "#section1" %} </code>. To link to sections on a page, you will need to use regular HTML or Markdown linking techniques.</p>
 <h3 id="linking-to-posts">Linking to posts</h3>
-<p>If you want to include a link to a post on your site, the <code class="highlighter-rouge">post_url</code> tag will generate the correct permalink URL for the post you specify.</p>
+<p>If you want to include a link to a post on your site, the <code class="language-plaintext highlighter-rouge">post_url</code> tag will generate the correct permalink URL for the post you specify.</p>
-<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span><span class="mi">2010</span>-<span class="mi">07</span>-<span class="mi">21</span>-name-of-post<span class="w"> </span><span class="p">%}</span>
+<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span><span class="mi">2010</span><span class="o">-</span><span class="mi">07</span><span class="o">-</span><span class="mi">21</span><span class="o">-</span>name-of-post<span class="w"> </span><span class="p">%}</span>
 </code></pre></div></div>
 <p>If you organize your posts in subdirectories, you need to include subdirectory path to the post:</p>
-<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span>/subdir/<span class="mi">2010</span>-<span class="mi">07</span>-<span class="mi">21</span>-name-of-post<span class="w"> </span><span class="p">%}</span>
+<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span>/subdir/2010-07-21-name-of-post<span class="w"> </span><span class="p">%}</span>
 </code></pre></div></div>
-<p>There is no need to include the file extension when using the <code class="highlighter-rouge">post_url</code> tag.</p>
+<p>There is no need to include the file extension when using the <code class="language-plaintext highlighter-rouge">post_url</code> tag.</p>
 <p>You can also use this tag to create a link to a post in Markdown as follows:</p>
-<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>[Name of Link](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span><span class="mi">2010</span>-<span class="mi">07</span>-<span class="mi">21</span>-name-of-post<span class="w"> </span><span class="p">%}</span>)
+<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>[Name of Link](<span class="p">{{</span><span class="w"> </span><span class="nv">site</span><span class="p">.</span><span class="nv">baseurl</span><span class="w"> </span><span class="p">}}{%</span><span class="w"> </span><span class="nt">post_url</span><span class="w"> </span><span class="mi">2010</span><span class="o">-</span><span class="mi">07</span><span class="o">-</span><span class="mi">21</span><span class="o">-</span>name-of-post<span class="w"> </span><span class="p">%}</span>)
 </code></pre></div></div>
@@ -1158,7 +1159,7 @@ numbers from the highlighted code.</p>
   <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/themes/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>Themes | 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="Themes" />
 <meta property="og:locale" content="en_US" />
 <meta name="description" content="Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content." />
@@ -22,12 +22,13 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/themes/" />
 <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="Themes" />
 <meta name="twitter:site" content="@jekyllrb" />
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
 <script type="application/ld+json">
-{"headline":"Themes","dateModified":"2018-12-01T11:24:20-08:00","datePublished":"2018-12-01T11:24:20-08:00","url":"https://jekyllrb.com/docs/themes/","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/themes/"},"description":"Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content.","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/themes/","headline":"Themes","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":"Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site’s presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site’s content.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/themes/"},"@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>
@@ -298,13 +299,13 @@
 <h2 id="understanding-gem-based-themes">Understanding gem-based themes</h2>
-<p>When you <a href="/docs/quickstart">create a new Jekyll site</a> (by running the <code class="highlighter-rouge">jekyll new &lt;PATH&gt;</code> command), Jekyll installs a site that uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>.</p>
+<p>When you <a href="/docs/quickstart">create a new Jekyll site</a> (by running the <code class="language-plaintext highlighter-rouge">jekyll new &lt;PATH&gt;</code> command), Jekyll installs a site that uses a gem-based theme called <a href="https://github.com/jekyll/minima">Minima</a>.</p>
-<p>With gem-based themes, some of the site’s directories (such as the <code class="highlighter-rouge">assets</code>, <code class="highlighter-rouge">_layouts</code>, <code class="highlighter-rouge">_includes</code>, and <code class="highlighter-rouge">_sass</code> directories) are stored in the theme’s gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll’s build process.</p>
+<p>With gem-based themes, some of the site’s directories (such as the <code class="language-plaintext highlighter-rouge">assets</code>, <code class="language-plaintext highlighter-rouge">_layouts</code>, <code class="language-plaintext highlighter-rouge">_includes</code>, and <code class="language-plaintext highlighter-rouge">_sass</code> directories) are stored in the theme’s gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll’s build process.</p>
 <p>In the case of Minima, you see only the following files in your Jekyll site directory:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>├── Gemfile
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>├── Gemfile
 ├── Gemfile.lock
 ├── _config.yml
 ├── _posts
@@ -313,11 +314,11 @@
 └── index.md
 </code></pre></div></div>
-<p>The <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">Gemfile.lock</code> files are used by Bundler to keep track of the required gems and gem versions you need to build your Jekyll site.</p>
+<p>The <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">Gemfile.lock</code> files are used by Bundler to keep track of the required gems and gem versions you need to build your Jekyll site.</p>
 <p>Gem-based themes make it easy for theme developers to make updates available to anyone who has the theme gem. When there’s an update, theme developers push the update to RubyGems.</p>
-<p>If you have the theme gem, you can (if you desire) run <code class="highlighter-rouge">bundle update</code> to update all gems in your project. Or you can run <code class="highlighter-rouge">bundle update &lt;THEME&gt;</code>, replacing <code class="highlighter-rouge">&lt;THEME&gt;</code> with the theme name, such as <code class="highlighter-rouge">minima</code>, to just update the theme gem. Any new files or updates the theme developer has made (such as to stylesheets or includes) will be pulled into your project automatically.</p>
+<p>If you have the theme gem, you can (if you desire) run <code class="language-plaintext highlighter-rouge">bundle update</code> to update all gems in your project. Or you can run <code class="language-plaintext highlighter-rouge">bundle update &lt;THEME&gt;</code>, replacing <code class="language-plaintext highlighter-rouge">&lt;THEME&gt;</code> with the theme name, such as <code class="language-plaintext highlighter-rouge">minima</code>, to just update the theme gem. Any new files or updates the theme developer has made (such as to stylesheets or includes) will be pulled into your project automatically.</p>
 <p>The goal of gem-based themes is to allow you to get all the benefits of a robust, continually updated theme without having all the theme’s files getting in your way and over-complicating what might be your primary focus: creating content.</p>
@@ -325,31 +326,31 @@
 <p>Jekyll themes set default layouts, includes, and stylesheets. However, you can override any of the theme defaults with your own site content.</p>
-<p>To replace layouts or includes in your theme, make a copy in your <code class="highlighter-rouge">_layouts</code> or <code class="highlighter-rouge">_includes</code> directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.</p>
+<p>To replace layouts or includes in your theme, make a copy in your <code class="language-plaintext highlighter-rouge">_layouts</code> or <code class="language-plaintext highlighter-rouge">_includes</code> directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.</p>
-<p>For example, if your selected theme has a <code class="highlighter-rouge">page</code> layout, you can override the theme’s layout by creating your own <code class="highlighter-rouge">page</code> layout in the <code class="highlighter-rouge">_layouts</code> directory (that is, <code class="highlighter-rouge">_layouts/page.html</code>).</p>
+<p>For example, if your selected theme has a <code class="language-plaintext highlighter-rouge">page</code> layout, you can override the theme’s layout by creating your own <code class="language-plaintext highlighter-rouge">page</code> layout in the <code class="language-plaintext highlighter-rouge">_layouts</code> directory (that is, <code class="language-plaintext highlighter-rouge">_layouts/page.html</code>).</p>
 <p>To locate a theme’s files on your computer:</p>
 <ol>
   <li>
-    <p>Run <code class="highlighter-rouge">bundle show</code> followed by the name of the theme’s gem, e.g., <code class="highlighter-rouge">bundle show minima</code> for Jekyll’s default theme.</p>
+    <p>Run <code class="language-plaintext highlighter-rouge">bundle show</code> followed by the name of the theme’s gem, e.g., <code class="language-plaintext highlighter-rouge">bundle show minima</code> for Jekyll’s default theme.</p>
-    <p>This returns the location of the gem-based theme files. For example, the Minima theme’s files might be located in <code class="highlighter-rouge">/usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0</code> on macOS.</p>
+    <p>This returns the location of the gem-based theme files. For example, the Minima theme’s files might be located in <code class="language-plaintext highlighter-rouge">/usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0</code> on macOS.</p>
   </li>
   <li>
     <p>Open the theme’s directory in Finder or Explorer:</p>
     <div class="language-sh highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code><span class="c"># On MacOS</span>
-open <span class="k">$(</span>bundle show minima<span class="k">)</span>
+open <span class="si">$(</span>bundle show minima<span class="si">)</span>
 <span class="c"># On Windows</span>
 explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
 </code></pre></div>    </div>
     <p>A Finder or Explorer window opens showing the theme’s files and directories. The Minima theme gem contains these files:</p>
-    <div class="highlighter-rouge">
+    <div class="language-plaintext highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code> ├── LICENSE.txt
  ├── README.md
  ├── _includes
@@ -381,17 +382,17 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
 <p>With a clear understanding of the theme’s files, you can now override any theme file by creating a similarly named file in your Jekyll site directory.</p>
-<p>Let’s say, for a second example, you want to override Minima’s footer. In your Jekyll site, create an <code class="highlighter-rouge">_includes</code> folder and add a file in it called <code class="highlighter-rouge">footer.html</code>. Jekyll will now use your site’s <code class="highlighter-rouge">footer.html</code> file instead of the <code class="highlighter-rouge">footer.html</code> file from the Minima theme gem.</p>
+<p>Let’s say, for a second example, you want to override Minima’s footer. In your Jekyll site, create an <code class="language-plaintext highlighter-rouge">_includes</code> folder and add a file in it called <code class="language-plaintext highlighter-rouge">footer.html</code>. Jekyll will now use your site’s <code class="language-plaintext highlighter-rouge">footer.html</code> file instead of the <code class="language-plaintext highlighter-rouge">footer.html</code> file from the Minima theme gem.</p>
-<p>To modify any stylesheet you must take the extra step of also copying the main sass file (<code class="highlighter-rouge">_sass/minima.scss</code> in the Minima theme) into the <code class="highlighter-rouge">_sass</code> directory in your site’s source.</p>
+<p>To modify any stylesheet you must take the extra step of also copying the main sass file (<code class="language-plaintext highlighter-rouge">_sass/minima.scss</code> in the Minima theme) into the <code class="language-plaintext highlighter-rouge">_sass</code> directory in your site’s source.</p>
 <p>Jekyll will look first to your site’s content before looking to the theme’s defaults for any requested file in the following folders:</p>
 <ul>
-  <li><code class="highlighter-rouge">/assets</code></li>
-  <li><code class="highlighter-rouge">/_layouts</code></li>
-  <li><code class="highlighter-rouge">/_includes</code></li>
-  <li><code class="highlighter-rouge">/_sass</code></li>
+  <li><code class="language-plaintext highlighter-rouge">/assets</code></li>
+  <li><code class="language-plaintext highlighter-rouge">/_layouts</code></li>
+  <li><code class="language-plaintext highlighter-rouge">/_includes</code></li>
+  <li><code class="language-plaintext highlighter-rouge">/_sass</code></li>
 </ul>
 <p>Note that making copies of theme files will prevent you from receiving any theme updates on those files. An alternative, to continue getting theme updates on all stylesheets, is to use higher specificity CSS selectors in your own additional, originally named CSS files.</p>
@@ -402,17 +403,17 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
 <p>Suppose you want to get rid of the gem-based theme and convert it to a regular theme, where all files are present in your Jekyll site directory, with nothing stored in the theme gem.</p>
-<p>To do this, copy the files from the theme gem’s directory into your Jekyll site directory. (For example, copy them to <code class="highlighter-rouge">/myblog</code> if you created your Jekyll site at <code class="highlighter-rouge">/myblog</code>. See the previous section for details.)</p>
+<p>To do this, copy the files from the theme gem’s directory into your Jekyll site directory. (For example, copy them to <code class="language-plaintext highlighter-rouge">/myblog</code> if you created your Jekyll site at <code class="language-plaintext highlighter-rouge">/myblog</code>. See the previous section for details.)</p>
 <p>Then you must tell Jekyll about the plugins that were referenced by the theme. You can find these plugins in the theme’s gemspec file as runtime dependencies. If you were converting the Minima theme, for example, you might see:</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spec.add_runtime_dependency "jekyll-feed", "~&gt; 0.9"
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>spec.add_runtime_dependency "jekyll-feed", "~&gt; 0.9"
 spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
 </code></pre></div></div>
-<p>You should include these references in the <code class="highlighter-rouge">Gemfile</code> in one of two ways.</p>
+<p>You should include these references in the <code class="language-plaintext highlighter-rouge">Gemfile</code> in one of two ways.</p>
-<p>You could list them individually in both <code class="highlighter-rouge">Gemfile</code> and <code class="highlighter-rouge">_config.yml</code>.</p>
+<p>You could list them individually in both <code class="language-plaintext highlighter-rouge">Gemfile</code> and <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
@@ -427,7 +428,7 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
   <span class="pi">-</span> <span class="s">jekyll-seo-tag</span>
 </code></pre></div></div>
-<p>Or you could list them explicitly as Jekyll plugins in your Gemfile, and not update <code class="highlighter-rouge">_config.yml</code>, like this:</p>
+<p>Or you could list them explicitly as Jekyll plugins in your Gemfile, and not update <code class="language-plaintext highlighter-rouge">_config.yml</code>, like this:</p>
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
@@ -437,43 +438,43 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
 <span class="k">end</span>
 </code></pre></div></div>
-<p>Either way, don’t forget to <code class="highlighter-rouge">bundle update</code>.</p>
+<p>Either way, don’t forget to <code class="language-plaintext highlighter-rouge">bundle update</code>.</p>
-<p>However, if you’re publishing on GitHub Pages you should update only your <code class="highlighter-rouge">_config.yml</code> as GitHub Pages doesn’t load plugins via Bundler.</p>
+<p>However, if you’re publishing on GitHub Pages you should update only your <code class="language-plaintext highlighter-rouge">_config.yml</code> as GitHub Pages doesn’t load plugins via Bundler.</p>
-<p>Finally, remove references to the theme gem in <code class="highlighter-rouge">Gemfile</code> and configuration. For example, to remove <code class="highlighter-rouge">minima</code>:</p>
+<p>Finally, remove references to the theme gem in <code class="language-plaintext highlighter-rouge">Gemfile</code> and configuration. For example, to remove <code class="language-plaintext highlighter-rouge">minima</code>:</p>
 <ul>
-  <li>Open <code class="highlighter-rouge">Gemfile</code> and remove <code class="highlighter-rouge">gem "minima", "~&gt; 2.0"</code>.</li>
-  <li>Open <code class="highlighter-rouge">_config.yml</code> and remove <code class="highlighter-rouge">theme: minima</code>.</li>
+  <li>Open <code class="language-plaintext highlighter-rouge">Gemfile</code> and remove <code class="language-plaintext highlighter-rouge">gem "minima", "~&gt; 2.0"</code>.</li>
+  <li>Open <code class="language-plaintext highlighter-rouge">_config.yml</code> and remove <code class="language-plaintext highlighter-rouge">theme: minima</code>.</li>
 </ul>
-<p>Now <code class="highlighter-rouge">bundle update</code> will no longer get updates for the theme gem.</p>
+<p>Now <code class="language-plaintext highlighter-rouge">bundle update</code> will no longer get updates for the theme gem.</p>
 <h2 id="installing-a-theme">Installing a gem-based theme</h2>
-<p>The <code class="highlighter-rouge">jekyll new &lt;PATH&gt;</code> command isn’t the only way to create a new Jekyll site with a gem-based theme. You can also find gem-based themes online and incorporate them into your Jekyll project.</p>
+<p>The <code class="language-plaintext highlighter-rouge">jekyll new &lt;PATH&gt;</code> command isn’t the only way to create a new Jekyll site with a gem-based theme. You can also find gem-based themes online and incorporate them into your Jekyll project.</p>
-<p>For example, search for <a href="https://rubygems.org/search?utf8=%E2%9C%93&amp;query=jekyll-theme">jekyll theme on RubyGems</a> to find other gem-based themes. (Note that not all themes are using <code class="highlighter-rouge">jekyll-theme</code> as a convention in the theme name.)</p>
+<p>For example, search for <a href="https://rubygems.org/search?utf8=%E2%9C%93&amp;query=jekyll-theme">jekyll theme on RubyGems</a> to find other gem-based themes. (Note that not all themes are using <code class="language-plaintext highlighter-rouge">jekyll-theme</code> as a convention in the theme name.)</p>
 <p>To install a gem-based theme:</p>
 <ol>
   <li>
-    <p>Add the theme to your site’s <code class="highlighter-rouge">Gemfile</code>:</p>
+    <p>Add the theme to your site’s <code class="language-plaintext highlighter-rouge">Gemfile</code>:</p>
     <div class="language-ruby highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code><span class="c1"># ./Gemfile</span>
 <span class="n">gem</span> <span class="s2">"jekyll-theme-awesome"</span>
 </code></pre></div>    </div>
-    <p>Or if you’ve started with the <code class="highlighter-rouge">jekyll new</code> command, replace <code class="highlighter-rouge">gem "minima", "~&gt; 2.0"</code> with your theme-gem:</p>
+    <p>Or if you’ve started with the <code class="language-plaintext highlighter-rouge">jekyll new</code> command, replace <code class="language-plaintext highlighter-rouge">gem "minima", "~&gt; 2.0"</code> with your theme-gem:</p>
     <div class="language-diff highlighter-rouge">
-<div class="highlight"><pre class="highlight"><code># ./Gemfile
+<div class="highlight"><pre class="highlight"><code><span class="err">#</span> ./Gemfile
-<span class="gd">- gem "minima", "~&gt; 2.0"
-</span><span class="gi">+ gem "jekyll-theme-awesome"
+- gem "minima", "~&gt; 2.0"
+<span class="gi">+ gem "jekyll-theme-awesome"
 </span></code></pre></div>    </div>
   </li>
   <li>
@@ -484,7 +485,7 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>Add the following to your site’s <code class="highlighter-rouge">_config.yml</code> to activate the theme:</p>
+    <p>Add the following to your site’s <code class="language-plaintext highlighter-rouge">_config.yml</code> to activate the theme:</p>
     <div class="language-yaml highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code><span class="na">theme</span><span class="pi">:</span> <span class="s">jekyll-theme-awesome</span>
@@ -499,7 +500,7 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
   </li>
 </ol>
-<p class="note info">You can have multiple themes listed in your site’s <code class="highlighter-rouge">Gemfile</code>, but only one theme can be selected in your site’s <code class="highlighter-rouge">_config.yml</code>.</p>
+<p class="note info">You can have multiple themes listed in your site’s <code class="language-plaintext highlighter-rouge">Gemfile</code>, but only one theme can be selected in your site’s <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
 <p>If you’re publishing your Jekyll site on <a href="https://pages.github.com/">GitHub Pages</a>, note that GitHub Pages supports only some gem-based themes. See <a href="https://pages.github.com/themes/">Supported Themes</a> in GitHub’s documentation to see which themes are supported.</p>
@@ -507,7 +508,7 @@ spec.add_runtime_dependency "jekyll-seo-tag", "~&gt; 2.1"
 <p>If you’re a Jekyll theme developer (rather than just a consumer of themes), you can package up your theme in RubyGems and allow users to install it through Bundler.</p>
-<p>If you’re unfamiliar with creating Ruby gems, don’t worry. Jekyll will help you scaffold a new theme with the <code class="highlighter-rouge">new-theme</code> command. Run <code class="highlighter-rouge">jekyll new-theme</code> with the theme name as an argument.</p>
+<p>If you’re unfamiliar with creating Ruby gems, don’t worry. Jekyll will help you scaffold a new theme with the <code class="language-plaintext highlighter-rouge">new-theme</code> command. Run <code class="language-plaintext highlighter-rouge">jekyll new-theme</code> with the theme name as an argument.</p>
 <p>Here is an example:</p>
@@ -528,59 +529,59 @@ Your new Jekyll theme, jekyll-theme-awesome, is ready <span class="k">for </span
 For <span class="nb">help </span>getting started, <span class="nb">read</span> /path/to/jekyll-theme-awesome/README.md.
 </code></pre></div></div>
-<p>Add your template files in the corresponding folders. Then complete the <code class="highlighter-rouge">.gemspec</code> and the README files according to your needs.</p>
+<p>Add your template files in the corresponding folders. Then complete the <code class="language-plaintext highlighter-rouge">.gemspec</code> and the README files according to your needs.</p>
 <h3 id="layouts-and-includes">Layouts and includes</h3>
-<p>Theme layouts and includes work just like they work in any Jekyll site. Place layouts in your theme’s <code class="highlighter-rouge">/_layouts</code> folder, and place includes in your themes <code class="highlighter-rouge">/_includes</code> folder.</p>
+<p>Theme layouts and includes work just like they work in any Jekyll site. Place layouts in your theme’s <code class="language-plaintext highlighter-rouge">/_layouts</code> folder, and place includes in your themes <code class="language-plaintext highlighter-rouge">/_includes</code> folder.</p>
-<p>For example, if your theme has a <code class="highlighter-rouge">/_layouts/page.html</code> file, and a page has <code class="highlighter-rouge">layout: page</code> in its YAML front matter, Jekyll will first look to the site’s <code class="highlighter-rouge">_layouts</code> folder for the <code class="highlighter-rouge">page</code> layout, and if none exists, will use your theme’s <code class="highlighter-rouge">page</code> layout.</p>
+<p>For example, if your theme has a <code class="language-plaintext highlighter-rouge">/_layouts/page.html</code> file, and a page has <code class="language-plaintext highlighter-rouge">layout: page</code> in its YAML front matter, Jekyll will first look to the site’s <code class="language-plaintext highlighter-rouge">_layouts</code> folder for the <code class="language-plaintext highlighter-rouge">page</code> layout, and if none exists, will use your theme’s <code class="language-plaintext highlighter-rouge">page</code> layout.</p>
 <h3 id="assets">Assets</h3>
-<p>Any file in <code class="highlighter-rouge">/assets</code> will be copied over to the user’s site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:</p>
+<p>Any file in <code class="language-plaintext highlighter-rouge">/assets</code> will be copied over to the user’s site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:</p>
 <ul>
   <li>If the file has <a href="/docs/frontmatter/">YAML front matter</a> at the top, it will be rendered.</li>
   <li>If the file does not have YAML front matter, it will simply be copied over into the resulting site.</li>
 </ul>
-<p>This allows theme creators to ship a default <code class="highlighter-rouge">/assets/styles.scss</code> file which their layouts can depend on as <code class="highlighter-rouge">/assets/styles.css</code>.</p>
+<p>This allows theme creators to ship a default <code class="language-plaintext highlighter-rouge">/assets/styles.scss</code> file which their layouts can depend on as <code class="language-plaintext highlighter-rouge">/assets/styles.css</code>.</p>
-<p>All files in <code class="highlighter-rouge">/assets</code> will be output into the compiled site in the <code class="highlighter-rouge">/assets</code> folder just as you’d expect from using Jekyll on your sites.</p>
+<p>All files in <code class="language-plaintext highlighter-rouge">/assets</code> will be output into the compiled site in the <code class="language-plaintext highlighter-rouge">/assets</code> folder just as you’d expect from using Jekyll on your sites.</p>
 <h3 id="stylesheets">Stylesheets</h3>
-<p>Your theme’s stylesheets should be placed in your theme’s <code class="highlighter-rouge">_sass</code> folder, again, just as you would when authoring a Jekyll site.</p>
+<p>Your theme’s stylesheets should be placed in your theme’s <code class="language-plaintext highlighter-rouge">_sass</code> folder, again, just as you would when authoring a Jekyll site.</p>
-<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>_sass
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>_sass
 ├── jekyll-theme-awesome.scss
 </code></pre></div></div>
-<p>Your theme’s styles can be included in the user’s stylesheet using the <code class="highlighter-rouge">@import</code> directive.</p>
+<p>Your theme’s styles can be included in the user’s stylesheet using the <code class="language-plaintext highlighter-rouge">@import</code> directive.</p>
 <div class="language-css highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="k">@import</span> <span class="s1">"{{ site.theme }}"</span><span class="p">;</span>
 </code></pre></div></div>
 <h3 id="theme-gem-dependencies350">Theme-gem dependencies<span class="version-badge" title="This feature is available starting version 3.5.0">3.5.0</span>
 </h3>
-<p>Jekyll will automatically require all whitelisted <code class="highlighter-rouge">runtime_dependencies</code> of your theme-gem even if they’re not explicitly included under the <code class="highlighter-rouge">plugins</code> array in the site’s config file. (Note: whitelisting is only required when building or serving with the <code class="highlighter-rouge">--safe</code> option.)</p>
+<p>Jekyll will automatically require all whitelisted <code class="language-plaintext highlighter-rouge">runtime_dependencies</code> of your theme-gem even if they’re not explicitly included under the <code class="language-plaintext highlighter-rouge">plugins</code> array in the site’s config file. (Note: whitelisting is only required when building or serving with the <code class="language-plaintext highlighter-rouge">--safe</code> option.)</p>
 <p>With this, the end-user need not keep track of the plugins required to be included in their config file for their theme-gem to work as intended.</p>
 <h3 id="documenting-your-theme">Documenting your theme</h3>
-<p>Your theme should include a <code class="highlighter-rouge">/README.md</code> file, which explains how site authors can install and use your theme. What layouts are included? What includes? Do they need to add anything special to their site’s configuration file?</p>
+<p>Your theme should include a <code class="language-plaintext highlighter-rouge">/README.md</code> file, which explains how site authors can install and use your theme. What layouts are included? What includes? Do they need to add anything special to their site’s configuration file?</p>
 <h3 id="adding-a-screenshot">Adding a screenshot</h3>
-<p>Themes are visual. Show users what your theme looks like by including a screenshot as <code class="highlighter-rouge">/screenshot.png</code> within your theme’s repository where it can be retrieved programmatically. You can also include this screenshot within your theme’s documentation.</p>
+<p>Themes are visual. Show users what your theme looks like by including a screenshot as <code class="language-plaintext highlighter-rouge">/screenshot.png</code> within your theme’s repository where it can be retrieved programmatically. You can also include this screenshot within your theme’s documentation.</p>
 <h3 id="previewing-your-theme">Previewing your theme</h3>
-<p>To preview your theme as you’re authoring it, it may be helpful to add dummy content in, for example, <code class="highlighter-rouge">/index.html</code> and <code class="highlighter-rouge">/page.html</code> files. This will allow you to use the <code class="highlighter-rouge">jekyll build</code> and <code class="highlighter-rouge">jekyll serve</code> commands to preview your theme, just as you’d preview a Jekyll site.</p>
+<p>To preview your theme as you’re authoring it, it may be helpful to add dummy content in, for example, <code class="language-plaintext highlighter-rouge">/index.html</code> and <code class="language-plaintext highlighter-rouge">/page.html</code> files. This will allow you to use the <code class="language-plaintext highlighter-rouge">jekyll build</code> and <code class="language-plaintext highlighter-rouge">jekyll serve</code> commands to preview your theme, just as you’d preview a Jekyll site.</p>
-<p class="info note">If you do preview your theme locally, be sure to add <code class="highlighter-rouge">/_site</code> to your theme’s <code class="highlighter-rouge">.gitignore</code> file to prevent the compiled site from also being included when you distribute your theme.</p>
+<p class="info note">If you do preview your theme locally, be sure to add <code class="language-plaintext highlighter-rouge">/_site</code> to your theme’s <code class="language-plaintext highlighter-rouge">.gitignore</code> file to prevent the compiled site from also being included when you distribute your theme.</p>
 <h3 id="publishing-your-theme">Publishing your theme</h3>
@@ -597,21 +598,21 @@ git commit <span class="nt">-m</span> <span class="s2">"Init commit"</span>
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>Next, package your theme, by running the following command, replacing <code class="highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
+    <p>Next, package your theme, by running the following command, replacing <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
     <div class="language-sh highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code>gem build jekyll-theme-awesome.gemspec
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>Finally, push your packaged theme up to the RubyGems service, by running the following command, again replacing <code class="highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
+    <p>Finally, push your packaged theme up to the RubyGems service, by running the following command, again replacing <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
     <div class="language-sh highlighter-rouge">
 <div class="highlight"><pre class="highlight"><code>gem push jekyll-theme-awesome-<span class="k">*</span>.gem
 </code></pre></div>    </div>
   </li>
   <li>
-    <p>To release a new version of your theme, update the version number in the gemspec file, ( <code class="highlighter-rouge">jekyll-theme-awesome.gemspec</code> in this example ), and then repeat Steps 1 - 3 above. We recommend that you follow <a href="http://semver.org/">Semantic Versioning</a> while bumping your theme-version.</p>
+    <p>To release a new version of your theme, update the version number in the gemspec file, ( <code class="language-plaintext highlighter-rouge">jekyll-theme-awesome.gemspec</code> in this example ), and then repeat Steps 1 - 3 above. We recommend that you follow <a href="http://semver.org/">Semantic Versioning</a> while bumping your theme-version.</p>
   </li>
 </ol>
@@ -906,7 +907,7 @@ git commit <span class="nt">-m</span> <span class="s2">"Init commit"</span>
   <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>