jekyll-docs 3.5.2 → 3.6.0

data/site/docs/continuous-integration/buddyworks/index.html

@@ -4,28 +4,28 @@
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width,initial-scale=1">
-  <meta name="generator" content="Jekyll v3.5.2">
+  <meta name="generator" content="Jekyll v3.6.0">
   <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>BuddyWorks | Jekyll • Simple, blog-aware, static sites</title>
-<meta property="og:title" content="BuddyWorks">
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
+<title>Buddy | Jekyll • Simple, blog-aware, static sites</title>
+<meta property="og:title" content="Buddy">
 <meta property="og:locale" content="en_US">
-<meta name="description" content="BuddyWorks is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.">
-<meta property="og:description" content="BuddyWorks is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.">
+<meta name="description" content="Buddy is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.">
+<meta property="og:description" content="Buddy is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.">
 <link rel="canonical" href="https://jekyllrb.com/docs/continuous-integration/buddyworks/">
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/buddyworks/">
 <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-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-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":"BuddyWorks","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"BuddyWorks is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/buddyworks/"},"url":"https://jekyllrb.com/docs/continuous-integration/buddyworks/"}</script>
+{"name":null,"description":"Buddy is a Docker-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports GitHub, Bitbucket, and GitLab repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.","url":"https://jekyllrb.com/docs/continuous-integration/buddyworks/","headline":"Buddy","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/buddyworks/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -286,8 +286,8 @@
           <div class="improve right hide-on-mobiles">
             <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/continuous-integration/buddyworks.md"><i class="fa fa-pencil"></i>  Improve this page</a>
           </div>
-          <h1>BuddyWorks</h1>
-          <p><a href="https://buddy.works">BuddyWorks</a> is a <a href="https://www.docker.com/">Docker</a>-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports <a href="https://github.com">GitHub</a>, <a href="https://bitbucket.org/">Bitbucket</a>, and <a href="https://gitlab.com">GitLab</a> repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.</p>
+          <h1>Buddy</h1>
+          <p><a href="https://buddy.works">Buddy</a> is a <a href="https://www.docker.com/">Docker</a>-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports <a href="https://github.com">GitHub</a>, <a href="https://bitbucket.org/">Bitbucket</a>, and <a href="https://gitlab.com">GitLab</a> repositories, and can be installed on-premises or used in cloud. The following guide will show you how to set up a free environment to build and test your Jekyll project.</p>
 
 <h2 id="1-getting-started">1. Getting started</h2>
 
@@ -308,8 +308,7 @@
 
 <p>If you prefer configuration as code over GUI, you can generate a <code class="highlighter-rouge">buddy.yml</code> that will create a pipeline with the Jekyll action once you push it to the target branch:</p>
 
-<div class="language-ruby highlighter-rouge">
-<pre class="highlight"><code><span class="o">-</span> <span class="ss">pipeline: </span><span class="s2">"Build and Deploy Jekyll site"</span>
+<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="o">-</span> <span class="ss">pipeline: </span><span class="s2">"Build and Deploy Jekyll site"</span>
   <span class="ss">trigger_mode: </span><span class="s2">"ON_EVERY_PUSH"</span>
   <span class="ss">ref_name: </span><span class="s2">"master"</span>
   <span class="ss">actions:
@@ -320,16 +319,15 @@
     <span class="ss">execute_commands:
     </span><span class="o">-</span> <span class="s2">"chown jekyll:jekyll $WORKING_DIR"</span>
     <span class="o">-</span> <span class="s2">"jekyll build"</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <h2 id="4-setting-up-on-premises-server">4. Setting up on-premises server</h2>
 
-<p>The self-hosted version of BuddyWorks can be installed on any type of server supporting Docker, including <a href="https://buddy.works/knowledge/standalone/installation-linux">Linux</a>, <a href="https://buddy.works/knowledge/standalone/installation-mac-osx">Mac</a>, <a href="https://buddy.works/knowledge/standalone/installation-amazon-ec2">AWS EC2</a>, <a href="https://buddy.works/knowledge/standalone/installation-digitalocean">DigitalOcean</a>, and <a href="https://buddy.works/knowledge/standalone/installation-azure">Microsoft Azure</a>.</p>
+<p>The self-hosted version of Buddy can be installed on any type of server supporting Docker, including <a href="https://buddy.works/knowledge/standalone/installation-linux">Linux</a>, <a href="https://buddy.works/knowledge/standalone/installation-mac-osx">Mac</a>, <a href="https://buddy.works/knowledge/standalone/installation-amazon-ec2">AWS EC2</a>, <a href="https://buddy.works/knowledge/standalone/installation-digitalocean">DigitalOcean</a>, and <a href="https://buddy.works/knowledge/standalone/installation-azure">Microsoft Azure</a>.</p>
 
 <h2 id="5-questions">5. Questions?</h2>
 
-<p>This entire guide is open-source. Go ahead and <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/continuous-integration/buddyworks.md">edit it</a> if you want to expand it or have a fix or <a href="https://jekyllrb.com/help/">ask for help</a> if you run into trouble and need assistance. BuddyWorks also has an <a href="http://forum.buddy.works/">online community</a> for help.</p>
+<p>This entire guide is open-source. Go ahead and <a href="https://github.com/jekyll/jekyll/edit/master/docs/_docs/continuous-integration/buddyworks.md">edit it</a> if you want to expand it or have a fix or <a href="https://jekyllrb.com/help/">ask for help</a> if you run into trouble and need assistance. Buddy also has an <a href="http://forum.buddy.works/">online community</a> for help.</p>
 
 
           

data/site/docs/continuous-integration/circleci/index.html

@@ -4,13 +4,13 @@
 <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.2">
+  <meta name="generator" content="Jekyll v3.6.0">
   <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 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>CircleCI | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="CircleCI">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/circleci/">
 <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-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-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":"CircleCI","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"Building, testing, and deploying your Jekyll-generated website can quickly be done with CircleCI, a continuous integration &amp; delivery tool. CircleCI supports GitHub and Bitbucket, and you can get started for free using an open-source or private repository.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/circleci/"},"url":"https://jekyllrb.com/docs/continuous-integration/circleci/"}</script>
+{"name":null,"description":"Building, testing, and deploying your Jekyll-generated website can quickly be done with CircleCI, a continuous integration &amp; delivery tool. CircleCI supports GitHub and Bitbucket, and you can get started for free using an open-source or private repository.","url":"https://jekyllrb.com/docs/continuous-integration/circleci/","headline":"CircleCI","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/circleci/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -305,15 +305,13 @@
 
 <p>The easiest way to manage dependencies for a Jekyll project (with or without CircleCI) is via a <a href="http://bundler.io/gemfile.html">Gemfile</a>. You’d want to have Jekyll, any Jekyll plugins, <a href="#html-proofer">HTML Proofer</a>, and any other gems that you are using in the <code class="highlighter-rouge">Gemfile</code>. Don’t forget to version <code class="highlighter-rouge">Gemfile.lock</code> as well. Here’s an example <code class="highlighter-rouge">Gemfile</code>:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">source 'https://rubygems.org'</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="s">source 'https://rubygems.org'</span>
 
 <span class="s">ruby '2.4.0'</span>
 
 <span class="s">gem 'jekyll'</span>
 <span class="s">gem 'html-proofer'</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>CircleCI detects when <code class="highlighter-rouge">Gemfile</code> is present is will automatically run <code class="highlighter-rouge">bundle install</code> for you in the <code class="highlighter-rouge">dependencies</code> phase.</p>
 
@@ -321,30 +319,25 @@
 
 <p>The most basic test that can be run is simply seeing if <code class="highlighter-rouge">jekyll build</code> actually works. This is a blocker, a dependency if you will,  for other tests you might run on the generate site. So we’ll run Jekyll, via Bundler, in the <code class="highlighter-rouge">dependencies</code> phase.</p>
 
-<div class="highlighter-rouge">
-<pre class="highlight"><code>dependencies:
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>dependencies:
   post:
     - bundle exec jekyll build
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <h3 id="html-proofer">HTML Proofer</h3>
 
 <p>With your site built, it’s useful to run tests to check for valid HTML, broken links, etc. There’s a few tools out there but <a href="https://github.com/gjtorikian/html-proofer">HTML Proofer</a> is popular amongst Jekyll users. We’ll run it in the <code class="highlighter-rouge">test</code> phase with a few preferred flags. Check out the <code class="highlighter-rouge">html-proofer</code> <a href="https://github.com/gjtorikian/html-proofer/blob/master/README.md#configuration">README</a> for all available flags, or run <code class="highlighter-rouge">htmlproofer --help</code> locally.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">test</span><span class="pi">:</span>
-  <span class="s">post</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">test</span><span class="pi">:</span>
+  <span class="na">post</span><span class="pi">:</span>
     <span class="pi">-</span> <span class="s">bundle exec htmlproofer ./_site --check-html --disable-external</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <h2 id="complete-example-circleyml-file">Complete Example circle.yml File</h2>
 
 <p>When you put it all together, here’s an example of what that <code class="highlighter-rouge">circle.yml</code> file could look like:</p>
 
-<div class="highlighter-rouge">
-<pre class="highlight"><code>machine:
+<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>machine:
   environment:
     NOKOGIRI_USE_SYSTEM_LIBRARIES: true # speeds up installation of html-proofer
 
@@ -361,8 +354,7 @@ deployment:
     branch: master
     commands:
       - rsync -va --delete ./_site username@my-website:/var/html
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <h2 id="questions">Questions?</h2>
 

data/site/docs/continuous-integration/index.html

@@ -4,13 +4,13 @@
 <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.2">
+  <meta name="generator" content="Jekyll v3.6.0">
   <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 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Continuous Integration | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Continuous Integration">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/">
 <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-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-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":"Continuous Integration","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"Continuous Integration (CI) enables you to publish your Jekyll generated website with confidence by automating the quality assurance and deployment processes. You can quickly get started using CI with one of the providers below:","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/"},"url":"https://jekyllrb.com/docs/continuous-integration/"}</script>
+{"name":null,"description":"Continuous Integration (CI) enables you to publish your Jekyll generated website with confidence by automating the quality assurance and deployment processes. You can quickly get started using CI with one of the providers below:","url":"https://jekyllrb.com/docs/continuous-integration/","headline":"Continuous Integration","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -292,7 +292,7 @@
 <ul>
   <li><a href="travis-ci">Travis CI</a></li>
   <li><a href="circleci">CircleCI</a></li>
-  <li><a href="buddyworks">BuddyWorks</a></li>
+  <li><a href="buddyworks">Buddy</a></li>
 </ul>
 
           

data/site/docs/continuous-integration/travis-ci/index.html

@@ -4,13 +4,13 @@
 <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.2">
+  <meta name="generator" content="Jekyll v3.6.0">
   <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 -->
+  <!-- Begin Jekyll SEO tag v2.3.0 -->
 <title>Travis CI | Jekyll • Simple, blog-aware, static sites</title>
 <meta property="og:title" content="Travis CI">
 <meta property="og:locale" content="en_US">
@@ -20,12 +20,12 @@
 <meta property="og:url" content="https://jekyllrb.com/docs/continuous-integration/travis-ci/">
 <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-08-12T13:36:54-07:00">
+<meta property="article:published_time" content="2017-10-24T08:07:43-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":"Travis CI","datePublished":"2017-08-12T13:36:54-07:00","dateModified":"2017-08-12T13:36:54-07:00","description":"You can easily test your website build against one or more versions of Ruby. The following guide will show you how to set up a free build environment on Travis, with GitHub integration for pull requests.","publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/travis-ci/"},"url":"https://jekyllrb.com/docs/continuous-integration/travis-ci/"}</script>
+{"name":null,"description":"You can easily test your website build against one or more versions of Ruby. The following guide will show you how to set up a free build environment on Travis, with GitHub integration for pull requests.","url":"https://jekyllrb.com/docs/continuous-integration/travis-ci/","headline":"Travis CI","dateModified":"2017-10-24T08:07:43-07:00","datePublished":"2017-10-24T08:07:43-07:00","sameAs":null,"@type":"BlogPosting","author":null,"image":null,"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jekyllrb.com/img/logo-2x.png"}},"mainEntityOfPage":{"@type":"WebPage","@id":"https://jekyllrb.com/docs/continuous-integration/travis-ci/"},"@context":"http://schema.org"}</script>
 <!-- End Jekyll SEO tag -->
 
   <!--[if lt IE 9]>
@@ -318,14 +318,12 @@ or write a Ruby script which utilizes the gem.</p>
 
 <h3 id="the-html-proofer-executable">The HTML Proofer Executable</h3>
 
-<div class="language-sh highlighter-rouge">
-<pre class="highlight"><code><span class="c">#!/usr/bin/env bash</span>
-<span class="nb">set</span> -e <span class="c"># halt script on error</span>
+<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c">#!/usr/bin/env bash</span>
+<span class="nb">set</span> <span class="nt">-e</span> <span class="c"># halt script on error</span>
 
 bundle <span class="nb">exec </span>jekyll build
 bundle <span class="nb">exec </span>htmlproofer ./_site
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>Some options can be specified via command-line switches. Check out the
 <code class="highlighter-rouge">html-proofer</code> README for more information about these switches, or run
@@ -333,22 +331,18 @@ bundle <span class="nb">exec </span>htmlproofer ./_site
 
 <p>For example to avoid testing external sites, use this command:</p>
 
-<div class="language-sh highlighter-rouge">
-<pre class="highlight"><code><span class="gp">$ </span>bundle <span class="nb">exec </span>htmlproofer ./_site --disable-external
-</code></pre>
-</div>
+<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nv">$ </span>bundle <span class="nb">exec </span>htmlproofer ./_site <span class="nt">--disable-external</span>
+</code></pre></div></div>
 
 <h3 id="the-html-proofer-library">The HTML Proofer Library</h3>
 
 <p>You can also invoke <code class="highlighter-rouge">html-proofer</code> in Ruby scripts (e.g. in a Rakefile):</p>
 
-<div class="language-ruby highlighter-rouge">
-<pre class="highlight"><code><span class="c1">#!/usr/bin/env ruby</span>
+<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1">#!/usr/bin/env ruby</span>
 
 <span class="nb">require</span> <span class="s1">'html-proofer'</span>
 <span class="no">HTMLProofer</span><span class="p">.</span><span class="nf">check_directory</span><span class="p">(</span><span class="s2">"./_site"</span><span class="p">).</span><span class="nf">run</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>Options are given as a second argument to <code class="highlighter-rouge">.new</code>, and are encoded in a
 symbol-keyed Ruby Hash. For more information about the configuration options,
@@ -363,77 +357,65 @@ an explanation of each line.</p>
 
 <p><strong>Note:</strong> You will need a Gemfile as well, <a href="https://docs.travis-ci.com/user/languages/ruby/#Dependency-Management">Travis will automatically install</a> the dependencies based on the referenced gems:</p>
 
-<div class="language-ruby highlighter-rouge">
-<pre class="highlight"><code><span class="n">source</span> <span class="s2">"https://rubygems.org"</span>
+<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="n">source</span> <span class="s2">"https://rubygems.org"</span>
 
 <span class="n">gem</span> <span class="s2">"jekyll"</span>
 <span class="n">gem</span> <span class="s2">"html-proofer"</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>Your <code class="highlighter-rouge">.travis.yml</code> file should look like this:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">language</span><span class="pi">:</span> <span class="s">ruby</span>
-<span class="s">rvm</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">language</span><span class="pi">:</span> <span class="s">ruby</span>
+<span class="na">rvm</span><span class="pi">:</span>
 <span class="pi">-</span> <span class="s">2.3.3</span>
 
-<span class="s">before_script</span><span class="pi">:</span>
+<span class="na">before_script</span><span class="pi">:</span>
  <span class="pi">-</span> <span class="s">chmod +x ./script/cibuild</span> <span class="c1"># or do this locally and commit</span>
 
 <span class="c1"># Assume bundler is being used, therefore</span>
 <span class="c1"># the `install` step will run `bundle install` by default.</span>
-<span class="s">script</span><span class="pi">:</span> <span class="s">./script/cibuild</span>
+<span class="na">script</span><span class="pi">:</span> <span class="s">./script/cibuild</span>
 
 <span class="c1"># branch whitelist, only for GitHub Pages</span>
-<span class="s">branches</span><span class="pi">:</span>
-  <span class="s">only</span><span class="pi">:</span>
+<span class="na">branches</span><span class="pi">:</span>
+  <span class="na">only</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">gh-pages</span>     <span class="c1"># test the gh-pages branch</span>
   <span class="pi">-</span> <span class="s">/pages-(.*)/</span> <span class="c1"># test every branch which starts with "pages-"</span>
 
-<span class="s">env</span><span class="pi">:</span>
-  <span class="s">global</span><span class="pi">:</span>
+<span class="na">env</span><span class="pi">:</span>
+  <span class="na">global</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">NOKOGIRI_USE_SYSTEM_LIBRARIES=true</span> <span class="c1"># speeds up installation of html-proofer</span>
 
-<span class="s">sudo</span><span class="pi">:</span> <span class="s">false</span> <span class="c1"># route your build to the container-based infrastructure for a faster build</span>
-</code></pre>
-</div>
+<span class="na">sudo</span><span class="pi">:</span> <span class="no">false</span> <span class="c1"># route your build to the container-based infrastructure for a faster build</span>
+</code></pre></div></div>
 
 <p>Ok, now for an explanation of each line:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">language</span><span class="pi">:</span> <span class="s">ruby</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">language</span><span class="pi">:</span> <span class="s">ruby</span>
+</code></pre></div></div>
 
 <p>This line tells Travis to use a Ruby build container. It gives your script
 access to Bundler, RubyGems, and a Ruby runtime.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">rvm</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">rvm</span><span class="pi">:</span>
 <span class="pi">-</span> <span class="s">2.3.3</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>RVM is a popular Ruby Version Manager (like rbenv, chruby, etc). This
 directive tells Travis the Ruby version to use when running your test
 script.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">before_script</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">before_script</span><span class="pi">:</span>
  <span class="pi">-</span> <span class="s">chmod +x ./script/cibuild</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>The build script file needs to have the <em>executable</em> attribute set or
 Travis will fail with a permission denied error. You can also run this
 locally and commit the permissions directly, thus rendering this step
 irrelevant.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">script</span><span class="pi">:</span> <span class="s">./script/cibuild</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">script</span><span class="pi">:</span> <span class="s">./script/cibuild</span>
+</code></pre></div></div>
 
 <p>Travis allows you to run any arbitrary shell script to test your site. One
 convention is to put all scripts for your project in the <code class="highlighter-rouge">script</code>
@@ -441,22 +423,18 @@ directory, and to call your test script <code class="highlighter-rouge">cibuild<
 customizable. If your script won’t change much, you can write your test
 incantation here directly:</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">install</span><span class="pi">:</span> <span class="s">gem install jekyll html-proofer</span>
-<span class="s">script</span><span class="pi">:</span> <span class="s">jekyll build &amp;&amp; htmlproofer ./_site</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">install</span><span class="pi">:</span> <span class="s">gem install jekyll html-proofer</span>
+<span class="na">script</span><span class="pi">:</span> <span class="s">jekyll build &amp;&amp; htmlproofer ./_site</span>
+</code></pre></div></div>
 
 <p>The <code class="highlighter-rouge">script</code> directive can be absolutely any valid shell command.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="c1"># branch whitelist, only for GitHub Pages</span>
-<span class="s">branches</span><span class="pi">:</span>
-  <span class="s">only</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># branch whitelist, only for GitHub Pages</span>
+<span class="na">branches</span><span class="pi">:</span>
+  <span class="na">only</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">gh-pages</span>     <span class="c1"># test the gh-pages branch</span>
   <span class="pi">-</span> <span class="s">/pages-(.*)/</span> <span class="c1"># test every branch which starts with "pages-"</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>You want to ensure the Travis builds for your site are being run only on
 the branch or branches which contain your site. One means of ensuring this
@@ -470,12 +448,10 @@ prefixed, exemplified above with the <code class="highlighter-rouge">/pages-(.*)
 <p>The <code class="highlighter-rouge">branches</code> directive is completely optional. Travis will build from every
 push to any branch of your repo if leave it out.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">env</span><span class="pi">:</span>
-  <span class="s">global</span><span class="pi">:</span>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">env</span><span class="pi">:</span>
+  <span class="na">global</span><span class="pi">:</span>
   <span class="pi">-</span> <span class="s">NOKOGIRI_USE_SYSTEM_LIBRARIES=true</span> <span class="c1"># speeds up installation of html-proofer</span>
-</code></pre>
-</div>
+</code></pre></div></div>
 
 <p>Using <code class="highlighter-rouge">html-proofer</code>? You’ll want this environment variable. Nokogiri, used
 to parse HTML files in your compiled site, comes bundled with libraries
@@ -491,10 +467,8 @@ environment variable <code class="highlighter-rouge">NOKOGIRI_USE_SYSTEM_LIBRARI
    servers, which Jekyll will mistakenly read and explode on.</p>
 </div>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="nv">vendor</span><span class="pi">]</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">exclude</span><span class="pi">:</span> <span class="pi">[</span><span class="nv">vendor</span><span class="pi">]</span>
+</code></pre></div></div>
 
 <p>By default you should supply the <code class="highlighter-rouge">sudo: false</code> command to Travis. This command
 explicitly tells Travis to run your build on Travis’s <a href="https://docs.travis-ci.com/user/workers/container-based-infrastructure/#Routing-your-build-to-container-based-infrastructure">container-based
@@ -502,10 +476,8 @@ explicitly tells Travis to run your build on Travis’s <a href="https://docs.tr
 speed up your build. If you have any trouble with your build, or if your build
 does need <code class="highlighter-rouge">sudo</code> access, modify the line to <code class="highlighter-rouge">sudo: required</code>.</p>
 
-<div class="language-yaml highlighter-rouge">
-<pre class="highlight"><code><span class="s">sudo</span><span class="pi">:</span> <span class="s">false</span>
-</code></pre>
-</div>
+<div class="language-yaml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="na">sudo</span><span class="pi">:</span> <span class="no">false</span>
+</code></pre></div></div>
 
 <h3 id="troubleshooting">Troubleshooting</h3>