site/docs/configuration/index.html in jekyll-docs-3.9.0 vs site/docs/configuration/index.html in jekyll-docs-4.0.0
- old
+ new
@@ -1,36 +1,39 @@
<!DOCTYPE HTML>
<html lang="en-US">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
- <meta name="generator" content="Jekyll v3.9.0">
+ <meta name="generator" content="Jekyll v4.0.0">
<link type="application/atom+xml" rel="alternate" href="https://jekyllrb.com/feed.xml" title="Jekyll • Simple, blog-aware, static sites" />
+ <link type="application/atom+xml" rel="alternate" href="/feed/release.xml" title="Jekyll releases posts" />
<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="preconnect" href="https://fonts.gstatic.com/" crossorigin>
- <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lato:300,300italic,400,400italic,700,700italic,900">
- <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
+ <link rel="preload" href="/fonts/lato-v14-latin-300.woff2" as="font" type="font/woff2" crossorigin />
+ <link rel="preload" href="/fonts/lato-v14-latin-700.woff2" as="font" type="font/woff2" crossorigin />
+ <link rel="preload" href="/css/screen.css" as="style">
<link rel="stylesheet" href="/css/screen.css">
<link rel="icon" type="image/x-icon" href="/favicon.ico">
<!-- Begin Jekyll SEO tag v2.6.1 -->
<title>Configuration | Jekyll • Simple, blog-aware, static sites</title>
-<meta name="generator" content="Jekyll v3.9.0" />
+<meta name="generator" content="Jekyll v4.0.0" />
<meta property="og:title" content="Configuration" />
<meta property="og:locale" content="en_US" />
-<meta name="description" content="Jekyll allows you to concoct your sites in any way you can dream up, and it’s thanks to the powerful and flexible configuration options that this is possible. These options can either be specified in a _config.yml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal." />
-<meta property="og:description" content="Jekyll allows you to concoct your sites in any way you can dream up, and it’s thanks to the powerful and flexible configuration options that this is possible. These options can either be specified in a _config.yml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal." />
+<meta name="description" content="Jekyll gives you a lot of flexibility to customize how it builds your site. These options can either be specified in a _config.yml or _config.toml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal." />
+<meta property="og:description" content="Jekyll gives you a lot of flexibility to customize how it builds your site. These options can either be specified in a _config.yml or _config.toml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal." />
<link rel="canonical" href="https://jekyllrb.com/docs/configuration/" />
<meta property="og:url" content="https://jekyllrb.com/docs/configuration/" />
<meta property="og:site_name" content="Jekyll • Simple, blog-aware, static sites" />
+<meta property="og:image" content="https://jekyllrb.com/img/jekyll-og.png" />
<meta property="og:type" content="article" />
-<meta property="article:published_time" content="2020-08-05T11:55:36-07:00" />
-<meta name="twitter:card" content="summary" />
+<meta property="article:published_time" content="2019-09-11T07:30:27-07:00" />
+<meta name="twitter:card" content="summary_large_image" />
+<meta property="twitter:image" content="https://jekyllrb.com/img/jekyll-og.png" />
<meta property="twitter:title" content="Configuration" />
<meta name="twitter:site" content="@jekyllrb" />
<meta name="google-site-verification" content="onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY" />
<script type="application/ld+json">
-{"url":"https://jekyllrb.com/docs/configuration/","headline":"Configuration","dateModified":"2020-08-05T11:55:36-07:00","datePublished":"2020-08-05T11:55:36-07:00","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"description":"Jekyll allows you to concoct your sites in any way you can dream up, and it’s thanks to the powerful and flexible configuration options that this is possible. These options can either be specified in a _config.yml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal.","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/configuration/"},"@type":"BlogPosting","@context":"https://schema.org"}</script>
+{"description":"Jekyll gives you a lot of flexibility to customize how it builds your site. These options can either be specified in a _config.yml or _config.toml file placed in your site’s root directory, or can be specified as flags for the jekyll executable in the terminal.","@type":"BlogPosting","mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/configuration/"},"headline":"Configuration","dateModified":"2019-09-11T07:30:27-07:00","url":"https://jekyllrb.com/docs/configuration/","datePublished":"2019-09-11T07:30:27-07:00","image":"https://jekyllrb.com/img/jekyll-og.png","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"@context":"https://schema.org"}</script>
<!-- End Jekyll SEO tag -->
<!--[if lt IE 9]>
<script src="/js/html5shiv.min.js"></script>
<script src="/js/respond.min.js"></script>
@@ -49,54 +52,69 @@
</a>
</h1>
</div>
<nav class="main-nav hide-on-mobiles">
<ul>
- <li class="">
+
+ <li>
<a href="/">Home</a>
</li>
+
<li class="current">
- <a href="/docs/home/">Docs</a>
+ <a href="/docs/">Docs</a>
</li>
- <li class="">
- <a href="/news/">News</a>
+
+ <li>
+ <a href="/resources/">Resources</a>
</li>
- <li class="">
- <a href="/help/">Help</a>
+
+ <li>
+ <a href="/showcase/">Showcase</a>
</li>
+
+ <li>
+ <a href="/news/">News</a>
+ </li>
+
</ul>
</nav>
<div class="search hide-on-mobiles">
<input type="text" id="docsearch-input" placeholder="Search the docs…">
</div>
<div class="meta hide-on-mobiles">
<ul>
<li>
- <a href="https://github.com/jekyll/jekyll/releases/tag/v3.9.0">v3.9.0</a>
+ <a href="https://github.com/jekyll/jekyll/releases/tag/v4.0.0">v4.0.0</a>
</li>
<li>
<a href="https://github.com/jekyll/jekyll">GitHub</a>
</li>
</ul>
</div>
</div>
<nav class="mobile-nav show-on-mobiles">
<ul>
- <li class="">
- <a href="/">Home</a>
- </li>
- <li class="current">
- <a href="/docs/home/">Docs</a>
- </li>
- <li class="">
- <a href="/news/">News</a>
- </li>
- <li class="">
- <a href="/help/">Help</a>
- </li>
+
+ <li>
+ <a href="/">Home</a>
+ </li>
+
+ <li class="current">
+ <a href="/docs/">Docs</a>
+ </li>
+
+ <li>
+ <a href="/resources/">Resources</a>
+ </li>
+
+
+ <li>
+ <a href="/news/">News</a>
+ </li>
+
<li>
<a href="https://github.com/jekyll/jekyll">GitHub</a>
</li>
</ul>
@@ -111,1249 +129,397 @@
<select onchange="if (this.value) window.location.href=this.value">
<option value="">Navigate the docs…</option>
<optgroup label="Getting Started">
-
-
- <option value="/docs/home/">Welcome</option>
-
-
-
- <option value="/docs/quickstart/">Quick-start guide</option>
-
-
-
- <option value="/docs/installation/">Installation</option>
-
-
-
- <option value="/docs/windows/">Jekyll on Windows</option>
-
-
-
- <option value="/docs/usage/">Basic Usage</option>
-
-
-
- <option value="/docs/structure/">Directory structure</option>
-
-
-
- <option value="/docs/configuration/">Configuration</option>
-
-
- </optgroup>
-
- <optgroup label="Your Content">
+
+ <option value="/docs/">
+ Quickstart
+ </option>
-
-
- <option value="/docs/frontmatter/">Front Matter</option>
-
-
-
- <option value="/docs/posts/">Writing posts</option>
-
-
-
- <option value="/docs/drafts/">Working with drafts</option>
-
-
-
- <option value="/docs/pages/">Creating pages</option>
-
-
-
- <option value="/docs/static-files/">Static Files</option>
-
-
-
- <option value="/docs/variables/">Variables</option>
-
-
-
- <option value="/docs/collections/">Collections</option>
-
-
-
- <option value="/docs/datafiles/">Data Files</option>
-
-
-
- <option value="/docs/assets/">Assets</option>
-
-
-
- <option value="/docs/migrations/">Blog migrations</option>
-
-
+
+ <option value="/docs/ruby-101/">
+ Ruby 101
+ </option>
+
+
+ <option value="/docs/installation/">
+ Installation
+ </option>
+
+
+ <option value="/docs/community/">
+ Community
+ </option>
+
+
+ <option value="/docs/step-by-step/01-setup/">
+ Step by Step Tutorial
+ </option>
+
</optgroup>
- <optgroup label="Customization">
+ <optgroup label="Build">
-
-
- <option value="/docs/templates/">Templates</option>
-
-
-
- <option value="/docs/includes/">Includes</option>
-
-
-
- <option value="/docs/permalinks/">Permalinks</option>
-
-
-
- <option value="/docs/pagination/">Pagination</option>
-
-
-
- <option value="/docs/plugins/">Plugins</option>
-
-
-
- <option value="/docs/themes/">Themes</option>
-
-
-
- <option value="/docs/extras/">Extras</option>
-
-
+
+ <option value="/docs/usage/">
+ Command Line Usage
+ </option>
+
+
+ <option value="/docs/configuration/">
+ Configuration
+ </option>
+
</optgroup>
- <optgroup label="Deployment">
+ <optgroup label="Content">
-
-
- <option value="/docs/github-pages/">GitHub Pages</option>
-
-
-
- <option value="/docs/deployment-methods/">Deployment methods</option>
-
-
-
- <option value="/docs/continuous-integration/">Continuous Integration</option>
-
-
+
+ <option value="/docs/pages/">
+ Pages
+ </option>
+
+
+ <option value="/docs/posts/">
+ Posts
+ </option>
+
+
+ <option value="/docs/front-matter/">
+ Front Matter
+ </option>
+
+
+ <option value="/docs/collections/">
+ Collections
+ </option>
+
+
+ <option value="/docs/datafiles/">
+ Data Files
+ </option>
+
+
+ <option value="/docs/assets/">
+ Assets
+ </option>
+
+
+ <option value="/docs/static-files/">
+ Static Files
+ </option>
+
</optgroup>
- <optgroup label="Miscellaneous">
+ <optgroup label="Site Structure">
-
-
- <option value="/docs/troubleshooting/">Troubleshooting</option>
-
-
-
- <option value="/docs/sites/">Sites using Jekyll</option>
-
-
-
- <option value="/docs/resources/">Resources</option>
-
-
-
- <option value="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</option>
-
-
-
- <option value="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</option>
-
-
+
+ <option value="/docs/structure/">
+ Directory Structure
+ </option>
+
+
+ <option value="/docs/liquid/">
+ Liquid
+ </option>
+
+
+ <option value="/docs/variables/">
+ Variables
+ </option>
+
+
+ <option value="/docs/includes/">
+ Includes
+ </option>
+
+
+ <option value="/docs/layouts/">
+ Layouts
+ </option>
+
+
+ <option value="/docs/permalinks/">
+ Permalinks
+ </option>
+
+
+ <option value="/docs/themes/">
+ Themes
+ </option>
+
+
+ <option value="/docs/pagination/">
+ Pagination
+ </option>
+
</optgroup>
- <optgroup label="Meta">
+ <optgroup label="Guides">
-
-
- <option value="/docs/contributing/">Contributing</option>
-
-
-
- <option value="/docs/maintaining/">Maintaining Jekyll</option>
-
-
-
- <option value="/docs/conduct/">Code of Conduct</option>
-
-
-
- <option value="/docs/history/">History</option>
-
-
+
+ <option value="/docs/plugins/">
+ Plugins
+ </option>
+
+
+ <option value="/docs/migrations/">
+ Blog Migrations
+ </option>
+
+
+ <option value="/docs/upgrading/">
+ Upgrading
+ </option>
+
+
+ <option value="/docs/deployment/">
+ Deployment
+ </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/_docs/configuration.md"><i class="fa fa-pencil"></i> Improve this page</a>
+ <a data-proofer-ignore href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/configuration.md"><i class="fa fa-pencil"></i> Improve this page</a>
</div>
<h1>Configuration</h1>
- <p>Jekyll allows you to concoct your sites in any way you can dream up, and it’s
-thanks to the powerful and flexible configuration options that this is possible.
-These options can either be specified in a <code class="language-plaintext highlighter-rouge">_config.yml</code> file placed in your
-site’s root directory, or can be specified as flags for the <code class="language-plaintext highlighter-rouge">jekyll</code> executable
-in the terminal.</p>
+ <p>Jekyll gives you a lot of flexibility to customize how it builds your site. These
+options can either be specified in a <code class="highlighter-rouge">_config.yml</code> or <code class="highlighter-rouge">_config.toml</code> file placed
+in your site’s root directory, or can be specified as flags for the <code class="highlighter-rouge">jekyll</code>
+executable in the terminal.</p>
-<h2 id="configuration-settings">Configuration Settings</h2>
-
-<h3 id="global-configuration">Global Configuration</h3>
-
-<p>The table below lists the available settings for Jekyll, and the various <code class="option">options</code> (specified in the configuration file) and <code class="flag">flags</code> (specified on the command-line) that control them.</p>
-
-<div class="mobile-side-scroller">
-<table>
- <thead>
- <tr>
- <th>Setting</th>
- <th>
- <span class="option">Options</span> and <span class="flag">Flags</span>
- </th>
- </tr>
- </thead>
- <tbody>
- <tr class="setting">
- <td>
- <p class="name"><strong>Site Source</strong></p>
- <p class="description">Change the directory where Jekyll will read files</p>
- </td>
- <td class="align-center">
- <p><code class="option">source: DIR</code></p>
- <p><code class="flag">-s, --source DIR</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Site Destination</strong></p>
- <p class="description">Change the directory where Jekyll will write files</p>
- </td>
- <td class="align-center">
- <p><code class="option">destination: DIR</code></p>
- <p><code class="flag">-d, --destination DIR</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Safe</strong></p>
- <p class="description">Disable <a href="../plugins/">custom plugins, and ignore symbolic links</a>.</p>
- </td>
- <td class="align-center">
- <p><code class="option">safe: BOOL</code></p>
- <p><code class="flag">--safe</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Exclude</strong></p>
- <p class="description">
- Exclude directories and/or files from the
- conversion. These exclusions are relative to the site's
- source directory and cannot be outside the source directory.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">exclude: [DIR, FILE, ...]</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Include</strong></p>
- <p class="description">
- Force inclusion of directories and/or files in the conversion.
- <code>.htaccess</code> is a good example since dotfiles are excluded
- by default.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">include: [DIR, FILE, ...]</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Keep files</strong></p>
- <p class="description">
- When clobbering the site destination, keep the selected files.
- Useful for files that are not generated by jekyll; e.g. files or
- assets that are generated by your build tool.
- The paths are relative to the <code>destination</code>.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">keep_files: [DIR, FILE, ...]</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Time Zone</strong></p>
- <p class="description">
- Set the time zone for site generation. This sets the <code>TZ</code>
- environment variable, which Ruby uses to handle time and date
- creation and manipulation. Any entry from the
- <a href="https://en.wikipedia.org/wiki/Tz_database">IANA Time Zone
- Database</a> is valid, e.g. <code>America/New_York</code>. A list of all
- available values can be found <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones">
- here</a>. When serving on a local machine, the default time zone is set by your operating system. But when served on a remote host/server, the default time zone depends on the server's setting or location.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">timezone: TIMEZONE</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Encoding</strong></p>
- <p class="description">
- Set the encoding of files by name (only available for Ruby
- 1.9 or later).
- The default value is <code>utf-8</code> starting in 2.0.0,
- and <code>nil</code> before 2.0.0, which will yield the Ruby
- default of <code>ASCII-8BIT</code>.
- Available encodings can be shown by the
- command <code>ruby -e 'puts Encoding::list.join("\n")'</code>.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">encoding: ENCODING</code></p>
- </td>
- </tr>
- <tr>
- <td>
- <p class="name"><strong>Defaults</strong></p>
- <p class="description">
- Set defaults for <a href="../frontmatter/" title="YAML Front Matter">YAML Front Matter</a>
- variables.
- </p>
- </td>
- <td class="align-center">
- <p>see <a href="#front-matter-defaults" title="details">below</a></p>
- </td>
- </tr>
- </tbody>
-</table>
-</div>
-
-<div class="note warning">
- <h5>Destination folders are cleaned on site builds</h5>
- <p>
- The contents of <code><destination></code> are automatically
- cleaned, by default, when the site is built. Files or folders that are not
- created by your site will be removed. Some files could be retained
- by specifying them within the <code><keep_files></code> configuration directive.
- </p>
- <p>
- Do not use an important location for <code><destination></code>; instead, use it as
- a staging area and copy files from there to your web server.
- </p>
-</div>
-
-<h3 id="build-command-options">Build Command Options</h3>
-
-<div class="mobile-side-scroller">
-<table>
- <thead>
- <tr>
- <th>Setting</th>
- <th>
-<span class="option">Options</span> and <span class="flag">Flags</span>
-</th>
- </tr>
- </thead>
- <tbody>
- <tr class="setting">
- <td>
- <p class="name"><strong>Regeneration</strong></p>
- <p class="description">Enable auto-regeneration of the site when files are modified.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">-w, --[no-]watch</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Configuration</strong></p>
- <p class="description">Specify config files instead of using <code>_config.yml</code> automatically. Settings in later files override settings in earlier files.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">--config FILE1[,FILE2,...]</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Drafts</strong></p>
- <p class="description">Process and render draft posts.</p>
- </td>
- <td class="align-center">
- <p><code class="option">show_drafts: BOOL</code></p>
- <p><code class="flag">--drafts</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Environment</strong></p>
- <p class="description">Use a specific environment value in the build.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">JEKYLL_ENV=production</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Future</strong></p>
- <p class="description">Publish posts or collection documents with a future date.</p>
- </td>
- <td class="align-center">
- <p><code class="option">future: BOOL</code></p>
- <p><code class="flag">--future</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Unpublished</strong></p>
- <p class="description">Render posts that were marked as unpublished.</p>
- </td>
- <td class="align-center">
- <p><code class="option">unpublished: BOOL</code></p>
- <p><code class="flag">--unpublished</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>LSI</strong></p>
- <p class="description">Produce an index for related posts. Requires the <a href="http://www.classifier-reborn.com/">classifier-reborn</a> plugin.</p>
- </td>
- <td class="align-center">
- <p><code class="option">lsi: BOOL</code></p>
- <p><code class="flag">--lsi</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Limit Posts</strong></p>
- <p class="description">Limit the number of posts to parse and publish.</p>
- </td>
- <td class="align-center">
- <p><code class="option">limit_posts: NUM</code></p>
- <p><code class="flag">--limit_posts NUM</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Force polling</strong></p>
- <p class="description">Force watch to use polling.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">--force_polling</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Verbose output</strong></p>
- <p class="description">Print verbose output.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">-V, --verbose</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Silence Output</strong></p>
- <p class="description">Silence the normal output from Jekyll
- during a build</p>
- </td>
- <td class="align-center">
- <p><code class="flag">-q, --quiet</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Incremental build</strong></p>
- <p class="description">
- Enable the experimental incremental build feature. Incremental build only
- re-builds posts and pages that have changed, resulting in significant performance
- improvements for large sites, but may also break site generation in certain
- cases.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">incremental: BOOL</code></p>
- <p><code class="flag">-I, --incremental</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Liquid profiler</strong></p>
- <p class="description">
- Generate a Liquid rendering profile to help you identify performance bottlenecks.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">profile: BOOL</code></p>
- <p><code class="flag">--profile</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Strict Front Matter</strong></p>
- <p class="description">
- Cause a build to fail if there is a YAML syntax error in a page's front matter.
- </p>
- </td>
- <td class="align-center">
- <p><code class="option">strict_front_matter: BOOL</code></p>
- <p><code class="flag">--strict_front_matter</code></p>
- </td>
- </tr>
- </tbody>
-</table>
-</div>
-
-<h3 id="serve-command-options">Serve Command Options</h3>
-
-<p>In addition to the options below, the <code class="language-plaintext highlighter-rouge">serve</code> sub-command can accept any of the options
-for the <code class="language-plaintext highlighter-rouge">build</code> sub-command, which are then applied to the site build which occurs right
-before your site is served.</p>
-
-<div class="mobile-side-scroller">
-<table>
- <thead>
- <tr>
- <th>Setting</th>
- <th>
-<span class="option">Options</span> and <span class="flag">Flags</span>
-</th>
- </tr>
- </thead>
- <tbody>
- <tr class="setting">
- <td>
- <p class="name"><strong>Local Server Port</strong></p>
- <p class="description">Listen on the given port.</p>
- </td>
- <td class="align-center">
- <p><code class="option">port: PORT</code></p>
- <p><code class="flag">--port PORT</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Local Server Hostname</strong></p>
- <p class="description">Listen at the given hostname.</p>
- </td>
- <td class="align-center">
- <p><code class="option">host: HOSTNAME</code></p>
- <p><code class="flag">--host HOSTNAME</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Base URL</strong></p>
- <p class="description">Serve the website from the given base URL</p>
- </td>
- <td class="align-center">
- <p><code class="option">baseurl: URL</code></p>
- <p><code class="flag">--baseurl URL</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Detach</strong></p>
- <p class="description">Detach the server from the terminal</p>
- </td>
- <td class="align-center">
- <p><code class="option">detach: BOOL</code></p>
- <p><code class="flag">-B, --detach</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>Skips the initial site build.</strong></p>
- <p class="description">Skips the initial site build which occurs before the server is started.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">--skip-initial-build</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>X.509 (SSL) Private Key</strong></p>
- <p class="description">SSL Private Key.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">--ssl-key</code></p>
- </td>
- </tr>
- <tr class="setting">
- <td>
- <p class="name"><strong>X.509 (SSL) Certificate</strong></p>
- <p class="description">SSL Public certificate.</p>
- </td>
- <td class="align-center">
- <p><code class="flag">--ssl-cert</code></p>
- </td>
- </tr>
- </tbody>
-</table>
-</div>
-
-<div class="note warning">
- <h5>Do not use tabs in configuration files</h5>
- <p>
- This will either lead to parsing errors, or Jekyll will revert to the
- default settings. Use spaces instead.
- </p>
-</div>
-
-<h2 id="custom-webrick-headers">Custom WEBrick Headers</h2>
-
-<p>You can provide custom headers for your site by adding them to <code class="language-plaintext highlighter-rouge">_config.yml</code></p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># File: _config.yml</span>
-<span class="na">webrick</span><span class="pi">:</span>
- <span class="na">headers</span><span class="pi">:</span>
- <span class="na">My-Header</span><span class="pi">:</span> <span class="s">My-Value</span>
- <span class="na">My-Other-Header</span><span class="pi">:</span> <span class="s">My-Other-Value</span>
-</code></pre></div></div>
-
-<h3 id="defaults">Defaults</h3>
-
-<p>We provide by default <code class="language-plaintext highlighter-rouge">Content-Type</code> and <code class="language-plaintext highlighter-rouge">Cache-Control</code> response headers: one
-dynamic in order to specify the nature of the data being served, the other
-static in order to disable caching so that you don’t have to fight with Chrome’s
-aggressive caching when you are in development mode.</p>
-
-<h2 id="specifying-a-jekyll-environment-at-build-time">Specifying a Jekyll environment at build time</h2>
-
-<p>In the build (or serve) arguments, you can specify a Jekyll environment and value. The build will then apply this value in any conditional statements in your content.</p>
-
-<p>For example, suppose you set this conditional statement in your code:</p>
-
-<div class="language-liquid highlighter-rouge"><div class="highlight"><pre class="highlight"><code>
-<span class="p">{%</span><span class="w"> </span><span class="kr">if</span><span class="w"> </span><span class="nv">jekyll</span><span class="p">.</span><span class="nv">environment</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="s2">"production"</span><span class="w"> </span><span class="p">%}</span>
- <span class="p">{%</span><span class="w"> </span><span class="nt">include</span><span class="w"> </span>disqus.html<span class="w"> </span><span class="p">%}</span>
-<span class="p">{%</span><span class="w"> </span><span class="kr">endif</span><span class="w"> </span><span class="p">%}</span>
-
-</code></pre></div></div>
-
-<p>When you build your Jekyll site, the content inside the <code class="language-plaintext highlighter-rouge">if</code> statement won’t be run unless you also specify a <code class="language-plaintext highlighter-rouge">production</code> environment in the build command, like this:</p>
-
-<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">JEKYLL_ENV</span><span class="o">=</span>production jekyll build
-</code></pre></div></div>
-
-<p>Specifying an environment value allows you to make certain content available only within specific environments.</p>
-
-<p>The default value for <code class="language-plaintext highlighter-rouge">JEKYLL_ENV</code> is <code class="language-plaintext highlighter-rouge">development</code>. Therefore if you omit <code class="language-plaintext highlighter-rouge">JEKYLL_ENV</code> from the build arguments, the default value will be <code class="language-plaintext highlighter-rouge">JEKYLL_ENV=development</code>. Any content inside <code class="language-plaintext highlighter-rouge">{% if jekyll.environment == "development" %}</code> tags will automatically appear in the build.</p>
-
-<p>Your environment values can be anything you want (not just <code class="language-plaintext highlighter-rouge">development</code> or <code class="language-plaintext highlighter-rouge">production</code>). Some elements you might want to hide in development environments include Disqus comment forms or Google Analytics. Conversely, you might want to expose an “Edit me in GitHub” button in a development environment but not include it in production environments.</p>
-
-<p>By specifying the option in the build command, you avoid having to change values in your configuration files when moving from one environment to another.</p>
-
-<h2 id="front-matter-defaults">Front Matter defaults</h2>
-
-<p>Using <a href="../frontmatter/">YAML Front Matter</a> is one way that you can specify configuration in the pages and posts for your site. Setting things like a default layout, or customizing the title, or specifying a more precise date/time for the post can all be added to your page or post front matter.</p>
-
-<p>Often times, you will find that you are repeating a lot of configuration options. Setting the same layout in each file, adding the same category - or categories - to a post, etc. You can even add custom variables like author names, which might be the same for the majority of posts on your blog.</p>
-
-<p>Instead of repeating this configuration each time you create a new post or page, Jekyll provides a way to set these defaults in the site configuration. To do this, you can specify site-wide defaults using the <code class="language-plaintext highlighter-rouge">defaults</code> key in the <code class="language-plaintext highlighter-rouge">_config.yml</code> file in your project’s root directory.</p>
-
-<p>The <code class="language-plaintext highlighter-rouge">defaults</code> key holds an array of scope/values pairs that define what defaults should be set for a particular file path, and optionally, a file type in that path.</p>
-
-<p>Let’s say that you want to add a default layout to all pages and posts in your site. You would add this to your <code class="language-plaintext highlighter-rouge">_config.yml</code> file:</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="c1"># an empty string here means all files in the project</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">default"</span>
-</code></pre></div></div>
-
-<div class="note info">
- <h5>Please stop and rerun `jekyll serve` command.</h5>
- <p>
- The <code>_config.yml</code> master configuration file contains global configurations
- and variable definitions that are read once at execution time. Changes made to <code>_config.yml</code>
- during automatic regeneration are not loaded until the next execution.
- </p>
- <p>
- Note <a href="../datafiles">Data Files</a> are included and reloaded during automatic regeneration.
- </p>
-</div>
-
-<p>Here, we are scoping the <code class="language-plaintext highlighter-rouge">values</code> to any file that exists in the path <code class="language-plaintext highlighter-rouge">scope</code>. Since the path is set as an empty string, it will apply to <strong>all files</strong> in your project. You probably don’t want to set a layout on every file in your project - like css files, for example - so you can also specify a <code class="language-plaintext highlighter-rouge">type</code> value under the <code class="language-plaintext highlighter-rouge">scope</code> key.</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="c1"># an empty string here means all files in the project</span>
- <span class="na">type</span><span class="pi">:</span> <span class="s2">"</span><span class="s">posts"</span> <span class="c1"># previously `post` in Jekyll 2.2.</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">default"</span>
-</code></pre></div></div>
-
-<p>Now, this will only set the layout for files where the type is <code class="language-plaintext highlighter-rouge">posts</code>.
-The different types that are available to you are <code class="language-plaintext highlighter-rouge">pages</code>, <code class="language-plaintext highlighter-rouge">posts</code>, <code class="language-plaintext highlighter-rouge">drafts</code> or any collection in your site. While <code class="language-plaintext highlighter-rouge">type</code> is optional, you must specify a value for <code class="language-plaintext highlighter-rouge">path</code> when creating a <code class="language-plaintext highlighter-rouge">scope/values</code> pair.</p>
-
-<p>As mentioned earlier, you can set multiple scope/values pairs for <code class="language-plaintext highlighter-rouge">defaults</code>.</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span>
- <span class="na">type</span><span class="pi">:</span> <span class="s2">"</span><span class="s">pages"</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">my-site"</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">projects"</span>
- <span class="na">type</span><span class="pi">:</span> <span class="s2">"</span><span class="s">pages"</span> <span class="c1"># previously `page` in Jekyll 2.2.</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">project"</span> <span class="c1"># overrides previous default layout</span>
- <span class="na">author</span><span class="pi">:</span> <span class="s2">"</span><span class="s">Mr.</span><span class="nv"> </span><span class="s">Hyde"</span>
-</code></pre></div></div>
-
-<p>With these defaults, all pages would use the <code class="language-plaintext highlighter-rouge">my-site</code> layout. Any html files that exist in the <code class="language-plaintext highlighter-rouge">projects/</code> folder will use the <code class="language-plaintext highlighter-rouge">project</code> layout, if it exists. Those files will also have the <code class="language-plaintext highlighter-rouge">page.author</code> <a href="../variables/">liquid variable</a> set to <code class="language-plaintext highlighter-rouge">Mr. Hyde</code>.</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">collections</span><span class="pi">:</span>
- <span class="na">my_collection</span><span class="pi">:</span>
- <span class="na">output</span><span class="pi">:</span> <span class="no">true</span>
-
-<span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span>
- <span class="na">type</span><span class="pi">:</span> <span class="s2">"</span><span class="s">my_collection"</span> <span class="c1"># a collection in your site, in plural form</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">default"</span>
-</code></pre></div></div>
-
-<p>In this example, the <code class="language-plaintext highlighter-rouge">layout</code> is set to <code class="language-plaintext highlighter-rouge">default</code> inside the
-<a href="../collections/">collection</a> with the name <code class="language-plaintext highlighter-rouge">my_collection</code>.</p>
-
-<h3 id="glob-patterns-in-front-matter-defaults">Glob patterns in Front Matter defaults</h3>
-
-<p>It is also possible to use glob patterns (currently limited to patterns that contain <code class="language-plaintext highlighter-rouge">*</code>) when matching defaults. For example, it is possible to set specific layout for each <code class="language-plaintext highlighter-rouge">special-page.html</code> in any subfolder of <code class="language-plaintext highlighter-rouge">section</code> folder.<span class="version-badge" title="This feature is available starting version 3.7.0">3.7.0</span></p>
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">collections</span><span class="pi">:</span>
- <span class="na">my_collection</span><span class="pi">:</span>
- <span class="na">output</span><span class="pi">:</span> <span class="no">true</span>
-
-<span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">section/*/special-page.html"</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">specific-layout"</span>
-</code></pre></div></div>
-
-<div class="note warning">
- <h5>Globbing and Performance</h5>
- <p>
- Please note that globbing a path is known to have a negative effect on
- performance and is currently not optimized, especially on Windows.
- Globbing a path will increase your build times in proportion to the size
- of the associated collection directory.
- </p>
-</div>
-
-<h3 id="precedence">Precedence</h3>
-
-<p>Jekyll will apply all of the configuration settings you specify in the <code class="language-plaintext highlighter-rouge">defaults</code> section of your <code class="language-plaintext highlighter-rouge">_config.yml</code> file. However, you can choose to override settings from other scope/values pair by specifying a more specific path for the scope.</p>
-
-<p>You can see that in the second to last example above. First, we set the default page layout to <code class="language-plaintext highlighter-rouge">my-site</code>. Then, using a more specific path, we set the default layout for pages in the <code class="language-plaintext highlighter-rouge">projects/</code> path to <code class="language-plaintext highlighter-rouge">project</code>. This can be done with any value that you would set in the page or post front matter.</p>
-
-<p>Finally, if you set defaults in the site configuration by adding a <code class="language-plaintext highlighter-rouge">defaults</code> section to your <code class="language-plaintext highlighter-rouge">_config.yml</code> file, you can override those settings in a post or page file. All you need to do is specify the settings in the post or page front matter. For example:</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># In _config.yml</span>
-<span class="nn">...</span>
-<span class="na">defaults</span><span class="pi">:</span>
- <span class="pi">-</span>
- <span class="na">scope</span><span class="pi">:</span>
- <span class="na">path</span><span class="pi">:</span> <span class="s2">"</span><span class="s">projects"</span>
- <span class="na">type</span><span class="pi">:</span> <span class="s2">"</span><span class="s">pages"</span>
- <span class="na">values</span><span class="pi">:</span>
- <span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">project"</span>
- <span class="na">author</span><span class="pi">:</span> <span class="s2">"</span><span class="s">Mr.</span><span class="nv"> </span><span class="s">Hyde"</span>
- <span class="na">category</span><span class="pi">:</span> <span class="s2">"</span><span class="s">project"</span>
-<span class="nn">...</span>
-</code></pre></div></div>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># In projects/foo_project.md</span>
-<span class="nn">---</span>
-<span class="na">author</span><span class="pi">:</span> <span class="s2">"</span><span class="s">John</span><span class="nv"> </span><span class="s">Smith"</span>
-<span class="na">layout</span><span class="pi">:</span> <span class="s2">"</span><span class="s">foobar"</span>
-<span class="nn">---</span>
-<span class="s">The post text goes here...</span>
-</code></pre></div></div>
-
-<p>The <code class="language-plaintext highlighter-rouge">projects/foo_project.md</code> would have the <code class="language-plaintext highlighter-rouge">layout</code> set to <code class="language-plaintext highlighter-rouge">foobar</code> instead
-of <code class="language-plaintext highlighter-rouge">project</code> and the <code class="language-plaintext highlighter-rouge">author</code> set to <code class="language-plaintext highlighter-rouge">John Smith</code> instead of <code class="language-plaintext highlighter-rouge">Mr. Hyde</code> when
-the site is built.</p>
-
-<h2 id="default-configuration">Default Configuration</h2>
-
-<p>Jekyll runs with the following configuration options by default. Alternative
-settings for these options can be explicitly specified in the configuration
-file or on the command-line.</p>
-
-<div class="note warning">
- <h5>There are two unsupported kramdown options</h5>
- <p>
- Please note that both <code>remove_block_html_tags</code> and
- <code>remove_span_html_tags</code> are currently unsupported in Jekyll due
- to the fact that they are not included within the kramdown HTML converter.
- </p>
-</div>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># Where things are</span>
-<span class="na">source</span><span class="pi">:</span> <span class="s">.</span>
-<span class="na">destination</span><span class="pi">:</span> <span class="s">./_site</span>
-<span class="na">collections_dir</span><span class="pi">:</span> <span class="s">.</span>
-<span class="na">plugins_dir</span><span class="pi">:</span> <span class="s">_plugins</span>
-<span class="na">layouts_dir</span><span class="pi">:</span> <span class="s">_layouts</span>
-<span class="na">data_dir</span><span class="pi">:</span> <span class="s">_data</span>
-<span class="na">includes_dir</span><span class="pi">:</span> <span class="s">_includes</span>
-<span class="na">collections</span><span class="pi">:</span>
- <span class="na">posts</span><span class="pi">:</span>
- <span class="na">output</span><span class="pi">:</span> <span class="no">true</span>
-
-<span class="c1"># Handling Reading</span>
-<span class="na">safe</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">include</span><span class="pi">:</span> <span class="pi">[</span><span class="s2">"</span><span class="s">.htaccess"</span><span class="pi">]</span>
-<span class="na">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="s2">"</span><span class="s">Gemfile"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">Gemfile.lock"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">node_modules"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">vendor/bundle/"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">vendor/cache/"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">vendor/gems/"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">vendor/ruby/"</span><span class="pi">]</span>
-<span class="na">keep_files</span><span class="pi">:</span> <span class="pi">[</span><span class="s2">"</span><span class="s">.git"</span><span class="pi">,</span> <span class="s2">"</span><span class="s">.svn"</span><span class="pi">]</span>
-<span class="na">encoding</span><span class="pi">:</span> <span class="s2">"</span><span class="s">utf-8"</span>
-<span class="na">markdown_ext</span><span class="pi">:</span> <span class="s2">"</span><span class="s">markdown,mkdown,mkdn,mkd,md"</span>
-<span class="na">strict_front_matter</span><span class="pi">:</span> <span class="no">false</span>
-
-<span class="c1"># Filtering Content</span>
-<span class="na">show_drafts</span><span class="pi">:</span> <span class="no">null</span>
-<span class="na">limit_posts</span><span class="pi">:</span> <span class="m">0</span>
-<span class="na">future</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">unpublished</span><span class="pi">:</span> <span class="no">false</span>
-
-<span class="c1"># Plugins</span>
-<span class="na">whitelist</span><span class="pi">:</span> <span class="pi">[]</span>
-<span class="na">plugins</span><span class="pi">:</span> <span class="pi">[]</span>
-
-<span class="c1"># Conversion</span>
-<span class="na">markdown</span><span class="pi">:</span> <span class="s">kramdown</span>
-<span class="na">highlighter</span><span class="pi">:</span> <span class="s">rouge</span>
-<span class="na">lsi</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">excerpt_separator</span><span class="pi">:</span> <span class="s2">"</span><span class="se">\n\n</span><span class="s">"</span>
-<span class="na">incremental</span><span class="pi">:</span> <span class="no">false</span>
-
-<span class="c1"># Serving</span>
-<span class="na">detach</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">port</span><span class="pi">:</span> <span class="m">4000</span>
-<span class="na">host</span><span class="pi">:</span> <span class="s">127.0.0.1</span>
-<span class="na">baseurl</span><span class="pi">:</span> <span class="s2">"</span><span class="s">"</span> <span class="c1"># does not include hostname</span>
-<span class="na">show_dir_listing</span><span class="pi">:</span> <span class="no">false</span>
-
-<span class="c1"># Outputting</span>
-<span class="na">permalink</span><span class="pi">:</span> <span class="s">date</span>
-<span class="na">paginate_path</span><span class="pi">:</span> <span class="s">/page:num</span>
-<span class="na">timezone</span><span class="pi">:</span> <span class="no">null</span>
-
-<span class="na">quiet</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">verbose</span><span class="pi">:</span> <span class="no">false</span>
-<span class="na">defaults</span><span class="pi">:</span> <span class="pi">[]</span>
-
-<span class="na">liquid</span><span class="pi">:</span>
- <span class="na">error_mode</span><span class="pi">:</span> <span class="s">warn</span>
- <span class="na">strict_filters</span><span class="pi">:</span> <span class="no">false</span>
- <span class="na">strict_variables</span><span class="pi">:</span> <span class="no">false</span>
-
-<span class="c1"># Markdown Processors</span>
-<span class="na">rdiscount</span><span class="pi">:</span>
- <span class="na">extensions</span><span class="pi">:</span> <span class="pi">[]</span>
-
-<span class="na">redcarpet</span><span class="pi">:</span>
- <span class="na">extensions</span><span class="pi">:</span> <span class="pi">[]</span>
-
-<span class="na">kramdown</span><span class="pi">:</span>
- <span class="na">auto_ids</span><span class="pi">:</span> <span class="no">true</span>
- <span class="na">entity_output</span><span class="pi">:</span> <span class="s">as_char</span>
- <span class="na">toc_levels</span><span class="pi">:</span> <span class="s">1..6</span>
- <span class="na">smart_quotes</span><span class="pi">:</span> <span class="s">lsquo,rsquo,ldquo,rdquo</span>
- <span class="na">input</span><span class="pi">:</span> <span class="s">GFM</span>
- <span class="na">hard_wrap</span><span class="pi">:</span> <span class="no">false</span>
- <span class="na">footnote_nr</span><span class="pi">:</span> <span class="m">1</span>
- <span class="na">show_warnings</span><span class="pi">:</span> <span class="no">false</span>
-</code></pre></div></div>
-
-<h2 id="liquid-options">Liquid Options</h2>
-
-<p>Liquid’s response to errors can be configured by setting <code class="language-plaintext highlighter-rouge">error_mode</code>. The
-options are</p>
-
<ul>
- <li>
-<code class="language-plaintext highlighter-rouge">lax</code> — Ignore all errors.</li>
- <li>
-<code class="language-plaintext highlighter-rouge">warn</code> — Output a warning on the console for each error.</li>
- <li>
-<code class="language-plaintext highlighter-rouge">strict</code> — Output an error message and stop the build.</li>
+ <li><a href="/docs/configuration/options/">Configuration Options</a></li>
+ <li><a href="/docs/configuration/default/">Default Configuration</a></li>
+ <li><a href="/docs/configuration/front-matter-defaults/">Front Matter Defaults</a></li>
+ <li><a href="/docs/configuration/environments/">Environments</a></li>
+ <li><a href="/docs/configuration/markdown/">Markdown Options</a></li>
+ <li><a href="/docs/configuration/liquid/">Liquid Options</a></li>
+ <li><a href="/docs/configuration/webrick/">Webrick Options</a></li>
+ <li><a href="/docs/configuration/incremental-regeneration/">Incremental Regeneration</a></li>
</ul>
-<p>You can also configure Liquid’s renderer to catch non-assigned variables and
-non-existing filters by setting <code class="language-plaintext highlighter-rouge">strict_variables</code> and / or <code class="language-plaintext highlighter-rouge">strict_filters</code>
-to <code class="language-plaintext highlighter-rouge">true</code> respectively. <span class="version-badge" title="This feature is available starting version 3.8.0">3.8.0</span></p>
+ </article>
+ </div>
-<p>Do note that while <code class="language-plaintext highlighter-rouge">error_mode</code> configures Liquid’s parser, the <code class="language-plaintext highlighter-rouge">strict_variables</code>
-and <code class="language-plaintext highlighter-rouge">strict_filters</code> options configure Liquid’s renderer and are consequently,
-mutually exclusive.</p>
-
-<h2 id="markdown-options">Markdown Options</h2>
-
-<p>The various Markdown renderers supported by Jekyll sometimes have extra options
-available.</p>
-
-<h3 id="redcarpet">Redcarpet</h3>
-
-<p>Redcarpet can be configured by providing an <code class="language-plaintext highlighter-rouge">extensions</code> sub-setting, whose
-value should be an array of strings. Each string should be the name of one of
-the <code class="language-plaintext highlighter-rouge">Redcarpet::Markdown</code> class’s extensions; if present in the array, it will
-set the corresponding extension to <code class="language-plaintext highlighter-rouge">true</code>.</p>
-
-<p>Jekyll handles two special Redcarpet extensions:</p>
-
-<ul>
- <li>
-<code class="language-plaintext highlighter-rouge">no_fenced_code_blocks</code> — By default, Jekyll sets the <code class="language-plaintext highlighter-rouge">fenced_code_blocks</code>
-extension (for delimiting code blocks with triple tildes or triple backticks)
-to <code class="language-plaintext highlighter-rouge">true</code>, probably because GitHub’s eager adoption of them is starting to make
-them inescapable. Redcarpet’s normal <code class="language-plaintext highlighter-rouge">fenced_code_blocks</code> extension is inert
-when used with Jekyll; instead, you can use this inverted version of the
-extension for disabling fenced code.</li>
-</ul>
-
-<p>Note that you can also specify a language for highlighting after the first
-delimiter:</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code> ```ruby
- # ...ruby code
- ```
-</code></pre></div></div>
-
-<p>With both fenced code blocks and highlighter enabled, this will statically
-highlight the code; without any syntax highlighter, it will add a
-<code class="language-plaintext highlighter-rouge">class="LANGUAGE"</code> attribute to the <code class="language-plaintext highlighter-rouge"><code></code> element, which can be used as a
-hint by various JavaScript code highlighting libraries.</p>
-
-<ul>
- <li>
-<code class="language-plaintext highlighter-rouge">smart</code> — This pseudo-extension turns on SmartyPants, which converts
-straight quotes to curly quotes and runs of hyphens to em (<code class="language-plaintext highlighter-rouge">---</code>) and en (<code class="language-plaintext highlighter-rouge">--</code>) dashes.</li>
-</ul>
-
-<p>All other extensions retain their usual names from Redcarpet, and no renderer
-options aside from <code class="language-plaintext highlighter-rouge">smart</code> can be specified in Jekyll. <a href="https://github.com/vmg/redcarpet/blob/v3.2.2/README.markdown#and-its-like-really-simple-to-use">A list of available
-extensions can be found in the Redcarpet README file.</a>
-Make sure you’re looking at the README for the right version of
-Redcarpet: Jekyll currently uses v3.2.x. The most commonly used
-extensions are:</p>
-
-<ul>
- <li><code class="language-plaintext highlighter-rouge">tables</code></li>
- <li><code class="language-plaintext highlighter-rouge">no_intra_emphasis</code></li>
- <li><code class="language-plaintext highlighter-rouge">autolink</code></li>
-</ul>
-
-<h3 id="custom-markdown-processors">Custom Markdown Processors</h3>
-
-<p>If you’re interested in creating a custom markdown processor, you’re in luck! Create a new class in the <code class="language-plaintext highlighter-rouge">Jekyll::Converters::Markdown</code> namespace:</p>
-
-<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="k">class</span> <span class="nc">Jekyll::Converters::Markdown::MyCustomProcessor</span>
- <span class="k">def</span> <span class="nf">initialize</span><span class="p">(</span><span class="n">config</span><span class="p">)</span>
- <span class="nb">require</span> <span class="s1">'funky_markdown'</span>
- <span class="vi">@config</span> <span class="o">=</span> <span class="n">config</span>
- <span class="k">rescue</span> <span class="no">LoadError</span>
- <span class="no">STDERR</span><span class="p">.</span><span class="nf">puts</span> <span class="s1">'You are missing a library required for Markdown. Please run:'</span>
- <span class="no">STDERR</span><span class="p">.</span><span class="nf">puts</span> <span class="s1">' $ [sudo] gem install funky_markdown'</span>
- <span class="k">raise</span> <span class="no">FatalException</span><span class="p">.</span><span class="nf">new</span><span class="p">(</span><span class="s2">"Missing dependency: funky_markdown"</span><span class="p">)</span>
- <span class="k">end</span>
-
- <span class="k">def</span> <span class="nf">convert</span><span class="p">(</span><span class="n">content</span><span class="p">)</span>
- <span class="o">::</span><span class="no">FunkyMarkdown</span><span class="p">.</span><span class="nf">new</span><span class="p">(</span><span class="n">content</span><span class="p">).</span><span class="nf">convert</span>
- <span class="k">end</span>
-<span class="k">end</span>
-</code></pre></div></div>
-
-<p>Once you’ve created your class and have it properly set up either as a plugin
-in the <code class="language-plaintext highlighter-rouge">_plugins</code> folder or as a gem, specify it in your <code class="language-plaintext highlighter-rouge">_config.yml</code>:</p>
-
-<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">markdown</span><span class="pi">:</span> <span class="s">MyCustomProcessor</span>
-</code></pre></div></div>
-
-<h2 id="incremental-regeneration">Incremental Regeneration</h2>
-<div class="note warning">
- <h5>Incremental regeneration is still an experimental feature</h5>
- <p>
- While incremental regeneration will work for the most common cases, it will
- not work correctly in every scenario. Please be extremely cautious when
- using the feature, and report any problems not listed below by
- <a href="https://github.com/jekyll/jekyll/issues/new">opening an issue on GitHub</a>.
- </p>
-</div>
-
-<p>Incremental regeneration helps shorten build times by only generating documents
-and pages that were updated since the previous build. It does this by keeping
-track of both file modification times and inter-document dependencies in the
-<code class="language-plaintext highlighter-rouge">.jekyll-metadata</code> file.</p>
-
-<p>Under the current implementation, incremental regeneration will only generate a
-document or page if either it, or one of its dependencies, is modified. Currently,
-the only types of dependencies tracked are includes (using the
-<code class="language-plaintext highlighter-rouge">{% include %}</code> tag) and layouts. This means that plain
-references to other documents (for example, the common case of iterating over
-<code class="language-plaintext highlighter-rouge">site.posts</code> in a post listings page) will not be detected as a dependency.</p>
-
-<p>To remedy some of these shortfalls, putting <code class="language-plaintext highlighter-rouge">regenerate: true</code> in the front-matter
-of a document will force Jekyll to regenerate it regardless of whether it has been
-modified. Note that this will generate the specified document only; references
-to other documents’ contents will not work since they won’t be re-rendered.</p>
-
-<p>Incremental regeneration can be enabled via the <code class="language-plaintext highlighter-rouge">--incremental</code> flag (<code class="language-plaintext highlighter-rouge">-I</code> for
-short) from the command-line or by setting <code class="language-plaintext highlighter-rouge">incremental: true</code> in your
-configuration file.</p>
-
+ <div class="unit one-fifth hide-on-mobiles">
+ <aside>
+
+ <h4>Getting Started</h4>
+ <ul>
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- <div class="section-nav">
- <div class="left align-right">
+ <li>
+ <a href="/docs/">
+ Quickstart
+ </a>
+ </li>
+
-
-
- <a href="/docs/structure/" class="prev">Back</a>
+ <li>
+ <a href="/docs/ruby-101/">
+ Ruby 101
+ </a>
+ </li>
+
- </div>
- <div class="right align-left">
+ <li>
+ <a href="/docs/installation/">
+ Installation
+ </a>
+ </li>
+
-
-
- <a href="/docs/frontmatter/" class="next">Next</a>
+ <li>
+ <a href="/docs/community/">
+ Community
+ </a>
+ </li>
+
- </div>
- </div>
- <div class="clear"></div>
+ <li>
+ <a href="/docs/step-by-step/01-setup/">
+ Step by Step Tutorial
+ </a>
+ </li>
+
+ </ul>
- </article>
- </div>
-
- <div class="unit one-fifth hide-on-mobiles">
- <aside>
+ <h4>Build</h4>
+ <ul>
+
+
+ <li>
+ <a href="/docs/usage/">
+ Command Line Usage
+ </a>
+ </li>
+
+
+ <li class="current">
+ <a href="/docs/configuration/">
+ Configuration
+ </a>
+ </li>
+
+ </ul>
- <h4>Getting Started</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/home/">Welcome</a></li>
-
-
-
- <li class=""><a href="/docs/quickstart/">Quick-start guide</a></li>
-
-
-
- <li class=""><a href="/docs/installation/">Installation</a></li>
-
-
-
- <li class=""><a href="/docs/windows/">Jekyll on Windows</a></li>
-
-
-
- <li class=""><a href="/docs/usage/">Basic Usage</a></li>
-
-
-
- <li class=""><a href="/docs/structure/">Directory structure</a></li>
-
-
-
- <li class="current"><a href="/docs/configuration/">Configuration</a></li>
-
-</ul>
-
+ <h4>Content</h4>
+ <ul>
+
+
+ <li>
+ <a href="/docs/pages/">
+ Pages
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/posts/">
+ Posts
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/front-matter/">
+ Front Matter
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/collections/">
+ Collections
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/datafiles/">
+ Data Files
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/assets/">
+ Assets
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/static-files/">
+ Static Files
+ </a>
+ </li>
+
+ </ul>
- <h4>Your Content</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/frontmatter/">Front Matter</a></li>
-
-
-
- <li class=""><a href="/docs/posts/">Writing posts</a></li>
-
-
-
- <li class=""><a href="/docs/drafts/">Working with drafts</a></li>
-
-
-
- <li class=""><a href="/docs/pages/">Creating pages</a></li>
-
-
-
- <li class=""><a href="/docs/static-files/">Static Files</a></li>
-
-
-
- <li class=""><a href="/docs/variables/">Variables</a></li>
-
-
-
- <li class=""><a href="/docs/collections/">Collections</a></li>
-
-
-
- <li class=""><a href="/docs/datafiles/">Data Files</a></li>
-
-
-
- <li class=""><a href="/docs/assets/">Assets</a></li>
-
-
-
- <li class=""><a href="/docs/migrations/">Blog migrations</a></li>
-
-</ul>
-
+ <h4>Site Structure</h4>
+ <ul>
+
+
+ <li>
+ <a href="/docs/structure/">
+ Directory Structure
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/liquid/">
+ Liquid
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/variables/">
+ Variables
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/includes/">
+ Includes
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/layouts/">
+ Layouts
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/permalinks/">
+ Permalinks
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/themes/">
+ Themes
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/pagination/">
+ Pagination
+ </a>
+ </li>
+
+ </ul>
- <h4>Customization</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/templates/">Templates</a></li>
-
-
-
- <li class=""><a href="/docs/includes/">Includes</a></li>
-
-
-
- <li class=""><a href="/docs/permalinks/">Permalinks</a></li>
-
-
-
- <li class=""><a href="/docs/pagination/">Pagination</a></li>
-
-
-
- <li class=""><a href="/docs/plugins/">Plugins</a></li>
-
-
-
- <li class=""><a href="/docs/themes/">Themes</a></li>
-
-
-
- <li class=""><a href="/docs/extras/">Extras</a></li>
-
-</ul>
-
+ <h4>Guides</h4>
+ <ul>
+
+
+ <li>
+ <a href="/docs/plugins/">
+ Plugins
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/migrations/">
+ Blog Migrations
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/upgrading/">
+ Upgrading
+ </a>
+ </li>
+
+
+ <li>
+ <a href="/docs/deployment/">
+ Deployment
+ </a>
+ </li>
+
+ </ul>
- <h4>Deployment</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/github-pages/">GitHub Pages</a></li>
-
-
-
- <li class=""><a href="/docs/deployment-methods/">Deployment methods</a></li>
-
-
-
- <li class=""><a href="/docs/continuous-integration/">Continuous Integration</a></li>
-
-</ul>
-
-
- <h4>Miscellaneous</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/troubleshooting/">Troubleshooting</a></li>
-
-
-
- <li class=""><a href="/docs/sites/">Sites using Jekyll</a></li>
-
-
-
- <li class=""><a href="/docs/resources/">Resources</a></li>
-
-
-
- <li class=""><a href="/docs/upgrading/0-to-2/">Upgrading from 0.x to 2.x</a></li>
-
-
-
- <li class=""><a href="/docs/upgrading/2-to-3/">Upgrading from 2.x to 3.x</a></li>
-
-</ul>
-
-
- <h4>Meta</h4>
- <ul>
-
-
-
- <li class=""><a href="/docs/contributing/">Contributing</a></li>
-
-
-
- <li class=""><a href="/docs/maintaining/">Maintaining Jekyll</a></li>
-
-
-
- <li class=""><a href="/docs/conduct/">Code of Conduct</a></li>
-
-
-
- <li class=""><a href="/docs/history/">History</a></li>
-
-</ul>
-
-
</aside>
</div>
<div class="clear"></div>
@@ -1363,16 +529,25 @@
<footer>
<div class="grid">
<div class="unit one-third center-on-mobiles">
- <p>The contents of this website are <br>© 2020 under the terms of the <a href="https://github.com/jekyll/jekyll/blob/master/LICENSE">MIT License</a>.</p>
+ <p>Jekyll is lovingly maintained by the <a href="/team/">core team</a> of volunteers. </p>
+ <p>The contents of this website are <br />© 2019 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 class="unit two-thirds align-right center-on-mobiles">
+ <p>
+ Jekyll is funded thanks to its
+ <a href="https://github.com/jekyll/jekyll#sponsors">
+ sponsors!
</a>
</p>
</div>
</div>
</footer>