jekyll-docs 3.5.2 → 3.6.0

data/site/docs/contributing/index.html

@@ -4,13 +4,13 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.5.2">
+  <meta name="generator" content="Jekyll v3.6.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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.2.3 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Contributing | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Contributing">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/contributing/">
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
 <meta property="og:type" content="article">
-<meta property="article:published_time" content="2017-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-07:00">
 <meta name="twitter:card" content="summary">
 <meta name="twitter:site" content="@jekyllrb">
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
 <script type="application/ld+json">
-{"@context":"http://schema.org","@type":"BlogPosting","headline":"Contributing","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/contributing/"},"url":"https://jekyllrb.com/docs/contributing/"}</script>
+{"name":null,"description":"Hi there! Interested in contributing to Jekyll? We’d love your help. Jekyll is an open source project, built one contribution at a time by users like you.","url":"https://jekyllrb.com/docs/contributing/","headline":"Contributing","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/contributing/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -291,12 +291,7 @@
 
 <h2 id="where-to-get-help-or-report-a-problem">Where to get help or report a problem</h2>
 
-<ul>
-  <li>If you have a question about using Jekyll, start a discussion on <a href="https://talk.jekyllrb.com">Jekyll Talk</a>.</li>
-  <li>If you think you’ve found a bug within a Jekyll plugin, open an issue in that plugin’s 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>
-  <li>More resources are listed on our <a href="https://jekyllrb.com/help/">Help page</a>.</li>
-</ul>
+<p>See <a href="SUPPORT.md">the support guidelines</a></p>
 
 <h2 id="ways-to-contribute">Ways to contribute</h2>
 
@@ -430,6 +425,11 @@
   <li>
     <p>Don’t bump the Gem version in your pull request (if you don’t know what that means, you probably didn’t).</p>
   </li>
+  <li>
+    <p>You can use the command <code class="highlighter-rouge">script/console</code> to start a REPL to explore the result of
+Jekyll’s methods. It also provides you with helpful methods to quickly create a
+site or configuration. <a href="https://github.com/jekyll/jekyll/blob/master/script/console">Feel free to check it out!</a></p>
+  </li>
 </ul>
 
 <h2 id="running-tests-locally">Running tests locally</h2>

data/site/docs/datafiles/index.html

@@ -4,13 +4,13 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.5.2">
+  <meta name="generator" content="Jekyll v3.6.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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.2.3 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Data Files | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Data Files">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/datafiles/">
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
 <meta property="og:type" content="article">
-<meta property="article:published_time" content="2017-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-07:00">
 <meta name="twitter:card" content="summary">
 <meta name="twitter:site" content="@jekyllrb">
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
 <script type="application/ld+json">
-{"@context":"http://schema.org","@type":"BlogPosting","headline":"Data Files","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"In addition to the built-in variables available from Jekyll, you can specify your own custom data that can be accessed via the Liquid templating system.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/datafiles/"},"url":"https://jekyllrb.com/docs/datafiles/"}</script>
+{"name":null,"description":"In addition to the built-in variables available from Jekyll, you can specify your own custom data that can be accessed via the Liquid templating system.","url":"https://jekyllrb.com/docs/datafiles/","headline":"Data Files","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/datafiles/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -315,35 +315,30 @@ of code in your Jekyll templates:</p>
 
 <p>In <code class="highlighter-rouge">_data/members.yml</code>:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Eric Mill</span>
-  <span class="s">github</span><span class="pi">:</span> <span class="s">konklone</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Eric Mill</span>
+  <span class="na">github</span><span class="pi">:</span> <span class="s">konklone</span>
 
-<span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Parker Moore</span>
-  <span class="s">github</span><span class="pi">:</span> <span class="s">parkr</span>
+<span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Parker Moore</span>
+  <span class="na">github</span><span class="pi">:</span> <span class="s">parkr</span>
 
-<span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Liu Fengyun</span>
-  <span class="s">github</span><span class="pi">:</span> <span class="s">liufengyun</span>
-</code></pre>
-</div>
+<span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Liu Fengyun</span>
+  <span class="na">github</span><span class="pi">:</span> <span class="s">liufengyun</span>
+</code></pre></div></div>
 
 <p>Or <code class="highlighter-rouge">_data/members.csv</code>:</p>
 
-<div class="language-text highlighter-rouge">
-<pre class="highlight"><code>name,github
+<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>name,github
 Eric Mill,konklone
 Parker Moore,parkr
 Liu Fengyun,liufengyun
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>This data can be accessed via <code class="highlighter-rouge">site.data.members</code> (notice that the filename
 determines the variable name).</p>
 
 <p>You can now render the list of members in a template:</p>
 
-<div class="language-html highlighter-rouge">
-<pre class="highlight"><code>
+<div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
 <span class="nt">&lt;ul&gt;</span>
 {% for member in site.data.members %}
   <span class="nt">&lt;li&gt;</span>
@@ -354,8 +349,7 @@ determines the variable name).</p>
 {% endfor %}
 <span class="nt">&lt;/ul&gt;</span>
 
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p class="note info">If your Jekyll site has a lot of pages, such as with documentation websites, see the detailed examples in <a href="/tutorials/navigation/">how to build robust navigation for your site</a>.</p>
 
@@ -368,34 +362,29 @@ folder:</p>
 
 <p>In <code class="highlighter-rouge">_data/orgs/jekyll.yml</code>:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">username</span><span class="pi">:</span> <span class="s">jekyll</span>
-<span class="s">name</span><span class="pi">:</span> <span class="s">Jekyll</span>
-<span class="s">members</span><span class="pi">:</span>
-  <span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Tom Preston-Werner</span>
-    <span class="s">github</span><span class="pi">:</span> <span class="s">mojombo</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">username</span><span class="pi">:</span> <span class="s">jekyll</span>
+<span class="na">name</span><span class="pi">:</span> <span class="s">Jekyll</span>
+<span class="na">members</span><span class="pi">:</span>
+  <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Tom Preston-Werner</span>
+    <span class="na">github</span><span class="pi">:</span> <span class="s">mojombo</span>
 
-  <span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Parker Moore</span>
-    <span class="s">github</span><span class="pi">:</span> <span class="s">parkr</span>
-</code></pre>
-</div>
+  <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">Parker Moore</span>
+    <span class="na">github</span><span class="pi">:</span> <span class="s">parkr</span>
+</code></pre></div></div>
 
 <p>In <code class="highlighter-rouge">_data/orgs/doeorg.yml</code>:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">username</span><span class="pi">:</span> <span class="s">doeorg</span>
-<span class="s">name</span><span class="pi">:</span> <span class="s">Doe Org</span>
-<span class="s">members</span><span class="pi">:</span>
-  <span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">John Doe</span>
-    <span class="s">github</span><span class="pi">:</span> <span class="s">jdoe</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">username</span><span class="pi">:</span> <span class="s">doeorg</span>
+<span class="na">name</span><span class="pi">:</span> <span class="s">Doe Org</span>
+<span class="na">members</span><span class="pi">:</span>
+  <span class="pi">-</span> <span class="na">name</span><span class="pi">:</span> <span class="s">John Doe</span>
+    <span class="na">github</span><span class="pi">:</span> <span class="s">jdoe</span>
+</code></pre></div></div>
 
 <p>The organizations can then be accessed via <code class="highlighter-rouge">site.data.orgs</code>, followed by the
 file name:</p>
 
-<div class="language-html highlighter-rouge">
-<pre class="highlight"><code>
+<div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
 <span class="nt">&lt;ul&gt;</span>
 {% for org_hash in site.data.orgs %}
 {% assign org = org_hash[1] %}
@@ -408,8 +397,7 @@ file name:</p>
 {% endfor %}
 <span class="nt">&lt;/ul&gt;</span>
 
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <h2 id="example-accessing-a-specific-author">Example: Accessing a specific author</h2>
 
@@ -417,17 +405,14 @@ file name:</p>
 
 <p><code class="highlighter-rouge">_data/people.yml</code>:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">dave</span><span class="pi">:</span>
-    <span class="s">name</span><span class="pi">:</span> <span class="s">David Smith</span>
-    <span class="s">twitter</span><span class="pi">:</span> <span class="s">DavidSilvaSmith</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">dave</span><span class="pi">:</span>
+    <span class="na">name</span><span class="pi">:</span> <span class="s">David Smith</span>
+    <span class="na">twitter</span><span class="pi">:</span> <span class="s">DavidSilvaSmith</span>
+</code></pre></div></div>
 
 <p>The author can then be specified as a page variable in a post’s frontmatter:</p>
 
-<div class="language-html highlighter-rouge">
-<pre class="highlight"><code>
+<div class="language-html highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
 ---
 title: sample post
 author: dave
@@ -441,8 +426,7 @@ author: dave
 <span class="nt">&lt;/a&gt;</span>
 
 
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>For information on how to build robust navigation for your site (especially if you have a documentation website or another type of Jekyll site with a lot of pages to organize), see <a href="/tutorials/navigation">Navigation</a>.</p>
 

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

@@ -4,13 +4,13 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.5.2">
+  <meta name="generator" content="Jekyll v3.6.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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.2.3 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Deployment methods | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Deployment methods">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <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="2017-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-07:00">
 <meta name="twitter:card" content="summary">
 <meta name="twitter:site" content="@jekyllrb">
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
 <script type="application/ld+json">
-{"@context":"http://schema.org","@type":"BlogPosting","headline":"Deployment methods","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","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.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/deployment-methods/"},"url":"https://jekyllrb.com/docs/deployment-methods/"}</script>
+{"name":null,"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.","url":"https://jekyllrb.com/docs/deployment-methods/","headline":"Deployment methods","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/deployment-methods/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -289,6 +289,31 @@
           <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 our <a href="https://www.aerobatic.com/docs/static-site-generators/#jekyll">Jekyll docs</a> for more details. Your built <code class="highlighter-rouge">_site</code> folder is deployed to our 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="highlighter-rouge">jekyll build</code> command and copy the contents of the generated <code class="highlighter-rouge">_site</code> folder to the root folder of your hosting account. This is most likely to be the <code class="highlighter-rouge">httpdocs</code> or <code class="highlighter-rouge">public_html</code> folder on most hosting providers.</p>
@@ -313,46 +338,38 @@ this</a>.</p>
 
 <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="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">
-<pre class="highlight"><code><span class="gp">laptop$ </span>ssh deployer@example.com
-<span class="gp">server$ </span>mkdir myrepo.git
-<span class="gp">server$ </span><span class="nb">cd </span>myrepo.git
-<span class="gp">server$ </span>git --bare init
-<span class="gp">server$ </span>cp hooks/post-receive.sample hooks/post-receive
-<span class="gp">server$ </span>mkdir /var/www/myrepo
-</code></pre>
-</div>
+<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>mkdir 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>cp hooks/post-receive.sample hooks/post-receive
+server<span class="nv">$ </span>mkdir /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-sh highlighter-rouge">
-<pre class="highlight"><code><span class="nv">GIT_REPO</span><span class="o">=</span><span class="nv">$HOME</span>/myrepo.git
+<div class="language-sh 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">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>
-jekyll build -s <span class="nv">$TMP_GIT_CLONE</span> -d <span class="nv">$PUBLIC_WWW</span>
-rm -Rf <span class="nv">$TMP_GIT_CLONE</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>
+rm <span class="nt">-Rf</span> <span class="nv">$TMP_GIT_CLONE</span>
 <span class="nb">exit</span>
-</code></pre>
-</div>
+</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">
-<pre class="highlight"><code><span class="gp">laptops$ </span>git remote add deploy deployer@example.com:~/myrepo.git
-</code></pre>
-</div>
+<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="highlighter-rouge">/var/www/myrepo</code> and running the following:</p>
 
-<div class="language-sh highlighter-rouge">
-<pre class="highlight"><code><span class="gp">laptops$ </span>git push deploy master
-</code></pre>
-</div>
+<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>
 
@@ -395,10 +412,8 @@ is to put the restriction to certificate-based authorization in
 <code class="highlighter-rouge">~/.ssh/authorized_keys</code>. Then, launch <code class="highlighter-rouge">rrsync</code> and supply
 it with the folder it shall have read-write access to:</p>
 
-<div class="language-sh highlighter-rouge">
-<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 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="highlighter-rouge">&lt;folder&gt;</code> is the path to your site. E.g., <code class="highlighter-rouge">~/public_html/you.org/blog-html/</code>.</p>
 
@@ -406,12 +421,10 @@ it with the folder it shall have read-write access to:</p>
 
 <p>Add the <code class="highlighter-rouge">deploy</code> script to the site source folder:</p>
 
-<div class="language-sh highlighter-rouge">
-<pre class="highlight"><code><span class="c">#!/bin/sh</span>
+<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#!/bin/sh</span>
 
-rsync -crvz --rsh<span class="o">=</span><span class="s1">'ssh -p2222'</span> --delete-after --delete-excluded   &lt;folder&gt; &lt;user&gt;@&lt;site&gt;:
-</code></pre>
-</div>
+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>
 
@@ -429,10 +442,8 @@ your host uses a different port than the default (e.g, HostGator)</li>
 
 <p>Using this setup, you might run the following command:</p>
 
-<div class="language-sh highlighter-rouge">
-<pre class="highlight"><code>rsync -crvz --rsh<span class="o">=</span><span class="s1">'ssh -p2222'</span> --delete-after --delete-excluded _site/ hostuser@example.org:
-</code></pre>
-</div>
+<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="highlighter-rouge">:</code> after server name!</p>
 
@@ -444,11 +455,9 @@ copy it to the output folder. This behavior can be changed in <code class="highl
 
 <p>Just add the following line:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="c1"># Do not copy these files to the output directory</span>
-<span class="s">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 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="highlighter-rouge">rsync-exclude.txt</code> file to control which files will be transferred to your server.</p>
 
@@ -483,25 +492,6 @@ low-volume blogs as you only pay for what you use.</p>
 <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="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="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="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 our <a href="https://www.aerobatic.com/docs/static-site-generators/#jekyll">Jekyll docs</a> for more details. Your built <code class="highlighter-rouge">_site</code> folder is deployed to our highly-available, globally distributed hosting service.</p>
-
           
 
 

data/site/docs/drafts/index.html

@@ -4,13 +4,13 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.5.2">
+  <meta name="generator" content="Jekyll v3.6.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="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.2.3 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Working with drafts | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Working with drafts">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/drafts/">
 <meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites">
 <meta property="og:type" content="article">
-<meta property="article:published_time" content="2017-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-07:00">
 <meta name="twitter:card" content="summary">
 <meta name="twitter:site" content="@jekyllrb">
 <meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY">
 <script type="application/ld+json">
-{"@context":"http://schema.org","@type":"BlogPosting","headline":"Working with drafts","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"Drafts are posts without a date. They’re posts you’re still working on and don’t want to publish yet. To get up and running with drafts, create a _drafts folder in your site’s root (as described in the site structure section) and create your first draft:","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/drafts/"},"url":"https://jekyllrb.com/docs/drafts/"}</script>
+{"name":null,"description":"Drafts are posts without a date. They’re posts you’re still working on and don’t want to publish yet. To get up and running with drafts, create a _drafts folder in your site’s root (as described in the site structure section) and create your first draft:","url":"https://jekyllrb.com/docs/drafts/","headline":"Working with drafts","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/drafts/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -292,11 +292,9 @@ don’t want to publish yet. To get up and running with drafts, create a
 <code class="highlighter-rouge">_drafts</code> folder in your site’s root (as described in the <a href="/docs/structure/">site structure</a> section) and create your
 first draft:</p>
 
-<div class="language-text highlighter-rouge">
-<pre class="highlight"><code>|-- _drafts/
+<div class="language-text highlighter-rouge"><div class="highlight"><pre class="highlight"><code>|-- _drafts/
 |   |-- a-draft-post.md
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>To preview your site with drafts, simply run <code class="highlighter-rouge">jekyll serve</code> or <code class="highlighter-rouge">jekyll build</code>
 with the <code class="highlighter-rouge">--drafts</code> switch. Each will be assigned the value modification time