jekyll-docs 3.4.3 → 3.5.1

data/site/philosophy.html

@@ -0,0 +1,46 @@
+<p>Jekyll offers a unique philosophy when approaching the problem of static
+site generation. This core philosophy drives development and product
+decisions. When a contributor, maintainer, or user asks herself what Jekyll
+is about, the following principles should come to mind:</p>
+
+<h3 id="1-no-magic">1. No Magic</h3>
+
+<p>Jekyll is not magic. A user should be able to understand the underlying
+processes that make up the Jekyll build without much reading. It should
+do only what you ask it to and nothing more. When a user takes a certain
+action, the outcome should be easily understandable and focused.</p>
+
+<h3 id="2-it-just-works">2. It “Just Works”</h3>
+
+<p>The out-of-the-box experience should be that it “just works.” Run
+<code class="highlighter-rouge">gem install jekyll</code> and it should build any Jekyll site that it’s given.
+Features like auto-regeneration and settings like the markdown renderer
+should represent sane defaults that work perfectly for the vast majority of
+cases. The burden of initial configuration should not be placed on the user.</p>
+
+<h3 id="3-content-is-king">3. Content is King</h3>
+
+<p>Why is Jekyll so loved by content creators? It focuses on content first and
+foremost, making the process of publishing content on the Web easy. Users
+should find the management of their content enjoyable and simple.</p>
+
+<h3 id="4-stability">4. Stability</h3>
+
+<p>If a user’s site builds today, it should build tomorrow.
+Backwards-compatibility should be strongly preferred over breaking changes.
+Breaking changes should be made to support a strong practical goal, and
+breaking changes should never be made to drive forward “purity” of the
+codebase, or other changes purely to make the maintainers’ lives easier.
+Breaking changes provide a significant amount of friction between upgrades
+and reduce the confidence of users in this software, and should thus be
+avoided unless absolutely necessary.
+Upon breaking changes, provide a clear path for users to upgrade.</p>
+
+<h3 id="5-small--extensible">5. Small &amp; Extensible</h3>
+
+<p>The core of Jekyll should be simple and small, and extensibility should be
+a first-class feature to provide added functionality from community
+contributors. The core should be kept to features used by at least 90% of
+users–everything else should be provided as a plugin. New features should
+be shipped as plugins and focus should be put on creating extensible core
+API’s to support rich plugins.</p>

data/site/sitemap.xml

@@ -2,187 +2,191 @@
 <urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
 <url>
 <loc>https://jekyllrb.com/docs/assets/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/collections/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/conduct/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/configuration/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/docs/continuous-integration/buddyworks/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/continuous-integration/circleci/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/continuous-integration/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/continuous-integration/travis-ci/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/contributing/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/datafiles/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/deployment-methods/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/drafts/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/extras/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/frontmatter/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/github-pages/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/history/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/includes/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/home/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/installation/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/affinity-team-captain/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/avoiding-burnout/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/becoming-a-maintainer/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/merging-a-pull-request/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/reviewing-a-pull-request/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/special-labels/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/maintaining/triaging-an-issue/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/migrations/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/pages/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/pagination/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/permalinks/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/plugins/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/posts/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/quickstart/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/resources/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/sites/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/static-files/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/structure/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/templates/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/themes/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/troubleshooting/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/upgrading/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/upgrading/0-to-2/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/upgrading/2-to-3/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/usage/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/variables/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/docs/windows/</loc>
-<lastmod>2017-03-22T08:08:47-07:00</lastmod>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/news/2013/05/05/jekyll-1-0-0-released/</loc>
@@ -409,7 +413,44 @@
 <lastmod>2017-01-18T11:19:13-08:00</lastmod>
 </url>
 <url>
-<loc>https://jekyllrb.com/news/</loc>
+<loc>https://jekyllrb.com/news/2017/03/02/jekyll-3-4-1-released/</loc>
+<lastmod>2017-03-02T11:20:26-08:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/news/2017/03/09/jekyll-3-4-2-released/</loc>
+<lastmod>2017-03-09T12:41:57-08:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/news/2017/03/21/jekyll-3-4-3-released/</loc>
+<lastmod>2017-03-21T06:52:53-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/news/2017/06/15/jekyll-3-5-0-released/</loc>
+<lastmod>2017-06-15T14:32:32-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/news/2017/07/17/jekyll-3-5-1-released/</loc>
+<lastmod>2017-07-17T09:40:37-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/tutorials/convert-site-to-jekyll/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/tutorials/custom-404-page/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/tutorials/home/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/tutorials/navigation/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
+</url>
+<url>
+<loc>https://jekyllrb.com/tutorials/orderofinterpretation/</loc>
+<lastmod>2017-07-17T13:16:40-07:00</lastmod>
 </url>
 <url>
 <loc>https://jekyllrb.com/</loc>
@@ -418,9 +459,15 @@
 <loc>https://jekyllrb.com/news/releases/</loc>
 </url>
 <url>
-<loc>https://jekyllrb.com/help/</loc>
+<loc>https://jekyllrb.com/news/</loc>
 </url>
 <url>
 <loc>https://jekyllrb.com/community/</loc>
 </url>
+<url>
+<loc>https://jekyllrb.com/help/</loc>
+</url>
+<url>
+<loc>https://jekyllrb.com/philosophy.html</loc>
+</url>
 </urlset>

data/site/tutorials/convert-site-to-jekyll/index.html

@@ -0,0 +1,851 @@
+<!DOCTYPE HTML>
+<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.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.2.3 -->
+<title>Convert an HTML site to Jekyll | Jekyll • Simple, blog-aware, static sites</title>
+<meta property="og:title" content="Convert an HTML site to Jekyll">
+<meta property="og:locale" content="en_US">
+<meta name="description" content="If you’re looking for themes for your Jekyll site, you don’t have to restrict yourself to existing Jekyll themes. It’s pretty easy to convert almost any static HTML files into a Jekyll website.">
+<meta property="og:description" content="If you’re looking for themes for your Jekyll site, you don’t have to restrict yourself to existing Jekyll themes. It’s pretty easy to convert almost any static HTML files into a Jekyll website.">
+<link rel="canonical" href="https://jekyllrb.com/tutorials/convert-site-to-jekyll/">
+<meta property="og:url" content="https://jekyllrb.com/tutorials/convert-site-to-jekyll/">
+<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-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":"Convert an HTML site to Jekyll","datePublished":"2017-07-17T13:16:40-07:00","dateModified":"2017-07-17T13:16:40-07:00","description":"If you’re looking for themes for your Jekyll site, you don’t have to restrict yourself to existing Jekyll themes. It’s pretty easy to convert almost any static HTML files into a Jekyll website.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/tutorials/convert-site-to-jekyll/"},"url":"https://jekyllrb.com/tutorials/convert-site-to-jekyll/"}</script>
+<!-- End Jekyll SEO tag -->
+
+  <!--[if lt IE 9]>
+  <script src="/js/html5shiv.min.js"></script>
+  <script src="/js/respond.min.js"></script>
+  <![endif]-->
+</head>
+
+
+<body class="wrap">
+  <header>
+  <nav class="mobile-nav show-on-mobiles">
+    <ul>
+  <li class="">
+    <a href="/">Home</a>
+  </li>
+  <li class="">
+    <a href="/docs/home/">Docs</a>
+  </li>
+  <li class="">
+    <a href="/news/">News</a>
+  </li>
+  <li class="">
+    <a href="/community/">Community</a>
+  </li>
+  <li class="">
+    <a href="/help/">Help</a>
+  </li>
+  <li>
+    <a href="https://github.com/jekyll/jekyll">GitHub</a>
+  </li>
+</ul>
+
+  </nav>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
+      <h1>
+        <a href="/">
+          <span class="sr-only">Jekyll</span>
+          <img src="/img/logo-2x.png" width="249" height="115" alt="Jekyll Logo">
+        </a>
+      </h1>
+    </div>
+    <nav class="main-nav unit two-thirds hide-on-mobiles">
+      <ul>
+  <li class="">
+    <a href="/">Home</a>
+  </li>
+  <li class="">
+    <a href="/docs/home/">Docs</a>
+  </li>
+  <li class="">
+    <a href="/news/">News</a>
+  </li>
+  <li class="">
+    <a href="/community/">Community</a>
+  </li>
+  <li class="">
+    <a href="/help/">Help</a>
+  </li>
+  <li>
+    <a href="https://github.com/jekyll/jekyll">GitHub</a>
+  </li>
+</ul>
+
+    </nav>
+  </div>
+</header>
+
+
+    <section class="docs">
+    <div class="grid">
+
+      <div class="docs-nav-mobile unit whole show-on-mobiles">
+  <select onchange="if (this.value) window.location.href=this.value">
+    <option value="">Navigate the tutorials…</option>
+    
+    <optgroup label="Tutorials">
+      
+  
+  
+  <option value="/tutorials/home/">Tutorials</option>
+
+  
+  
+  <option value="/tutorials/navigation/">Navigation</option>
+
+  
+  
+  <option value="/tutorials/orderofinterpretation/">Order of interpretation</option>
+
+  
+  
+  <option value="/tutorials/custom-404-page/">Custom 404 Page</option>
+
+  
+  
+  <option value="/tutorials/convert-site-to-jekyll/">Convert an HTML site to Jekyll</option>
+
+
+    </optgroup>
+    
+  </select>
+</div>
+
+
+      <div class="unit four-fifths">
+        <article>
+          <div class="improve right hide-on-mobiles">
+            <a href="https://github.com/jekyll/jekyll/edit/master/docs/_tutorials/convert-existing-site-to-jekyll.md"><i class="fa fa-pencil"></i>  Improve this page</a>
+          </div>
+          <h1>Convert an HTML site to Jekyll</h1>
+          <p>If you’re looking for themes for your Jekyll site, you don’t have to restrict yourself to existing Jekyll themes. It’s pretty easy to convert almost any static HTML files into a Jekyll website.</p>
+
+<p>In many ways, any site that is currently a static site is <em>already</em> a Jekyll website. Jekyll just allows you to automate parts of the site (like inserting pages into templates, rendering lists for navigation, generating feeds and sitemaps, and more) as it processes the files.</p>
+
+<p>Understanding how to convert any HTML site into Jekyll templates will open your world to many more options for Jekyll themes. Instead of <a href="https://duckduckgo.com/?q=Jekyll+themes">searching online for  <em>Jekyll themes</em></a>, you can choose from the large variety of HTML templates for your site, quickly Jekyll-ize the HTML templates as you need to, and build the output with Jekyll.</p>
+
+<p>Although websites can have sophisticated features and controls, we’ll keep things simple in this tutorial.</p>
+
+<h2 id="what-is-a-jekyll-website">What is a Jekyll Website?</h2>
+
+<p>First, let’s start with a grounding in the basics. Stripping a Jekyll site down to an extremely basic level will help clarify what happens in a Jekyll site. If you haven’t already installed the jekyll gem, <a href="/docs/installation/">install it</a>.</p>
+
+<p>We’ll start with a <em>basic Jekyll site</em> consisting of three files:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>├── _config.yml
+├── _layouts
+│   └── default.html
+└── index.md
+</code></pre>
+</div>
+
+<p>Manually create these three files in a folder called <code class="highlighter-rouge">my_jekyll_site</code> or whatever suits you the most, and place <code class="highlighter-rouge">default.html</code> inside a folder named <code class="highlighter-rouge">_layouts</code>.</p>
+
+<div class="language-sh highlighter-rouge">
+<pre class="highlight"><code><span class="gp">$ </span>touch _config.yml index.md default.html
+<span class="gp">$ </span>mkdir _layouts <span class="o">&amp;&amp;</span> mv default.html _layouts
+</code></pre>
+</div>
+
+<p>Fire up your favorite editor, and populate the contents of the <code class="highlighter-rouge">default.html</code> and <code class="highlighter-rouge">index.md</code> files as follows:</p>
+
+<p><strong>_config.yml</strong></p>
+
+<div class="language-yaml highlighter-rouge">
+<pre class="highlight"><code><span class="s">name</span><span class="pi">:</span> <span class="s">My Jekyll Website</span>
+</code></pre>
+</div>
+
+<p><strong>_layouts/default.html</strong></p>
+
+<div class="language-html highlighter-rouge">
+<pre class="highlight"><code><span class="cp">&lt;!DOCTYPE html&gt;</span>
+<span class="nt">&lt;html&gt;</span>
+  <span class="nt">&lt;body&gt;</span>
+     {{ content }}
+  <span class="nt">&lt;/body&gt;</span>
+<span class="nt">&lt;/html&gt;</span>
+</code></pre>
+</div>
+
+<p><strong>index.md</strong></p>
+
+<div class="language-yaml highlighter-rouge">
+<pre class="highlight"><code><span class="nn">---</span>
+<span class="s">title</span><span class="pi">:</span> <span class="s">My page</span>
+<span class="s">layout</span><span class="pi">:</span> <span class="s">default</span>
+<span class="nn">---</span>
+
+<span class="c1"># {{ page.title }}</span>
+
+<span class="s">Content is written in [Markdown](https://learnxinyminutes.com/docs/markdown/). Plain text format allows you to focus on your **content**.</span>
+
+<span class="s">&lt;!--</span>
+<span class="s">You can use HTML elements in Markdown, such as the comment element, and they won't be affected by a markdown parser. However, if you create an HTML element in your markdown file, you cannot use markdown syntax within that element's contents.</span>
+<span class="s">--&gt;</span>
+</code></pre>
+</div>
+
+<p>Now <code class="highlighter-rouge">cd</code> to <code class="highlighter-rouge">my_jekyll_site</code> and serve the site with the built-in server:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>cd my_jekyll_site
+jekyll serve
+</code></pre>
+</div>
+
+<p class="note info">If you have a Gemfile, <a href="/docs/quickstart/#about-bundler">use Bundler</a> by typing <code class="highlighter-rouge">bundle exec jekyll serve</code> instead.</p>
+
+<p>When you serve the site, you get a preview URL such as <code class="highlighter-rouge">http://127.0.0.1:4000/</code> (which is the same as <code class="highlighter-rouge">http://localhost:4000/</code>). The site’s files are built into the <code class="highlighter-rouge">_site</code> folder by default.</p>
+
+<p>This is a Jekyll site at the most basic functional level. Here’s what is happening:</p>
+
+<ul>
+  <li>The <code class="highlighter-rouge">_config.yml</code> file contains settings that Jekyll uses as it processes your site. An empty config file will use default values for building a Jekyll site. For example, to convert <a href="https://learnxinyminutes.com/docs/markdown/">Markdown</a> to HTML, Jekyll will automatically use the <a href="https://rubygems.org/gems/kramdown/">kramdown Markdown filter</a>, without any need to specify it.</li>
+  <li>Jekyll looks for files with <a href="/docs/frontmatter/">front matter tags</a> (the two sets of dashed lines <code class="highlighter-rouge">---</code> like those in <code class="highlighter-rouge">index.md</code>) and processes the files (populating site variables, rendering any <a href="https://shopify.github.io/liquid/">Liquid</a>, and converting Markdown to HTML).</li>
+  <li>Jekyll pushes the content from all pages and posts into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> variable in the layout specified (<code class="highlighter-rouge">default</code>) in the front matter tags.</li>
+  <li>The processed files get written as <code class="highlighter-rouge">.html</code> files in the <code class="highlighter-rouge">_site</code> directory.</li>
+</ul>
+
+<p>You can read more about how Jekyll processes the files in <a href="/tutorials/orderofinterpretation/">order of Interpretation</a>.</p>
+
+<p>With this basic understanding of how a Jekyll site works, you can convert almost any HTML theme for Jekyll. The following sections will take you through a step-by-step tutorial to do so.</p>
+
+<h2 id="1-create-a-template-for-your-default-layout">1. Create a template for your default layout</h2>
+
+<p>Find your HTML theme and save it as a <code class="highlighter-rouge">default</code> layout. If you’re converting or cloning an existing site, you can right-click the page and view the source code.</p>
+
+<p>For example, suppose you’re cloning your company site to create a documentation site with the same branding. Or suppose you have a personal site that you built with HTML and now want to make it a Jekyll site. Get the HTML source code for your site.</p>
+
+<p class="note info">Regardless of the site, do check the license and make sure you have permission to copy and use the code.</p>
+
+<p>Copy and paste the source code into a file called <code class="highlighter-rouge">default.html</code>. Put the <code class="highlighter-rouge">default.html</code> file inside the <code class="highlighter-rouge">_layouts</code> folder. This will be the default layout template for your pages and posts — that is, each page or post will use this layout when Jekyll builds the site.</p>
+
+<p>Note that in looking for templates, you want the HTML output of the template. If the template has PHP tags or other dynamic scripts, these dynamic elements will need to be converted to HTML or to <a href="https://shopify.github.io/liquid/">Liquid</a>. Liquid is <a href="/docs/templates/">Jekyll templating system</a> to retrieve dynamic content.</p>
+
+<p>Open <code class="highlighter-rouge">default.html</code> into your browser locally to ensure the site looks and behaves like it does online. You will likely need to adjust CSS, JS, and image paths so they work.</p>
+
+<p>For example, if the paths were relative on the site you copied, you’ll need to either download the same assets into your Jekyll site or use absolute paths to the same assets in the cloud. (Syntax such as <code class="highlighter-rouge">src="//</code> requires a prefix such as <code class="highlighter-rouge">src="http://</code> to work in your local browser.)</p>
+
+<p>Jekyll provides some <a href="/docs/templates/#filters">filters</a> to prepend a site URL before path. For example, you could preface your stylesheet like this:</p>
+
+<div class="language-liquid highlighter-rouge">
+<pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="s2">"/assets/style.css"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">relative_url</span><span class="w"> </span><span class="p">}}</span>
+</code></pre>
+</div>
+
+<p>The <code class="highlighter-rouge">relative_url</code> filter will prepend the <a href="https://byparker.com/blog/2014/clearing-up-confusion-around-baseurl/"><code class="highlighter-rouge">baseurl</code></a> value from your config file (as<code class="highlighter-rouge">blog</code> for instance) to the input. This is useful if your site is hosted at a subpath rather than at the root of the domain (for example, <code class="highlighter-rouge">http://mysite.com/blog/</code>).</p>
+
+<p>You can also use an <code class="highlighter-rouge">absolute_url</code> filter. This filter will prepend the <code class="highlighter-rouge">url</code> <em>and</em> <code class="highlighter-rouge">baseurl</code> value to the input:</p>
+
+<div class="language-liquid highlighter-rouge">
+<pre class="highlight"><code><span class="p">{{</span><span class="w"> </span><span class="s2">"/assets/style.css"</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">absolute_url</span><span class="w"> </span><span class="p">}}</span>
+</code></pre>
+</div>
+
+<p>Again, both <code class="highlighter-rouge">url</code> and <code class="highlighter-rouge">baseurl</code> can be defined in your site’s config file, like this:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>url: http://mysite.com
+baseurl: /blog
+</code></pre>
+</div>
+
+<p>The result in the output will be <code class="highlighter-rouge">http://mysite.com/blog/assets/style.css</code>.</p>
+
+<p>Note that the <code class="highlighter-rouge">url</code> property of any page begins with a forward slash (<code class="highlighter-rouge">/</code>), so omit this at the end of your <code class="highlighter-rouge">url</code> or <code class="highlighter-rouge">baseurl</code> property.</p>
+
+<p>You don’t have to prepend filters to link paths like this. You could also use relative links across your entire site. However you decide to code the paths to your assets, make sure they render correctly.</p>
+
+<p>Does your local <code class="highlighter-rouge">default.html</code> page look good in your browser? Are all images, styles, and other elements showing up correctly? If so, great. Keep going. You can use this template as the layout for all your pages and posts or create as many templates as you need.</p>
+
+<p>In the next section, you’ll blank out the content of the layout and replace it with placeholder tags that get populated dynamically with your Jekyll pages.</p>
+
+<h2 id="2-identify-the-content-part-of-the-layout">2. Identify the content part of the layout</h2>
+
+<p>In <code class="highlighter-rouge">default.html</code>, find where the page content begins (usually at <code class="highlighter-rouge">h1</code> or <code class="highlighter-rouge">h2</code> tags). Replace the title that appears inside these tags with <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">page.title</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code>.</p>
+
+<p>Remove the content part (keep everything else: navigation menu, sidebar, footer, etc.) and replace it with <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code>.</p>
+
+<p>Check the layout again in your browser and make sure you didn’t corrupt or alter it up by inadvertently removing a crucial <code class="highlighter-rouge">div</code> tag or other element. The only change should be to the title and page content, which are now blanked out or showing the placeholder tag.</p>
+
+<h2 id="3-create-a-couple-of-files-with-front-matter-tags">3. Create a couple of files with front matter tags</h2>
+
+<p>Create a couple of files (<code class="highlighter-rouge">index.md</code> and <code class="highlighter-rouge">about.md</code>) in your root directory.</p>
+
+<p>In your <code class="highlighter-rouge">index.md</code> file, add some front matter tags containing a <code class="highlighter-rouge">title</code> and <code class="highlighter-rouge">layout</code> property, like this:</p>
+
+<div class="language-yaml highlighter-rouge">
+<pre class="highlight"><code><span class="nn">---</span>
+<span class="s">title</span><span class="pi">:</span> <span class="s">Home</span>
+<span class="s">layout</span><span class="pi">:</span> <span class="s">default</span>
+<span class="nn">---</span>
+
+<span class="s">Some page content here...</span>
+</code></pre>
+</div>
+
+<p>Create another page for testing called <code class="highlighter-rouge">about.md</code> with similar front matter tags.</p>
+
+<p class="note info">If you don’t specify a layout in your pages, Jekyll will simply render that page as an unstyled basic HTML page.</p>
+
+<h2 id="4-add-a-configuration-file">4. Add a configuration file</h2>
+
+<p>Add a <code class="highlighter-rouge">_config.yml</code> file in your root directory. In <code class="highlighter-rouge">_config.yml</code>, you can optionally specify the markdown filter you want. By default, <a href="https://kramdown.gettalong.org/">kramdown</a> is used (without the need to specify it). If no other filter is specified, your config file will automatically apply the following as a default setting:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>markdown: kramdown
+</code></pre>
+</div>
+
+<p>You can also specify <a href="https://kramdown.gettalong.org/converter/html.html">some options</a> for kramdown to make it behave more like <a href="https://github.github.com/gfm/">GitHub Flavored Markdown (GFM)</a>:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>kramdown:
+ input: GFM
+ auto_ids: true
+ hard_wrap: false
+ syntax_highlighter: rouge
+</code></pre>
+</div>
+
+<h2 id="5-test-your-pages">5. Test your pages</h2>
+
+<p>Now run <code class="highlighter-rouge">jekyll serve</code> and toggle between your <code class="highlighter-rouge">index.html</code> and <code class="highlighter-rouge">about.html</code> pages. The default layout should load for both pages.</p>
+
+<p>You’ve now extracted your content out into separate files and defined a common layout for pages.</p>
+
+<p>You could define any number of layouts you want for pages. Then just identify the layout you want that particular page to use. For example:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+title: Sample page
+layout: homepage
+---
+</code></pre>
+</div>
+
+<p>This page would then use the <code class="highlighter-rouge">homepage.html</code> template in the <code class="highlighter-rouge">_layouts</code> folder.</p>
+
+<p>You can even set <a href="/docs/configuration/#front-matter-defaults">default front matter tags</a> for pages, posts, or <a href="/docs/collections/">collections</a> in your <code class="highlighter-rouge">_config.yml</code> file so that you don’t have to specify the layout in the front matter variables. Anywayd, setting defaults is beyond the scope of this tutorial, let’s get back to work.</p>
+
+<h2 id="6-configure-site-variables">6. Configure site variables</h2>
+
+<p>You already configured the page title using <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">page.title</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tags. But there are more <code class="highlighter-rouge">title</code> tags to populate. Pages also have a <a href="https://moz.com/learn/seo/title-tag"><code class="highlighter-rouge">title</code></a> tag that appears in the browser tab or window. Typically you put the page title followed by the site title here.</p>
+
+<p>In your <code class="highlighter-rouge">default.html</code> layout, look for the <code class="highlighter-rouge">title</code> tags below your <code class="highlighter-rouge">head</code> tags:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>&lt;title&gt;ACME Website&lt;/title&gt;
+</code></pre>
+</div>
+
+<p>Insert the following site variables:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>&lt;title&gt;{{ page.title }} | {{ site.title }}&lt;/title&gt;
+</code></pre>
+</div>
+
+<p>Open <code class="highlighter-rouge">_config.yml</code> and add a <code class="highlighter-rouge">title</code> property for your site’s name.</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>title: ACME Website
+</code></pre>
+</div>
+
+<p>Any properties you add in your <code class="highlighter-rouge">_config.yml</code> file are accessible through the <code class="highlighter-rouge">site</code> namespace. Similarly, any properties in your page’s front matter are accessible through the <code class="highlighter-rouge">page</code> namespace. Use dot notation after <code class="highlighter-rouge">site</code> or <code class="highlighter-rouge">page</code> to access the value.</p>
+
+<p>Stop your Jekyll server with <kbd>Ctrl</kbd> + <kbd>C</kbd> and restart it. Verify that the <code class="highlighter-rouge">title</code> tags are populating correctly.</p>
+
+<p class="note info">Every time you modify your config file, you have to restart Jekyll for the changes to take effect. When you modify other files, Jekyll automatically picks up the changes when it rebuilds.</p>
+
+<p>If you have other variables to populate in your site, rinse and repeat.</p>
+
+<h2 id="7-show-posts-on-a-page">7. Show posts on a page</h2>
+
+<p>It’s common to show a list of posts on the homepage. First, let’s create some posts so that we have something to showcase.</p>
+
+<p>Add some posts in a <code class="highlighter-rouge">_posts</code> folder following the standard <code class="highlighter-rouge">YYYY-MM-DD-title.md</code> post format:</p>
+
+<ul>
+  <li><code class="highlighter-rouge">2017-01-02-my-first-post.md</code></li>
+  <li><code class="highlighter-rouge">2017-01-15-my-second-post.md</code></li>
+  <li><code class="highlighter-rouge">2017-02-08-my-third-post.md</code></li>
+</ul>
+
+<p>In each post, add some basic content:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+title: My First Post
+layout: default
+---
+
+Some sample content...
+</code></pre>
+</div>
+
+<p>Now let’s create a layout that will display the posts. Create a new file in <code class="highlighter-rouge">_layouts</code> called <code class="highlighter-rouge">home.html</code> and add the following logic:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+layout: default
+---
+
+{{ content }}
+&lt;ul class="myposts"&gt;
+{% for post in site.posts %}
+    &lt;li&gt;&lt;a href="{{ post.url }}"&gt;{{ post.title}}&lt;/a&gt;
+    &lt;span class="postDate"&gt;{{ post.date | date: "%b %-d, %Y" }}&lt;/span&gt;
+    &lt;/li&gt;
+{% endfor %}
+&lt;/ul&gt;
+</code></pre>
+</div>
+
+<p>Create a file called <code class="highlighter-rouge">blog.md</code> in your root directory and specify the <code class="highlighter-rouge">home</code> layout:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+title: Blog
+layout: home
+---
+</code></pre>
+</div>
+
+<p>In this case, contents of <code class="highlighter-rouge">blog.md</code> will be pushed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag in the <code class="highlighter-rouge">home</code> layout. Then the <code class="highlighter-rouge">home</code> layout will be pushed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag of the <code class="highlighter-rouge">default</code> layout.</p>
+
+<h3 id="how-layouts-work">How layouts work</h3>
+
+<p>When a layout specifies another layout, it means the content of the first layout will be stuffed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag of the second layout. As an analogy, think of Russian dolls that fit into each other. Each layout fits into another layout that it specifies.</p>
+
+<p>The following diagram shows how layouts work in Jekyll:</p>
+
+<p><img src="../../img/jekylllayoutconcept.png" alt="Concept of Jekyll layouts"></p>
+
+<p class="image-description">In this example, the content from a Markdown document <code class="highlighter-rouge">document.md</code> that specifies <code class="highlighter-rouge">layout: docs</code> gets pushed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag of the layout file <code class="highlighter-rouge">docs.html</code>. Because the <code class="highlighter-rouge">docs</code> layout itself specifies <code class="highlighter-rouge">layout: page</code>, the content from <code class="highlighter-rouge">docs.html</code> gets pushed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag in the layout file <code class="highlighter-rouge">page.html</code>. Finally because the <code class="highlighter-rouge">page</code> layout specifies <code class="highlighter-rouge">layout: default</code>, the content from <code class="highlighter-rouge">page.html</code> gets pushed into the <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code> tag of the layout file <code class="highlighter-rouge">default.html</code>.</p>
+
+<p>You don’t need multiple layouts. You could just use one: <code class="highlighter-rouge">default</code>. You have options for how you design your site. In general, it’s common to define one layout for pages and another layout for posts, but for both of these layouts to inherit the <code class="highlighter-rouge">default</code> template (which usually defines the top and bottom parts of the site).</p>
+
+<p>In your browser, go to <code class="highlighter-rouge">blog.html</code> and see the list of posts.
+Note that you don’t have to use the method described here. You could have simply added the <code class="highlighter-rouge">for</code> loop to any page, such as <code class="highlighter-rouge">index.md</code>, to display these posts. But given that you may have more complex logic for other features, it can be helpful to store your logic in templates separate from the page area where you frequently type your content.</p>
+
+<p class="note info">At minimum, a layout should contain <code class="highlighter-rouge"><span class="p">{</span><span class="err">{</span><span class="w"> </span><span class="err">content</span><span class="w"> </span><span class="p">}</span><span class="err">}</span></code>, which acts as a receiver for the <em>content</em> to be rendered.</p>
+
+<h3 id="for-loops">For loops</h3>
+
+<p>By the way, let’s pause here to look at the <code class="highlighter-rouge">for</code> loop logic a little more closely. <a href="https://help.shopify.com/themes/liquid/tags/iteration-tags#for">For loops in Liquid</a> are one of the most commonly used Liquid tags. <em>For loops</em> let you iterate through content in your Jekyll site and build out a result. The <code class="highlighter-rouge">for</code> loop also has <a href="https://help.shopify.com/themes/liquid/objects/for-loops">certain properties available</a> (like first or last iteration) based on the loop’s position in the loop as well.</p>
+
+<p>We’ve only scratched the surface of what you can do with <code class="highlighter-rouge">for</code> loops in retrieving posts. For example, if you wanted to display posts from a specific category, you could do so by adding a <code class="highlighter-rouge">categories</code> property to your post’s front matter and then look in those categories. Further, you could limit the number of results by adding a <code class="highlighter-rouge">limit</code> property. Here’s an example:</p>
+
+<div class="language-liquid highlighter-rouge">
+<pre class="highlight"><code>&lt;ul class="myposts"&gt;
+<span class="p">{%</span><span class="w"> </span><span class="nt">for</span><span class="w"> </span>post<span class="w"> </span>in<span class="w"> </span>site.categories.podcasts<span class="w"> </span><span class="na">limit</span><span class="o">:</span><span class="mi">3</span><span class="w"> </span><span class="p">%}</span>
+    &lt;li&gt;&lt;a href="<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">url</span><span class="w"> </span><span class="p">}}</span>"&gt;<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">title</span><span class="p">}}</span>&lt;/a&gt;
+    &lt;span class="postDate"&gt;<span class="p">{{</span><span class="w"> </span><span class="nv">post</span><span class="p">.</span><span class="nv">date</span><span class="w"> </span><span class="p">|</span><span class="w"> </span><span class="nf">date</span><span class="p">:</span><span class="w"> </span><span class="s2">"%b %-d, %Y"</span><span class="w"> </span><span class="p">}}</span>&lt;/span&gt;
+    &lt;/li&gt;
+<span class="p">{%</span><span class="w"> </span><span class="nt">endfor</span><span class="w"> </span><span class="p">%}</span>
+</code></pre>
+</div>
+
+<p>This loop would get the latest three posts that have a category called <code class="highlighter-rouge">podcasts</code> in the front matter.</p>
+
+<h2 id="8-configure-navigation">8. Configure navigation</h2>
+
+<p>Now that you’ve configured posts, let’s configure page navigation. Most websites have some navigation either in the sidebar or header area.</p>
+
+<p>In this tutorial, we’ll assume you’ve got a simple list of pages you want to generate. If you only have a handful of pages, you could list them by using a <code class="highlighter-rouge">for</code> loop to iterate through the <code class="highlighter-rouge">site.pages</code> object and then order them by a front matter property.</p>
+
+<p>Identify the part of your code where the list of pages appears. Usually this is a <code class="highlighter-rouge">&lt;ul&gt;</code> element with various child <code class="highlighter-rouge">&lt;li&gt;</code> elements. Replace the code with the following:</p>
+
+<div class="language-html highlighter-rouge">
+<pre class="highlight"><code><span class="nt">&lt;ul&gt;</span>
+  {% assign mypages = site.pages | sort: "order" %}
+    {% for page in mypages %}
+    <span class="nt">&lt;li&gt;&lt;a</span> <span class="na">href=</span><span class="s">"{{ page.url | absolute_url }}"</span><span class="nt">&gt;</span>{{ page.title }}<span class="nt">&lt;/a&gt;&lt;/li&gt;</span>
+    {% endfor %}
+  <span class="nt">&lt;/ul&gt;</span>
+</code></pre>
+</div>
+
+<p>This example assumes each page would have front matter containing both a <code class="highlighter-rouge">title</code> and <code class="highlighter-rouge">order</code> property like this:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+title: My page
+order: 2
+---
+</code></pre>
+</div>
+
+<p>Here the <code class="highlighter-rouge">order</code> property will define how the pages get sorted, with <code class="highlighter-rouge">1</code> appearing first in the list.</p>
+
+<p>You could also iterate through a list of pages that you maintain in a separate data file. This might be more appropriate if you have a lot of pages, or you have other properties about the pages you want to store.</p>
+
+<p>To manage page links this way, create a folder in your Jekyll project called <code class="highlighter-rouge">_data</code>. In this folder, create a file called e.g. <code class="highlighter-rouge">navigation.yml</code> with this content:</p>
+
+<div class="language-yaml highlighter-rouge">
+<pre class="highlight"><code><span class="pi">-</span> <span class="s">title</span><span class="pi">:</span> <span class="s">Sample page 1</span>
+  <span class="s">url</span><span class="pi">:</span> <span class="s">/page-1-permalink/</span>
+
+<span class="pi">-</span> <span class="s">title</span><span class="pi">:</span> <span class="s">Sample page 2</span>
+  <span class="s">url</span><span class="pi">:</span> <span class="s">/page-2-permalink/</span>
+
+<span class="pi">-</span> <span class="s">title</span><span class="pi">:</span> <span class="s">Sample page 3</span>
+  <span class="s">url</span><span class="pi">:</span> <span class="s">/page-3-permalink/</span>
+</code></pre>
+</div>
+
+<p class="note info">If you never wrote any YAML before, you’ll get quickly familiar with it. Take a look at <a href="https://learnxinyminutes.com/docs/yaml/">what you can do with YAML</a>.</p>
+
+<p>You can store additional properties for each item in this data file as desired. Arrange the list items in the order you want them to appear.</p>
+
+<p>To print the list of pages from the data file, use code like this:</p>
+
+<div class="language-html highlighter-rouge">
+<pre class="highlight"><code><span class="nt">&lt;ul&gt;</span>
+    {% for link in site.data.navigation %}
+    <span class="nt">&lt;li&gt;&lt;a</span> <span class="na">href=</span><span class="s">"{{ link.url }}"</span><span class="nt">&gt;</span>{{ link.title }}<span class="nt">&lt;/a&gt;&lt;/li&gt;</span>
+    {% endfor %}
+<span class="nt">&lt;/ul&gt;</span>
+</code></pre>
+</div>
+
+<p>If you have more sophisticated requirements around navigation, such as when building a documentation site, see the <a href="/tutorials/navigation/">detailed tutorial on navigation</a>.</p>
+
+<h2 id="9-simplify-your-site-with-includes">9. Simplify your site with includes</h2>
+
+<p>Let’s suppose your <code class="highlighter-rouge">default.html</code> file is massive and hard to work with. You can break up your layout by putting some of the HTML code in <em>include</em> files.</p>
+
+<p>Add a folder called <code class="highlighter-rouge">_includes</code> in your root directory. In that folder, add a file there called <code class="highlighter-rouge">sidebar.html</code>.</p>
+
+<p>Remove your sidebar code from your <code class="highlighter-rouge">default.html</code> layout and insert it into the <code class="highlighter-rouge">sidebar.html</code> file.</p>
+
+<p>Where the sidebar code previously existed in <code class="highlighter-rouge">default.html</code>, pull in your “include” like this:</p>
+
+<div class="language-liquid highlighter-rouge">
+<pre class="highlight"><code><span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span><span class="na">sidebar</span><span class="p">.</span><span class="na">html</span><span class="w"> </span><span class="p">%}</span>
+</code></pre>
+</div>
+
+<p>You can break up other elements of your theme like this, such as your header or footer. Then you can apply these common elements to other layout files. This way you won’t have duplicate code.</p>
+
+<h2 id="10-rss-feed">10. RSS feed</h2>
+
+<p>Your Jekyll site needs an RSS feed. Here’s the <a href="http://www.w3schools.com/xml/xml_rss.asp">basic RSS feed syntax</a>. To create an RSS file in Jekyll, create a file called <code class="highlighter-rouge">feed.xml</code> in your root directory and add the following:</p>
+
+<div class="language-xml highlighter-rouge">
+<pre class="highlight"><code>---
+layout: null
+---
+
+<span class="cp">&lt;?xml version="1.0" encoding="UTF-8" ?&gt;</span>
+<span class="nt">&lt;rss</span> <span class="na">version=</span><span class="s">"2.0"</span><span class="nt">&gt;</span>
+
+    <span class="nt">&lt;channel&gt;</span>
+        <span class="nt">&lt;title&gt;</span>{{ site.title }}<span class="nt">&lt;/title&gt;</span>
+        <span class="nt">&lt;link&gt;</span>{{ site.url }}<span class="nt">&lt;/link&gt;</span>
+        <span class="nt">&lt;description&gt;</span>{{ site.description }}<span class="nt">&lt;/description&gt;</span>
+        <span class="nt">&lt;lastBuildDate&gt;</span>{{ site.time | date_to_rfc822 }}<span class="nt">&lt;/lastBuildDate&gt;</span>
+        {% for post in site.posts %}
+        <span class="nt">&lt;item&gt;</span>
+            <span class="nt">&lt;description&gt;</span>
+                {{ post.content | escape | truncate: '400' }}
+            <span class="nt">&lt;/description&gt;</span>
+            <span class="nt">&lt;pubDate&gt;</span>{{ post.date | date_to_rfc822 }}<span class="nt">&lt;/pubDate&gt;</span>
+            <span class="nt">&lt;guid&gt;</span>
+                {{ post.url | prepend: site.url }}
+            <span class="nt">&lt;/guid&gt;</span>
+        <span class="nt">&lt;/item&gt;</span>
+        {% endfor %}
+    <span class="nt">&lt;/channel&gt;</span>
+<span class="nt">&lt;/rss&gt;</span>
+</code></pre>
+</div>
+
+<p>Make sure your <code class="highlighter-rouge">_config.yml</code> file has properties for <code class="highlighter-rouge">title</code>, <code class="highlighter-rouge">url</code>, and <code class="highlighter-rouge">description</code>.</p>
+
+<p>This code uses a <code class="highlighter-rouge">for</code> loop to look through your last 20 posts. The content from the posts gets escaped and truncated to the last 400 characters using <a href="https://help.shopify.com/themes/liquid/filters">Liquid filters</a>.</p>
+
+<p>In your <code class="highlighter-rouge">default.html</code> layout, look for a reference to the RSS or Atom feed in your header, and replace it with a reference to the file you just created. For example:</p>
+
+<div class="language-html highlighter-rouge">
+<pre class="highlight"><code><span class="nt">&lt;link</span> <span class="na">rel=</span><span class="s">"alternate"</span> <span class="na">type=</span><span class="s">"application/rss+xml"</span>  <span class="na">href=</span><span class="s">"{{ site.url }}/feed.xml"</span> <span class="na">title=</span><span class="s">"{{ site.title }}"</span><span class="nt">&gt;</span>
+</code></pre>
+</div>
+
+<p>You can also auto-generate your posts feed by adding a gem called <a href="https://help.github.com/articles/atom-rss-feeds-for-github-pages/"><code class="highlighter-rouge">jekyll-feed</code></a>. This gem will also work on GitHub Pages.</p>
+
+<h2 id="11-add-a-sitemap">11. Add a sitemap</h2>
+
+<p>Finally, add a <a href="https://www.sitemaps.org/protocol.html">site map</a>. Create a <code class="highlighter-rouge">sitemap.xml</code> file in your root directory and add this code:</p>
+
+<div class="language-xml highlighter-rouge">
+<pre class="highlight"><code>---
+layout: null
+search: exclude
+---
+
+<span class="cp">&lt;?xml version="1.0" encoding="UTF-8"?&gt;</span>
+<span class="nt">&lt;urlset</span> <span class="na">xmlns=</span><span class="s">"http://www.sitemaps.org/schemas/sitemap/0.9"</span><span class="nt">&gt;</span>
+
+    {% for page in site.pages %}
+    <span class="nt">&lt;url&gt;</span>
+        <span class="nt">&lt;loc&gt;</span>{{page.url}}<span class="nt">&lt;/loc&gt;</span>
+        <span class="nt">&lt;lastmod&gt;</span>{{site.time | date: '%Y-%m-%d' }}<span class="nt">&lt;/lastmod&gt;</span>
+        <span class="nt">&lt;changefreq&gt;</span>daily<span class="nt">&lt;/changefreq&gt;</span>
+        <span class="nt">&lt;priority&gt;</span>0.5<span class="nt">&lt;/priority&gt;</span>
+    <span class="nt">&lt;/url&gt;</span>
+    {% endfor %}
+
+    {% for post in site.posts %}
+    <span class="nt">&lt;url&gt;</span>
+        <span class="nt">&lt;loc&gt;</span>{{post.url}}<span class="nt">&lt;/loc&gt;</span>
+        <span class="nt">&lt;lastmod&gt;</span>{{site.time | date: '%Y-%m-%d' }}<span class="nt">&lt;/lastmod&gt;</span>
+        <span class="nt">&lt;changefreq&gt;</span>daily<span class="nt">&lt;/changefreq&gt;</span>
+        <span class="nt">&lt;priority&gt;</span>0.5<span class="nt">&lt;/priority&gt;</span>
+    <span class="nt">&lt;/url&gt;</span>
+    {% endfor %}
+
+<span class="nt">&lt;/urlset&gt;</span>
+</code></pre>
+</div>
+
+<p>Again, we’re using a <code class="highlighter-rouge">for</code> loop here to iterate through all posts and pages to add them to the sitemap.</p>
+
+<p>You can also auto-generate your sitemap by adding a gem called <a href="https://help.github.com/articles/sitemaps-for-github-pages/"><code class="highlighter-rouge">jekyll-sitemap</code></a>. This gem will also work on GitHub Pages.</p>
+
+<h2 id="12-add-external-services">12. Add external services</h2>
+
+<p>For other services you might need (such as contact forms, search, comments, and more), look for third-party services. For example, you might use the following:</p>
+
+<ul>
+  <li>For comments: <a href="https://disqus.com/">Disqus</a>
+</li>
+  <li>For a newsletter: <a href="https://tinyletter.com/">Tinyletter</a>
+</li>
+  <li>For contact forms: <a href="https://www.wufoo.com/">Wufoo</a>
+</li>
+  <li>For search: <a href="https://community.algolia.com/docsearch/">Algolia Docsearch</a>
+</li>
+</ul>
+
+<p>For more details on services for static sites, see the <a href="https://learn.cloudcannon.com/jekyll-third-parties/">Third Parties</a> list and tutorials from CloudCannon.</p>
+
+<p>Your Jekyll pages consist of HTML, CSS, and JavaScript, so pretty much any code you need to embed will work without a problem.</p>
+
+<p>As you integrate code for these services, note that <strong>if a page in your Jekyll site doesn’t have front matter tags, Jekyll won’t process any of the content in that page.</strong> The page will just be passed to the <code class="highlighter-rouge">_site</code> folder when you build your site.</p>
+
+<p>If you do want Jekyll to process some page content (for example, to populate a variable that you define in your site’s config file), just add front matter tags to the page. If you don’t want any layout applied to the page, specify <code class="highlighter-rouge">layout: null</code> like this:</p>
+
+<div class="highlighter-rouge">
+<pre class="highlight"><code>---
+layout: null
+---
+</code></pre>
+</div>
+
+<h2 id="13-conclusion">13. Conclusion</h2>
+
+<p>Although websites can implement more sophisticated features and functionality, we’ve covered the basics in this tutorial. You now have a fully functional Jekyll site.</p>
+
+<p>To deploy your site, consider using <a href="https://pages.github.com/">GitHub Pages</a>, <a href="https://www.netlify.com/">Netlify</a>, <a href="https://aws.amazon.com/s3/">Amazon AWS S3</a> using the <a href="https://github.com/laurilehmijoki/s3_website">s3_website plugin</a>, or just FTP your files to your web server.</p>
+
+<p>You can also package your layouts, includes and assets into a Ruby <code class="highlighter-rouge">gem</code> and <a href="/docs/themes/#creating-a-theme">make it a Jekyll theme</a>.</p>
+
+<h2 id="additional-resources">Additional resources</h2>
+
+<p>Here are some additional tutorials on creating Jekyll sites:</p>
+
+<ul>
+  <li><a href="http://jekyll.tips/jekyll-casts/converting-a-static-site-to-jekyll/">Convert a static site to Jekyll</a></li>
+  <li><a href="https://css-tricks.com/building-a-jekyll-site-part-1-of-3/">Building a Jekyll Site – Part 1 of 3: Converting a Static Website To Jekyll</a></li>
+</ul>
+
+
+          
+
+
+
+
+
+  
+  
+
+  
+  
+
+  
+  
+
+  
+  
+
+  
+  
+    <div class="section-nav">
+      <div class="left align-right">
+          
+            
+            
+            <a href="/tutorials/custom-404-page/" class="prev">Back</a>
+          
+      </div>
+      <div class="right align-left">
+          
+            <span class="next disabled">Next</span>
+          
+      </div>
+    </div>
+    <div class="clear"></div>
+    
+        </article>
+      </div>
+
+      <div class="unit one-fifth hide-on-mobiles">
+  <aside>
+    
+    <h4>Tutorials</h4>
+
+   <ul>
+
+  
+  
+  <li class=""><a href="/tutorials/home/">Tutorials</a></li>
+
+  
+  
+  <li class=""><a href="/tutorials/navigation/">Navigation</a></li>
+
+  
+  
+  <li class=""><a href="/tutorials/orderofinterpretation/">Order of interpretation</a></li>
+
+  
+  
+  <li class=""><a href="/tutorials/custom-404-page/">Custom 404 Page</a></li>
+
+  
+  
+  <li class="current"><a href="/tutorials/convert-site-to-jekyll/">Convert an HTML site to Jekyll</a></li>
+
+</ul>
+
+
+    
+  </aside>
+</div>
+
+
+      <div class="clear"></div>
+
+    </div>
+  </section>
+
+
+  <footer>
+  <div class="grid">
+    <div class="unit one-third center-on-mobiles">
+      <p>The contents of this website are <br>© 2017 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
+    </div>
+    <div class="unit two-thirds align-right center-on-mobiles">
+      <p>
+        Proudly hosted by
+        <a href="https://github.com">
+          <img src="/img/footer-logo.png" width="100" height="30" alt="GitHub • Social coding">
+        </a>
+      </p>
+    </div>
+  </div>
+</footer>
+
+  <script>
+  var anchorForId = function (id) {
+    var anchor = document.createElement("a");
+    anchor.className = "header-link";
+    anchor.href      = "#" + id;
+    anchor.innerHTML = "<span class=\"sr-only\">Permalink</span><i class=\"fa fa-link\"></i>";
+    anchor.title = "Permalink";
+    return anchor;
+  };
+
+  var linkifyAnchors = function (level, containingElement) {
+    var headers = containingElement.getElementsByTagName("h" + level);
+    for (var h = 0; h < headers.length; h++) {
+      var header = headers[h];
+
+      if (typeof header.id !== "undefined" && header.id !== "") {
+        header.appendChild(anchorForId(header.id));
+      }
+    }
+  };
+
+  document.onreadystatechange = function () {
+    if (this.readyState === "complete") {
+      var contentBlock = document.getElementsByClassName("docs")[0] || document.getElementsByClassName("news")[0];
+      if (!contentBlock) {
+        return;
+      }
+      for (var level = 1; level <= 6; level++) {
+        linkifyAnchors(level, contentBlock);
+      }
+    }
+  };
+</script>
+
+  
+  <!-- Gauges (http://get.gaug.es/) -->
+  <script>
+    var _gauges = _gauges || [];
+    (function() {
+      var t   = document.createElement('script');
+      t.type  = 'text/javascript';
+      t.async = true;
+      t.id    = 'gauges-tracker';
+      t.setAttribute('data-site-id', '503c5af6613f5d0f19000027');
+      t.src = '//secure.gaug.es/track.js';
+      var s = document.getElementsByTagName('script')[0];
+      s.parentNode.insertBefore(t, s);
+    })();
+  </script>
+
+
+
+  <!-- Google Analytics (https://www.google.com/analytics) -->
+  <script>
+    !function(j,e,k,y,l,L){j.GoogleAnalyticsObject=y,j[y]||(j[y]=function(){
+    (j[y].q=j[y].q||[]).push(arguments)}),j[y].l=+new Date,l=e.createElement(k),
+    L=e.getElementsByTagName(k)[0],l.src='//www.google-analytics.com/analytics.js',
+    L.parentNode.insertBefore(l,L)}(window,document,'script','ga');
+
+    ga('create', 'UA-50755011-1', 'jekyllrb.com');
+    ga('send', 'pageview');
+
+  </script>
+
+
+
+</body>
+</html>