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

jekyll-docs 3.9.0 → 4.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (225) hide show

checksums.yaml +4 -4
data/lib/jekyll-docs.rb +3 -3
data/site/404.html +10 -7
data/site/css/screen.css +3 -1
data/site/css/screen.css.map +28 -0
data/site/docs/assets/index.html +412 -453
data/site/docs/code_of_conduct/index.html +447 -501
data/site/docs/collections/index.html +487 -674
data/site/docs/community/bug/index.html +603 -0
data/site/docs/community/index.html +635 -0
data/site/docs/conduct/index.html +447 -515
data/site/docs/configuration/default/index.html +682 -0
data/site/docs/configuration/environments/index.html +641 -0
data/site/docs/configuration/front-matter-defaults/index.html +738 -0
data/site/docs/configuration/incremental-regeneration/index.html +631 -0
data/site/docs/configuration/index.html +405 -1230
data/site/docs/configuration/liquid/index.html +616 -0
data/site/docs/configuration/markdown/index.html +766 -0
data/site/docs/configuration/options/index.html +1011 -0
data/site/docs/configuration/webrick/index.html +615 -0
data/site/docs/continuous-integration/buddyworks/index.html +393 -479
data/site/docs/continuous-integration/circleci/index.html +465 -481
data/site/docs/continuous-integration/travis-ci/index.html +450 -507
data/site/docs/contributing/index.html +425 -514
data/site/docs/datafiles/index.html +411 -453
data/site/docs/deployment-methods/index.html +9 -871
data/site/docs/deployment/automated/index.html +663 -0
data/site/docs/deployment/index.html +607 -0
data/site/docs/deployment/manual/index.html +631 -0
data/site/docs/deployment/third-party/index.html +639 -0
data/site/docs/drafts/index.html +9 -634
data/site/docs/extras/index.html +9 -687
data/site/docs/front-matter/index.html +799 -0
data/site/docs/frontmatter/index.html +9 -819
data/site/docs/github-pages/index.html +407 -475
data/site/docs/history/index.html +1370 -1154
data/site/docs/home/index.html +9 -627
data/site/docs/includes/index.html +425 -501
data/site/docs/index.html +630 -9
data/site/docs/installation/index.html +403 -540
data/site/docs/installation/macos/index.html +716 -0
data/site/docs/installation/other-linux/index.html +613 -0
data/site/docs/installation/ubuntu/index.html +623 -0
data/site/docs/installation/windows/index.html +733 -0
data/site/docs/layouts/index.html +726 -0
data/site/docs/liquid/filters/index.html +1169 -0
data/site/docs/liquid/index.html +615 -0
data/site/docs/liquid/tags/index.html +728 -0
data/site/docs/maintaining/affinity-team-captain/index.html +395 -479
data/site/docs/maintaining/avoiding-burnout/index.html +391 -475
data/site/docs/maintaining/becoming-a-maintainer/index.html +391 -475
data/site/docs/maintaining/index.html +391 -486
data/site/docs/maintaining/merging-a-pull-request/index.html +406 -490
data/site/docs/maintaining/releasing-a-new-version/index.html +409 -485
data/site/docs/maintaining/reviewing-a-pull-request/index.html +392 -476
data/site/docs/maintaining/special-labels/index.html +397 -481
data/site/docs/maintaining/triaging-an-issue/index.html +394 -478
data/site/docs/markdown-101/index.html +601 -0
data/site/docs/migrations/index.html +396 -440
data/site/docs/pages/index.html +408 -482
data/site/docs/pagination/index.html +450 -509
data/site/docs/permalinks/index.html +552 -587
data/site/docs/plugins/commands/index.html +656 -0
data/site/docs/plugins/converters/index.html +685 -0
data/site/docs/plugins/filters/index.html +624 -0
data/site/docs/plugins/generators/index.html +697 -0
data/site/docs/plugins/hooks/index.html +838 -0
data/site/docs/plugins/index.html +415 -1565
data/site/docs/plugins/installation/index.html +681 -0
data/site/docs/plugins/tags/index.html +699 -0
data/site/docs/plugins/your-first-plugin/index.html +741 -0
data/site/docs/posts/index.html +491 -627
data/site/docs/quickstart/index.html +9 -645
data/site/docs/resources/index.html +9 -761
data/site/docs/ruby-101/index.html +640 -0
data/site/docs/sites/index.html +9 -696
data/site/docs/static-files/index.html +401 -433
data/site/docs/step-by-step/01-setup/index.html +771 -0
data/site/docs/step-by-step/02-liquid/index.html +756 -0
data/site/docs/step-by-step/03-front-matter/index.html +730 -0
data/site/docs/step-by-step/04-layouts/index.html +770 -0
data/site/docs/step-by-step/05-includes/index.html +768 -0
data/site/docs/step-by-step/06-data-files/index.html +738 -0
data/site/docs/step-by-step/07-assets/index.html +773 -0
data/site/docs/step-by-step/08-blogging/index.html +835 -0
data/site/docs/step-by-step/09-collections/index.html +932 -0
data/site/docs/step-by-step/10-deployment/index.html +842 -0
data/site/docs/structure/index.html +411 -430
data/site/docs/support/index.html +392 -476
data/site/docs/templates/index.html +9 -1232
data/site/docs/themes/index.html +487 -521
data/site/docs/troubleshooting/index.html +443 -520
data/site/docs/upgrading/0-to-2/index.html +437 -523
data/site/docs/upgrading/2-to-3/index.html +422 -507
data/site/docs/upgrading/3-to-4/index.html +765 -0
data/site/docs/upgrading/index.html +395 -478
data/site/docs/usage/index.html +409 -506
data/site/docs/variables/index.html +504 -652
data/site/docs/windows/index.html +9 -784
data/site/feed.xml +269 -188
data/site/feed/release.xml +324 -0
data/site/fonts/lato-v14-latin-300.woff +0 -0
data/site/fonts/lato-v14-latin-300.woff2 +0 -0
data/site/fonts/lato-v14-latin-300italic.woff +0 -0
data/site/fonts/lato-v14-latin-300italic.woff2 +0 -0
data/site/fonts/lato-v14-latin-700.woff +0 -0
data/site/fonts/lato-v14-latin-700.woff2 +0 -0
data/site/fonts/lato-v14-latin-700italic.woff +0 -0
data/site/fonts/lato-v14-latin-700italic.woff2 +0 -0
data/site/fonts/lato-v14-latin-900.woff +0 -0
data/site/fonts/lato-v14-latin-900.woff2 +0 -0
data/site/fonts/lato-v14-latin-900italic.woff +0 -0
data/site/fonts/lato-v14-latin-900italic.woff2 +0 -0
data/site/fonts/lato-v14-latin-italic.woff +0 -0
data/site/fonts/lato-v14-latin-italic.woff2 +0 -0
data/site/fonts/lato-v14-latin-regular.woff +0 -0
data/site/fonts/lato-v14-latin-regular.woff2 +0 -0
data/site/help/index.html +9 -247
data/site/img/forestry-logo.svg +19 -0
data/site/img/jekyll-og.png +0 -0
data/site/img/spacer.gif +0 -0
data/site/index.html +56 -29
data/site/jekyllconf/index.html +62 -35
data/site/latest_version.txt +1 -1
data/site/news/2013/05/05/jekyll-1-0-0-released/index.html +180 -115
data/site/news/2013/05/08/jekyll-1-0-1-released/index.html +182 -117
data/site/news/2013/05/12/jekyll-1-0-2-released/index.html +183 -118
data/site/news/2013/06/07/jekyll-1-0-3-released/index.html +184 -119
data/site/news/2013/07/14/jekyll-1-1-0-released/index.html +183 -118
data/site/news/2013/07/24/jekyll-1-1-1-released/index.html +180 -115
data/site/news/2013/07/25/jekyll-1-0-4-released/index.html +182 -117
data/site/news/2013/07/25/jekyll-1-1-2-released/index.html +182 -117
data/site/news/2013/09/06/jekyll-1-2-0-released/index.html +185 -120
data/site/news/2013/09/14/jekyll-1-2-1-released/index.html +183 -118
data/site/news/2013/10/28/jekyll-1-3-0-rc1-released/index.html +180 -115
data/site/news/2013/11/04/jekyll-1-3-0-released/index.html +189 -124
data/site/news/2013/11/26/jekyll-1-3-1-released/index.html +181 -116
data/site/news/2013/12/07/jekyll-1-4-0-released/index.html +181 -116
data/site/news/2013/12/09/jekyll-1-4-1-released/index.html +180 -115
data/site/news/2013/12/16/jekyll-1-4-2-released/index.html +182 -117
data/site/news/2014/01/13/jekyll-1-4-3-released/index.html +181 -116
data/site/news/2014/03/24/jekyll-1-5-0-released/index.html +181 -116
data/site/news/2014/03/27/jekyll-1-5-1-released/index.html +181 -116
data/site/news/2014/05/06/jekyll-turns-2-0-0/index.html +184 -119
data/site/news/2014/05/08/jekyll-2-0-3-released/index.html +180 -115
data/site/news/2014/06/04/jekyll-stickers-1-dollar-stickermule/index.html +181 -116
data/site/news/2014/06/28/jekyll-turns-21-i-mean-2-1-0/index.html +185 -120
data/site/news/2014/07/01/jekyll-2-1-1-released/index.html +182 -117
data/site/news/2014/07/29/jekyll-2-2-0-released/index.html +181 -116
data/site/news/2014/08/10/jekyll-2-3-0-released/index.html +189 -124
data/site/news/2014/09/09/jekyll-2-4-0-released/index.html +187 -122
data/site/news/2014/11/05/jekylls-midlife-crisis-jekyll-turns-2-5-0/index.html +188 -123
data/site/news/2014/11/09/jekyll-2-5-1-released/index.html +180 -115
data/site/news/2014/11/12/jekyll-2-5-2-released/index.html +182 -117
data/site/news/2014/12/17/alfredxing-welcome-to-jekyll-core/index.html +179 -114
data/site/news/2014/12/22/jekyll-2-5-3-released/index.html +180 -115
data/site/news/2015/01/20/jekyll-meet-and-greet/index.html +179 -114
data/site/news/2015/01/24/jekyll-3-0-0-beta1-released/index.html +180 -115
data/site/news/2015/02/26/introducing-jekyll-talk/index.html +180 -115
data/site/news/2015/10/26/jekyll-3-0-released/index.html +185 -120
data/site/news/2015/11/17/jekyll-3-0-1-released/index.html +184 -119
data/site/news/2016/01/20/jekyll-3-0-2-released/index.html +182 -117
data/site/news/2016/01/24/jekyll-3-1-0-released/index.html +186 -121
data/site/news/2016/01/28/jekyll-3-1-1-released/index.html +183 -118
data/site/news/2016/02/08/jekyll-3-0-3-released/index.html +181 -116
data/site/news/2016/02/19/jekyll-3-1-2-released/index.html +182 -117
data/site/news/2016/03/10/making-it-easier-to-contribute-to-jekyll/index.html +179 -114
data/site/news/2016/04/19/jekyll-3-0-4-released/index.html +181 -116
data/site/news/2016/04/19/jekyll-3-1-3-released/index.html +181 -116
data/site/news/2016/04/26/jekyll-3-0-5-released/index.html +180 -115
data/site/news/2016/05/18/jekyll-3-1-4-released/index.html +186 -121
data/site/news/2016/05/18/jekyll-3-1-5-released/index.html +181 -116
data/site/news/2016/05/19/jekyll-3-1-6-released/index.html +181 -116
data/site/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/index.html +179 -114
data/site/news/2016/07/26/jekyll-3-2-0-released/index.html +184 -119
data/site/news/2016/08/02/jekyll-3-2-1-released/index.html +180 -115
data/site/news/2016/08/24/jekyll-admin-initial-release/index.html +179 -114
data/site/news/2016/10/06/jekyll-3-3-is-here/index.html +207 -142
data/site/news/2016/11/14/jekyll-3-3-1-released/index.html +181 -116
data/site/news/2017/01/18/jekyll-3-4-0-released/index.html +183 -118
data/site/news/2017/03/02/jekyll-3-4-1-released/index.html +181 -116
data/site/news/2017/03/09/jekyll-3-4-2-released/index.html +189 -124
data/site/news/2017/03/21/jekyll-3-4-3-released/index.html +190 -125
data/site/news/2017/06/15/jekyll-3-5-0-released/index.html +187 -122
data/site/news/2017/07/17/jekyll-3-5-1-released/index.html +182 -117
data/site/news/2017/08/12/jekyll-3-5-2-released/index.html +185 -120
data/site/news/2017/09/21/jekyll-3-6-0-released/index.html +181 -116
data/site/news/2017/10/19/diversity-open-source/index.html +181 -116
data/site/news/2017/10/21/jekyll-3-6-2-released/index.html +183 -118
data/site/news/2018/01/02/jekyll-3-7-0-released/index.html +184 -119
data/site/news/2018/01/25/jekyll-3-7-2-released/index.html +189 -124
data/site/news/2018/02/19/meet-jekyll-s-new-lead-developer/index.html +180 -115
data/site/news/2018/02/24/jekyll-3-7-3-released/index.html +185 -120
data/site/news/2018/04/19/development-update/index.html +699 -0
data/site/news/2018/04/19/jekyll-3-8-0-released/index.html +715 -0
data/site/news/2018/05/01/jekyll-3-8-1-released/index.html +182 -117
data/site/news/2018/05/19/jekyll-3-8-2-released/index.html +181 -116
data/site/news/2018/06/05/jekyll-3-8-3-released/index.html +183 -118
data/site/news/2018/08/01/jekyll-sponsoring/index.html +748 -0
data/site/news/2018/09/19/security-fixes-for-3-6-3-7-3-8/index.html +692 -0
data/site/news/2018/11/04/jekyll-3-8-5-released/index.html +682 -0
data/site/news/2019/03/18/jekyll-4-0-0-pre-alpha1-released/index.html +710 -0
data/site/news/2019/07/02/jekyll-3-8-6-released/index.html +180 -115
data/site/news/2019/07/20/jekyll-4-0-0-pre-beta1-released/index.html +11 -0
data/site/news/2019/08/04/jekyll-4-0-0-pre-beta1-released/index.html +708 -0
data/site/news/2019/08/20/jekyll-4-0-0-released/index.html +809 -0
data/site/news/index.html +976 -326
data/site/news/releases/index.html +820 -321
data/site/{philosophy.html → philosophy/index.html} +1 -1
data/site/redirects.json +1 -1
data/site/resources/index.html +332 -0
data/site/showcase/index.html +844 -0
data/site/sitemap.xml +256 -81
data/site/team/index.html +63 -77
data/site/tutorials/cache-api/index.html +418 -0
data/site/tutorials/convert-site-to-jekyll/index.html +155 -124
data/site/tutorials/custom-404-page/index.html +76 -43
data/site/tutorials/home/index.html +64 -37
data/site/tutorials/navigation/index.html +186 -103
data/site/tutorials/orderofinterpretation/index.html +80 -53
data/site/tutorials/using-jekyll-with-bundler/index.html +80 -51
data/site/tutorials/video-walkthroughs/index.html +62 -35
metadata +102 -13
data/site/community/index.html +0 -11
data/site/docs/continuous-integration/index.html +0 -681

data/site/docs/deployment-methods/index.html CHANGED

@@ -1,873 +1,11 @@
-<!DOCTYPE HTML>
+<!DOCTYPE html>
 <html lang="en-US">
-<head>
-  <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width,initial-scale=1">
-  <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>
-  <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
-  <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.6.1 -->
-<title>Deployment methods | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.9.0" />
-<meta property="og:title" content="Deployment methods" />
-<meta property="og:locale" content="en_US" />
-<meta name="description" content="Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. A few of the most common deployment techniques are described below." />
-<meta property="og:description" content="Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. A few of the most common deployment techniques are described below." />
-<link rel="canonical" href="https://jekyllrb.com/docs/deployment-methods/" />
-<meta property="og:url" content="https://jekyllrb.com/docs/deployment-methods/" />
-<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
-<meta property="og:type" content="article" />
-<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
-<meta name="twitter:card" content="summary" />
-<meta property="twitter:title" content="Deployment methods" />
-<meta name="twitter:site" content="@jekyllrb" />
-<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
-<script type="application/ld+json">
-{"url":"https://jekyllrb.com/docs/deployment-methods/","headline":"Deployment methods","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":"Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. A few of the most common deployment techniques are described below.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/deployment-methods/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
-<!-- End Jekyll SEO tag -->
-  <!--[if lt IE 9]>
-  <script src="/js/html5shiv.min.js"></script>
-  <script src="/js/respond.min.js"></script>
-  <![endif]-->
-</head>
-<body class="wrap">
-  <header>
-  <div class="flexbox">
-    <div class="center-on-mobiles">
-      <h1>
-        <a href="/" class="logo">
-          <span class="sr-only">Jekyll</span>
-          <img src="/img/logo-2x.png" width="140" height="65" alt="Jekyll Logo">
-        </a>
-      </h1>
-    </div>
-    <nav class="main-nav hide-on-mobiles">
-      <ul>
-  <li class="">
-    <a href="/">Home</a>
-  </li>
-  <li class="current">
-    <a href="/docs/home/">Docs</a>
-  </li>
-  <li class="">
-    <a href="/news/">News</a>
-  </li>
-  <li class="">
-    <a href="/help/">Help</a>
-  </li>
-</ul>
-    </nav>
-    <div class="search hide-on-mobiles">
-      <input type="text" id="docsearch-input" placeholder="Search the docs…">
-    </div>
-    <div class="meta hide-on-mobiles">
-      <ul>
-        <li>
-          <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>
-        </li>
-      </ul>
-    </div>
-  </div>
-  <nav class="mobile-nav show-on-mobiles">
-    <ul>
-  <li class="">
-    <a href="/">Home</a>
-  </li>
-  <li class="current">
-    <a href="/docs/home/">Docs</a>
-  </li>
-  <li class="">
-    <a href="/news/">News</a>
-  </li>
-  <li class="">
-    <a href="/help/">Help</a>
-  </li>
-  <li>
-    <a href="https://github.com/jekyll/jekyll">GitHub</a>
-  </li>
-</ul>
-  </nav>
-</header>
-    <section class="docs">
-    <div class="grid">
-      <div class="docs-nav-mobile unit whole show-on-mobiles">
-  <select onchange="if (this.value) window.location.href=this.value">
-    <option value="">Navigate the docs…</option>
-    <optgroup label="Getting Started">
-  <option value="/docs/home/">Welcome</option>
-  <option value="/docs/quickstart/">Quick-start guide</option>
-  <option value="/docs/installation/">Installation</option>
-  <option value="/docs/windows/">Jekyll on Windows</option>
-  <option value="/docs/usage/">Basic Usage</option>
-  <option value="/docs/structure/">Directory structure</option>
-  <option value="/docs/configuration/">Configuration</option>
-    </optgroup>
-    <optgroup label="Your Content">
-  <option value="/docs/frontmatter/">Front Matter</option>
-  <option value="/docs/posts/">Writing posts</option>
-  <option value="/docs/drafts/">Working with drafts</option>
-  <option value="/docs/pages/">Creating pages</option>
-  <option value="/docs/static-files/">Static Files</option>
-  <option value="/docs/variables/">Variables</option>
-  <option value="/docs/collections/">Collections</option>
-  <option value="/docs/datafiles/">Data Files</option>
-  <option value="/docs/assets/">Assets</option>
-  <option value="/docs/migrations/">Blog migrations</option>
-    </optgroup>
-    <optgroup label="Customization">
-  <option value="/docs/templates/">Templates</option>
-  <option value="/docs/includes/">Includes</option>
-  <option value="/docs/permalinks/">Permalinks</option>
-  <option value="/docs/pagination/">Pagination</option>
-  <option value="/docs/plugins/">Plugins</option>
-  <option value="/docs/themes/">Themes</option>
-  <option value="/docs/extras/">Extras</option>
-    </optgroup>
-    <optgroup label="Deployment">
-  <option value="/docs/github-pages/">GitHub Pages</option>
-  <option value="/docs/deployment-methods/">Deployment methods</option>
-  <option value="/docs/continuous-integration/">Continuous Integration</option>
-    </optgroup>
-    <optgroup label="Miscellaneous">
-  <option value="/docs/troubleshooting/">Troubleshooting</option>
-  <option value="/docs/sites/">Sites using Jekyll</option>
-  <option value="/docs/resources/">Resources</option>
-  <option value="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</option>
-  <option value="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</option>
-    </optgroup>
-    <optgroup label="Meta">
-  <option value="/docs/contributing/">Contributing</option>
-  <option value="/docs/maintaining/">Maintaining Jekyll</option>
-  <option value="/docs/conduct/">Code of Conduct</option>
-  <option value="/docs/history/">History</option>
-    </optgroup>
-  </select>
-</div>
-      <div class="unit four-fifths">
-        <article>
-          <div class="improve right hide-on-mobiles">
-            <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/deployment-methods.md"><i class="fa fa-pencil"></i> &nbsp;Improve this page</a>
-          </div>
-          <h1>Deployment methods</h1>
-          <p>Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. A few of the most common deployment techniques are described below.</p>
-<div class="note">
-  <h5>ProTip™: Use GitHub Pages for zero-hassle Jekyll hosting</h5>
-  <p>GitHub Pages are powered by Jekyll behind the scenes, so if you’re looking for a zero-hassle, zero-cost solution, GitHub Pages are a great way to <a href="../github-pages/">host your Jekyll-powered website for free</a>.</p>
-</div>
-<h2 id="netlify">Netlify</h2>
-<p>Netlify provides Global CDN, Continuous Deployment, one click HTTPS and <a href="https://www.netlify.com/features/">much more</a>, providing developers the most robust toolset available for modern web projects, without added complexity. Netlify supports custom plugins for Jekyll and has a free plan for open source projects.</p>
-<p>Read this <a href="https://www.netlify.com/blog/2015/10/28/a-step-by-step-guide-jekyll-3.0-on-netlify/">Jekyll step-by-step guide</a> to setup your Jekyll site on Netlify.</p>
-<h2 id="aerobatic">Aerobatic</h2>
-<p><a href="https://www.aerobatic.com">Aerobatic</a> has custom domains, global CDN distribution, basic auth, CORS proxying, and a growing list of plugins all included.</p>
-<p>Automating the deployment of a Jekyll site is simple. See their <a href="https://www.aerobatic.com/docs/static-site-generators/#jekyll">Jekyll docs</a> for more details. Your built <code class="language-plaintext highlighter-rouge">_site</code> folder is deployed to their highly-available, globally distributed hosting service.</p>
-<h2 id="kickster">Kickster</h2>
-<p>Use <a href="http://kickster.nielsenramon.com/">Kickster</a> for easy (automated) deploys to GitHub Pages when using unsupported plugins on GitHub Pages.</p>
-<p>Kickster provides a basic Jekyll project setup packed with web best practises and useful optimization tools increasing your overall project quality. Kickster ships with automated and worry-free deployment scripts for GitHub Pages.</p>
-<p>Setting up Kickster is very easy, just install the gem and you are good to go. More documentation can here found <a href="https://github.com/nielsenramon/kickster#kickster">here</a>. If you do not want to use the gem or start a new project you can just copy paste the deployment scripts for <a href="https://github.com/nielsenramon/kickster/tree/master/snippets/travis">Travis CI</a> or <a href="https://github.com/nielsenramon/kickster#automated-deployment-with-circle-ci">Circle CI</a>.</p>
-<h2 id="web-hosting-providers-ftp">Web hosting providers (FTP)</h2>
-<p>Just about any traditional web hosting provider will let you upload files to their servers over FTP. To upload a Jekyll site to a web host using FTP, simply run the <code class="language-plaintext highlighter-rouge">jekyll build</code> command and copy the contents of the generated <code class="language-plaintext highlighter-rouge">_site</code> folder to the root folder of your hosting account. This is most likely to be the <code class="language-plaintext highlighter-rouge">httpdocs</code> or <code class="language-plaintext highlighter-rouge">public_html</code> folder on most hosting providers.</p>
-<h2 id="self-managed-web-server">Self-managed web server</h2>
-<p>If you have direct access to the deployment web server, the process is essentially the same, except you might have other methods available to you (such as <code class="language-plaintext highlighter-rouge">scp</code>, or even direct filesystem access) for transferring the files. Just remember to make sure the contents of the generated <code class="language-plaintext highlighter-rouge">_site</code> folder get placed in the appropriate web root directory for your web server.</p>
-<h2 id="automated-methods">Automated methods</h2>
-<p>There are also a number of ways to easily automate the deployment of a Jekyll site. If you’ve got another method that isn’t listed below, we’d love it if you <a href="../contributing/">contributed</a> so that everyone else can benefit too.</p>
-<h3 id="git-post-update-hook">Git post-update hook</h3>
-<p>If you store your Jekyll site in <a href="https://git-scm.com/">Git</a> (you are using
-version control, right?), it’s pretty easy to automate the
-deployment process by setting up a post-update hook in your Git
-repository, <a href="http://web.archive.org/web/20091223025644/http://www.taknado.com/en/2009/03/26/deploying-a-jekyll-generated-site/">like
-this</a>.</p>
-<h3 id="git-post-receive-hook">Git post-receive hook</h3>
-<p>To have a remote server handle the deploy for you every time you push changes using Git, you can create a user account which has all the public keys that are authorized to deploy in its <code class="language-plaintext highlighter-rouge">authorized_keys</code> file. With that in place, setting up the post-receive hook is done as follows:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>laptop<span class="nv">$ </span>ssh deployer@example.com
-server<span class="nv">$ </span><span class="nb">mkdir </span>myrepo.git
-server<span class="nv">$ </span><span class="nb">cd </span>myrepo.git
-server<span class="nv">$ </span>git <span class="nt">--bare</span> init
-server<span class="nv">$ </span><span class="nb">cp </span>hooks/post-receive.sample hooks/post-receive
-server<span class="nv">$ </span><span class="nb">mkdir</span> /var/www/myrepo
-</code></pre></div></div>
-<p>Next, add the following lines to hooks/post-receive and be sure Jekyll is
-installed on the server:</p>
-<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">GIT_REPO</span><span class="o">=</span><span class="nv">$HOME</span>/myrepo.git
-<span class="nv">TMP_GIT_CLONE</span><span class="o">=</span><span class="nv">$HOME</span>/tmp/myrepo
-<span class="nv">GEMFILE</span><span class="o">=</span><span class="nv">$TMP_GIT_CLONE</span>/Gemfile
-<span class="nv">PUBLIC_WWW</span><span class="o">=</span>/var/www/myrepo
-git clone <span class="nv">$GIT_REPO</span> <span class="nv">$TMP_GIT_CLONE</span>
-<span class="nv">BUNDLE_GEMFILE</span><span class="o">=</span><span class="nv">$GEMFILE</span> bundle <span class="nb">install
-</span><span class="nv">BUNDLE_GEMFILE</span><span class="o">=</span><span class="nv">$GEMFILE</span> bundle <span class="nb">exec </span>jekyll build <span class="nt">-s</span> <span class="nv">$TMP_GIT_CLONE</span> <span class="nt">-d</span> <span class="nv">$PUBLIC_WWW</span>
-<span class="nb">rm</span> <span class="nt">-Rf</span> <span class="nv">$TMP_GIT_CLONE</span>
-<span class="nb">exit</span>
-</code></pre></div></div>
-<p>Finally, run the following command on any users laptop that needs to be able to
-deploy using this hook:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>laptops<span class="nv">$ </span>git remote add deploy deployer@example.com:~/myrepo.git
-</code></pre></div></div>
-<p>Deploying is now as easy as telling nginx or Apache to look at
-<code class="language-plaintext highlighter-rouge">/var/www/myrepo</code> and running the following:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>laptops<span class="nv">$ </span>git push deploy master
-</code></pre></div></div>
-<h3 id="static-publisher">Static Publisher</h3>
-<p><a href="https://github.com/static-publisher/static-publisher">Static Publisher</a> is another automated deployment option with a server listening for webhook posts, though it’s not tied to GitHub specifically. It has a one-click deploy to Heroku, it can watch multiple projects from one server, it has an easy to user admin interface and can publish to either S3 or to a git repository (e.g. gh-pages).</p>
-<h3 id="rake">Rake</h3>
-<p>Another way to deploy your Jekyll site is to use <a href="https://github.com/ruby/rake">Rake</a>, <a href="https://github.com/JEG2/highline">HighLine</a>, and
-<a href="https://github.com/net-ssh/net-ssh">Net::SSH</a>. A more complex example of deploying Jekyll with Rake that deals with multiple branches can be found in <a href="https://github.com/gitready/gitready/blob/cdfbc4ec5321ff8d18c3ce936e9c749dbbc4f190/Rakefile">Git Ready</a>.</p>
-<h3 id="scp">scp</h3>
-<p>Once you’ve generated the <code class="language-plaintext highlighter-rouge">_site</code> directory, you can easily scp its content using a
-<code class="language-plaintext highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/henrik/henrik.nyh.se/blob/master/script/deploy">this deploy script</a>. You’d obviously
-need to change the values to reflect your site’s details. There is even <a href="https://gist.github.com/henrik/214959">a
-matching TextMate command</a> that will help you run this script.</p>
-<h3 id="rsync">rsync</h3>
-<p>Once you’ve generated the <code class="language-plaintext highlighter-rouge">_site</code> directory, you can easily rsync its content using a <code class="language-plaintext highlighter-rouge">tasks/deploy</code> shell script similar to <a href="https://github.com/vitalyrepin/vrepinblog/blob/master/transfer.sh">this deploy script here</a>. You’d obviously need to change the values to reflect your site’s details.</p>
-<p>Certificate-based authorization is another way to simplify the publishing
-process. It makes sense to restrict rsync access only to the directory which it is supposed to sync. This can be done using rrsync.</p>
-<h4 id="step-1-install-rrsync-to-your-home-folder-server-side">Step 1: Install rrsync to your home folder (server-side)</h4>
-<p>If it is not already installed by your host, you can do it yourself:</p>
-<ul>
-  <li><a href="https://ftp.samba.org/pub/unpacked/rsync/support/rrsync">Download rrsync</a></li>
-  <li>Place it in the <code class="language-plaintext highlighter-rouge">bin</code> subdirectory of your home folder  (<code class="language-plaintext highlighter-rouge">~/bin</code>)</li>
-  <li>Make it executable (<code class="language-plaintext highlighter-rouge">chmod +x</code>)</li>
-</ul>
-<h4 id="step-2-set-up-certificate-based-ssh-access-server-side">Step 2: Set up certificate-based SSH access (server side)</h4>
-<p>This <a href="https://wiki.gentoo.org/wiki/SSH#Passwordless_Authentication">process</a> is
-described in several places online. What is different from the typical approach
-is to put the restriction to certificate-based authorization in
-<code class="language-plaintext highlighter-rouge">~/.ssh/authorized_keys</code>. Then, launch <code class="language-plaintext highlighter-rouge">rrsync</code> and supply
-it with the folder it shall have read-write access to:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nb">command</span><span class="o">=</span><span class="s2">"</span><span class="nv">$HOME</span><span class="s2">/bin/rrsync &lt;folder&gt;"</span>,no-agent-forwarding,no-port-forwarding,no-pty,no-user-rc,no-X11-forwarding ssh-rsa &lt;cert&gt;
-</code></pre></div></div>
-<p><code class="language-plaintext highlighter-rouge">&lt;folder&gt;</code> is the path to your site. E.g., <code class="language-plaintext highlighter-rouge">~/public_html/you.org/blog-html/</code>.</p>
-<h4 id="step-3-rsync-client-side">Step 3: Rsync (client-side)</h4>
-<p>Add the <code class="language-plaintext highlighter-rouge">deploy</code> script to the site source folder:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#!/bin/sh</span>
-rsync <span class="nt">-crvz</span> <span class="nt">--rsh</span><span class="o">=</span><span class="s1">'ssh -p2222'</span> <span class="nt">--delete-after</span> <span class="nt">--delete-excluded</span>   &lt;folder&gt; &lt;user&gt;@&lt;site&gt;:
-</code></pre></div></div>
-<p>Command line parameters are:</p>
-<ul>
-  <li><code class="language-plaintext highlighter-rouge">--rsh=ssh -p2222</code> — The port for SSH access. It is required if
-your host uses a different port than the default (e.g, HostGator)</li>
-  <li><code class="language-plaintext highlighter-rouge">&lt;folder&gt;</code> — The name of the local output folder (defaults to <code class="language-plaintext highlighter-rouge">_site</code>)</li>
-  <li><code class="language-plaintext highlighter-rouge">&lt;user&gt;</code> — The username for your hosting account</li>
-  <li><code class="language-plaintext highlighter-rouge">&lt;site&gt;</code> — Your hosting server</li>
-</ul>
-<p>Using this setup, you might run the following command:</p>
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code>rsync <span class="nt">-crvz</span> <span class="nt">--rsh</span><span class="o">=</span><span class="s1">'ssh -p2222'</span> <span class="nt">--delete-after</span> <span class="nt">--delete-excluded</span> _site/ hostuser@example.org:
-</code></pre></div></div>
-<p>Don’t forget the column <code class="language-plaintext highlighter-rouge">:</code> after server name!</p>
-<h4 id="step-4-optional-exclude-the-transfer-script-from-being-copied-to-the-output-folder">Step 4 (Optional): Exclude the transfer script from being copied to the output folder.</h4>
-<p>This step is recommended if you use these instructions to deploy your site. If
-you put the <code class="language-plaintext highlighter-rouge">deploy</code> script in the root folder of your project, Jekyll will
-copy it to the output folder. This behavior can be changed in <code class="language-plaintext highlighter-rouge">_config.yml</code>.</p>
-<p>Just add the following line:</p>
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># Do not copy these files to the output directory</span>
-<span class="na">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="s2">"</span><span class="s">deploy"</span><span class="pi">]</span>
-</code></pre></div></div>
-<p>Alternatively, you can use an <code class="language-plaintext highlighter-rouge">rsync-exclude.txt</code> file to control which files will be transferred to your server.</p>
-<h4 id="done">Done!</h4>
-<p>Now it’s possible to publish your website simply by running the <code class="language-plaintext highlighter-rouge">deploy</code>
-script. If your SSH certificate  is <a href="https://martin.kleppmann.com/2013/05/24/improving-security-of-ssh-private-keys.html">passphrase-protected</a>, you will be asked to enter it when the
-script executes.</p>
-<h2 id="rack-jekyll">Rack-Jekyll</h2>
-<p><a href="https://github.com/adaoraul/rack-jekyll/">Rack-Jekyll</a> is an easy way to deploy your site on any Rack server such as Amazon EC2, Slicehost, Heroku, and so forth. It also can run with <a href="https://github.com/rtomayko/shotgun/">shotgun</a>, <a href="https://github.com/rack/rack">rackup</a>, <a href="https://github.com/mongrel/mongrel">mongrel</a>, <a href="https://github.com/defunkt/unicorn/">unicorn</a>, and <a href="https://github.com/adaoraul/rack-jekyll#readme">others</a>.</p>
-<p>Read <a href="http://andycroll.com/ruby/serving-a-jekyll-blog-using-heroku/">this post</a> on how to deploy to Heroku using Rack-Jekyll.</p>
-<h2 id="jekyll-admin-for-rails">Jekyll-Admin for Rails</h2>
-<p>If you want to maintain Jekyll inside your existing Rails app, <a href="https://github.com/zkarpinski/Jekyll-Admin">Jekyll-Admin</a> contains drop in code to make this possible. See Jekyll-Admin’s <a href="https://github.com/zkarpinski/Jekyll-Admin/blob/master/README">README</a> for more details.</p>
-<h2 id="amazon-s3">Amazon S3</h2>
-<p>If you want to host your site in Amazon S3, you can do so by
-using the <a href="https://github.com/laurilehmijoki/s3_website">s3_website</a>
-application. It will push your site to Amazon S3 where it can be served like
-any web server,
-dynamically scaling to almost unlimited traffic. This approach has the
-benefit of being about the cheapest hosting option available for
-low-volume blogs as you only pay for what you use.</p>
-<h2 id="openshift">OpenShift</h2>
-<p>If you’d like to deploy your site to an OpenShift gear, there’s <a href="https://github.com/openshift-quickstart/jekyll-openshift">a cartridge
-for that</a>.</p>
-    <div class="section-nav">
-      <div class="left align-right">
-            <a href="/docs/github-pages/" class="prev">Back</a>
-      </div>
-      <div class="right align-left">
-            <a href="/docs/continuous-integration/" class="next">Next</a>
-      </div>
-    </div>
-    <div class="clear"></div>
-        </article>
-      </div>
-      <div class="unit one-fifth hide-on-mobiles">
-  <aside>
-    <h4>Getting Started</h4>
-    <ul>
-  <li class=""><a href="/docs/home/">Welcome</a></li>
-  <li class=""><a href="/docs/quickstart/">Quick-start guide</a></li>
-  <li class=""><a href="/docs/installation/">Installation</a></li>
-  <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
-  <li class=""><a href="/docs/usage/">Basic Usage</a></li>
-  <li class=""><a href="/docs/structure/">Directory structure</a></li>
-  <li class=""><a href="/docs/configuration/">Configuration</a></li>
-</ul>
-    <h4>Your Content</h4>
-    <ul>
-  <li class=""><a href="/docs/frontmatter/">Front Matter</a></li>
-  <li class=""><a href="/docs/posts/">Writing posts</a></li>
-  <li class=""><a href="/docs/drafts/">Working with drafts</a></li>
-  <li class=""><a href="/docs/pages/">Creating pages</a></li>
-  <li class=""><a href="/docs/static-files/">Static Files</a></li>
-  <li class=""><a href="/docs/variables/">Variables</a></li>
-  <li class=""><a href="/docs/collections/">Collections</a></li>
-  <li class=""><a href="/docs/datafiles/">Data Files</a></li>
-  <li class=""><a href="/docs/assets/">Assets</a></li>
-  <li class=""><a href="/docs/migrations/">Blog migrations</a></li>
-</ul>
-    <h4>Customization</h4>
-    <ul>
-  <li class=""><a href="/docs/templates/">Templates</a></li>
-  <li class=""><a href="/docs/includes/">Includes</a></li>
-  <li class=""><a href="/docs/permalinks/">Permalinks</a></li>
-  <li class=""><a href="/docs/pagination/">Pagination</a></li>
-  <li class=""><a href="/docs/plugins/">Plugins</a></li>
-  <li class=""><a href="/docs/themes/">Themes</a></li>
-  <li class=""><a href="/docs/extras/">Extras</a></li>
-</ul>
-    <h4>Deployment</h4>
-    <ul>
-  <li class=""><a href="/docs/github-pages/">GitHub Pages</a></li>
-  <li class="current"><a href="/docs/deployment-methods/">Deployment methods</a></li>
-  <li class=""><a href="/docs/continuous-integration/">Continuous Integration</a></li>
-</ul>
-    <h4>Miscellaneous</h4>
-    <ul>
-  <li class=""><a href="/docs/troubleshooting/">Troubleshooting</a></li>
-  <li class=""><a href="/docs/sites/">Sites using Jekyll</a></li>
-  <li class=""><a href="/docs/resources/">Resources</a></li>
-  <li class=""><a href="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</a></li>
-  <li class=""><a href="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</a></li>
-</ul>
-    <h4>Meta</h4>
-    <ul>
-  <li class=""><a href="/docs/contributing/">Contributing</a></li>
-  <li class=""><a href="/docs/maintaining/">Maintaining Jekyll</a></li>
-  <li class=""><a href="/docs/conduct/">Code of Conduct</a></li>
-  <li class=""><a href="/docs/history/">History</a></li>
-</ul>
-  </aside>
-</div>
-      <div class="clear"></div>
-    </div>
-  </section>
-  <footer>
-  <div class="grid">
-    <div class="unit one-third center-on-mobiles">
-      <p>The contents of this website are <br />&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>
-        Proudly hosted by
-        <a href="https://github.com">
-          <img src="/img/footer-logo.png" width="100" height="30" alt="GitHub • Social coding">
-        </a>
-      </p>
-    </div>
-  </div>
-</footer>
-  <script>
-  var anchorForId = function (id) {
-    var anchor = document.createElement("a");
-    anchor.className = "header-link";
-    anchor.href      = "#" + id;
-    anchor.innerHTML = "<span class=\"sr-only\">Permalink</span><i class=\"fa fa-link\"></i>";
-    anchor.title = "Permalink";
-    return anchor;
-  };
-  var linkifyAnchors = function (level, containingElement) {
-    var headers = containingElement.getElementsByTagName("h" + level);
-    for (var h = 0; h < headers.length; h++) {
-      var header = headers[h];
-      if (typeof header.id !== "undefined" && header.id !== "") {
-        header.appendChild(anchorForId(header.id));
-      }
-    }
-  };
-  document.onreadystatechange = function () {
-    if (this.readyState === "complete") {
-      var contentBlock = document.getElementsByClassName("docs")[0] || document.getElementsByClassName("news")[0];
-      if (!contentBlock) {
-        return;
-      }
-      for (var level = 1; level <= 6; level++) {
-        linkifyAnchors(level, contentBlock);
-      }
-    }
-  };
-</script>
-  <!-- Google Analytics (https://www.google.com/analytics) -->
-  <script>
-    !function(j,e,k,y,l,L){j.GoogleAnalyticsObject=y,j[y]||(j[y]=function(){
-    (j[y].q=j[y].q||[]).push(arguments)}),j[y].l=+new Date,l=e.createElement(k),
-    L=e.getElementsByTagName(k)[0],l.src='https://www.google-analytics.com/analytics.js',
-    L.parentNode.insertBefore(l,L)}(window,document,'script','ga');
-    ga('create', 'UA-50755011-1', 'jekyllrb.com');
-    ga('send', 'pageview');
-  </script>
-  <script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script>
-<script type="text/javascript"> docsearch({
-apiKey: '50fe39c839958dfad797000f33e2ec17',
-indexName: 'jekyllrb',
-inputSelector: '#docsearch-input',
-enhancedSearchInput: true,
-debug: false // Set debug to true if you want to inspect the dropdown
-});
-</script>
-</body>
+  <meta charset="utf-8">
+  <title>Redirecting&hellip;</title>
+  <link rel="canonical" href="https://jekyllrb.com/docs/deployment/">
+  <script>location="https://jekyllrb.com/docs/deployment/"</script>
+  <meta http-equiv="refresh" content="0; url=https://jekyllrb.com/docs/deployment/">
+  <meta name="robots" content="noindex">
+  <h1>Redirecting&hellip;</h1>
+  <a href="https://jekyllrb.com/docs/deployment/">Click here if you are not redirected.</a>
 </html>