RubyGems - jekyll - Versions diffs - 2.2.0 → 2.3.0 - Mend

jekyll 2.2.0 → 2.3.0

Potentially problematic release.

This version of jekyll might be problematic. Click here for more details.

Files changed (306) hide show

checksums.yaml +4 -4
data/README.markdown +1 -1
data/lib/jekyll.rb +0 -1
data/lib/jekyll/collection.rb +18 -3
data/lib/jekyll/command.rb +0 -25
data/lib/jekyll/commands/build.rb +7 -2
data/lib/jekyll/commands/help.rb +33 -0
data/lib/jekyll/configuration.rb +36 -28
data/lib/jekyll/converters/markdown/kramdown_parser.rb +1 -1
data/lib/jekyll/convertible.rb +43 -20
data/lib/jekyll/deprecator.rb +15 -8
data/lib/jekyll/document.rb +21 -4
data/lib/jekyll/filters.rb +27 -1
data/lib/jekyll/frontmatter_defaults.rb +46 -12
data/lib/jekyll/plugin.rb +10 -1
data/lib/jekyll/post.rb +6 -13
data/lib/jekyll/related_posts.rb +2 -2
data/lib/jekyll/renderer.rb +7 -2
data/lib/jekyll/site.rb +5 -7
data/lib/jekyll/static_file.rb +24 -4
data/lib/jekyll/tags/include.rb +3 -1
data/lib/jekyll/tags/post_url.rb +2 -2
data/lib/jekyll/utils.rb +88 -69
data/lib/jekyll/version.rb +1 -1
data/lib/site_template/_config.yml +6 -4
data/lib/site_template/_includes/footer.html +43 -49
data/lib/site_template/_includes/head.html +3 -4
data/lib/site_template/_includes/header.html +9 -10
data/lib/site_template/_layouts/default.html +6 -5
data/lib/site_template/_layouts/page.html +3 -3
data/lib/site_template/_layouts/post.html +4 -4
data/lib/site_template/_posts/0000-00-00-welcome-to-jekyll.markdown.erb +6 -5
data/lib/site_template/_sass/_base.scss +203 -0
data/lib/site_template/_sass/_layout.scss +236 -0
data/lib/site_template/_sass/_syntax-highlighting.scss +67 -0
data/lib/site_template/css/main.scss +49 -0
data/lib/site_template/feed.xml +1 -1
data/lib/site_template/index.html +7 -4
metadata +24 -431
data/.gitignore +0 -15
data/.travis.yml +0 -27
data/CONTRIBUTING.markdown +0 -91
data/Gemfile +0 -2
data/History.markdown +0 -1310
data/Rakefile +0 -268
data/cucumber.yml +0 -3
data/docs/jp/CONTRIBUTING.jp.markdown +0 -93
data/docs/jp/README.jp.markdown +0 -68
data/features/collections.feature +0 -145
data/features/create_sites.feature +0 -158
data/features/data.feature +0 -105
data/features/drafts.feature +0 -46
data/features/embed_filters.feature +0 -107
data/features/frontmatter_defaults.feature +0 -136
data/features/include_tag.feature +0 -68
data/features/markdown.feature +0 -67
data/features/pagination.feature +0 -82
data/features/permalinks.feature +0 -85
data/features/post_data.feature +0 -261
data/features/post_excerpts.feature +0 -50
data/features/rendering.feature +0 -34
data/features/site_configuration.feature +0 -283
data/features/site_data.feature +0 -107
data/features/step_definitions/jekyll_steps.rb +0 -201
data/features/support/env.rb +0 -65
data/jekyll.gemspec +0 -66
data/lib/site_template/css/main.css +0 -410
data/script/bootstrap +0 -4
data/script/branding +0 -11
data/script/cibuild +0 -7
data/script/console +0 -38
data/script/proof +0 -22
data/script/rebund +0 -140
data/script/test +0 -17
data/site/.gitignore +0 -4
data/site/CNAME +0 -1
data/site/README +0 -1
data/site/_config.yml +0 -9
data/site/_data/docs.yml +0 -46
data/site/_includes/analytics.html +0 -30
data/site/_includes/anchor_links.html +0 -32
data/site/_includes/css/font-awesome.css +0 -44
data/site/_includes/css/gridism.css +0 -110
data/site/_includes/css/normalize.css +0 -1
data/site/_includes/css/pygments.css +0 -72
data/site/_includes/css/style.css +0 -1045
data/site/_includes/docs_contents.html +0 -8
data/site/_includes/docs_contents_mobile.html +0 -10
data/site/_includes/docs_option.html +0 -11
data/site/_includes/docs_ul.html +0 -20
data/site/_includes/footer.html +0 -15
data/site/_includes/header.html +0 -18
data/site/_includes/news_contents.html +0 -33
data/site/_includes/news_contents_mobile.html +0 -11
data/site/_includes/news_item.html +0 -24
data/site/_includes/primary-nav-items.html +0 -17
data/site/_includes/section_nav.html +0 -22
data/site/_includes/top.html +0 -17
data/site/_layouts/default.html +0 -13
data/site/_layouts/docs.html +0 -23
data/site/_layouts/news.html +0 -19
data/site/_layouts/news_item.html +0 -27
data/site/_posts/2013-05-06-jekyll-1-0-0-released.markdown +0 -23
data/site/_posts/2013-05-08-jekyll-1-0-1-released.markdown +0 -27
data/site/_posts/2013-05-12-jekyll-1-0-2-released.markdown +0 -28
data/site/_posts/2013-06-07-jekyll-1-0-3-released.markdown +0 -25
data/site/_posts/2013-07-14-jekyll-1-1-0-released.markdown +0 -27
data/site/_posts/2013-07-24-jekyll-1-1-1-released.markdown +0 -31
data/site/_posts/2013-07-25-jekyll-1-0-4-released.markdown +0 -20
data/site/_posts/2013-07-25-jekyll-1-1-2-released.markdown +0 -20
data/site/_posts/2013-09-06-jekyll-1-2-0-released.markdown +0 -23
data/site/_posts/2013-09-14-jekyll-1-2-1-released.markdown +0 -19
data/site/_posts/2013-10-28-jekyll-1-3-0-rc1-released.markdown +0 -19
data/site/_posts/2013-11-04-jekyll-1-3-0-released.markdown +0 -43
data/site/_posts/2013-11-26-jekyll-1-3-1-released.markdown +0 -21
data/site/_posts/2013-12-07-jekyll-1-4-0-released.markdown +0 -30
data/site/_posts/2013-12-09-jekyll-1-4-1-released.markdown +0 -20
data/site/_posts/2013-12-16-jekyll-1-4-2-released.markdown +0 -18
data/site/_posts/2014-01-13-jekyll-1-4-3-released.markdown +0 -26
data/site/_posts/2014-03-24-jekyll-1-5-0-released.markdown +0 -19
data/site/_posts/2014-03-27-jekyll-1-5-1-released.markdown +0 -26
data/site/_posts/2014-05-06-jekyll-turns-2-0-0.markdown +0 -31
data/site/_posts/2014-05-08-jekyll-2-0-3-released.markdown +0 -18
data/site/_posts/2014-06-04-jekyll-stickers-1-dollar-stickermule.markdown +0 -19
data/site/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown +0 -31
data/site/_posts/2014-07-01-jekyll-2-1-1-released.markdown +0 -30
data/site/_posts/2014-07-29-jekyll-2-2-0-released.markdown +0 -19
data/site/css/screen.css +0 -31
data/site/docs/assets.md +0 -66
data/site/docs/collections.md +0 -259
data/site/docs/configuration.md +0 -536
data/site/docs/continuous-integration.md +0 -177
data/site/docs/contributing.md +0 -133
data/site/docs/datafiles.md +0 -108
data/site/docs/deployment-methods.md +0 -127
data/site/docs/drafts.md +0 -21
data/site/docs/extras.md +0 -18
data/site/docs/frontmatter.md +0 -191
data/site/docs/github-pages.md +0 -91
data/site/docs/history.md +0 -1514
data/site/docs/index.md +0 -58
data/site/docs/installation.md +0 -106
data/site/docs/migrations.md +0 -11
data/site/docs/pages.md +0 -86
data/site/docs/pagination.md +0 -212
data/site/docs/permalinks.md +0 -188
data/site/docs/plugins.md +0 -561
data/site/docs/posts.md +0 -211
data/site/docs/quickstart.md +0 -26
data/site/docs/resources.md +0 -43
data/site/docs/sites.md +0 -29
data/site/docs/structure.md +0 -190
data/site/docs/templates.md +0 -376
data/site/docs/troubleshooting.md +0 -147
data/site/docs/upgrading.md +0 -146
data/site/docs/usage.md +0 -74
data/site/docs/variables.md +0 -382
data/site/docs/windows.md +0 -44
data/site/favicon.ico +0 -0
data/site/feed.xml +0 -48
data/site/fonts/FontAwesome.otf +0 -0
data/site/fonts/fontawesome-webfont.eot +0 -0
data/site/fonts/fontawesome-webfont.svg +0 -504
data/site/fonts/fontawesome-webfont.ttf +0 -0
data/site/fonts/fontawesome-webfont.woff +0 -0
data/site/freenode.txt +0 -1
data/site/img/article-footer.png +0 -0
data/site/img/footer-arrow.png +0 -0
data/site/img/footer-logo.png +0 -0
data/site/img/jekyll-sticker.jpg +0 -0
data/site/img/logo-2x.png +0 -0
data/site/img/logo-rss.png +0 -0
data/site/img/octojekyll.png +0 -0
data/site/index.html +0 -90
data/site/js/html5shiv.min.js +0 -4
data/site/js/respond.min.js +0 -5
data/site/news/index.html +0 -10
data/site/news/releases/index.html +0 -10
data/test/fixtures/broken_front_matter1.erb +0 -5
data/test/fixtures/broken_front_matter2.erb +0 -4
data/test/fixtures/broken_front_matter3.erb +0 -7
data/test/fixtures/exploit_front_matter.erb +0 -4
data/test/fixtures/front_matter.erb +0 -4
data/test/helper.rb +0 -80
data/test/source/+/%# +.md +0 -6
data/test/source/+/foo.md +0 -7
data/test/source/.htaccess +0 -8
data/test/source/_config.dev.toml +0 -2
data/test/source/_data/categories/dairy.yaml +0 -6
data/test/source/_data/languages.yml +0 -2
data/test/source/_data/members.json +0 -12
data/test/source/_data/members.yaml +0 -7
data/test/source/_data/products.yml +0 -4
data/test/source/_drafts/draft-properties.text +0 -11
data/test/source/_includes/include.html +0 -1
data/test/source/_includes/params.html +0 -7
data/test/source/_includes/sig.markdown +0 -3
data/test/source/_layouts/default.html +0 -27
data/test/source/_layouts/post/simple.html +0 -1
data/test/source/_layouts/simple.html +0 -1
data/test/source/_methods/_do_not_read_me.md +0 -5
data/test/source/_methods/configuration.md +0 -8
data/test/source/_methods/sanitized_path.md +0 -5
data/test/source/_methods/site/_dont_include_me_either.md +0 -5
data/test/source/_methods/site/generate.md +0 -6
data/test/source/_methods/site/initialize.md +0 -4
data/test/source/_methods/um_hi.md +0 -6
data/test/source/_plugins/dummy.rb +0 -8
data/test/source/_posts/2008-02-02-not-published.textile +0 -8
data/test/source/_posts/2008-02-02-published.textile +0 -8
data/test/source/_posts/2008-10-18-foo-bar.textile +0 -8
data/test/source/_posts/2008-11-21-complex.textile +0 -8
data/test/source/_posts/2008-12-03-permalinked-post.textile +0 -9
data/test/source/_posts/2008-12-13-include.markdown +0 -8
data/test/source/_posts/2009-01-27-array-categories.textile +0 -10
data/test/source/_posts/2009-01-27-categories.textile +0 -7
data/test/source/_posts/2009-01-27-category.textile +0 -7
data/test/source/_posts/2009-01-27-empty-categories.textile +0 -7
data/test/source/_posts/2009-01-27-empty-category.textile +0 -7
data/test/source/_posts/2009-01-27-no-category.textile +0 -6
data/test/source/_posts/2009-03-12-hash-#1.markdown +0 -6
data/test/source/_posts/2009-05-18-empty-tag.textile +0 -6
data/test/source/_posts/2009-05-18-empty-tags.textile +0 -6
data/test/source/_posts/2009-05-18-tag.textile +0 -6
data/test/source/_posts/2009-05-18-tags.textile +0 -9
data/test/source/_posts/2009-06-22-empty-yaml.textile +0 -3
data/test/source/_posts/2009-06-22-no-yaml.textile +0 -1
data/test/source/_posts/2010-01-08-triple-dash.markdown +0 -5
data/test/source/_posts/2010-01-09-date-override.textile +0 -7
data/test/source/_posts/2010-01-09-time-override.textile +0 -7
data/test/source/_posts/2010-01-09-timezone-override.textile +0 -7
data/test/source/_posts/2010-01-16-override-data.textile +0 -4
data/test/source/_posts/2011-04-12-md-extension.md +0 -7
data/test/source/_posts/2011-04-12-text-extension.text +0 -0
data/test/source/_posts/2013-01-02-post-excerpt.markdown +0 -14
data/test/source/_posts/2013-01-12-nil-layout.textile +0 -6
data/test/source/_posts/2013-01-12-no-layout.textile +0 -5
data/test/source/_posts/2013-03-19-not-a-post.markdown/.gitkeep +0 -0
data/test/source/_posts/2013-04-11-custom-excerpt.markdown +0 -10
data/test/source/_posts/2013-05-10-number-category.textile +0 -7
data/test/source/_posts/2013-07-22-post-excerpt-with-layout.markdown +0 -23
data/test/source/_posts/2013-08-01-mkdn-extension.mkdn +0 -0
data/test/source/_posts/2013-12-17-include-variable-filters.markdown +0 -21
data/test/source/_posts/2013-12-20-properties.text +0 -11
data/test/source/_posts/2014-01-06-permalink-traversal.md +0 -5
data/test/source/_posts/2014-03-03-yaml-with-dots.md +0 -5
data/test/source/_posts/2014-03-22-escape-+ %20[].markdown +0 -6
data/test/source/_posts/es/2008-11-21-nested.textile +0 -8
data/test/source/_sass/_grid.scss +0 -1
data/test/source/_slides/example-slide-1.html +0 -4
data/test/source/_slides/example-slide-2.html +0 -7
data/test/source/_slides/example-slide-3.html +0 -5
data/test/source/_with.dots/all.dots/2.4.0.md +0 -5
data/test/source/_with.dots/file.with.dots.md +0 -0
data/test/source/about.html +0 -6
data/test/source/category/_posts/2008-9-23-categories.textile +0 -6
data/test/source/contacts.html +0 -5
data/test/source/contacts/bar.html +0 -5
data/test/source/contacts/index.html +0 -5
data/test/source/css/main.scss +0 -4
data/test/source/css/screen.css +0 -76
data/test/source/deal.with.dots.html +0 -7
data/test/source/environment.html +0 -5
data/test/source/exploit.md +0 -5
data/test/source/foo/_posts/bar/2008-12-12-topical-post.textile +0 -8
data/test/source/index.html +0 -22
data/test/source/js/coffeescript.coffee +0 -10
data/test/source/pgp.key +0 -2
data/test/source/products.yml +0 -4
data/test/source/properties.html +0 -8
data/test/source/sitemap.xml +0 -32
data/test/source/static_files.html +0 -4
data/test/source/symlink-test/symlinked-file +0 -22
data/test/source/unpublished.html +0 -7
data/test/source/win/_posts/2009-05-24-yaml-linebreak.markdown +0 -7
data/test/source/z_category/_posts/2008-9-23-categories.textile +0 -6
data/test/suite.rb +0 -11
data/test/test_cleaner.rb +0 -77
data/test/test_coffeescript.rb +0 -49
data/test/test_collections.rb +0 -224
data/test/test_command.rb +0 -53
data/test/test_configuration.rb +0 -201
data/test/test_convertible.rb +0 -49
data/test/test_document.rb +0 -193
data/test/test_draft.rb +0 -56
data/test/test_entry_filter.rb +0 -124
data/test/test_excerpt.rb +0 -131
data/test/test_filters.rb +0 -207
data/test/test_generated_site.rb +0 -97
data/test/test_kramdown.rb +0 -62
data/test/test_layout_reader.rb +0 -34
data/test/test_liquid_extensions.rb +0 -31
data/test/test_log_adapter.rb +0 -59
data/test/test_new_command.rb +0 -104
data/test/test_page.rb +0 -254
data/test/test_path_sanitization.rb +0 -18
data/test/test_post.rb +0 -741
data/test/test_rdiscount.rb +0 -22
data/test/test_redcarpet.rb +0 -77
data/test/test_redcloth.rb +0 -86
data/test/test_related_posts.rb +0 -47
data/test/test_sass.rb +0 -26
data/test/test_site.rb +0 -452
data/test/test_tags.rb +0 -509
data/test/test_url.rb +0 -28
data/test/test_utils.rb +0 -67

data/site/_posts/2014-07-01-jekyll-2-1-1-released.markdown DELETED

@@ -1,30 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 2.1.1 Released'
-date: 2014-07-01 20:16:43 -0400
-author: parkr
-version: 2.1.1
-categories: [release]
----
-This is a minor release for Jekyll 2.1.0. It fixes a couple bugs and
-introduces fixes for a couple security-related issues.
-It covers two security vulnerabilities:
-1. One in the reading of data
-2. One in the `layouts` setting
-They were identified in Jekyll 1.5.1 and has been confirmed as patched
-in this version and the version used by GitHub Pages. If you are in the
-business of building Jekyll sites, please ensure you upgrade to 2.1.1 as
-soon as possible.
-For more, check out [`jekyll/jekyll#2563`](https://github.com/jekyll/jekyll/pull/2563).
-Additionally, the dependency on Maruku has been loosened and a bug was
-fixed with document URLs.
-As always, check out the [full changelog](/docs/history/) for more info!
-Happy Jekylling!

data/site/_posts/2014-07-29-jekyll-2-2-0-released.markdown DELETED

@@ -1,19 +0,0 @@
----
-layout: news_item
-title: 'Jekyll 2.2.0 Released'
-date: 2014-07-29 18:59:13 -0400
-author: parkr
-version: 2.2.0
-categories: [release]
----
-Jekyll 2.2.0 contains a few key updates:
-1. A warning will now fire if you specify a layout in any of your pages or
-    posts that doesn't exist.
-2. Certain Pygments options are now whitelisted in safe mode
-3. Categories in a post's path are now respected (i.e. folders in `_posts`
-   will now work properly).
-As always, a full list of the updates are on the
-[history page](/docs/history#v2-2-0). Happy Jekylling!

data/site/css/screen.css DELETED

@@ -1,31 +0,0 @@
----
----
-{% capture screen %}
-/*                *\
- * $normalize.css *
-\*                */
-{% include css/normalize.css %}
-/*                *\
- * $gridism.css   *
-\*                */
-{% include css/gridism.css %}
-/*                *\
- * $style.css     *
-\*                */
-{% include css/style.css %}
-/*                *\
- * $pygments.css  *
-\*                */
-{% include css/pygments.css %}
-/*                *\
- * $font-awesome.css  *
-\*                */
-{% include css/font-awesome.css %}
-{% endcapture %}
-{% if site.GH_ENV %}
-  {{ screen | strip_newlines | remove: '  ' }}
-{% else %}
-  {{ screen }}
-{% endif %}

data/site/docs/assets.md DELETED

@@ -1,66 +0,0 @@
----
-layout: docs
-title: Assets
-prev_section: datafiles
-next_section: migrations
-permalink: /docs/assets/
----
-Jekyll provides built-in support for Sass and CoffeeScript. In order to use
-them, create a file with the proper extension name (one of `.sass`, `.scss`,
-or `.coffee`) and start the file with two lines of triple dashes, like this:
-{% highlight sass %}
----
----
-// start content
-.my-definition
-  font-size: 1.2em
-{% endhighlight %}
-Jekyll treats these files the same as a regular page, in that the output file
-will be placed in the same directory that it came from. For instance, if you
-have a file named `css/styles.scss` in your site's source folder, Jekyll
-will process it and put it in your site's destination folder under
-`css/styles.css`.
-## Sass/SCSS
-Jekyll allows you to customize your Sass conversion in certain ways.
-If you are using Sass `@import` statements, you'll need to ensure that your
-`sass_dir` is set to the base directory that contains your Sass files. You
-can do that thusly:
-{% highlight yaml %}
-sass:
-    sass_dir: _sass
-{% endhighlight %}
-The Sass converter will default the `sass_dir` configuration option to
-`_sass`.
-<div class="note info">
-  <h5>The <code>sass_dir</code> is only used by Sass</h5>
-  <p>
-    Note that the `sass_dir` becomes the load path for Sass imports,
-    nothing more. This means that Jekyll does not know about these files
-    directly, so any files here should not contain the YAML front matter as
-    described above nor will they be transformed as described above. This
-    folder should only contain imports.
-  </p>
-</div>
-You may also specify the output style with the `style` option in your
-`_config.yml` file:
-{% highlight yaml %}
-sass:
-    style: :compressed
-{% endhighlight %}
-These are passed to Sass, so any output style options Sass supports are valid
-here, too.

data/site/docs/collections.md DELETED

@@ -1,259 +0,0 @@
----
-layout: docs
-title: Collections
-prev_section: variables
-next_section: datafiles
-permalink: /docs/collections/
----
-<div class="note warning">
-  <h5>Collections support is unstable and may change</h5>
-  <p>
-    This is an experimental feature and that the API may likely change until the feature stabilizes.
-  </p>
-</div>
-Not everything is a post or a page. Maybe you want to document the various methods in your open source project, members of a team, or talks at a conference. Collections allow you to define a new type of document that behave like Pages or Posts do normally, but also have their own unique properties and namespace.
-## Using Collections
-### Step 1: Tell Jekyll to read in your collection
-Add the following to your site's `_config.yml` file, replacing `my_collection` with the name of your collection:
-{% highlight yaml %}
-collections:
-- my_collection
-{% endhighlight %}
-You can optionally specify metadata for your collection in the configuration:
-{% highlight yaml %}
-collections:
-  my_collection:
-    foo: bar
-{% endhighlight %}
-### Step 2: Add your content
-Create a corresponding folder (e.g. `<source>/_my_collection`) and add documents.
-YAML front-matter is read in as data if it exists, if not, then everything is just stuck in the Document's `content` attribute.
-Note: the folder must be named identical to the collection you defined in you config.yml file, with the addition of the preceding `_` character.
-### Step 3: Optionally render your collection's documents into independent files
-If you'd like Jekyll to create a public-facing, rendered version of each document in your collection, set the `output` key to `true` in your collection metadata in your `_config.yml`:
-{% highlight yaml %}
-collections:
-  my_collection:
-    output: true
-{% endhighlight %}
-This will produce a file for each document in the collection.
-For example, if you have `_my_collection/some_subdir/some_doc.md`,
-it will be rendered using Liquid and the Markdown converter of your
-choice and written out to `<dest>/my_collection/some_subdir/some_doc.html`.
-As for posts with [Permalinks](../permalinks/), document URL can be customized by setting a `permalink` metadata to the collection:
-{% highlight yaml %}
-collections:
-  my_collection:
-    output: true
-    permalink: /awesome/:path/
-{% endhighlight %}
-For example, if you have `_my_collection/some_subdir/some_doc.md`, it will be written out to `<dest>/awesome/some_subdir/some_doc/index.html`.
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Variable</th>
-      <th>Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p><code>collection</code></p>
-      </td>
-      <td>
-        <p>Label of the containing collection</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>path</code></p>
-      </td>
-      <td>
-        <p>Path to the document relative to the collection's directory</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>output_ext</code></p>
-      </td>
-      <td>
-        <p>Extension of the output file</p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-## Liquid Attributes
-### Collections
-Each collection is accessible via the `site` Liquid variable. For example, if you want to access the `albums` collection found in `_albums`, you'd use `site.albums`. Each collection is itself an array of documents (e.g. `site.albums` is an array of documents, much like `site.pages` and `site.posts`). See below for how to access attributes of those documents.
-The collections are also available under `site.collections`, with the metadata you specified in your `_config.yml` (if present) and the following information:
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Variable</th>
-      <th>Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p><code>label</code></p>
-      </td>
-      <td>
-        <p>
-          The name of your collection, e.g. <code>my_collection</code>.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>docs</code></p>
-      </td>
-      <td>
-        <p>
-          An array of <a href="#documents">documents</a>.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>relative_directory</code></p>
-      </td>
-      <td>
-        <p>
-          The path to the collections's source directory, relative to the site source.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>directory</code></p>
-      </td>
-      <td>
-        <p>
-          The full path to the collections's source directory.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>output</code></p>
-      </td>
-      <td>
-        <p>
-          Whether the collection's documents will be output as individual files.
-        </p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-### Documents
-In addition to any YAML front-matter provided in the document's corresponding file, each document has the following attributes:
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Variable</th>
-      <th>Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p><code>content</code></p>
-      </td>
-      <td>
-        <p>
-          The (unrendered) content of the document. If no YAML front-matter is provided,
-          this is the entirety of the file contents. If YAML front-matter
-          is used, then this is all the contents of the file after the terminating
-          `---` of the front-matter.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>output</code></p>
-      </td>
-      <td>
-        <p>
-          The rendered output of the document, based on the <code>content</code>.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>path</code></p>
-      </td>
-      <td>
-        <p>
-          The full path to the document's source file.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>relative_path</code></p>
-      </td>
-      <td>
-        <p>
-          The path to the document's source file relative to the site source.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>url</code></p>
-      </td>
-      <td>
-        <p>
-          The URL of the rendered collection. The file is only written to the
-          destination when the name of the collection to which it belongs is
-          included in the <code>render</code> key in the site's configuration file.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>collection</code></p>
-      </td>
-      <td>
-        <p>
-          The name of the document's collection.
-        </p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>

data/site/docs/configuration.md DELETED

@@ -1,536 +0,0 @@
----
-layout: docs
-title: Configuration
-prev_section: structure
-next_section: frontmatter
-permalink: /docs/configuration/
----
-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.
-## Configuration Settings
-### Global Configuration
-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.
-<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>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="http://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="http://en.wikipedia.org/wiki/List_of_tz_database_time_zones">
-            here</a>. The default is the local time zone, as set by your operating system.
-        </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 frontmatter">YAML frontmatter</a>
-            variables.
-        </p>
-      </td>
-      <td class='align-center'>
-        <p>see <a href="#frontmatter-defaults" title="details">below</a></p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-### Build Command Options
-<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, --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="flag">--drafts</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Future</strong></p>
-        <p class="description">Publish posts 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>LSI</strong></p>
-        <p class="description">Produce an index for related posts.</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>
-  </tbody>
-</table>
-</div>
-### Serve Command Options
-In addition to the options below, the `serve` sub-command can accept any of the options
-for the `build` sub-command, which are then applied to the site build which occurs right
-before your site is served.
-<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>
-  </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>
-## Frontmatter defaults
-Using [YAML front-matter](../frontmatter/) 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.
-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.
-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 `defaults` key in the `_config.yml` file in your projects root directory.
-The `defaults` 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.
-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 `_config.yml` file:
-{% highlight yaml %}
-defaults:
-  -
-    scope:
-      path: "" # an empty string here means all files in the project
-    values:
-      layout: "default"
-{% endhighlight %}
-Here, we are scoping the `values` to any file that exists in the scopes path. Since the path is set as an empty string, it will apply to **all files** 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 `type` value under the `scope` key.
-{% highlight yaml %}
-defaults:
-  -
-    scope:
-      path: "" # an empty string here means all files in the project
-      type: "post"
-    values:
-      layout: "default"
-{% endhighlight %}
-Now, this will only set the layout for files where the type is `post`.
-The different types that are available to you are `page`, `post`, `draft` or any collection in your site. While `type` is optional, you must specify a value for `path` when creating a `scope/values` pair.
-As mentioned earlier, you can set multiple scope/values pairs for `defaults`.
-{% highlight yaml %}
-defaults:
-  -
-    scope:
-      path: ""
-      type: "post"
-    values:
-      layout: "my-site"
-  -
-    scope:
-      path: "projects"
-      type: "page"
-    values:
-      layout: "project" # overrides previous default layout
-      author: "Mr. Hyde"
-      category: "project"
-{% endhighlight %}
-With these defaults, all posts would use the `my-site` layout. Any html files that exist in the `projects/` folder will use the `project` layout, if it exists. Those files will also have the `page.author` [liquid variable](../variables/) set to `Mr. Hyde` as well as have the category for the page set to `project`.
-{% highlight yaml %}
-collections:
-  - my_collection:
-    output: true
-defaults:
-  -
-    scope:
-      path: ""
-      type: "my_collection" # a collection in your site
-    values:
-      layout: "default"
-{% endhighlight %}
-In this example the `layout` is set to `default` inside the [collection](../collections) with the name `my_collection`.
-### Precedence
-Jekyll will apply all of the configuration settings you specify in the `defaults` section of your `_config.yml` file. However, you can choose to override settings from other scope/values pair by specifying a more specific path for the scope.
-You can see that in the last example above. First, we set the default layout to `my-site`. Then, using a more specific path, we set the default layout for files in the `projects/` path to `project`. This can be done with any value that you would set in the page or post front-matter.
-Finally, if you set defaults in the site configuration by adding a `defaults` section to your `_config.yml` 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:
-{% highlight yaml %}
-# In _config.yml
-...
-defaults:
-  -
-    scope:
-      path: "projects"
-      type: "page"
-    values:
-      layout: "project"
-      author: "Mr. Hyde"
-      category: "project"
-...
-{% endhighlight %}
-{% highlight yaml %}
-# In projects/foo_project.md
----
-author: "John Smith"
-layout: "foobar"
----
-The post text goes here...
-{% endhighlight %}
-The `projects/foo_project.md` would have the `layout` set to `foobar` instead of `project` and the `author` set to `John Smith` instead of `Mr. Hyde` when the site is built.
-## Default Configuration
-Jekyll runs with the following configuration options by default. Unless
-alternative settings for these options are explicitly specified in the
-configuration file or on the command-line, Jekyll will run using these options.
-<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>
-{% highlight yaml %}
-source:      .
-destination: ./_site
-plugins:     ./_plugins
-layouts:     ./_layouts
-include:     ['.htaccess']
-exclude:     []
-keep_files:  ['.git','.svn']
-gems:        []
-timezone:    nil
-encoding:    nil
-future:      true
-show_drafts: false
-limit_posts: 0
-highlighter: pygments
-relative_permalinks: true
-permalink:     date
-paginate_path: 'page:num'
-paginate:      nil
-markdown:      kramdown
-markdown_ext:  markdown,mkdown,mkdn,mkd,md
-textile_ext:   textile
-excerpt_separator: "\n\n"
-safe:        false
-watch:       false    # deprecated
-server:      false    # deprecated
-host:        0.0.0.0
-port:        4000
-baseurl:     ""
-lsi:         false
-maruku:
-  use_tex:    false
-  use_divs:   false
-  png_engine: blahtex
-  png_dir:    images/latex
-  png_url:    /images/latex
-  fenced_code_blocks: true
-rdiscount:
-  extensions: []
-redcarpet:
-  extensions: []
-kramdown:
-  auto_ids: true
-  footnote_nr: 1
-  entity_output: as_char
-  toc_levels: 1..6
-  smart_quotes: lsquo,rsquo,ldquo,rdquo
-  use_coderay: false
-  coderay:
-    coderay_wrap: div
-    coderay_line_numbers: inline
-    coderay_line_numbers_start: 1
-    coderay_tab_width: 4
-    coderay_bold_every: 10
-    coderay_css: style
-redcloth:
-  hard_breaks: true
-{% endhighlight %}
-## Markdown Options
-The various Markdown renderers supported by Jekyll sometimes have extra options available.
-### Redcarpet
-Redcarpet can be configured by providing an `extensions` sub-setting, whose value should be an array of strings. Each string should be the name of one of the `Redcarpet::Markdown` class's extensions; if present in the array, it will set the corresponding extension to `true`.
-Jekyll handles two special Redcarpet extensions:
-- `no_fenced_code_blocks` --- By default, Jekyll sets the `fenced_code_blocks` extension (for delimiting code blocks with triple tildes or triple backticks) to `true`, probably because GitHub's eager adoption of them is starting to make them inescapable. Redcarpet's normal `fenced_code_blocks` extension is inert when used with Jekyll; instead, you can use this inverted version of the extension for disabling fenced code.
-    Note that you can also specify a language for highlighting after the first delimiter:
-        ```ruby
-        # ...ruby code
-        ```
-    With both fenced code blocks and highlighter enabled, this will statically highlight the code; without any syntax highlighter, it will add a `class="LANGUAGE"` attribute to the `<code>` element, which can be used as a hint by various JavaScript code highlighting libraries.
-- `smart` --- This pseudo-extension turns on SmartyPants, which converts straight quotes to curly quotes and runs of hyphens to em (`---`) and en (`--`) dashes.
-All other extensions retain their usual names from Redcarpet, and no renderer options aside from `smart` can be specified in Jekyll. [A list of available extensions can be found in the Redcarpet README file.][redcarpet_extensions] Make sure you're looking at the README for the right version of Redcarpet: Jekyll currently uses v2.2.x, and extensions like `footnotes` and `highlight` weren't added until after version 3.0.0. The most commonly used extensions are:
-- `tables`
-- `no_intra_emphasis`
-- `autolink`
-[redcarpet_extensions]: https://github.com/vmg/redcarpet/blob/v2.2.2/README.markdown#and-its-like-really-simple-to-use
-### Kramdown
-In addition to the defaults mentioned above, you can also turn on recognition of Github Flavored Markdown by passing an `input` option with a value of "GFM".
-For example, in your `_config.yml`:
-    kramdown:
-      input: GFM
-### Custom Markdown Processors
-If you're interested in creating a custom markdown processor, you're in luck! Create a new class in the `Jekyll::Converters::Markdown` namespace:
-{% highlight ruby %}
-class Jekyll::Converters::Markdown::MyCustomProcessor
-  def initialize(config)
-    require 'funky_markdown'
-    @config = config
-  rescue LoadError
-    STDERR.puts 'You are missing a library required for Markdown. Please run:'
-    STDERR.puts '  $ [sudo] gem install funky_markdown'
-    raise FatalException.new("Missing dependency: funky_markdown")
-  end
-  def convert(content)
-    ::FunkyMarkdown.new(content).convert
-  end
-end
-{% endhighlight %}
-Once you've created your class and have it properly setup either as a plugin in the `_plugins` folder or as a gem, specify it in your `_config.yml`:
-{% highlight yaml %}
-markdown: MyCustomProcessor
-{% endhighlight %}