index.html in jekyll-docs-3.5.1

- old
+ new

@@ -2,39 +2,32 @@
 <html lang="en-US">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.4.3">
+  <meta name="generator" content="Jekyll v3.5.1">
   <link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites">
   <link rel="alternate" type="application/atom+xml" title="Recent commits to Jekyll’s master branch" href="https://github.com/jekyll/jekyll/commits/master.atom">
   <link rel="stylesheet" href="//fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
   <link rel="stylesheet" href="/css/screen.css">
   <link rel="icon" type="image/x-icon" href="/favicon.ico">
-  <!-- Begin Jekyll SEO tag v2.1.0 -->
-<title>Deployment methods - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Deployment methods | Jekyll • Simple, blog-aware, static sites</title>
 <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="2017-03-22T08:08:47-07:00">
+<meta property="article:published_time" content="2017-07-17T13:16:40-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-03-22T08:08:47-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"}},
-"url": "https://jekyllrb.com/docs/deployment-methods/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Deployment methods","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-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>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
   <script src="/js/html5shiv.min.js"></script>
   <script src="/js/respond.min.js"></script>
@@ -60,11 +53,11 @@
   </li>
   <li class="">
     <a href="/help/">Help</a>
   </li>
   <li>
-    <a href="https://github.com/jekyll/jekyll"><span class="hide-on-mobiles">View on </span>GitHub</a>
+    <a href="https://github.com/jekyll/jekyll">GitHub</a>
   </li>
 </ul>
 
   </nav>
   <div class="grid">
@@ -92,11 +85,11 @@
   </li>
   <li class="">
     <a href="/help/">Help</a>
   </li>
   <li>
-    <a href="https://github.com/jekyll/jekyll"><span class="hide-on-mobiles">View on </span>GitHub</a>
+    <a href="https://github.com/jekyll/jekyll">GitHub</a>
   </li>
 </ul>
 
     </nav>
   </div>
@@ -124,10 +117,14 @@
   
   <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>
@@ -292,11 +289,11 @@
           <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>
 
 <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 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>
+<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>
 
 <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="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="highlighter-rouge">_site</code> folder get placed in the appropriate web root directory for your web server.</p>
 
@@ -366,18 +363,18 @@
 <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="highlighter-rouge">_site</code> directory, you can easily scp it using a
+<p>Once you’ve generated the <code class="highlighter-rouge">_site</code> directory, you can easily scp its content using a
 <code class="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="highlighter-rouge">_site</code> directory, you can easily rsync it using a <code class="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>Once you’ve generated the <code class="highlighter-rouge">_site</code> directory, you can easily rsync its content using a <code class="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>
@@ -499,13 +496,13 @@
 
 <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> is an add-on for Bitbucket that brings GitHub Pages style functionality to Bitbucket users. It includes continuous deployment, custom domains with a wildcard SSL cert, CDN, basic auth, and staging branches all in the box.</p>
+<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 build and deployment of a Jekyll site is just as simple as GitHub Pages - push your changes to your repo (excluding the <code class="highlighter-rouge">_site</code> directory) and within seconds a build will be triggered and your built site deployed to our highly- available, globally distributed hosting service. The build process will even install and execute custom Ruby plugins. See our <a href="https://www.aerobatic.com/docs/static-generators#jekyll">Jekyll docs</a> for more details.</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>
 
           
 
 
 
@@ -583,10 +580,13 @@
   
   
 
   
   
+
+  
+  
     <div class="section-nav">
       <div class="left align-right">
           
             
             
@@ -621,9 +621,13 @@
   <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>
 