jekyll-docs 3.4.3 → 3.5.1

data/site/docs/assets/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>Assets - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Assets | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Assets">
+<meta property="og:locale" content="en_US">
 <meta name="description" content="Jekyll provides built-in support for Sass and can work with CoffeeScript via a Ruby gem. In order to use them, you must first create a file with the proper extension name (one of .sass, .scss, or .coffee) and start the file with two lines of triple dashes, like this:">
 <meta property="og:description" content="Jekyll provides built-in support for Sass and can work with CoffeeScript via a Ruby gem. In order to use them, you must first create a file with the proper extension name (one of .sass, .scss, or .coffee) and start the file with two lines of triple dashes, like this:">
 <link rel="canonical" href="https://jekyllrb.com/docs/assets/">
 <meta property="og:url" content="https://jekyllrb.com/docs/assets/">
 <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": "Assets",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"description": "Jekyll provides built-in support for Sass and can work with CoffeeScript via a Ruby gem. In order to use them, you must first create a file with the proper extension name (one of .sass, .scss, or .coffee) and start the file with two lines of triple dashes, like this:",
-"publisher": {"@type": "Organization",
-"logo": {"@type": "ImageObject",
-"url": "https://jekyllrb.com/img/logo-2x.png"}},
-"url": "https://jekyllrb.com/docs/assets/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Assets","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"Jekyll provides built-in support for Sass and can work with CoffeeScript via a Ruby gem. In order to use them, you must first create a file with the proper extension name (one of .sass, .scss, or .coffee) and start the file with two lines of triple dashes, like this:","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/assets/"},"url":"https://jekyllrb.com/docs/assets/"}</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>
 
   
@@ -377,7 +374,7 @@ here, too.</p>
 </ul>
 
 <div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">gems</span><span class="pi">:</span>
+<pre class="highlight"><code><span class="s">plugins</span><span class="pi">:</span>
  <span class="pi">-</span> <span class="s">jekyll-coffeescript</span>
 </code></pre>
 </div>
@@ -428,6 +425,9 @@ here, too.</p>
   
 
   
+  
+
+  
   
 
   
@@ -473,6 +473,10 @@ here, too.</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/collections/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>Collections - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Collections | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Collections">
+<meta property="og:locale" content="en_US">
 <meta name="description" content="Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.">
 <meta property="og:description" content="Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.">
 <link rel="canonical" href="https://jekyllrb.com/docs/collections/">
 <meta property="og:url" content="https://jekyllrb.com/docs/collections/">
 <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": "Collections",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"description": "Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.",
-"publisher": {"@type": "Organization",
-"logo": {"@type": "ImageObject",
-"url": "https://jekyllrb.com/img/logo-2x.png"}},
-"url": "https://jekyllrb.com/docs/collections/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Collections","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/collections/"},"url":"https://jekyllrb.com/docs/collections/"}</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>
 
   
@@ -382,19 +379,94 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
 
 <h2 id="permalinks">Configuring permalinks for collections</h2>
 
-<p>You can customize the <a href="../permalinks/">Permalinks</a> for your collection’s documents by setting <code class="highlighter-rouge">permalink</code> property in the collection’s configuration as follows:</p>
+<p>If you wish to specify a custom pattern for the URLs where your Collection pages
+will reside, you may do so with the <a href="../permalinks/"><code class="highlighter-rouge">permalink</code> property</a>:</p>
 
 <div class="language-yaml highlighter-rouge">
 <pre class="highlight"><code><span class="s">collections</span><span class="pi">:</span>
   <span class="s">my_collection</span><span class="pi">:</span>
     <span class="s">output</span><span class="pi">:</span> <span class="s">true</span>
-    <span class="s">permalink</span><span class="pi">:</span> <span class="s">/awesome/:path/:title.:output_ext</span>
+    <span class="s">permalink</span><span class="pi">:</span> <span class="s">/:collection/:name</span>
+</code></pre>
+</div>
+
+<h3 id="examples">Examples</h3>
+
+<p>For a collection with the following source file structure,</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>_my_collection/
+└── some_subdir
+    └── some_doc.md
 </code></pre>
 </div>
 
-<p>In this example, the collection documents will the have the URL of <code class="highlighter-rouge">awesome</code> followed by the path to the document and its file extension.</p>
+<p>each of the following <code class="highlighter-rouge">permalink</code> configurations will produce the document structure shown below it.</p>
+
+<ul>
+  <li>
+    <p><strong>Default</strong><br>
+Same as <code class="highlighter-rouge">permalink: /:collection/:path</code>.</p>
+
+    <div class="highlighter-rouge">
+<pre class="highlight"><code>_site/
+├── my_collection
+│   └── some_subdir
+│       └── some_doc.html
+...
+</code></pre>
+    </div>
+  </li>
+  <li>
+    <p><code class="highlighter-rouge">permalink: pretty</code><br>
+Same as <code class="highlighter-rouge">permalink: /:collection/:path/</code>.</p>
+
+    <div class="highlighter-rouge">
+<pre class="highlight"><code>_site/
+├── my_collection
+│   └── some_subdir
+│       └── some_doc
+│           └── index.html
+...
+</code></pre>
+    </div>
+  </li>
+  <li>
+    <p><code class="highlighter-rouge">permalink: /doc/:path</code></p>
+
+    <div class="highlighter-rouge">
+<pre class="highlight"><code>_site/
+├── doc
+│   └── some_subdir
+│       └── some_doc.html
+...
+</code></pre>
+    </div>
+  </li>
+  <li>
+    <p><code class="highlighter-rouge">permalink: /doc/:name</code></p>
+
+    <div class="highlighter-rouge">
+<pre class="highlight"><code>_site/
+├── doc
+│   └── some_doc.html
+...
+</code></pre>
+    </div>
+  </li>
+  <li>
+    <p><code class="highlighter-rouge">permalink: /:name</code></p>
+
+    <div class="highlighter-rouge">
+<pre class="highlight"><code>_site/
+├── some_doc.html
+...
+</code></pre>
+    </div>
+  </li>
+</ul>
 
-<p>Collections have the following template variables available for permalinks:</p>
+<h3 id="template-variables">Template Variables</h3>
 
 <div class="mobile-side-scroller">
 <table>
@@ -407,7 +479,7 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
   <tbody>
     <tr>
       <td>
-        <p><code>collection</code></p>
+        <p><code>:collection</code></p>
       </td>
       <td>
         <p>Label of the containing collection.</p>
@@ -415,7 +487,7 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
     </tr>
     <tr>
       <td>
-        <p><code>path</code></p>
+        <p><code>:path</code></p>
       </td>
       <td>
         <p>Path to the document relative to the collection's directory.</p>
@@ -423,7 +495,7 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
     </tr>
     <tr>
       <td>
-        <p><code>name</code></p>
+        <p><code>:name</code></p>
       </td>
       <td>
         <p>The document's base filename, with every sequence of spaces
@@ -432,7 +504,7 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
     </tr>
     <tr>
       <td>
-        <p><code>title</code></p>
+        <p><code>:title</code></p>
       </td>
       <td>
         <p>The document's lowercase title (as defined in its <a href="/docs/frontmatter/">front matter</a>), with every sequence of spaces and non-alphanumeric characters replaced by a hyphen. If the document does not define a title in its <a href="/docs/frontmatter/">front matter</a>, this is equivalent to <code>name</code>.</p>
@@ -440,100 +512,16 @@ choice and written out to <code class="highlighter-rouge">&lt;dest&gt;/my_collec
     </tr>
     <tr>
       <td>
-        <p><code>output_ext</code></p>
+        <p><code>:output_ext</code></p>
       </td>
       <td>
-        <p>Extension of the output file.</p>
+        <p>Extension of the output file. (Included by default and usually unnecessary.)</p>
       </td>
     </tr>
   </tbody>
 </table>
 </div>
 
-<h2 id="permalink-examples-for-collections">Permalink examples for collections</h2>
-
-<p>Depending on how you declare the permalinks in your configuration file, the permalinks and paths get written differently in the <code class="highlighter-rouge">_site</code> folder. A few examples will help clarify the options.</p>
-
-<p>Let’s say your collection is called <code class="highlighter-rouge">apidocs</code> with <code class="highlighter-rouge">doc1.md</code> in your collection. <code class="highlighter-rouge">doc1.md</code> is grouped inside a folder called <code class="highlighter-rouge">mydocs</code>. Your project’s source directory for the collection looks this:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── \_apidocs
-│   └── mydocs
-│       └── doc1.md
-</code></pre>
-</div>
-
-<p>Based on this scenario, here are a few permalink options.</p>
-
-<p><strong>Permalink configuration 1</strong>: [Nothing configured] <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── apidocs
-│   └── mydocs
-│       └── doc1.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 2</strong>: <code class="highlighter-rouge">/:collection/:path/:title:output_ext</code>  <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── apidocs
-│   └── mydocs
-│       └── doc1.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 3</strong>: No collection permalinks configured, but <code class="highlighter-rouge">pretty</code> configured for pages/posts. <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── apidocs
-│   └── mydocs
-│       └── doc1
-│           └── index.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 4</strong>: <code class="highlighter-rouge">/awesome/:path/:title.html</code>   <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── awesome
-│   └── mydocs
-│       └── doc1.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 5</strong>: <code class="highlighter-rouge">/awesome/:path/:title/</code>  <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── awesome
-│   └── mydocs
-│       └── doc1
-│           └── index.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 6</strong>: <code class="highlighter-rouge">/awesome/:title.html</code> <br>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── awesome
-│   └── doc1.html
-</code></pre>
-</div>
-
-<p><strong>Permalink configuration 7</strong>: <code class="highlighter-rouge">:title.html</code>
-<strong>Output</strong>:</p>
-
-<div class="highlighter-rouge">
-<pre class="highlight"><code>├── doc1.html
-</code></pre>
-</div>
-
 <h2 id="liquid-attributes">Liquid Attributes</h2>
 
 <h3 id="collections">Collections</h3>
@@ -623,6 +611,17 @@ you specified in your <code class="highlighter-rouge">_config.yml</code> (if pre
 </table>
 </div>
 
+<div class="note info">
+  <h5>A Hard-Coded Collection</h5>
+  <p>In addition to any collections you create yourself, the 
+  <code>posts</code> collection is hard-coded into Jekyll. It exists whether 
+  you have a <code>_posts</code> directory or not. This is something to note 
+  when iterating through <code>site.collections</code> as you may need to 
+  filter it out.</p>
+  <p>You may wish to use filters to find your collection:
+  <code>{{ site.collections | where: "label", "myCollection" | first }}</code></p>
+</div>
+
 <h3 id="documents">Documents</h3>
 
 <p>In addition to any YAML Front Matter provided in the document’s corresponding
@@ -806,6 +805,9 @@ extension):</p>
   
 
   
+  
+
+  
   
 
   
@@ -851,6 +853,10 @@ extension):</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/conduct/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>Code of Conduct - Jekyll • Simple, blog-aware, static sites</title>
+  <!-- Begin Jekyll SEO tag v2.2.3 -->
+<title>Code of Conduct | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Code of Conduct">
+<meta property="og:locale" content="en_US">
 <meta name="description" content="As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.">
 <meta property="og:description" content="As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.">
 <link rel="canonical" href="https://jekyllrb.com/docs/conduct/">
 <meta property="og:url" content="https://jekyllrb.com/docs/conduct/">
 <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": "Code of Conduct",
-"datePublished": "2017-03-22T08:08:47-07:00",
-"description": "As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.",
-"publisher": {"@type": "Organization",
-"logo": {"@type": "ImageObject",
-"url": "https://jekyllrb.com/img/logo-2x.png"}},
-"url": "https://jekyllrb.com/docs/conduct/"}</script>
+{"@context":"http://schema.org","@type":"BlogPosting","headline":"Code of Conduct","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/conduct/"},"url":"https://jekyllrb.com/docs/conduct/"}</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>
 
   
@@ -440,6 +437,9 @@ version 1.3.0, available at
   
 
   
+  
+
+  
   
 
   
@@ -485,6 +485,10 @@ version 1.3.0, available at
 
   
   
+  <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
+
+  
+  
   <li class=""><a href="/docs/usage/">Basic Usage</a></li>