jekyll-docs 3.4.3 → 3.5.1

data/site/docs/themes/index.html

@@ -4,35 +4,28 @@
 <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>Themes - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Themes | Jekyll • Simple, blog-aware, static sites</title>
 <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 package up layouts, includes, and stylesheets in a way that can be overridden by your site’s content.">
 <meta property="og: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 package up layouts, includes, and stylesheets in a way that can be overridden by your site’s content.">
 <link rel="canonical" href="https://jekyllrb.com/docs/themes/">
 <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="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": "Themes",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"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 package up 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"}},
-"url": "https://jekyllrb.com/docs/themes/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Themes","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","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 package up 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"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/themes/"},"url":"https://jekyllrb.com/docs/themes/"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -62,7 +55,7 @@
     <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>
 
@@ -94,7 +87,7 @@
     <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>
 
@@ -126,6 +119,10 @@
 
   
   
+  <option value="/docs/windows/">Jekyll on Windows</option>
+
+  
+  
   <option value="/docs/usage/">Basic Usage</option>
 
   
@@ -323,26 +320,17 @@
 
 <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>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>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>
-</ul>
+<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 class="note info">Refer to your selected theme’s documentation and source repository for more information on what files you can 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>To locate theme’s files on your computer:</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 default Jekyll’s theme.</p>
+    <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>This returns the location of the gem-based theme files. For example, Minima theme’s files are 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="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>
@@ -385,13 +373,28 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
      └── main.scss
 </code></pre>
     </div>
-
-    <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 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>
   </li>
 </ol>
 
+<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>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>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>
+</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>
+
+<p class="note info">Refer to your selected theme’s documentation and source repository for more information on what files you can override.</p>
+
 <h2 id="converting-gem-based-themes-to-regular-themes">Converting gem-based themes to regular themes</h2>
 
 <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>
@@ -450,7 +453,7 @@ explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
   </li>
 </ol>
 
-<p>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>. {: .note .info }</p>
+<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>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>
 
@@ -494,7 +497,7 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
 <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>
 
 <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 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>
 
@@ -519,6 +522,12 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
 </code></pre>
 </div>
 
+<h3 id="theme-gem-dependencies">Theme-gem dependencies</h3>
+
+<p>From <code class="highlighter-rouge">v3.5</code>, 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">gems</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>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>
@@ -531,7 +540,7 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
 
 <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>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. {: .info .note}</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>
 
 <h3 id="publishing-your-theme">Publishing your theme</h3>
 
@@ -539,7 +548,17 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
 
 <ol>
   <li>
-    <p>First, 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>First, you need to have it in a git repository:</p>
+
+    <div class="language-sh highlighter-rouge">
+<pre class="highlight"><code>git init <span class="c"># Only the first time</span>
+git add -A
+git commit -m <span class="s2">"Init commit"</span>
+</code></pre>
+    </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>
 
     <div class="language-sh highlighter-rouge">
 <pre class="highlight"><code>gem build jekyll-theme-awesome.gemspec
@@ -547,7 +566,7 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
     </div>
   </li>
   <li>
-    <p>Next, 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="highlighter-rouge">jekyll-theme-awesome</code> with the name of your theme:</p>
 
     <div class="language-sh highlighter-rouge">
 <pre class="highlight"><code>gem push jekyll-theme-awesome-<span class="k">*</span>.gem
@@ -555,7 +574,7 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
     </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 &amp; 2 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="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>
 
@@ -626,6 +645,9 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
   
 
   
+  
+
+  
   
 
   
@@ -671,6 +693,10 @@ For <span class="nb">help </span>getting started, <span class="nb">read</span> /
 
   
   
+  <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
+
+  
+  
   <li class=""><a href="/docs/usage/">Basic Usage</a></li>
 
   

data/site/docs/troubleshooting/index.html

@@ -4,35 +4,28 @@
 <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>Troubleshooting - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Troubleshooting | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Troubleshooting">
+<meta property="og:locale" content="en_US">
 <meta name="description" content="If you ever run into problems installing or using Jekyll, here are a few tips that might be of help. If the problem you’re experiencing isn’t covered below, please check out our other help resources as well.">
 <meta property="og:description" content="If you ever run into problems installing or using Jekyll, here are a few tips that might be of help. If the problem you’re experiencing isn’t covered below, please check out our other help resources as well.">
 <link rel="canonical" href="https://jekyllrb.com/docs/troubleshooting/">
 <meta property="og:url" content="https://jekyllrb.com/docs/troubleshooting/">
 <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": "Troubleshooting",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"description": "If you ever run into problems installing or using Jekyll, here are a few tips that might be of help. If the problem you’re experiencing isn’t covered below, please check out our other help resources as well.",
-"publisher": {"@type": "Organization",
-"logo": {"@type": "ImageObject",
-"url": "https://jekyllrb.com/img/logo-2x.png"}},
-"url": "https://jekyllrb.com/docs/troubleshooting/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Troubleshooting","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"If you ever run into problems installing or using Jekyll, here are a few tips that might be of help. If the problem you’re experiencing isn’t covered below, please check out our other help resources as well.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/troubleshooting/"},"url":"https://jekyllrb.com/docs/troubleshooting/"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -62,7 +55,7 @@
     <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>
 
@@ -94,7 +87,7 @@
     <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>
 
@@ -126,6 +119,10 @@
 
   
   
+  <option value="/docs/windows/">Jekyll on Windows</option>
+
+  
+  
   <option value="/docs/usage/">Basic Usage</option>
 
   
@@ -306,7 +303,7 @@ that might be of help. If the problem you’re experiencing isn’t covered belo
 <h2 id="installation-problems">Installation Problems</h2>
 
 <p>If you encounter errors during gem installation, you may need to install
-the header files for compiling extension modules for Ruby 2.0.0. This
+the header files for compiling extension modules for Ruby 2.x This
 can be done on Ubuntu or Debian by running:</p>
 
 <div class="language-sh highlighter-rouge">
@@ -328,6 +325,17 @@ can be done on Ubuntu or Debian by running:</p>
 </code></pre>
 </div>
 
+<p>On Ubuntu if you get stuck after <code class="highlighter-rouge">bundle exec jekyll serve</code> and see error
+messages like <code class="highlighter-rouge">Could not locate Gemfile</code> or <code class="highlighter-rouge">.bundle/ directory</code>, it’s likely
+because all requirements have not been fully met. Recent stock Ubuntu
+distributions require the installation of both the <code class="highlighter-rouge">ruby</code> and <code class="highlighter-rouge">ruby-all-dev</code>
+packages:</p>
+
+<div class="language-sh highlighter-rouge">
+<pre class="highlight"><code>sudo apt-get install ruby ruby-all-dev
+</code></pre>
+</div>
+
 <p>On <a href="https://www.nearlyfreespeech.net/">NearlyFreeSpeech</a> you need to run the
 following commands before installing Jekyll:</p>
 
@@ -349,6 +357,13 @@ following commands before installing Jekyll:</p>
 <p>On Windows, you may need to install <a href="https://wiki.github.com/oneclick/rubyinstaller/development-kit">RubyInstaller
 DevKit</a>.</p>
 
+<p>On Android (with Termux) you can install all requirements by running:</p>
+
+<div class="language-sh highlighter-rouge">
+<pre class="highlight"><code>apt update <span class="o">&amp;&amp;</span> apt install libffi-dev clang ruby-dev make
+</code></pre>
+</div>
+
 <p>On macOS, you may need to update RubyGems (using <code class="highlighter-rouge">sudo</code> only if necessary):</p>
 
 <div class="language-sh highlighter-rouge">
@@ -481,9 +496,9 @@ is as follows:</p>
 and flags specified at the command-line will override all other settings
 specified elsewhere.</p>
 
-<p>If you encounter an error in building the site, with the error message 
-“‘0000-00-00-welcome-to-jekyll.markdown.erb’ does not have a valid date in the 
-YAML front matter.” try including the line <code class="highlighter-rouge">exclude: [vendor]</code> 
+<p>If you encounter an error in building the site, with the error message
+“‘0000-00-00-welcome-to-jekyll.markdown.erb’ does not have a valid date in the
+YAML front matter.” try including the line <code class="highlighter-rouge">exclude: [vendor]</code>
 in <code class="highlighter-rouge">_config.yml</code>.</p>
 
 <h2 id="markup-problems">Markup Problems</h2>
@@ -609,6 +624,9 @@ The issue is caused by trying to copy a non-existing symlink.</p>
   
 
   
+  
+
+  
   
 
   
@@ -654,6 +672,10 @@ The issue is caused by trying to copy a non-existing symlink.</p>
 
   
   
+  <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
+
+  
+  
   <li class=""><a href="/docs/usage/">Basic Usage</a></li>
 
   

data/site/docs/upgrading/0-to-2/index.html

@@ -4,35 +4,28 @@
 <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>Upgrading from 0.x to 2.x - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Upgrading from 0.x to 2.x | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Upgrading from 0.x to 2.x">
+<meta property="og:locale" content="en_US">
 <meta name="description" content="Upgrading from an older version of Jekyll? A few things have changed in 1.0 and 2.0 that you’ll want to know about.">
 <meta property="og:description" content="Upgrading from an older version of Jekyll? A few things have changed in 1.0 and 2.0 that you’ll want to know about.">
 <link rel="canonical" href="https://jekyllrb.com/docs/upgrading/0-to-2/">
 <meta property="og:url" content="https://jekyllrb.com/docs/upgrading/0-to-2/">
 <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": "Upgrading from 0.x to 2.x",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"description": "Upgrading from an older version of Jekyll? A few things have changed in 1.0 and 2.0 that you’ll want to know about.",
-"publisher": {"@type": "Organization",
-"logo": {"@type": "ImageObject",
-"url": "https://jekyllrb.com/img/logo-2x.png"}},
-"url": "https://jekyllrb.com/docs/upgrading/0-to-2/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Upgrading from 0.x to 2.x","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"Upgrading from an older version of Jekyll? A few things have changed in 1.0 and 2.0 that you’ll want to know about.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/upgrading/0-to-2/"},"url":"https://jekyllrb.com/docs/upgrading/0-to-2/"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -62,7 +55,7 @@
     <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>
 
@@ -94,7 +87,7 @@
     <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>
 
@@ -126,6 +119,10 @@
 
   
   
+  <option value="/docs/windows/">Jekyll on Windows</option>
+
+  
+  
   <option value="/docs/usage/">Basic Usage</option>
 
   
@@ -524,6 +521,9 @@ you’d expect in both environments.</p>
   
 
   
+  
+
+  
   
 
   
@@ -569,6 +569,10 @@ you’d expect in both environments.</p>
 
   
   
+  <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
+
+  
+  
   <li class=""><a href="/docs/usage/">Basic Usage</a></li>