Release 💎 3.1.5

Sort the results of the require_all glob.

.codeclimate.yml

@@ -1,36 +1,29 @@
 engines:
-  fixme:
-    enabled: false
-  rubocop:
-    enabled: true
-    channel: rubocop-0-54
-
+  rubocop: { enabled: true  }
+  fixme:   { enabled: false }
 exclude_paths:
-  - .codeclimate.yml
-  - .gitignore
-  - .rspec
-  - .rubocop.yml
-  - .travis.yml
+- .rubocop.yml
+- .codeclimate.yml
+- .travis.yml
+- .gitignore
+- .rspec
 
-  - Gemfile.lock
-  - CHANGELOG.{md,markdown,txt,textile}
-  - CONTRIBUTING.{md,markdown,txt,textile}
-  - readme.{md,markdown,txt,textile}
-  - README.{md,markdown,txt,textile}
-  - Readme.{md,markdown,txt,textile}
-  - ReadMe.{md,markdown,txt,textile}
-  - COPYING
-  - LICENSE
-
-  - features/**/*
-  - script/**/*
-  - docs/**/*
-  - spec/**/*
-  - test/**/*
-  - vendor/**/*
-
-  - lib/jekyll/commands/serve/livereload_assets/livereload.js
+- Gemfile.lock
+- CHANGELOG.{md,markdown,txt,textile}
+- CONTRIBUTING.{md,markdown,txt,textile}
+- readme.{md,markdown,txt,textile}
+- README.{md,markdown,txt,textile}
+- Readme.{md,markdown,txt,textile}
+- ReadMe.{md,markdown,txt,textile}
+- COPYING
+- LICENSE
 
+- site/**/*
+- test/**/*
+- vendor/**/*
+- features/**/*
+- script/**/*
+- spec/**/*
 ratings:
   paths:
-    - lib/**/*.rb
+  - lib/**/*.rb

.editorconfig

@@ -1,14 +0,0 @@
-# editorconfig.org
-
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-indent_size = 2
-indent_style = space
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.md]
-trim_trailing_whitespace = false

.github/CODEOWNERS

@@ -1,86 +0,0 @@
-# The Jekyll project has 6 affinity teams, shown here: https://teams.jekyllrb.com/
-# They are as follows:
-#
-#   1. @jekyll/build
-#   2. @jekyll/documentation
-#   3. @jekyll/ecosystem
-#   4. @jekyll/performance
-#   5. @jekyll/stability
-#   6. @jekyll/windows
-#
-# Each of these teams has a mission. Wherever possible, GitHub should
-# automatically require review from these teams on the pieces of the
-# repository they maintain.
-
-# @jekyll/documentation
-/docs/                               @jekyll/documentation
-
-# @jekyll/build
-/exe/                                @jekyll/build
-/lib/jekyll.rb                       @jekyll/build
-/lib/jekyll/cleaner.rb               @jekyll/build
-/lib/jekyll/collection.rb            @jekyll/build
-/lib/jekyll/command.rb               @jekyll/build
-/lib/jekyll/commands/                @jekyll/build
-/lib/jekyll/converter.rb             @jekyll/build
-/lib/jekyll/converters/              @jekyll/build
-/lib/jekyll/convertible.rb           @jekyll/build
-/lib/jekyll/document.rb              @jekyll/build
-/lib/jekyll/drops/                   @jekyll/build
-/lib/jekyll/entry_filter.rb          @jekyll/build
-/lib/jekyll/errors.rb                @jekyll/build
-/lib/jekyll/excerpt.rb               @jekyll/build
-/lib/jekyll/filters/                 @jekyll/build
-/lib/jekyll/filters.rb               @jekyll/build
-/lib/jekyll/layout.rb                @jekyll/build
-/lib/jekyll/liquid_extensions.rb     @jekyll/build
-/lib/jekyll/liquid_renderer/         @jekyll/build
-/lib/jekyll/liquid_renderer.rb       @jekyll/build
-/lib/jekyll/log_adapter.rb           @jekyll/build
-/lib/jekyll/mime.types               @jekyll/build
-/lib/jekyll/page.rb                  @jekyll/build
-/lib/jekyll/publisher.rb             @jekyll/build
-/lib/jekyll/reader.rb                @jekyll/build
-/lib/jekyll/readers/                 @jekyll/build
-/lib/jekyll/regenerator.rb           @jekyll/build
-/lib/jekyll/related_posts.rb         @jekyll/build
-/lib/jekyll/renderer.rb              @jekyll/build
-/lib/jekyll/site.rb                  @jekyll/build
-/lib/jekyll/static_file.rb           @jekyll/build
-/lib/jekyll/stevenson.rb             @jekyll/build
-/lib/jekyll/tags/                    @jekyll/build
-/lib/jekyll/url.rb                   @jekyll/build
-/lib/jekyll/utils/                   @jekyll/build
-/lib/jekyll/utils.rb                 @jekyll/build
-
-# @jekyll/ecosystem
-/lib/jekyll/external.rb              @jekyll/ecosystem
-/lib/jekyll/generator.rb             @jekyll/ecosystem
-/lib/jekyll/hooks.rb                 @jekyll/ecosystem
-/lib/jekyll/plugin.rb                @jekyll/ecosystem
-/lib/jekyll/plugin_manager.rb        @jekyll/ecosystem
-/lib/jekyll/theme.rb                 @jekyll/ecosystem
-/lib/jekyll/theme_builder.rb         @jekyll/ecosystem
-
-# @jekyll/stability
-Gemfile                              @jekyll/stability
-*.gemspec                            @jekyll/stability
-.travis.yml                          @jekyll/stability
-appveyor.yml                         @jekyll/stability
-/lib/jekyll/configuration.rb         @jekyll/stability
-/lib/jekyll/deprecator.rb            @jekyll/stability
-/lib/jekyll/frontmatter_defaults.rb  @jekyll/stability
-/lib/site_template                   @jekyll/stability
-/lib/theme_template                  @jekyll/stability
-/features/                           @jekyll/stability
-/test/                               @jekyll/stability
-
-# Special cases
-.github/                             @jekyll/affinity-team-captains
-CODE_OF_CONDUCT.markdown             @jekyll/affinity-team-captains
-History.markdown                     @jekyll/affinity-team-captains
-LICENSE                              @jekyll/affinity-team-captains   # This file should never change.
-README.markdown                      @jekyll/affinity-team-captains
-/lib/jekyll/version.rb               @jekyll/affinity-team-captains
-/rake/                               @jekyll/affinity-team-captains
-/script/                             @jekyll/affinity-team-captains

.github/CONTRIBUTING.markdown

@@ -1,151 +0,0 @@
-# Contributing to Jekyll
-
-Hi there! Interested in contributing to Jekyll? We'd love your help. Jekyll is an open source project, built one contribution at a time by users like you.
-
-## Where to get help or report a problem
-
-See [the support guidelines](https://jekyllrb.com/docs/support/)
-
-## Ways to contribute
-
-Whether you're a developer, a designer, or just a Jekyll devotee, there are lots of ways to contribute. Here's a few ideas:
-
-* [Install Jekyll on your computer](https://jekyllrb.com/docs/installation/) and kick the tires. Does it work? Does it do what you'd expect? If not, [open an issue](https://github.com/jekyll/jekyll/issues/new) and let us know.
-* Comment on some of the project's [open issues](https://github.com/jekyll/jekyll/issues). Have you experienced the same problem? Know a work around? Do you have a suggestion for how the feature could be better?
-* Read through [the documentation](https://jekyllrb.com/docs/home/), and click the "improve this page" button, any time you see something confusing, or have a suggestion for something that could be improved.
-* Browse through [the Jekyll discussion forum](https://talk.jekyllrb.com/), and lend a hand answering questions. There's a good chance you've already experienced what another user is experiencing.
-* Find [an open issue](https://github.com/jekyll/jekyll/issues) (especially [those labeled `help-wanted`](https://github.com/jekyll/jekyll/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted)), and submit a proposed fix. If it's your first pull request, we promise we won't bite, and are glad to answer any questions.
-* Help evaluate [open pull requests](https://github.com/jekyll/jekyll/pulls), by testing the changes locally and reviewing what's proposed.
-
-## Submitting a pull request
-
-### Pull requests generally
-
-* The smaller the proposed change, the better. If you'd like to propose two unrelated changes, submit two pull requests.
-
-* The more information, the better. Make judicious use of the pull request body. Describe what changes were made, why you made them, and what impact they will have for users.
-
-* Pull requests are easy and fun. If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/).
-
-* If you're submitting a code contribution, be sure to read the [code contributions](#code-contributions) section below.
-
-### Submitting a pull request via github.com
-
-Many small changes can be made entirely through the github.com web interface.
-
-1. Navigate to the file within [`jekyll/jekyll`](https://github.com/jekyll/jekyll) that you'd like to edit.
-2. Click the pencil icon in the top right corner to edit the file
-3. Make your proposed changes
-4. Click "Propose file change"
-5. Click "Create pull request"
-6. Add a descriptive title and detailed description for your proposed change. The more information the better.
-7. Click "Create pull request"
-
-That's it! You'll be automatically subscribed to receive updates as others review your proposed change and provide feedback.
-
-### Submitting a pull request via Git command line
-
-1. Fork the project by clicking "Fork" in the top right corner of [`jekyll/jekyll`](https://github.com/jekyll/jekyll).
-2. Clone the repository locally `git clone https://github.com/<you-username>/jekyll`.
-3. Create a new, descriptively named branch to contain your change ( `git checkout -b my-awesome-feature` ).
-4. Hack away, add tests. Not necessarily in that order.
-5. Make sure everything still passes by running `script/cibuild` (see [the tests section](#running-tests-locally) below)
-6. Push the branch up ( `git push origin my-awesome-feature` ).
-7. Create a pull request by visiting `https://github.com/<your-username>/jekyll` and following the instructions at the top of the screen.
-
-## Proposing updates to the documentation
-
-We want the Jekyll documentation to be the best it can be. We've open-sourced our docs and we welcome any pull requests if you find it lacking.
-
-### How to submit changes
-
-You can find the documentation for jekyllrb.com in the [docs](https://github.com/jekyll/jekyll/tree/master/docs) directory. See the section above, [submitting a pull request](#submitting-a-pull-request) for information on how to propose a change.
-
-One gotcha, all pull requests should be directed at the `master` branch (the default branch).
-
-### Updating FontAwesome iconset for jekyllrb.com
-
-We use a custom version of FontAwesome which contains just the icons we use.
-
-If you ever need to update our documentation with an icon that is not already available in our custom iconset, you'll have to regenerate the iconset using Icomoon's Generator:
-
-1. Go to <https://icomoon.io/app/>.
-2. Click `Import Icons` on the top-horizontal-bar and upload the existing `<jekyll>/docs/icomoon-selection.json`.
-3. Click `Add Icons from Library..` further down on the page, and add 'Font Awesome'.
-4. Select the required icon(s) from the Library (make sure its the 'FontAwesome' library instead of 'IcoMoon-Free' library).
-5. Click `Generate Font` on the bottom-horizontal-bar.
-6. Inspect the included icons and proceed by clicking `Download`.
-7. Extract the font files and adapt the CSS to the paths we use in Jekyll:
-  - Copy the entire `fonts` directory over and overwrite existing ones at `<jekyll>/docs/`.
-  - Copy the contents of `selection.json` and overwrite existing content inside `<jekyll>/docs/icomoon-selection.json`.
-  - Copy the entire `@font-face {}` declaration and only the **new-icon(s)' css declarations** further below, to update the
-  `<jekyll>/docs/_sass/_font-awesome.scss` sass partial.
-  - Fix paths in the `@font-face {}` declaration by adding `../` before `fonts/FontAwesome.*` like so:
-  `('../fonts/Fontawesome.woff?9h6hxj')`.
-
-### Adding plugins
-
-If you want to add your plugin to the [list of plugins](https://jekyllrb.com/docs/plugins/#available-plugins), please submit a pull request modifying the [plugins page source file](https://github.com/jekyll/jekyll/blob/master/docs/_docs/plugins.md) by adding a link to your plugin under the proper subheading depending upon its type.
-
-## Code Contributions
-
-Interesting in submitting a pull request? Awesome. Read on. There's a few common gotchas that we'd love to help you avoid.
-
-### Tests and documentation
-
-Any time you propose a code change, you should also include updates to the documentation and tests within the same pull request.
-
-#### Documentation
-
-If your contribution changes any Jekyll behavior, make sure to update the documentation. Documentation lives in the `docs/_docs` folder (spoiler alert: it's a Jekyll site!). If the docs are missing information, please feel free to add it in. Great docs make a great project. Include changes to the documentation within your pull request, and once merged, `jekyllrb.com` will be updated.
-
-#### Tests
-
-* If you're creating a small fix or patch to an existing feature, a simple test is more than enough. You can usually copy/paste from an existing example in the `tests` folder, but if you need you can find out about our tests suites [Shoulda](https://github.com/thoughtbot/shoulda/tree/master) and [RSpec-Mocks](https://github.com/rspec/rspec-mocks).
-
-* If it's a brand new feature, create a new [Cucumber](https://github.com/cucumber/cucumber/) feature, reusing existing steps where appropriate.
-
-### Code contributions generally
-
-* Jekyll uses the [Rubocop](https://github.com/bbatsov/rubocop) static analyzer to ensure that contributions follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby). Please check your code using `script/fmt` and resolve any errors before pushing your branch.
-
-* Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't).
-
-* You can use the command `script/console` to start a REPL to explore the result of
-Jekyll's methods. It also provides you with helpful methods to quickly create a
-site or configuration. [Feel free to check it out!](https://github.com/jekyll/jekyll/blob/master/script/console)
-
-## Running tests locally
-
-### Test Dependencies
-
-To run the test suite and build the gem you'll need to install Jekyll's dependencies by running the following command:
-
-```sh
-script/bootstrap
-```
-
-Before you make any changes, run the tests and make sure that they pass (to confirm your environment is configured properly):
-
-```sh
-script/cibuild
-```
-
-If you are only updating a file in `test/`, you can use the command:
-
-```sh
-script/test test/blah_test.rb
-```
-
-If you are only updating a `.feature` file, you can use the command:
-
-```sh
-script/cucumber features/blah.feature
-```
-
-Both `script/test` and `script/cucumber` can be run without arguments to
-run its entire respective suite.
-
-## A thank you
-
-Thanks! Hacking on Jekyll should be fun. If you find any of this hard to figure out, let us know so we can improve our process or documentation!

.github/ISSUE_TEMPLATE.md

@@ -1,78 +0,0 @@
-<!--
-  Hi! Thanks for considering to file a bug with Jekyll. Please take the time to
-  answer the basic questions. You can convert `[ ]` into `[x]` to check boxes (or submit
-  and check.) If there is no need for certain fields like output and redirection, please delete
-  those headers before submitting. We know not all tickets require those steps.
-  Otherwise, please try to be as detailed as possible.
-
-  If you are unsure this is a bug in Jekyll, or this is a bug caused
-  by a plugin that isn't directly related to Jekyll, or if this is just
-  a generic usage question, please consider asking your question at
-  https://talk.jekyllrb.com where non-bug questions go.
-
-  Thanks!
--->
-
-- [ ] I believe this to be a bug, not a question about using Jekyll.
-- [ ] I updated to the latest Jekyll (or) if on GitHub Pages to the latest `github-pages`
-- [ ] I ran `jekyll doctor` to check my configuration
-- [ ] I read the CONTRIBUTION file at https://jekyllrb.com/docs/contributing/
-- [ ] This is a feature request.
-
----
-
-- [ ] I am on (or have tested on) ***macOS*** 10+
-- [ ] I am on (or have tested on) ***Debian/Ubuntu*** GNU/Linux
-- [ ] I am on (or have tested on) ***Fedora*** GNU/Linux
-- [ ] I am on (or have tested on) ***Arch*** GNU/Linux
-- [ ] I am on (or have tested on) ***Other*** GNU/Linux
-- [ ] I am on (or have tested on) ***Windows*** 10+
-
-<!--
-  Other GNU/Linux includes Scientific GNU/Linux, CentOS GNU/Linux, and others.
-  If you are on a minor sub-distro (such as ElementaryOS which does not diverge from
-  Ubuntu much, please check the parent distro. Kubuntu, Edubuntu, Lubuntu should
-  also be flagged as Ubuntu as their packages come from upstream Ubuntu.
--->
-
----
-
-- [ ] I was trying to install.
-- [ ] There is a broken Plugin API.
-- [ ] I had an error on GitHub Pages, and I have reproduced it locally.
-- [ ] I had an error on GitHub Pages, and GitHub Support said it was a Jekyll Bug.
-- [ ] I had an error on GitHub Pages and I did not test it locally.
-- [ ] I was trying to build.
-- [ ] It was another bug.
-
-## My Reproduction Steps
-
-<!--
-  If this error occurred on GitHub Pages, please try to provide us with logs,
-  and look at them yourself, to determine if this is an actual Jekyll bug. In
-  the event you are unsure, file a ticket, however, when you do please provide
-  the logs (strip them of personal information.)
-
-  If you have trouble finding your logs, please email support@github.com and
-  they will happily help you. If you cannot find logs, please try your best to
-  replicate it locally because we cannot fix a problem if we do not know
-  exactly what caused it, or within a relatively close distance.
--->
-
-<!--
-  Insert the steps you took to for this problem to exist. Such as the
-  directories you created and, the full command you ran, and include any
-  plugins you have installed, this is very important.
-
-  If your steps are complicated, you can also submit a GitHub
-  repository (please no zips, they will be removed and rejected by maintainers,)
-  and just supply a command for us to reproduce it ourselves.
--->
-
-## The Output I Wanted
-
-<!--
-  Insert the output from the command. Alter it as little as you can.
-  The minimum should be personal information. Though we normally don't log
-  anything like that so there should be no need to alter it.
--->

.github/SUPPORT.markdown

@@ -1,20 +0,0 @@
-# Jekyll Support
-
-## Getting Help
-
-**Jekyll's issue tracker is not a support forum.**
-
-If you're looking for support for Jekyll, there are a lot of options:
-
-* Read [Jekyll Documentation](https://jekyllrb.com/docs/home/)
-* If you have a question about using Jekyll, start a discussion on [Jekyll Forum](https://talk.jekyllrb.com/) or [StackOverflow](https://stackoverflow.com/questions/tagged/jekyll)
-* Chat with Jekyllers — Join [our Gitter channel](https://gitter.im/jekyll/jekyll) or [our IRC channel on Freenode](irc:irc.freenode.net/jekyll)
-
-There are a bunch of helpful community members on these services that should be willing to point you in the right direction.
-
-## Report a bug
-
-* If you think you've found a bug within a Jekyll plugin, open an issue in that plugin's repository — First [look for the plugin on rubygems](https://rubygems.org/) then click on the `Homepage` link to access the plugin repository.
-* If you think you've found a bug within Jekyll itself, [open an issue](https://github.com/jekyll/jekyll/issues/new).
-
-Happy Jekyllin'!

.github/first-timers-issue-template.md

@@ -1,44 +0,0 @@
-### 🆕🐥☝ First Timers Only.
-
-This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
-
-[About First Timers Only](http://www.firsttimersonly.com/).
-
-### 🤔 What you will need to know.
-
-Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
-
-### 📋 Step by Step
-
-- [ ] 👌 **Join the team**: Add yourself to a Jekyll affinity team.
-
-  Go to [teams.jekyllrb.com](https://teams.jekyllrb.com/) and join a team that best fits your interests. Once you click the link to join a team, you will soon receive an email inviting you to join the Jekyll organization.
-
-- [ ] 🙋 **Claim this issue**: Comment below.
-
-  Leave a comment that you have claimed this issue.
-
-- [ ] 📝 **Update** the file [$FILENAME]($BRANCH_URL) in the `$REPO` repository (press the little pen Icon) and edit the line as shown below.
-
-
-```diff
-$DIFF
-```
-
-
-- [ ] 💾 **Commit** your changes
-
-- [ ] 🔀 **Start a Pull Request**. There are two ways how you can start a pull request:
-
-  1. If you are familiar with the terminal or would like to learn it, [here is a great tutorial](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) on how to send a pull request using the terminal.
-
-  2. You can [edit files directly in your browser](https://help.github.com/articles/editing-files-in-your-repository/)
-
-- [ ] 🏁 **Done** Ask in comments for a review :)
-
-### 🤔❓ Questions
-
-Leave a comment below!
-
-
-This issue was created by [First-Timers-Bot](https://github.com/hoodiehq/first-timers-bot).

.github/first-timers.yml

@@ -1,6 +0,0 @@
-repository: jekyll
-labels:
-  - good first issue
-  - help-wanted
-  - first-time-only
-template: .github/first-timers-issue-template.md

.gitignore

@@ -13,7 +13,6 @@
 /vendor
 Gemfile.lock
 _site/
-bin/
 bbin/
 coverage
 gh-pages/

.rubocop.yml

@@ -1,162 +1,80 @@
----
+Metrics/MethodLength: { Max:  24 }
+Metrics/ClassLength:  { Max: 240 }
+Metrics/ModuleLength: { Max: 240 }
+Metrics/LineLength:   { Max: 112 }
+Metrics/CyclomaticComplexity: { Max: 8 }
+Metrics/PerceivedComplexity: { Max: 8 }
+Metrics/ParameterLists: { Max: 4 }
+Metrics/MethodLength: { Max: 24 }
+Metrics/AbcSize: { Max: 20 }
 
-require:
-  - ./rubocop/jekyll
+Style/IndentHash: { EnforcedStyle: consistent }
+Style/HashSyntax: { EnforcedStyle: hash_rockets }
+Style/SignalException: { EnforcedStyle: only_raise }
+Style/AlignParameters: { EnforcedStyle: with_fixed_indentation }
+Style/StringLiteralsInInterpolation: { EnforcedStyle: double_quotes }
+Style/MultilineMethodCallIndentation: { EnforcedStyle: indented }
+Style/MultilineOperationIndentation: { EnforcedStyle: indented }
+Style/FirstParameterIndentation: { EnforcedStyle: consistent }
+Style/StringLiterals: { EnforcedStyle: double_quotes }
+Style/RegexpLiteral: { EnforcedStyle: slashes }
+Style/IndentArray: { EnforcedStyle: consistent }
+Style/ExtraSpacing: { AllowForAlignment: true }
 
-Jekyll/NoPutsAllowed:
-  Exclude:
-    - rake/*.rake
-
-AllCops:
-  TargetRubyVersion: 2.3
-  Include:
-    - lib/**/*.rb
-    - test/**/*.rb
-  Exclude:
-    - bin/**/*
-    - exe/**/*
-    - benchmark/**/*
-    - script/**/*
-    - vendor/**/*
-    - tmp/**/*
-Layout/AlignHash:
-  EnforcedHashRocketStyle: table
-Layout/IndentationWidth:
-  Severity: error
-Layout/IndentArray:
-  EnforcedStyle: consistent
-Layout/IndentHash:
-  EnforcedStyle: consistent
-Layout/MultilineMethodCallIndentation:
-  EnforcedStyle: indented
-Layout/MultilineOperationIndentation:
-  EnforcedStyle: indented
-Lint/NestedPercentLiteral:
-  Exclude:
-    - test/test_site.rb
-Layout/EmptyComment:
-  Enabled: false
-Layout/EndAlignment:
-  Severity: error
-Lint/UnreachableCode:
-  Severity: error
-Lint/Void:
-  Exclude:
-    - lib/jekyll/site.rb
-Metrics/AbcSize:
-  Max: 21
-Metrics/BlockLength:
-  Exclude:
-    - test/**/*.rb
-    - lib/jekyll/configuration.rb
-    - rake/*.rake
-Metrics/ClassLength:
-  Exclude:
-    - !ruby/regexp /features\/.*.rb$/
-    - !ruby/regexp /test\/.*.rb$/
-    - lib/jekyll/document.rb
-    - lib/jekyll/site.rb
-    - lib/jekyll/commands/serve.rb
-    - lib/jekyll/configuration.rb
-  Max: 240
-Metrics/CyclomaticComplexity:
-  Exclude:
-    - lib/jekyll/utils.rb
-    - lib/jekyll/commands/serve.rb
-Metrics/LineLength:
-  Exclude:
-    - !ruby/regexp /features\/.*.rb/
-    - Rakefile
-    - rake/*.rake
-    - Gemfile
-  Max: 100
-  Severity: warning
-Metrics/MethodLength:
-  CountComments: false
-  Max: 20
-  Severity: error
-Metrics/ModuleLength:
-  Max: 240
-Metrics/ParameterLists:
-  Max: 4
-Metrics/PerceivedComplexity:
-  Max: 8
-Naming/FileName:
-  Enabled: false
-Naming/HeredocDelimiterNaming:
-  Exclude:
-    - test/**/*.rb
-Naming/MemoizedInstanceVariableName:
-  Exclude:
-    - lib/jekyll/page_without_a_file.rb
-    - lib/jekyll/drops/unified_payload_drop.rb
-    - lib/jekyll/drops/site_drop.rb
-Naming/UncommunicativeMethodParamName:
-  AllowedNames:
-    - _
-Security/MarshalLoad:
-  Exclude:
-    - !ruby/regexp /test\/.*.rb$/
-    - lib/jekyll/regenerator.rb
-Security/YAMLLoad:
-  Exclude:
-    - !ruby/regexp /features\/.*.rb/
-    - !ruby/regexp /test\/.*.rb$/
-Style/AccessModifierDeclarations:
-  Enabled: false
-Style/Alias:
-  EnforcedStyle: prefer_alias_method
-Style/AndOr:
-  Severity: error
-Style/ClassAndModuleChildren:
-  Exclude:
-    - test/**/*.rb
-Style/FrozenStringLiteralComment:
-  EnforcedStyle: always
-Style/Documentation:
-  Enabled: false
-Style/DoubleNegation:
-  Enabled: false
-Style/FormatStringToken:
-  Exclude:
-    - lib/jekyll/utils/ansi.rb
-Style/GuardClause:
-  Enabled: false
-Style/HashSyntax:
-  EnforcedStyle: hash_rockets
-  Severity: error
-Style/MixinUsage:
-  Exclude:
-    - test/helper.rb
-Style/ModuleFunction:
-  Enabled: false
-Style/MultilineTernaryOperator:
-  Severity: error
 Style/PercentLiteralDelimiters:
   PreferredDelimiters:
-    "%q": "{}"
-    "%Q": "{}"
-    "%r": "!!"
-    "%s": "()"
-    "%w": "()"
-    "%W": "()"
-    "%x": "()"
-Style/RegexpLiteral:
-  EnforcedStyle: percent_r
-Style/RescueModifier:
-  Enabled: false
-Style/SafeNavigation:
+    '%q': '{}'
+    '%Q': '{}'
+    '%r': '!!'
+    '%s': '()'
+    '%w': '()'
+    '%W': '()'
+    '%x': '()'
+
+Style/AlignArray:                     { Enabled: false }
+Style/StringLiterals:                 { Enabled: false }
+Style/Documentation:                  { Enabled: false }
+Style/DoubleNegation:                 { Enabled: false }
+Style/UnneededCapitalW:               { Enabled: false }
+Style/EmptyLinesAroundModuleBody:     { Enabled: false }
+Style/EmptyLinesAroundAccessModifier: { Enabled: false }
+Style/BracesAroundHashParameters:     { Enabled: false }
+Style/SpaceInsideBrackets:            { Enabled: false }
+Style/IfUnlessModifier:               { Enabled: false }
+Style/ModuleFunction:                 { Enabled: false }
+Style/RescueModifier:                 { Enabled: false }
+Style/GuardClause:                    { Enabled: false }
+Style/FileName:                       { Enabled: false }
+Lint/UselessAccessModifier:           { Enabled: false }
+Style/SpaceAroundOperators:           { Enabled: false }
+Style/RedundantReturn:                { Enabled: false }
+Style/SingleLineMethods:              { Enabled: false }
+
+AllCops:
+  TargetRubyVersion: 2.0
+  Include:
+  - lib/**/*.rb
+
   Exclude:
-    - lib/jekyll/document.rb
-Style/SignalException:
-  EnforcedStyle: only_raise
-Style/StringLiterals:
-  EnforcedStyle: double_quotes
-Style/StringLiteralsInInterpolation:
-  EnforcedStyle: double_quotes
-Style/SymbolArray:
-  EnforcedStyle: brackets
-Style/TrailingCommaInArrayLiteral:
-  EnforcedStyleForMultiline: consistent_comma
-Style/TrailingCommaInHashLiteral:
-  EnforcedStyleForMultiline: consistent_comma
+  - .rubocop.yml
+  - .codeclimate.yml
+  - .travis.yml
+  - .gitignore
+  - .rspec
+
+  - Gemfile.lock
+  - CHANGELOG.{md,markdown,txt,textile}
+  - CONTRIBUTING.{md,markdown,txt,textile}
+  - readme.{md,markdown,txt,textile}
+  - README.{md,markdown,txt,textile}
+  - Readme.{md,markdown,txt,textile}
+  - ReadMe.{md,markdown,txt,textile}
+  - COPYING
+  - LICENSE
+
+  - site/**/*
+  - test/**/*
+  - vendor/**/*
+  - features/**/*
+  - script/**/*
+  - spec/**/*

.travis.yml

@@ -1,3 +1,4 @@
+before_script: bundle update
 bundler_args: --without benchmark:site:development
 script: script/cibuild
 cache: bundler
@@ -5,34 +6,32 @@ language: ruby
 sudo: false
 
 rvm:
-  - &ruby1 2.5.1
-  - &ruby2 2.4.4
-  - &ruby3 2.3.7
-  - &jruby jruby-9.1.16.0
+  - &ruby1 2.3.0
+  - &ruby2 2.2.4
+  - &ruby3 2.1.8
+  - &ruby4 2.0.0-p648
+  - &jruby jruby-9.0.4.0
+  - &rhead ruby-head
 
 matrix:
-  include:
-    - rvm: *ruby1
-      env: TEST_SUITE=fmt
-      name: "🤖️ Code Format"
-    - rvm: *ruby1
-      env: TEST_SUITE=default-site
-      name: "🏠️ Default Site"
-  exclude:
+  fast_finish: true
+  allow_failures:
     - rvm: *jruby
-      env: TEST_SUITE=cucumber
-
+    - rvm: *rhead
 env:
   matrix:
     - TEST_SUITE=test
     - TEST_SUITE=cucumber
-branches:
-  only:
-    - master
-    - themes
-    - /*-stable/
 
 notifications:
+  irc:
+    template: "%{repository}#%{build_number} (%{branch}) %{message} %{build_url}"
+    channels: irc.freenode.org#jekyll
+
+  email:
+    recipients:
+      - jordon@envygeeks.io
+
   slack:
     secure: "\
       dNdKk6nahNURIUbO3ULhA09/vTEQjK0fNbgjVjeYPEvROHgQBP1cIP3AJy8aWs8rl5Yyow4Y\
@@ -48,10 +47,3 @@ addons:
         DA4vsRURfABU0fIhwYkQuZqEcA3d8TL36BZcGEshG6MQ2AmnYsmFiTcxqV5bmlElHEqQuT\
         5SUFXLafgZPBnL0qDwujQcHukID41sE=\
       "
-# regular test configuration
-after_success:
-  - bundle exec codeclimate-test-reporter
-
-before_install:
-  - gem update --system
-  - gem install bundler --version 1.16.2

CODE_OF_CONDUCT.markdown

@@ -1,46 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting a project maintainer. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html][version]
-
-[homepage]: https://www.contributor-covenant.org/
-[version]: https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONDUCT.markdown

@@ -1,10 +1,4 @@
----
-title: Code of Conduct
-permalink: "/docs/code_of_conduct/"
-note: This file is autogenerated. Edit /CODE_OF_CONDUCT.markdown instead.
-redirect_from: "/conduct/index.html"
-editable: false
----
+# Contributor Code of Conduct
 
 As contributors and maintainers of this project, and in the interest of
 fostering an open and welcoming community, we pledge to respect all people who

CONTRIBUTING.markdown

@@ -0,0 +1,106 @@
+Contribute
+==========
+
+So you've got an awesome idea to throw into Jekyll. Great! Please keep the
+following in mind:
+
+* **Use https://talk.jekyllrb.com for non-technical or indirect Jekyll questions that are not bugs.**
+* **Contributions will not be accepted without tests or necessary documentation updates.**
+* If you're creating a small fix or patch to an existing feature, just a simple
+  test will do. Please stay in the confines of the current test suite and use
+  [Shoulda](https://github.com/thoughtbot/shoulda/tree/master) and
+  [RSpec-Mocks](https://github.com/rspec/rspec-mocks).
+* If it's a brand new feature, make sure to create a new
+  [Cucumber](https://github.com/cucumber/cucumber/) feature and reuse steps
+  where appropriate. Also, whipping up some documentation in your fork's `site`
+  would be appreciated, and once merged it will be transferred over to the main
+  `site`, jekyllrb.com.
+* If your contribution changes any Jekyll behavior, make sure to update the
+  documentation. It lives in `site/_docs`. If the docs are missing information,
+  please feel free to add it in. Great docs make a great project!
+* Please follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby)
+  when modifying Ruby code.
+* Please do your best to submit **small pull requests**. The easier the proposed
+  change is to review, the more likely it will be merged.
+* When submitting a pull request, please make judicious use of the pull request
+  body. A description of what changes were made, the motivations behind the
+  changes and [any tasks completed or left to complete](http://git.io/gfm-tasks)
+  will also speed up review time.
+
+Test Dependencies
+-----------------
+
+To run the test suite and build the gem you'll need to install Jekyll's
+dependencies. Simply run this command to get all setup:
+
+    $ script/bootstrap
+
+Before you start, run the tests and make sure that they pass (to confirm your
+environment is configured properly):
+
+    $ script/cibuild
+
+If you are only updating a file in `test/`, you can use the command:
+
+    $ script/test test/blah_test.rb
+
+If you are only updating a `.feature` file, you can use the command:
+
+    $ script/cucumber features/blah.feature
+
+Both `script/test` and `script/cucumber` can be run without arguments to
+run its entire respective suite.
+
+Workflow
+--------
+
+Here's the most direct way to get your work merged into the project:
+
+* Fork the project.
+* Clone down your fork ( `git clone git@github.com:[username]/jekyll.git` ).
+* Create a topic branch to contain your change ( `git checkout -b my_awesome_feature` ).
+* Hack away, add tests. Not necessarily in that order.
+* Make sure everything still passes by running `script/cibuild`.
+* If necessary, rebase your commits into logical chunks, without errors.
+* Push the branch up ( `git push origin my_awesome_feature` ).
+* Create a pull request against jekyll/jekyll and describe what your change
+  does and the why you think it should be merged.
+
+Updating Documentation
+----------------------
+
+We want the Jekyll documentation to be the best it can be. We've
+open-sourced our docs and we welcome any pull requests if you find it
+lacking.
+
+You can find the documentation for jekyllrb.com in the
+[site](https://github.com/jekyll/jekyll/tree/master/site) directory of
+Jekyll's repo on GitHub.com.
+
+All documentation pull requests should be directed at `master`. Pull
+requests directed at another branch will not be accepted.
+
+The [Jekyll wiki](https://github.com/jekyll/jekyll/wiki) on GitHub
+can be freely updated without a pull request as all GitHub users have access.
+
+If you want to add your plugin to the
+[list of plugins](http://jekyllrb.com/docs/plugins/#available-plugins),
+please submit a pull request modifying the
+[plugins page source file](site/_docs/plugins.md) by adding a
+link to your plugin under the proper subheading depending upon its type.
+
+Gotchas
+-------
+
+* Please do not bump the gem version in your pull requests.
+* Try to keep your patch(es) based from the latest commit on jekyll/jekyll.
+  The easier it is to apply your work, the less work the maintainers have to do,
+  which is always a good thing.
+* Please don't tag your GitHub issue with [fix], [feature], etc. The maintainers
+  actively read the issues and will label it once they come across it.
+
+Finally...
+----------
+
+Thanks! Hacking on Jekyll should be fun. If you find any of this hard to figure
+out, let us know so we can improve our process or documentation!

Gemfile

@@ -1,12 +1,10 @@
-# frozen_string_literal: true
-
 source "https://rubygems.org"
 gemspec :name => "jekyll"
 
-gem "rake", "~> 12.0"
-
+gem "rake", "~> 10.1"
 group :development do
   gem "launchy", "~> 2.3"
+  gem "rubocop", "~> 0.40"
   gem "pry"
 
   unless RUBY_ENGINE == "jruby"
@@ -17,82 +15,70 @@ end
 #
 
 group :test do
-  gem "codeclimate-test-reporter", "~> 1.0.5"
-  gem "cucumber", "~> 3.0"
-  gem "httpclient"
+  gem "cucumber", "~> 2.1"
   gem "jekyll_test_plugin"
   gem "jekyll_test_plugin_malicious"
-  gem "nokogiri", "~> 1.7"
-  gem "rspec"
+  gem "codeclimate-test-reporter"
   gem "rspec-mocks"
-  gem "rubocop", "~> 0.57.2"
-  gem "test-dependency-theme", :path => File.expand_path("test/fixtures/test-dependency-theme", __dir__)
-  gem "test-theme", :path => File.expand_path("test/fixtures/test-theme", __dir__)
-
-  gem "jruby-openssl" if RUBY_ENGINE == "jruby"
+  gem "nokogiri"
+  gem "rspec"
 end
 
 #
 
 group :test_legacy do
-  if RUBY_PLATFORM =~ %r!cygwin!
-    gem "test-unit"
+  if RUBY_PLATFORM =~ /cygwin/ || RUBY_VERSION.start_with?("2.2")
+    gem 'test-unit'
   end
 
-  gem "minitest"
-  gem "minitest-profile"
-  gem "minitest-reporters"
-  gem "shoulda"
+  gem "redgreen"
   gem "simplecov"
+  gem "minitest-reporters"
+  gem "minitest-profile"
+  gem "minitest"
+  gem "shoulda"
 end
 
 #
 
 group :benchmark do
   if ENV["BENCHMARK"]
-    gem "benchmark-ips"
-    gem "rbtrace"
     gem "ruby-prof"
+    gem "benchmark-ips"
     gem "stackprof"
+    gem "rbtrace"
   end
 end
 
 #
 
 group :jekyll_optional_dependencies do
+  gem "toml", "~> 0.1.0"
   gem "coderay", "~> 1.1.0"
-  gem "jekyll-coffeescript"
-  gem "jekyll-docs", :path => "../docs" if Dir.exist?("../docs") && ENV["JEKYLL_VERSION"]
-  gem "jekyll-feed", "~> 0.9"
-  gem "jekyll-gist"
-  gem "jekyll-paginate"
-  gem "jekyll-redirect-from"
-  gem "kramdown", "~> 1.14"
+  gem "jekyll-docs", path: '../docs' if Dir.exist?('../docs') && ENV["JEKYLL_VERSION"]
+  gem "jekyll-gist", "~> 1.0"
+  gem "jekyll-feed", "~> 0.1.3"
+  gem "jekyll-coffeescript", "~> 1.0"
+  gem "jekyll-redirect-from", "~> 0.9.1"
+  gem "jekyll-paginate", "~> 1.0"
   gem "mime-types", "~> 3.0"
-  gem "rdoc", "~> 6.0"
-  gem "tomlrb", "~> 1.2"
+  gem "kramdown", "~> 1.9"
+  gem "rdoc", "~> 4.2"
 
-  platform :ruby, :mswin, :mingw, :x64_mingw do
-    gem "classifier-reborn", "~> 2.2.0"
+  platform :ruby, :mswin, :mingw do
+    gem "rdiscount", "~> 2.0"
+    gem "pygments.rb", "~> 0.6.0"
+    gem "redcarpet", "~> 3.2", ">= 3.2.3"
+    gem "classifier-reborn", "~> 2.0"
     gem "liquid-c", "~> 3.0"
-    gem "pygments.rb", "~> 1.0"
-    gem "yajl-ruby", "~> 1.3"
   end
-
-  # Windows does not include zoneinfo files, so bundle the tzinfo-data gem
-  gem "tzinfo-data", :platforms => [:mingw, :mswin, :x64_mingw, :jruby]
 end
 
 #
 
 group :site do
   if ENV["PROOF"]
-    gem "html-proofer", "~> 3.4"
+    gem "html-proofer", "~> 2.0"
   end
-
-  gem "jekyll-avatar"
-  gem "jekyll-mentions"
-  gem "jekyll-seo-tag"
-  gem "jekyll-sitemap"
   gem "jemoji"
 end

ISSUE_TEMPLATE.md

@@ -0,0 +1,20 @@
+###### What version of Jekyll are you using (`jekyll -v`)?
+
+
+
+###### What operating system are you using?
+
+
+
+###### What did you do?
+(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
+
+
+
+###### What did you expect to see?
+
+
+
+###### What did you see instead?
+
+

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2008-2018 Tom Preston-Werner and Jekyll contributors
+Copyright (c) 2008-2016 Tom Preston-Werner
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.markdown

@@ -1,83 +1,58 @@
-# [Jekyll](https://jekyllrb.com/)
+# [Jekyll](http://jekyllrb.com/)
 
 [![Gem Version](https://img.shields.io/gem/v/jekyll.svg)][ruby-gems]
-[![Linux Build Status](https://img.shields.io/travis/jekyll/jekyll/master.svg?label=Linux%20build)][travis]
-[![Windows Build status](https://img.shields.io/appveyor/ci/jekyll/jekyll/master.svg?label=Windows%20build)][appveyor]
-[![Maintainability](https://api.codeclimate.com/v1/badges/8ba0cb5b17bb9848e128/maintainability)][codeclimate]
-[![Test Coverage](https://api.codeclimate.com/v1/badges/8ba0cb5b17bb9848e128/test_coverage)][coverage]
+[![Build Status](https://travis-ci.org/jekyll/jekyll.svg?branch=master)][travis]
+[![Test Coverage](https://codeclimate.com/github/jekyll/jekyll/badges/coverage.svg)][coverage]
+[![Code Climate](https://codeclimate.com/github/jekyll/jekyll/badges/gpa.svg)][codeclimate]
+[![Dependency Status](https://gemnasium.com/jekyll/jekyll.svg)][gemnasium]
 [![Security](https://hakiri.io/github/jekyll/jekyll/master.svg)][hakiri]
-[![Backers on Open Collective](https://opencollective.com/jekyll/backers/badge.svg)](#backers)
-[![Sponsors on Open Collective](https://opencollective.com/jekyll/sponsors/badge.svg)](#sponsors) 
 
 [ruby-gems]: https://rubygems.org/gems/jekyll
+[gemnasium]: https://gemnasium.com/jekyll/jekyll
 [codeclimate]: https://codeclimate.com/github/jekyll/jekyll
 [coverage]: https://codeclimate.com/github/jekyll/jekyll/coverage
 [hakiri]: https://hakiri.io/github/jekyll/jekyll/master
 [travis]: https://travis-ci.org/jekyll/jekyll
-[appveyor]: https://ci.appveyor.com/project/jekyll/jekyll/branch/master
 
-Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites. Think of it like a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind [GitHub Pages](https://pages.github.com), which you can use to host sites right from your GitHub repositories.
+Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites. Think of it like a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind [GitHub Pages](http://pages.github.com), which you can use to host sites right from your GitHub repositories.
 
 ## Philosophy
 
 Jekyll does what you tell it to do — no more, no less. It doesn't try to outsmart users by making bold assumptions, nor does it burden them with needless complexity and configuration. Put simply, Jekyll gets out of your way and allows you to concentrate on what truly matters: your content.
 
-See: https://jekyllrb.com/philosophy
+## Having trouble with OS X El Capitan?
 
-## Having trouble?
-
-See: https://jekyllrb.com/docs/troubleshooting/
+See: http://jekyllrb.com/docs/troubleshooting/#jekyll-amp-mac-os-x-1011
 
 ## Getting Started
 
-* [Install](https://jekyllrb.com/docs/installation/) the gem
-* Read up about its [Usage](https://jekyllrb.com/docs/usage/) and [Configuration](https://jekyllrb.com/docs/configuration/)
+* [Install](http://jekyllrb.com/docs/installation/) the gem
+* Read up about its [Usage](http://jekyllrb.com/docs/usage/) and [Configuration](http://jekyllrb.com/docs/configuration/)
 * Take a gander at some existing [Sites](https://wiki.github.com/jekyll/jekyll/sites)
-* [Fork](https://github.com/jekyll/jekyll/fork) and [Contribute](https://jekyllrb.com/docs/contributing/) your own modifications
+* Fork and [Contribute](http://jekyllrb.com/docs/contributing/) your own modifications
 * Have questions? Check out our official forum community [Jekyll Talk](https://talk.jekyllrb.com/) or [`#jekyll` on irc.freenode.net](https://botbot.me/freenode/jekyll/)
 
 ## Code of Conduct
 
 In order to have a more open and welcoming community, Jekyll adheres to a
-[code of conduct](CODE_OF_CONDUCT.markdown) adapted from the Ruby on Rails code of
+[code of conduct](CONDUCT.markdown) adapted from the Ruby on Rails code of
 conduct.
 
 Please adhere to this code of conduct in any interactions you have in the
 Jekyll community. It is strictly enforced on all official Jekyll
 repositories, websites, and resources. If you encounter someone violating
-these terms, please let one of our [core team members](https://jekyllrb.com/team/#core-team) know and we will address it as soon as possible.
+these terms, please let a maintainer (@parkr, @envygeeks, or @mattr-) know
+and we will address it as soon as possible.
 
 ## Diving In
 
 * [Migrate](http://import.jekyllrb.com/docs/home/) from your previous system
-* Learn how the [YAML Front Matter](https://jekyllrb.com/docs/frontmatter/) works
-* Put information on your site with [Variables](https://jekyllrb.com/docs/variables/)
-* Customize the [Permalinks](https://jekyllrb.com/docs/permalinks/) your posts are generated with
-* Use the built-in [Liquid Extensions](https://jekyllrb.com/docs/templates/) to make your life easier
-* Use custom [Plugins](https://jekyllrb.com/docs/plugins/) to generate content specific to your site
-
-## Credits
-
-### Contributors
-
-This project exists thanks to all the people who contribute.
-<a href="graphs/contributors"><img src="https://opencollective.com/jekyll/contributors.svg?width=890&button=false" /></a>
-
-### Backers
-
-Thank you to all our backers! 🙏 [Become a backer](https://opencollective.com/jekyll#backer)
-
-<a href="https://opencollective.com/jekyll#backers" target="_blank"><img src="https://opencollective.com/jekyll/backers.svg?width=890" /></a>
-
-### Sponsors
-
-Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor!](https://opencollective.com/jekyll#sponsor)
-
-<a href="https://opencollective.com/jekyll/sponsor/0/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/0/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/1/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/1/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/2/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/2/avatar.svg" /></a>
-
+* Learn how the [YAML Front Matter](http://jekyllrb.com/docs/frontmatter/) works
+* Put information on your site with [Variables](http://jekyllrb.com/docs/variables/)
+* Customize the [Permalinks](http://jekyllrb.com/docs/permalinks/) your posts are generated with
+* Use the built-in [Liquid Extensions](http://jekyllrb.com/docs/templates/) to make your life easier
+* Use custom [Plugins](http://jekyllrb.com/docs/plugins/) to generate content specific to your site
 
 ## License
 
-See the [LICENSE](https://github.com/jekyll/jekyll/blob/master/LICENSE) file.
+See [LICENSE](https://github.com/jekyll/jekyll/blob/master/LICENSE).

Rakefile

@@ -1,15 +1,13 @@
-# frozen_string_literal: true
+require 'rubygems'
+require 'rake'
+require 'rdoc'
+require 'date'
+require 'yaml'
 
-require "rubygems"
-require "rake"
-require "rdoc"
-require "date"
-require "yaml"
+$LOAD_PATH.unshift(File.join(File.dirname(__FILE__), *%w[lib]))
+require 'jekyll/version'
 
-$LOAD_PATH.unshift File.expand_path("lib", __dir__)
-require "jekyll/version"
-
-Dir.glob("rake/**.rake").each { |f| import f }
+Dir.glob('rake/**.rake').each { |f| import f }
 
 #############################################################################
 #
@@ -29,53 +27,55 @@ def docs_name
   "#{name}-docs"
 end
 
-def docs_folder
-  "docs"
-end
-
 def gemspec_file
   "#{name}.gemspec"
 end
 
 def gem_file
-  "#{name}-#{Gem::Version.new(version)}.gem"
+  "#{name}-#{Gem::Version.new(version).to_s}.gem"
 end
 
 def normalize_bullets(markdown)
-  markdown.gsub(%r!\n\s{2}\*{1}!, "\n-")
+  markdown.gsub(/\n\s{2}\*{1}/, "\n-")
 end
 
 def linkify_prs(markdown)
-  markdown.gsub(%r!(?<\!&)#(\d+)!) do |word|
+  markdown.gsub(/#(\d+)/) do |word|
     "[#{word}]({{ site.repository }}/issues/#{word.delete("#")})"
   end
 end
 
+def linkify_users(markdown)
+  markdown.gsub(/(@\w+)/) do |username|
+    "[#{username}](https://github.com/#{username.delete("@")})"
+  end
+end
+
 def linkify(markdown)
-  linkify_prs(markdown)
+  linkify_users(linkify_prs(markdown))
 end
 
 def liquid_escape(markdown)
-  markdown.gsub(%r!(`{[{%].+[}%]}`)!, "{% raw %}\\1{% endraw %}")
+  markdown.gsub(/(`{[{%].+[}%]}`)/, "{% raw %}\\1{% endraw %}")
 end
 
 def custom_release_header_anchors(markdown)
-  header_regexp = %r!^(\d{1,2})\.(\d{1,2})\.(\d{1,2}) \/ \d{4}-\d{2}-\d{2}!
-  section_regexp = %r!^### \w+ \w+$!
-  markdown.split(%r!^##\s!).map do |release_notes|
+  header_regexp = /^(\d{1,2})\.(\d{1,2})\.(\d{1,2}) \/ \d{4}-\d{2}-\d{2}/
+  section_regexp = /^### \w+ \w+$/
+  markdown.split(/^##\s/).map do |release_notes|
     _, major, minor, patch = *release_notes.match(header_regexp)
     release_notes
       .gsub(header_regexp, "\\0\n{: #v\\1-\\2-\\3}")
-      .gsub(section_regexp) { |section| "#{section}\n{: ##{slugify(section)}-v#{major}-#{minor}-#{patch}}" }
+      .gsub(section_regexp) { |section| "#{section}\n{: ##{sluffigy(section)}-v#{major}-#{minor}-#{patch}}" }
   end.join("\n## ")
 end
 
-def slugify(header)
-  header.delete("#").strip.downcase.gsub(%r!\s+!, "-")
+def sluffigy(header)
+  header.gsub(/#/, '').strip.downcase.gsub(/\s+/, '-')
 end
 
 def remove_head_from_history(markdown)
-  index = markdown =~ %r!^##\s+\d+\.\d+\.\d+!
+  index = markdown =~ /^##\s+\d+\.\d+\.\d+/
   markdown[index..-1]
 end
 
@@ -84,38 +84,7 @@ def converted_history(markdown)
     custom_release_header_anchors(
       liquid_escape(
         linkify(
-          normalize_bullets(markdown)
-        )
-      )
-    )
-  )
-end
-
-def siteify_file(file, overrides_front_matter = {})
-  abort "You seem to have misplaced your #{file} file. I can haz?" unless File.exist?(file)
-  title = begin
-            File.read(file).match(%r!\A# (.*)$!)[1]
-          rescue NoMethodError
-            File.basename(file, ".*").downcase.capitalize
-          end
-  slug  = File.basename(file, ".markdown").downcase
-  front_matter = {
-    "title"     => title,
-    "permalink" => "/docs/#{slug}/",
-    "note"      => "This file is autogenerated. Edit /#{file} instead.",
-  }.merge(overrides_front_matter)
-  contents = "#{front_matter.to_yaml}---\n\n#{content_for(file)}"
-  File.write("#{docs_folder}/_docs/#{slug}.md", contents)
-end
-
-def content_for(file)
-  contents = File.read(file)
-  case file
-  when "History.markdown"
-    converted_history(contents)
-  else
-    contents.gsub(%r!\A# .*\n\n?!, "")
-  end
+          normalize_bullets(markdown)))))
 end
 
 #############################################################################
@@ -127,23 +96,23 @@ end
 multitask :default => [:test, :features]
 
 task :spec => :test
-require "rake/testtask"
+require 'rake/testtask'
 Rake::TestTask.new(:test) do |test|
-  test.libs << "lib" << "test"
-  test.pattern = "test/**/test_*.rb"
+  test.libs << 'lib' << 'test'
+  test.pattern = 'test/**/test_*.rb'
   test.verbose = true
 end
 
-require "rdoc/task"
+require 'rdoc/task'
 Rake::RDocTask.new do |rdoc|
-  rdoc.rdoc_dir = "rdoc"
+  rdoc.rdoc_dir = 'rdoc'
   rdoc.title = "#{name} #{version}"
-  rdoc.rdoc_files.include("README*")
-  rdoc.rdoc_files.include("lib/**/*.rb")
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
 end
 
 begin
-  require "cucumber/rake/task"
+  require 'cucumber/rake/task'
   Cucumber::Rake::Task.new(:features) do |t|
     t.profile = "travis"
   end
@@ -151,9 +120,9 @@ begin
     t.profile = "html_report"
   end
 rescue LoadError
-  desc "Cucumber rake task not available"
+  desc 'Cucumber rake task not available'
   task :features do
-    abort "Cucumber rake task is not available. Be sure to install cucumber as a gem or plugin"
+    abort 'Cucumber rake task is not available. Be sure to install cucumber as a gem or plugin'
   end
 end
 

appveyor.yml

@@ -1,40 +0,0 @@
-version: "{build}"
-
-clone_depth: 10
-
-branches:
-  only:
-    - master
-    - themes
-
-build: off
-
-install:
-  - SET PATH=C:\Ruby%RUBY_FOLDER_VER%\bin;%PATH%
-  - bundle install --retry 5 --jobs=%NUMBER_OF_PROCESSORS% --clean --path vendor\bundle
-
-environment:
-  BUNDLE_WITHOUT: "benchmark:site:development"
-  matrix:
-    - RUBY_FOLDER_VER: "25"
-      TEST_SUITE: "test"
-    - RUBY_FOLDER_VER: "25"
-      TEST_SUITE: "cucumber"
-    - RUBY_FOLDER_VER: "25"
-      TEST_SUITE: "default-site"
-    - RUBY_FOLDER_VER: "25-x64"
-      TEST_SUITE: "test"
-    - RUBY_FOLDER_VER: "24"
-      TEST_SUITE: "test"
-    - RUBY_FOLDER_VER: "23"
-      TEST_SUITE: "test"
-
-test_script:
-  - ruby --version
-  - gem --version
-  - bundler --version
-  - bash ./script/cibuild
-
-cache:
-  # If one of the files after the right arrow changes, cache will be skipped
-  - 'vendor\bundle -> appveyor.yml,Gemfile,jekyll.gemspec'

benchmark/capture-assign.rb

@@ -1,21 +0,0 @@
-#!/usr/bin/env ruby
-require "liquid"
-require "benchmark/ips"
-
-puts "Ruby #{RUBY_VERSION}-p#{RUBY_PATCHLEVEL}"
-puts "Liquid #{Liquid::VERSION}"
-
-template1 = '{% capture foobar %}foo{{ bar }}{% endcapture %}{{ foo }}{{ foobar }}'
-template2 = '{% assign foobar = "foo" | append: bar %}{{ foobar }}'
-
-def render(template)
-  Liquid::Template.parse(template).render("bar" => "42")
-end
-
-puts render(template1)
-puts render(template2)
-
-Benchmark.ips do |x|
-  x.report('capture') { render(template1) }
-  x.report('assign')  { render(template2) }
-end

benchmark/conditional_liquid.rb

@@ -1,101 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "liquid"
-require "benchmark/ips"
-
-# Test if processing content string without any Liquid constructs, via Liquid,
-# is slower than checking whether constructs exist ( using `String#include?` )
-# and return-ing the "plaintext" content string as is..
-#
-# Ref: https://github.com/jekyll/jekyll/pull/6735
-
-# Sample contents
-WITHOUT_LIQUID = <<-TEXT.freeze
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce auctor libero at
-pharetra tempus. Etiam bibendum magna et metus fermentum, eu cursus lorem
-mattis. Curabitur vel dui et lacus rutrum suscipit et eget neque.
-
-Nullam luctus fermentum est id blandit. Phasellus consectetur ullamcorper
-ligula, at finibus eros laoreet id. Etiam sit amet est in libero efficitur
-tristique. Ut nec magna augue. Quisque ut fringilla lacus, ac dictum enim.
-Aliquam vel ornare mauris. Suspendisse ornare diam tempor nulla facilisis
-aliquet. Sed ultrices placerat ultricies.
-TEXT
-
-WITH_LIQUID = <<-LIQUID.freeze
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce auctor libero at
-pharetra tempus. {{ author }} et metus fermentum, eu cursus lorem
-mattis. Curabitur vel dui et lacus rutrum suscipit et eget neque.
-
-Nullam luctus fermentum est id blandit. Phasellus consectetur ullamcorper
-ligula, {% if author == "Jane Doe" %} at finibus eros laoreet id. {% else %}
-Etiam sit amet est in libero efficitur.{% endif %}
-tristique. Ut nec magna augue. Quisque ut fringilla lacus, ac dictum enim.
-Aliquam vel ornare mauris. Suspendisse ornare diam tempor nulla facilisis
-aliquet. Sed ultrices placerat ultricies.
-LIQUID
-
-WITH_JUST_LIQUID_VAR = <<-LIQUID.freeze
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce auctor libero at
-pharetra tempus. et metus fermentum, eu cursus lorem, ac dictum enim.
-mattis. Curabitur vel dui et lacus rutrum suscipit et {{ title }} neque.
-
-Nullam luctus fermentum est id blandit. Phasellus consectetur ullamcorper
-ligula, at finibus eros laoreet id. Etiam sit amet est in libero efficitur.
-tristique. Ut nec magna augue. {{ author }} Quisque ut fringilla lacus
-Aliquam vel ornare mauris. Suspendisse ornare diam tempor nulla facilisis
-aliquet. Sed ultrices placerat ultricies.
-LIQUID
-
-SUITE = {
-  :"plain text"  => WITHOUT_LIQUID,
-  :"tags n vars" => WITH_LIQUID,
-  :"just vars"   => WITH_JUST_LIQUID_VAR,
-}.freeze
-
-# Mimic how Jekyll's LiquidRenderer would process a non-static file, with
-# some dummy payload
-def always_liquid(content)
-  Liquid::Template.error_mode = :warn
-  Liquid::Template.parse(content, :line_numbers => true).render(
-    "author" => "John Doe",
-    "title"  => "FooBar"
-  )
-end
-
-# Mimic how the proposed change would first execute a couple of checks and
-# proceed to process with Liquid if necessary
-def conditional_liquid(content)
-  return content if content.nil? || content.empty?
-  return content unless content.include?("{%") || content.include?("{{")
-  always_liquid(content)
-end
-
-# Test https://github.com/jekyll/jekyll/pull/6735#discussion_r165499868
-# ------------------------------------------------------------------------
-def check_with_regex(content)
-  !content.to_s.match?(%r!{[{%]!)
-end
-
-def check_with_builtin(content)
-  content.include?("{%") || content.include?("{{")
-end
-
-SUITE.each do |key, text|
-  Benchmark.ips do |x|
-    x.report("regex-check   - #{key}") { check_with_regex(text) }
-    x.report("builtin-check - #{key}") { check_with_builtin(text) }
-    x.compare!
-  end
-end
-# ------------------------------------------------------------------------
-
-# Let's roll!
-SUITE.each do |key, text|
-  Benchmark.ips do |x|
-    x.report("always thru liquid - #{key}") { always_liquid(text) }
-    x.report("conditional liquid - #{key}") { conditional_liquid(text) }
-    x.compare!
-  end
-end

benchmark/end-with-vs-regexp

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 Benchmark.ips do |x|

benchmark/flat-map

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 enum = (0..50).to_a

benchmark/hash-fetch

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 h = {:bar => 'uco'}

benchmark/local-require

@@ -1,29 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require 'benchmark/ips'
-require 'jekyll'
-require 'json'
-
-DATA = {"foo"=>"bar", "alpha"=>{"beta"=>"gamma"}, "lipsum"=>["lorem", "ipsum", "dolor"]}
-
-def local_require
-  require 'json'
-  JSON.pretty_generate(DATA)
-end
-
-def global_require
-  JSON.pretty_generate(DATA)
-end
-
-def graceful_require
-  Jekyll::External.require_with_graceful_fail("json")
-  JSON.pretty_generate(DATA)
-end
-
-Benchmark.ips do |x|
-  x.report("local-require") { local_require }
-  x.report("global-require") { global_require }
-  x.report("graceful-require") { graceful_require }
-  x.compare!
-end

benchmark/native-vs-pathutil-relative

@@ -1,33 +0,0 @@
-#!/usr/bin/env ruby
-
-# -------------------------------------------------------------------
-# Benchmarking changes in https://github.com/jekyll/jekyll/pull/6767
-# -------------------------------------------------------------------
-
-require 'benchmark/ips'
-require 'pathutil'
-
-DOC_PATH = File.join(File.expand_path(__dir__), "_puppies", "rover.md")
-COL_PATH = File.join(File.expand_path(__dir__), "_puppies")
-
-
-def pathutil_relative
-  Pathutil.new(DOC_PATH).relative_path_from(COL_PATH).to_s
-end
-
-def native_relative
-  DOC_PATH.sub("#{COL_PATH}/", "")
-end
-
-if pathutil_relative == native_relative
-  Benchmark.ips do |x|
-    x.report("pathutil") { pathutil_relative }
-    x.report("native")   { native_relative }
-    x.compare!
-  end
-else
-  print "PATHUTIL: "
-  puts pathutil_relative
-  print "NATIVE:   "
-  puts native_relative
-end

benchmark/proc-call-vs-yield

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 def fast

benchmark/regexp-vs-include.rb

@@ -1,51 +0,0 @@
-#!/usr/bin/env ruby
-require 'benchmark/ips'
-
-# For this pull request, which changes Page#dir
-# https://github.com/jekyll/jekyll/pull/4403
-
-CONTENT_CONTAINING = <<-HTML.freeze
-<!DOCTYPE HTML>
-<html lang="en-US">
-  <head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-    <meta charset="UTF-8">
-    <title>Jemoji</title>
-    <meta name="viewport" content="width=device-width,initial-scale=1">
-    <link rel="stylesheet" href="/css/screen.css">
-  </head>
-  <body class="wrap">
-    <p><img class="emoji" title=":+1:" alt=":+1:" src="https://assets.github.com/images/icons/emoji/unicode/1f44d.png" height="20" width="20" align="absmiddle"></p>
-
-  </body>
-</html>
-HTML
-CONTENT_NOT_CONTAINING = <<-HTML.freeze
-<!DOCTYPE HTML>
-<html lang="en-US">
-  <head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-    <meta charset="UTF-8">
-    <title>Jemoji</title>
-    <meta name="viewport" content="width=device-width,initial-scale=1">
-    <link rel="stylesheet" href="/css/screen.css">
-  </head>
-  <body class="wrap">
-    <p><img class="emoji" title=":+1:" alt=":+1:" src="https://assets.github.com/images/icons/emoji/unicode/1f44d.png" height="20" width="20" align="absmiddle"></p>
-
-  </body>
-</html>
-HTML
-
-Benchmark.ips do |x|
-  x.report("no body include?") { CONTENT_NOT_CONTAINING.include?('<body') }
-  x.report("no body regexp")   { CONTENT_NOT_CONTAINING =~ /<\s*body/ }
-  x.compare!
-end
-
-# No trailing slash
-Benchmark.ips do |x|
-  x.report("with body include?") { CONTENT_CONTAINING.include?('<body') }
-  x.report("with body regexp")   { CONTENT_CONTAINING =~ /<\s*body/ }
-  x.compare!
-end

benchmark/sanitize-url.rb

@@ -1,26 +0,0 @@
-#!/usr/bin/env ruby
-
-require "benchmark/ips"
-
-PATH = "/../../..../...//.....//lorem/ipsum//dolor///sit.xyz"
-
-def sanitize_with_regex
-  "/" + PATH.gsub(%r!/{2,}!, "/").gsub(%r!\.+/|\A/+!, "")
-end
-
-def sanitize_with_builtin
-  "/#{PATH}".gsub("..", "/").gsub("./", "").squeeze("/")
-end
-
-if sanitize_with_regex == sanitize_with_builtin
-  Benchmark.ips do |x|
-    x.report("sanitize w/ regexes") { sanitize_with_regex }
-    x.report("sanitize w/ builtin") { sanitize_with_builtin }
-    x.compare!
-  end
-else
-  puts "w/ regexes: #{sanitize_with_regex}"
-  puts "w/ builtin: #{sanitize_with_builtin}"
-  puts ""
-  puts "Thank you. Do try again :("
-end

benchmark/schwartzian_transform.rb

@@ -1,115 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-#
-# The Ruby documentation for #sort_by describes what's called a Schwartzian transform:
-#
-#  > A more efficient technique is to cache the sort keys (modification times in this case)
-#  > before the sort. Perl users often call this approach a Schwartzian transform, after
-#  > Randal Schwartz. We construct a temporary array, where each element is an array
-#  > containing our sort key along with the filename. We sort this array, and then extract
-#  > the filename from the result.
-#  > This is exactly what sort_by does internally.
-#
-# The well-documented efficiency of sort_by is a good reason to use it. However, when a property
-# does not exist on an item being sorted, it can cause issues (no nil's allowed!)
-# In Jekyll::Filters#sort_input, we extract the property in each iteration of #sort,
-# which is quite inefficient! How inefficient? This benchmark will tell you just how, and how much
-# it can be improved by using the Schwartzian transform. Thanks, Randall!
-
-require 'benchmark/ips'
-require 'minitest'
-require File.expand_path("../lib/jekyll", __dir__)
-
-def site
-  @site ||= Jekyll::Site.new(
-    Jekyll.configuration("source" => File.expand_path("../docs", __dir__))
-  ).tap(&:reset).tap(&:read)
-end
-
-def site_docs
-  site.collections["docs"].docs.dup
-end
-
-def sort_by_property_directly(docs, meta_key)
-  docs.sort! do |apple, orange|
-    apple_property = apple[meta_key]
-    orange_property = orange[meta_key]
-
-    if !apple_property.nil? && !orange_property.nil?
-      apple_property <=> orange_property
-    elsif !apple_property.nil? && orange_property.nil?
-      -1
-    elsif apple_property.nil? && !orange_property.nil?
-      1
-    else
-      apple <=> orange
-    end
-  end
-end
-
-def schwartzian_transform(docs, meta_key)
-  docs.collect! { |d|
-    [d[meta_key], d]
-  }.sort! { |apple, orange|
-    if !apple[0].nil? && !orange[0].nil?
-      apple.first <=> orange.first
-    elsif !apple[0].nil? && orange[0].nil?
-      -1
-    elsif apple[0].nil? && !orange[0].nil?
-      1
-    else
-      apple[-1] <=> orange[-1]
-    end
-  }.collect! { |d| d[-1] }
-end
-
-# Before we test efficiency, do they produce the same output?
-class Correctness
-  include Minitest::Assertions
-
-  require "pp"
-  define_method :mu_pp, &:pretty_inspect
-
-  attr_accessor :assertions
-
-  def initialize(docs, property)
-    @assertions = 0
-    @docs = docs
-    @property = property
-  end
-
-  def assert!
-    assert sort_by_property_directly(@docs, @property).is_a?(Array), "sort_by_property_directly must return an array"
-    assert schwartzian_transform(@docs, @property).is_a?(Array), "schwartzian_transform must return an array"
-    assert_equal sort_by_property_directly(@docs, @property),
-      schwartzian_transform(@docs, @property)
-    puts "Yeah, ok, correctness all checks out for property #{@property.inspect}"
-  end
-end
-
-Correctness.new(site_docs, "redirect_from".freeze).assert!
-Correctness.new(site_docs, "title".freeze).assert!
-
-# First, test with a property only a handful of documents have.
-Benchmark.ips do |x|
-  x.config(time: 10, warmup: 5)
-  x.report('sort_by_property_directly with sparse property') do
-    sort_by_property_directly(site_docs, "redirect_from".freeze)
-  end
-  x.report('schwartzian_transform with sparse property') do
-    schwartzian_transform(site_docs, "redirect_from".freeze)
-  end
-  x.compare!
-end
-
-# Next, test with a property they all have.
-Benchmark.ips do |x|
-  x.config(time: 10, warmup: 5)
-  x.report('sort_by_property_directly with non-sparse property') do
-    sort_by_property_directly(site_docs, "title".freeze)
-  end
-  x.report('schwartzian_transform with non-sparse property') do
-    schwartzian_transform(site_docs, "title".freeze)
-  end
-  x.compare!
-end

benchmark/sequential-assignment

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 Benchmark.ips do |x|

benchmark/string-concat

@@ -1,7 +1,6 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
-url = "https://jekyllrb.com"
+url = "http://jekyllrb.com"
 
 Benchmark.ips do |x|
   x.report('+=') { url += '/' }

benchmark/string-replacement

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 def str

benchmark/symbol-to-proc

@@ -1,4 +1,3 @@
-#!/usr/bin/env ruby
 require 'benchmark/ips'
 
 Benchmark.ips do |x|

bin/jekyll

@@ -0,0 +1,51 @@
+#!/usr/bin/env ruby
+STDOUT.sync = true
+
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), *%w( .. lib ))
+
+require 'jekyll'
+require 'mercenary'
+
+Jekyll::PluginManager.require_from_bundler
+
+Jekyll::Deprecator.process(ARGV)
+
+Mercenary.program(:jekyll) do |p|
+  p.version Jekyll::VERSION
+  p.description 'Jekyll is a blog-aware, static site generator in Ruby'
+  p.syntax 'jekyll <subcommand> [options]'
+
+  p.option 'source', '-s', '--source [DIR]', 'Source directory (defaults to ./)'
+  p.option 'destination', '-d', '--destination [DIR]', 'Destination directory (defaults to ./_site)'
+  p.option 'safe', '--safe', 'Safe mode (defaults to false)'
+  p.option 'plugins_dir', '-p', '--plugins PLUGINS_DIR1[,PLUGINS_DIR2[,...]]', Array, 'Plugins directory (defaults to ./_plugins)'
+  p.option 'layouts_dir', '--layouts DIR', String, 'Layouts directory (defaults to ./_layouts)'
+  p.option 'profile', '--profile', 'Generate a Liquid rendering profile'
+
+  Jekyll::External.require_if_present(Jekyll::External.blessed_gems) do |g|
+    cmd = g.split('-').last
+    p.command(cmd.to_sym) do |c|
+      c.syntax cmd
+      c.action do
+        Jekyll.logger.abort_with "You must install the '#{g}' gem to use the 'jekyll #{cmd}' command."
+      end
+    end
+  end
+
+  Jekyll::Command.subclasses.each { |c| c.init_with_program(p) }
+
+  p.action do |args, _|
+    if args.empty?
+      Jekyll.logger.error "A subcommand is required."
+      puts p
+      abort
+    else
+      subcommand = args.first
+      unless p.has_command? subcommand
+        Jekyll.logger.abort_with "fatal: 'jekyll #{args.first}' could not" \
+          " be found. You may need to install the jekyll-#{args.first} gem" \
+          " or a related gem to be able to use this subcommand."
+      end
+    end
+  end
+end

docs/404.html

@@ -1,37 +0,0 @@
----
-layout: error
-permalink: /404.html
-sitemap: false
----
-
-<section class="intro">
-  <div class="grid">
-    <div class="unit whole align-center">
-      <p class="first">Huh. It seems that page is<br/>Hyde-ing...</p>
-    </div>
-  </div>
-</section>
-
-<section class="error">
-  <div class="grid">
-    <div class="unit whole align-center">
-      <p>The resource you requested was not found. Here are some links to help you find your way:</p>
-      <nav class="main-nav">
-        <ul>
-          <li>
-            <a href="/">Home</a>
-          </li>
-          <li>
-            <a href="/docs/home/">Documentation</a>
-          </li>
-          <li>
-            <a href="/news/">News</a>
-          </li>
-          <li>
-            <a href="/help/">Help</a>
-          </li>
-        </ul>
-      </nav>
-    </div>
-  </div>
-</section>

docs/_config.yml

@@ -1,48 +0,0 @@
----
-version: 3.8.3
-name: Jekyll • Simple, blog-aware, static sites
-description: Transform your plain text into static websites and blogs
-url: https://jekyllrb.com
-repository: https://github.com/jekyll/jekyll
-timezone: America/Los_Angeles
-twitter:
-  username: jekyllrb
-logo: "/img/logo-2x.png"
-google_analytics_id: UA-50755011-1
-google_site_verification: onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY
-collections:
-  docs:
-    permalink: "/:collection/:path/"
-    output: true
-  posts:
-    permalink: "/news/:year/:month/:day/:title/"
-    output: true
-  tutorials:
-    output: true
-defaults:
-- scope:
-    path: _docs
-    type: docs
-  values:
-    layout: docs
-- scope:
-    path: _posts
-    type: posts
-  values:
-    layout: news_item
-    image: "/img/twitter-card.png"
-plugins:
-- jekyll-avatar
-- jekyll-feed
-- jekyll-mentions
-- jekyll-redirect-from
-- jekyll-seo-tag
-- jekyll-sitemap
-- jemoji
-sass:
-  style: compressed
-exclude:
-- ".gitignore"
-- CNAME
-- icomoon-selection.json
-- readme.md

docs/_data/jekyllconf-talks.yml

@@ -1,167 +0,0 @@
-- speaker: Ben Balter
-  twitter_handle: BenBalter
-  youtube_id: Z-37y1qaoxc
-  topic: GitHub Pages behind the scenes
-  year: 2015
-
-- speaker: Brandon Mathis
-  twitter_handle: imathis
-  youtube_id: KS6e4XxY2H4
-  topic: What the heck is Octopress and why should I care?
-  year: 2015
-
-- speaker: Brian Rinaldi
-  twitter_handle: remotesynth
-  youtube_id: vT7DhK5zbv0
-  topic: Comparing Jekyll with the Competition
-  year: 2015
-
-- speaker: Kyle Rush
-  twitter_handle: kylerush
-  youtube_id: ia8vsuiXiL0
-  topic: Meet the Obama Campaign's $250 Million Fundraising Platform
-  year: 2015
-
-- speaker: Michael Jovel
-  twitter_handle: mjovel
-  youtube_id: 8zSHG6XU_xY
-  topic: Building Living Style Guides with Jekyll
-  year: 2015
-
-- speaker: Mike Neumegen
-  twitter_handle: mikeneumegen
-  youtube_id: NuChR_YdjrI
-  topic: A CMS for Jekyll
-  year: 2015
-
-- speaker: Parker Moore
-  twitter_handle: parkr
-  youtube_id: y2SbOIQ5nSA
-  topic: Jekyll 3 and Beyond
-  year: 2015
-
-- speaker: Tom Preston-Werner
-  twitter_handle: mojombo
-  youtube_id: BMve1OCKj6M
-  topic: Some crazy ideas I have for the future of static sites
-  year: 2015
-
-- speaker: Allison Zadrozny
-  twitter_handle: allizad
-  youtube_id: Rsc0Mmp1qc8
-  topic: Elasticsearch for Jekyll
-  year: 2016
-
-- speaker: Amy Johnston
-  twitter_handle: amybeukenex
-  youtube_id: HR12JiUI2Zc
-  topic: Jekyll for Technical Documentation
-  year: 2016
-
-- speaker: Bud Parr
-  twitter_handle: budparr
-  youtube_id: A1nTuNjoNbg
-  topic: Real World Content Strategy with Jekyll
-  year: 2016
-
-- speaker: George Phillips
-  twitter_handle: gphillips_nz
-  youtube_id: skb_XWABEDc
-  topic: Building client-editable Jekyll sites
-  year: 2016
-
-- speaker: Ire Aderinokun
-  twitter_handle: ireaderinokun
-  youtube_id: PRKV5IGKF2c
-  topic: Using Jekyll for Rapid CSS Testing
-  year: 2016
-
-- speaker: Jon Chan
-  twitter_handle: JonHMChan
-  youtube_id: vDeKPs6xpOM
-  topic: Stack Overflow on Jekyll
-  year: 2016
-
-- speaker: Julio Faerman
-  twitter_handle: jmfaerman
-  youtube_id: SOMonG8Iqak
-  topic: Jekyll on AWS
-  year: 2016
-
-- speaker: Katy DeCorah
-  twitter_handle: katydecorah
-  youtube_id: s84wFRD8vfE
-  topic: Unconventional use cases for Jekyll
-  year: 2016
-
-- speaker: David Darnes
-  twitter_handle: DavidDarnes
-  youtube_id: Y4qwpN40Dvg
-  topic: Doing a lot with a little
-  year: 2016
-
-- speaker: Ronan Berder
-  twitter_handle: hunvreus
-  youtube_id: TteAQq25_Ns
-  topic: Designing fast websites with Jekyll
-  year: 2016
-
-- speaker: David Von Lehman
-  twitter_handle: davidvlsea
-  youtube_id: wMlPlKCZfEk
-  topic: Continuous deployment of Jekyll sites powered by Docker
-  year: 2016
-
-- speaker: David Jones
-  twitter_handle: d_jones
-  youtube_id: 4XxYQ7efk0E
-  topic: Building our agency site with Jekyll
-  year: 2016
-
-- speaker: Scott Hewitt
-  twitter_handle: scotthewitt
-  youtube_id: qSd3pXQaPsE
-  topic: Jekyll For Every Case
-  year: 2016
-
-- speaker: Tim Carry
-  twitter_handle: pixelastic
-  youtube_id: ivMML1J4ABY
-  topic: Algolia search on Jekyll sites
-  year: 2016
-
-- speaker: Nils Borchers
-  twitter_handle: nilsborchers
-  youtube_id: DtNMjuv6Rbo
-  topic: Building a living brand guide with Jekyll and Hologram
-  year: 2016
-
-- speaker: Mike Neumegen
-  twitter_handle: mikeneumegen
-  youtube_id: rJ5EhVmTR7I
-  topic: Learning resources for the Jekyll community
-  year: 2016
-
-- speaker: Oliver Pattison
-  twitter_handle: olivermakes
-  youtube_id: BIf6oNpGl74
-  topic: Responsive srcset images with imgix
-  year: 2016
-
-- speaker: Michael Lee
-  twitter_handle: michaelsoolee
-  youtube_id: F4bJRLEvXIc
-  topic: Jekyll, Your Website's Baseplate
-  year: 2016
-
-- speaker: Paul Webb
-  twitter_handle: NetOpWibby
-  youtube_id: BRB5DgAE5nM
-  topic: Deploy Jekyll Like A Boss
-  year: 2016
-
-- speaker: Tom Johnson
-  twitter_handle: tomjohnson
-  youtube_id: nq1AUB72GCQ
-  topic: Overcoming challenges in using Jekyll for documentation projects
-  year: 2016

docs/_data/sponsors.yml

@@ -1,15 +0,0 @@
-- name: Forestry.io
-  image: /img/forestry-logo.png
-  url: https://forestry.io
-  width: 140
-  height: 30
-- name: CloudCannon
-  image: /img/cloudcannon-logo.png
-  url: https://cloudcannon.com
-  width: 75
-  height: 30
-- name: Siteleaf
-  image: /img/siteleaf-logo.png
-  url: https://siteleaf.com
-  width: 40
-  height: 50

docs/_data/tutorials.yml

@@ -1,13 +0,0 @@
-- title: Tutorials
-  tutorials:
-  - home
-  - video-walkthroughs
-  - navigation
-  - orderofinterpretation
-  - custom-404-page
-  - convert-site-to-jekyll
-  - using-jekyll-with-bundler
-
-#- title: Another section
-#  tutorials:
-#  - sample

docs/_docs/continuous-integration/buddyworks.md

@@ -1,62 +0,0 @@
----
-title: "Buddy"
----
-
-[Buddy][buddy-homepage] is a [Docker][docker-homepage]-based CI server that you can set up in 15-20 minutes to build, test, and deploy your Jekyll websites. It supports [GitHub][github-homepage], [Bitbucket][bitbucket-homepage], and [GitLab][gitlab-homepage] 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.
-
-[buddy-homepage]: https://buddy.works
-[docker-homepage]: https://www.docker.com/
-[github-homepage]: https://github.com
-[bitbucket-homepage]: https://bitbucket.org/
-[gitlab-homepage]: https://gitlab.com
-
-## 1. Getting started
-
-1. Log in at [https://buddy.works][buddy-homepage] with your GitHub/Bitbucket account or email
-2. Choose your Git provider and select or push your Jekyll Project
-3. Create a new pipeline and set the trigger mode to 'On every push'
-4. Add and configure the Jekyll action and save the pipeline
-
-## 2. How it works
-
-Whenever you make a push to the selected branch, the Jekyll action runs `jekyll build` in an isolated [Jekyll Docker image][jekyll-docker-image]. The output is generated to the `/filesystem` directory, and can be further deployed to FTP/SFTP and IaaS services. You can add your own commands, install additional packages, attach services, and run Selenium tests, as well as add other actions down the pipeline, eg. a Slack notification or an SSH script that will restart your server.
-
-![Jekyll Build](https://buddy.works/data/blog/_images/buddyworks-jekyll-small.png)
-
-[jekyll-docker-image]: https://hub.docker.com/r/jekyll/jekyll/
-
-## 3. Using YAML for configuration
-
-If you prefer configuration as code over GUI, you can generate a `buddy.yml` that will create a pipeline with the Jekyll action once you push it to the target branch:
-
-```yaml
-- pipeline: "Build and Deploy Jekyll site"
-  trigger_mode: "ON_EVERY_PUSH"
-  ref_name: "master"
-  actions:
-  - action: "Execute: jekyll build"
-    type: "BUILD"
-    docker_image_name: "jekyll/jekyll"
-    docker_image_tag: "latest"
-    execute_commands:
-    - "chown jekyll:jekyll $WORKING_DIR"
-    - "jekyll build"
-```
-
-## 4. Setting up on-premises server
-
-The self-hosted version of Buddy can be installed on any type of server supporting Docker, including [Linux][bw-linux], [Mac][bw-mac], [AWS EC2][bw-aws-ec2], [DigitalOcean][bw-digitalocean], and [Microsoft Azure][bw-azure].
-
-[bw-linux]: https://buddy.works/knowledge/standalone/installation-linux
-[bw-mac]: https://buddy.works/knowledge/standalone/installation-mac-osx
-[bw-aws-ec2]: https://buddy.works/knowledge/standalone/installation-amazon-ec2
-[bw-digitalocean]: https://buddy.works/knowledge/standalone/installation-digitalocean
-[bw-azure]: https://buddy.works/knowledge/standalone/installation-azure
-
-## 5. Questions?
-
-This entire guide is open-source. Go ahead and [edit it][jekyll-docs-ci-buddy] if you want to expand it or have a fix or [ask for help][jekyll-help] if you run into trouble and need assistance. Buddy also has an [online community][buddy-forum] for help.
-
-[jekyll-docs-ci-buddy]: https://github.com/jekyll/jekyll/edit/master/docs/_docs/continuous-integration/buddyworks.md
-[jekyll-help]: https://jekyllrb.com/help/
-[buddy-forum]: http://forum.buddy.works/

docs/_docs/continuous-integration/circleci.md

@@ -1,161 +0,0 @@
----
-title: "CircleCI"
----
-
-Building, testing, and deploying your Jekyll-generated website can quickly be done with [CircleCI][0], a continuous integration & delivery tool. CircleCI supports [GitHub][1] and [Bitbucket][2], and you can get started for free using an open-source or private repository.
-
-[0]: https://circleci.com/
-[1]: https://github.com/
-[2]: https://bitbucket.org/
-
-## 1. Follow Your Project on CircleCI
-
-To start building your project on CircleCI, all you need to do is 'follow' your project from CircleCI's website:
-
-1. Visit the 'Add Projects' page: <https://circleci.com/add-projects>
-1. From the GitHub or Bitbucket tab on the left, choose a user or organization.
-1. Find your project in the list and click 'Build project' on the right.
-1. The first build will start on its own. You can start telling CircleCI how to build your project by creating a [circle.yml][3] file in the root of your repository.
-
-[3]: https://circleci.com/docs/configuration/
-
-## 2. Dependencies
-
-The easiest way to manage dependencies for a Jekyll project (with or without CircleCI) is via a [Gemfile][4]. You'd want to have Jekyll, any Jekyll plugins, [HTML Proofer](#html-proofer), and any other gems that you are using in the `Gemfile`. Don't forget to version `Gemfile.lock` as well. Here's an example `Gemfile`:
-
-[4]: http://bundler.io/gemfile.html
-
-```ruby
-source 'https://rubygems.org'
-
-ruby '2.4.0'
-
-gem 'jekyll'
-gem 'html-proofer'
-```
-
-CircleCI detects when `Gemfile` is present is will automatically run `bundle install` for you in the `dependencies` phase.
-
-## 3. Testing
-
-The most basic test that can be run is simply seeing if `jekyll build` 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 `dependencies` phase.
-
-```yaml
-dependencies:
-  post:
-    - bundle exec jekyll build
-```
-
-### HTML Proofer
-
-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 [HTML Proofer][5] is popular amongst Jekyll users. We'll run it in the `test` phase with a few preferred flags. Check out the `html-proofer` [README][6] for all available flags, or run `htmlproofer --help` locally.
-
-[5]: https://github.com/gjtorikian/html-proofer
-[6]: https://github.com/gjtorikian/html-proofer/blob/master/README.md#configuration
-
-```yaml
-test:
-  post:
-    - bundle exec htmlproofer ./_site --check-html --disable-external
-```
-
-## Complete Example circle.yml File
-
-When you put it all together, here's an example of what that `circle.yml` file could look like in v1:
-
-```yaml
-machine:
-  environment:
-    NOKOGIRI_USE_SYSTEM_LIBRARIES: true # speeds up installation of html-proofer
-
-dependencies:
-  post:
-    - bundle exec jekyll build
-
-test:
-  post:
-    - bundle exec htmlproofer ./_site --allow-hash-href --check-favicon --check-html --disable-external
-
-deployment:
-  prod:
-    branch: master
-    commands:
-      - rsync -va --delete ./_site username@my-website:/var/html
-```
-
-for CircleCI v2, a Docker-based system which new projects will follow, set the `S3_BUCKET_NAME` environment variable (an example of the required config file is shown below).
-
-```yaml
-defaults: &defaults
-  working_directory: ~/repo
-version: 2
-jobs:
-  build:
-    <<: *defaults
-    docker:
-      - image: circleci/ruby:2.5
-    environment:
-      BUNDLE_PATH: ~/repo/vendor/bundle
-    steps:
-      - checkout
-      - restore_cache:
-          keys:
-            - rubygems-v1-{% raw %}{{ checksum "Gemfile.lock" }}{% endraw %}
-            - rubygems-v1-fallback
-      - run:
-          name: Bundle Install
-          command: bundle check || bundle install
-      - run:
-          name: HTMLProofer tests
-          command: |
-            bundle exec htmlproofer ./_site \
-              --allow-hash-href \
-              --check-favicon  \
-              --check-html \
-              --disable-external
-      - save_cache:
-          key: rubygems-v1-{% raw %}{{ checksum "Gemfile.lock" }}{% endraw %}
-          paths:
-            - vendor/bundle
-      - run:
-          name: Jekyll build
-          command: bundle exec jekyll build
-      - persist_to_workspace:
-          root: ./
-          paths:
-            - _site
-  deploy:
-    <<: *defaults
-    docker:
-      - image: circleci/python:3.6.3
-    environment:
-      S3_BUCKET_NAME: <<YOUR BUCKET NAME HERE>>
-    steps:
-      - attach_workspace:
-          at: ./
-      - run:
-          name: Install AWS CLI
-          command: pip install awscli --upgrade --user
-      - run:
-          name: Upload to s3
-          command: ~/.local/bin/aws s3 sync ./_site s3://$S3_BUCKET_NAME/ --delete --acl public-read
-workflows:
-  version: 2
-  test-deploy:
-    jobs:
-      - build
-      - deploy:
-          requires:
-            - build
-          filters:
-            branches:
-              only: master
-```
-
-## Questions?
-
-This entire guide is open-source. Go ahead and [edit it][7] if you have a fix or [ask for help][8] if you run into trouble and need some help. CircleCI also has an [online community][9] for help.
-
-[7]: https://github.com/jekyll/jekyll/edit/master/docs/_docs/continuous-integration/circleci.md
-[8]: https://jekyllrb.com/help/
-[9]: https://discuss.circleci.com

docs/_docs/continuous-integration/index.md

@@ -1,10 +0,0 @@
----
-title: Continuous Integration
-permalink: /docs/continuous-integration/
----
-
-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:
-
-* [Travis CI](travis-ci)
-* [CircleCI](circleci)
-* [Buddy](buddyworks)

docs/_docs/contributing.md

@@ -1,155 +0,0 @@
----
-title: Contributing
-permalink: "/docs/contributing/"
-note: This file is autogenerated. Edit /.github/CONTRIBUTING.markdown instead.
----
-
-Hi there! Interested in contributing to Jekyll? We'd love your help. Jekyll is an open source project, built one contribution at a time by users like you.
-
-## Where to get help or report a problem
-
-See [the support guidelines](https://jekyllrb.com/docs/support/)
-
-## Ways to contribute
-
-Whether you're a developer, a designer, or just a Jekyll devotee, there are lots of ways to contribute. Here's a few ideas:
-
-* [Install Jekyll on your computer](https://jekyllrb.com/docs/installation/) and kick the tires. Does it work? Does it do what you'd expect? If not, [open an issue](https://github.com/jekyll/jekyll/issues/new) and let us know.
-* Comment on some of the project's [open issues](https://github.com/jekyll/jekyll/issues). Have you experienced the same problem? Know a work around? Do you have a suggestion for how the feature could be better?
-* Read through [the documentation](https://jekyllrb.com/docs/home/), and click the "improve this page" button, any time you see something confusing, or have a suggestion for something that could be improved.
-* Browse through [the Jekyll discussion forum](https://talk.jekyllrb.com/), and lend a hand answering questions. There's a good chance you've already experienced what another user is experiencing.
-* Find [an open issue](https://github.com/jekyll/jekyll/issues) (especially [those labeled `help-wanted`](https://github.com/jekyll/jekyll/issues?q=is%3Aopen+is%3Aissue+label%3Ahelp-wanted)), and submit a proposed fix. If it's your first pull request, we promise we won't bite, and are glad to answer any questions.
-* Help evaluate [open pull requests](https://github.com/jekyll/jekyll/pulls), by testing the changes locally and reviewing what's proposed.
-
-## Submitting a pull request
-
-### Pull requests generally
-
-* The smaller the proposed change, the better. If you'd like to propose two unrelated changes, submit two pull requests.
-
-* The more information, the better. Make judicious use of the pull request body. Describe what changes were made, why you made them, and what impact they will have for users.
-
-* Pull requests are easy and fun. If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/).
-
-* If you're submitting a code contribution, be sure to read the [code contributions](#code-contributions) section below.
-
-### Submitting a pull request via github.com
-
-Many small changes can be made entirely through the github.com web interface.
-
-1. Navigate to the file within [`jekyll/jekyll`](https://github.com/jekyll/jekyll) that you'd like to edit.
-2. Click the pencil icon in the top right corner to edit the file
-3. Make your proposed changes
-4. Click "Propose file change"
-5. Click "Create pull request"
-6. Add a descriptive title and detailed description for your proposed change. The more information the better.
-7. Click "Create pull request"
-
-That's it! You'll be automatically subscribed to receive updates as others review your proposed change and provide feedback.
-
-### Submitting a pull request via Git command line
-
-1. Fork the project by clicking "Fork" in the top right corner of [`jekyll/jekyll`](https://github.com/jekyll/jekyll).
-2. Clone the repository locally `git clone https://github.com/<you-username>/jekyll`.
-3. Create a new, descriptively named branch to contain your change ( `git checkout -b my-awesome-feature` ).
-4. Hack away, add tests. Not necessarily in that order.
-5. Make sure everything still passes by running `script/cibuild` (see [the tests section](#running-tests-locally) below)
-6. Push the branch up ( `git push origin my-awesome-feature` ).
-7. Create a pull request by visiting `https://github.com/<your-username>/jekyll` and following the instructions at the top of the screen.
-
-## Proposing updates to the documentation
-
-We want the Jekyll documentation to be the best it can be. We've open-sourced our docs and we welcome any pull requests if you find it lacking.
-
-### How to submit changes
-
-You can find the documentation for jekyllrb.com in the [docs](https://github.com/jekyll/jekyll/tree/master/docs) directory. See the section above, [submitting a pull request](#submitting-a-pull-request) for information on how to propose a change.
-
-One gotcha, all pull requests should be directed at the `master` branch (the default branch).
-
-### Updating FontAwesome iconset for jekyllrb.com
-
-We use a custom version of FontAwesome which contains just the icons we use.
-
-If you ever need to update our documentation with an icon that is not already available in our custom iconset, you'll have to regenerate the iconset using Icomoon's Generator:
-
-1. Go to <https://icomoon.io/app/>.
-2. Click `Import Icons` on the top-horizontal-bar and upload the existing `<jekyll>/docs/icomoon-selection.json`.
-3. Click `Add Icons from Library..` further down on the page, and add 'Font Awesome'.
-4. Select the required icon(s) from the Library (make sure its the 'FontAwesome' library instead of 'IcoMoon-Free' library).
-5. Click `Generate Font` on the bottom-horizontal-bar.
-6. Inspect the included icons and proceed by clicking `Download`.
-7. Extract the font files and adapt the CSS to the paths we use in Jekyll:
-  - Copy the entire `fonts` directory over and overwrite existing ones at `<jekyll>/docs/`.
-  - Copy the contents of `selection.json` and overwrite existing content inside `<jekyll>/docs/icomoon-selection.json`.
-  - Copy the entire `@font-face {}` declaration and only the **new-icon(s)' css declarations** further below, to update the
-  `<jekyll>/docs/_sass/_font-awesome.scss` sass partial.
-  - Fix paths in the `@font-face {}` declaration by adding `../` before `fonts/FontAwesome.*` like so:
-  `('../fonts/Fontawesome.woff?9h6hxj')`.
-
-### Adding plugins
-
-If you want to add your plugin to the [list of plugins](https://jekyllrb.com/docs/plugins/#available-plugins), please submit a pull request modifying the [plugins page source file](https://github.com/jekyll/jekyll/blob/master/docs/_docs/plugins.md) by adding a link to your plugin under the proper subheading depending upon its type.
-
-## Code Contributions
-
-Interesting in submitting a pull request? Awesome. Read on. There's a few common gotchas that we'd love to help you avoid.
-
-### Tests and documentation
-
-Any time you propose a code change, you should also include updates to the documentation and tests within the same pull request.
-
-#### Documentation
-
-If your contribution changes any Jekyll behavior, make sure to update the documentation. Documentation lives in the `docs/_docs` folder (spoiler alert: it's a Jekyll site!). If the docs are missing information, please feel free to add it in. Great docs make a great project. Include changes to the documentation within your pull request, and once merged, `jekyllrb.com` will be updated.
-
-#### Tests
-
-* If you're creating a small fix or patch to an existing feature, a simple test is more than enough. You can usually copy/paste from an existing example in the `tests` folder, but if you need you can find out about our tests suites [Shoulda](https://github.com/thoughtbot/shoulda/tree/master) and [RSpec-Mocks](https://github.com/rspec/rspec-mocks).
-
-* If it's a brand new feature, create a new [Cucumber](https://github.com/cucumber/cucumber/) feature, reusing existing steps where appropriate.
-
-### Code contributions generally
-
-* Jekyll uses the [Rubocop](https://github.com/bbatsov/rubocop) static analyzer to ensure that contributions follow the [GitHub Ruby Styleguide](https://github.com/styleguide/ruby). Please check your code using `script/fmt` and resolve any errors before pushing your branch.
-
-* Don't bump the Gem version in your pull request (if you don't know what that means, you probably didn't).
-
-* You can use the command `script/console` to start a REPL to explore the result of
-Jekyll's methods. It also provides you with helpful methods to quickly create a
-site or configuration. [Feel free to check it out!](https://github.com/jekyll/jekyll/blob/master/script/console)
-
-## Running tests locally
-
-### Test Dependencies
-
-To run the test suite and build the gem you'll need to install Jekyll's dependencies by running the following command:
-
-```sh
-script/bootstrap
-```
-
-Before you make any changes, run the tests and make sure that they pass (to confirm your environment is configured properly):
-
-```sh
-script/cibuild
-```
-
-If you are only updating a file in `test/`, you can use the command:
-
-```sh
-script/test test/blah_test.rb
-```
-
-If you are only updating a `.feature` file, you can use the command:
-
-```sh
-script/cucumber features/blah.feature
-```
-
-Both `script/test` and `script/cucumber` can be run without arguments to
-run its entire respective suite.
-
-## A thank you
-
-Thanks! Hacking on Jekyll should be fun. If you find any of this hard to figure out, let us know so we can improve our process or documentation!

docs/_docs/github-pages.md

@@ -1,140 +0,0 @@
----
-title: GitHub Pages
-permalink: /docs/github-pages/
----
-
-[GitHub Pages](https://pages.github.com) are public web pages for users,
-organizations, and repositories, that are freely hosted on GitHub's `github.io`
-domain or on a custom domain name of your choice. GitHub Pages are powered by
-Jekyll behind the scenes, so they're a great way to host your Jekyll-powered
-website for free.
-
-Your site is automatically generated by GitHub Pages when you push your source
-files. Note that GitHub Pages works equally well for regular HTML content,
-simply because Jekyll treats files without YAML front matter as static assets.
-So if you only need to push generated HTML, you're good to go without any
-further setup.
-
-Never built a website with GitHub Pages before? [See this marvelous guide by
-Jonathan McGlone](http://jmcglone.com/guides/github-pages/) to get you up and
-running. This guide will teach you what you need to know about Git, GitHub, and
-Jekyll to create your very own website on GitHub Pages.
-
-##  The github-pages gem
-
-Our friends at GitHub have provided the
-[github-pages](https://github.com/github/pages-gem) gem which is used to manage
-[Jekyll and its dependencies on GitHub Pages](https://pages.github.com/versions/).
-Using it in your projects means that when you deploy your site to GitHub Pages,
-you will not be caught by unexpected differences between various versions of the
-gems.
-
-Note that GitHub Pages runs in `safe` mode and only allows [a set of whitelisted
-plugins](https://help.github.com/articles/configuring-jekyll-plugins/#default-plugins).
-
-To use the currently-deployed version of the gem in your project, add the
-following to your `Gemfile`:
-
-```ruby
-source "https://rubygems.org"
-
-gem "github-pages", group: :jekyll_plugins
-```
-
-Be sure to run `bundle update` often.
-
-<div class="note">
-  <h5>GitHub Pages Documentation, Help, and Support</h5>
-  <p>
-    For more information about what you can do with GitHub Pages, as well as for
-    troubleshooting guides, you should check out
-    <a href="https://help.github.com/categories/github-pages-basics/">GitHub’s Pages Help section</a>.
-    If all else fails, you should contact <a href="https://github.com/contact">GitHub Support</a>.
-  </p>
-</div>
-
-### Project Page URL Structure
-
-Sometimes it's nice to preview your Jekyll site before you push your `gh-pages`
-branch to GitHub. However, the subdirectory-like URL structure GitHub uses for
-Project Pages complicates the proper resolution of URLs. In order to assure your
-site builds properly, use the handy [URL filters](../templates/#filters):
-
-{% raw %}
-```liquid
-<!-- For styles with static names... -->
-<link href="{{ "/assets/css/style.css" | relative_url }}" rel="stylesheet">
-<!-- For documents/pages whose URLs can change... -->
-[{{ page.title }}]("{{ page.url | relative_url }}")
-```
-{% endraw %}
-
-This way you can preview your site locally from the site root on localhost,
-but when GitHub generates your pages from the `gh-pages` branch all the URLs
-will resolve properly.
-
-## Deploying Jekyll to GitHub Pages
-
-GitHub Pages work by looking at certain branches of repositories on GitHub.
-There are two basic types available: [user/organization and project pages](https://help.github.com/articles/user-organization-and-project-pages/).
-The way to deploy these two types of sites are nearly identical, except for a
-few minor details.
-
-### User and Organization Pages
-
-User and organization pages live in a special GitHub repository dedicated to
-only the GitHub Pages files. This repository must be named after the account
-name. For example, [@mojombo’s user page repository](https://github.com/mojombo/mojombo.github.io) has the name
-`mojombo.github.io`.
-
-Content from the `master` branch of your repository will be used to build and
-publish the GitHub Pages site, so make sure your Jekyll site is stored there.
-
-<div class="note info">
-  <h5>Custom domains do not affect repository names</h5>
-  <p>
-    GitHub Pages are initially configured to live under the
-    <code>username.github.io</code> subdomain, which is why repositories must
-    be named this way <strong>even if a custom domain is being used</strong>.
-  </p>
-</div>
-
-### Project Pages
-
-Unlike user and organization Pages, Project Pages are kept in the same
-repository as the project they are for, except that the website content is
-stored in a specially named `gh-pages` branch or in a `docs` folder on the
-`master` branch. The content will be rendered using Jekyll, and the output
-will become available under a subpath of your user pages subdomain, such as
-`username.github.io/project` (unless a custom domain is specified).
-
-The Jekyll project repository itself is a perfect example of this branch
-structure—the [master branch]({{ site.repository }}) contains the
-actual software project for Jekyll, and the Jekyll website that you’re
-looking at right now is contained in the [docs
-folder]({{ site.repository }}/tree/master/docs) of the same repository.
-
-Please refer to GitHub official documentation on
-[user, organization and project pages](https://help.github.com/articles/user-organization-and-project-pages/)
-to see more detailed examples.
-
-<div class="note warning">
-  <h5>Source files must be in the root directory</h5>
-  <p>
-    GitHub Pages <a href="https://help.github.com/articles/troubleshooting-github-pages-build-failures#source-setting">overrides</a>
-    the <a href="/docs/configuration/#global-configuration">“Site Source”</a>
-    configuration value, so if you locate your files anywhere other than the
-    root directory, your site may not build correctly.
-  </p>
-</div>
-
-<div class="note info">
-  <h5>Installing the <code>github-pages</code> gem on Windows</h5>
-
-  <p>
-    While Windows is not officially supported, it is possible
-    to install the <code>github-pages</code> gem on Windows.
-    Special instructions can be found on our
-    <a href="../windows/#installation">Windows-specific docs page</a>.
-  </p>
-</div>

docs/_docs/includes.md

@@ -1,192 +0,0 @@
----
-title: Includes
-permalink: /docs/includes/
----
-
-The `include` tag allows you to include the content from another file stored in the `_includes` folder:
-
-{% raw %}
-```liquid
-{% include footer.html %}
-```
-{% endraw %}
-
-Jekyll will look for the referenced file (in this case, `footer.html`) in the `_includes` directory at the root of your source directory and insert its contents.
-
-### Including files relative to another file
-
-You can choose to include file fragments relative to the current file by using the `include_relative` tag:
-
-{% raw %}
-```liquid
-{% include_relative somedir/footer.html %}
-```
-{% endraw %}
-
-You won't need to place your included content within the `_includes` directory. Instead,
-the inclusion is specifically relative to the file where the tag is being used. For example,
-if `_posts/2014-09-03-my-file.markdown` uses the `include_relative` tag, the included file
-must be within the `_posts` directory or one of its subdirectories.
-
-Note that you cannot use the `../` syntax to specify an include location that refers to a higher-level directory.
-
-All the other capabilities of the `include` tag are available to the `include_relative` tag,
-such as variables.
-
-### Using variables names for the include file
-
-The name of the file you want to embed can be specified as a variable instead of an actual file name. For example, suppose you defined a variable in your page's front matter like this:
-
-```yaml
----
-title: My page
-my_variable: footer_company_a.html
----
-```
-
-You could then reference that variable in your include:
-
-{% raw %}
-```liquid
-{% include {{ page.my_variable }} %}
-```
-{% endraw %}
-
-In this example, the include would insert the file `footer_company_a.html` from the `_includes/footer_company_a.html` directory.
-
-### Passing parameters to includes
-
-You can also pass parameters to an include. For example, suppose you have a file called `note.html` in your `_includes` folder that contains this formatting:
-
-{% raw %}
-```liquid
-<div markdown="span" class="alert alert-info" role="alert">
-<i class="fa fa-info-circle"></i> <b>Note:</b>
-{{ include.content }}
-</div>
-```
-{% endraw %}
-
-The `{% raw %}{{ include.content }}{% endraw %}` is a parameter that gets populated when you call the include and specify a value for that parameter, like this:
-
-{% raw %}
-```liquid
-{% include note.html content="This is my sample note." %}
-```
-{% endraw %}
-
-The value of `content` (which is `This is my sample note`) will be inserted into the {% raw %}`{{ include.content }}`{% endraw %} parameter.
-
-Passing parameters to includes is especially helpful when you want to hide away complex formatting from your Markdown content.
-
-For example, suppose you have a special image syntax with complex formatting, and you don't want your authors to remember the complex formatting. As a result, you decide to simplify the formatting by using an include with parameters. Here's an example of the special image syntax you might want to populate with an include:
-
-```html
-<figure>
-   <a href="http://jekyllrb.com">
-   <img src="logo.png" style="max-width: 200px;"
-      alt="Jekyll logo" />
-   </a>
-   <figcaption>This is the Jekyll logo</figcaption>
-</figure>
-```
-
-You could templatize this content in your include and make each value available as a parameter, like this:
-
-{% raw %}
-```liquid
-<figure>
-   <a href="{{ include.url }}">
-   <img src="{{ include.file }}" style="max-width: {{ include.max-width }};"
-      alt="{{ include.alt }}"/>
-   </a>
-   <figcaption>{{ include.caption }}</figcaption>
-</figure>
-```
-{% endraw %}
-
-This include contains 5 parameters:
-
-* `url`
-* `max-width`
-* `file`
-* `alt`
-* `caption`
-
-Here's an example that passes all the parameters to this include (the include file is named `image.html`):
-
-{% raw %}
-```liquid
-{% include image.html url="http://jekyllrb.com"
-max-width="200px" file="logo.png" alt="Jekyll logo"
-caption="This is the Jekyll logo." %}
-```
-{% endraw %}
-
-The result is the original HTML code shown earlier.
-
-To safeguard situations where users don't supply a value for the parameter, you can use [Liquid's default filter](https://shopify.github.io/liquid/filters/default/).
-
-Overall, you can create includes that act as templates for a variety of uses &mdash; inserting audio or video clips, alerts, special formatting, and more. However, note that you should avoid using too many includes, as this will slow down the build time of your site. For example, don't use includes every time you insert an image. (The above technique shows a use case for special images.)
-
-### Passing parameter variables to includes
-
-Suppose the parameter you want to pass to the include is a variable rather than a string. For example, you might be using {% raw %}`{{ site.product_name }}`{% endraw %} to refer to every instance of your product rather than the actual hard-coded name. (In this case, your `_config.yml` file would have a key called `product_name` with a value of your product's name.)
-
-The string you pass to your include parameter can't contain curly braces. For example, you can't pass a parameter that contains this: {% raw %}`"The latest version of {{ site.product_name }} is now available."`{% endraw %}
-
-If you want to include this variable in your parameter that you pass to an include, you need to store the entire parameter as a variable before passing it to the include. You can use `capture` tags to create the variable:
-
-{% raw %}
-```liquid
-{% capture download_note %}
-The latest version of {{ site.product_name }} is now available.
-{% endcapture %}
-```
-{% endraw %}
-
-Then pass this captured variable into the parameter for the include. Omit the quotation marks around the parameter content because it's no longer a string (it's a variable):
-
-{% raw %}
-```liquid
-{% include note.html content=download_note %}
-```
-{% endraw %}
-
-### Passing references to YAML files as parameter values
-
-Instead of passing string variables to the include, you can pass a reference to a YAML data file stored in the `_data` folder.
-
-Here's an example. In the `_data` folder, suppose you have a YAML file called `profiles.yml`. Its content looks like this:
-
-```yaml
-- name: John Doe
-  login_age: old
-  image: johndoe.jpg
-
-- name: Jane Doe
-  login_age: new
-  image: janedoe.jpg
-```
-
-In the `_includes` folder, assume you have a file called `spotlight.html` with this code:
-
-{% raw %}
-```liquid
-{% for person in include.participants %}
-{% if person.login_age == "new" %}
-{{ person.name }}
-{% endif %}
-{% endfor %}
-```
-{% endraw %}
-
-Now when you insert the `spotlight.html` include file, you can submit the YAML file as a parameter:
-
-{% raw %}
-```liquid
-{% include spotlight.html participants=site.data.profiles %}
-```
-{% endraw %}
-
-In this instance, `site.data.profiles` gets inserted in place of {% raw %}`include.participants`{% endraw %} in the include file, and the Liquid logic processes. The result will be `Jane Doe`.

docs/_docs/index.md

@@ -1,41 +0,0 @@
----
-title: Welcome
-permalink: /docs/home/
-redirect_from: /docs/index.html
----
-
-This site aims to be a comprehensive guide to Jekyll. We’ll cover topics such as getting your site up and running, creating and managing content, customizing your build, and deploying.
-
-## What is Jekyll, exactly?
-
-Jekyll is a simple, blog-aware, static site generator.
-
-You create your content as text files ([Markdown](https://daringfireball.net/projects/markdown/)), and organize them into folders. Then, you build the shell of your site using [Liquid](https://shopify.github.io/liquid/)-enhanced HTML templates. Jekyll automatically stitches the content and templates together, generating a website made entirely of static assets, suitable for uploading to any server.
-
-Jekyll happens to be the engine behind [GitHub Pages](https://pages.github.com), so you can host your project’s Jekyll page/blog/website on GitHub’s servers **for free**.
-
-## Navigating the Guide
-
-Throughout this guide, you'll see these special sections that help you get the most out of Jekyll:
-
-<div class="note">
-  <h5>ProTips™</h5>
-  <p>Tips and tricks that'll make you a Jekyll wizard!</p>
-</div>
-
-<div class="note info">
-  <h5>Notes</h5>
-  <p>Extra tidbits that are sometimes necessary to understand Jekyll.</p>
-</div>
-
-<div class="note warning">
-  <h5>Warnings</h5>
-  <p>Common pitfalls to avoid.</p>
-</div>
-
-<div class="note unreleased">
-  <h5>Unreleased</h5>
-  <p>Features planned for future versions of Jekyll, but not available yet.</p>
-</div>
-
-If you find anything we haven’t covered, or would like to share a tip that others might find handy, please [file an issue]({{ site.repository }}/issues/new) and we’ll see about adding it to the guide.

docs/_docs/installation.md

@@ -1,202 +0,0 @@
----
-title: Installation
-description: Official guide to install Jekyll on macOS, GNU/Linux or Windows.
-permalink: /docs/installation/
----
-
-Jekyll is a [Ruby Gem](http://guides.rubygems.org/rubygems-basics/), and can be
-installed on most systems.
-
-- [Requirements](#requirements)
-- [Install Jekyll on macOS](#macOS)
-- [Install Jekyll on Ubuntu Linux](#ubuntu)
-- [Install Jekyll on Windows](../windows/)
-- [Upgrade Jekyll](#upgrade-jekyll)
-
-## Requirements
-
-Before you start, make sure your system has the following:
-
-- [Ruby](https://www.ruby-lang.org/en/downloads/) version 2.2.5 or above, including all development headers (ruby installation can be checked by running `ruby -v`)
-- [RubyGems](https://rubygems.org/pages/download) (which you can check by running `gem -v`)
-- [GCC](https://gcc.gnu.org/install/) and [Make](https://www.gnu.org/software/make/) (in case your system doesn't have them installed, which you can check by running `gcc -v`,`g++ -v`  and `make -v` in your system's command line interface)
-
-## Install on macOS {#macOS}
-
-We only cover macOS High Sierra 10.13 here, which comes with Ruby 2.3.3, older systems will need to [install a more recent Ruby version via Homebrew](#homebrew).
-
-First, you need to install the command-line tools to be able to compile native extensions, open a terminal and run:
-
-```sh
-xcode-select --install
-```
-
-### Set up Ruby included with the OS
-
-Check your Ruby version meet our requirements:
-
-```sh
-ruby -v
-2.3.3
-```
-
-Great, let's install Jekyll. We also need [Bundler](https://bundler.io/) to help us handle [plugins](../plugins) and [themes](../themes):
-
-```sh
-gem install bundler jekyll
-```
-
-That's it, you're ready to go, either by installing our [default minimal blog theme](https://github.com/jekyll/minima) with `jekyll new jekyll-website` or by starting from scratch:
-
-```sh
-mkdir jekyll-website
-cd jekyll-website
-
-# Create a Gemfile
-bundle init
-
-# Add Jekyll
-bundle add jekyll
-
-# Install gems
-bundle install
-```
-
-Great, from there you can now either use a [theme](../themes/) or [create your own layouts](../templates/).
-
-### Install a newer Ruby version via Homebrew {#homebrew}
-
-If you wish to install the latest version of Ruby and get faster builds, we recommend to do it via [Homebrew](https://brew.sh) a handy package manager for macOS.
-
-```sh
-/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-brew install ruby
-ruby -v
-ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
-```
-
-Yay! Now you have a shiny Ruby on your system!
-
-### Install multiple Ruby versions with rbenv {#rbenv}
-
-Developers often use [rbenv](https://github.com/rbenv/rbenv) to manage multiple Ruby versions. This can be useful if you want to run the same Ruby version used by [GitHub Pages](https://pages.github.com/versions/) or [Netlify](https://www.netlify.com/docs/#ruby) for instance.
-
-```sh
-# Install rbenv and ruby-build
-brew install rbenv
-
-# Setup rbenv integration to your shell
-rbenv init
-
-# Check your install
-curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | bash
-```
-
-Restart your terminal for changes to take effect.
-Now we can install the Ruby version of our choice, let's go with Ruby 2.5.1 here:
-
-```sh
-rbenv install 2.5.1
-rbenv global 2.5.1
-ruby -v
-ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin17]
-```
-
-That's it! Head over [rbenv command references](https://github.com/rbenv/rbenv#command-reference) to learn how to use different versions of Ruby in your projects.
-
-<div class="note info" markdown="1">
-
-##### Problems installing Jekyll?
-
-Check out the [troubleshooting](../troubleshooting/) page or
-[ask for help on our forum](https://talk.jekyllrb.com).
-
-</div>
-
-## Install on Ubuntu Linux {#ubuntu}
-
-Before we install Jekyll, we need to make sure we have all the required
-dependencies.
-
-```sh
-sudo apt-get install ruby ruby-dev build-essential
-```
-
-It is best to avoid installing Ruby Gems as the root user. Therefore, we need to
-set up a gem installation directory for your user account. The following
-commands will add environment variables to your `~/.bashrc` file to configure
-the gem installation path. Run them now:
-
-```sh
-echo '# Install Ruby Gems to ~/gems' >> ~/.bashrc
-echo 'export GEM_HOME=$HOME/gems' >> ~/.bashrc
-echo 'export PATH=$HOME/gems/bin:$PATH' >> ~/.bashrc
-source ~/.bashrc
-```
-
-Finally, install Jekyll:
-
-```sh
-gem install jekyll bundler
-```
-
-That's it! You're ready to start using Jekyll.
-
-## Upgrade Jekyll
-
-Before you start developing with Jekyll, you may want to check that you're up to date with the latest version. To find the currently installed version of Jekyll, run one of these commands:
-
-```sh
-jekyll --version
-gem list jekyll
-```
-
-You can use RubyGems to find [the current version of Jekyll](https://rubygems.org/gems/jekyll). Another way to check if you have the latest version is to run the command `gem outdated`. This will provide a list of all the gems on your system that need to be updated. If you aren't running the latest version, run this command:
-
-```sh
-bundle update jekyll
-```
-
-Alternatively, if you don't have Bundler installed run:
-
-```sh
-gem update jekyll
-```
-
-To upgrade to latest Rubygems, run:
-
-```
-gem update --system
-```
-
-Refer to our [upgrading section](../upgrading/) to upgrade from Jekyll 2.x or 1.x.
-
-## Pre-releases
-
-In order to install a pre-release, make sure you have all the requirements
-installed properly and run:
-
-```sh
-gem install jekyll --pre
-```
-
-This will install the latest pre-release. If you want a particular pre-release,
-use the `-v` switch to indicate the version you'd like to install:
-
-```sh
-gem install jekyll -v '2.0.0.alpha.1'
-```
-
-If you'd like to install a development version of Jekyll, the process is a bit
-more involved. This gives you the advantage of having the latest and greatest,
-but may be unstable.
-
-```sh
-git clone git://github.com/jekyll/jekyll.git
-cd jekyll
-script/bootstrap
-bundle exec rake build
-ls pkg/*.gem | head -n 1 | xargs gem install -l
-```
-
-Now that you’ve got everything up-to-date and installed, let’s get to work!

docs/_docs/maintaining/affinity-team-captain.md

@@ -1,28 +0,0 @@
----
-title: Affinity Team Captains
----
-
-**This guide is for affinity team captains.** These special people are **team maintainers** of one of our [affinity teams][] and help triage and evaluate the issues and contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-## Affinity teams & their captains
-
-The Jekyll project uses [affinity teams][] to help break up the work of incoming issues and pull requests from community members. We receive a sizeable number of issues and pull requests each week; the use of affinity teams helps distribute this load across a number of specialized groups instead of pushing it all onto @jekyll/core.
-
-## Responsibilities of Team Captains
-
-Each affinity team has a few captains who manage the issues and pull requests for that team. When an issue or PR is opened with a `/cc` for a given affinity team, @jekyllbot automatically assigns a random affinity team captain to the issue to triage it. They have access to add labels, reassign the issue, give LGTM's, and so forth. While they do not merge PR's today, they are still asked to review PR's for parts of the codebase under their purview.
-
-## How do I become a team captain?
-
-Just ask! Feel free to open an issue on `jekyll/jekyll` and add `/cc @jekyll/core`. We can add you. :smile:
-
-Alternatively, you can email or otherwise reach out to [@parkr](https://github.com/parkr) directly if you prefer the more private route.
-
-## Ugh, I'm tired and don't have time to be a captain anymore. What now?
-
-No sweat at all! Email [@parkr](https://github.com/parkr) and ask to be removed. Alternatively, you should be able to go to your team's page on GitHub.com (go to https://github.com/jekyll, click "Teams", click the link to your team) and change your status to either "member" or leave the team.
-
-We realize that being a captain is no easy feat so we want to make it a great experience. As always, communicate as much as you can with us about what is working, and what isn't. Thanks for dedicating some time to Jekyll! :sparkles:
-
-[affinity teams]: https://teams.jekyllrb.com/

docs/_docs/maintaining/avoiding-burnout.md

@@ -1,30 +0,0 @@
----
-title: "Avoiding Burnout"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-# 1. Use Jekyll
-
-Maintainers of Jekyll should be using it regularly. This is partly because you won't be a good maintainer unless you can put yourself in the shoes of our users, but also because you may at some point decide to stop using Jekyll, and at that point you should also decide to stop being a maintainer and find other things to work on.
-
-# 2. No Guilt About Leaving
-
-All maintainers can stop working on Jekyll at any time without any guilt or explanation (like at a job). We may still ask for your help with questions after you leave but you are under no obligation to answer them. If you create a big mess and then leave you still have no obligations but we may think less of you (or, realistically, probably just revert the problematic work). Also, you should probably take a break from Jekyll at least a few times a year.
-
-This also means contributors should be consumers. If a maintainer finds they are not using a project in the real-world, they should reconsider their involvement with the project.
-
-# 3. Prioritise Maintainers Over Users
-
-It's important to be user-focused but ultimately, as long as you follow #1 above, Jekyll's minimum number of users will be the number of maintainers. However, if Jekyll has no maintainers it will quickly become useless to all users and the project will die. As a result, no user complaint, behaviour or need takes priority over the burnout of maintainers. If users do not like the direction of the project, the easiest way to influence it is to make significant, high-quality code contributions and become a maintainer.
-
-# 4. Learn To Say No
-
-Jekyll gets a lot of feature requests, non-reproducible bug reports, usage questions and PRs we won't accept. These should be closed out as soon as we realise that they aren't going to be resolved or merged. This is kinder than deciding this after a long period of review. Our issue tracker should reflect work to be done.
-
----
-
-Thanks to https://gist.github.com/ryanflorence/124070e7c4b3839d4573 which influenced this document.
-
-Thanks to [Homebrew's "Avoiding Burnout" document](https://github.com/Homebrew/brew/blob/master/docs/Maintainers-Avoiding-Burnout.md) for providing a perfect base for this document.

docs/_docs/maintaining/becoming-a-maintainer.md

@@ -1,38 +0,0 @@
----
-title: "Becoming a Maintainer"
----
-
-**This guide is for contributors.** These special people have contributed to one or more of Jekyll's repositories, but do not yet have write access to any. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-So you want to become a maintainer of a Jekyll project? We'd love to have you! Here are some things we like to see from community members before we promote them to maintainers.
-
-## 1. Use Jekyll
-
-You want to maintain Jekyll? Use it often. Do weird things with it. Do normal things with it. Does it work? Does it have any weaknesses? Is there a gap in the product that you think should be filled?
-
-## 2. Help Triage Issues
-
-Watch the repository you're interested in. Join [an Affinity Team](https://teams.jekyllrb.com) and receive mentions regarding a particular interest area of the project. When you receive a notification for an issue that has not been triaged by a maintainer, dive in. Can you reproduce the issue? Can you determine the fix? [More tips on Triaging an Issue in our maintainer guide](../triaging-an-issue). Every maintainer loves an issue that is resolved before they get to it. :smiley:
-
-## 3. Write Documentation
-
-Good documentation means less confusion for our users and fewer issues to triage. Documentation is always in need of fixes and updates as we change the code. Read through the documentation during your normal usage of the product and submit changes as you feel they are necessary.
-
-## 4. Write Code
-
-As a maintainer, you will be reviewing pull requests which update code. You should feel comfortable with the Jekyll codebase enough to confidently review any pull request put forward. In order to become more comfortable, write some code of your own and send a pull request. A great place to start is with any issue labeled "bug" in the issue tracker. Write a test which replicates the problem and fails, then work on fixing the code such that the test passes.
-
-## 5. Review Pull Requests
-
-Start by reviewing one pull request a week. Leave detailed comments and [follow our guide for reviewing pull requests](../reviewing-a-pull-request).
-
-## 6. Ask!
-
-Open an issue describing your contributions to the project and why you wish to be a maintainer. Issues are nice because you can easily reference where you have demonstrated that you help triage issues, write code & documentation, and review pull requests. You may also email any maintainer privately if you do not feel comfortable asking in the open.
-
-We would love to expand the team and look forward to many more community members becoming maintainers!
-
-# Helping Out Elsewhere
-
-In addition to maintainers of our core and plugin code, the Jekyll team is comprised of moderators for our forums. These helpful community members take a look at the topics posted to [https://talk.jekyllrb.com](https://talk.jekyllrb.com) and ensure they are properly categorized and are acceptable under our Code of Conduct. If you would like to be a moderator, email one of the maintainers with links to where you have answered questions and a request to be added as a moderator. More help is always welcome.

docs/_docs/maintaining/index.md

@@ -1,21 +0,0 @@
----
-title: Maintaining Jekyll
-permalink: /docs/maintaining/
----
-
-**This guide is for Jekyll contributors and maintainers.** These special people contribute to one or more of Jekyll's repositories or help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-Hello! This is where we document various processes for maintaining Jekyll. Being a maintainer for any Jekyll project is a big responsibility, so we put together some helpful documentation for various tasks you might do as a maintainer.
-
-- [Affinity teams & their captains](affinity-team-captain/)
-- [Triaging an issue](triaging-an-issue/)
-- [Reviewing a pull request](reviewing-a-pull-request/)
-- [Merging a pull request](merging-a-pull-request/)
-- [Avoiding burnout](avoiding-burnout/)
-- [Special Labels](special-labels/)
-- [Releasing a new version](releasing-a-new-version/)
-
-Interested in becoming a maintainer? Here is some documentation for **contributors**:
-
-- [Becoming a maintainer](becoming-a-maintainer/)

docs/_docs/maintaining/merging-a-pull-request.md

@@ -1,55 +0,0 @@
----
-title: "Merging a Pull Request"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-## Code Review
-
-All pull requests should be subject to code review. Code review is a [foundational value](https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs-b125a13aa292) of good engineering teams. Besides providing validation of correctness, it promotes a sense of community and gives other maintainers understanding of all parts of the code base. In short, code review is crucial to a healthy open source project.
-
-**Read our guide for [Reviewing a pull request](../reviewing-a-pull-request) before merging.** Notably, the change must have tests if for code, and at least two maintainers must give it an OK.
-
-## Merging
-
-We have [a helpful little bot](https://github.com/jekyllbot) which we use to merge pull requests. We don't use the GitHub.com interface for two reasons:
-
-1. You can't modify anything on mobile (e.g. titles, labels)
-2. We like to provide a consistent paper trail in the `History.markdown` file for each release
-
-To merge a pull request, leave a comment thanking the contributor, then add the special merge request:
-
-```text
-Thank you very much for your contribution. Folks like you make this project and community strong. :heart:
-
-@jekyllbot: merge +dev
-```
-
-The merge request is made up of three things:
-
-1. `@jekyllbot:` – this is the prefix our bot looks for when processing commands
-2. `merge` – the command
-3. `+dev` – the category to which the changes belong.
-
-The categories match the headings in the `History.markdown` file, and they are:
-
-1. Major Enhancements (`+major`) – major updates or breaking changes to the code which necessitate a major version bump (v3 ~> v4)
-2. Minor Enhancements (`+minor`) – minor updates (with the labels `feature` or `enhancement`) which necessitate a minor version bump (v3.1 ~> v3.2)
-3. Bug Fixes (`+bug`) – corrections to code which do not change or add functionality, which necessitate a patch version bump (v3.1.0 ~> v3.1.1)
-4. Documentation (`+doc`) - changes to the documentation found in `docs/_docs/`
-5. Site Enhancements (`+site`) – changes to the source of [https://jekyllrb.com](https://jekyllrb.com) found in `docs/`
-6. Development Fixes (`+dev`) – changes which do not affect user-facing functionality or documentation, such as test fixes or bumping internal dependencies
-7. Forward Ports (`+port`) — bug fixes applied to a previous version of Jekyll pulled onto `master`, e.g. cherry-picked commits from `3-1-stable` to `master`
-
-Once @jekyllbot has merged the pull request, you should see three things:
-
-1. A successful merge
-2. Addition of labels for the necessary category if they aren't already applied
-3. A commit to the `History.markdown` file which adds a note about the change
-
-If you forget the category, that's just fine. You can always go back and move the line to the proper category header later. The category is always necessary for `jekyll/jekyll`, but many plugins have too few changes to necessitate changelog categories.
-
-## Rejoice
-
-You did it! Thanks for being a maintainer for one of our official Jekyll projects. Your work means the world to our thousands of users who rely on Jekyll daily. :heart:

docs/_docs/maintaining/releasing-a-new-version.md

@@ -1,89 +0,0 @@
----
-title: "Releasing a new version"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-The most important thing to understand before making a release is that there's no need to feel nervous. Most things are revertable, and even if you do publish an incomplete gem version, we can always skip that one. Don't hestitate to contact the other maintainers if you feel unsure or don't know what to do next.
-
-### Bump the version
-
-The only important place you need to manually bump the version is in `lib/jekyll/version.rb`. Adjust that, and everything else should work fine.
-
-### Update the history document
-
-Replace the first header of the history document with a version milestone. This looks like the following:
-
-```diff
--## HEAD
-+## 3.7.1 / 2018-01-25
-```
-
-Adjust the version number and the date. The `## HEAD` heading will be regenerated next time a pull request is merged.
-
-Once you've done this, update the website by running the following command:
-
-```sh
-bundle exec rake site:generate
-```
-
-This updates the website's changelog, and pushes the versions in various other places.
-
-It's recommended that you go over the `History.markdown` file manually one more time, in case there are any spelling errors or such. Feel free to fix those manually, and after you're done generating the website changelog, commit your changes.
-
-## Write a release post
-
-In case this isn't done already, you can generate a new release post using the included `rake` command:
-
-```sh
-bundle exec rake site:releases:new[3.8.0]
-```
-
-where `3.8.0` should be replaced with the new version. Then, write the post. Be sure to thank all of the collaborators and maintainers who have contributed since the last release. You can generate a log of their names using the following command:
-
-```sh
-git shortlog -sn master...v3.7.2
-```
-
-where, again `v3.7.2` is the last release. Be sure to open a pull request for your release post.
-
-### Push the version
-
-Before you do this step, make sure the following things are done:
-
-- You have permission to push a new gem version to RubyGems
-- You're logged into RubyGems on your command line
-- A release post has been prepared, and is ideally already live
-- All of the prior steps are done, committed, and pushed to `master`
-
-Really the only thing left to do is to run this command:
-
-```sh
-bundle exec rake release
-```
-
-This will automatically build the new gem, make a release commit and tag and then push the new gem to RubyGems. Don't worry about creating a GitHub release, @jekyllbot should take care of that.
-
-And then, you're done! :tada: Feel free to celebrate!
-
-If you have access to the [@jekyllrb](https://twitter.com/jekyllrb) Twitter account, you should tweet the release post from there. If not, just ask another maintainer to do it or to give you access.
-
-### Build the docs
-
-We package our documentation as a :gem: Gem for offline use.
-
-This is done with the
-[**jekyll-docs**](https://github.com/jekyll/jekyll-docs#building) repository,
-and more detailed instructions are provided there.
-
-## For non-core gems
-
-If you're not a maintainer for `jekyll/jekyll`, the procedure is much simpler in a lot of cases. Generally, the procedure still looks like this:
-
-- Bump the gem version manually, usually in `lib/<plugin_name>/version.rb`
-- Adjust the history file
-- Run `bundle exec rake release` or `script/release`, depending on which of the two exists
-- Rejoice
-
-Be sure to ask your project's maintainers if you're unsure!

docs/_docs/maintaining/reviewing-a-pull-request.md

@@ -1,46 +0,0 @@
----
-title: "Reviewing a Pull Request"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-## Respond Kindly
-
-Above all else, please review a pull request kindly. Our community can only be strong if we make it a welcoming and inclusive environment. To further promote this, the Jekyll community is governed by a [Code of Conduct](/docs/conduct/) by which all community members must abide.
-
-Use emoji liberally :heart: :tada: :sparkles: :confetti_ball: and feel free to be emotive!! Contributions keep this project moving forward and we're always happy to receive them, even if the pull request isn't ultimately merged.
-
-Mike McQuaid's post on the GitHub blog entitled ["Kindly Closing Pull Requests"](https://github.com/blog/2124-kindly-closing-pull-requests) is a great place to start. It describes various scenarios in which it would be acceptable to close a pull request for reasons other than lack of technical integrity or accuracy. Part of being kind is responding to and resolving pull requests quickly.
-
-## Respond Quickly
-
-We should be able to review all pull requests within one week. The only time initial review should take longer is if all the maintainers mysteriously took vacation during the same week. Promptness encourages frequent, high-quality contributions from community members and other maintainers.
-
-If your response requires a response on the part of the author, please add the `pending-feedback` tag. @jekyllbot will automatically remove the tag once the author of the pull request responds.
-
-## Resolve Quickly
-
-Similarly, we should aim to resolve pull requests quickly. If a pull request introduces a feature which does not fit into the core purpose or goal of the project, close it promptly with a kind explanation of why it is not acceptable.
-
-Leave detailed comments wherever possible. Provide the contributor with context around why the change you are requesting is necessary, or why the question you are asking is important to resolve. The more context we can clearly communicate to the contributor, the better able the contributor is to provide high-quality patches.
-
-You may close a pull request if more than 30 days pass without a response from the author.
-
-In some cases, review will involve many weeks of back-and-forth. As long as communication continues, this is fine. Ideally, any PR would be capable of resolution within 30 days of it being opened.
-
-## Look for Tests
-
-If this is a code change, are there tests for the updated or added behaviour? Shipping a version with bugs is inevitable, but ensuring changes are tested helps keep bugs and regressions to a minimum.
-
-## CI Must Pass
-
-It is fine to ask a contributor to investigate failures on Travis and patch them up before you begin your review. It is helpful to leave a message for the contributor indicating that the tests have failed and that no review will occur before the tests pass. If they ask for help, take a look and assist if you can.
-
-## Rule of Two
-
-A pull request may be merged once two maintainers have reviewed the pull request and indicated that it is acceptable to them. There is no need to wait for a third unless one of the two reviewers wishes for another set of eyes.
-
-## Think Security
-
-We owe it to our users to ensure that using a theme from the community or building someone else's site doesn't come with built-in security vulnerabilities. Things like where files may be read from and written to are important to keep secure. Jekyll is also the basis for hosted services such as [GitHub Pages](https://pages.github.com), which cannot upgrade when security issues are introduced.

docs/_docs/maintaining/special-labels.md

@@ -1,24 +0,0 @@
----
-title: "Special Labels"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-We use a series of "special labels" on GitHub.com to automate handling of some parts of the pull request and issue process. @jekyllbot may automatically apply or remove certain labels based on actions taken by users or maintainers. Below are the labels and how they work:
-
-## `pending-feedback`
-
-This label is used to indicate that we need more information from the issue/PR author in order to continue. It may be that you need more info before you can properly triage a bug report, or that you have some unanswered questions about a PR that need to be resolved before moving forward. You can safely ignore any issue with this label, as it is waiting for feedback.
-
-## `needs-work` & `pending-rebase`
-
-These labels are used to indicate that the Git state of a pull request must change. Both are removed once a push is registered (a "synchronize" event for the pull request) and the pull request becomes mergable. Add `needs-work` to a PR if, after your review, it requires code changes. Add `pending-rebase` to a PR if the code is fine but the branch is not automatically mergable with the target branch (e.g. `master`).
-
-## `stale`
-
-This label is automatically added and removed by @jekyllbot based on activity on an issue or pull request. The rules for this label are laid out in [Triaging an Issue: Staleness and automatic closure](../triaging-an-issue/#staleness-and-automatic-closure).
-
-## `pinned`
-
-This label is for @jekyllbot to ignore the age of the issue, which means that the `stale` label won't be automatically added, and the issue won't be closed after a while. This needs to be set manually, and should be set with care. (The `has-pull-request` label does the same thing, but shouldn't be used to _only_ keep an issue open)

docs/_docs/maintaining/triaging-an-issue.md

@@ -1,54 +0,0 @@
----
-title: "Triaging an Issue"
----
-
-**This guide is for maintainers.** These special people have **write access** to one or more of Jekyll's repositories and help merge the contributions of others. You may find what is written here interesting, but it’s definitely not for everyone.
-{: .note .info }
-
-Before evaluating an issue, it is important to identify if it is a feature
-request or a bug. For the Jekyll project the following definitions are used
-to identify a feature or a bug:
-
-**Feature** - A feature is defined as a request that adds functionality to
-Jekyll outside of its current capabilities.
-**Bug** - A bug is defined as an issue that identifies an error that a user
-(or users) encounter when using current Jekyll functionalities.
-
-## Feature?
-
-If the issue describes a feature request, ask:
-
-1. Is this a setting? [Settings are a crutch](http://ben.balter.com/2016/03/08/optimizing-for-power-users-and-edge-cases/#settings-are-a-crutch) for doing "the right thing". Settings usually point to a bad default or an edge case that could be solved easily with a plugin. Keep the :christmas_tree: of settings as small as possible so as not to reduce the usability of the product. We like the philosophy "decisions not options."
-2. Would at least 80% of users find it useful? If even a quarter of our users won't use it, it's very likely that the request doesn't fit our product's core goal.
-3. Is there another way to accomplish the end goal of the request? Most feature requests are due to bad documentation for or understanding of a pre-existing feature. See if you can clarify the end goal of the request. What is the user trying to do? Could they accomplish that goal through another feature we already support?
-4. Even if 80% of our users will use it, does it fit the core goal of our project? We are writing a tool for making static websites, not a swiss army knife for publishing more generally.
-
-Feel free to get others' opinions and ask questions of the issue author, but depending upon the answers to the questions above, it may be out of scope for our project.
-
-If the request is within scope, prioritize it on the product roadmap with the other maintainers. Apply the appropriate tags and ensure the right people have weighed in to define the feature's scope and implementation. If you want to be the _best ever_, submit a PR yourself which adds the feature.
-
-## Bug?
-
-### Reproducibility
-
-If the bug has clear reproduction steps, take a minute to try them. If it helps, write a test in our test suite for the scenario which replicates the problem. Can you reliably replicate the issue?
-
-If you can't replicate the issue, post your replication steps which didn't work and ask for clarification from the issue author.
-
-### Supported Platform
-
-Is the author using a supported platform? We support the latest versions of macOS, Ubuntu, Debian, CentOS, Fedora, and Arch Linux.
-
-You may close the issue immediately if the author cannot reproduce the issue on a supported platform. For Windows-related problems, leave a comment letting the user know that Windows is not officially supported, but that they may absolutely continue using the issue to communicate with folks from `@jekyll/windows` to further investigate. Additionally, you can point them to Jekyll Talk (https://talk.jekyllrb.com) as a means of getting support from the community.
-
-If the user is experiencing issues with GitHub Pages or another hosted platform that we cannot reproduce, please direct them to the platform's support channel and close the issue.
-
-### What they wanted vs. what they got
-
-An issue without a clear explanation of what the user got and what they were expecting to get is not an issue we can accurately respond to. If the user doesn't provide this information, please ask for clarification and apply the `pending-feedback` label. This information helps us build test cases such that we do not break the behaviour again in the future. The `pending-feedback` label will be removed automatically once the issue author posts a reply.
-
-Is what they wanted to get something we want to happen? Sometimes a bug report is actually masquerading as a feature request. See the guidance above for handling feature requests.
-
-### Staleness and automatic closure
-
-@jekyllbot will automatically mark issues as `stale` if no activity occurs for at least one month. @jekyllbot leaves a comment asking for information about reproducibility in current versions. If no one responds after another month, the issue is automatically closed. This behaviour can be suppressed by setting the [`pinned` label](../maintaining/special-labels.md/#pinned).

docs/_docs/pages.md

@@ -1,74 +0,0 @@
----
-title: Creating pages
-permalink: /docs/pages/
----
-
-In addition to [writing posts](../posts/), you might also want to add static pages (content that isn't date-based) to your Jekyll site. By taking advantage of the way Jekyll copies files and directories, this is easy to do.
-
-## Homepage
-
-Just about every web server configuration you come across will look for an HTML
-file called `index.html` (by convention) in the site's root folder and display
-that as the homepage. Unless the web server you’re using is configured to look
-for some different filename as the default, this file will turn into the
-homepage of your Jekyll-generated site.
-
-<div class="note">
-  <h5>ProTip™: Use layouts on your homepage</h5>
-  <p>
-    Any HTML file on your site can use layouts and/or includes, even the
-    homepage. Common content, like headers and footers, make excellent
-    candidates for extraction into a layout.
-  </p>
-</div>
-
-## Where additional pages live
-
-Where you put HTML or [Markdown](https://daringfireball.net/projects/markdown/)
-files for pages depends on how you want the pages to work. There are two main ways of creating pages:
-
-- Place named HTML or [Markdown](https://daringfireball.net/projects/markdown/)
-files for each page in your site's root folder.
-- Place pages inside folders and subfolders named whatever you want.
-
-Both methods work fine (and can be used in conjunction with each other),
-with the only real difference being the resulting URLs. By default, pages retain the same folder structure in `_site` as they do in the source directory.
-
-### Named HTML files
-
-The simplest way of adding a page is just to add an HTML file in the root
-directory with a suitable name for the page you want to create. For a site with
-a homepage, an about page, and a contact page, here’s what the root directory
-and associated URLs might look like:
-
-```sh
-.
-|-- _config.yml
-|-- _includes/
-|-- _layouts/
-|-- _posts/
-|-- _site/
-|-- about.html    # => http://example.com/about.html
-|-- index.html    # => http://example.com/
-|-- other.md      # => http://example.com/other.html
-└── contact.html  # => http://example.com/contact.html
-```
-
-If you have a lot of pages, you can organize those pages into subfolders. The same subfolders that are used to group your pages in our project's source will exist in the `_site` folder when your site builds.
-
-## Flattening pages from subfolders into the root directory
-
-If you have pages organized into subfolders in your source folder and want to flatten them in the root folder on build, you must add the [permalink]({% link _docs/permalinks.md %}) property directly in your page's front matter like this:
-
-```yaml
----
-title: My page
-permalink: mypageurl.html
----
-```
-
-### Named folders containing index HTML files
-
-If you don't want file extensions (`.html`) to appear in your page URLs (file extensions are the default), you can choose a [permalink style](../permalinks/#builtinpermalinkstyles) that has a trailing slash instead of a file extension.
-
-Note if you want to view your site offline *without the Jekyll preview server*, your browser will need the file extension to display the page, and all assets will need to be relative links that function without the server baseurl.

docs/_docs/permalinks.md

@@ -1,394 +0,0 @@
----
-title: Permalinks
-permalink: /docs/permalinks/
----
-
-Permalinks refer to the URLs (excluding the domain name or directory folder) for your pages, posts, or collections.
-Jekyll supports a flexible way to build permalinks, allowing you to leverage various template variables or choose built-in permalink styles (such as `date`) that automatically use a template-variable pattern.
-
-You construct permalinks by creating a template URL where dynamic elements are represented by colon-prefixed keywords. The default template permalink is `/:categories/:year/:month/:day/:title:output_ext`. Each of the colon-prefixed keywords is a template variable.
-
-## Where to configure permalinks
-
-You can configure your site's permalinks through the [Configuration]({% link _docs/configuration.md %}) file or in the [Front Matter]({% link _docs/frontmatter.md %}) for each post, page, or collection.
-
-Setting permalink styles in your configuration file applies the setting globally in your project. You configure permalinks in your `_config.yml` file like this:
-
-```yaml
-permalink: /:categories/:year/:month/:day/:title:output_ext
-```
-
-If you don't specify any permalink setting, Jekyll uses the above pattern as the default.
-
-The permalink can also be set using a built-in permalink style:
-
-```yaml
-permalink: date
-```
-
-`date` is the same as `:categories/:year/:month/:day/:title:output_ext`, the default. See [Built-in Permalink Styles](#builtinpermalinkstyles) below for more options.
-
-Setting the permalink in your post, page, or collection's front matter overrides any global settings. Here's an example:
-
-```yaml
----
-title: My page title
-permalink: /mypageurl/
----
-```
-
-Even if your configuration file specifies the `date` style, the URL for this page would be `http://somedomain.com/mypageurl/`.
-
-When you use permalinks that omit the `.html` file extension (called "pretty URLs") Jekyll builds the file as index.html placed inside a folder with the page's name. For example:
-
-```
-├── mypageurl
-│   └── index.html
-```
-
-With a URL such as `/mypageurl/`, servers automatically load the index.html file inside the folder, so users can simply navigate to `http://somedomain.com/mypageurl/` to get to `mypageurl/index.html`.
-
-## Template variables for permalinks {#template-variables}
-
-The following table lists the template variables available for permalinks. You can use these variables in the `permalink` property in your config file.
-
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Variable</th>
-      <th>Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p><code>year</code></p>
-      </td>
-      <td>
-        <p>
-          Year from the post's filename. May be overridden via the document’s
-          <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>month</code></p>
-      </td>
-      <td>
-        <p>
-          Month from the post's filename. May be overridden via the document’s
-          <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>i_month</code></p>
-      </td>
-      <td>
-        <p>
-          Month without leading zeros from the post's filename. May be
-          overridden via the document’s <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>day</code></p>
-      </td>
-      <td>
-        <p>
-          Day from the post's filename. May be overridden via the document’s
-          <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>i_day</code></p>
-      </td>
-      <td>
-        <p>
-          Day without leading zeros from the post's filename. May be overridden
-          via the document’s <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>y_day</code></p>
-      </td>_
-      <td>
-        <p>Day of the year from the post's filename, with leading zeros.</p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>short_year</code></p>
-      </td>
-      <td>
-        <p>
-          Year without the century from the post's filename. May be overridden
-          via the document’s <code>date</code> YAML front matter
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>hour</code></p>
-      </td>
-      <td>
-        <p>
-          Hour of the day, 24-hour clock, zero-padded from the post's
-          <code>date</code> front matter. (00..23)
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>minute</code></p>
-      </td>
-      <td>
-        <p>
-          Minute of the hour from the post's <code>date</code> front matter. (00..59)
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>second</code></p>
-      </td>
-      <td>
-        <p>
-          Second of the minute from the post's <code>date</code> front matter. (00..59)
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>title</code></p>
-      </td>
-      <td>
-        <p>
-            Title from the document’s filename. May be overridden via
-            the document’s <code>slug</code> YAML front matter.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>slug</code></p>
-      </td>
-      <td>
-        <p>
-            Slugified title from the document’s filename (any character
-            except numbers and letters is replaced as hyphen). May be
-            overridden via the document’s <code>slug</code> YAML front matter.
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>categories</code></p>
-      </td>
-      <td>
-        <p>
-          The specified categories for this post. If a post has multiple
-          categories, Jekyll will create a hierarchy (e.g. <code>/category1/category2</code>).
-          Also Jekyll automatically parses out double slashes in the URLs,
-          so if no categories are present, it will ignore this.
-        </p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-
-Note that all template variables relating to time or categories are available to posts only.
-
-## Built-in permalink styles {#builtinpermalinkstyles}
-
-Although you can specify a custom permalink pattern using [template variables](#template-variables), Jekyll also provides the following built-in styles for convenience.
-
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Permalink Style</th>
-      <th>URL Template</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p><code>date</code></p>
-      </td>
-      <td>
-        <p><code>/:categories/:year/:month/:day/:title:output_ext</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>pretty</code></p>
-      </td>
-      <td>
-        <p><code>/:categories/:year/:month/:day/:title/</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>ordinal</code></p>
-      </td>
-      <td>
-        <p><code>/:categories/:year/:y_day/:title:output_ext</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>none</code></p>
-      </td>
-      <td>
-        <p><code>/:categories/:title:output_ext</code></p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-
-Rather than typing `permalink: /:categories/:year/:month/:day/:title/`, you can just type `permalink: pretty`.
-
-<div class="note info">
-<h5>Specifying permalinks through the YAML Front Matter</h5>
-<p>Built-in permalink styles are not recognized in YAML Front Matter. As a result, <code>permalink: pretty</code> will not work.</p>
-</div>
-
-## Permalink style examples with posts {#permalink-style-examples}
-
-Here are a few examples to clarify how permalink styles get applied with posts.
-
-Given a post named: `/2009-04-29-slap-chop.md`
-
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>URL Template</th>
-      <th>Resulting Permalink URL</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p>None specified, or <code>permalink: date</code></p>
-      </td>
-      <td>
-        <p><code>/2009/04/29/slap-chop.html</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>pretty</code></p>
-      </td>
-      <td>
-        <p><code>/2009/04/29/slap-chop/</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>/:month-:day-:year/:title:output_ext</code></p>
-      </td>
-      <td>
-        <p><code>/04-29-2009/slap-chop.html</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>/blog/:year/:month/:day/:title/</code></p>
-      </td>
-      <td>
-        <p><code>/blog/2009/04/29/slap-chop/</code></p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p><code>/:year/:month/:title</code></p>
-        <p>See <a href="#extensionless-permalinks">Extensionless permalinks with no trailing slashes</a> for details.</p>
-      </td>
-      <td>
-        <p><code>/2009/04/slap-chop</code></p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-
-## Permalink settings for pages and collections {#pages-and-collections}
-
-The permalink setting in your configuration file specifies the permalink style used for posts, pages, and collections. However, because pages and collections don't have time or categories, these aspects of the permalink style are ignored with pages and collections.
-
-For example:
-
-* A permalink style of `/:categories/:year/:month/:day/:title:output_ext` for posts becomes `/:title.html` for pages and collections.
-* A permalink style of `pretty` (or `/:categories/:year/:month/:day/:title/`), which omits the file extension and contains a trailing slash, will update page and collection permalinks to also omit the file extension and contain a trailing slash: `/:title/`.
-* A permalink style of `date`, which contains a trailing file extension, will update page permalinks to also contain a trailing file extension: `/:title.html`. But no time or category information will be included.
-
-## Permalinks and default paths
-
-The path to the post or page in the built site differs for posts, pages, and collections:
-
-### Posts
-
-The subfolders into which you may have organized your posts inside the `_posts` directory will not be part of the permalink.
-
-If you use a permalink style that omits the `.html` file extension, each post is rendered as an `index.html` file inside a folder with the post's name (for example, `categoryname/2016/12/01/mypostname/index.html`).
-
-### Pages
-
-Unlike posts, pages by default mimic the source directory structure exactly. (The only exception is if your page has a `permalink` declared its front matter &mdash; in that case, the structure honors the permalink setting instead of the source folder structure.)
-
-As with posts, if you use a permalink style that omits the `.html` file extension, each page is rendered as an `index.html` file inserted inside a folder with the page's name (for example, `mypage/index.html`).
-
-### Collections
-
-By default, collections follow a similar structure in the `_site` folder as pages, except that the path is prefaced by the collection name. For example: `collectionname/mypage.html`. For permalink settings that omit the file extension, the path would be `collection_name/mypage/index.html`.
-
-Collections have their own way of setting permalinks. Additionally, collections have unique template variables available (such as `path` and `output_ext`). See the [Configuring permalinks for collections](../collections/#permalinks) in Collections for more information.
-
-## Flattening pages in \_site on build
-
-If you want to flatten your pages (pull them out of subfolders) in the `_site` directory when your site builds (similar to posts), add the `permalink` property to the front matter of each page, with no path specified:
-
-```yaml
----
-title: My page
-permalink: mypageurl.html
----
-```
-
-## Extensionless permalinks with no trailing slashes {#extensionless-permalinks}
-
-Jekyll supports permalinks that contain neither a trailing slash nor a file extension, but this requires additional support from the web server to properly serve. When using these types of permalinks, output files written to disk will still have the proper file extension (typically `.html`), so the web server must be able to map requests without file extensions to these files.
-
-Both [GitHub Pages](../github-pages/) and the Jekyll's built-in WEBrick server handle these requests properly without any additional work.
-
-### Apache
-
-The Apache web server has extensive support for content negotiation and can handle extensionless URLs by setting the [multiviews](https://httpd.apache.org/docs/current/content-negotiation.html#multiviews) option in your `httpd.conf` or `.htaccess` file:
-
-{% highlight apache %}
-Options +MultiViews
-{% endhighlight %}
-
-### Nginx
-
-The [try_files](http://nginx.org/en/docs/http/ngx_http_core_module.html#try_files) directive allows you to specify a list of files to search for to process a request. The following configuration will instruct nginx to search for a file with an `.html` extension if an exact match for the requested URI is not found.
-
-{% highlight nginx %}
-try_files $uri $uri.html $uri/ =404;
-{% endhighlight %}
-
-## Linking without regard to permalink styles
-
-You can create links in your topics to other posts, pages, or collection items in a way that is valid no matter what permalink configuration you choose. By using the `link` tag, if you change your permalinks, your links won't break. See [Linking to pages](../templates#link) in Templates for more details.

docs/_docs/quickstart.md

@@ -1,53 +0,0 @@
----
-title: Quick-start guide
-permalink: /docs/quickstart/
----
-
-
-If you already have a full [Ruby](https://www.ruby-lang.org/en/downloads/) development environment with all headers and [RubyGems](https://rubygems.org/pages/download) installed (see Jekyll's [requirements](/docs/installation/#requirements)), you can create a new Jekyll site by doing the following:
-
-```sh
-# Install Jekyll and Bundler gems through RubyGems
-gem install jekyll bundler
-
-# Create a new Jekyll site at ./myblog
-jekyll new myblog
-
-# Change into your new directory
-cd myblog
-
-# Build the site on the preview server
-bundle exec jekyll serve
-
-# Now browse to http://localhost:4000
-```
-
-If you encounter any unexpected errors during the above, please refer to the [troubleshooting](/docs/troubleshooting/#configuration-problems) page or the already-mentioned [requirements](/docs/installation/#requirements) page, as you might be missing development headers or other prerequisites.
-
-## About Bundler
-
-`gem install bundler` installs the [bundler](https://rubygems.org/gems/bundler) gem through [RubyGems](https://rubygems.org/). You only need to install it once — not every time you create a new Jekyll project. Here are some additional details:
-
-* `bundler` is a gem that manages other Ruby gems. It makes sure your gems and gem versions are compatible, and that you have all necessary dependencies each gem requires.
-* The `Gemfile` and `Gemfile.lock` files inform Bundler about the gem requirements in your site. If your site doesn't have these Gemfiles, you can omit `bundle exec` and just run `jekyll serve`.
-
-* When you run `bundle exec jekyll serve`, Bundler uses the gems and versions as specified in `Gemfile.lock` to ensure your Jekyll site builds with no compatibility or dependency conflicts.
-
-For more information about how to use Bundler in your Jekyll project, this [tutorial](https://jekyllrb.com/tutorials/using-jekyll-with-bundler/) should provide answers to the most common questions and explain how to get up and running quickly.
- 
-## Options for creating a new site with Jekyll
-
-`jekyll new <PATH>` installs a new Jekyll site at the path specified (relative to current directory). In this case, Jekyll will be installed in a directory called `myblog`. Here are some additional details:
-
-* To install the Jekyll site into the directory you're currently in, run `jekyll new .` If the existing directory isn't empty, you can pass the `--force` option with `jekyll new . --force`.
-* `jekyll new` automatically initiates `bundle install` to install the dependencies required. (If you don't want Bundler to install the gems, use `jekyll new myblog --skip-bundle`.)
-* By default, the Jekyll site installed by `jekyll new` uses a gem-based theme called [Minima](https://github.com/jekyll/minima). With [gem-based themes](../themes), some of the directories and files are stored in the theme-gem, hidden from your immediate view.
-* We recommend setting up Jekyll with a gem-based theme but if you want to start with a blank slate, use `jekyll new myblog --blank`
-* To learn about other parameters you can include with `jekyll new`, type `jekyll new --help`.
-
-When in doubt, use the <code>help</code> command to remind you of all available options and usage, it also works with the <code>new</code>, <code>build</code> and <code>serve</code> subcommands, e.g. <code>jekyll help new</code> or <code>jekyll help build</code>.
-{: .note .info }
-
-## Next steps
-
-Building a Jekyll site with the default theme is just the first step. The real magic happens when you start creating blog posts, using the front matter to control templates and layouts, and taking advantage of all the awesome configuration options Jekyll makes available.

docs/_docs/resources.md

@@ -1,62 +0,0 @@
----
-title: Resources
-permalink: /docs/resources/
----
-
-Jekyll's growing use is producing a wide variety of tutorials, frameworks, extensions, examples, and other resources that can be very helpful. Below is a collection of links to some of the most popular Jekyll resources.
-
-## Editors
-
-- [jekyll-atom](https://atom.io/packages/jekyll): A collection of snippets and tools for Jekyll in Atom
-- [markdown-writer](https://atom.io/packages/markdown-writer): An Atom package for Jekyll. It can create new posts/drafts, manage tags/categories, insert link/images and add many useful key mappings.
-- [sublime-jekyll](https://github.com/23maverick23/sublime-jekyll): A Sublime Text package for Jekyll static sites. This package should help creating Jekyll sites and posts easier by providing access to key template tags and filters, as well as common completions and a current date/datetime command (for dating posts). You can install this package manually via GitHub, or via [Package Control](https://packagecontrol.io/packages/Jekyll).
-- [vim-jekyll](https://github.com/parkr/vim-jekyll): A vim plugin to generate new posts and run `jekyll build` all without leaving vim.
-- [WordPress2Jekyll](https://wordpress.org/plugins/wp2jekyll/): A WordPress plugin that allows you to use WordPress as your editor and (automatically) export content in to Jekyll. WordPress2Jekyll attempts to marry these two systems together in order to make a site that can be easily managed from all devices.
-
-## Useful Guides
-
-- [CloudCannon Academy](https://learn.cloudcannon.com/) is a set of resources created by [CloudCannon](https://cloudcannon.com/) to help folks get up and running with Jekyll. They cover all skill levels, and even include some great video tutorials.
-- [Jekyll Cheatsheet](https://learn.cloudcannon.com/jekyll-cheat-sheet/) is a single-page resource for Jekyll filters, variables, and the like.
-- ["Creating and Hosting a Personal Site on GitHub"](http://jmcglone.com/guides/github-pages/)
-- ['Build A Blog With Jekyll And GitHub Pages' on Smashing Magazine](https://www.smashingmagazine.com/2014/08/01/build-blog-jekyll-github-pages/)
-- Publishing to GitHub Pages? [Check out our documentation page for just that purpose](/docs/github-pages/).
-- [Blogging with Git, Emacs and Jekyll](https://metajack.im/2009/01/23/blogging-with-git-emacs-and-jekyll/)
-- [Tips for working with GitHub Pages Integration](https://gist.github.com/jedschneider/2890453)
-
-## Integrations
-
-- Use a SaaS service as a backend for forms (contact forms, hiring forms, etc.)
-
-  - [Formspree (open source)](https://formspree.io/)
-  - [FormKeep](https://formkeep.com/guides/contact-form-jekyll?utm_source=github&utm_medium=jekyll-docs&utm_campaign=contact-form-jekyll)
-  - [Simple Form](https://getsimpleform.com/)
-  - [Formingo](https://www.formingo.co/guides/jekyll?utm_source=github&utm_medium=jekyll-docs&utm_campaign=Jekyll%20Documentation)
-  - [Formester](http://www.formester.com)
-  - [Talkyard](https://www.talkyard.io/blog-comments): Embedded comments for Jekyll and others (free and open source, or hosted serverless)
-  - [Staticman](https://staticman.net): Add user-generated content to a Jekyll site (free and open source)
-  - [Snipcart](https://snipcart.com/blog/static-site-e-commerce-part-2-integrating-snipcart-with-jekyll): Add a shopping cart to a Jekyll site
-  - [Contentful](https://www.contentful.com/ecosystem/jekyll/): use Jekyll together with the API-driven Contentful CMS.
-  - [Algolia](https://blog.algolia.com/instant-search-blog-documentation-jekyll-plugin/): Add a powerful instant search to your Jekyll site
-
-## Other commentary
-
-- [How I'm using Jekyll in 2016](https://mademistakes.com/articles/using-jekyll-2016/)
-
-- [Talkyard comments instructions for Jekyll](https://jekyll-demo.talkyard.io/2018/01/09/installation-instructions.html)
-
-- [Static Comments with Jekyll & Staticman](https://mademistakes.com/articles/improving-jekyll-static-comments/)
-
-- [Adding Ajax pagination to Jekyll](https://eduardoboucas.com/blog/2014/11/05/adding-ajax-pagination-to-jekyll.html)
-
-- ['My Jekyll Fork', by Mike West](https://mikewest.org/2009/11/my-jekyll-fork)
-
-  > "Jekyll is a well-architected throwback to a time before WordPress, when men were men, and HTML was static. I like the ideas it espouses, and have made a few improvements to it's core. Here, I'll point out some highlights of my fork in the hopes that they see usage beyond this site."
-
-- ['About this Website', by Carter Allen](http://cartera.me/2010/08/12/about-this-website/)
-
-  > "Jekyll is everything that I ever wanted in a blogging engine. Really. It isn't perfect, but what's excellent about it is that if there's something wrong, I know exactly how it works and how to fix it. It runs on the your machine only, and is essentially an added"build" step between you and the browser. I coded this entire site in TextMate using standard HTML5 and CSS3, and then at the end I added just a few little variables to the markup. Presto-chango, my site is built and I am at peace with the world."
-
-- [Generating a Tag Cloud in Jekyll](http://www.justkez.com/generating-a-tag-cloud-in-jekyll/) – A guide to implementing a tag cloud and per-tag content pages using Jekyll.
-
-- A way to [extend Jekyll](https://github.com/rfelix/jekyll_ext) without forking and modifying the Jekyll gem codebase and some [portable Jekyll extensions](https://wiki.github.com/rfelix/jekyll_ext/extensions) that can be reused and shared.
-- [Using your Rails layouts in Jekyll](http://numbers.brighterplanet.com/2010/08/09/sharing-rails-views-with-jekyll)

docs/_docs/static_files.md

@@ -1,100 +0,0 @@
----
-title: Static Files
-permalink: /docs/static-files/
----
-
-In addition to renderable and convertible content, we also have **static
-files**.
-
-A static file is a file that does not contain any YAML front matter. These
-include images, PDFs, and other un-rendered content.
-
-They're accessible in Liquid via `site.static_files` and contain the
-following metadata:
-
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Variable</th>
-      <th>Description</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td><p><code>file.path</code></p></td>
-      <td><p>
-
-        The relative path to the file, e.g. <code>/assets/img/image.jpg</code>
-
-      </p></td>
-    </tr>
-    <tr>
-      <td><p><code>file.modified_time</code></p></td>
-      <td><p>
-
-        The `Time` the file was last modified, e.g. <code>2016-04-01 16:35:26 +0200</code>
-
-      </p></td>
-    </tr>
-    <tr>
-      <td><p><code>file.name</code></p></td>
-      <td><p>
-
-        The string name of the file e.g. <code>image.jpg</code> for <code>image.jpg</code>
-
-      </p></td>
-    </tr>
-    <tr>
-      <td><p><code>file.basename</code></p></td>
-      <td><p>
-
-        The string basename of the file e.g. <code>image</code> for <code>image.jpg</code>
-
-      </p></td>
-    </tr>
-    <tr>
-      <td><p><code>file.extname</code></p></td>
-      <td><p>
-
-        The extension name for the file, e.g.
-        <code>.jpg</code> for <code>image.jpg</code>
-
-      </p></td>
-    </tr>
-  </tbody>
-</table>
-</div>
-
-Note that in the above table, `file` can be anything. It's simply an arbitrarily set variable used in your own logic (such as in a for loop). It isn't a global site or page variable.
-
-## Add front matter to static files
-
-Although you can't directly add front matter values to static files, you can set front matter values through the [defaults property](../configuration/#front-matter-defaults) in your configuration file. When Jekyll builds the site, it will use the front matter values you set.
-
-Here's an example:
-
-In your `_config.yml` file, add the following values to the `defaults` property:
-
-```yaml
-defaults:
-  - scope:
-      path: "assets/img"
-    values:
-      image: true
-```
-
-This assumes that your Jekyll site has a folder path of `assets/img` where  you have images (static files) stored. When Jekyll builds the site, it will treat each image as if it had the front matter value of `image: true`.
-
-Suppose you want to list all your image assets as contained in `assets/img`. You could use this for loop to look in the `static_files` object and get all static files that have this front matter property:
-
-{% raw %}
-```liquid
-{% assign image_files = site.static_files | where: "image", true %}
-{% for myimage in image_files %}
-  {{ myimage.path }}
-{% endfor %}
-```
-{% endraw %}
-
-When you build your site, the output will list the path to each file that meets this front matter condition.

docs/_docs/support.md

@@ -1,24 +0,0 @@
----
-title: Support
-permalink: "/docs/support/"
-note: This file is autogenerated. Edit /.github/SUPPORT.markdown instead.
----
-
-## Getting Help
-
-**Jekyll's issue tracker is not a support forum.**
-
-If you're looking for support for Jekyll, there are a lot of options:
-
-* Read [Jekyll Documentation](https://jekyllrb.com/docs/home/)
-* If you have a question about using Jekyll, start a discussion on [Jekyll Forum](https://talk.jekyllrb.com/) or [StackOverflow](https://stackoverflow.com/questions/tagged/jekyll)
-* Chat with Jekyllers — Join [our Gitter channel](https://gitter.im/jekyll/jekyll) or [our IRC channel on Freenode](irc:irc.freenode.net/jekyll)
-
-There are a bunch of helpful community members on these services that should be willing to point you in the right direction.
-
-## Report a bug
-
-* If you think you've found a bug within a Jekyll plugin, open an issue in that plugin's repository — First [look for the plugin on rubygems](https://rubygems.org/) then click on the `Homepage` link to access the plugin repository.
-* If you think you've found a bug within Jekyll itself, [open an issue](https://github.com/jekyll/jekyll/issues/new).
-
-Happy Jekyllin'!

docs/_docs/templates.md

@@ -1,619 +0,0 @@
----
-title: Templates
-permalink: /docs/templates/
----
-
-Jekyll uses the [Liquid](https://shopify.github.io/liquid/) templating language to
-process templates. All of the standard Liquid [tags](https://shopify.github.io/liquid/tags/control-flow/) and
-[filters](https://shopify.github.io/liquid/filters/abs/) are
-supported. To make common tasks easier, Jekyll even adds a few handy filters
-and tags of its own, all of which you can find on this page. Jekyll even lets
-you come up with your own tags via plugins.
-
-## Filters
-
-<div class="mobile-side-scroller">
-<table>
-  <thead>
-    <tr>
-      <th>Description</th>
-      <th><span class="filter">Filter</span> and <span class="output">Output</span></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td>
-        <p class="name"><strong>Relative URL</strong></p>
-        <p>Prepend the <code>baseurl</code> value to the input. Useful if your site is hosted at a subpath rather than the root of the domain.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "/assets/style.css" | relative_url }}{% endraw %}</code>
-        </p>
-        <p>
-         <code class="output">/my-baseurl/assets/style.css</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Absolute URL</strong></p>
-        <p>Prepend the <code>url</code> and <code>baseurl</code> value to the input.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "/assets/style.css" | absolute_url }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">http://example.com/my-baseurl/assets/style.css</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to XML Schema</strong></p>
-        <p>Convert a Date into XML Schema (ISO 8601) format.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_xmlschema }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">2008-11-07T13:07:54-08:00</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to RFC-822 Format</strong></p>
-        <p>Convert a Date into the RFC-822 format used for RSS feeds.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_rfc822 }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">Mon, 07 Nov 2008 13:07:54 -0800</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to String</strong></p>
-        <p>Convert a date to short format.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_string }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">07 Nov 2008</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to String in ordinal US style</strong></p>
-        <p>Format a date to ordinal, US, short format.
-        {% include docs_version_badge.html version="3.8.0" %}</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_string: "ordinal", "US" }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">Nov 7th, 2008</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to Long String</strong></p>
-        <p>Format a date to long format.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_long_string }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">07 November 2008</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Date to Long String in ordinal UK style</strong></p>
-        <p>Format a date to ordinal, UK, long format.
-        {% include docs_version_badge.html version="3.8.0" %}</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.time | date_to_long_string: "ordinal" }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">7th November 2008</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Where</strong></p>
-        <p>Select all the objects in an array where the key has the given value.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.members | where:"graduation_year","2014" }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Where Expression</strong></p>
-        <p>Select all the objects in an array where the expression is true.
-        {% include docs_version_badge.html version="3.2.0" %}</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.members | where_exp:"item",
-"item.graduation_year == 2014" }}{% endraw %}</code>
-         <code class="filter">{% raw %}{{ site.members | where_exp:"item",
-"item.graduation_year < 2014" }}{% endraw %}</code>
-         <code class="filter">{% raw %}{{ site.members | where_exp:"item",
-"item.projects contains 'foo'" }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Group By</strong></p>
-        <p>Group an array's items by a given property.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.members | group_by:"graduation_year" }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">[{"name"=>"2013", "items"=>[...]},
-{"name"=>"2014", "items"=>[...]}]</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Group By Expression</strong></p>
-        <p>Group an array's items using a Liquid expression.
-        {% include docs_version_badge.html version="3.4.0" %}</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.members | group_by_exp:"item",
-"item.graduation_year | truncate: 3, \"\"" }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">[{"name"=>"201...", "items"=>[...]},
-{"name"=>"200...", "items"=>[...]}]</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>XML Escape</strong></p>
-        <p>Escape some text for use in XML.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.content | xml_escape }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>CGI Escape</strong></p>
-        <p>
-          CGI escape a string for use in a URL. Replaces any special characters
-          with appropriate <code>%XX</code> replacements. CGI escape normally replaces a space with a plus <code>+</code> sign.
-        </p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "foo, bar; baz?" | cgi_escape }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">foo%2C+bar%3B+baz%3F</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>URI Escape</strong></p>
-        <p>
-          Percent encodes any special characters in a URI. URI escape normally replaces a space with <code>%20</code>. <a href="https://en.wikipedia.org/wiki/Percent-encoding#Types_of_URI_characters">Reserved characters</a> will not be escaped.
-        </p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "http://foo.com/?q=foo, \bar?" | uri_escape }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">http://foo.com/?q=foo,%20%5Cbar?</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Number of Words</strong></p>
-        <p>Count the number of words in some text.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.content | number_of_words }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">1337</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Array to Sentence</strong></p>
-        <p>Convert an array into a sentence. Useful for listing tags. Optional argument for connector.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.tags | array_to_sentence_string }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">foo, bar, and baz</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ page.tags | array_to_sentence_string: 'or' }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">foo, bar, or baz</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Markdownify</strong></p>
-        <p>Convert a Markdown-formatted string into HTML.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.excerpt | markdownify }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Smartify</strong></p>
-        <p>Convert "quotes" into &ldquo;smart quotes.&rdquo;</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.title | smartify }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Converting Sass/SCSS</strong></p>
-        <p>Convert a Sass- or SCSS-formatted string into CSS.</p>
-      </td>
-      <td class="align-center">
-        <p>
-          <code class="filter">{% raw %}{{ some_scss | scssify }}{% endraw %}</code>
-          <code class="filter">{% raw %}{{ some_sass | sassify }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Slugify</strong></p>
-        <p>Convert a string into a lowercase URL "slug". See below for options.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "The _config.yml file" | slugify }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">the-config-yml-file</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ "The _config.yml file" | slugify: 'pretty' }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">the-_config.yml-file</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ "The _cönfig.yml file" | slugify: 'ascii' }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">the-c-nfig-yml-file</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ "The cönfig.yml file" | slugify: 'latin' }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">the-config-yml-file</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Data To JSON</strong></p>
-        <p>Convert Hash or Array to JSON.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.data.projects | jsonify }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Normalize Whitespace</strong></p>
-        <p>Replace any occurrence of whitespace with a single space.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ "a \n b" | normalize_whitespace }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Sort</strong></p>
-        <p>Sort an array. Optional arguments for hashes: 1.&nbsp;property name 2.&nbsp;nils order (<em>first</em> or <em>last</em>).</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ page.tags | sort }}{% endraw %}</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ site.posts | sort: 'author' }}{% endraw %}</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ site.pages | sort: 'title', 'last' }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Sample</strong></p>
-        <p>Pick a random value from an array. Optional: pick multiple values.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ site.pages | sample }}{% endraw %}</code>
-        </p>
-        <p>
-         <code class="filter">{% raw %}{{ site.pages | sample:2 }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>To Integer</strong></p>
-        <p>Convert a string or boolean to integer.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ some_var | to_integer }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Array Filters</strong></p>
-        <p>Push, pop, shift, and unshift elements from an Array.</p>
-        <p>These are <strong>NON-DESTRUCTIVE</strong>, i.e. they do not mutate the array, but rather make a copy and mutate that.</p>
-      </td>
-      <td class="align-center">
-        <p>
-          <code class="filter">{% raw %}{{ page.tags | push: 'Spokane' }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">['Seattle', 'Tacoma', 'Spokane']</code>
-        </p>
-        <p>
-          <code class="filter">{% raw %}{{ page.tags | pop }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">['Seattle']</code>
-        </p>
-        <p>
-          <code class="filter">{% raw %}{{ page.tags | shift }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">['Tacoma']</code>
-        </p>
-        <p>
-          <code class="filter">{% raw %}{{ page.tags | unshift: "Olympia" }}{% endraw %}</code>
-        </p>
-        <p>
-          <code class="output">['Olympia', 'Seattle', 'Tacoma']</code>
-        </p>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <p class="name"><strong>Inspect</strong></p>
-        <p>Convert an object into its String representation for debugging.</p>
-      </td>
-      <td class="align-center">
-        <p>
-         <code class="filter">{% raw %}{{ some_var | inspect }}{% endraw %}</code>
-        </p>
-      </td>
-    </tr>
-  </tbody>
-</table>
-</div>
-
-### Options for the `slugify` filter
-
-The `slugify` filter accepts an option, each specifying what to filter.
-The default is `default`. They are as follows (with what they filter):
-
-- `none`: no characters
-- `raw`: spaces
-- `default`: spaces and non-alphanumeric characters
-- `pretty`: spaces and non-alphanumeric characters except for `._~!$&'()+,;=@`
-- `ascii`: spaces, non-alphanumeric, and non-ASCII characters
-- `latin`: like `default`, except Latin characters are first transliterated (e.g. `àèïòü` to `aeiou`) {%- include docs_version_badge.html version="3.7.0" -%}
-
-## Tags
-
-* [Includes](#includes)
-* [Code snippet highlighting](#code-snippet-highlighting)
-* [Linking to pages, collections and posts (the new and improved way)](#links)
-* [Linking to posts (the old way)](#linking-to-posts)
-
-### Includes
-
-If you have small page snippets that you want to include in multiple places on your site, save the snippets as *include files* and insert them where required, by using the `include` tag:
-
-{% raw %}
-```liquid
-{% include footer.html %}
-```
-{% endraw %}
-
-Jekyll expects all *include files* to be placed in an `_includes` directory at the root of your source directory. In the above example, this will embed the contents of `_includes/footer.html` into the calling file.
-
-For more advanced information on using includes, see [Includes](../includes).
-
-### Code snippet highlighting
-
-Jekyll has built in support for syntax highlighting of over 60 languages
-thanks to [Rouge](http://rouge.jneen.net). Rouge is the default highlighter
-in Jekyll 3 and above. To use it in Jekyll 2, set `highlighter` to `rouge`
-and ensure the `rouge` gem is installed properly.
-
-Alternatively, you can use [Pygments](http://pygments.org) to highlight
-your code snippets. To use Pygments, you must have Python installed on your
-system, have the `pygments.rb` gem installed and set `highlighter` to
-`pygments` in your site's configuration file. Pygments supports [over 100
-languages](http://pygments.org/languages/)
-
-To render a code block with syntax highlighting, surround your code as follows:
-
-{% raw %}
-```liquid
-{% highlight ruby %}
-def foo
-  puts 'foo'
-end
-{% endhighlight %}
-```
-{% endraw %}
-
-The argument to the `highlight` tag (`ruby` in the example above) is the
-language identifier. To find the appropriate identifier to use for the language
-you want to highlight, look for the “short name” on the [Rouge
-wiki](https://github.com/jayferd/rouge/wiki/List-of-supported-languages-and-lexers)
-or the [Pygments' Lexers page](http://pygments.org/docs/lexers/).
-
-<div class="note info">
-  <h5>Jekyll processes all Liquid filters in code blocks</h5>
-  <p>If you are using a language that contains curly braces, you
-    will likely need to place <code>{&#37; raw &#37;}</code> and
-    <code>{&#37; endraw &#37;}</code> tags around your code.</p>
-</div>
-
-#### Line numbers
-
-There is a second argument to `highlight` called `linenos` that is optional.
-Including the `linenos` argument will force the highlighted code to include line
-numbers. For instance, the following code block would include line numbers next
-to each line:
-
-{% raw %}
-```liquid
-{% highlight ruby linenos %}
-def foo
-  puts 'foo'
-end
-{% endhighlight %}
-```
-{% endraw %}
-
-#### Stylesheets for syntax highlighting
-
-In order for the highlighting to show up, you’ll need to include a highlighting
-stylesheet. For an example stylesheet you can look at
-[syntax.css](https://github.com/mojombo/tpw/tree/master/css/syntax.css). These
-are the same styles as used by GitHub and you are free to use them for your own
-site. If you use `linenos`, you might want to include an additional CSS class
-definition for the `.lineno` class in `syntax.css` to distinguish the line
-numbers from the highlighted code.
-
-
-## Links
-
-### Linking to pages {#link}
-
-To link to a post, a page, collection item, or file, the `link` tag will generate the correct permalink URL for the path you specify. For example, if you use the `link` tag to link to `mypage.html`, even if you change your permalink style to include the file extension or omit it, the URL formed by the `link` tag will always be valid.
-
-You must include the file's original extension when using the `link` tag. Here are some examples:
-
-{% raw %}
-```liquid
-{{ site.baseurl }}{% link _collection/name-of-document.md %}
-{{ site.baseurl }}{% link _posts/2016-07-26-name-of-post.md %}
-{{ site.baseurl }}{% link news/index.html %}
-{{ site.baseurl }}{% link /assets/files/doc.pdf %}
-```
-{% endraw %}
-
-You can also use the `link` tag to create a link in Markdown as follows:
-
-{% raw %}
-```liquid
-[Link to a document]({{ site.baseurl }}{% link _collection/name-of-document.md %})
-[Link to a post]({{ site.baseurl }}{% link _posts/2016-07-26-name-of-post.md %})
-[Link to a page]({{ site.baseurl }}{% link news/index.html %})
-[Link to a file]({{ site.baseurl }}{% link /assets/files/doc.pdf %})
-```
-{% endraw %}
-
-(Including `{% raw %}{{ site.baseurl }}{% endraw %}` is optional &mdash; it depends on whether you want to preface the page URL with the `baseurl` value.)
-
-The path to the post, page, or collection is defined as the path relative to the root directory (where your config file is) to the file, not the path from your existing page to the other page.
-
-For example, suppose you're creating a link in `page_a.md` (stored in `pages/folder1/folder2`) to `page_b.md` (stored in  `pages/folder1`). Your path in the link would not be `../page_b.html`. Instead, it would be `/pages/folder1/page_b.md`.
-
-If you're unsure of the path, add `{% raw %}{{ page.path }}{% endraw %}` to the page and it will display the path.
-
-One major benefit of using the `link` or `post_url` tag is link validation. If the link doesn't exist, Jekyll won't build your site. This is a good thing, as it will alert you to a broken link so you can fix it (rather than allowing you to build and deploy a site with broken links).
-
-Note you cannot add filters to `link` tags. For example, you cannot append a string using Liquid filters, such as `{% raw %}{% link mypage.html | append: "#section1" %} {% endraw %}`. To link to sections on a page, you will need to use regular HTML or Markdown linking techniques.
-
-### Linking to posts
-
-If you want to include a link to a post on your site, the `post_url` tag will generate the correct permalink URL for the post you specify.
-
-{% raw %}
-```liquid
-{{ site.baseurl }}{% post_url 2010-07-21-name-of-post %}
-```
-{% endraw %}
-
-If you organize your posts in subdirectories, you need to include subdirectory path to the post:
-
-{% raw %}
-```liquid
-{{ site.baseurl }}{% post_url /subdir/2010-07-21-name-of-post %}
-```
-{% endraw %}
-
-There is no need to include the file extension when using the `post_url` tag.
-
-You can also use this tag to create a link to a post in Markdown as follows:
-
-{% raw %}
-```liquid
-[Name of Link]({{ site.baseurl }}{% post_url 2010-07-21-name-of-post %})
-```
-{% endraw %}

docs/_docs/themes.md

@@ -1,316 +0,0 @@
----
-title: Themes
-permalink: /docs/themes/
----
-
-Jekyll has an extensive theme system that allows you to leverage community-maintained templates and styles to customize your site's presentation. Jekyll themes specify plugins and package up assets, layouts, includes, and stylesheets in a way that can be overridden by your site's content.
-
-## Understanding gem-based themes
-
-When you [create a new Jekyll site](/docs/quickstart) (by running the `jekyll new <PATH>` command), Jekyll installs a site that uses a gem-based theme called [Minima](https://github.com/jekyll/minima).
-
-With gem-based themes, some of the site's directories (such as the `assets`, `_layouts`, `_includes`, and `_sass` directories) are stored in the theme's gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll's build process.
-
-In the case of Minima, you see only the following files in your Jekyll site directory:
-
-```
-├── Gemfile
-├── Gemfile.lock
-├── _config.yml
-├── _posts
-│   └── 2016-12-04-welcome-to-jekyll.markdown
-├── about.markdown
-└── index.markdown
-```
-
-The `Gemfile` and `Gemfile.lock` files are used by Bundler to keep track of the required gems and gem versions you need to build your Jekyll site.
-
-Gem-based themes make it easy for theme developers to make updates available to anyone who has the theme gem. When there's an update, theme developers push the update to RubyGems.
-
-If you have the theme gem, you can (if you desire) run `bundle update` to update all gems in your project. Or you can run `bundle update <THEME>`, replacing `<THEME>` with the theme name, such as `minima`, to just update the theme gem. Any new files or updates the theme developer has made (such as to stylesheets or includes) will be pulled into your project automatically.
-
-The goal of gem-based themes is to allow you to get all the benefits of a robust, continually updated theme without having all the theme's files getting in your way and over-complicating what might be your primary focus: creating content.
-
-## Overriding theme defaults
-
-Jekyll themes set default layouts, includes, and stylesheets. However, you can override any of the theme defaults with your own site content.
-
-To replace layouts or includes in your theme, make a copy in your `_layouts` or `_includes` directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.
-
-For example, if your selected theme has a `page` layout, you can override the theme's layout by creating your own `page` layout in the `_layouts` directory (that is, `_layouts/page.html`).
-
-To locate a theme's files on your computer:
-
-1. Run `bundle show` followed by the name of the theme's gem, e.g., `bundle show minima` for Jekyll's default theme.
-
-   This returns the location of the gem-based theme files. For example, the Minima theme's files might be located in `/usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0` on macOS.
-
-2. Open the theme's directory in Finder or Explorer:
-
-   ```sh
-   # On MacOS
-   open $(bundle show minima)
-   # On Windows
-   explorer /usr/local/lib/ruby/gems/2.3.0/gems/minima-2.1.0
-   # On Linux
-   xdg-open $(bundle show minima)
-   ```
-
-   A Finder or Explorer window opens showing the theme's files and directories. The Minima theme gem contains these files:
-
-    ```
-    ├── LICENSE.txt
-    ├── README.md
-    ├── _includes
-    │   ├── disqus_comments.html
-    │   ├── footer.html
-    │   ├── google-analytics.html
-    │   ├── head.html
-    │   ├── header.html
-    │   ├── icon-github.html
-    │   ├── icon-github.svg
-    │   ├── icon-twitter.html
-    │   └── icon-twitter.svg
-    ├── _layouts
-    │   ├── default.html
-    │   ├── home.html
-    │   ├── page.html
-    │   └── post.html
-    ├── _sass
-    │   ├── minima
-    │   │   ├── _base.scss
-    │   │   ├── _layout.scss
-    │   │   └── _syntax-highlighting.scss
-    │   └── minima.scss
-    └── assets
-        └── main.scss
-     ```
-
-With a clear understanding of the theme's files, you can now override any theme file by creating a similarly named file in your Jekyll site directory.
-
-Let's say, for a second example, you want to override Minima's footer. In your Jekyll site, create an `_includes` folder and add a file in it called `footer.html`. Jekyll will now use your site's `footer.html` file instead of the `footer.html` file from the Minima theme gem.
-
-To modify any stylesheet you must take the extra step of also copying the main sass file (`_sass/minima.scss` in the Minima theme) into the `_sass` directory in your site's source.
-
-Jekyll will look first to your site's content before looking to the theme's defaults for any requested file in the following folders:
-
-- `/assets`
-- `/_layouts`
-- `/_includes`
-- `/_sass`
-
-Note that making copies of theme files will prevent you from receiving any theme updates on those files. An alternative, to continue getting theme updates on all stylesheets, is to use higher specificity CSS selectors in your own additional, originally named CSS files.
-
-Refer to your selected theme's documentation and source repository for more information on what files you can override.
-{: .note .info}
-
-## Converting gem-based themes to regular themes
-
-Suppose you want to get rid of the gem-based theme and convert it to a regular theme, where all files are present in your Jekyll site directory, with nothing stored in the theme gem.
-
-To do this, copy the files from the theme gem's directory into your Jekyll site directory. (For example, copy them to `/myblog` if you created your Jekyll site at `/myblog`. See the previous section for details.)
-
-Then you must tell Jekyll about the plugins that were referenced by the theme. You can find these plugins in the theme's gemspec file as runtime dependencies. If you were converting the Minima theme, for example, you might see:
-
-```
-spec.add_runtime_dependency "jekyll-feed", "~> 0.9"
-spec.add_runtime_dependency "jekyll-seo-tag", "~> 2.1"
-```
-
-You should include these references in the `Gemfile` in one of two ways.
-
-You could list them individually in both `Gemfile` and `_config.yml`.
-
-```ruby
-# ./Gemfile
-
-gem "jekyll-feed", "~> 0.9"
-gem "jekyll-seo-tag", "~> 2.1"
-```
-
-```yaml
-# ./_config.yml
-
-plugins:
-  - jekyll-feed
-  - jekyll-seo-tag
-```
-
-Or you could list them explicitly as Jekyll plugins in your Gemfile, and not update `_config.yml`, like this:
-
-```ruby
-# ./Gemfile
-
-group :jekyll_plugins do
-  gem "jekyll-feed", "~> 0.9"
-  gem "jekyll-seo-tag", "~> 2.1"
-end
-```
-
-Either way, don't forget to `bundle update`.
-
-However, if you're publishing on GitHub Pages you should update only your `_config.yml` as GitHub Pages doesn't load plugins via Bundler.
-
-Finally, remove references to the theme gem in `Gemfile` and configuration. For example, to remove `minima`:
-
-- Open `Gemfile` and remove `gem "minima", "~> 2.0"`.
-- Open `_config.yml` and remove `theme: minima`.
-
-Now `bundle update` will no longer get updates for the theme gem.
-
-## Installing a gem-based theme {#installing-a-theme}
-
-The `jekyll new <PATH>` command isn't the only way to create a new Jekyll site with a gem-based theme. You can also find gem-based themes online and incorporate them into your Jekyll project.
-
-For example, search for [jekyll theme on RubyGems](https://rubygems.org/search?utf8=%E2%9C%93&query=jekyll-theme) to find other gem-based themes. (Note that not all themes are using `jekyll-theme` as a convention in the theme name.)
-
-To install a gem-based theme:
-
-1. Add the theme gem to your site's `Gemfile`:
-
-   ```ruby
-   # ./Gemfile
-
-   # This is an example, declare the theme gem you want to use here
-   gem "jekyll-theme-minimal"
-   ```
-  Or if you've started with the `jekyll new` command, replace `gem "minima", "~> 2.0"` with the gem you want, e.g:
-
-   ```diff
-   # ./Gemfile
-
-   - gem "minima", "~> 2.0"
-   + gem "jekyll-theme-minimal"
-   ```
-
-2. Install the theme:
-
-   ```sh
-   bundle install
-   ```
-
-3. Add the following to your site's `_config.yml` to activate the theme:
-
-   ```yaml
-   theme: jekyll-theme-minimal
-   ```
-
-4. Build your site:
-
-   ```sh
-   bundle exec jekyll serve
-   ```
-
-You can have multiple themes listed in your site's `Gemfile`, but only one theme can be selected in your site's `_config.yml`.
-{: .note .info }
-
-If you're publishing your Jekyll site on [GitHub Pages](https://pages.github.com/), note that GitHub Pages supports only [some gem-based themes](https://pages.github.com/themes/). GitHub Pages also supports [using any theme hosted on GitHub](https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site/#adding-a-jekyll-theme-in-your-sites-_configyml-file) using the `remote_theme` configuration as if it were a gem-based theme.
-
-## Creating a gem-based theme
-
-If you're a Jekyll theme developer (rather than just a consumer of themes), you can package up your theme in RubyGems and allow users to install it through Bundler.
-
-If you're unfamiliar with creating Ruby gems, don't worry. Jekyll will help you scaffold a new theme with the `new-theme` command. Run `jekyll new-theme` with the theme name as an argument.
-
-Here is an example:
-
-```sh
-jekyll new-theme jekyll-theme-awesome
-    create /path/to/jekyll-theme-awesome/_layouts
-    create /path/to/jekyll-theme-awesome/_includes
-    create /path/to/jekyll-theme-awesome/_sass
-    create /path/to/jekyll-theme-awesome/_layouts/page.html
-    create /path/to/jekyll-theme-awesome/_layouts/post.html
-    create /path/to/jekyll-theme-awesome/_layouts/default.html
-    create /path/to/jekyll-theme-awesome/Gemfile
-    create /path/to/jekyll-theme-awesome/jekyll-theme-awesome.gemspec
-    create /path/to/jekyll-theme-awesome/README.md
-    create /path/to/jekyll-theme-awesome/LICENSE.txt
-    initialize /path/to/jekyll-theme-awesome/.git
-    create /path/to/jekyll-theme-awesome/.gitignore
-Your new Jekyll theme, jekyll-theme-awesome, is ready for you in /path/to/jekyll-theme-awesome!
-For help getting started, read /path/to/jekyll-theme-awesome/README.md.
-```
-
-Add your template files in the corresponding folders. Then complete the `.gemspec` and the README files according to your needs.
-
-### Layouts and includes
-
-Theme layouts and includes work just like they work in any Jekyll site. Place layouts in your theme's `/_layouts` folder, and place includes in your themes `/_includes` folder.
-
-For example, if your theme has a `/_layouts/page.html` file, and a page has `layout: page` in its YAML front matter, Jekyll will first look to the site's `_layouts` folder for the `page` layout, and if none exists, will use your theme's `page` layout.
-
-### Assets
-
-Any file in `/assets` will be copied over to the user's site upon build unless they have a file with the same relative path. You can ship any kind of asset here: SCSS, an image, a webfont, etc. These files behave like pages and static files in Jekyll:
-
-- If the file has [YAML front matter](/docs/frontmatter/) at the top, it will be rendered.
-- If the file does not have YAML front matter, it will simply be copied over into the resulting site.
-
-This allows theme creators to ship a default `/assets/styles.scss` file which their layouts can depend on as `/assets/styles.css`.
-
-All files in `/assets` will be output into the compiled site in the `/assets` folder just as you'd expect from using Jekyll on your sites.
-
-### Stylesheets
-
-Your theme's stylesheets should be placed in your theme's `_sass` folder, again, just as you would when authoring a Jekyll site.
-
-```
-_sass
-├── jekyll-theme-awesome.scss
-```
-
-Your theme's styles can be included in the user's stylesheet using the `@import` directive.
-
-{% raw %}
-```css
-@import "{{ site.theme }}";
-```
-{% endraw %}
-
-### Theme-gem dependencies {%- include docs_version_badge.html version="3.5.0" -%}
-
-Jekyll will automatically require all whitelisted `runtime_dependencies` of your theme-gem even if they're not explicitly included under the `plugins` array in the site's config file. (Note: whitelisting is only required when building or serving with the `--safe` option.)
-
-With this, the end-user need not keep track of the plugins required to be included in their config file for their theme-gem to work as intended.
-
-### Documenting your theme
-
-Your theme should include a `/README.md` file, which explains how site authors can install and use your theme. What layouts are included? What includes? Do they need to add anything special to their site's configuration file?
-
-### Adding a screenshot
-
-Themes are visual. Show users what your theme looks like by including a screenshot as `/screenshot.png` within your theme's repository where it can be retrieved programmatically. You can also include this screenshot within your theme's documentation.
-
-### Previewing your theme
-
-To preview your theme as you're authoring it, it may be helpful to add dummy content in, for example, `/index.html` and `/page.html` files. This will allow you to use the `jekyll build` and `jekyll serve` commands to preview your theme, just as you'd preview a Jekyll site.
-
-If you do preview your theme locally, be sure to add `/_site` to your theme's `.gitignore` file to prevent the compiled site from also being included when you distribute your theme.
-{: .info .note}
-
-### Publishing your theme
-
-Themes are published via [RubyGems.org](https://rubygems.org). You will need a RubyGems account, which you can [create for free](https://rubygems.org/sign_up).
-
-1. First, you need to have it in a git repository:
-
-   ```sh
-   git init # Only the first time
-   git add -A
-   git commit -m "Init commit"
-   ```
-
-2. Next, package your theme, by running the following command, replacing `jekyll-theme-awesome` with the name of your theme:
-
-   ```sh
-   gem build jekyll-theme-awesome.gemspec
-   ```
-
-3. Finally, push your packaged theme up to the RubyGems service, by running the following command, again replacing `jekyll-theme-awesome` with the name of your theme:
-
-   ```sh
-   gem push jekyll-theme-awesome-*.gem
-   ```
-
-4. To release a new version of your theme, update the version number in the gemspec file, ( `jekyll-theme-awesome.gemspec` in this example ), and then repeat Steps 1 - 3 above. We recommend that you follow [Semantic Versioning](http://semver.org/) while bumping your theme-version.

docs/_docs/upgrading.md

@@ -1,29 +0,0 @@
----
-layout: docs
-title: Upgrading
-permalink: /docs/upgrading/
----
-
-Upgrading from an older version of Jekyll? Upgrading to a new major version of
-Jekyll (e.g. from v2.x to v3.x) may cause some headaches. Take the following
-guides to aid your upgrade:
-
-- [From 0.x to 1.x and 2.x](/docs/upgrading/0-to-2/)
-- [From 2.x to 3.x](/docs/upgrading/2-to-3/)
-
-## Minor updates
-
-<div class="note">
-  <h5>Stay Up to Date</h5>
-  <p>We recommend you update Jekyll as often as possible to benefit from
-  the latest bug fixes.
-  </p>
-</div>
-
-If you followed our setup recommendations and installed [Bundler](http://bundler.io/), run `bundle update jekyll` or simply `bundle update` and all your gems will
-update to the latest versions.
-
-If you don't have Bundler installed, run `gem update jekyll`.
-
-The procedure is similar [if you use the `github-pages`
-gem](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/#keeping-your-site-up-to-date-with-the-github-pages-gem).

docs/_docs/upgrading/3-to-4.md

@@ -1,51 +0,0 @@
----
-title: Upgrading from 3.x to 4.x
-permalink: /docs/upgrading/3-to-4/
----
-
-Upgrading from an older version of Jekyll? A few things have changed in Jekyll 4
-that you'll want to know about.
-
-Before we dive in, you need to have at least Ruby 2.3.0 installed. Run the following
-in your terminal to check
-
-```sh
-ruby -v
-```
-
-If you're using Ruby >= 2.3.0, go ahead and fetch the latest version of Jekyll:
-
-```sh
-gem update jekyll
-```
-
-
-### Template rendering
-
-We've slightly altered the way Jekyll parses and renders your various templates to improve
-the overall build times. Jekyll now parses a template once, caches it internally and then
-renders the parsed template multiple times as required by your pages and documents.
-
-The downside to this is that some of the community-authored plugins may not work as they
-previously used to.
-
-#### For Plugin-authors
-
-* If your plugin depends on the following code: `site.liquid_renderer.file(path).parse(content)`,
-note that the return value (`template`, an instance of *`Liquid::Template`*), from that line will
-always be the **same object** for a given `path`. <br/>
-The *`template`* instance is then rendered as previously, with respect to the `payload` passed to it.
-You'll therefore have to ensure that *`payload`* is not memoized or cached in your plugin instance.
-
-* If its a requirement that `template` you get from the above step *be different* at all times,
-you can invoke *`Liquid::Template`* directly:
-
-
-  ```diff
-  - template = site.liquid_renderer.file(path).parse(content)
-  + template = Liquid::Template.parse(content)
-  ```
-
----
-
-*Did we miss something? Please click "Improve this page" above and add a section. Thanks!*

docs/_docs/windows.md

@@ -1,138 +0,0 @@
----
-title: Jekyll on Windows
-permalink: /docs/windows/
----
-
-While Windows is not an officially-supported platform, it can be used to run Jekyll with the proper tweaks. This page aims to collect some of the general knowledge and lessons that have been unearthed by Windows users.
-
-
-## Installing Jekyll
-The easiest way to run Jekyll is by using the [RubyInstaller][] for Windows.
-
-### Installation via RubyInstaller
-
-[RubyInstaller][] is a self-contained Windows-based installer that includes the Ruby language, an execution environment, important documentation, and more.
-We only cover RubyInstaller-2.4 and newer here, older versions need to [install the Devkit][Devkit-install] manually.
-
-1. Download and Install a **Ruby+Devkit** version from [RubyInstaller Downloads][RubyInstaller-downloads].
-   Use default options for installation.
-2. Open a new command prompt window from the start menu, so that changes to the `PATH` environment variable becomes effective.
-   Install Jekyll and Bundler via: `gem install jekyll bundler`
-3. Check if Jekyll installed properly: `jekyll -v`
-
-That's it, you're ready to install our [default minimal blog theme](https://github.com/jekyll/minima) with `jekyll new jekyll-website`.
-
-[RubyInstaller]: https://rubyinstaller.org/
-[RubyInstaller-downloads]: https://rubyinstaller.org/downloads/
-[Devkit-install]: https://github.com/oneclick/rubyinstaller/wiki/Development-Kit
-
-
-### Encoding
-
-If you use UTF-8 encoding, make sure that no `BOM` header characters exist in your files or very, very bad things will happen to
-Jekyll. This is especially relevant when you're running Jekyll on Windows.
-
-Additionally, you might need to change the code page of the console window to UTF-8 in case you get a "Liquid Exception: Incompatible character encoding" error during the site generation process. It can be done with the following command:
-
-```sh
-chcp 65001
-```
-
-
-### Time-Zone Management
-
-Since Windows doesn't have a native source of zoneinfo data, the Ruby Interpreter would not understand IANA Timezones and hence using them had the `TZ` environment variable default to UTC/GMT 00:00.
-Though Windows users could alternatively define their blog's timezone by setting the key to use POSIX format of defining timezones, it wasn't as user-friendly when it came to having the clock altered to changing DST-rules.
-
-Jekyll now uses a rubygem to internally configure Timezone based on established [IANA Timezone Database][IANA-database].
-While 'new' blogs created with Jekyll v3.4 and greater, will have the following added to their 'Gemfile' by default, existing sites *will* have to update their 'Gemfile' (and installed) to enable development on Windows:
-
-```ruby
-# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
-gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
-```
-
-[IANA-database]: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
-
-### Auto Regeneration
-
-Jekyll uses the `listen` gem to watch for changes when the `--watch` switch is specified during a build or serve. While `listen` has built-in support for UNIX systems, it may require an extra gem for compatibility with Windows.
-
-Add the following to the Gemfile for your site if you have issues with auto-regeneration on Windows alone:
-
-```ruby
-gem 'wdm', '~> 0.1.1' if Gem.win_platform?
-```
-
-You have to use a [Ruby+Devkit](https://rubyinstaller.org/downloads/) version of the RubyInstaller.
-
-
-## Installation via Bash on Windows 10
-
-If you are using Windows 10 version 1607 or later, another option to run Jekyll is by [installing][WSL-Guide] the Windows Subsystem for Linux.
-
-
-*Note:* You must have [Windows Subsystem for Linux][BASH-WSL] enabled.
-
-First let's make sure all our packages / repositories are up to date. Open a new Command Prompt instance, and type the following:
-
-```sh
-bash
-```
-Your Command Prompt instance should now be a Bash instance. Now we must update our repo lists and packages.
-
-```sh
-sudo apt-get update -y && sudo apt-get upgrade -y
-```
-Now we can install Ruby. To do this we will use a repository from [BrightBox](https://www.brightbox.com/docs/ruby/ubuntu/), which hosts optimized versions of Ruby for Ubuntu.
-
-```sh
-sudo apt-add-repository ppa:brightbox/ruby-ng
-sudo apt-get update
-sudo apt-get install ruby2.4 ruby2.4-dev build-essential dh-autoreconf
-```
-
-Next let's update our Ruby gems:
-
-```sh
-sudo gem update
-```
-
-Now all that is left to do is install Jekyll.
-
-```sh
-sudo gem install jekyll bundler
-```
-
-Check if Jekyll installed properly by running:
-
-```sh
-jekyll -v
-```
-
-Configure the bundler/gem path so bundle doesn't prompt for sudo
-
-```sh
-bundle config path vendor/bundle
-```
-
-**And that's it!**
-
-To start a new project named `my_blog`, just run:
-
-```sh
-jekyll new my_blog
-```
-
-You can make sure time management is working properly by inspecting your `_posts` folder. You should see a markdown file with the current date in the filename.
-
-<div class="note info">
-  <h5>Non-superuser account issues</h5>
-  <p>If the `jekyll new` command prints the error "Your user account isn't allowed to install to the system RubyGems", see the "Running Jekyll as Non-Superuser" instructions in <a href="/docs/troubleshooting/#no-sudo">Troubleshooting</a>.</p>
-</div>
-
-**Note:** Bash on Ubuntu on Windows is still under development, so you may run into issues.
-
-[WSL-Guide]: https://msdn.microsoft.com/en-us/commandline/wsl/install_guide
-[BASH-WSL]: https://msdn.microsoft.com/en-us/commandline/wsl/about
-

docs/_includes/analytics.html

@@ -1,13 +0,0 @@
-{% if site.google_analytics_id %}
-  <!-- Google Analytics (https://www.google.com/analytics) -->
-  <script>
-    !function(j,e,k,y,l,L){j.GoogleAnalyticsObject=y,j[y]||(j[y]=function(){
-    (j[y].q=j[y].q||[]).push(arguments)}),j[y].l=+new Date,l=e.createElement(k),
-    L=e.getElementsByTagName(k)[0],l.src='https://www.google-analytics.com/analytics.js',
-    L.parentNode.insertBefore(l,L)}(window,document,'script','ga');
-
-    ga('create', '{{ site.google_analytics_id }}', 'jekyllrb.com');
-    ga('send', 'pageview');
-
-  </script>
-{% endif %}

docs/_includes/docs_option.html

@@ -1,5 +0,0 @@
-{% for item in include.items %}
-  {% assign item_url = item | prepend:"/docs/" | append:"/" %}
-  {% assign doc = site.docs | where: "url", item_url | first %}
-  <option value="{{ doc.url }}">{{ doc.title }}</option>
-{% endfor %}

docs/_includes/docs_ul.html

@@ -1,7 +0,0 @@
-<ul>
-{% for item in include.items %}
-  {% assign item_url = item | prepend:"/docs/" | append:"/" %}
-  {% assign p = site.docs | where:"url", item_url | first %}
-  <li class="{% if item_url == page.url %}current{% endif %}"><a href="{{ p.url }}">{{ p.title }}</a></li>
-{% endfor %}
-</ul>

docs/_includes/docs_version_badge.html

@@ -1 +0,0 @@
-<span class="version-badge" title="This feature is available starting version {{ include.version }}">{{ include.version }}</span>

docs/_includes/header.html

@@ -1,31 +0,0 @@
-<header>
-  <div class="flexbox">
-    <div class="center-on-mobiles">
-      <h1>
-        <a href="/" class="logo">
-          <span class="sr-only">Jekyll</span>
-          <img src="/img/logo-2x.png" width="140" height="65" alt="Jekyll Logo">
-        </a>
-      </h1>
-    </div>
-    <nav class="main-nav hide-on-mobiles">
-      {% include primary-nav-items.html %}
-    </nav>
-    <div class="search hide-on-mobiles">
-      {% include search/input.html %}
-    </div>
-    <div class="meta hide-on-mobiles">
-      <ul>
-        <li>
-          <a href="{{ site.repository }}/releases/tag/v{{ site.version }}">v{{ site.version }}</a>
-        </li>
-        <li>
-          <a href="{{ site.repository }}">GitHub</a>
-        </li>
-      </ul>
-    </div>
-  </div>
-  <nav class="mobile-nav show-on-mobiles">
-    {% include mobile-nav-items.html %}
-  </nav>
-</header>

docs/_includes/primary-nav-items.html

@@ -1,14 +0,0 @@
-<ul>
-  <li class="{% if page.overview %}current{% endif %}">
-    <a href="/">Home</a>
-  </li>
-  <li class="{% if page.url contains '/docs/' %}current{% endif %}">
-    <a href="/docs/home/">Docs</a>
-  </li>
-  <li class="{% if page.author %}current{% endif %}">
-    <a href="/news/">News</a>
-  </li>
-  <li class="{% if page.url contains '/help/' %}current{% endif %}">
-    <a href="/help/">Help</a>
-  </li>
-</ul>

docs/_includes/search/input.html

@@ -1 +0,0 @@
-<input type="text" id="docsearch-input" placeholder="Search the docs…">

docs/_includes/search/script.html

@@ -1,9 +0,0 @@
-<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script>
-<script type="text/javascript"> docsearch({
-apiKey: '50fe39c839958dfad797000f33e2ec17',
-indexName: 'jekyllrb',
-inputSelector: '#docsearch-input',
-enhancedSearchInput: true,
-debug: false // Set debug to true if you want to inspect the dropdown
-});
-</script>

docs/_includes/section_nav_tutorials.html

@@ -1,39 +0,0 @@
-{% comment %}
-Map grabs the tutorials sections, giving us an array of arrays. Join, flattens all
-the items to a comma delimited string. Split turns it into an array again.
-{% endcomment %}
-{% assign tutorials = site.data.tutorials | map: 'tutorials' | join: ',' | split: ',' %}
-
-{% comment %}
-Because this is built for every page, lets find where we are in the ordered
-document list by comparing url strings. Then if there's something previous or
-next, lets build a link to it.
-{% endcomment %}
-
-{% for tutorial in tutorials %}
-  {% assign tutorial_url = tutorial | prepend:"/tutorials/" | append:"/" %}
-  {% if tutorial_url == page.url %}
-    <div class="section-nav">
-      <div class="left align-right">
-          {% if forloop.first %}
-            <span class="prev disabled">Back</span>
-          {% else %}
-            {% assign previous = forloop.index0 | minus: 1 %}
-            {% assign previous_page = tutorials[previous] | prepend:"/tutorials/" | append:"/" %}
-            <a href="{{ previous_page }}" class="prev">Back</a>
-          {% endif %}
-      </div>
-      <div class="right align-left">
-          {% if forloop.last %}
-            <span class="next disabled">Next</span>
-          {% else %}
-            {% assign next = forloop.index0 | plus: 1 %}
-            {% assign next_page = tutorials[next] | prepend:"/tutorials/" | append:"/" %}
-            <a href="{{ next_page }}" class="next">Next</a>
-          {% endif %}
-      </div>
-    </div>
-    <div class="clear"></div>
-    {% break %}
-  {% endif %}
-{% endfor %}

docs/_includes/tutorials_contents.html

@@ -1,10 +0,0 @@
-<div class="unit one-fifth hide-on-mobiles">
-  <aside>
-    {% for section in site.data.tutorials %}
-    <h4>{{ section.title }}</h4>
-
-   {% include tutorials_ul.html items=section.tutorials %}
-
-    {% endfor %}
-  </aside>
-</div>

docs/_includes/tutorials_contents_mobile.html

@@ -1,10 +0,0 @@
-<div class="docs-nav-mobile unit whole show-on-mobiles">
-  <select onchange="if (this.value) window.location.href=this.value">
-    <option value="">Navigate the tutorials…</option>
-    {% for section in site.data.tutorials %}
-    <optgroup label="{{ section.title }}">
-      {% include tutorials_option.html items=section.tutorials %}
-    </optgroup>
-    {% endfor %}
-  </select>
-</div>

docs/_includes/tutorials_option.html

@@ -1,5 +0,0 @@
-{% for item in include.items %}
-  {% assign item_url = item | prepend:"/tutorials/" | append:"/" %}
-  {% assign tutorial = site.tutorials | where: "url", item_url | first %}
-  <option value="{{ tutorial.url }}">{{ tutorial.title }}</option>
-{% endfor %}

docs/_includes/tutorials_ul.html

@@ -1,7 +0,0 @@
-<ul>
-{% for item in include.items %}
-  {% assign item_url = item | prepend:"/tutorials/" | append:"/" %}
-  {% assign p = site.tutorials | where:"url", item_url | first %}
-  <li class="{% if item_url == page.url %}current{% endif %}"><a href="{{ p.url }}">{{ p.title }}</a></li>
-{% endfor %}
-</ul>

docs/_layouts/error.html

@@ -1,23 +0,0 @@
-{% include top.html %}
-
-<body class="wrap">
-  <header>
-    <div class="grid">
-      <div class="unit whole align-center">
-        <h1>
-          <a href="/">
-            <span class="sr-only">Jekyll</span>
-            <img src="/img/logo-2x.png" width="249" height="115" alt="Jekyll Logo">
-          </a>
-        </h1>
-      </div>
-    </div>
-  </header>
-
-  {{ content }}
-
-  {% include anchor_links.html %}
-  {% include analytics.html %}
-
-</body>
-</html>

docs/_layouts/tutorials.html

@@ -1,27 +0,0 @@
----
-layout: default
----
-
-  <section class="docs">
-    <div class="grid">
-
-      {% include tutorials_contents_mobile.html %}
-
-      <div class="unit four-fifths">
-        <article>
-          <div class="improve right hide-on-mobiles">
-            <a href="https://github.com/jekyll/jekyll/edit/master/docs/{{ page.path }}"><i
-                    class="fa fa-pencil"></i> &nbsp;Improve this page</a>
-          </div>
-          <h1>{{ page.title }}</h1>
-          {{ content }}
-          {% include section_nav_tutorials.html %}
-        </article>
-      </div>
-
-      {% include tutorials_contents.html %}
-
-      <div class="clear"></div>
-
-    </div>
-  </section>

docs/_posts/2013-07-24-jekyll-1-1-1-released.markdown

@@ -1,23 +0,0 @@
----
-title: "Jekyll 1.1.1 Released"
-date: "2013-07-24 22:24:14 +0200"
-author: parkr
-version: 1.1.1
-categories: [release]
----
-
-Coming just 10 days after the release of v1.1.0, v1.1.1 is out with a patch for
-the nasty excerpt inception bug ([#1339]({{ site.repository }}/issues/1339)) and
-non-zero exit codes for invalid commands ([#1338]({{ site.repository
-}}/issues/1338)).
-
-To all those affected by the [strange excerpt bug in v1.1.0]({{ site.repository
-}}/issues/1321), I'm sorry. I think we have it all patched up and it should be
-deployed to [GitHub Pages](https://pages.github.com/) in the next couple weeks.
-Thank you for your patience!
-
-If you're checking out v1.1.x for the first time, definitely check out [what
-shipped with v1.1.0!]({{ site.repository }}/releases/tag/v1.1.0)
-
-See the [GitHub Release]({{ site.repository }}/releases/tag/v1.1.1) page for
-more a more detailed changelog for this release.

docs/_posts/2016-03-10-making-it-easier-to-contribute-to-jekyll.md

@@ -1,16 +0,0 @@
----
-title: Making it easier to contribute to Jekyll
-description: We've made it easier to contribute to Jekyll by updating our contributing documentation and introducing Jekyll Affinity Teams, teams dedicated to specific aspects of the project.
-author: benbalter
-categories: [community]
----
-
-Jekyll is an open source project, built one contribution at a time by community members just like you. These community contributions can come in many forms beyond just writing code, from reporting an issue or suggesting a new feature to improving documentation or providing feedback on proposed changes.
-
-If you've been looking to get involved with the Jekyll community, but didn't know, we've recently made it easier to contribute to Jekyll in two ways:
-
-First, we've completely rewritten [the project's contributing guidelines](https://jekyllrb.com/docs/contributing/), outlining [the various ways you can contribute](https://jekyllrb.com/docs/contributing/#ways-to-contribute), and including better instructions for [submitting proposed changes via GitHub.com](https://jekyllrb.com/docs/contributing/#submitting-a-pull-request-via-githubcom) or for [submitting your first code improvement](https://jekyllrb.com/docs/contributing/#code-contributions). And if you have any feedback, we'd love to hear it! Simply click the "improve this page" button in the top right corner of the contributing documentation.
-
-Second, this week, we created six community interest groups, we're calling [Jekyll affinity teams](https://teams.jekyllrb.com). If you're interested in a particular aspect of the project (or just want to learn more), you can join any one of these teams (or two, or three), to participate in discussions about potential bugs and proposed improvements. And the best part is there's no commitment. If you just want to listen, or if at any point you want to leave (or switch teams), that's totally fine. We won't say a thing. To learn more about the various affinity teams, or to join one (please do!), just head on over to [teams.jekyllrb.com](https://teams.jekyllrb.com/).
-
-We hope these changes will make it easier for you to make your first (or second, or third) contribution to Jekyll today. Thanks for helping to make Jekyll awesome!

docs/_posts/2016-04-19-jekyll-3-0-4-released.markdown

@@ -1,23 +0,0 @@
----
-title: 'Jekyll 3.0.4 Released'
-date: 2016-04-19 10:26:12 -0700
-author: parkr
-version: 3.0.4
-categories: [release]
----
-
-v3.0.4 is a patch release which fixes the follow two issues:
-
-- Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source
-- Configuration for the posts permalink might be borked when a user specified a value for `collections.posts.permalink` directly. This forced the use of `permalink` at the top level, which also affected pages. To configure a permalink _just for posts_, you can do so with:
-
-{% highlight yaml %}
-collections:
-  posts:
-    output: true
-    permalink: /blog/:year/:title/
-{% endhighlight %}
-
-Both of these issues have been resolved. For more information, check out [the full history](/docs/history/#v3-0-4).
-
-Happy Jekylling!

docs/_posts/2016-04-19-jekyll-3-1-3-released.markdown

@@ -1,16 +0,0 @@
----
-title: 'Jekyll 3.1.3 Released'
-date: 2016-04-19 10:26:16 -0700
-author: parkr
-version: 3.1.3
-categories: [release]
----
-
-v3.1.3 is a patch release which fixes the follow two issues:
-
-- Front matter defaults may not have worked for collection documents and posts due to a problem where they were looked up by their URL rather than their path relative to the site source
-- Running `jekyll serve` with SSL enabled was broken due to a bad configuration.
-
-Both of these issues have been resolved. For more information, check out [the full history](/docs/history/#v3-1-3).
-
-Happy Jekylling!

docs/_posts/2016-04-26-jekyll-3-0-5-released.markdown

@@ -1,24 +0,0 @@
----
-title: 'Jekyll 3.0.5 Released'
-date: 2016-04-26 17:40:44 -0700
-author: parkr
-version: 3.0.5
-categories: [release]
----
-
-This version fixes a bug affecting only v3.0.4 where autoregeneration was
-*always* disabled when running Jekyll locally. This feature is a huge
-reason why Jekyll (or any static site generator, for that matter) is a joy
-to use. Sorry for the regression!
-
-If you're using GitHub Pages, [you can follow the progress of the upgrade
-on the github/pages-gem repo](https://github.com/github/pages-gem/pull/285).
-
-As always, our [history doc](/docs/history/#v3-0-5) has links to the pull
-requests and issues associated with the release for your perusal.
-
-We're looking forward to the upcoming release of v3.2 which [has some
-excellent goodies](https://github.com/jekyll/jekyll/blob/master/History.markdown#head)
-we think you'll love.
-
-Happy Jekylling!

docs/_posts/2016-05-18-jekyll-3-1-4-released.markdown

@@ -1,25 +0,0 @@
----
-title: 'Jekyll 3.1.4 "Stability Sam" Released'
-date: 2016-05-18 16:50:37 -0700
-author: parkr
-version: 3.1.4
-categories: [release]
----
-
-Hey Jekyllites!
-
-Today, we released v3.1.4 in an effort to bring more stability to the v3.1.x series. This bugfix release consists of:
-
-* A fix for `layout` in Liquid where values would carry over from one document to the next
-* A fix for `layout` in Liquid where a parent layout (e.g. `default` or `base`) would overwrite the metadata of the child layout (e.g. `post` or `special`).
-* A fix where `page.excerpt` referencing its excerpt would cause an infinite loop of recursive horror.
-* We added `Configuration.from` and the great permalink fix from [v3.0.4](/news/2016/04/19/jekyll-3-0-4-released/) to the v3.1.x series
-* `site.collections` in Liquid is now sorted alphabetically by label, so `docs` shows up before `posts` reliably.
-
-The fixes for `layout` may not be seamless for everyone, but we believe they will be the "right thing to do" going forward.
-
-We are alwawys striving to make Jekyll more straight-forward to use. Please do open an issue if you believe an aspect of Jekyll's user experience isn't up to par.
-
-For a full history of our changes, [see the changelog](/docs/history/#v3-1-4).
-
-As always, Happy Jekylling!

docs/_posts/2016-05-18-jekyll-3-1-5-released.markdown

@@ -1,16 +0,0 @@
----
-title: 'Jekyll 3.1.5 Released'
-date: 2016-05-18 21:35:27 -0700
-author: parkr
-version: 3.1.5
-categories: [release]
----
-
-There's always at least one bug, right? :)
-
-Hot on the trails of [v3.1.4](/news/2016/05/18/jekyll-3-1-4-released/), we
-bring you v3.1.5! It fixes one bug around requiring the `ExcerptDrop`,
-which only affects Linux. For the gory details, see [the pull
-request for the fix](https://github.com/jekyll/jekyll/pull/4912).
-
-Happy Jekylling!

docs/_posts/2016-05-19-jekyll-3-1-6-released.markdown

@@ -1,18 +0,0 @@
----
-title: 'Jekyll 3.1.6 Released'
-date: 2016-05-19 12:48:14 -0700
-author: parkr
-version: 3.1.6
-categories: [release]
----
-
-Upon releasing 3.1.5 and kicking the tires, we noticed a glaring bug: our
-beloved `jsonify` filter doesn't work! With that, our work was cut out for
-us and we decided a 3.1.6 was necessary. This release restores sanity to
-our object-to-JSON generation in Liquid and we hope you enjoy.
-
-For the gory details, see [the pull
-request](https://github.com/jekyll/jekyll/pull/4914) or [the
-changelog](/docs/history/#v3-1-6).
-
-Happy Jekylling!

docs/_posts/2016-06-03-update-on-jekyll-s-google-summer-of-code-projects.markdown

@@ -1,18 +0,0 @@
----
-title: "Jekyll's Google Summer of Code Project: The CMS You Always Wanted"
-date: "2016-06-03 13:21:02 -0700"
-author: parkr
-categories: [community]
----
-
-This year, Jekyll applied to be a part of [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works/). Students were able to propose any project related to Jekyll. With a gracious sponsorship from GitHub and the participation of myself, @benbalter and @jldec, Jekyll was able to accept two students for the 2016 season, @mertkahyaoglu and @rush-skills.
-
-These students are working on a project that fills a huge need for the community: _a graphical solution for managing your site's content._ Current plans include a fully-integrated admin which spins up when you run jekyll serve and provides a friendly web interface for creating and editing your content. The server and web interface will speak a common HTTP interface so either piece could be switched out for, e.g. a server which writes directly to a repository on GitHub.
-
-The strength of text files as the storage medium for content has been part of Jekyll's success. [Our homepage](/) lauds the absence of a traditional SQL database when using Jekyll – your content should be what demands your time, not pesky database downtime. Unfortunately, understanding of the structure of a Jekyll site takes some work, enough that for some users, it's prohibitive to using Jekyll to accomplish their publishing goals.
-
-Mert and Ankur both applied to take on this challenge and agreed to split the project, one taking on the web interface and the other taking on the backend. We're very excited to see a fully-functional CMS for Jekyll at the end of the summer produced by these excellent community members, and we hope you'll join us in cheering them on and sharing our gratitude for all their hard work.
-
-Thanks, as always, for being part of such a wonderful community that made this all possible. I'm honored to work with each of you to create something folks all around the globe find a joy to use. I look forward to our continued work to move Jekyll forward.
-
-As always, Happy Jekylling!

docs/_posts/2016-07-26-jekyll-3-2-0-released.markdown

@@ -1,124 +0,0 @@
----
-title: 'Jekyll turns 3.2'
-date: 2016-07-26 15:06:49 -0700
-author: parkr
-version: 3.2.0
-categories: [release]
----
-
-Happy Day! Jekyll v3.2.0 is out, and packed full of goodies.
-
-Our flagship feature for this release has been **themes**. _Themes?!_, you
-say? Yes, proper, versionable, releasable, first-class themes. We're pretty
-stoked about it and we hope you like building and using them. For now, it
-only supports layouts, includes, and sass, but we have plans to include
-static assets like images and CSS/JS in a future release. [Read more about
-it in the docs.](/docs/themes/) Our site template generated by `jekyll new`
-now dogfoods this feature, using the [minima](https://github.com/jekyll/minima) theme.
-
-Some other notable changes:
-
-- Symlinks are allowed as long as they target a file in the site source
-- Explicit support for Ruby 2.0.x was dropped
-- Added an `:after_init` Hook
-- Added a `where_exp` filter to provide more powerful filtering
-- Added a `link` liquid tag which can be used to generate URLs for any
-post or document based on its path relative to the site source
-- ... and lots more!
-
-As always, there is [a full list of changes](/docs/history/#v3-2-0) for
-your perusal.
-
-Every release is made possible by the countless hours of hard work that our
-fellow community members put into sending patches, filing thoughtful
-patches, and so on. These release took the work of over 80 people:
-
-- Aaron Sky
-- Adam Hollett
-- ajhit406
-- Aki
-- Alex Hanselka
-- Alex Hoyau
-- Alex Ivkin
-- Alex Kitchens
-- Alex Plescan
-- Alex Wood
-- Anatoliy Yastreb
-- Andrew Artajos
-- Andrew Munsell
-- AndrewCz
-- Ankush Menat
-- Anthony Smith
-- Ben Balter
-- Brian Jones
-- Brint O'Hearn
-- Chayoung You
-- Chris Wells
-- chrisfinazzo
-- Clark Winkelmann
-- Dan Allen
-- David Von Lehman
-- David Zhang
-- Derek Gottlieb
-- Enes Gönültaş
-- EricH
-- Erick Sasse
-- Eugênio Cabral
-- Florian Thomas
-- Frank Taillandier
-- Henry Goodman
-- Henry Wright
-- Hugo Duksis
-- Hugo Giraudel
-- Jack Reed
-- Jamie Bilinski
-- Jeff Kolesky
-- Jens Willmer
-- Jordon Bedwell
-- Josh Waller
-- Joshua Barnett
-- Keegan Mullaney
-- Kevin Miller
-- Krzysztof Jurewicz
-- Loren Rogers
-- Marcos Brito
-- Marcus Stollsteimer
-- Matt Rogers
-- Michaël Guitton
-- Mike Linksvayer
-- Mike Neumegen
-- Nathan Hazout
-- Nick
-- No
-- nscyclone
-- Parker Moore
-- Pat Hawks
-- Pierre Fenoll
-- Praveen Kumar
-- Rares Vernica
-- Saleem Rashid
-- Sam Dutton
-- Shengbin Meng
-- Shinn Kondo
-- Shinnosuke Kondo
-- skim
-- Sondre Nilsen
-- Spencer A. Bywater
-- Stephen Checkoway
-- Suriyaa Kudo
-- surrim
-- TheLucasMoore
-- Thomas Wood
-- Tim Wisniewski
-- Tom Fejfar
-- Tony Garnock-Jones
-- Vincent Wochnik
-- XhmikosR
-- Yanis Vieilly
-- Yordis Prieto
-- Zack Spencer
-
-We are so grateful to all of you for helping to put together a terrific
-release. Thank you!
-
-Happy Jekylling!

docs/_posts/2016-08-02-jekyll-3-2-1-released.markdown

@@ -1,23 +0,0 @@
----
-title: 'Jekyll 3.2.1 Released with Fix for Windows'
-date: 2016-08-02 13:20:11 -0700
-author: parkr
-version: 3.2.1
-categories: [release]
----
-
-Well, 3.2.0 has been a success, but with one fatal flaw: it doesn't work on
-Windows! Sorry, Windows users. Hot on the trail of 3.2.0, this release
-should squash that :bug:. Sorry about that!
-
-This release also fixes an issue when using [gem-based themes](/docs/themes/)
-where the theme was rejected if it existed behind a symlink. This is a
-common setup for the various ruby version managers, and for Ruby installed
-via Homebrew. Props to @benbalter for fixing that up.
-
-Thanks to the contributors for this release: Adam Petrie, Ben Balter,
-Daniel Chapman, DirtyF, Gary Ewan Park, Jordon Bedwell, and Parker Moore.
-
-As always, you can see our full changelog on [the History page](/docs/history/).
-
-Happy Jekylling!

docs/_posts/2016-08-24-jekyll-admin-initial-release.markdown

@@ -1,17 +0,0 @@
----
-title: "Jekyll Admin Initial Release"
-date: "2016-08-25 09:50:00 +0300"
-author: mertkahyaoglu
-categories: [community]
----
-
-[Jekyll's Google Summer of Code Project](https://jekyllrb.com/news/2016/06/03/update-on-jekyll-s-google-summer-of-code-projects/) has concluded. After three months of hard (but fun) work with my mentors @benbalter, @jldec, and @parkr, I'm proud to announce [Jekyll Admin](https://github.com/jekyll/jekyll-admin)'s [initial release](https://github.com/jekyll/jekyll-admin/releases/tag/v0.1.0). Jekyll admin is a Jekyll plugin that provides users with a traditional CMS-style graphical interface to author content and administer Jekyll sites. You can start to use it right away by following [these instructions](https://github.com/jekyll/jekyll-admin#installation).
-
-As a Google Summer of Code student, I feel very lucky to be part of a project that the community has been wanting for such a long time. The three-month Google Summer of Code period was a great journey. It was a lot of fun developing the project and seeing how it could help the community, and going forward, we are really excited to see where the project goes with the help of the amazing Jekyll community.
-
-I would like to thank my mentors who embraced me as their teammate and guided me throughout the process. They have put a lot of work and time to mentor me and helped me with everything. It was a great pleasure to work with them. I also would like to thank the wonderful Jekyll community for making Jekyll what it is today. It was amazing to see the community contribute to the project and give their feedback
-prior to its release. I'm sure that they will support Jekyll Admin as much as they can and move Jekyll even further.
-
-Please let us know what you think about [Jekyll Admin](https://github.com/jekyll/jekyll-admin) and feel free to [contribute](https://github.com/jekyll/jekyll-admin/blob/master/.github/CONTRIBUTING.md). Your feedback and contributions are greatly appreciated.
-
-Happy (graphical) Jekylling!

docs/_posts/2016-10-06-jekyll-3-3-is-here.md

@@ -1,109 +0,0 @@
----
-title: 'Jekyll 3.3 is here with better theme support, new URL filters, and tons more'
-date: 2016-10-06 11:10:38 -0700
-author: parkr
-version: 3.3.0
-categories: [release]
----
-
-There are tons of great new quality-of-life features you can use in 3.3.
-Three key things you might want to try:
-
-### 1. Themes can now ship static & dynamic assets in an `/assets` directory
-
-In Jekyll 3.2, we shipped the ability to use a theme that was packaged as a
-[gem](http://guides.rubygems.org/). 3.2 included support for includes,
-layouts, and sass partials. In 3.3, we're adding assets to that list.
-
-In an effort to make theme management a bit easier, any files you put into
-`/assets` in your theme will be read in as though they were part of the
-user's site. This means you can ship SCSS and CoffeeScript, images and
-webfonts, and so on -- anything you'd consider a part of the
-*presentation*. Same rules apply here as in a Jekyll site: if it has YAML
-front matter, it will be converted and rendered. No YAML front matter, and
-it will simply be copied over like a static asset.
-
-Note that if a user has a file of the same path, the theme content will not
-be included in the site, i.e. a user's `/assets/main.scss` will be read and
-processed if present instead of a theme's `/assets/main.scss`.
-
-See our [documentation on the subject]({{ "/docs/themes/#assets" | relative_url }})
-for more info.
-
-### 2. `relative_url` and `absolute_url` filters
-
-Want a clean way to prepend the `baseurl` or `url` in your config? These
-new filters have you covered. When working locally, if you set your
-`baseurl` to match your deployment environment, say `baseurl: "/myproject"`,
-then `relative_url` will ensure that this baseurl is prepended to anything
-you pass it:
-
-{% highlight liquid %}
-{% raw %}
-{{ "/docs/assets/" | relative_url }} => /myproject/docs/assets
-{% endraw %}
-{% endhighlight %}
-
-By default, `baseurl` is set to `""` and therefore yields (never set to
-`"/"`):
-
-{% highlight liquid %}
-{% raw %}
-{{ "/docs/assets/" | relative_url }} => /docs/assets
-{% endraw %}
-{% endhighlight %}
-
-A result of `relative_url` will safely always produce a URL which is
-relative to the domain root. A similar principle applies to `absolute_url`.
-It prepends your `baseurl` and `url` values, making absolute URLs all the
-easier to make:
-
-{% highlight liquid %}
-{% raw %}
-{{ "/docs/assets/" | absolute_url }} => https://jekyllrb.com/myproject/docs/assets
-{% endraw %}
-{% endhighlight %}
-
-### 3. `site.url` is set by the development server
-
-When you run `jekyll serve` locally, it starts a web server, usually at
-`http://localhost:4000`, that you use to preview your site during
-development. If you are using the new `absolute_url` filter, or using
-`site.url` anywhere, you have probably had to create a development config
-which resets the `url` value to point to `http://localhost:4000`.
-
-No longer! When you run `jekyll serve`, Jekyll will build your site with
-the value of the `host`, `port`, and SSL-related options. This defaults to
-`url: http://localhost:4000`. When you are developing locally, `site.url`
-will yield `http://localhost:4000`.
-
-This happens by default when running Jekyll locally. It will not be set if
-you set `JEKYLL_ENV=production` and run `jekyll serve`. If `JEKYLL_ENV` is
-any value except `development` (its default value), Jekyll will not
-overwrite the value of `url` in your config. And again, this only applies
-to serving, not to building.
-
-## A *lot* more!
-
-There are dozens of bug fixes and minor improvements to make your Jekyll
-experience better than ever. With every Jekyll release, we strive to bring
-greater stability and reliability to your everyday development workflow.
-
-As always, thanks to our many contributors who contributed countless hours
-of their free time to making this release happen:
-
-Anatoliy Yastreb, Anthony Gaudino, Antonio, Ashwin Maroli, Ben Balter,
-Charles Horn, Chris Finazzo, Daniel Chapman, David Zhang, Eduardo
-Bouças, Edward Thomson, Eloy Espinaco, Florian Thomas, Frank Taillandier,
-Gerardo, Heng Kwokfu, Heng, K. (Stephen), Jeff Kolesky, Jonathan Thornton,
-Jordon Bedwell, Jussi Kinnula, Júnior Messias, Kyle O'Brien, Manmeet Gill,
-Mark H. Wilkinson, Marko Locher, Mertcan GÖKGÖZ, Michal Švácha, Mike
-Kasberg, Nadjib Amar, Nicolas Hoizey, Nicolas Porcel, Parker Moore, Pat
-Hawks, Patrick Marsceill, Stephen Checkoway, Stuart Kent, XhmikosR, Zlatan
-Vasović, mertkahyaoglu, shingo-nakanishi, and vohedge.
-
-[Full release notes]({{ "/docs/history/#v3-3-0" | relative_url }}) are available
-for your perusal. If you notice any issues, please don't hesitate to file a
-bug report.
-
-Happy Jekylling!