Handle Liquid v4 'empty' and 'blank' values explicitly

Prevents a lookup error since Liquid::Expression::MethodLiteral doesn't exist in v5

.devcontainer/Dockerfile

@@ -0,0 +1,55 @@
+#-------------------------------------------------------------------------------------------------------------
+# Copyright (c) Microsoft Corporation. All rights reserved.
+# Licensed under the MIT License. See https://go.microsoft.com/fwlink/?linkid=2090316 for license information.
+#-------------------------------------------------------------------------------------------------------------
+
+FROM ruby:2
+
+# Avoid warnings by switching to noninteractive
+ENV DEBIAN_FRONTEND=noninteractive
+
+# This Dockerfile adds a non-root user with sudo access. Use the "remoteUser"
+# property in devcontainer.json to use it. On Linux, the container user's GID/UIDs
+# will be updated to match your local UID/GID (when using the dockerFile property).
+# See https://aka.ms/vscode-remote/containers/non-root-user for details.
+ARG USERNAME=vscode
+ARG USER_UID=1000
+ARG USER_GID=$USER_UID
+
+# Configure apt and install packages
+RUN apt-get update \
+    && apt-get -y install --no-install-recommends apt-utils dialog locales 2>&1 \
+    # Verify git, process tools installed
+    && apt-get -y install git openssh-client iproute2 procps lsb-release \
+    #
+    # Install ruby-debug-ide and debase
+    && gem install ruby-debug-ide \
+    && gem install debase \
+    #
+    # Install node.js
+    && apt-get -y install curl software-properties-common \
+    && curl -sL https://deb.nodesource.com/setup_13.x | bash - \
+    && apt-get -y install nodejs \
+    #
+    # Create a non-root user to use if preferred - see https://aka.ms/vscode-remote/containers/non-root-user.
+    && groupadd --gid $USER_GID $USERNAME \
+    && useradd -s /bin/bash --uid $USER_UID --gid $USER_GID -m $USERNAME \
+    # [Optional] Add sudo support for the non-root user
+    && apt-get install -y sudo \
+    && echo $USERNAME ALL=\(root\) NOPASSWD:ALL > /etc/sudoers.d/$USERNAME\
+    && chmod 0440 /etc/sudoers.d/$USERNAME \
+    #
+    # Clean up
+    && apt-get autoremove -y \
+    && apt-get clean -y \
+    && rm -rf /var/lib/apt/lists/*
+
+# Set the locale
+RUN sed -i -e 's/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/locale.gen && \
+    dpkg-reconfigure --frontend=noninteractive locales && \
+    update-locale LANG=en_US.UTF-8
+
+ENV LANG en_US.UTF-8
+
+# Switch back to dialog for any ad-hoc use of apt-get
+ENV DEBIAN_FRONTEND=dialog

.devcontainer/devcontainer.json

@@ -0,0 +1,26 @@
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.101.1/containers/ruby-2
+{
+	"name": "Ruby 2",
+	"dockerFile": "Dockerfile",
+
+	// Set *default* container specific settings.json values on container create.
+	"settings": { 
+		"terminal.integrated.shell.linux": "/bin/bash"
+	},
+
+	// Add the IDs of extensions you want installed when the container is created.
+	"extensions": [
+		"rebornix.Ruby"
+	]
+	
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	"postCreateCommand": "bundle install",
+
+	// Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+	// "remoteUser": "vscode"
+
+}

.gitattributes

@@ -0,0 +1 @@
+* text=auto

.github/CONTRIBUTING.markdown

@@ -10,24 +10,24 @@ See the [support guidelines](https://jekyllrb.com/docs/support/)
 
 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.
+- [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 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.
+- 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.
 
-* If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/).
+- 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.
+- 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
 
@@ -76,11 +76,12 @@ If you ever need to update our documentation with an icon that is not already av
 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
+
+- 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:
+- Fix paths in the `@font-face {}` declaration by adding `../` before `fonts/FontAwesome.*` like so:
   `('../fonts/Fontawesome.woff?9h6hxj')`.
 
 ### Adding plugins
@@ -101,21 +102,21 @@ If your contribution changes any Jekyll behavior, make sure to update the docume
 
 #### 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 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.
+- 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.
+- 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).
+- 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)
+- 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)
 
-* Previously, we've used the WIP Probot app to help contributors determine whether their pull request is ready for review. Please use a [draft pull request](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests) instead. When you're ready, [mark the pull request as ready for review](https://help.github.com/en/articles/changing-the-stage-of-a-pull-request)
+- Previously, we've used the WIP Probot app to help contributors determine whether their pull request is ready for review. Please use a [draft pull request](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests) instead. When you're ready, [mark the pull request as ready for review](https://help.github.com/en/articles/changing-the-stage-of-a-pull-request)
 
 ## Running tests locally
 
@@ -148,6 +149,10 @@ script/cucumber features/blah.feature
 Both `script/test` and `script/cucumber` can be run without arguments to
 run its entire respective suite.
 
+## Visual Studio Code Development Container
+
+If you've got [Visual Studio Code](https://code.visualstudio.com/) with the [Remote Development Extension Pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) installed then simply opening this repository in Visual Studio Code and following the prompts to "Re-open In A Development Container" will get you setup and ready to go with a fresh environment with all the requirements installed.
+
 ## 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/FUNDING.yml

@@ -1,5 +1,5 @@
 # These are supported funding model platforms
 
-github: [ashmaroli, DirtyF, mattr-]
+# github: jekyll
 open_collective: jekyll
 tidelift: rubygems/jekyll

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,71 +0,0 @@
----
-name: Bug Report
-about: Is something not working as expected?
-title: ''
-labels: ''
-assignees: ''
-
----
-
-<!--
-  Hi! Thanks for considering to file a bug with Jekyll. Please take the time to
-  answer the basic questions. 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!
--->
-
-<!-- 
-  Make sure that you've done all of these. If you're sure that the bug you're
-  reporting is only apparent in a previous version of Jekyll, please say so explicitly
-  in your description.
-
-  - 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 contributing document at https://jekyllrb.com/docs/contributing/
--->
-
-## My Environment
-
-<!--
-  Replace the values in the Version(s) column with the ones in your build. If you're not
-  using `github-pages`, just replace it with "No".
--->
-
-| Software         | Version(s) |
-| ---------------- | ---------- |
-| Operating System |            |
-| `jekyll`         | Latest     |
-| `github-pages`   | Latest     |
-
----
-
-## Expected Behaviour
-
-<!--
-  What is it you expected to happen? This should be a description of how the
-  functionality you tried to use is supposed to work.
--->
-
-## Current Behavior
-
-<!--
-  Describe the details of the bug. Be sure to include any steps you took for the
-  problem to exist, such as the directories you created and the full command
-  you ran. Include any plugins you have installed (this is very important!).
-
-  You can include any logs you think relevant here. If you're using GitHub pages
-  and you're not sure where your logs are, please email support@github.com and
-  they will happily help you.
--->
-
-## Code Sample
-
-<!--
-  Please provide a code repository, gist, code snippet or sample files to
-  reproduce the issue.
--->

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,104 @@
+name: Bug Report
+description: "Is something not working as expected?"
+title: "[Bug]: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Hi! Thank you for taking the time to report a bug with Jekyll.
+
+        Please consider asking your question at https://talk.jekyllrb.com if one or more of the following is applicable to your situation:
+
+          - You are not sure if the issue is a bug in Jekyll.
+          - The issue is caused by a third-party plugin.
+          - This is just a generic usage question.
+
+        Additionally, please note that this platform is meant for bugs in Jekyll core only.
+        Issues regarding dependencies and plugins should be reported in their respective repositories.
+  - type: input
+    id: os
+    attributes:
+      label: Operating System
+      description: The operating system of your computer.
+      placeholder: "Ubuntu 21.10"
+    validations:
+      required: true
+  - type: input
+    id: ruby-version
+    attributes:
+      label: Ruby Version
+      description: |
+        The Ruby version you were using at the time.
+        Run `ruby -v` in your terminal and paste the output in the input field.
+      placeholder: "ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x64-mingw32]"
+    validations:
+      required: true
+  - type: input
+    id: jekyll-version
+    attributes:
+      label: Jekyll Version
+      description: |
+        The version of Jekyll used in your project.
+        Run `bundle exec jekyll -v` and paste the output in the input field.
+        *If you are not using a Gemfile, run `jekyll -v` instead.*
+      placeholder: "jekyll 4.2.1"
+    validations:
+      required: true
+  - type: input
+    id: ghp-version
+    attributes:
+      label: GitHub Pages Version
+      description: |
+        Are you deploying your site using GitHub Pages?
+        If yes, then we need to know the `github-pages` version used by your project. Proceed ahead otherwise.
+        If you're using the `github-pages` gem in your Gemfile, paste the output from running the following:
+        ```
+        bundle exec github-pages -v
+        ```
+        Otherwise, enter `Latest` in the input field and proceed ahead.
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: Briefly describe what you expected to see or get with a certain functionality.
+      placeholder: |
+        I expected my site to be built successfully when I run the following:
+        ```
+        bundle exec jekyll build
+        ```
+    validations:
+      required: true
+  - type: textarea
+    id: actual
+    attributes:
+      label: Current Behavior
+      description: >
+        Describe the details of the bug.
+        Be sure to include any steps you took for the problem to exist, such as the directories
+        you created and the full command you ran.
+        Include any plugins you have configured for use in the site.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: |
+        Please copy and paste any relevant log output from your terminal.
+        *Note: This will be automatically formatted into code, so no need for backticks.*
+      render: shell
+  - type: textarea
+    id: sample
+    attributes:
+      label: Code Sample
+      description: >
+        The easiest way for someone to understand an issue is if they could reproduce your issue
+        in their environment. Therefore, please provide a link to your project repository alongwith
+        instructions to reproduce your issue. If your project is not publicly accessible, please
+        consider setting up a minimal test repository complete with necessary instructions.
+      placeholder: |
+        ### Steps to reproduce issue
+
+        - Clone [my repo](https://github.com/owner/repo)
+        - Install site dependencies
+        - Run `bundle exec jekyll build -s src -d src/dist`

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Jekyll Community Forum
+    url: https://talk.jekyllrb.com/
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/documentation.md

@@ -1,9 +1,9 @@
 ---
 name: Documentation
 about: Found a typo or something that isn't crystal clear in our docs?
-title: 'docs: '
+title: '[Docs]: '
 labels: documentation
-assignees: DirtyF
+assignees: ''
 
 ---
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -27,7 +27,7 @@ assignees: ''
   implemented at the plugin level, but in Jekyll core? What use cases does it support?
 
   NOTE: Please be mindful of the Jekyll philosophy (https://jekyllrb.com/philosophy/),
-  particularily Section 5. Think about if 90% of the users would benefit from your
+  particularly Section 5. Think about if 90% of the users would benefit from your
   feature request, and whether your feature would be better off in a plugin.
 -->
 

.github/ISSUE_TEMPLATE/question.md

@@ -1,15 +0,0 @@
----
-name: Question
-about: Have any questions about how Jekyll works?
-title: ''
-labels: ''
-assignees: ''
-
----
-
-<!--
-  The Jekyll issue tracker IS NOT for usage questions! Please post your
-  question on our dedicated forum at https://talk.jekyllrb.com.
-
-  Thank you!
--->

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,6 +12,7 @@
 <!-- This is a 🐛 bug fix. -->
 <!-- This is a 🙋 feature or enhancement. -->
 <!-- This is a 🔦 documentation change. -->
+<!-- This is a 🔨 code refactoring. -->
 
 <!--
   Before you submit this pull request, make sure to have a look at the following

.github/SECURITY.markdown

@@ -0,0 +1,32 @@
+# Security Policy
+
+## Supported Versions
+
+Security updates are applied to the latest MINOR version of Jekyll, and the version used by GitHub Pages, v3.9.x.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 4.2.x   | :white_check_mark: |
+| 3.9.x   | :white_check_mark: |
+| < 3.9.x | :x:                |
+
+## Reporting a Vulnerability
+
+Please report vulnerabilities by sending an email to security@jekyllrb.com with the following information:
+
+1. A description of the vulnerability
+2. Reproduction steps and/or a sample site (share a private repo to the [Jekyll Security Team](docs/pages/team.md))
+3. Your contact information
+
+The Jekyll security team will respond to your submission and notify you whether it has been confirmed by the team.
+Your confidentiality is kindly requested as we work on a fix. We will provide our patch to you to test and verify that the vulnerability has
+been closed.
+
+If you have created a patch and would like to submit that to us as well, we will happily consider it though we cannot guarantee that we will
+use it. If we use your patch, we will attribute authorship to you either as the commit author, or as a co-author.
+
+Once a fix is verified, we will release PATCH versions of the supported MINOR versions and assign a CVE to the vulnerability. You will receive
+credit in our release post.
+
+Once the patched version has been released, we will no longer request you to maintain confidentiality and you may choose to share details on
+how you found the vulnerability with the community.

.github/actions/spelling/README.md

@@ -0,0 +1,15 @@
+# check-spelling/check-spelling configuration
+
+File | Purpose | Format | Info
+-|-|-|-
+[dictionary.txt](dictionary.txt) | Replacement dictionary (creating this file will override the default dictionary) | one word per line | [dictionary](https://github.com/check-spelling/check-spelling/wiki/Configuration#dictionary)
+[allow.txt](allow.txt) | Add words to the dictionary | one word per line (only letters and `'`s allowed) | [allow](https://github.com/check-spelling/check-spelling/wiki/Configuration#allow)
+[reject.txt](reject.txt) | Remove words from the dictionary (after allow) | grep pattern matching whole dictionary words | [reject](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-reject)
+[excludes.txt](excludes.txt) | Files to ignore entirely | perl regular expression | [excludes](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-excludes)
+[only.txt](only.txt) | Only check matching files (applied after excludes) | perl regular expression | [only](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-only)
+[patterns.txt](patterns.txt) | Patterns to ignore from checked lines | perl regular expression (order matters, first match wins) | [patterns](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-patterns)
+[expect.txt](expect.txt) | Expected words that aren't in the dictionary | one word per line (sorted, alphabetically) | [expect](https://github.com/check-spelling/check-spelling/wiki/Configuration#expect)
+[advice.txt](advice.txt) | Supplement for GitHub comment when unrecognized words are found | GitHub Markdown | [advice](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-advice)
+
+Note: you can replace any of these files with a directory by the same name (minus the `.txt` extension) and
+then include multiple files (with a `.txt` extension) inside that directory to merge multiple files together.

.github/actions/spelling/advice.md

@@ -0,0 +1,28 @@
+<!-- See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples%3A-advice --> <!-- markdownlint-disable MD033 MD041 -->
+
+<details><summary>If you see a bunch of garbage</summary>
+
+If it relates to a ...
+<details><summary>well-formed pattern</summary>
+
+See if there's a [pattern](https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns) that would match it.
+
+If not, try writing one and adding it to the `patterns.txt` file.
+
+Patterns are Perl 5 Regular Expressions - you can [test](
+https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your lines.
+
+Note that patterns can't match multiline strings.
+</details>
+<details><summary>binary-ish string</summary>
+
+Please add a file path to the `excludes.txt` file instead of just accepting the garbage.
+
+File paths are Perl 5 Regular Expressions - you can [test](
+https://www.regexplanet.com/advanced/perl/) yours before committing to verify it will match your files.
+
+`^` refers to the file's path from the root of the repository, so `^README\.md$` would exclude [README.md](
+../tree/HEAD/README.md) (on whichever branch you're using).
+</details>
+
+</details>

.github/actions/spelling/excludes.txt

@@ -0,0 +1,35 @@
+# See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-excludes
+
+(?:^|/)(?i)COPYRIGHT
+(?:^|/)(?i)LICEN[CS]E
+(?:^|/)package(?:-lock|)\.json$
+(?:^|/)vendor/
+
+/fonts/
+ignore$
+
+\.avi$
+\.eot$
+\.ico$
+\.jpe?g$
+\.lock$
+\.map$
+\.min\.
+\.mod$
+\.mp[34]$
+\.png$
+\.svg$
+\.ttf$
+\.wav$
+\.woff$
+\.woff2$
+
+^docs/pages/redirects/github\.html$
+^lib/jekyll/mime\.types$
+^lib/theme_template/example/index\.html$
+^lib/theme_template/example/_post\.md$
+^test/fixtures/empty_permalink\.erb$
+^test/fixtures/webrick/bar/baz\.html$
+^test/fixtures/webrick/bar/foo\.xhtml$
+^test/source/_posts/2009-06-22-no-yaml\.markdown$
+^\.github/

.github/actions/spelling/expect.txt

@@ -0,0 +1,760 @@
+acl
+activesupport
+adaoraul
+addons
+aeiou
+AFile
+afterall
+Alexey
+alfredxing
+algolia
+allowfullscreen
+Anatoliy
+andreyvit
+Ankit
+Anning
+apps
+appveyor
+arengu
+args
+ariejan
+arounds
+asciinema
+asdf
+ashmaroli
+attr
+Autobuild
+autocompletion
+autogenerated
+Autolink
+autoload
+autoreconf
+autosave
+awood
+aws
+awscli
+backend
+backport
+backtick
+barcamp
+baseurl
+bashrc
+baz
+bbatsov
+bdimcheff
+bellvat
+benbalter
+Beney
+binstubs
+bip
+bitbucket
+blog
+Blogger
+blogging
+bonafide
+Bou
+breadcrumbs
+briandoll
+bridgetown
+bridgetownrb
+brightbox
+brighterplanet
+buddyworks
+Bugfix
+Burela
+byparker
+cachegrind
+calavera
+callgraphs
+cartera
+cavalle
+CDNs
+cgi
+changefreq
+changelog
+chango
+charset
+Chayoung
+chcp
+chdir
+Cheatsheet
+Checkoway
+chmod
+chown
+Chrononaut
+chruby
+cibuild
+cimg
+circleci
+CJK
+classname
+cloudcannon
+Cloudinary
+cloudsh
+CLT
+codebase
+codeclimate
+CODEOWNERS
+coderay
+codeslinger
+coffeescript
+colorator
+commandline
+commonmark
+compat
+compatibilize
+concat
+config
+configyml
+contentblocks
+CORS
+Cov
+CRLFs
+cron
+crontab
+cruft
+css
+csv
+Currin
+CVE
+CWD
+cygwin
+daringfireball
+Dassonville
+datafiles
+datetime
+DCEU
+Debian
+debuggability
+defunkt
+delegators
+deployer
+deps
+dest
+Devkit
+devops
+digitalocean
+dirs
+disqus
+ditaa
+dnf
+doclist
+doctype
+doeorg
+dommmel
+dotfile
+Dousse
+downcase
+downcased
+duckduckgo
+duritong
+Dusseau
+dysinger
+ecf
+editorconfig
+eduardoboucas
+Elasticsearch
+elsif
+Emacs
+emails
+emoji
+endcapture
+endcomment
+endfor
+endhighlight
+endif
+endraw
+endrender
+endtablerow
+Enumerables
+EOL
+erb
+errordocument
+Espinaco
+eugenebolshakov
+evaled
+exe
+execjs
+extensionpack
+extname
+exts
+favicon
+Fengyun
+ffi
+figcaption
+filesystem
+Finazzo
+firstimage
+FIXME
+flakey
+flickr
+fnmatch
+fontello
+forloop
+formcake
+formcarry
+formester
+formingo
+formkeep
+formspark
+formspree
+formx
+Forwardable
+frameborder
+freenode
+frontmatter
+fsnotify
+ftp
+fullstory
+Gaudino
+gcc
+gcnovus
+gemfile
+gemset
+gemspec
+getform
+getset
+getsimpleform
+gettalong
+gfm
+ghp
+ghpages
+giraffeacademy
+github
+githubcom
+githubusercontent
+gitignore
+gitlab
+gjtorikian
+globbed
+globbing
+google
+gotcha
+Goulven
+gridism
+GSo
+gsub
+gsubbing
+Hakiri
+hardcode
+hashbang
+hashmap
+helaili
+henrik
+heredoc
+heroku
+highlighter
+hilighting
+Hoizey
+homepage
+hostman
+hostname
+href
+htaccess
+htm
+html
+htmlproofer
+http
+httpd
+httpdocs
+hyperlinks
+Iaa
+ial
+ico
+icomoon
+iconset
+ified
+iframe
+img
+Impl
+Inlining
+invokables
+irc
+ivey
+ize
+jalali
+jameshamann
+jamstackthemes
+jan
+javascript
+Jax
+jayferd
+jcon
+jdoe
+jeffreytse
+jeffrydegrande
+Jekpack
+jekyllbot
+jekyllconf
+Jekyllers
+Jekyllin
+Jekylling
+jekyllized
+jekylllayoutconcept
+jekyllrb
+jekyllthemes
+jemoji
+jmcglone
+jneen
+johnreilly
+jpg
+jqr
+jruby
+json
+jsonify
+juretta
+jwarby
+Kacper
+Kasberg
+kbd
+Kentico
+Kewin
+keycdn
+kickster
+Kinnula
+kiwifruit
+Kolesky
+konklone
+kontent
+Kotvinsky
+kramdown
+Kulig
+Kwokfu
+Lamprecht
+laquo
+lastmod
+launchctl
+launchy
+laurilehmijoki
+ldquo
+learnxinyminutes
+lexer
+LGTM
+libcurl
+libffi
+lifecycle
+lightgray
+limjh
+linenos
+linkify
+linux
+liufengyun
+livereload
+localheinz
+localhost
+localtime
+Locher
+loglevel
+Losslessly
+lovin
+lsi
+lsquo
+lstrip
+lyche
+macos
+macromates
+mademistakes
+mailto
+Manmeet
+markdownify
+Maroli
+Marsceill
+maruku
+mathjax
+mathml
+mattr
+Maximiliano
+mchung
+mdash
+memberspace
+Memoize
+memoized
+memoizing
+mentoring
+mergable
+Mertcan
+mertkahyaoglu
+metadata
+microdata
+microsoft
+mimetype
+mingw
+minibundle
+minifier
+minitest
+Mittal
+mixin
+mkasberg
+mkd
+mkdir
+mkdn
+mkdown
+mmistakes
+modernizr
+mojombo
+moncefbelyamani
+moz
+mreid
+msdn
+mswin
+MSYS
+mtime
+multiline
+munging
+Mvvm
+myblog
+mycontent
+mydata
+mydoc
+myimage
+mypage
+myposts
+myproject
+myrepo
+mysite
+myvalue
+myvar
+myvariable
+Nadjib
+nakanishi
+namespace
+namespaced
+navbar
+nbsp
+nearlyfreespeech
+nethack
+netlify
+netlifycms
+Neue
+nginx
+ngx
+nielsenramon
+nior
+nodejs
+noifniof
+nokogiri
+notextile
+onclick
+onebox
+oneclick
+onschedule
+opensource
+openssl
+Optim
+orderofinterpretation
+orgs
+OSVDB
+osx
+packagecontrol
+pacman
+paginator
+pandoc
+pantulis
+params
+parkr
+parseable
+paspagon
+passthrough
+pathawks
+Pathutil
+paywall
+pdf
+Pelykh
+permalink
+PHP
+pinboard
+Piwigo
+pjhyett
+pkill
+pkpass
+placeholders
+planetjekyll
+plantuml
+plugin
+png
+podcasts
+popen
+Porcel
+Posterous
+postfiles
+postlayout
+postmodern
+preinstalled
+prepends
+Prioritise
+Probot
+projectlist
+pubstorm
+pufuwozu
+pwa
+pwd
+pygments
+qrush
+Quaid
+quickstart
+rackup
+Rakefile
+raquo
+razorops
+rbenv
+rdiscount
+rdoc
+rdquo
+readme
+realz
+rebund
+redcarpet
+redcloth
+redgreen
+redhat
+refactor
+refactoring
+Refheap
+regen
+regex
+regexp
+remi
+reqs
+Responsify
+revertable
+rfc
+rfelix
+RHEL
+ridk
+roadmap
+rowspan
+rspec
+rsquo
+rss
+rstrip
+rsync
+rtomayko
+Rubo
+rubocop
+rubychan
+rubygem
+rubyinstaller
+rubyprof
+Ruparelia
+Rusiczki
+rvm
+ryanflorence
+saas
+samplelist
+samrayner
+sandboxed
+Sassc
+sassify
+schemastore
+Schroers
+Schwartzian
+scp
+screenshot
+scrollbar
+scroller
+scss
+scssify
+sdk
+SDKROOT
+sectore
+semver
+seo
+serverless
+setenv
+SFTP
+shingo
+shopify
+shortlog
+shoulda
+sieversii
+sigpipe
+simplecov
+Singhaniya
+siteleaf
+sitemap
+SITENAME
+Slicehost
+slugified
+slugify
+smartforms
+smartify
+snipcart
+socio
+somedir
+sonnym
+Sonomy
+sourced
+sourcemaps
+spam
+spotify
+src
+ssg
+ssh
+SSL
+stackoverflow
+standalone
+staticfiles
+staticman
+statictastic
+STDERR
+stdout
+Stickyposts
+strftime
+stringified
+Stringify
+styleguide
+stylesheet
+subdir
+subdomain
+subfolder
+subfolderitems
+subnav
+subpages
+subpath
+subpiece
+subsubfolderitems
+subthing
+subvalues
+subwidget
+sudo
+superdirectories
+superdirs
+SUSE
+sverrirs
+svg
+svn
+swfobject
+swupd
+symlink
+symlinking
+tablerow
+tada
+Taillandier
+talkyard
+tbody
+technicalpickles
+templating
+templatize
+Termux
+textilize
+textpattern
+thead
+therubyracer
+Theunissen
+Thornquest
+thoughtbot
+throughs
+Tidelift
+timeago
+timezone
+titleize
+TLS
+tmm
+tmp
+toc
+tok
+tomjoht
+toml
+tomo
+toolset
+toshimaru
+triaged
+triaging
+truncatewords
+tsv
+ttf
+Tudou
+Tumblr
+Tweetsert
+txtpen
+Tyborska
+tzinfo
+ubuntu
+uby
+ujh
+ultron
+undumpable
+unencode
+Unescape
+unescaping
+unicode
+uniq
+upcase
+uppercasing
+uri
+url
+urlset
+username
+usr
+utf
+utils
+utime
+utm
+vanpelt
+Vasovi
+vendored
+vercel
+versioned
+versioning
+vertycal
+Veyor
+vilcans
+Vishesh
+visualstudio
+vnd
+vohedge
+vps
+vscode
+vwochnik
+Walkthroughs
+wdm
+We'd
+webfont
+webhook
+webhosting
+webmentions
+webrick
+website
+weekdate
+whitelist
+whitelisting
+wiki
+wikipedia
+wildcards
+willcodeforfoo
+woff
+wordpress
+Workaround
+workflow
+wsl
+www
+xcode
+xcrun
+xdg
+Xhmikos
+xhtml
+Xiaoiver
+XMinutes
+xml
+xmlns
+xmlschema
+yajl
+yaml
+Yarp
+Yashu
+Yastreb
+yml
+Youku
+youtube
+yunbox
+zeropadding
+Zlatan
+zlib
+zoneinfo
+zpinter
+Zsh
+zshrc
+zypper
+zzot
+frontend
+prefetching

.github/actions/spelling/only.txt

@@ -0,0 +1 @@
+^docs/.*\.md$

.github/actions/spelling/patterns.txt

@@ -0,0 +1,75 @@
+# See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns
+
+# data urls
+(['"])data:.*?\g{-1}
+data:[-a-zA-Z=;:/0-9+]*,\S*
+
+# YouTube
+https?://(?:(?:www\.|)youtube\.com|youtu.be)/(?:channel/|embed/|playlist\?list=|watch\?v=|v/|)[-a-zA-Z0-9?&=_]*
+<\s*youtube\s+id=['"][-a-zA-Z0-9?_]*['"]
+\bimg\.youtube\.com/vi/[-a-zA-Z0-9?&=_]*
+youtube_id:\s*[-a-zA-Z0-9?&=_]*
+
+# Google Analytics
+\bgoogle-analytics\.com/collect.[-0-9a-zA-Z?%=&_.~]*
+
+# Google APIs
+\bgoogleapis\.com/[a-z]+/v\d+/[a-z]+/[@./?=\w]+
+\b[-a-zA-Z0-9.]*\bstorage\d*\.googleapis\.com(?:/\S*|)
+
+# Google Calendar
+\bcalendar\.google\.com/calendar(?:/u/\d+|)/embed\?src=[@./?=\w&%]+
+\w+\@group\.calendar\.google\.com\b
+
+# Google DataStudio
+\bdatastudio\.google\.com/(?:(?:c/|)u/\d+/|)(?:embed/|)(?:open|reporting|datasources|s)/[-0-9a-zA-Z]+(?:/page/[-0-9a-zA-Z]+|)
+
+# The leading `/` here is as opposed to the `\b` above
+# ... a short way to match `https://` or `http://` since most urls have one of those prefixes
+# Google Docs
+/docs\.google\.com/[a-z]+/d/(?:e/|)[0-9a-zA-Z_-]+/?
+
+# Google Groups
+https://groups\.google\.com/d/topic/[^/]+/[a-zA-Z0-9]+/discussion
+https://groups\.google\.com/d/msg/[^/]+/[a-zA-Z0-9]+/[a-zA-Z0-9]+
+
+# Google themes
+themes\.googleusercontent\.com/static/fonts/[^/]+/v\d+/[^.]+.
+
+# Google CDN
+\bclients2\.google(?:usercontent|)\.com[-0-9a-zA-Z/.]*
+
+# Goo.gl
+/goo\.gl/[a-zA-Z0-9]+
+
+# Google Chrome Store
+\bchrome\.google\.com/webstore/detail/\w*(?:/\w*|)
+
+# google_site_verification:
+google_site_verification: [-a-zA-Z=;:/0-9+]*
+
+# Ruby-doc.org
+https://ruby-doc\.org/.*
+
+# Contributors
+alphabetical order.*:.*
+twitter_handle: .*
+
+# apiKey
+apiKey: '[a-f0-9]+'
+
+# FontAwesome
+/(?:(?i)FontAwesome\.\w+\?\w+)
+
+# Lorem
+(?:\w|\s|[,.])*\b(?i)(?:amet|consectetur|cursus|dolor|eros|ipsum|lacus|libero|ligula|lorem|magna|neque|nulla|suscipit|tempus|ultrices)\b(?:\w|\s|[,.])*
+
+# URL escaped characters
+\%[0-9A-F]{2}
+# c99 hex digits (not the full format, just one I've seen)
+
+# hex digits including css/html color classes:
+(?:[\\0][xX]|\\u|[uU]\+|#x?|\%23)[0-9a-fA-FgGrR_]{2,}(?:[uU]?[lL]{0,2}|u\d+)\b
+
+# ignore long runs of a single character:
+\b([A-Za-z])\g{-1}{3,}\b

.github/actions/spelling/reject.txt

@@ -0,0 +1,7 @@
+^attache$
+benefitting
+occurence
+Sorce
+^[Ss]pae
+^untill
+^wether

.github/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/actions/memprof.rb

@@ -0,0 +1,14 @@
+# frozen_string_literal: true
+
+require 'jekyll'
+require 'memory_profiler'
+
+MemoryProfiler.report(allow_files: ['lib/jekyll/', 'lib/jekyll.rb']) do
+  Jekyll::PluginManager.require_from_bundler
+  Jekyll::Commands::Build.process({
+    "source"             => File.expand_path(ARGV[0]),
+    "destination"        => File.expand_path("#{ARGV[0]}/_site"),
+    "disable_disk_cache" => true,
+  })
+  puts ''
+end.pretty_print(scale_bytes: true, normalize_paths: true)

.github/workflows/benchmark.yml

@@ -0,0 +1,30 @@
+name: Micro Benchmark Runs
+
+on:
+  workflow_dispatch:
+    inputs:
+      path:
+        description: "Path to benchmark script relative to 'benchmark' directory."
+        required: true
+        default: "capture-assign.rb"
+      ruby_version:
+        description: "Ruby version to use (via `ruby/setup-ruby@v1`) action."
+        required: false
+        default: "2.7"
+
+jobs:
+  benchmark:
+    name: "Benchmark (${{ github.event.inputs.path }}) (Ruby ${{ github.event.inputs.ruby_version }})"
+    runs-on: "ubuntu-latest"
+    env:
+      BENCHMARK: true
+    steps:
+    - name: Checkout Jekyll
+      uses: actions/checkout@v3
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: ${{ github.event.inputs.ruby_version }}
+        bundler-cache: true
+    - name: Run Benchmark
+      run: "bundle exec ruby benchmark/${{ github.event.inputs.path }}"

.github/workflows/ci.yml

@@ -0,0 +1,73 @@
+name: Continuous Integration
+
+on:
+  push:
+    branches:
+      - master
+      - "*-stable"
+  pull_request:
+    branches:
+      - master
+      - "*-stable"
+
+jobs:
+  ci:
+    name: "Run Tests (${{ matrix.label }})"
+    runs-on: "ubuntu-latest"
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - label: Ruby 2.7
+            ruby_version: "2.7"
+          - label: Ruby 3.0
+            ruby_version: "3.0"
+          - label: Ruby 3.1
+            ruby_version: "3.1"
+          - label: JRuby 9.3.4.0
+            ruby_version: "jruby-9.3.4.0"
+          - label: Liquid 4
+            ruby_version: 3.1
+            liquid_version: "~> 4.0"
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+      - name: "Set up ${{ matrix.label }}"
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby_version }}
+          bundler-cache: true
+        env:
+          LIQUID_VERSION: ${{ matrix.liquid_version }}
+      - name: Run Minitest based tests
+        run: bash script/test
+      - name: Run Cucumber based tests
+        run: bash script/cucumber
+      - name: Generate and Build a new site
+        run: bash script/default-site
+
+  xtras:
+    name: "${{ matrix.job_name }} (Ruby ${{ matrix.ruby_version }})"
+    runs-on: "ubuntu-latest"
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - job_name: "Profile Docs Site"
+            step_name: "Build and Profile docs site"
+            script_file: "profile-docs"
+            ruby_version: "2.7"
+          - job_name: "Style Check"
+            step_name: "Run RuboCop"
+            script_file: "fmt"
+            ruby_version: "2.7"
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+      - name: "Set up Ruby ${{ matrix.ruby_version }}"
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby_version }}
+          bundler-cache: true
+      - name: ${{ matrix.step_name }}
+        run: bash script/${{ matrix.script_file }}

.github/workflows/docs.yml

@@ -0,0 +1,52 @@
+name: Build and deploy Jekyll documentation site
+
+on:
+  push:
+    branches:
+      - master
+
+env:
+  RUBY_VERSION: 2.7
+
+jobs:
+  deploy_docs:
+    if: "!contains(github.event.commits[0].message, '[ci skip]')"
+    runs-on: 'ubuntu-latest'
+    env:
+      BUNDLE_PATH: "vendor/bundle"
+      BUNDLE_JOBS: 4
+      BUNDLE_RETRY: 3
+    steps:
+      - uses: actions/checkout@v3
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ env.RUBY_VERSION }}
+          bundler-cache: true
+      - name: Clone target branch
+        run: |
+          REMOTE_BRANCH="${REMOTE_BRANCH:-gh-pages}"
+          REMOTE_REPO="https://${GITHUB_ACTOR}:${{ secrets.GITHUB_TOKEN }}@github.com/${GITHUB_REPOSITORY}.git"
+
+          echo "Publishing to ${GITHUB_REPOSITORY} on branch ${REMOTE_BRANCH}"
+          rm -rf docs/_site/
+          git clone --depth=1 --branch="${REMOTE_BRANCH}" --single-branch --no-checkout \
+            "${REMOTE_REPO}" docs/_site/
+      - name: Build site
+        run: bundle exec jekyll build --source docs --destination docs/_site --verbose --trace
+        env:
+          # For jekyll-github-metadata
+          JEKYLL_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Deploy to GitHub Pages
+        run: |
+          SOURCE_COMMIT="$(git log -1 --pretty="%an: %B" "$GITHUB_SHA")"
+          pushd docs/_site &>/dev/null
+          : > .nojekyll
+
+          git add --all
+          git -c user.name="${GITHUB_ACTOR}" -c user.email="${GITHUB_ACTOR}@users.noreply.github.com" \
+            commit --quiet \
+            --message "Deploy docs from ${GITHUB_SHA}" \
+            --message "$SOURCE_COMMIT"
+          git push
+
+          popd &>/dev/null

.github/workflows/release.yml

@@ -0,0 +1,34 @@
+name: Release Gem
+
+on:
+  push:
+    branches:
+      - master
+      - "*-stable"
+    paths:
+      - "lib/**/version.rb"
+
+jobs:
+  release:
+    if: "github.repository_owner == 'jekyll'"
+    name: "Release Gem (Ruby ${{ matrix.ruby_version }})"
+    runs-on: "ubuntu-latest"
+    strategy:
+      fail-fast: true
+      matrix:
+        ruby_version:
+          - 2.7
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v3
+      - name: "Set up Ruby ${{ matrix.ruby_version }}"
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby_version }}
+          bundler-cache: true
+      - name: Build and Publish Gem
+        uses: ashmaroli/release-gem@dist
+        with:
+          gemspec_name: jekyll
+        env:
+          GEM_HOST_API_KEY: ${{ secrets.RUBYGEMS_GEM_PUSH_API_KEY }}

.github/workflows/spelling.yml

@@ -0,0 +1,22 @@
+name: Spell Check
+on:
+  push:
+    branches:
+      - master
+      - "*-stable"
+  # Switch from `pull_request_target` event to reduce distraction from comments
+  # regarding errors reported in unmodified files.
+  pull_request:
+    branches:
+      - master
+      - "*-stable"
+
+jobs:
+  build:
+    name: Spell Check
+    runs-on: "ubuntu-latest"
+    steps:
+    - name: Checkout Repository
+      uses: actions/checkout@v3
+    - name: Check Spellings
+      uses: check-spelling/check-spelling@v0.0.19

.github/workflows/third-party.yml

@@ -0,0 +1,41 @@
+name: Third-Party Repository Profiling
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+jobs:
+  build_n_profile:
+    if: "!contains(github.event.commits[0].message, '[ci skip]')"
+    runs-on: 'ubuntu-latest'
+    env:
+      BUNDLE_GEMFILE: "sandbox/Gemfile"
+      BUNDLE_PATH: "vendor/bundle"
+      BUNDLE_JOBS: 4
+      BUNDLE_RETRY: 3
+    steps:
+    - name: Checkout Jekyll
+      uses: actions/checkout@v3
+      with:
+        fetch-depth: 5
+        path: jekyll
+    - name: Checkout Third-Party Repository
+      uses: actions/checkout@v3
+      with:
+        repository: ashmaroli/tomjoht.github.io
+        path: sandbox
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        ruby-version: 2.7
+        bundler-cache: true
+    - name: Run Jekyll Build 3 times
+      run: |
+        bundle exec jekyll build -s sandbox -d sandbox/_site --trace
+        bundle exec jekyll build -s sandbox -d sandbox/_site --trace
+        bundle exec jekyll build -s sandbox -d sandbox/_site --trace
+    - name: Memory Analysis of Jekyll Build
+      run: bundle exec ruby jekyll/.github/workflows/actions/memprof.rb sandbox

.gitignore

@@ -1,8 +1,7 @@
 # Jekyll
 _site/
-.jekyll-cache
+*-cache/
 .jekyll-metadata
-.sass-cache
 
 # Ruby
 .bundle/

.rubocop.yml

@@ -1,7 +1,11 @@
 ---
+inherit_from: .rubocop_todo.yml
 
 require:
+  - rubocop-minitest
   - rubocop-performance
+  - rubocop-rake
+  - rubocop-rspec
   - ./rubocop/jekyll
 
 Jekyll/NoPutsAllowed:
@@ -9,7 +13,7 @@ Jekyll/NoPutsAllowed:
     - rake/*.rake
 
 AllCops:
-  TargetRubyVersion: 2.4
+  TargetRubyVersion: 2.7
   Include:
     - lib/**/*.rb
     - test/**/*.rb
@@ -20,32 +24,137 @@ AllCops:
     - script/**/*
     - vendor/**/*
     - tmp/**/*
-Layout/AlignHash:
+
+Gemspec/DateAssignment:
+  Enabled: true
+Layout/BeginEndAlignment:
+  Enabled: true
+Layout/EmptyComment:
+  Enabled: false
+Layout/EmptyLinesAroundAttributeAccessor:
+  Enabled: true
+Layout/EndAlignment:
+  Severity: error
+Layout/FirstArrayElementIndentation:
+  EnforcedStyle: consistent
+Layout/FirstHashElementIndentation:
+  EnforcedStyle: consistent
+Layout/HashAlignment:
   EnforcedHashRocketStyle: table
 Layout/IndentationWidth:
   Severity: error
-Layout/IndentFirstArrayElement:
-  EnforcedStyle: consistent
-Layout/IndentFirstHashElement:
-  EnforcedStyle: consistent
+Layout/LineLength:
+  Exclude:
+    - !ruby/regexp /features\/.*.rb/
+    - Rakefile
+    - rake/*.rake
+    - Gemfile
+  Max: 100
+  Severity: warning
 Layout/MultilineMethodCallIndentation:
   EnforcedStyle: indented
 Layout/MultilineOperationIndentation:
   EnforcedStyle: indented
+Layout/SpaceAroundMethodCallOperator:
+  Enabled: true
+Layout/SpaceBeforeBrackets:
+  Enabled: true
+Layout/SpaceInsideHashLiteralBraces:
+  Enabled: true
+  Exclude:
+    - test/**/*.rb
+
+Lint/AmbiguousAssignment:
+  Enabled: true
+Lint/BinaryOperatorWithIdenticalOperands:
+  Enabled: true
+Lint/ConstantDefinitionInBlock:
+  Enabled: true
+  Exclude:
+    - test/**/*.rb
+Lint/DeprecatedConstants:
+  Enabled: true
+Lint/DeprecatedOpenSSLConstant:
+  Enabled: true
+Lint/DuplicateBranch:
+  Enabled: true
+Lint/DuplicateElsifCondition:
+  Enabled: true
+Lint/DuplicateRegexpCharacterClassElement:
+  Enabled: true
+Lint/DuplicateRequire:
+  Enabled: true
+Lint/DuplicateRescueException:
+  Enabled: true
+Lint/EmptyBlock:
+  Enabled: true
+Lint/EmptyClass:
+  Enabled: true
+Lint/EmptyConditionalBody:
+  Enabled: true
+Lint/EmptyFile:
+  Enabled: true
+Lint/FloatComparison:
+  Enabled: true
+Lint/HashCompareByIdentity:
+  Enabled: true
+Lint/IdentityComparison:
+  Enabled: true
+Lint/LambdaWithoutLiteralBlock:
+  Enabled: true
+Lint/MissingSuper:
+  Enabled: false
+Lint/MixedRegexpCaptureTypes:
+  Enabled: false
 Lint/NestedPercentLiteral:
   Exclude:
     - test/test_site.rb
-Layout/EmptyComment:
+Lint/NoReturnInBeginEndBlocks:
+  Enabled: true
+Lint/NumberedParameterAssignment:
+  Enabled: true
+Lint/OrAssignmentToConstant:
+  Enabled: true
+Lint/OutOfRangeRegexpRef:
+  Enabled: true
+Lint/RaiseException:
+  Enabled: true
+Lint/RedundantDirGlobSort:
+  Enabled: true
+Lint/RedundantSafeNavigation:
+  Enabled: true
+Lint/SelfAssignment:
+  Enabled: true
+Lint/StructNewOverride:
+  Enabled: true
+Lint/SymbolConversion:
+  Enabled: true
+Lint/ToEnumArguments:
   Enabled: false
-Layout/EndAlignment:
-  Severity: error
+Lint/TopLevelReturnWithArgument:
+  Enabled: true
+Lint/TrailingCommaInAttributeDeclaration:
+  Enabled: true
+Lint/TripleQuotes:
+  Enabled: true
+Lint/UnexpectedBlockArity:
+  Enabled: true
+Lint/UnmodifiedReduceAccumulator:
+  Enabled: true
 Lint/UnreachableCode:
   Severity: error
+Lint/UnreachableLoop:
+  Enabled: true
+Lint/UselessMethodDefinition:
+  Enabled: true
+Lint/UselessTimes:
+  Enabled: true
 Lint/Void:
   Exclude:
     - lib/jekyll/site.rb
+
 Metrics/AbcSize:
-  Max: 21
+  Max: 23
 Metrics/BlockLength:
   Exclude:
     - test/**/*.rb
@@ -64,24 +173,49 @@ 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
+  Max: 11
 Metrics/MethodLength:
   CountComments: false
   Max: 20
   Severity: error
 Metrics/ModuleLength:
+  Exclude:
+    - lib/jekyll/filters.rb
   Max: 240
 Metrics/ParameterLists:
   Max: 4
 Metrics/PerceivedComplexity:
-  Max: 8
+  Max: 13
+
+Minitest/AssertInDelta:
+  Enabled: true
+Minitest/AssertionInLifecycleHook:
+  Enabled: true
+Minitest/AssertKindOf:
+  Enabled: true
+Minitest/AssertOutput:
+  Enabled: true
+Minitest/AssertPathExists:
+  Enabled: true
+Minitest/AssertSilent:
+  Enabled: true
+Minitest/LiteralAsActualArgument:
+  Enabled: true
+Minitest/TestMethodName:
+  Enabled: false
+Minitest/MultipleAssertions:
+  Enabled: true
+Minitest/RefuteInDelta:
+  Enabled: true
+Minitest/RefuteKindOf:
+  Enabled: true
+Minitest/RefutePathExists:
+  Enabled: true
+Minitest/UnspecifiedException:
+  Enabled: true
+Minitest/AssertEmptyLiteral:
+  Enabled: false
+
 Naming/FileName:
   Enabled: false
 Naming/HeredocDelimiterNaming:
@@ -93,6 +227,40 @@ Naming/MemoizedInstanceVariableName:
     - lib/jekyll/drops/site_drop.rb
     - lib/jekyll/drops/unified_payload_drop.rb
     - lib/jekyll/page_without_a_file.rb
+
+Performance/AncestorsInclude:
+  Enabled: false
+Performance/ArraySemiInfiniteRangeSlice:
+  Enabled: true
+Performance/BigDecimalWithNumericArgument:
+  Enabled: true
+Performance/BlockGivenWithExplicitBlock:
+  Enabled: true
+Performance/ChainArrayAllocation:
+  Enabled: true
+Performance/CollectionLiteralInLoop:
+  Enabled: true
+Performance/ConstantRegexp:
+  Enabled: true
+Performance/MethodObjectAsBlock:
+  Enabled: true
+Performance/RedundantSortBlock:
+  Enabled: true
+Performance/RedundantStringChars:
+  Enabled: true
+Performance/ReverseFirst:
+  Enabled: true
+Performance/SortReverse:
+  Enabled: false
+Performance/Squeeze:
+  Enabled: true
+Performance/StringInclude:
+  Enabled: true
+  Exclude:
+    - lib/jekyll/utils/platforms.rb
+Performance/Sum:
+  Enabled: true
+
 Security/MarshalLoad:
   Exclude:
     - !ruby/regexp /test\/.*.rb$/
@@ -101,31 +269,78 @@ Security/YAMLLoad:
   Exclude:
     - !ruby/regexp /features\/.*.rb/
     - !ruby/regexp /test\/.*.rb$/
+
 Style/AccessModifierDeclarations:
   Enabled: false
+Style/AccessorGrouping:
+  Enabled: true
 Style/Alias:
   EnforcedStyle: prefer_alias_method
 Style/AndOr:
   Severity: error
-Style/BracesAroundHashParameters:
+Style/ArgumentsForwarding:
   Enabled: false
+Style/ArrayCoercion:
+  Enabled: true
+Style/BisectedAttrAccessor:
+  Enabled: true
+Style/CaseLikeIf:
+  Enabled: true
+Style/StringChars:
+  Enabled: true
 Style/ClassAndModuleChildren:
   Exclude:
     - test/**/*.rb
-Style/FrozenStringLiteralComment:
-  EnforcedStyle: always
+Style/ClassEqualityComparison:
+  Enabled: true
+Style/CollectionCompact:
+  Enabled: true
+Style/CombinableLoops:
+  Enabled: true
+Style/DocumentDynamicEvalDefinition:
+  Enabled: true
 Style/Documentation:
   Enabled: false
 Style/DoubleNegation:
   Enabled: false
+Style/EndlessMethod:
+  Enabled: true
+Style/ExplicitBlockArgument:
+  Enabled: false
+Style/ExponentialNotation:
+  Enabled: true
 Style/FormatStringToken:
   Exclude:
     - lib/jekyll/utils/ansi.rb
+    - lib/jekyll/liquid_renderer/table.rb
+    - lib/jekyll/profiler.rb
+Style/FrozenStringLiteralComment:
+  EnforcedStyle: always
+Style/GlobalStdStream:
+  Enabled: true
 Style/GuardClause:
   Enabled: false
+Style/HashAsLastArrayItem:
+  Enabled: true
+Style/HashConversion:
+  Enabled: true  
+Style/HashEachMethods:
+  Enabled: true
+Style/HashExcept:
+  Enabled: true
+Style/HashLikeCase:
+  Enabled: true
 Style/HashSyntax:
   EnforcedStyle: hash_rockets
   Severity: error
+Style/HashTransformKeys:
+  Enabled: false
+Style/HashTransformValues:
+  Enabled: true
+Style/IfWithBooleanLiteralBranches:
+  Enabled: true
+Style/KeywordParametersOrder:
+  Enabled: true
 Style/MixinUsage:
   Exclude:
     - test/helper.rb
@@ -133,15 +348,35 @@ Style/ModuleFunction:
   Enabled: false
 Style/MultilineTernaryOperator:
   Severity: error
+Style/NegatedIfElseCondition:
+  Enabled: true
+Style/NilLambda:
+  Enabled: true
+Style/OptionalBooleanParameter:
+  Enabled: true
 Style/PercentLiteralDelimiters:
   PreferredDelimiters:
-    "%q": "{}"
     "%Q": "{}"
+    "%W": ()
+    "%q": "{}"
     "%r": "!!"
-    "%s": "()"
-    "%w": "()"
-    "%W": "()"
-    "%x": "()"
+    "%s": ()
+    "%w": ()
+    "%x": ()
+Style/RedundantArgument:
+  Enabled: true
+Style/RedundantAssignment:
+  Enabled: true
+Style/RedundantFetchBlock:
+  Enabled: false
+Style/RedundantFileExtensionInRequire:
+  Enabled: true
+Style/RedundantRegexpCharacterClass:
+  Enabled: true
+Style/RedundantRegexpEscape:
+  Enabled: true
+Style/RedundantSelfAssignment:
+  Enabled: true
 Style/RegexpLiteral:
   EnforcedStyle: percent_r
 Style/RescueModifier:
@@ -151,10 +386,23 @@ Style/SafeNavigation:
     - lib/jekyll/document.rb
 Style/SignalException:
   EnforcedStyle: only_raise
+Style/SingleArgumentDig:
+  Enabled: true
+Style/SlicingWithRange:
+  Enabled: false
+Style/SoleNestedConditional:
+  Enabled: true
+Style/StringConcatenation:
+  Enabled: true
+  Exclude:
+    - lib/jekyll/commands/*.rb
+    - test/**/*.rb
 Style/StringLiterals:
   EnforcedStyle: double_quotes
 Style/StringLiteralsInInterpolation:
   EnforcedStyle: double_quotes
+Style/SwapValues:
+  Enabled: true
 Style/SymbolArray:
   EnforcedStyle: brackets
 Style/TrailingCommaInArrayLiteral:

.rubocop_todo.yml

@@ -0,0 +1,25 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config --auto-gen-only-exclude`
+# on 2022-04-06 10:48:47 UTC using RuboCop version 1.26.1.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 1
+# This cop supports safe auto-correction (--auto-correct).
+Performance/BindCall:
+  Exclude:
+    - 'test/helper.rb'
+
+# Offense count: 1
+Style/CombinableLoops:
+  Exclude:
+    - 'lib/jekyll/tags/post_url.rb'
+
+# Offense count: 1
+# Configuration parameters: AllowedMethods.
+# AllowedMethods: respond_to_missing?
+Style/OptionalBooleanParameter:
+  Exclude:
+    - 'lib/jekyll/log_adapter.rb'

.travis.yml

@@ -1,60 +0,0 @@
-bundler_args: --without benchmark:development
-script: script/cibuild
-cache: bundler
-language: ruby
-
-rvm:
-  - &ruby1 2.7.1
-  - &ruby2 2.6.6
-  - &ruby3 2.5.8
-  - &ruby4 2.4.10
-  - &jruby jruby-9.2.11.1
-
-matrix:
-  include:
-    - rvm: *ruby1
-      env: TEST_SUITE=fmt
-      name: "🤖️ Code Format"
-    - rvm: *ruby1
-      env: TEST_SUITE=default-site
-      name: "🏠️ Default Site"
-    - rvm: *ruby1
-      env: TEST_SUITE=profile-docs
-      name: "Profile Docs"
-    - rvm: *ruby4
-      env: TEST_SUITE=memprof
-      name: "Profile Memory Allocation"
-  exclude:
-    - rvm: *jruby
-      env: TEST_SUITE=cucumber
-
-env:
-  matrix:
-    - TEST_SUITE=test
-    - TEST_SUITE=cucumber
-branches:
-  only:
-    - master
-    - themes
-    - /.*-stable/
-
-before_script:
-  - curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
-  - chmod +x ./cc-test-reporter
-  - ./cc-test-reporter before-build
-
-after_script:
-  - ./cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT
-
-notifications:
-  email: false
-  slack:
-    secure: "\
-      dNdKk6nahNURIUbO3ULhA09/vTEQjK0fNbgjVjeYPEvROHgQBP1cIP3AJy8aWs8rl5Yyow4Y\
-      GEilNRzKPz18AsFptVXofpwyqcBxaCfmHP809NX5PHBaadydveLm+TNVao2XeLXSWu+HUNAY\
-      O1AanCUbJSEyJTju347xCBGzESU=\
-    "
-
-before_install:
-  - gem update --system --no-document
-  - gem install bundler --no-document

Earthfile

@@ -0,0 +1,49 @@
+FROM alpine
+
+# Run locally: `earthly +all` to run full CI process
+all:
+    BUILD --build-arg RUBY=3.0 +test
+    BUILD --build-arg RUBY=2.7 +test
+    BUILD --build-arg RUBY=2.5 +test
+    BUILD --build-arg RUBY=jruby:9.2.14.0 +test
+    BUILD style-check
+    BUILD profile-docs
+
+# Run locally: `earthly +test`
+# Run with specific version: `earthly --build-arg RUBY=2.5 +test`
+test:
+    FROM +deps
+    RUN script/test    
+    RUN script/cucumber
+    RUN script/default-site
+
+style-check:
+    FROM +deps
+    RUN script/fmt
+
+profile-docs:
+    FROM +deps
+    RUN bundle install --jobs 4
+    RUN script/profile-docs
+    RUN script/memprof
+
+# Install dependencies and copy in source
+# used in above steps
+deps:
+    ARG RUBY=3.0
+    IF case $RUBY in jruby*) ;; *) false; esac
+        FROM $RUBY
+        ENV JRUBY_OPTS="--dev -J-XX:+TieredCompilation -J-XX:TieredStopAtLevel=1  -J-XX:CompileThreshold=10 -J-XX:ReservedCodeCacheSize=128M"
+    ELSE
+        FROM ruby:$RUBY
+    END
+    WORKDIR /src
+    RUN apt-get update && apt-get install nodejs dnsutils git make coreutils g++ build-essential -y
+    RUN gem install bundler
+    RUN gem install sassc -v '2.4.0' --source 'https://rubygems.org/'
+    COPY Gemfile .
+    COPY jekyll.gemspec .
+    COPY lib/jekyll/version.rb lib/jekyll/version.rb
+    COPY test test
+    RUN bundle install --jobs 4
+    COPY . .

Gemfile

@@ -3,11 +3,11 @@
 source "https://rubygems.org"
 gemspec :name => "jekyll"
 
-# Temporarily lock JRuby builds on Travis CI to i18n-1.2.x until JRuby is able to handle
-# refinements introduced in i18n-1.3.0
-gem "i18n", "~> 1.2.0" if RUBY_ENGINE == "jruby"
+gem "rake", "~> 13.0"
 
-gem "rake", "~> 12.0"
+if ENV["LIQUID_VERSION"] && ENV["LIQUID_VERSION"] != ""
+  gem "liquid", ENV["LIQUID_VERSION"]
+end
 
 group :development do
   gem "launchy", "~> 2.3"
@@ -19,7 +19,7 @@ end
 #
 
 group :test do
-  gem "cucumber", "~> 3.0"
+  gem "cucumber", RUBY_VERSION >= "2.5" ? "~> 5.1.2" : "~> 4.1"
   gem "httpclient"
   gem "jekyll_test_plugin"
   gem "jekyll_test_plugin_malicious"
@@ -27,14 +27,21 @@ group :test do
   gem "nokogiri", "~> 1.7"
   gem "rspec"
   gem "rspec-mocks"
-  gem "rubocop", "~> 0.72.0"
+  gem "rubocop", "~> 1.26.0"
+  gem "rubocop-minitest"
   gem "rubocop-performance"
+  gem "rubocop-rake"
+  gem "rubocop-rspec"
   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 "test-theme-skinny", :path => File.expand_path("test/fixtures/test-theme-skinny", __dir__)
   gem "test-theme-symlink", :path => File.expand_path("test/fixtures/test-theme-symlink", __dir__)
+  gem "test-theme-w-empty-data", :path => File.expand_path("test/fixtures/test-theme-w-empty-data", __dir__)
 
-  gem "jruby-openssl" if RUBY_ENGINE == "jruby"
+  if RUBY_ENGINE == "jruby"
+    gem "http_parser.rb", "~> 0.6.0"
+    gem "jruby-openssl"
+  end
 end
 
 #
@@ -70,11 +77,12 @@ group :jekyll_optional_dependencies do
   gem "jekyll-paginate"
   gem "jekyll-redirect-from"
   gem "kramdown-syntax-coderay"
+  gem "matrix"
   gem "mime-types", "~> 3.0"
-  gem "rdoc", "~> 6.0"
-  gem "tomlrb", "~> 1.2"
+  gem "rdoc", "~> 6.3.0"
+  gem "tomlrb"
 
-  platform :ruby, :mswin, :mingw, :x64_mingw do
+  platforms :ruby, :mswin, :mingw, :x64_mingw do
     gem "classifier-reborn", "~> 2.2"
     gem "liquid-c", "~> 4.0"
     gem "yajl-ruby", "~> 1.4"
@@ -82,8 +90,8 @@ group :jekyll_optional_dependencies do
 
   # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
   # and associated library
-  install_if -> { RUBY_PLATFORM =~ %r!mingw|mswin|java! } do
-    gem "tzinfo", "~> 1.2"
+  platforms :jruby, :mswin, :mingw, :x64_mingw do
+    gem "tzinfo", ENV["TZINFO_VERSION"] if ENV["TZINFO_VERSION"]
     gem "tzinfo-data"
   end
 end

History.markdown

@@ -1,3 +1,431 @@
+## HEAD
+
+  * Bump check-spelling/check-spelling from 0.0.18 to 0.0.19 (#8740)
+
+### Documentation
+
+  * typo - do instead of don't (#8518)
+  * Document support for TSV files consistently (#8488)
+  * Add a disclaimer to tutorials involving Ruby code (#8525)
+  * Improve documentation on developing generators (#8527)
+  * Fixes typo in layouts_dir documentation (#8532)
+  * Fix i.e. typos in collections.md (#8529)
+  * Remove GitHub Pages content which is in GitHub docs (#8533)
+  * Step By Step Instructions Review (#8399)
+  * Fix typo in migrating from 3.0 to 4.0 page (#8572)
+  * Fix for important missing step in macOS Installation Docs: Add the Homebrew gems directory to the PATH (#8496)
+  * Use latest Jekyll-action configuration (#8579)
+  * docs: troubleshoot macOS with ARM64 architecture (#8560)
+  * docs: add overview of .jekyll-cache dir (#8648)
+  * docs: clarify where .jekyll-metadata comes from (#8646)
+  * Razorops cicd added (#8656)
+  * Specify default port and host for serve commands in docs (#8624)
+  * Update third-party.md (#8652)
+  * Add documentation for Sass configuration options (#8587)
+  * Add formcarry to forms section (#8471)
+  * Add step to set SDKROOT (#8478)
+  * Improve the "Markdown Options" Docs (#8681)
+  * Add 'webrick' warning note to "Quickstart" Docs (#8727)
+  * Update windows.md (#8701)
+  * IRC networks - Libera, Freenode (#8706)
+  * Improve GitHub Flavored Markdown Docs (#8684)
+  * Fixing URL in MacOS install for rbenv-doctor (#8693)
+  * Fix adjective in `troubleshooting.md` document (#8777)
+  * Goodbye Frank. We'll miss you. 💔 (#8807)
+  * Update index.html: Grammar fix. (#8803)
+  * Prefer Libera. Remove Freenode. (#8811)
+  * Update feature_request.md (#8797)
+  * Remove AWS Amplify from the showcase (#8812)
+  * Move Frank to Emeritus Core Team Members (#8813)
+  * Release post for v4.2.1 (#8818)
+  * Update CircleCI example (#8829)
+  * Fix typo (#8835)
+  * Added docs for running locally (#8852)
+  * Linting README.markdown (#8900)
+  * Remove text on GITHUB_TOKEN which is now built-in (#8907)
+  * Add Security Policy document (#8823)
+  * Manage repository meta documents consistently (#8908)
+  * docs: add Layer0 deployment guide (#8915)
+  * docs: Update REAMDE generated by `jekyll new-theme` (#8919)
+  * Update resources.md (#8925)
+  * Rewrite documentation on installing plugins (#8921)
+  * Improve maintainers guide on releasing a new version (#8928)
+  * Fix link for "CloudSh" (#8934)
+  * Recommend using `actions/cache` in GitHub Actions documentation (#8948)
+  * Remove references to EOL hakiri.io service (#8946)
+  * Release post for v4.2.2 (#8982)
+  * Document releasing off `*-stable` branches (#8984)
+  * Update document by fix yaml syntax error (#8991)
+  * Enhance option's case for Jekyll configuration (#8992)
+  * Fix typo in `_docs/deployment/manual.md` (#8997)
+  * Add quiet/verbose options (#8996)
+  * Update README.markdown re IRC Pointer (#9005)
+  * Remove Aerobatic (#9007)
+  * Add Jekyll 3.9.2 release post to 'master' branch (#9013)
+  * Simplify macOS installation docs (#8993)
+  * Improve document about Github Actions section (#8853)
+  * Update permalinks.md  (#9017)
+
+### Bug Fixes
+
+  * Add webrick as a dependency (#8524)
+  * fix: pin rubocop to 1.12 due to error with ruby 2.4 (#8651)
+  * Load Jekyll plugins from BUNDLE_GEMFILE location (#8585)
+  * fix(security):  CVE-2021-28834 (#8680)
+  * Inject livereload script using `location.protocol` instead of `http:` (#8718)
+  * Respect collections_dir config within include tag (#8756)
+  * Fix regression in Convertible module from v4.2.0  (#8786)
+  * Revert #7253: "Don't reset site.url to localhost:4000 by default" (#8620)
+  * Improve readability of CI logs (#8877)
+  * Fix deprecation message for missing doc method (#8960)
+  * Fix response header for content served via `jekyll serve` (#8965)
+  * Trigger livereload in sites without pages (#8337)
+  * Only enable BOM encoding option on UTF encodings (#8363)
+
+### Development Fixes
+
+  * style: enable new cops (#8538)
+  * Allow dependabot to keep github actions up-to-date (#8540)
+  * Update actions/cache requirement to v2.1.3 (#8543)
+  * Pin rubocop version (#8564)
+  * style: add rubocop 1.9 cops (#8567)
+  * Cross Version Testing Locally and Faster CI (#8610)
+  * Use official Ruby setup GH action (#8614)
+  * Spell check action for markdown documentation (#8675)
+  * Update expect to cover docs/_posts (#8677)
+  * Enable Rubocop accessor grouping, fix existing offenses (#8293)
+  * Tags:Highlight: Decomposed HTMLLegacy formatter (#8623)
+  * Relax Rubocop Dependency (#8831)
+  * Add a workflow to build gems consistently (#8830)
+  * Fix random test failures in TestExcerpt #to_liquid (#8884)
+  * Lock gem `psych` to `v3.x` (#8918)
+  * Fix typo in Bug Report template (#8951)
+  * Check symlink outside site_source without Pathutil (#9015)
+  * Stop testing with Rubies older than 2.7 on non-Windows  (#8955)
+  * Bump actions/checkout from 2 to 3 (#8986)
+
+### Minor Enhancements
+
+  * Regenerate supported mime types (#8542)
+  * Update include tag to be more permissive (#8618)
+  * Optimize `Jekyll::Utils.parse_date` (#8425)
+  * Update rubocop from 1.12 to 1.18 and min ruby from 2.4 to 2.5 (#8741)
+  * Always hide cache-dir contents from Git (#8798)
+  * Remove the warning about auto-regeneration on Windows (#8821)
+  * Propagate _data folder from theme (#8815)
+  * Support both tzinfo v1 and v2 alongwith non-half hour offsets. (#8880)
+  * Run vendor-mimes to update mime.types (#8940)
+  * Expose collection static files via `site.static_files` (#8961)
+  * Expose `basename` from `document.rb` as `name` to Liquid templates (#8761)
+  * Allow Configurable Converters on CSV (#8858)
+
+### Site Enhancements
+
+  * Improvements to CSS (#7834)
+  * Slightly update lang `sh` code-block styling (#8857)
+
+## 4.2.2 / 2022-03-03
+
+### Bug Fixes
+
+  * Lock `http_parser.rb` gem to `v0.6.x` on JRuby.
+
+### Development Fixes
+
+  * Backport #8830 for v4.2.x: Add a workflow to build gems consistently (#8869)
+  * Lock `rubocop-performance` to `v1.11.x`.
+
+## 4.2.1 / 2021-09-27
+
+### Bug Fixes
+
+  * Backport #8620 for v4.2.x: Revert #7253: "Don't reset site.url to localhost:4000 by default" (#8808)
+  * Backport #8756 for v4.2.x: Respect collections_dir config within include tag (#8794)
+  * Backport #8786 for v4.2.x: Fix regression in Convertible module from v4.2.0 (#8793)
+
+## 4.2.0 / 2020-12-14
+
+### Minor Enhancements
+
+  * Warn on command-line with permalink conflict (#8342)
+  * Suppress warning issued for redirect pages (#8347)
+  * Enhance detection of conflicting destination URLs (#8459)
+  * Add `:post_convert` hook to modify HTML content before layout (#8368)
+  * Allow triggering `:post_convert` events atomically (#8465)
+  * Debug reading Page and Layout objects (#8100)
+  * Do not reset `site.url` to `http://localhost:4000` by default (#7253)
+  * Add custom debug strings for Jekyll objects (#8473)
+  * Debug reading data files in a site (#8481)
+
+### Bug Fixes
+
+  * Replace nested conditional with guard clauses (#8294)
+  * Fix: security bump (#8349)
+  * Fix path matching regex in post_url Liquid tag (#8375)
+  * Enable `Performance/ChainArrayAllocation` cop (#8404)
+  * Enable Lint/NoReturnInBeginEndBlocks Cop (#8457)
+  * Generate items from `site.include` list only once (#8463)
+  * Explicitly return nil after site process phase (#8472)
+
+### Optimization Fixes
+
+  * Implement custom delegators for drop methods (#8183)
+  * Handle `nil` argument to `Jekyll.sanitized_path` (#8415)
+  * Cache `Jekyll.sanitized_path` (#8424)
+  * Memoize array of drop getter method names (#8421)
+  * Reduce string allocations from the `link` tag (#8387)
+  * Optimize parsing of parameters in `include` tag (#8192)
+  * Stash documents `write?` attribute in a variable (#8389)
+  * Reduce string allocations from generating doc URLs (#8392)
+  * Check if site is in incremental mode optimally (#8401)
+  * Utilize flexibility of `Site#in_dest_dir` (#8403)
+  * Reduce allocations from rendering item as liquid (#8406)
+  * Compute relative_path of pages using PathManager (#8408)
+  * Reduce allocation from `normalize_whitespace` filter (#8400)
+  * Use `Regexp#match?` when `MatchData` is not required (#8427)
+  * Check default front matter scope against symbols (#8393)
+  * Stash frequently used `Drop` setter keys for reuse (#8394)
+  * Memoize defaults computed for Convertibles (#8451)
+  * Reduce array allocations from merging categories (#8453)
+  * Memoize destination of pages, documents and staticfiles (#8458)
+  * Reduce allocations from computing item property (#8485)
+  * Optimize `Page#dir` with a private method (#8489)
+  * Stash attribute hash for Liquid computed for pages (#8497)
+
+### Development Fixes
+
+  * Update cucumber gem to version 4.1 (#8278)
+  * Move permalink styles data to constant (#8282)
+  * Update rubocop gem to 0.87.1 (#8287)
+  * Update RuboCop to-do file (#8296)
+  * Fix `rake console` generating LoadError (#8312)
+  * Configure Performance cops (#8369)
+  * Update rubocop gem to 0.90.0 (#8313)
+  * Refactor `Jekyll::Utils::Platforms` (#7236)
+  * Bump RuboCop to v0.91.x (#8391)
+  * Add workflow to build and profile third-party repo (#8398)
+  * Bump RuboCop to v0.92.x
+  * Update cucumber gem version to 5.1.2 (#8413)
+  * Fix test suite compatibility with JRuby (#8418)
+  * chore(deps): bump Rubocop to 0.93.0 (#8430)
+  * Use Ruby 2.7.1 in GitHub Actions (#8444)
+  * Test that Liquid expressions are not deeply evaled (#8292)
+  * Test rendering arbitrary Liquid variables by default (#7414)
+  * Migrate TravisCI jobs to GitHub Actions (#8492)
+
+### Documentation
+
+  * Update pointer to special permalink variables for collections (#8274)
+  * Fix special treatment for 'page 1' in docs of pagination (#8230)
+  * Add Formcake to forms section (#8283)
+  * Add a note on the rendering process in the docs (#8291)
+  * Add refactoring type to PULL_REQUEST_TEMPLATE (#8297)
+  * Update resources.md (#7864)
+  * Extra apostrophes in an URL (#8319)
+  * Clarify target of subordinate clause (#8320)
+  * Cherry-pick commits from conflicting branch `docs-40`
+  * Update documentation on third party site (#8352)
+  * Update default.md with info requested in #8314 (#8353)
+  * Clarify description of `safe` option (#8354)
+  * Simplifying the Git post-receive hook-example (#8358)
+  * Add missing doc for build and serve commands (#8365)
+  * Docs Review: Getting Started (#8372)
+  * Add note about rebooting system after installation (#8359)
+  * Use data file to render table at `/docs/configuration/options/#global-configuration` (#8377)
+  * Use data file(s) to render table(s) at `/docs/configuration/options/` (#8380)
+  * Improve maintainability of config option data (#8383)
+  * Remove CircleCI v1 docs (#8410)
+  * Remove `NOKOGIRI_USE_SYSTEM_LIBRARIES` from Travis CI docs (#8409)
+  * Add links to all Jekyll themes on GitHub tagged with #jekyll-theme (#8447)
+  * Document initializing project Gemfile from scratch (#8450)
+  * Document installation of additional dependencies for installing Jekyll on Fedora (#8456)
+  * Improve documentation on Hooks in Jekyll (#8467)
+  * Build docs site with GitHub Actions (#8201)
+  * Add link to Assets page from `_sass` section in `_docs/structure.md` (#8486)
+
+### Site Enhancements
+
+  * Fix rendering of *showcase* images (#8504)
+
+## 4.1.1 / 2020-06-24
+
+### Bug Fixes
+
+  * Disable page excerpts by default (#8222)
+  * Revert introduction of PageDrop (#8221)
+  * Don't generate excerpts for non-html pages (#8234)
+  * Make page excerpts consistent with doc excerpts (#8236)
+
+### Documentation
+
+  * Replace deprecated 'show' command with 'info' (#8235)
+  * Change name to ▲Vercel (#8247)
+  * Add language and examples to describe how to use the configuration op… (#8249)
+  * Fix missing yaml front matter colon and adjust/add clarifying language. (#8250)
+  * correct typo (#8261)
+  * Allow hyperlinks to specific filter documentation (#8231)
+  * Update link to Netlify step-by-step guide (#8264)
+  * Fix grammar in documentation section (#8265)
+
+### Site Enhancements
+
+  * Including correct Sketch website (#8241)
+  * Release post for v4.1.1 (#8243)
+
+### Development Fixes
+
+  * Bump RuboCop to v0.85.x (#8223)
+  * Expect drive letter only on vanilla windows (#8227)
+
+## 4.1.0 / 2020-05-27
+
+### Bug Fixes
+
+  * Memoize `absolute_url` and `relative_url` filters (#7793)
+  * Fix documentation comment for `Jekyll::Converters::Identity` (#7883)
+  * Optimize `Jekyll::Filters#item_property` (#7696)
+  * Allow multiple binary operators in `where_exp` filter (#8047)
+  * Fix documents custom-ordering logic (#8028)
+  * Use `layout.path` when rendering the Liquid layout (#8069)
+  * Reduce array allocations from `StaticFile#path` (#8083)
+  * Simplify `Jekyll::Renderer#validate_layout` (#8064)
+  * Add static file's basename to its `url_placeholder` (#7908)
+  * Clear cached Liquid template scope before render (#7967)
+  * Cache `URLFilter` results of string inputs per site (#7990)
+  * Use `platforms` instead of `install_if` in Gemfile (#8140)
+  * Config include trailing slash (#8113)
+  * Improve path normalization in liquid_renderer (#8075)
+  * Switch slugify regex to support more Unicode character groups (#8167)
+  * Check if entry is a directory once per enumerator (#8177)
+  * Filter out exclusively excluded entries sooner (#7482)
+  * Return `relative_url` if site.url is an empty string (#7988)
+  * Configure kramdown toc_levels as array by default (#8015)
+  * Reduce `Pathname` objects from front matter defaults (#8067)
+  * Simplify `Jekyll::Hooks.trigger` logic (#8044)
+  * Quicker categories for documents without superdirs (#7987)
+  * Reduce `Jekyll::Renderer` instances during a build (#7570)
+  * Escape regex characters in paths to match (#8138)
+  * Provide invokables for common drop query keys (#8165)
+  * Optimize path sanitization of default front matter (#8154)
+  * Initialize static files' data hash only if needed (#8188)
+  * Initialize include-files as Jekyll objects (#8158)
+
+### Minor Enhancements
+
+  * serve: add support for ECC certificates (#7768)
+  * Update `item_property` to recognize integers (#7878)
+  * Include `_config.yml` in a new theme's gemspec (#7865)
+  * Add an option to easily disable disk-cache (#7928)
+  * Optimize markdown parsing with Kramdown by reusing the options and parser objects (#8013)
+  * Add `PageDrop` to provide Liquid templates with data (#7992)
+  * Optimize `Kramdown::JekyllDocument#to_html` calls (#8041)
+  * Configure default language for syntax-highlighting (#8035)
+  * Remove dev dependencies from new theme-gem gemspec (#8042)
+  * Allow disabling import of theme configuration (#8131)
+  * Allow excerpts to be generated for `Page` objects (#7642)
+  * Profile various stages of a site's build process (#6760)
+  * Add find filters to optimize where-first chains (#8171)
+  * Make `number_of_words` filter respect CJK characters (#7813)
+  * Allow extensionless document in a strict site (#7950)
+  * Add `:slugified_categories` URL placeholder (#8094)
+
+### Documentation
+
+  * Add dropped 'title: Staff' to the code (#7805)
+  * Clarify docs for static files in collection (#7812)
+  * Rephrase the CircleCI v2 section (#7815)
+  * Update old GitHub wiki URL with new one (#7823)
+  * Update JekyllConf page with 2019 talks (#7826)
+  * link for memberships (#7825)
+  * Doc: minor fix, should be greater or equal to min version (#7856)
+  * Update third-party.md - Fix broken link (#7857)
+  * clarify _config.yml/collections type (#7873)
+  * Replace backticks with HTML tags in data file (#7879)
+  * add new theme source (#7875)
+  * fixed grammatical error (it's --> its) (#7887)
+  * Docs: Clarify organizing pages into subfolders (#7896)
+  * Disambiguate the placeholder of permalink (#7906)
+  * docs: add short serve command for livereload (#7919)
+  * docs: add options for watch and force polling (#7918)
+  * add install instructions for ArchLinux and openSUSE (#7920)
+  * Improve index page of Jekyll documentation  (#7926)
+  * Include path in `jekyll new` commands (Usage docs) (#7931)
+  * Change `affect` to `effect` in the collections docs (#7937)
+  * Changed deprecated command in themes documentation (#7941)
+  * Adds some documentation for the `:clean`, `:on_obsolete` hook (#7954)
+  * docs: fix broken link (#7955)
+  * Corrected typo (#7975)
+  * docs: remove watch option in config (#7940)
+  * Correct a sentence in the documentation (#7978)
+  * Fix YAML representation of `group_by` result (#7979)
+  * Move `--baseurl` to build command options (#7985)
+  * Correct documentation of filters (#7989)
+  * Document sorting two documents by their `date` (#7870)
+  * Fix English grammar error (#7994)
+  * Update 03-front-matter.md (#7996)
+  * Add Kentico Kontent CMS integration to resources (#8000)
+  * Update 07-assets.md (#7413)
+  * Fix file references in Step by Step Tutorial's Assets step (#8007)
+  * docs: improve highlighting of code blocks (#8017)
+  * remove leading slash from Sass file location (#8021)
+  * [Docs] Fix asset link ref in step-by-step tutorial (#8026)
+  * Corrected command to modify PATH (#8029)
+  * Corrected command to modify PATH (#8030)
+  * Docs: Render full contents of just the latest post (#8032)
+  * docs: improvements for note boxes (#8037)
+  * Non-deprecated `vendor/bundle` path configuration (#8048)
+  * Update 09-collections.md (#8060)
+  * Remove extra paragraph tags (#8063)
+  * Add default front matter for tutorials collection (#8081)
+  * Create CSV to table tutorial (#8090)
+  * Add version badge for Custom Sorting of Documents (#8098)
+  * Docs: Fix grammar in `_docs/front-matter.md` (#8097)
+  * Update variables.md (#8106)
+  * Add help about Gentoo/Linux (#8002)
+  * Update documentation on third party site (#8122)
+  * Added Clear Linux (#8132)
+  * Added note about OS specific installation instructions. (#8135)
+  * Fix broken URL in the Resources Page on the Documentation Site (#8136)
+  * Docs: Deploy Jekyll site with GitHub Actions (#8119)
+  * Clarify `bundle config` in Bundler tutorial (#8150)
+  * docs: update your-first-plugin.md (#8147)
+  * Fix typo in documentation on GitHub Actions (#8162)
+  * Ease discovery of CLI commands (in their entirety) (#8178)
+  * Remove `sudo` from Travis CI tutorial (#8187)
+  * Add GitLab Pages to 3rd party list (#8191)
+  * docs: add 21yunbox for deployment (#8193)
+  * Improve documentation on tags and categories (#8196)
+
+### Development Fixes
+
+  * Ci/GitHub actions (#7822)
+  * Rubocop version upgrade (#7846)
+  * Split action steps to avoid using `&&` on Windows (#7885)
+  * Upgrade rake to use version 13 (#7910)
+  * Update dependency constraint to allow RuboCop v0.76 (#7893)
+  * Use bash executable consistently (#7909)
+  * Test with JRuby 9.2.9.0 (#7779)
+  * Bump RuboCop to v0.79.x (#7970)
+  * Remove post-install message from gemspec (#7974)
+  * Attain Ruby 3.0 compatibility (#7948)
+  * Test `where` filter handling numeric property values (#7821)
+  * chore(deps): rubocop 0.80.0 (#8012)
+  * Update unit tests for Kramdown-based converter (#8014)
+  * Add Visual Studio Code Development Container (#8016)
+  * chore: simplify require for `Jekyll::VERSION` (#8057)
+  * Remove version-constraint relaxation for i18n gem (#8055)
+  * Mirror `spec.homepage` as `metadata["homepage_uri"]` (#8056)
+  * Bump Ruby versions on Travis builds (#8088)
+  * chore(ci): cache dependencies (#8168)
+
+### Site Enhancements
+
+  * Optimize rendering of the documentation site (#8020)
+  * Utilize `relative_url` filter in documentation site (#8089)
+  * Render tutorial metadata in documentation site (#8092)
+  * Improve syntax-highlighting in documentation site (#8079)
+  * Site: Filter through just the *docs* collection (#8170)
+
 ## 4.0.1 / 2020-05-08
 
 ### Bug Fixes
@@ -11,6 +439,38 @@
 
   * Fix Kramdown converter based tests for v4.0.x (#8143)
 
+## 3.9.2 / 2022-03-27
+
+### Bug Fixes
+
+  * Lock `http_parser.rb` gem to `v0.6.x` on JRuby (#8943)
+  * Backport #8756 for v3.9.x: Respect collections_dir config within include tag (#8795)
+  * Backport #8965 for v3.9.x: Fix response header for content served via `jekyll serve` (#8976)
+
+### Development Fixes
+
+  * Update and fix CI for `3.9-stable` on Ruby 3.x (#8942)
+  * Fix CI for commits to `3.9-stable` branch (#8788)
+
+## 3.9.1 / 2021-04-08
+
+### Bug Fixes
+
+  * Backport #8618 for v3.9.x: Update include tag to be more permissive (#8629)
+
+## 3.9.0 / 2020-08-05
+
+### Minor Enhancements
+
+  * Allow use of kramdown v2 (#8322)
+  * Add default language for kramdown syntax highlighting (#8325)
+
+## 3.8.7 / 2020-05-08
+
+### Bug Fixes
+
+  * Prevent console warnings with Ruby 2.7 (#8125)
+
 ## 4.0.0 / 2019-08-19
 
 ### Major Enhancements
@@ -261,7 +721,7 @@
   * Remove alt attribute from a tags (#7407)
   * Fix BASH code-block in ubuntu.md (#7420)
   * zlib is missing (#7428)
-  * Fixed unnecessary aticles and pronouns (#7466)
+  * Fixed unnecessary articles and pronouns (#7466)
   * Store SSL key and cert in site source (#7473)
   * Fix typo in tutorial for converting existing site (#7524)
   * Check if var exists before include tag (#7530)
@@ -276,7 +736,7 @@
   * fix link to Site Source config (#7708)
   * Introduce frontmatter in step 2 (#7704)
   * Add @ashmaroli to Core Team listing (#7398)
-  * Lnk to Tidelift in site's footer (#7377)
+  * Link to Tidelift in site's footer (#7377)
   * Link to OpenCollective backing (#7378
   * Link to sponsor listing in README (#7405)
   * Adjust team page listings (#7395)
@@ -297,6 +757,7 @@
 
 ### Release
 
+  * Jekyll v4.0 release (#7782)
   * Release post for v4.0.0 beta1 (#7716)
   * Release post for v4.0.0.pre.alpha1 (#7574)
   * Release post for v3.8.0 (#6849)
@@ -426,7 +887,7 @@
   * doc: add liquid tag plugin jekyll-onebox for html previews (#6898)
   * Add `jekyll-w2m` to plugins (#6855)
   * Fix tutorials navigation HTML (#6919)
-  * add Arch Linux instalation troubleshoot (#6782)
+  * add Arch Linux installation troubleshoot (#6782)
   * Docs: Install Jekyll on macOS (#6881)
   * Fix CodeClimate badges [ci skip] (#6930)
   * Update index.md (#6933)
@@ -582,7 +1043,7 @@
   * Fix list appearance by adding missing `ol` tag (#6421)
   * Explain how to override output collection index page (#6424)
   * Added github-cards to the list of plugins (#6425)
-  * CoC violation correspondants (#6429)
+  * CoC violation correspondents (#6429)
   * Add a note about Liquid and syntax highlighting (#6466)
   * Remove `sudo` from macOS troubleshooting instructions (#6486)
   * Add a note on `:jekyll_plugins` group in the docs (#6488)
@@ -698,7 +1159,7 @@
   * add SUPPORT file for GitHub (#6324)
   * Rename CODE_OF_CONDUCT to show in banner (#6325)
   * Docs : illustrate page.id for a collection's document (#6329)
-  * Docs: post's date can be overriden in front matter (#6334)
+  * Docs: post's date can be overridden in front matter (#6334)
   * Docs: `site.url` behavior on development and production environments (#6270)
   * Fix typo in site.url section of variables.md :-[ (#6337)
   * Docs: updates (#6343)
@@ -746,7 +1207,7 @@
 
 ### Bug Fixes
 
-  * Backward compatiblize URLFilters module (#6163)
+  * Backward compatibilize URLFilters module (#6163)
   * Static files contain front matter default keys when `to_liquid`'d  (#6162)
   * Always normalize the result of the `relative_url` filter (#6185)
 
@@ -1216,7 +1677,7 @@
 
 ### Minor Enhancements
 
-  * Stop testing with Ruby 2.0.x, which is EOL'd. (#4381)
+  * Stop testing with Ruby 2.0.x EOL (#4381)
   * Allow collections to have documents that have no file extension (#4545)
   * Add size property to `group_by` result (#4557)
   * Site Template: Removed unnecessary nesting from `_base.scss` (#4637)
@@ -1242,7 +1703,7 @@
   * Add 'jekyll new-theme' command to help users get up and running creating a theme (#4848)
   * `markdownify` and `smartify` should convert input to string before conversion (#4958)
   * Run `Site#generate` for 'jekyll doctor' to catch plugin issues (#5005)
-  * Add `normalize_whitepace` filter (#4917)
+  * Add `normalize_whitespace` filter (#4917)
   * Move bin/jekyll to exe/jekyll to prevent collision with binstubs (#5014)
   * Cleaning up site template & theme updates. (#4922)
   * Add fetch method to Drops (#5056)
@@ -1291,7 +1752,7 @@
   * Fix state leakage in Kramdown test (#4618)
   * Unify method for copying special files from repo to site (#4601)
   * Refresh the contributing file (#4596)
-  * change smartify doc from copy/paste of mardownify doc (#4653)
+  * change smartify doc from copy/paste of markdownify doc (#4653)
   * Update Rake & disable warnings when running tests (#4720)
   * Fix many warnings (#4537)
   * Don't blindly assume the last system when determining "open" cmd (#4717)
@@ -1389,7 +1850,7 @@
   * Corrected pagination docs for hidden: true feature (#4903)
   * Remove a Broken Link for Refheap Plugin (#4971)
   * Instructions on how to install github-gem on Windows (#4975)
-  * Minor tweak to fix missing apostrophne (#4962)
+  * Minor tweak to fix missing apostrophe (#4962)
   * Instructions on how to install github-gem on Windows (v2) (#4977)
   * Fix inaccurate HTTP response header field name (#4976)
   * Add post about GSoC project (#4980)
@@ -1397,10 +1858,10 @@
   * Update normalize.css to v4.0.0. (#4989)
   * Add jekyll-tags-list-plugin to list of third-party plugins (#5000)
   * Windows docs: Command needs to be called from blog path (#5006)
-  * Update text to be consitent with example (#5010)
+  * Update text to be consistent with example (#5010)
   * Update template links to point to core Liquid site (#5012)
   * Add generator-jekyllized to third-party plugins (#5027)
-  * Add Jekyll Art Hallery generator plugin to list of third-party plugins (#5043)
+  * Add Jekyll Art Gallery generator plugin to list of third-party plugins (#5043)
   * Add Formingo to the list of Jekyll form SaaS (#5054)
   * Highlight help nav item when navigated to. (#5058)
   * Update normalize.css to v4.2.0. (#5096)
@@ -1552,9 +2013,9 @@
   * Reorganize and cleanup the Gemfile, shorten required depends. (#4318)
   * Remove script/rebund. (#4341)
   * Implement codeclimate platform (#4340)
-  * Remove ObectSpace dumping and start using inherited, it's faster. (#4342)
+  * Remove ObjectSpace dumping and start using inherited, it's faster. (#4342)
   * Add script/travis so all people can play with Travis-CI images. (#4338)
-  * Move Cucumber to using RSpec-Expections and furthering JRuby support. (#4343)
+  * Move Cucumber to using RSpec-Expectations and furthering JRuby support. (#4343)
   * Rearrange Cucumber and add some flair. (#4347)
   * Remove old FIXME (#4349)
   * Clean up the Gemfile (and keep all the necessary dependencies) (#4350)
@@ -1887,7 +2348,7 @@
   * Define the `install` step in the CI example `.travis.yml` (#3622)
   * Expand collections documentation. (#3638)
   * Add the "warning" note label to excluding `vendor` in the CI docs page (#3623)
-  * Upgrade pieces of the Ugrading guide for Jekyll 3 (#3607)
+  * Upgrade pieces of the Upgrading guide for Jekyll 3 (#3607)
   * Showing how to access specific data items (#3468)
   * Clarify pagination works from within HTML files (#3467)
   * Add note to `excerpt_separator` documentation that it can be set globally (#3667)
@@ -2882,7 +3343,7 @@
   * Add ReadInXMinutes plugin to the plugin list (#1222)
   * Remove plugins from the plugin list that have equivalents in Jekyll proper (#1223)
   * Add jekyll-assets to the plugin list (#1225)
-  * Add jekyll-pandoc-mulitple-formats to the plugin list (#1229)
+  * Add jekyll-pandoc-multiple-formats to the plugin list (#1229)
   * Remove dead link to "Using Git to maintain your blog" (#1227)
   * Tidy up the third-party plugins listing (#1228)
   * Update contributor information (#1192)
@@ -3035,7 +3496,7 @@
   * Adds excerpt attribute to posts which contains first paragraph of content (#837)
   * Accept custom configuration file via CLI (#863)
   * Load in GitHub Pages MIME Types on `jekyll serve` (#847, #871)
-  * Improve debugability of error message for a malformed highlight tag (#785)
+  * Improve debuggability of error message for a malformed highlight tag (#785)
   * Allow symlinked files in unsafe mode (#824)
   * Add 'gist' Liquid tag to core (#822, #861)
   * New format of Jekyll output (#795)

README.markdown

@@ -1,19 +1,13 @@
 # [Jekyll](https://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]
+[![Linux Build Status](https://github.com/jekyll/jekyll/workflows/Continuous%20Integration/badge.svg)][ci-workflow]
 [![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]
-[![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
-[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
+[ci-workflow]: https://github.com/jekyll/jekyll/actions?query=workflow%3A%22Continuous+Integration%22+branch%3Amaster
 [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.
@@ -22,7 +16,7 @@ Jekyll is a simple, blog-aware, static site generator perfect for personal, proj
 
 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
+See: [https://jekyllrb.com/philosophy](https://jekyllrb.com/philosophy)
 
 ## Getting Started
 
@@ -30,7 +24,7 @@ See: https://jekyllrb.com/philosophy
 * Read up about its [Usage](https://jekyllrb.com/docs/usage/) and [Configuration](https://jekyllrb.com/docs/configuration/)
 * Take a gander at some existing [Sites](https://github.com/jekyll/jekyll/wiki/sites)
 * [Fork](https://github.com/jekyll/jekyll/fork) and [Contribute](https://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/)
+* Have questions? Check out our official forum community [Jekyll Talk](https://talk.jekyllrb.com/) and [`#jekyll` Channel on Libera IRC](https://libera.chat)
 
 ## Diving In
 
@@ -49,7 +43,7 @@ If you don't find the answer to your problem in our [docs](https://jekyllrb.com/
 ## 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](https://jekyllrb.com/docs/conduct/) adapted from the Ruby on Rails code of
 conduct.
 
 Please adhere to this code of conduct in any interactions you have in the
@@ -62,28 +56,27 @@ these terms, please let one of our [core team members](https://jekyllrb.com/team
 ### Sponsors
 
 Support this project by becoming a sponsor. Your logo will show up in this README 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>
-<a href="https://opencollective.com/jekyll/sponsor/3/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/3/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/4/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/4/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/5/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/5/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/6/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/6/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/7/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/7/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/8/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/8/avatar.svg" /></a>
-<a href="https://opencollective.com/jekyll/sponsor/9/website" target="_blank"><img src="https://opencollective.com/jekyll/sponsor/9/avatar.svg" /></a>
+[![Jekyll Sponsor 0](https://opencollective.com/jekyll/sponsor/0/avatar.svg)](https://opencollective.com/jekyll/sponsor/0/website)
+[![Jekyll Sponsor 1](https://opencollective.com/jekyll/sponsor/1/avatar.svg)](https://opencollective.com/jekyll/sponsor/1/website)
+[![Jekyll Sponsor 2](https://opencollective.com/jekyll/sponsor/2/avatar.svg)](https://opencollective.com/jekyll/sponsor/2/website)
+[![Jekyll Sponsor 3](https://opencollective.com/jekyll/sponsor/3/avatar.svg)](https://opencollective.com/jekyll/sponsor/3/website)
+[![Jekyll Sponsor 4](https://opencollective.com/jekyll/sponsor/4/avatar.svg)](https://opencollective.com/jekyll/sponsor/4/website)
+[![Jekyll Sponsor 5](https://opencollective.com/jekyll/sponsor/5/avatar.svg)](https://opencollective.com/jekyll/sponsor/5/website)
+[![Jekyll Sponsor 6](https://opencollective.com/jekyll/sponsor/6/avatar.svg)](https://opencollective.com/jekyll/sponsor/6/website)
+[![Jekyll Sponsor 7](https://opencollective.com/jekyll/sponsor/7/avatar.svg)](https://opencollective.com/jekyll/sponsor/7/website)
+[![Jekyll Sponsor 8](https://opencollective.com/jekyll/sponsor/8/avatar.svg)](https://opencollective.com/jekyll/sponsor/8/website)
+[![Jekyll Sponsor 9](https://opencollective.com/jekyll/sponsor/9/avatar.svg)](https://opencollective.com/jekyll/sponsor/9/website)
 
 ### 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>
+[![Jekyll Contributors](https://opencollective.com/jekyll/contributors.svg?width=890&button=false)](../../graphs/contributors)
 
 ### 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>
+[![Jekyll Backers](https://opencollective.com/jekyll/backers.svg?width=890)](https://opencollective.com/jekyll#backers)
 
 ## License
 

Rakefile

@@ -159,5 +159,5 @@ end
 
 desc "Open an irb session preloaded with this library"
 task :console do
-  sh "irb -rubygems -r ./lib/#{name}.rb"
+  sh "irb -r ./lib/#{name}.rb"
 end

appveyor.yml

@@ -13,9 +13,11 @@ build: off
 environment:
   BUNDLE_WITHOUT: "benchmark:development"
   matrix:
-    - RUBY_FOLDER_VER: "24"
+    - RUBY_FOLDER_VER: "26"
+      TZINFO_VERSION: "~> 1.2"
       TEST_SUITE: "test"
     - RUBY_FOLDER_VER: "26"
+      TZINFO_VERSION: "~> 2.0"
       TEST_SUITE: "test"
     - RUBY_FOLDER_VER: "26"
       TEST_SUITE: "default-site"
@@ -24,6 +26,10 @@ environment:
     - RUBY_FOLDER_VER: "26"
       TEST_SUITE: "memprof"
     - RUBY_FOLDER_VER: "26"
+      TZINFO_VERSION: "~> 1.2"
+      TEST_SUITE: "cucumber"
+    - RUBY_FOLDER_VER: "26"
+      TZINFO_VERSION: "~> 2.0"
       TEST_SUITE: "cucumber"
 
 install:

benchmark/find-filter-vs-where-first-filters.rb

@@ -0,0 +1,49 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'benchmark/ips'
+require_relative '../lib/jekyll'
+
+puts ''
+print 'Setting up... '
+
+SITE = Jekyll::Site.new(
+  Jekyll.configuration({
+    "source"             => File.expand_path("../docs", __dir__),
+    "destination"        => File.expand_path("../docs/_site", __dir__),
+    "disable_disk_cache" => true,
+    "quiet"              => true,
+  })
+)
+
+TEMPLATE_1 = Liquid::Template.parse(<<~HTML)
+  {%- assign doc = site.documents | where: 'url', '/docs/assets/' | first -%}
+  {{- doc.title -}}
+HTML
+
+TEMPLATE_2 = Liquid::Template.parse(<<~HTML)
+  {%- assign doc = site.documents | find: 'url', '/docs/assets/' -%}
+  {{- doc.title -}}
+HTML
+
+[:reset, :read, :generate].each { |phase| SITE.send(phase) }
+
+puts 'done.'
+puts 'Testing... '
+puts "  #{'where + first'.cyan} results in #{TEMPLATE_1.render(SITE.site_payload).inspect.green}"
+puts "  #{'find'.cyan} results in #{TEMPLATE_2.render(SITE.site_payload).inspect.green}"
+
+if TEMPLATE_1.render(SITE.site_payload) == TEMPLATE_2.render(SITE.site_payload)
+  puts 'Success! Proceeding to run benchmarks.'.green
+  puts ''
+else
+  puts 'Something went wrong. Aborting.'.magenta
+  puts ''
+  return
+end
+
+Benchmark.ips do |x|
+  x.report('where + first') { TEMPLATE_1.render(SITE.site_payload) }
+  x.report('find') { TEMPLATE_2.render(SITE.site_payload) }
+  x.compare!
+end

benchmark/parse-date

@@ -0,0 +1,25 @@
+#!/usr/bin/env ruby
+
+require_relative '../lib/jekyll'
+require 'benchmark/ips'
+
+date = "2014-08-02 14:43:06 PDT".freeze
+time = Time.parse(date)
+
+Benchmark.ips do |x|
+  x.report('Time.parse') do
+    Time.parse(date)
+  end
+
+  x.report('localtime') do
+    Time.parse(date).localtime
+  end
+
+  x.report('localtime parsed') do
+    time.localtime
+  end
+
+  x.report('Utils.parse_date') do
+    Jekyll::Utils.parse_date(date)
+  end
+end

benchmark/parse-include-tag-params.rb

@@ -0,0 +1,91 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+# For pull request: https://github.com/jekyll/jekyll/pull/8192
+
+require 'benchmark/ips'
+require 'bundler/setup'
+require 'memory_profiler'
+require 'jekyll'
+
+CONTEXT = {"bar"=>"The quick brown fox"}
+MARKUP_1 = %Q(foo=bar lorem="ipsum \\"dolor\\"" alpha='beta \\'gamma\\'').freeze
+MARKUP_2 = %Q(foo=bar lorem="ipsum 'dolor'" alpha='beta "gamma"').freeze
+
+#
+
+def old_parse_params(markup)
+  params = {}
+
+  while (match = Jekyll::Tags::IncludeTag::VALID_SYNTAX.match(markup))
+    markup = markup[match.end(0)..-1]
+
+    value = if match[2]
+              match[2].gsub('\\"', '"')
+            elsif match[3]
+              match[3].gsub("\\'", "'")
+            elsif match[4]
+              CONTEXT[match[4]]
+            end
+
+    params[match[1]] = value
+  end
+  params
+end
+
+def new_parse_params(markup)
+  params = {}
+  markup.scan(Jekyll::Tags::IncludeTag::VALID_SYNTAX) do |key, d_quoted, s_quoted, variable|
+    value = if d_quoted
+              d_quoted.include?('\\"') ? d_quoted.gsub('\\"', '"') : d_quoted
+            elsif s_quoted
+              s_quoted.include?("\\'") ? s_quoted.gsub("\\'", "'") : s_quoted
+            elsif variable
+              CONTEXT[variable]
+            end
+
+    params[key] = value
+  end
+  params
+end
+
+#
+
+def report(label, markup, color)
+  prof_report = MemoryProfiler.report { yield }
+
+  allocated_memory  = prof_report.scale_bytes(prof_report.total_allocated_memsize)
+  allocated_objects = prof_report.total_allocated
+  retained_memory   = prof_report.scale_bytes(prof_report.total_retained_memsize)
+  retained_objects  = prof_report.total_retained
+
+  puts <<~MSG.send(color)
+    #{(label + " ").ljust(49, "-")}
+
+    MARKUP: #{markup}
+    RESULT: #{yield}
+
+    Total allocated: #{allocated_memory} (#{allocated_objects} objects)
+    Total retained:  #{retained_memory} (#{retained_objects} objects)
+  MSG
+end
+
+report('old w/ escaping', MARKUP_1, :magenta) { old_parse_params(MARKUP_1) }
+report('new w/ escaping', MARKUP_1, :cyan)    { new_parse_params(MARKUP_1) }
+
+report('old no escaping', MARKUP_2, :green)  { old_parse_params(MARKUP_2) }
+report('new no escaping', MARKUP_2, :yellow) { new_parse_params(MARKUP_2) }
+
+#
+
+Benchmark.ips do |x|
+  x.report("old + esc".magenta) { old_parse_params(MARKUP_1) }
+  x.report("new + esc".cyan)    { new_parse_params(MARKUP_1) }
+  x.compare!
+end
+
+Benchmark.ips do |x|
+  x.report("old - esc".green)  { old_parse_params(MARKUP_2) }
+  x.report("new - esc".yellow) { new_parse_params(MARKUP_2) }
+  x.compare!
+end

benchmark/path-manager.rb

@@ -0,0 +1,65 @@
+# frozen_string_literal: true
+
+require 'benchmark/ips'
+require 'jekyll'
+
+class FooPage
+  def initialize(dir:, name:)
+    @dir = dir
+    @name = name
+  end
+
+  def slow_path
+    File.join(*[@dir, @name].map(&:to_s).reject(&:empty?)).sub(%r!\A/!, "")
+  end
+
+  def fast_path
+    Jekyll::PathManager.join(@dir, @name).sub(%r!\A/!, "")
+  end
+end
+
+nil_page     = FooPage.new(:dir => nil, :name => nil)
+empty_page   = FooPage.new(:dir => "", :name => "")
+root_page    = FooPage.new(:dir => "", :name => "ipsum.md")
+nested_page  = FooPage.new(:dir => "lorem", :name => "ipsum.md")
+slashed_page = FooPage.new(:dir => "/lorem/", :name => "/ipsum.md")
+
+if nil_page.slow_path == nil_page.fast_path
+  Benchmark.ips do |x|
+    x.report('nil_page slow') { nil_page.slow_path }
+    x.report('nil_page fast') { nil_page.fast_path }
+    x.compare!
+  end
+end
+
+if empty_page.slow_path == empty_page.fast_path
+  Benchmark.ips do |x|
+    x.report('empty_page slow') { empty_page.slow_path }
+    x.report('empty_page fast') { empty_page.fast_path }
+    x.compare!
+  end
+end
+
+if root_page.slow_path == root_page.fast_path
+  Benchmark.ips do |x|
+    x.report('root_page slow') { root_page.slow_path }
+    x.report('root_page fast') { root_page.fast_path }
+    x.compare!
+  end
+end
+
+if nested_page.slow_path == nested_page.fast_path
+  Benchmark.ips do |x|
+    x.report('nested_page slow') { nested_page.slow_path }
+    x.report('nested_page fast') { nested_page.fast_path }
+    x.compare!
+  end
+end
+
+if slashed_page.slow_path == slashed_page.fast_path
+  Benchmark.ips do |x|
+    x.report('slashed_page slow') { slashed_page.slow_path }
+    x.report('slashed_page fast') { slashed_page.fast_path }
+    x.compare!
+  end
+end

benchmark/schwartzian_transform.rb

@@ -90,7 +90,7 @@ end
 Correctness.new(site_docs, "redirect_from".freeze).assert!
 Correctness.new(site_docs, "title".freeze).assert!
 
-def test_property(property, meta_key)
+def property(property, meta_key)
   Benchmark.ips do |x|
     x.config(time: 10, warmup: 5)
     x.report("sort_by_property_directly with #{property} property") do

benchmark/static-drop-vs-forwarded.rb

@@ -0,0 +1,83 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "forwardable"
+require "colorator"
+require "liquid"
+require "benchmark/ips"
+require "memory_profiler"
+
+# Set up (memory) profiler
+
+class Profiler
+  def self.run
+    yield new(ARGV[0] || 10_000)
+  end
+
+  def initialize(count)
+    @count = count.to_i
+  end
+
+  def report(label, color, &block)
+    prof_report = MemoryProfiler.report { @count.to_i.times(&block) }
+
+    allocated_memory  = prof_report.scale_bytes(prof_report.total_allocated_memsize)
+    allocated_objects = prof_report.total_allocated
+    retained_memory   = prof_report.scale_bytes(prof_report.total_retained_memsize)
+    retained_objects  = prof_report.total_retained
+
+    puts <<~MSG.send(color)
+      With #{label} calls
+
+      Total allocated: #{allocated_memory} (#{allocated_objects} objects)
+      Total retained:  #{retained_memory} (#{retained_objects} objects)
+    MSG
+  end
+end
+
+# Set up stage
+
+class Drop < Liquid::Drop
+  def initialize(obj)
+    @obj = obj
+  end
+end
+
+class ForwardDrop < Drop
+  extend Forwardable
+  def_delegators :@obj, :name
+end
+
+class StaticDrop < Drop
+  def name
+    @obj.name
+  end
+end
+
+class Document
+  def name
+    "lipsum"
+  end
+end
+
+# Set up actors
+
+document = Document.new
+alpha    = ForwardDrop.new(document)
+beta     = StaticDrop.new(document)
+count    = ARGV[0] || 10_000
+
+# Run profilers
+puts "\nMemory profiles for #{count} calls to invoke drop key:"
+Profiler.run do |x|
+  x.report("forwarded", :cyan) { alpha["name"] }
+  x.report("static", :green) { beta["name"] }
+end
+
+# Benchmark
+puts "\nBenchmarking the two scenarios..."
+Benchmark.ips do |x|
+  x.report("forwarded".cyan) { alpha["name"] }
+  x.report("static".green) { beta["name"] }
+  x.compare!
+end

docs/_config.yml

@@ -1,5 +1,5 @@
 ---
-version: 4.0.1
+version: 4.2.2
 name: Jekyll • Simple, blog-aware, static sites
 description: Transform your plain text into static websites and blogs
 url: https://jekyllrb.com
@@ -10,6 +10,7 @@ twitter:
 logo: "/img/logo-2x.png"
 google_analytics_id: UA-50755011-1
 google_site_verification: onQcXpAvtHBrUI5LlroHNE_FP0b2qvFyPq7VZw36iEY
+cloudinary_url: https://res.cloudinary.com/jekyll/image/upload/f_auto,q_auto,w_404
 collections:
   docs:
     permalink: "/:collection/:path/"
@@ -18,6 +19,7 @@ collections:
     permalink: "/news/:year/:month/:day/:title/"
     output: true
   tutorials:
+    permalink: "/:collection/:path/"
     output: true
 defaults:
 - scope:
@@ -30,6 +32,11 @@ defaults:
     type: posts
   values:
     layout: news_item
+- scope:
+    path: _tutorials
+    type: tutorials
+  values:
+    layout: tutorials
 - scope:
     path: ''
   values:
@@ -46,12 +53,12 @@ plugins:
 feed:
   categories:
   - release
+kramdown:
+  syntax_highlighter_opts:
+    default_lang: plaintext
 sass:
   style: compressed
 strict_front_matter: true
 exclude:
-- ".gitignore"
-- ".jekyll-cache"
-- CNAME
 - icomoon-selection.json
 - readme.md

docs/_data/config_options/build.yml

@@ -0,0 +1,123 @@
+- name: Regeneration
+  description: Enable auto-regeneration of the site when files are modified.
+  flag: "-w, --[no-]watch"
+
+
+- name: Configuration
+  description: >-
+    Specify config files instead of using <code>_config.yml</code> automatically.
+    Settings in later files override settings in earlier files.
+  flag: "--config FILE1[,FILE2,...]"
+
+
+- name: Plugins
+  description: >-
+    Specify plugin directories instead of using <code>_plugins/</code> automatically.
+  option: "plugins_dir: [ DIR1,... ]"
+  flag: "-p, --plugins DIR1[,DIR2,...]"
+
+
+- name: Layouts
+  description: >-
+    Specify layout directory instead of using <code>_layouts/</code> automatically.
+  option: "layouts_dir: DIR"
+  flag: --layouts DIR
+
+
+- name: Drafts
+  description: Process and render draft posts.
+  option: "show_drafts: BOOL"
+  flag: -D, --drafts
+
+
+- name: Environment
+  description: Use a specific environment value in the build.
+  flag: JEKYLL_ENV=production
+
+
+- name: Future
+  description: Publish posts or collection documents with a future date.
+  option: "future: BOOL"
+  flag: --future
+
+
+- name: Unpublished
+  description: Render posts that were marked as unpublished.
+  option: "unpublished: BOOL"
+  flag: --unpublished
+
+
+- name: LSI
+  description: >-
+    Produce an index for related posts. Requires the
+    <a href="https://jekyll.github.io/classifier-reborn/">classifier-reborn</a> plugin.
+  option: "lsi: BOOL"
+  flag: --lsi
+
+
+- name: Limit posts
+  description: Limit the number of posts to parse and publish.
+  option: "limit_posts: NUM"
+  flag: --limit_posts NUM
+
+
+- name: Force polling
+  description: Force watch to use polling.
+  option: "force_polling: BOOL"
+  flag: --force_polling
+
+
+- name: Verbose output
+  description: Print verbose output.
+  option: "verbose: BOOL"
+  flag: -V, --verbose
+
+
+- name: Silence output
+  description: Silence the normal output from Jekyll during a build.
+  option: "quiet: BOOL"
+  flag: -q, --quiet
+
+
+- name: Log level
+  description: Specify a log level among debug, info, warn, or error.
+  flag: JEKYLL_LOG_LEVEL=info
+
+
+- name: Incremental build
+  description: >-
+    Enable the experimental
+    <a href="/docs/configuration/incremental-regeneration/">incremental
+    build</a> feature. Incremental build only re-builds posts and pages that
+    have changed, resulting in significant performance improvements for large
+    sites, but may also break site generation in certain cases.
+  option: "incremental: BOOL"
+  flag: -I, --incremental
+
+
+- name: Disable bundle require
+  description: Disables the need to require gems in `:jekyll_plugins` Gemfile
+  flag: JEKYLL_NO_BUNDLER_REQUIRE=true
+
+
+- name: Liquid profiler
+  description: Generate a Liquid rendering profile to help you identify performance bottlenecks.
+  option: "profile: BOOL"
+  flag: --profile
+
+
+- name: Strict front matter
+  description: Cause a build to fail if there is a YAML syntax error in a page's front matter.
+  option: "strict_front_matter: BOOL"
+  flag: --strict_front_matter
+
+
+- name: Base URL
+  description: Serve the website from the given base URL.
+  option: "baseurl: URL"
+  flag: -b, --baseurl URL
+
+
+- name: Trace
+  description: Show the full backtrace when an error occurs.
+  flag: -t, --trace

docs/_data/config_options/global.yml

@@ -0,0 +1,77 @@
+- name: Site source
+  description: Change the directory where Jekyll will read files
+  option: "source: DIR"
+  flag: -s, --source DIR
+
+
+- name: Site destination
+  description: Change the directory where Jekyll will write files
+  option: "destination: DIR"
+  flag: -d, --destination DIR
+
+
+- name: Safe
+  description: >-
+    Disable <a href="/docs/plugins/">non-whitelisted plugins</a>, caching to disk, and ignore symbolic links.
+  option: "safe: BOOL"
+  flag: --safe
+
+
+- name: Disable disk cache
+  version-badge: 4.1.0
+  description: >-
+    Disable caching of content to disk in order to skip creating a <code>.jekyll-cache</code> or similar directory at
+    the source to avoid interference with virtual environments and third-party directory watchers. Caching to disk is
+    always disabled in <code>safe</code> mode.
+  option: "disable_disk_cache: BOOL"
+  flag: --disable-disk-cache
+
+
+- name: Ignore theme configuration
+  version-badge: 4.1.0
+  description: >-
+    Jekyll 4.0 started allowing themes to bundle a <code>_config.yml</code> to simplify theme-onboarding for new users.
+    In the unfortunate situation that importing a bundled theme configuration messes up the merged site-configuration,
+    the user can configure Jekyll to not import the theme-config entirely.
+  option: "ignore_theme_config: BOOL"
+
+
+- name: Exclude
+  description: >-
+    Exclude directories and/or files from the conversion. These exclusions are relative to the site's source directory
+    and cannot be outside the source directory.
+  option: "exclude: [DIR, FILE, ...]"
+
+
+- name: Include
+  description: >-
+    Force inclusion of directories and/or files in the conversion. <code>.htaccess</code> is a good example since
+    dotfiles are excluded by default.
+  option: "include: [DIR, FILE, ...]"
+
+
+- name: Keep files
+  description: >-
+    When clobbering the site destination, keep the selected files. Useful for files that are not generated by jekyll;
+    e.g. files or assets that are generated by your build tool. The paths are relative to the <code>destination</code>.
+  option: "keep_files: [DIR, FILE, ...]"
+
+
+- name: Time zone
+  description: >-
+    Set the time zone for site generation. This sets the <code>TZ</code> environment variable, which Ruby uses to handle
+    time and date creation and manipulation. Any entry from the
+    <a href="https://en.wikipedia.org/wiki/Tz_database">IANA Time Zone Database</a>
+    is valid, e.g. <code>America/New_York</code>. A list of all available values can be found
+    <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones"> here</a>.
+    When serving on a local machine, the default time zone is set by your operating system. But when served on a remote
+    host/server, the default time zone depends on the server's setting or location.
+  option: "timezone: TIMEZONE"
+
+
+- name: Encoding
+  description: >-
+    Set the encoding of files by name (only available for Ruby 1.9 or later). The default value is <code>utf-8</code>
+    starting in 2.0.0, and <code>nil</code> before 2.0.0, which will yield the Ruby default of <code>ASCII-8BIT</code>.
+    Available encodings can be shown by the command <code>ruby -e 'puts Encoding::list.join("\n")'</code>.
+  option: "encoding: ENCODING"

docs/_data/config_options/serve.yml

@@ -0,0 +1,71 @@
+- name: Local server port
+  description: Listen on the given port. The default is `4000`.
+  option: "port: PORT"
+  flag: "-P, --port PORT"
+
+
+- name: Local server hostname
+  description: Listen at the given hostname. The default is `localhost`.
+  option: "host: HOSTNAME"
+  flag: "-H, --host HOSTNAME"
+
+
+- name: Live reload
+  description: Reload a page automatically on the browser when its content is edited.
+  option: "livereload: BOOL"
+  flag: "-l, --livereload"
+
+
+- name: Live reload ignore
+  description: File glob patterns for LiveReload to ignore.
+  option: "livereload_ignore: [ GLOB1,... ]"
+  flag: "--livereload-ignore GLOB1[,GLOB2,...]"
+
+
+- name: Live reload min/max delay
+  description: Minimum/Maximum delay before automatically reloading page.
+  options:
+    - "livereload_min_delay: SECONDS"
+    - "livereload_max_delay: SECONDS"
+  flags:
+    - "--livereload-min-delay SECONDS"
+    - "--livereload-max-delay SECONDS"
+
+
+- name: Live reload port
+  description: Port for LiveReload to listen on.
+  flag: "--livereload-port PORT"
+
+
+- name: Open URL
+  description: Open the site's URL in the browser.
+  option: "open_url: BOOL"
+  flag: "-o, --open-url"
+
+
+- name: Detach
+  description: Detach the server from the terminal.
+  option: "detach: BOOL"
+  flag: "-B, --detach"
+
+
+- name: Skips the initial site build
+  description: Skips the initial site build which occurs before the server is started.
+  option: "skip_initial_build: BOOL"
+  flag: "--skip-initial-build"
+
+
+- name: Show directory listing
+  description: Show a directory listing instead of loading your index file.
+  option: "show_dir_listing: BOOL"
+  flag: "--show-dir-listing"
+
+
+- name: X.509 (SSL) private key
+  description: "SSL Private Key, stored or symlinked in the site source."
+  flag: "--ssl-key"
+
+
+- name: X.509 (SSL) certificate
+  description: "SSL Public certificate, stored or symlinked in the site source."
+  flag: "--ssl-cert"

docs/_data/docs_nav.yml

@@ -1,14 +1,15 @@
 - title: Getting Started
   docs:
     - link: /docs/
-    - link: /docs/ruby-101/
     - link: /docs/installation/
+    - link: /docs/ruby-101/
     - link: /docs/community/
     - link: /docs/step-by-step/01-setup/
 - title: Build
   docs:
     - link: /docs/usage/
     - link: /docs/configuration/
+    - link: /docs/rendering-process/
 - title: Content
   docs:
     - link: /docs/pages/

docs/_data/jekyll_filters.yml

@@ -18,8 +18,8 @@
 #
 - name: Relative URL
   description: >-
-    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.
+    Prepend <code>baseurl</code> config value to the input to convert a URL path into a relative URL. 
+    This is recommended for a site that is hosted on a subpath of a domain.
   examples:
     - input: '{{ "/assets/style.css" | relative_url }}'
       output: '/my-baseurl/assets/style.css'
@@ -27,7 +27,8 @@
 #
 
 - name: Absolute URL
-  description: Prepend the <code>url</code> and <code>baseurl</code> value to the input.
+  description: >-
+    Prepend <code>url</code> and <code>baseurl</code> values to the input to convert a URL path to an absolute URL.
   examples:
     - input: '{{ "/assets/style.css" | absolute_url }}'
       output: 'http://example.com/my-baseurl/assets/style.css'
@@ -111,6 +112,40 @@
 
 #
 
+- name: Find
+  description: >-
+    Return <strong>the first object</strong> in an array for which the queried
+    attribute has the given value or return <code>nil</code> if no item in
+    the array satisfies the given criteria.
+  version_badge: 4.1.0
+  examples:
+    - input: '{{ site.members | find: "graduation_year", "2014" }}'
+      output:
+
+#
+
+- name: Find Expression
+  description: >-
+    Return <strong>the first object</strong> in an array for which the given
+    expression evaluates to true or return <code>nil</code> if no item in
+    the array satisfies the evaluated expression.
+  version_badge: 4.1.0
+  examples:
+    - input: |-
+        {{ site.members | find_exp:"item",
+        "item.graduation_year == 2014" }}
+      output:
+    - input: |-
+        {{ site.members | find_exp:"item",
+        "item.graduation_year < 2014" }}
+      output:
+    - input: |-
+        {{ site.members | find_exp:"item",
+        "item.projects contains 'foo'" }}
+      output:
+
+#
+
 - name: Group By
   description: Group an array's items by a given property.
   examples:
@@ -166,10 +201,25 @@
 #
 
 - name: Number of Words
-  description: Count the number of words in some text.
+  description: >-
+    Count the number of words in some text.<br/>
+    From <span class="version-badge">v4.1.0</span>, this filter takes an optional
+    argument to control the handling of Chinese-Japanese-Korean (CJK) characters
+    in the <code>input</code> string.<br/>
+    Passing <code>'cjk'</code> as the argument will count every CJK character
+    detected as one word irrespective of being separated by whitespace.<br/>
+    Passing <code>'auto'</code> (auto-detect) works similar to <code>'cjk'</code>
+    but is more performant if the filter is used on a variable string that may
+    or may not contain CJK chars.
   examples:
-    - input: '{{ page.content | number_of_words }}'
-      output: 1337
+    - input: '{{ "Hello world!" | number_of_words }}'
+      output: 2
+    - input: '{{ "你好hello世界world" | number_of_words }}'
+      output: 1
+    - input: '{{ "你好hello世界world" | number_of_words: "cjk" }}'
+      output: 6
+    - input: '{{ "你好hello世界world" | number_of_words: "auto" }}'
+      output: 6
 
 #
 

docs/_data/jekyll_variables.yml

@@ -1,7 +1,7 @@
 # Variables provided by Jekyll core
 #
 #   name:           : name of the variable
-#   description:    : content returned by the varialble
+#   description:    : content returned by the variable
 
 global:
   - name: site
@@ -51,10 +51,10 @@ site:
       <code>name</code>, <code>basename</code> and <code>extname</code>.
   - name: site.html_pages
     description: >-
-      A subset of `site.pages` listing those which end in `.html`.
+      A subset of <code>site.pages</code> listing those which end in <code>.html</code>.
   - name: site.html_files
     description: >-
-      A subset of `site.static_files` listing those which end in `.html`.
+      A subset of <code>site.static_files</code> listing those which end in <code>.html</code>.
   - name: site.collections
     description: >-
       A list of all the collections (including posts).
@@ -76,7 +76,7 @@ site:
       Contains the url of your site as it is configured in the <code>_config.yml</code>.
       For example, if you have <code>url: http://mysite.com</code> in your configuration file,
       then it will be accessible in Liquid as <code>site.url</code>. For the development
-      environment there is <a href="/news/#3-siteurl-is-set-by-the-development-server">an
+      environment there is <a href="/news/2016/10/06/jekyll-3-3-is-here/#3-siteurl-is-set-by-the-development-server">an
       exception</a>, if you are running <code>jekyll serve</code> in a development environment
       <code>site.url</code> will be set to the value of <code>host</code>, <code>port</code>,
       and SSL-related options. This defaults to <code>url: http://localhost:4000</code>.

docs/_data/jekyllconf-talks.yml

@@ -165,3 +165,45 @@
   youtube_id: nq1AUB72GCQ
   topic: Overcoming challenges in using Jekyll for documentation projects
   year: 2016
+
+- speaker: Pieter Roozen
+  twitter_handle: Pieter_Roozen
+  youtube_id: moQP0SqEPsw
+  topic: Jekyll As An API Endpoint
+  year: 2019
+
+- speaker: Chen Hui Jing
+  twitter_handle: hj_chen
+  youtube_id: CERXESTZ5w4
+  topic: Why I love Jekyll Data Files
+  year: 2019
+
+- speaker: Chris Ferdinandi
+  twitter_handle: ChrisFerdinandi
+  youtube_id: vR1aI_kQ4-A
+  topic: The Lean Web
+  year: 2019
+  
+- speaker: Catherine Roebuck
+  twitter_handle: 
+  youtube_id: zTAP1m1BaDM
+  topic: Jekyll For City Government
+  year: 2019
+  
+- speaker: Joost van der Schee
+  twitter_handle: jhvanderschee
+  youtube_id: ztJJ1GSlYgI
+  topic: "Jekyll Codex - Jekyll for front-end developers"
+  year: 2019
+  
+- speaker: Matthew Loberg
+  twitter_handle: mloberg
+  youtube_id: 6eiAjAtSGqw
+  topic: Leverage AWS S3 And CloudFront To Deploy Blazing Fast Jekyll Sites
+  year: 2019
+  
+- speaker: George Phillips
+  twitter_handle: gphillips_nz
+  youtube_id: nEvdOwFJBVc
+  topic: Structuring Jekyll Sites For Enterprise Design Systems
+  year: 2019

docs/_data/ruby.yml

@@ -1,3 +1,3 @@
-min_version: 2.4.0
-current_version: 2.6.3
-current_version_output: ruby 2.6.3p62 (2019-04-16 revision 67580)
+min_version: 2.5.0
+current_version: 3.1.1
+current_version_output: ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236)

docs/_data/showcase.yml

@@ -1,241 +1,322 @@
 - name: Tom Preston Werner Blog
   url: http://tom.preston-werner.com/
+  image: tom-preston-werner.png
   categories:
     - personal
     - blog
-- name: GitHub On Demand Training
-  url: https://services.github.com/on-demand/
-  categories:
-    - software
-    - knowledgebase
-- name: Vesterheim Norwegian-American Museum
-  url: http://vesterheim.org/
-  categories:
-    - marketing-site
-- name: KOTN
-  url: https://kotn.com/
-  categories:
-   - marketing-site
-- name: MvvmCross
-  url: https://www.mvvmcross.com/
-  categories:
-    - software
-    - marketing-site
-- name: Vidgrid
-  url: https://www.vidgrid.com/
-  categories:
-    - software
-    - marketing-site
-- name: Bitcoin
-  url: https://bitcoin.org/en/
-  categories:
-    - software
-    - marketing-site
-- name: Mapwize
-  url: https://www.mapwize.io/
-  categories:
-    - software
-    - marketing-site
-- name: Auth0 Blog
-  url: https://auth0.com/blog/
-  categories:
-    - software
-    - blog
-- name: AWS Amplify
-  url: https://aws-amplify.github.io/
-  categories:
-    - open-source
-    - marketing-site
-- name: Yeoman
-  url: http://yeoman.io/
-  categories:
-    - open-source
-    - marketing-site
-- name: Ionic Framwork
-  url: https://ionicframework.com/
-  categories:
-    - software
-    - marketing-site
-- name: Release Management Blog
-  url: https://release.mozilla.org/
-  categories:
-    - software
-    - blog
-- name: Freedom of Information Act
-  url: https://www.foia.gov/
-  categories:
-    - government
-- name: Art & About Sydney
-  url: https://www.artandabout.com.au/
-  categories:
-    - government
-- name: Passbolt Help
-  url: https://help.passbolt.com/
-  categories:
-    - knowledgebase
-- name: We are COLLINS
-  url: https://www.wearecollins.com/
-  categories:
-    - agency
-- name: Light Burn
-  url: https://lightburn.co/
-  categories:
-    - agency
-- name: italia.it
-  url: https://developers.italia.it/
-  categories:
-    - community
-- name: Sydney New Years Eve
-  url: https://www.sydneynewyearseve.com/
-  categories:
-    - government
-- name: Login.gov
-  url: https://login.gov/
-  categories:
-    - government
-- name: plainlanguage.gov
-  url: https://plainlanguage.gov/
-  categories:
-    - government
-- name: U.S. Web Design Standards
-  url: https://standards.usa.gov/
-  categories:
-    - government
-- name: Grantmaker Search
-  url: https://www.grantmakers.io/
-  categories:
-    - marketing-site
-- name: Rehan Butt
-  url: http://rehanbutt.com/
-  categories:
-    - personal
-    - portfolio
-- name: The Markdown Guide
-  url: https://www.markdownguide.org/
-  categories:
-    - knowledgebase
-- name: PROBOT
-  url: https://probot.github.io/
-  categories:
-    - documentation
-- name: Matt Grey
-  url: https://himatt.com/
-  categories:
-    - personal
-    - portfolio
-- name: frame.ai
-  url: https://frame.ai/
-  categories:
-    - software
-    - marketing-site
-- name: AdHawk
-  url: https://www.tryadhawk.com/
-  categories:
-    - agency
-- name: City of Boston Budget
-  url: https://budget.boston.gov/
-  categories:
-    - government
-- name: Lattice
-  url: https://latticehq.com/
-  categories:
-    - software
-    - marketing-site
-- name: MailTape
-  url: https://www.mailta.pe/
-  categories:
-    - other
-- name: Digital Democracy
-  url: http://www.digital-democracy.org/
-  categories:
-    - other
-- name: HTML Reference
-  url: http://htmlreference.io/
-  categories:
-    - documentation
-- name: CSS Reference
-  url: http://cssreference.io/
-  categories:
-    - documentation
-- name: Chain
-  url: https://chain.com/
-  categories:
-    - marketing-site
-- name: Boxy Suite
-  url: https://www.boxysuite.com/
-  categories:
-    - marketing-site
-    - software
-- name: Pattern Lab
-  url: http://patternlab.io/
-  categories:
-    - documentation
-- name: IBM MobileFirst Foundation
-  url: https://mobilefirstplatform.ibmcloud.com/
-  categories:
-    - documentation
-- name: 18F
-  url: https://18f.gsa.gov/
-  categories:
-    - agency
-    - government
-- name: Mapbox
-  url: https://mapbox.com/
-  categories:
-    - marketing-site
-- name: Development Seed
-  url: https://developmentseed.org/
-  categories:
-    - agency
-- name: Isomer - Singapore Government Static Websites
-  url: https://isomer.gov.sg/
-  categories:
-    - government
+
+# - name: White House Social and Behavioral Sciences Team
+#   url: https://sbst.gov/
+#   image: sbst.png
+#   categories:
+#     - government
+
 - name: SiteLeaf
   url: https://siteleaf.com
+  image: siteleaf.png
   categories:
     - software
     - marketing-site
+
 - name: CloudCannon
   url: https://cloudcannon.com/
+  image: cloudcannon.png
   categories:
     - software
     - marketing-site
-- name: Ruby on Rails
-  url: http://rubyonrails.org/
+
+- name: Vesterheim Norwegian-American Museum
+  url: http://vesterheim.org/
+  image: vesterheim.png
   categories:
     - marketing-site
+
+- name: KOTN
+  url: https://kotn.com/
+  image: kotn.png
+  categories:
+   - marketing-site
+
+- name: MvvmCross
+  url: https://www.mvvmcross.com/
+  image: mvvm.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Vidgrid
+  url: https://www.vidgrid.com/
+  image: vidgrid.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Bitcoin
+  url: https://bitcoin.org/en/
+  image: bitcoin.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Mapwize
+  url: https://www.mapwize.io/
+  image: mapwize.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Auth0 Blog
+  url: https://auth0.com/blog/
+  image: auth0-blog.png
+  categories:
+    - software
+    - blog
+
+- name: Freedom of Information Act
+  url: https://www.foia.gov/
+  image: foia-gov.png
+  categories:
+    - government
+
+- name: "Art & About Sydney"
+  url: https://www.artandabout.com.au/
+  image: art-sydney.png
+  categories:
+    - government
+
+- name: Passbolt Help
+  url: https://help.passbolt.com/
+  image: passbolt-help.png
+  categories:
+    - knowledgebase
+
+- name: We are COLLINS
+  url: https://www.wearecollins.com/
+  image: collins.png
+  categories:
+    - agency
+
+- name: Lightburn
+  url: https://lightburn.co/
+  image: lightburn.png
+  categories:
+    - agency
+
+- name: italia.it
+  url: https://developers.italia.it/
+  image: italia-it.png
+  categories:
+    - community
+
+- name: Sydney New Years Eve
+  url: https://www.sydneynewyearseve.com/
+  image: nsw.png
+  categories:
+    - government
+
+- name: Login.gov
+  url: https://login.gov/
+  image: login-gov.png
+  categories:
+    - government
+
+- name: plainlanguage.gov
+  url: https://plainlanguage.gov/
+  image: plainlanguage-gov.png
+  categories:
+    - government
+
+- name: U.S. Web Design Standards
+  url: https://standards.usa.gov/
+  image: uswds.png
+  categories:
+    - government
+
+- name: Grantmaker Search
+  url: https://www.grantmakers.io/
+  image: grantmakers.png
+  categories:
+    - marketing-site
+
+- name: Rehan Butt
+  url: http://rehanbutt.com/
+  image: rehn.png
+  categories:
+    - personal
+    - portfolio
+
+- name: The Markdown Guide
+  url: https://www.markdownguide.org/
+  image: markdown-guide.png
+  categories:
+    - knowledgebase
+
+- name: Probot
+  url: https://probot.github.io/
+  image: probot.png
+  categories:
     - documentation
-- name: White House Social and Behavioral Sciences Team
-  url: https://sbst.gov/
+
+- name: Matt Grey
+  url: https://himatt.com/
+  image: matt-grey.png
   categories:
-    - government
-- name: UN World Statistics
-  url: https://worldstatisticsday.org
-  categories:
-    - government
-- name: Sketch App
-  url: https://sketchapp.com/
+    - personal
+    - portfolio
+
+- name: Lattice
+  url: https://latticehq.com/
+  image: lattice.png
   categories:
     - software
     - marketing-site
-- name: Netflix Devices
-  url: https://devices.netflix.com/en/
+
+- name: MailTape
+  url: https://www.mailta.pe/
+  image: mailtape.png
+  categories:
+    - other
+
+- name: Digital Democracy
+  url: http://www.digital-democracy.org/
+  image: digital-democracy.png
+  categories:
+    - other
+
+- name: HTML Reference
+  url: http://htmlreference.io/
+  image: htmlreference.png
+  categories:
+    - documentation
+
+- name: CSS Reference
+  url: http://cssreference.io/
+  image: cssreference.png
+  categories:
+    - documentation
+
+- name: Chain
+  url: https://chain.com/
+  image: chain.png
   categories:
     - marketing-site
+
+- name: IBM MobileFirst Foundation
+  url: https://mobilefirstplatform.ibmcloud.com/
+  image: ibm-mobile-foundation.png
+  categories:
+    - documentation
+
+- name: "18F"
+  url: https://18f.gsa.gov/
+  image: 18f.png
+  categories:
+    - agency
+    - government
+
+- name: Development Seed
+  url: https://developmentseed.org/
+  image: development-seed.png
+  categories:
+    - agency
+
+- name: Isomer - Singapore Government Static Websites
+  url: https://isomer.gov.sg/
+  image: isomer.png
+  categories:
+    - government
+
+- name: French Government Digital Services
+  url: https://beta.gouv.fr/
+  image: beta-gouv-fr.png
+  categories:
+    - government
+
+- name: Paris Call for Trust and Security in Cyberspace
+  url: https://pariscall.international/
+  image: appel-de-paris.png
+  categories:
+    - government
+
+- name: GitHub On Demand Training
+  url: https://services.github.com/on-demand/
+  image: github-learning-lab.png
+  categories:
+    - software
+    - knowledgebase
+
 - name: TwitchCon
   url: https://www.twitchcon.com/
+  image: twitchcon.png
   categories:
     - marketing-site
     - conference
+
+- name: UN World Statistics
+  url: https://worldstatisticsday.org
+  image: world-statistics-day.png
+  categories:
+    - government
+
+- name: Netflix Devices
+  url: https://devices.netflix.com/en/
+  image: netflix.png
+  categories:
+    - marketing-site
+
 - name: Twitch Developer Documentation
   url: https://dev.twitch.tv/
+  image: twitch-developers.png
   categories:
     - marketing-site
     - documentation
+
+- name: Yeoman
+  url: http://yeoman.io/
+  image: yeoman.png
+  categories:
+    - open-source
+    - marketing-site
+
+- name: Release Management Blog
+  url: https://release.mozilla.org/
+  image: mozilla-release-blog.png
+  categories:
+    - software
+    - blog
+
+- name: frame.ai
+  url: https://frame.ai/
+  image: frame-ai.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Ionic Framework
+  url: https://ionicframework.com/
+  image: ionic-framework.png
+  categories:
+    - software
+    - marketing-site
+
 - name: Spotify for Developers
   url: https://developer.spotify.com
+  image: spotify-developers.png
   categories:
     - marketing-site
     - documentation
     - software
+
+- name: Sketch
+  url: https://sketch.com/
+  image: sketch.png
+  categories:
+    - software
+    - marketing-site
+
+- name: Ruby on Rails
+  url: http://rubyonrails.org/
+  image: ruby-on-rails.png
+  categories:
+    - marketing-site
+    - documentation

docs/_data/tutorials.yml

@@ -7,6 +7,7 @@
   - custom-404-page
   - convert-site-to-jekyll
   - using-jekyll-with-bundler
+  - csv-to-table
 
 #- title: Another section
 #  tutorials:

docs/_docs/assets.md

@@ -28,7 +28,7 @@ will process it and put it in your site's destination folder under
   <h5>Jekyll processes all Liquid filters and tags in asset files</h5>
   <p>If you are using <a href="https://mustache.github.io">Mustache</a>
      or another JavaScript templating language that conflicts with
-     the <a href="/docs/templates/">Liquid template syntax</a>, you
+     the <a href="{{ '/docs/templates/' | relative_url }}">Liquid template syntax</a>, you
      will need to place <code>{&#37; raw &#37;}</code> and
      <code>{&#37; endraw &#37;}</code> tags around your code.</p>
 </div>
@@ -79,6 +79,7 @@ sass:
 These are passed to Sass, so any output style options Sass supports are valid
 here, too.
 
+For more information on Sass configuration options, see the [Sass configuration]({{ '/docs/configuration/sass/' | relative_url }}) docs.
 
 ## Coffeescript
 

docs/_docs/code_of_conduct.md

@@ -1,7 +1,7 @@
 ---
 title: Code of Conduct
 permalink: "/docs/code_of_conduct/"
-note: This file is autogenerated. Edit /CODE_OF_CONDUCT.markdown instead.
+note: This file is autogenerated. Edit /.github/CODE_OF_CONDUCT.markdown instead.
 redirect_from: "/conduct/index.html"
 editable: false
 ---

docs/_docs/collections.md

@@ -16,7 +16,8 @@ collections:
   - staff_members
 ```
 
-You can optionally specify metadata for your collection in the configuration:
+In this case `collections` is defined as a sequence (i.e., array) with no additional metadata defined for each collection.
+You can optionally specify metadata for your collection by defining `collections` as a mapping (i.e., hashmap) instead of sequence, and then defining additional fields in it:
 
 ```yaml
 collections:
@@ -24,6 +25,12 @@ collections:
     people: true
 ```
 
+{: .note .info}
+When defining a collection as a sequence, its pages will not be rendered by
+default. To enable this, <code>output: true</code> must be specified on the
+collection, which requires defining the collection as a mapping. For more
+information, see the section <a href="#output">Output</a>.
+
 <div class="note">
   <h5>Gather your collections {%- include docs_version_badge.html version="3.7.0" -%}</h5>
 
@@ -44,10 +51,13 @@ collections:
 Create a corresponding folder (e.g. `<source>/_staff_members`) and add
 documents. Front matter is processed if the front matter exists, and everything
 after the front matter is pushed into the document's `content` attribute. If no front
-matter is provided, Jekyll will consider it to be a [static file](/docs/static-files/)
-and copy it to the destination (e.g. `_site`) without processing. If front matter
-is provided, Jekyll will process the file in your collection but will not write to disk
-unless `output: true` is set in the collection's metadata.
+matter is provided, Jekyll will consider it to be a [static file]({{ '/docs/static-files/' | relative_url }})
+and the contents will not undergo further processing. If front matter is provided,
+Jekyll will process the file contents into the expected output.
+
+Regardless of whether front matter exists or not, Jekyll will write to the destination
+directory (e.g. `_site`) only if `output: true` has been set in the collection's
+metadata.
 
 For example here's how you would add a staff member to the collection set above.
 The filename is `./_staff_members/jane.md` with the following content:
@@ -60,6 +70,12 @@ position: Developer
 Jane has worked on Jekyll for the past *five years*.
 ```
 
+<em>
+  Do note that in spite of being considered as a collection internally, the above
+  doesn't apply to [posts](/docs/posts/). Posts with a valid filename format will be
+  marked for processing even if they do not contain front matter.
+</em>
+
 <div class="note info">
   <h5>Be sure to name your directories correctly</h5>
   <p>
@@ -83,7 +99,6 @@ using the `content` variable:
 ```
 {% endraw %}
 
-
 If you'd like Jekyll to create a rendered page for each document in your
 collection, you can set the `output` key to `true` in your collection
 metadata in `_config.yml`:
@@ -111,12 +126,15 @@ You can link to the generated page using the `url` attribute:
 
 ## Permalinks
 
-There are special [permalink variables for collections](/docs/permalinks/) to
+There are special [permalink variables for collections]({{ '/docs/permalinks/#collections' | relative_url }}) to
 help you control the output url for the entire collection.
 
-## Custom Sorting of Documents
+## Custom Sorting of Documents {%- include docs_version_badge.html version="4.0" -%}
+{: #custom-sorting-of-documents}
 
-By default, documents in a collection are sorted by their paths. But you can control this sorting via the collection's metadata.
+By default, two documents in a collection are sorted by their `date` attribute when both of them have the `date` key in their front matter. However, if either or both documents do not have the `date` key in their front matter, they are sorted by their respective paths.
+
+You can control this sorting via the collection's metadata.
 
 ### Sort By Front Matter Key
 
@@ -270,7 +288,6 @@ you specified in your `_config.yml` (if present) and the following information:
   </p>
 </div>
 
-
 ### Documents
 
 In addition to any front matter provided in the document's corresponding

docs/_docs/community/community.md

@@ -8,30 +8,36 @@ redirect_from: "/help/index.html"
 
 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 contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
 
-Read the full [code of conduct](/docs/conduct/)
+Read the full [code of conduct]({{ '/docs/conduct/' | relative_url }})
+
+## Reporting Security Vulnerabilities
+
+Find something in our codebase that could be exploited by malicious elements?
+
+Consult our [Security Policy]({{ '/docs/security/' | relative_url }}) to see if a product version is considered *outdated* and how to report
+the situation responsibly.
 
 ## Where to get support
 
 If you're looking for support for Jekyll, there are a lot of options:
 
-* Read the [Jekyll Documentation](https://jekyllrb.com/docs/)
+* Read the [Jekyll Documentation]({{ '/docs/' | relative_url }})
 * If you have a question about using Jekyll, start a discussion on the [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)
+* Chat with Jekyllers — Join our [Gitter channel](https://gitter.im/jekyll/jekyll) or our IRC channel #jekyll on [Libera](irc://irc.libera.chat/#jekyll).
 
-There are a bunch of helpful community members on these services that should be willing to point you in the right direction.
+There are a bunch of helpful community members on these services who are willing to point you in the right direction.
 
 **Reminder: Jekyll's issue tracker is not a support forum.**
 
 ## Ways to contribute
 
-* [How to Contribute](/docs/contributing/)
-* [How to file a bug](/docs/community/bug/)
-* [Guide for maintaining Jekyll](/docs/maintaining/)
-
+* [How to Contribute]({{ '/docs/contributing/' | relative_url }})
+* [How to file a bug]({{ '/docs/community/bug/' | relative_url }})
+* [Guide for maintaining Jekyll]({{ '/docs/maintaining/' | relative_url }})
 
 ## Jekyllconf
 
-[Watch videos](/jekyllconf/) from members of the Jekyll community speak about interesting use cases, tricks they’ve learned or meta Jekyll topics.
+[Watch videos]({{ '/jekyllconf/' | relative_url }}) from members of the Jekyll community speak about interesting use cases, tricks they’ve learned or meta Jekyll topics.
 
 ## Jekyll on Twitter
 

docs/_docs/configuration.md

@@ -8,11 +8,12 @@ options can either be specified in a `_config.yml` or `_config.toml` file placed
 in your site’s root directory, or can be specified as flags for the `jekyll`
 executable in the terminal.
 
-* [Configuration Options](/docs/configuration/options/)
-* [Default Configuration](/docs/configuration/default/)
-* [Front Matter Defaults](/docs/configuration/front-matter-defaults/)
-* [Environments](/docs/configuration/environments/)
-* [Markdown Options](/docs/configuration/markdown/)
-* [Liquid Options](/docs/configuration/liquid/)
-* [Webrick Options](/docs/configuration/webrick/)
-* [Incremental Regeneration](/docs/configuration/incremental-regeneration/)
+* [Configuration Options]({{ '/docs/configuration/options/' | relative_url }})
+* [Default Configuration]({{ '/docs/configuration/default/' | relative_url }})
+* [Front Matter Defaults]({{ '/docs/configuration/front-matter-defaults/' | relative_url }})
+* [Environments]({{ '/docs/configuration/environments/' | relative_url }})
+* [Markdown Options]({{ '/docs/configuration/markdown/' | relative_url }})
+* [Liquid Options]({{ '/docs/configuration/liquid/' | relative_url }})
+* [Sass/SCSS Options]({{ '/docs/configuration/sass/' | relative_url }})
+* [Webrick Options]({{ '/docs/configuration/webrick/' | relative_url }})
+* [Incremental Regeneration]({{ '/docs/configuration/incremental-regeneration/' | relative_url }})

docs/_docs/configuration/default.md

@@ -7,12 +7,19 @@ Jekyll runs with the following configuration options by default. Alternative
 settings for these options can be explicitly specified in the configuration
 file or on the command-line.
 
+<div class="note info">
+  <h5>Be aware of directory paths</h5>
+  <p>
+    In general, make directory path values in configuration keys like <code>plugins_dir</code> relative to the current working directory, not the site source. The <code>sass</code> configuration key is an exception, where values must be relative to the site source.
+  </p>
+</div>
+
 ```yaml
 # Where things are
 source              : .
 destination         : ./_site
 collections_dir     : .
-plugins_dir         : _plugins
+plugins_dir         : _plugins # takes an array of strings and loads plugins in that order
 layouts_dir         : _layouts
 data_dir            : _data
 includes_dir        : _includes
@@ -70,16 +77,10 @@ liquid:
   strict_variables  : false
 
 # Markdown Processors
-rdiscount:
-  extensions        : []
-
-redcarpet:
-  extensions        : []
-
 kramdown:
   auto_ids          : true
   entity_output     : as_char
-  toc_levels        : 1..6
+  toc_levels        : [1, 2, 3, 4, 5, 6]
   smart_quotes      : lsquo,rsquo,ldquo,rdquo
   input             : GFM
   hard_wrap         : false

docs/_docs/configuration/environments.md

@@ -42,8 +42,8 @@ environment but not include it in production environments.
 By specifying the option in the build command, you avoid having to change
 values in your configuration files when moving from one environment to another.
 
-<div class="note info">
-  <p>
-    To switch part of your config settings depending on the environment, use the <a href="/docs/configuration/options/#build-command-options">build command option</a>, for example <code>--config _config.yml,_config_development.yml</code>. Settings in later files override settings in earlier files.
-  </p>
-</div>
+{: .note}
+To switch part of your config settings depending on the environment, use the
+<a href="{{ '/docs/configuration/options/#build-command-options' | relative_url }}">build command option</a>,
+for example <code>--config _config.yml,_config_development.yml</code>. Settings
+in later files override settings in earlier files.

docs/_docs/configuration/front-matter-defaults.md

@@ -30,7 +30,7 @@ defaults:
     during automatic regeneration are not loaded until the next execution.
   </p>
   <p>
-    Note <a href="/docs/datafiles">Data Files</a> are included and reloaded during automatic regeneration.
+    Note <a href="{{ '/docs/datafiles/' | relative_url }}">Data Files</a> are included and reloaded during automatic regeneration.
   </p>
 </div>
 
@@ -68,7 +68,9 @@ defaults:
       author: "Mr. Hyde"
 ```
 
-With these defaults, all pages would use the `my-site` layout. Any html files that exist in the `projects/` folder will use the `project` layout, if it exists. Those files will also have the `page.author` [liquid variable](/docs/variables/) set to `Mr. Hyde`.
+With these defaults, all pages would use the `my-site` layout. Any html files that exist in the `projects/`
+folder will use the `project` layout, if it exists. Those files will also have the `page.author`
+[liquid variable]({{ '/docs/variables/' | relative_url }}) set to `Mr. Hyde`.
 
 ```yaml
 collections:
@@ -85,7 +87,7 @@ defaults:
 ```
 
 In this example, the `layout` is set to `default` inside the
-[collection](/docs/collections/) with the name `my_collection`.
+[collection]({{ '/docs/collections/' | relative_url }}) with the name `my_collection`.
 
 ### Glob patterns in Front Matter defaults
 
@@ -114,7 +116,6 @@ defaults:
   </p>
 </div>
 
-
 ### Precedence
 
 Jekyll will apply all of the configuration settings you specify in the `defaults` section of your `_config.yml` file. You can choose to override settings from other scope/values pair by specifying a more specific path for the scope.

docs/_docs/configuration/liquid.md

@@ -6,13 +6,33 @@ Liquid's response to errors can be configured by setting `error_mode`. The
 options are
 
 - `lax` --- Ignore all errors.
-- `warn` --- Output a warning on the console for each error.
+- `warn` --- Output a warning on the console for each error. (default)
 - `strict` --- Output an error message and stop the build.
 
+Within _config.yml, the default configuration is as follows:
+
+```yaml
+liquid:
+  error_mode: warn
+```
+
+The above example depicts the "warn" value, which is already set by default- `error_mode: warn`. This results in any issues being called out during the build process however will continue to build if possible.
+
 You can also configure Liquid's renderer to catch non-assigned variables and
 non-existing filters by setting `strict_variables` and / or `strict_filters`
 to `true` respectively. {% include docs_version_badge.html version="3.8.0" %}
 
 Do note that while `error_mode` configures Liquid's parser, the `strict_variables`
-and `strict_filters` options configure Liquid's renderer and are consequently,
-mutually exclusive.
+and `strict_filters` options configure Liquid's renderer and are consequently
+orthogonal.
+
+An example of setting these variables within _config.yml is as follows:
+
+```yaml
+liquid:
+  error_mode: strict
+  strict_variables: true
+  strict_filters: true
+```
+
+Configuring as described above will stop your build/serve from happening and call out the offending error and halt. This is helpful when desiring to catch liquid-related issues by stopping the build or serve process and allowing you to deal with any issues.

docs/_docs/configuration/markdown.md

@@ -5,102 +5,69 @@ permalink: "/docs/configuration/markdown/"
 The various Markdown renderers supported by Jekyll sometimes have extra options
 available.
 
-### Kramdown
+## Kramdown
 
-Kramdown is the default Markdown renderer for Jekyll. Below is a list of the
-currently supported options:
+Kramdown is the default Markdown renderer for Jekyll, and often works well with no additional configuration. However, it does support many configuration options.
 
-* **auto_id_prefix** - Prefix used for automatically generated header IDs
-* **auto_id_stripping** - Strip all formatting from header text for automatic ID generation
-* **auto_ids** - Use automatic header ID generation
-* **coderay_bold_every** - Defines how often a line number should be made bold
-* **coderay_css** - Defines how the highlighted code gets styled
-* **coderay_default_lang** - Sets the default language for highlighting code blocks
-* **coderay_line_number_start** - The start value for the line numbers
-* **coderay_line_numbers** - Defines how and if line numbers should be shown
-* **coderay_tab_width** - The tab width used in highlighted code
-* **coderay_wrap** - Defines how the highlighted code should be wrapped
-* **enable_coderay** - Use coderay for syntax highlighting
-* **entity_output** - Defines how entities are output
-* **footnote_backlink** - Defines the text that should be used for the footnote backlinks
-* **footnote_backlink_inline** - Specifies whether the footnote backlink should always be inline
-* **footnote_nr** - The number of the first footnote
-* **gfm_quirks** - Enables a set of GFM specific quirks
-* **hard_wrap** - Interprets line breaks literally
-* **header_offset** - Sets the output offset for headers
-* **html_to_native** - Convert HTML elements to native elements
-* **line_width** - Defines the line width to be used when outputting a document
-* **link_defs** - Pre-defines link definitions
-* **math_engine** - Set the math engine
-* **math_engine_opts** - Set the math engine options
-* **parse_block_html** - Process kramdown syntax in block HTML tags
-* **parse_span_html** - Process kramdown syntax in span HTML tags
-* **smart_quotes** - Defines the HTML entity names or code points for smart quote output
-* **syntax_highlighter** - Set the syntax highlighter
-* **syntax_highlighter_opts** - Set the syntax highlighter options
-* **toc_levels** - Defines the levels that are used for the table of contents
-* **transliterated_header_ids** - Transliterate the header text before generating the ID
-* **typographic_symbols** - Defines a mapping from typographical symbol to output characters
+### Kramdown Processor
+
+By default, Jekyll uses the [GitHub Flavored Markdown (GFM) processor](https://github.com/kramdown/parser-gfm) for Kramdown. (Specifying `input: GFM` is fine, but redundant.) GFM supports a couple additional Kramdown options, documented by [kramdown-parser-gfm](https://github.com/kramdown/parser-gfm). These options can be used directly in your Kramdown Jekyll config, like this:
+
+```yaml
+kramdown:
+  gfm_quirks: [paragraph_end]
+```
+
+You can also change the processor used by Kramdown (as specified for the `input` key in the [Kramdown RDoc](https://kramdown.gettalong.org/rdoc/Kramdown/Document.html#method-c-new)). For example, to use the non-GFM Kramdown processor in Jekyll, add the following to your configuration.
+
+```yaml
+kramdown:
+  input: Kramdown
+```
+
+Documentation for Kramdown parsers is available in the [Kramdown docs](https://kramdown.gettalong.org/parser/kramdown.html). If you use a Kramdown parser other than Kramdown or GFM, you'll need to add the gem for it.
+
+### Syntax Highlighting (CodeRay)
+
+To use the [CodeRay](http://coderay.rubychan.de/) syntax highlighter with Kramdown, you  need to add a dependency on the `kramdown-syntax-coderay` gem. For example, `bundle add kramdown-syntax-coderay`. Then, you'll be able to specify CodeRay in your `syntax_highlighter` config:
+
+```yaml
+kramdown:
+  syntax_highlighter: coderay
+```
+
+CodeRay supports several of its own configuration options, documented in the [kramdown-syntax-coderay docs](https://github.com/kramdown/syntax-coderay) which can be passed as `syntax_highlighter_opts` like this:
+
+```yaml
+kramdown:
+  syntax_highlighter: coderay
+  syntax_highlighter_opts:
+    line_numbers: table
+    bold_every: 5
+```
+
+### Advanced Kramdown Options
+
+Kramdown supports a variety of other relatively advanced options such as `header_offset` and `smart_quotes`. These are documented in the [Kramdown configuration documentation](https://kramdown.gettalong.org/options.html) and can be added to your Kramdown config like this:
+
+```yaml
+kramdown:
+  header_offset: 2
+```
 
 <div class="note warning">
-  <h5>There are two unsupported kramdown options</h5>
+  <h5>There are several unsupported kramdown options</h5>
   <p>
-    Please note that both <code>remove_block_html_tags</code> and
-    <code>remove_span_html_tags</code> are currently unsupported in Jekyll due
-    to the fact that they are not included within the kramdown HTML converter.
+    Please note that Jekyll uses Kramdown's HTML converter. Kramdown options used only by other converters, such as <code>remove_block_html_tags</code> (used by the RemoveHtmlTags converter), will not work.
   </p>
 </div>
 
-For more details about these options have a look at the [Kramdown configuration documentation](https://kramdown.gettalong.org/options.html). 
-
-### CommonMark
+## CommonMark
 
 [CommonMark](https://commonmark.org/) is a rationalized version of Markdown syntax, implemented in C and thus faster than default Kramdown implemented in Ruby. It [slightly differs](https://github.com/commonmark/CommonMark#differences-from-original-markdown) from original Markdown and does not support all the syntax elements implemented in Kramdown, like [Block Inline Attribute Lists](https://kramdown.gettalong.org/syntax.html#block-ials).
 
 It comes in two flavors: basic CommonMark with [jekyll-commonmark](https://github.com/jekyll/jekyll-commonmark) plugin and [GitHub Flavored Markdown supported by GitHub Pages](https://github.com/github/jekyll-commonmark-ghpages).
 
-### Redcarpet
-
-Redcarpet can be configured by providing an `extensions` sub-setting, whose
-value should be an array of strings. Each string should be the name of one of
-the `Redcarpet::Markdown` class's extensions; if present in the array, it will
-set the corresponding extension to `true`.
-
-Jekyll handles two special Redcarpet extensions:
-
-- `no_fenced_code_blocks` --- By default, Jekyll sets the `fenced_code_blocks`
-extension (for delimiting code blocks with triple tildes or triple backticks)
-to `true`, probably because GitHub's eager adoption of them is starting to make
-them inescapable. Redcarpet's normal `fenced_code_blocks` extension is inert
-when used with Jekyll; instead, you can use this inverted version of the
-extension for disabling fenced code.
-
-Note that you can also specify a language for highlighting after the first
-delimiter:
-
-        ```ruby
-        # ...ruby code
-        ```
-
-With both fenced code blocks and highlighter enabled, this will statically
-highlight the code; without any syntax highlighter, it will add a
-`class="LANGUAGE"` attribute to the `<code>` element, which can be used as a
-hint by various JavaScript code highlighting libraries.
-
-- `smart` --- This pseudo-extension turns on SmartyPants, which converts
-  straight quotes to curly quotes and runs of hyphens to em (`---`) and en (`--`) dashes.
-
-All other extensions retain their usual names from Redcarpet, and no renderer
-options aside from `smart` can be specified in Jekyll. [A list of available
-extensions can be found in the Redcarpet README file.](https://github.com/vmg/redcarpet/blob/v3.2.2/README.markdown#and-its-like-really-simple-to-use)
-Make sure you're looking at the README for the right version of
-Redcarpet: Jekyll currently uses v3.2.x. The most commonly used
-extensions are:
-
-- `tables`
-- `no_intra_emphasis`
-- `autolink`
-
 ### Custom Markdown Processors
 
 If you're interested in creating a custom markdown processor, you're in luck! Create a new class in the `Jekyll::Converters::Markdown` namespace:

docs/_docs/configuration/options.md

@@ -20,120 +20,35 @@ class="flag">flags</code> (specified on the command-line) that control them.
     </tr>
   </thead>
   <tbody>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Site Source</strong></p>
-        <p class="description">Change the directory where Jekyll will read files</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">source: DIR</code></p>
-        <p><code class="flag">-s, --source DIR</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Site Destination</strong></p>
-        <p class="description">Change the directory where Jekyll will write files</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">destination: DIR</code></p>
-        <p><code class="flag">-d, --destination DIR</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Safe</strong></p>
-        <p class="description">Disable <a href="/docs/plugins/">custom plugins, and ignore symbolic links</a>.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">safe: BOOL</code></p>
-        <p><code class="flag">--safe</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Exclude</strong></p>
-        <p class="description">
-          Exclude directories and/or files from the
-          conversion. These exclusions are relative to the site's
-          source directory and cannot be outside the source directory.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">exclude: [DIR, FILE, ...]</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Include</strong></p>
-        <p class="description">
-          Force inclusion of directories and/or files in the conversion.
-          <code>.htaccess</code> is a good example since dotfiles are excluded
-          by default.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">include: [DIR, FILE, ...]</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Keep files</strong></p>
-        <p class="description">
-          When clobbering the site destination, keep the selected files.
-          Useful for files that are not generated by jekyll; e.g. files or
-          assets that are generated by your build tool.
-          The paths are relative to the <code>destination</code>.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">keep_files: [DIR, FILE, ...]</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Time Zone</strong></p>
-        <p class="description">
-            Set the time zone for site generation. This sets the <code>TZ</code>
-            environment variable, which Ruby uses to handle time and date
-            creation and manipulation. Any entry from the
-            <a href="https://en.wikipedia.org/wiki/Tz_database">IANA Time Zone
-            Database</a> is valid, e.g. <code>America/New_York</code>. A list of all
-            available values can be found <a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones">
-            here</a>. When serving on a local machine, the default time zone is set by your operating system. But when served on a remote host/server, the default time zone depends on the server's setting or location.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">timezone: TIMEZONE</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Encoding</strong></p>
-        <p class="description">
-            Set the encoding of files by name (only available for Ruby
-            1.9 or later).
-            The default value is <code>utf-8</code> starting in 2.0.0,
-            and <code>nil</code> before 2.0.0, which will yield the Ruby
-            default of <code>ASCII-8BIT</code>.
-            Available encodings can be shown by the
-            command <code>ruby -e 'puts Encoding::list.join("\n")'</code>.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">encoding: ENCODING</code></p>
-      </td>
-    </tr>
+    {% for setting in site.data.config_options.global %}
+      <tr class="setting">
+        <td>
+          <p class="name">
+            <strong>{{ setting.name }}</strong>
+            {% if setting.version-badge %}
+              <span class="version-badge" title="Introduced in v{{ setting.version-badge }}">{{ setting.version-badge }}</span>
+            {% endif %}
+          </p> 
+          <p class="description">{{ setting.description }}</p>
+        </td> 
+        <td class="align-center">
+          <p><code class="option">{{ setting.option }}</code></p>
+          {% if setting.flag %}
+            <p><code class="flag">{{ setting.flag }}</code></p>
+          {% endif %}
+        </td>
+      </tr>
+    {% endfor %}
     <tr>
       <td>
         <p class='name'><strong>Defaults</strong></p>
         <p class='description'>
-            Set defaults for <a href="/docs/front-matter/" title="front matter">front matter</a>
+            Set defaults for <a href="{{ '/docs/front-matter/' | relative_url }}" title="front matter">front matter</a>
             variables.
         </p>
       </td>
       <td class='align-center'>
-        <p>see <a href="/docs/configuration/front-matter-defaults/" title="details">below</a></p>
+        <p>see <a href="{{ '/docs/configuration/front-matter-defaults/' | relative_url }}" title="details">below</a></p>
       </td>
     </tr>
   </tbody>
@@ -165,155 +80,27 @@ class="flag">flags</code> (specified on the command-line) that control them.
     </tr>
   </thead>
   <tbody>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Regeneration</strong></p>
-        <p class="description">Enable auto-regeneration of the site when files are modified.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">-w, --[no-]watch</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Configuration</strong></p>
-        <p class="description">Specify config files instead of using <code>_config.yml</code> automatically. Settings in later files override settings in earlier files.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">--config FILE1[,FILE2,...]</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Drafts</strong></p>
-        <p class="description">Process and render draft posts.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">show_drafts: BOOL</code></p>
-        <p><code class="flag">--drafts</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Environment</strong></p>
-        <p class="description">Use a specific environment value in the build.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">JEKYLL_ENV=production</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Future</strong></p>
-        <p class="description">Publish posts or collection documents with a future date.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">future: BOOL</code></p>
-        <p><code class="flag">--future</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Unpublished</strong></p>
-        <p class="description">Render posts that were marked as unpublished.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">unpublished: BOOL</code></p>
-        <p><code class="flag">--unpublished</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>LSI</strong></p>
-        <p class="description">Produce an index for related posts. Requires the <a href="http://www.classifier-reborn.com/">classifier-reborn</a> plugin.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">lsi: BOOL</code></p>
-        <p><code class="flag">--lsi</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Limit Posts</strong></p>
-        <p class="description">Limit the number of posts to parse and publish.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">limit_posts: NUM</code></p>
-        <p><code class="flag">--limit_posts NUM</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Force polling</strong></p>
-        <p class="description">Force watch to use polling.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">--force_polling</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Verbose output</strong></p>
-        <p class="description">Print verbose output.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">-V, --verbose</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Silence Output</strong></p>
-        <p class="description">Silence the normal output from Jekyll
-        during a build</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">-q, --quiet</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Incremental build</strong></p>
-        <p class="description">
-            Enable the experimental incremental build feature. Incremental build only
-            re-builds posts and pages that have changed, resulting in significant performance
-            improvements for large sites, but may also break site generation in certain
-            cases.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">incremental: BOOL</code></p>
-        <p><code class="flag">-I, --incremental</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Liquid profiler</strong></p>
-        <p class="description">
-            Generate a Liquid rendering profile to help you identify performance bottlenecks.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">profile: BOOL</code></p>
-        <p><code class="flag">--profile</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Strict Front Matter</strong></p>
-        <p class="description">
-            Cause a build to fail if there is a YAML syntax error in a page's front matter.
-        </p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">strict_front_matter: BOOL</code></p>
-        <p><code class="flag">--strict_front_matter</code></p>
-      </td>
-    </tr>
+    {% for setting in site.data.config_options.build %}
+      <tr class="setting">
+        <td>
+          <p class="name">
+            <strong>{{ setting.name }}</strong>
+            {% if setting.version-badge %}
+              <span class="version-badge" title="Introduced in v{{ setting.version-badge }}">{{ setting.version-badge }}</span>
+            {% endif %}
+          </p> 
+          <p class="description">{{ setting.description }}</p>
+        </td> 
+        <td class="align-center">
+          {% if setting.option %}<p><code class="option">{{ setting.option }}</code></p>{% endif %}
+          {% if setting.flag %}<p><code class="flag">{{ setting.flag }}</code></p>{% endif %}
+        </td>
+      </tr>
+    {% endfor %}
   </tbody>
 </table>
 </div>
 
-
 ### Serve Command Options
 
 In addition to the options below, the `serve` sub-command can accept any of the options
@@ -329,83 +116,39 @@ before your site is served.
     </tr>
   </thead>
   <tbody>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Local Server Port</strong></p>
-        <p class="description">Listen on the given port.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">port: PORT</code></p>
-        <p><code class="flag">--port PORT</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Local Server Hostname</strong></p>
-        <p class="description">Listen at the given hostname.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">host: HOSTNAME</code></p>
-        <p><code class="flag">--host HOSTNAME</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Base URL</strong></p>
-        <p class="description">Serve the website from the given base URL.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">baseurl: URL</code></p>
-        <p><code class="flag">--baseurl URL</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Live Reload</strong></p>
-        <p class="description">Reload a page automatically on the browser when its content is edited.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">livereload: true</code></p>
-        <p><code class="flag">--livereload</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Detach</strong></p>
-        <p class="description">Detach the server from the terminal.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="option">detach: BOOL</code></p>
-        <p><code class="flag">-B, --detach</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>Skips the initial site build</strong></p>
-        <p class="description">Skips the initial site build which occurs before the server is started.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">--skip-initial-build</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>X.509 (SSL) Private Key</strong></p>
-        <p class="description">SSL Private Key, stored or symlinked in the site source.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">--ssl-key</code></p>
-      </td>
-    </tr>
-    <tr class="setting">
-      <td>
-        <p class="name"><strong>X.509 (SSL) Certificate</strong></p>
-        <p class="description">SSL Public certificate, stored or symlinked in the site source.</p>
-      </td>
-      <td class="align-center">
-        <p><code class="flag">--ssl-cert</code></p>
-      </td>
-    </tr>
+    {% for setting in site.data.config_options.serve %}
+      <tr class="setting">
+        <td>
+          <p class="name">
+            <strong>{{ setting.name }}</strong>
+            {% if setting.version-badge %}
+              <span class="version-badge" title="Introduced in v{{ setting.version-badge }}">{{ setting.version-badge }}</span>
+            {% endif %}
+          </p> 
+          <p class="description">{{ setting.description }}</p>
+        </td> 
+        <td class="align-center">
+          {% if setting.option %}
+            <p><code class="option">{{ setting.option }}</code></p>
+          {% elsif setting.options %}
+            <p>
+              {% for option in setting.options %}
+                <code class="option">{{ option }}</code><br>
+              {% endfor %}
+            </p>
+          {% endif %}
+          {% if setting.flag %}
+            <p><code class="flag">{{ setting.flag }}</code></p>
+          {% elsif setting.flags %}
+            <p>
+            {% for flag in setting.flags %}
+              <code class="flag">{{ flag }}</code><br>
+            {% endfor %}
+            </p>
+          {% endif %}
+        </td>
+      </tr>
+    {% endfor %}
   </tbody>
 </table>
 </div>

docs/_docs/configuration/sass.md

@@ -0,0 +1,15 @@
+---
+title: Sass/SCSS Options
+permalink: "/docs/configuration/sass/"
+---
+
+Jekyll comes bundled with [jekyll-sass-converter](https://github.com/jekyll/jekyll-sass-converter) plugin. By default, Jekyll will look for Sass partials in the `_sass` directory relative to your site's `source` directory.
+
+You can further configure the plugin by adding options to your Jekyll config under the `sass` attribute. See the [plugin's documentation](https://github.com/jekyll/jekyll-sass-converter#usage) for details and for its default values.
+
+<div class="note info">
+  <p>
+    Note that directory paths specified in the <code>sass</code> configuration
+    are resolved relative to your site's <code>source</code>, not relative to the location of the <code>_config.yml</code> file.
+  </p>
+</div>

docs/_docs/continuous-integration/circleci.md

@@ -15,9 +15,9 @@ To start building your project on CircleCI, all you need to do is 'follow' your
 1. Visit the 'Add Projects' page
 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.
+1. The first build will start on its own. You can start telling CircleCI how to build your project by creating a [.circleci/config.yml][3] file in the root of your repository.
 
-[3]: https://circleci.com/docs/configuration/
+[3]: https://circleci.com/docs/2.0/configuration-reference/
 
 ## 2. Dependencies
 
@@ -28,22 +28,24 @@ The easiest way to manage dependencies for a Jekyll project (with or without Cir
 ```ruby
 source 'https://rubygems.org'
 
-ruby '2.4.0'
+ruby '2.7.4'
 
 gem 'jekyll'
 gem 'html-proofer'
 ```
 
-CircleCI detects when `Gemfile` is present and will automatically run `bundle install` for you in the `dependencies` phase.
+```yaml
+    - step:
+       run: bundle install
+```
 
 ## 3. Testing
 
 The most basic test that can be run is 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
+    - step:
+        run: bundle exec jekyll build
 ```
 
 ### HTML Proofer
@@ -54,46 +56,32 @@ With your site built, it's useful to run tests to check for valid HTML, broken l
 [6]: https://github.com/gjtorikian/html-proofer/blob/master/README.md#configuration
 
 ```yaml
-test:
-  post:
-    - bundle exec htmlproofer ./_site --check-html --disable-external
+    - step:
+        run: bundle exec htmlproofer ./_site --check-html --disable-external
 ```
 
-## Complete Example circle.yml File
+## Complete Example .circleci/config.yml File
 
-When you put it all together, here's an example of what that `circle.yml` file could look like in v1:
+The example `.circleci/config.yml` below demonstrates how to
+deploy your Jekyll project to AWS. In order for this to work you would first have to set the
+`S3_BUCKET_NAME` [environment variable](https://circleci.com/docs/2.0/env-vars/).
 
 ```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
+workflows:
+  test-deploy:
+    jobs:
+      - build
+      - deploy:
+          requires:
+            - build
+          filters:
+            branches:
+              only: master
+version: 2.1
 jobs:
   build:
-    <<: *defaults
     docker:
-      - image: circleci/ruby:2.5
+      - image: cimg/ruby:2.7.4
     environment:
       BUNDLE_PATH: ~/repo/vendor/bundle
     steps:
@@ -125,9 +113,8 @@ jobs:
           paths:
             - _site
   deploy:
-    <<: *defaults
     docker:
-      - image: circleci/python:3.6.3
+      - image: cimg/python:3.9.1
     environment:
       S3_BUCKET_NAME: <<YOUR BUCKET NAME HERE>>
     steps:
@@ -139,17 +126,6 @@ jobs:
       - 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?

docs/_docs/continuous-integration/github-actions.md

@@ -0,0 +1,232 @@
+---
+title: GitHub Actions
+---
+
+When building a Jekyll site with GitHub Pages, the standard flow is restricted for security reasons
+and to make it simpler to get a site setup. For more control over the build and still host the site
+with GitHub Pages you can use GitHub Actions.
+
+## Advantages of using Actions
+
+### Control over gemset
+
+- **Jekyll version** --- Instead of using the currently enabled version at `3.9.0`, you can use any
+  version of Jekyll you want. For example `{{site.version}}`, or point directly to the repository.
+- **Plugins** --- You can use any Jekyll plugins irrespective of them being on the
+  [supported versions][ghp-whitelist] list, even `*.rb` files placed in the `_plugins` directory
+  of your site.
+- **Themes** --- While using a custom theme is possible without Actions, it is now simpler.
+
+### Workflow Management
+
+- **Customization** --- By creating a workflow file to run Actions, you can specify custom build
+  steps, use environment variables.
+- **Logging** --- The build log is visible and can be tweaked to be verbose, so it is much easier to
+  debug errors using Actions.
+
+## Workspace setup
+
+The first and foremost requirement is a Jekyll project hosted at GitHub. Choose an existing Jekyll
+project or follow the [quickstart]({{ '/docs/' | relative_url }}) and push the repository to GitHub
+if it is not hosted there already.
+
+We're only going to cover builds from the `main` branch in this page. Therefore, ensure that you
+are working on the `main` branch. If necessary, you may create it based on your default branch.
+When the Action builds your site, the contents of the _destination_ directory will be automatically
+pushed to the `gh-pages` branch with a commit, ready to be used for serving.
+
+{: .note .warning}
+The Action we're using here will create (or reset an existing) `gh-pages` branch on every successful
+deploy.<br/> So, if you have an existing `gh-pages` branch that is used to deploy your production
+build, ensure to make a backup of the contents into a different branch so that you can rollback
+easily if necessary.
+
+The Jekyll site we'll be using for the rest of this page initially consists of just a `_config.yml`,
+an `index.md` page and a `Gemfile`. The contents are respectively:
+
+```yaml
+# _config.yml
+
+title: "Jekyll Actions Demo"
+```
+
+{% raw %}
+
+```liquid
+---
+---
+
+Welcome to My Home Page
+
+{% assign date = '2020-04-13T10:20:00Z' %}
+
+- Original date - {{ date }}
+- With timeago filter - {{ date | timeago }}
+```
+
+{% endraw %}
+
+```ruby
+# Gemfile
+
+source 'https://rubygems.org'
+
+gem 'jekyll', '~> 4.2'
+
+group :jekyll_plugins do
+  gem 'jekyll-timeago', '~> 0.13.1'
+end
+```
+
+{: .note .info}
+The demo site uses Jekyll 4 and a [third-party plugin][timeago-plugin], both of which are currently
+not whitelisted for use on GitHub pages. The plugin will allow us to describe how far back a date
+was from today. e.g. If we give a date as `2016-03-23T10:20:00Z` and the current date is
+`2020-04-13T10:20:00Z`, then the output would be `4 years and 3 weeks ago`.
+
+{: .note .info}
+The action we're using takes care of installing the Ruby gems and dependencies. While that keeps
+the setup simple for the user, one may encounter issues if they also check-in `Gemfile.lock` if it
+was generated with an old version of Bundler.
+
+### Setting up the Action
+
+GitHub Actions are registered for a repository by using a YAML file inside the directory path
+`.github/workflows` (note the dot at the start). For simplicity, here we use one of the
+[Jekyll Actions](#external-links) to show you how to use the action.
+
+Create a **workflow file**, say `github-pages.yml`, using either the GitHub interface or by pushing
+a YAML file to the workflow directory path manually. The base contents are:
+
+{% raw %}
+
+```yaml
+name: Build and deploy Jekyll site to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main # or master before October 2020
+
+jobs:
+  github-pages:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/cache@v2
+        with:
+          path: vendor/bundle
+          key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile') }}
+          restore-keys: |
+            ${{ runner.os }}-gems-
+      - uses: helaili/jekyll-action@2.0.5    # Choose any one of the Jekyll Actions
+        with:                                # Some relative inputs of your action
+          token: ${{ secrets.GITHUB_TOKEN }}
+```
+
+{% endraw %}
+
+The above workflow can be explained as the following:
+
+- We trigger the build using **on.push** condition for `main` branch only --- this prevents
+  the Action from overwriting the `gh-pages` branch on any feature branch pushes.
+- The **name** of the job matches our YAML filename: `github-pages`.
+- The **checkout** action takes care of cloning your repository.
+- The **cache** action is an optimization to avoid fetching and installing gems on every build.
+- We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.5`,
+  this handles the build and deploy. You can choose any one of the Jekyll Actions that matches
+  your project and flavor from [GitHub Marketplace](https://github.com/marketplace?type=actions&query=jekyll+action).
+- We set a reference to a secret **environment variable** for the action to use. The `GITHUB_TOKEN`
+  is a secret token automatically initialized at the start of every workflow run.
+  More information can be found in [GitHub documentation](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#about-the-github_token-secret). 
+
+Instead of using the **on.push** condition, you could trigger your build on a **schedule** by
+using the [on.schedule] parameter. For example, here we build daily at midnight by specifying
+**cron** syntax, which can be tested at the [crontab guru] site.
+
+```yaml
+on:
+  schedule:
+    - cron: "0 0 * * *"
+```
+
+Note that this string must be quoted to prevent the asterisks from being evaluated incorrectly.
+
+[on.schedule]: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule
+[crontab guru]: https://crontab.guru/
+
+### Providing permissions
+
+At the start of each workflow run, GitHub automatically creates a unique `GITHUB_TOKEN` secret to use in
+your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run. You can use the
+`GITHUB_TOKEN` by using the standard syntax for referencing secrets: `${{ secrets.GITHUB_TOKEN }}`.
+For more information, please read [GitHub's docs on token authentication][github-token-ref]
+
+[github-token-ref]: https://docs.github.com/en/actions/security-guides/automatic-token-authentication
+
+If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create
+a Personal Access Token (PAT), and set it as a secret in your repository for this action to push to the
+`gh-pages` branch:
+
+1. On your GitHub profile, under **Developer Settings**, go to the [Personal Access Tokens][tokens]
+   section.
+2. **Create** a token. Give it a name like "GitHub Actions" and ensure it has permissions to
+   `public_repos` (or the entire `repo` scope for private repository) --- necessary for the action
+   to commit to the `gh-pages` branch.
+3. **Copy** the token value.
+4. Go to your repository's **Settings** and then the **Secrets** tab.
+5. **Create** a token named `YOUR_CUSTOM_TOKEN` (_important_). Give it a value using the value copied
+   above.
+
+### Build and deploy
+
+On pushing any local changes onto `main`, the action will be triggered and the build will
+**start**.
+
+To watch the progress and see any build errors, check on the build **status** using one of the
+following approaches:
+
+- **View by commit**
+  - Go to the repository level view in GitHub. Under the most recent commit (near the top) you’ll
+    see a **status symbol** next to the commit message as a tick or _X_. Hover over it and click
+    the **details** link.
+- **Actions tab**
+  - Go to the repository's Actions tab. Click on the `jekyll` workflow tab.
+
+If all goes well, all steps will be green and the built assets will now exist on the `gh-pages`
+branch.
+
+On a successful build, GitHub Pages will **publish** the site stored on the repository `gh-pages`
+branches. Note that you do not need to setup a `gh-pages` branch or enable GitHub Pages, as the
+action will take care of this for you.
+(For private repositories, you'll have to upgrade to a paid plan).
+
+To see the **live site**:
+
+1. Go to the **environment** tab on your repository.
+2. Click **View Deployment** to see the deployed site URL.
+3. View your site at the **URL**. Make sure the `timeago` filter works as expected.
+4. Optionally **add** this URL to your repository's main page and to your `README.md`, to make it
+   easy for people to find.
+
+When you need to make further **changes** to the site, commit to `master` and push. The workflow
+will build and deploy your site again.
+
+Be sure **not to edit** the `gh-pages` branch directly, as any changes will be lost on the next
+successful deploy from the Action.
+
+## External links
+
+- [jekyll-actions] is an action available on the GitHub Marketplace and was used in this guide.
+- [jekyll-actions-quickstart] is an unofficial repository that includes a live demo of the
+  `jekyll-actions` action. That project can be used as a template for making a new site.
+- [jekyll-action-ts] is another action to build and publish Jekyll sites on GiHub Pages that includes HTML formatting options with Prettier and caching.
+- [jekyll-deploy-action] is a GitHub Action to deploy the Jekyll site conveniently for GitHub Pages (An alternative action with better speed and compatibility).
+
+[ghp-whitelist]: https://pages.github.com/versions/
+[timeago-plugin]: https://rubygems.org/gems/jekyll-timeago
+[tokens]: https://github.com/settings/tokens
+[jekyll-actions]: https://github.com/marketplace/actions/jekyll-actions
+[jekyll-actions-quickstart]: https://github.com/MichaelCurrin/jekyll-actions-quickstart
+[jekyll-action-ts]: https://github.com/limjh16/jekyll-action-ts
+[jekyll-deploy-action]: https://github.com/jeffreytse/jekyll-deploy-action

docs/_docs/continuous-integration/razorops.md

@@ -0,0 +1,61 @@
+---
+title: "Razorops"
+---
+
+[Razorops][razorops-homepage] is a complete container native CI/CD solution handling all aspects of the software lifecycle from the moment a commit is created until it is deployed to production.
+Razorops has all the capabilities that you would expect from a CI/CD platform such as
+1. Code compilation/build
+2. Artifact packaging
+3. Testing Automation(unit, integration, acceptance etc.)
+4. Faster builds and shipping to production
+
+Razorops is a single solution that implements the whole pipeline from start to deployment.
+
+With [Razorops][razorops-homepage] you can set up your Jekyll websites project's build, test, and deploy steps just in 15 min. It supports [GitHub][github-homepage], [Bitbucket][bitbucket-homepage], and [GitLab][gitlab-homepage] repositories. The following guide will show you how to set up a free environment to build, test and deploy your Jekyll project.
+
+[razorops-homepage]: https://razorops.com/
+[docker-homepage]: https://www.docker.com/
+[github-homepage]: https://github.com
+[bitbucket-homepage]: https://bitbucket.org/
+[gitlab-homepage]: https://gitlab.com
+[deploy-s3]: https://razorops.com/blog/how-to-deploy-a-static-website-to-aws-s3-with-razorops-ci-cd/
+
+## 1. Getting started
+
+1. Log in at [https://razorops.com/][razorops-homepage] with your GitHub/Bitbucket or Gitlab account
+2. Create a pipeline, choose your Git provider and select your Jekyll Project
+3. Add .razorops.yaml file in your root directory of your project
+4. Add environment var and your deployment is ready
+5. Add build and deployment steps as shown in this post [How to Deploy a Static Website to AWS S3 with Razorops CI/CD][deploy-s3]
+
+## 2. How it works
+
+Whenever you make a push to the selected branch, your steps auto runs as defined in .razorops.yaml file 
+
+```yaml
+  tasks:
+    build-and-deploy:
+      steps:
+      - checkout
+      # commands to build jekyll website
+      - commands:
+        - bundle install
+        - JEKYLL_ENV=production bundle exec jekyll build
+      # Commands to upload static pages folder to AWS S3 or ftp
+      # Set AWS access key & secrets environment variables under 
+      # Razorops dashboard project pipelines 
+      - commands:
+        - aws s3 rm s3://$AWS_S3_BUCKET --recursive
+        - aws s3 cp _site s3://$AWS_S3_BUCKET --recursive
+        if: branch == 'main'
+
+```
+
+
+
+ Build step generates _site folder as Jekyll default and during deploy you will able to ship code to s3 or any ftp server you can define any command to ship your website code to server.
+
+Razorops is FREE for opensource projects, Try it Now
+[https://razorops.com/][razorops-homepage]
+
+

docs/_docs/continuous-integration/travis-ci.md

@@ -34,7 +34,7 @@ Save the commands you want to run and succeed in a file: `./script/cibuild`
 
 ### The HTML Proofer Executable
 
-```sh
+```bash
 #!/usr/bin/env bash
 set -e # halt script on error
 
@@ -105,17 +105,11 @@ branches:
   - gh-pages     # test the gh-pages branch
   - /pages-(.*)/ # test every branch which starts with "pages-"
 
-env:
-  global:
-  - NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
-
 addons:
   apt:
     packages:
     - libcurl4-openssl-dev
 
-sudo: false # route your build to the container-based infrastructure for a faster build
-
 cache: bundler # caching bundler gem packages will speed up build
 
 # Optional: disable email notifications about the outcome of your builds
@@ -189,18 +183,6 @@ prefixed, exemplified above with the `/pages-(.*)/` regular expression.
 The `branches` directive is completely optional. Travis will build from every
 push to any branch of your repo if leave it out.
 
-```yaml
-env:
-  global:
-  - NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
-```
-
-Using `html-proofer`? You'll want this environment variable. Nokogiri, used
-to parse HTML files in your compiled site, comes bundled with libraries
-which it must compile each time it is installed. Luckily, you can
-dramatically decrease the install time of Nokogiri by setting the
-environment variable `NOKOGIRI_USE_SYSTEM_LIBRARIES` to `true`.
-
 <div class="note warning">
   <h5>Be sure to exclude <code>vendor</code> from your
    <code>_config.yml</code></h5>
@@ -212,16 +194,6 @@ environment variable `NOKOGIRI_USE_SYSTEM_LIBRARIES` to `true`.
 exclude: [vendor]
 ```
 
-By default you should supply the `sudo: false` command to Travis. This command
-explicitly tells Travis to run your build on Travis's [container-based
- infrastructure](https://docs.travis-ci.com/user/workers/container-based-infrastructure/#Routing-your-build-to-container-based-infrastructure). Running on the container-based infrastructure can often times
-speed up your build. If you have any trouble with your build, or if your build
-does need `sudo` access, modify the line to `sudo: required`.
-
-```yaml
-sudo: false
-```
-
 To speed up the build, you should cache the gem packages created by `bundler`.
 Travis has a pre-defined [cache strategy for this tool][6] which should have
 all the default configs to do exactly that.

docs/_docs/contributing.md

@@ -14,24 +14,24 @@ See the [support guidelines](https://jekyllrb.com/docs/support/)
 
 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.
+- [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 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.
+- 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.
 
-* If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/).
+- 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.
+- 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
 
@@ -80,11 +80,12 @@ If you ever need to update our documentation with an icon that is not already av
 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
+
+- 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:
+- Fix paths in the `@font-face {}` declaration by adding `../` before `fonts/FontAwesome.*` like so:
   `('../fonts/Fontawesome.woff?9h6hxj')`.
 
 ### Adding plugins
@@ -105,21 +106,21 @@ If your contribution changes any Jekyll behavior, make sure to update the docume
 
 #### 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 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.
+- 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.
+- 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).
+- 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)
+- 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)
 
-* Previously, we've used the WIP Probot app to help contributors determine whether their pull request is ready for review. Please use a [draft pull request](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests) instead. When you're ready, [mark the pull request as ready for review](https://help.github.com/en/articles/changing-the-stage-of-a-pull-request)
+- Previously, we've used the WIP Probot app to help contributors determine whether their pull request is ready for review. Please use a [draft pull request](https://help.github.com/en/articles/about-pull-requests#draft-pull-requests) instead. When you're ready, [mark the pull request as ready for review](https://help.github.com/en/articles/changing-the-stage-of-a-pull-request)
 
 ## Running tests locally
 
@@ -152,6 +153,10 @@ script/cucumber features/blah.feature
 Both `script/test` and `script/cucumber` can be run without arguments to
 run its entire respective suite.
 
+## Visual Studio Code Development Container
+
+If you've got [Visual Studio Code](https://code.visualstudio.com/) with the [Remote Development Extension Pack](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) installed then simply opening this repository in Visual Studio Code and following the prompts to "Re-open In A Development Container" will get you setup and ready to go with a fresh environment with all the requirements installed.
+
 ## 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/datafiles.md

@@ -3,9 +3,9 @@ title: Data Files
 permalink: /docs/datafiles/
 ---
 
-In addition to the [built-in variables](../variables/) available from Jekyll,
+In addition to the [built-in variables]({{'/docs/variables/' | relative_url }}) available from Jekyll,
 you can specify your own custom data that can be accessed via the [Liquid
-templating system](https://wiki.github.com/shopify/liquid/liquid-for-designers).
+templating system](https://github.com/Shopify/liquid/wiki/Liquid-for-Designers).
 
 Jekyll supports loading data from [YAML](http://yaml.org/), [JSON](http://www.json.org/), [CSV](https://en.wikipedia.org/wiki/Comma-separated_values), and [TSV](https://en.wikipedia.org/wiki/Tab-separated_values) files located in the `_data` directory.
 Note that CSV and TSV files *must* contain a header row.
@@ -18,8 +18,8 @@ Plugins/themes can also leverage Data Files to set configuration variables.
 ## The Data Folder
 
 The `_data` folder is where you can store additional data for Jekyll to use when
-generating your site. These files must be YAML, JSON, or CSV files (using either
-the `.yml`, `.yaml`, `.json` or `.csv` extension), and they will be
+generating your site. These files must be YAML, JSON, TSV or CSV files (using either
+the `.yml`, `.yaml`, `.json`, `.tsv`, or `.csv` extension), and they will be
 accessible via `site.data`.
 
 ## Example: List of members
@@ -42,15 +42,15 @@ In `_data/members.yml`:
 
 Or `_data/members.csv`:
 
-```text
+```
 name,github
 Eric Mill,konklone
 Parker Moore,parkr
 Liu Fengyun,liufengyun
 ```
 
-This data can be accessed via `site.data.members` (notice that the filename
-determines the variable name).
+This data can be accessed via `site.data.members` (notice that the file's *basename* determines the variable name and
+therefore one should avoid having data files with the same basename but different extensions, in the same directory).
 
 You can now render the list of members in a template:
 
@@ -147,4 +147,31 @@ author: dave
 ```
 {% endraw %}
 
-For information on how to build robust navigation for your site (especially if you have a documentation website or another type of Jekyll site with a lot of pages to organize), see [Navigation](/tutorials/navigation).
+For information on how to build robust navigation for your site (especially if you have a documentation website or another type of Jekyll site with a lot of pages to organize), see [Navigation]({{ '/tutorials/navigation/' | relative_url }}).
+
+## CSV/TSV Parse Options
+
+The way Ruby parses CSV and TSV files can be customized with the `csv_reader` and `tsv_reader`
+configuration options. Each configuration key exposes the same options:
+
+`converters`: What [CSV converters](https://ruby-doc.org/stdlib-2.5.0/libdoc/csv/rdoc/CSV.html#Converters) should be
+              used when parsing the file. Available options are `integer`, `float`, `numeric`, `date`, `date_time` and
+              `all`. By default, this list is empty.
+`encoding`:   What encoding the files are in. Defaults to the site `encoding` configuration option.
+`headers`:    Boolean field for whether to parse the first line of the file as headers. When `false`, it treats the
+              first row as data. Defaults to `true`.
+
+Examples:
+
+```yaml
+csv_reader:
+    converters:
+      - numeric
+      - datetime
+    headers: true
+    encoding: utf-8
+tsv_reader:
+    converters:
+      - all
+    headers: false
+```

docs/_docs/deployment.md

@@ -6,6 +6,6 @@ redirect_from: "/docs/deployment-methods/index.html"
 
 Sites built using Jekyll can be deployed in a large number of ways due to the static nature of the generated output. Here's some of the most common ways:
 
-* [Manually](/docs/deployment/manual/)
-* [Automated](/docs/deployment/automated/)
-* [Third Party](/docs/deployment/third-party/)
+* [Manually]({{ '/docs/deployment/manual/' | relative_url }})
+* [Automated]({{ '/docs/deployment/automated/' | relative_url }})
+* [Third Party]({{ '/docs/deployment/third-party/' | relative_url }})

docs/_docs/deployment/automated.md

@@ -11,13 +11,15 @@ CI.
 
 These services run a script when there's a commit on your Git repository.
 You might want this script to build the site, run tests over the output then deploy it to the
-service of your choice. 
+service of your choice.
 
 We have guides for the following providers:
 
-* [Travis CI](/docs/continuous-integration/travis-ci/)
-* [CircleCI](/docs/continuous-integration/circleci/)
-* [Buddy](/docs/continuous-integration/buddyworks/)
+* [GitHub Actions]({{ '/docs/continuous-integration/github-actions/' | relative_url }})
+* [Travis CI]({{ '/docs/continuous-integration/travis-ci/' | relative_url }})
+* [CircleCI]({{ '/docs/continuous-integration/circleci/' | relative_url }})
+* [Buddy]({{ '/docs/continuous-integration/buddyworks/' | relative_url }})
+* [Razorops CI/CD]({{ '/docs/continuous-integration/razorops/' | relative_url }})
 
 ## Git post-receive hook
 
@@ -42,12 +44,11 @@ installed on the server:
 export GEM_HOME=$HOME/gems
 export PATH=$GEM_HOME/bin:$PATH
 
-GIT_REPO=$HOME/myrepo.git
 TMP_GIT_CLONE=$HOME/tmp/myrepo
 GEMFILE=$TMP_GIT_CLONE/Gemfile
 PUBLIC_WWW=/var/www/myrepo
 
-git clone $GIT_REPO $TMP_GIT_CLONE
+git clone $GIT_DIR $TMP_GIT_CLONE
 BUNDLE_GEMFILE=$GEMFILE bundle install
 BUNDLE_GEMFILE=$GEMFILE bundle exec jekyll build -s $TMP_GIT_CLONE -d $PUBLIC_WWW
 rm -Rf $TMP_GIT_CLONE

docs/_docs/deployment/manual.md

@@ -25,13 +25,12 @@ low-volume blogs as you only pay for what you use.
 
 ## FTP
 
-Most traditional web hosting provider let you upload files to their servers over FTP. To upload a Jekyll site to a web host using FTP, run the `jekyll build` command and copy the contents of the generated `_site` folder to the root folder of your hosting account. This is most likely to be the `httpdocs` or `public_html` folder on most hosting providers.
+Most traditional web hosting providers let you upload files to their servers over FTP. To upload a Jekyll site to a web host using FTP, run the `jekyll build` command and copy the contents of the generated `_site` folder to the root folder of your hosting account. This is most likely to be the `httpdocs` or `public_html` folder on most hosting providers.
 
 ## scp
 
 If you have direct access to the deployment web server, the process is essentially the same, except you might have other methods available to you (such as `scp`, or even direct filesystem access) for transferring the files. Remember to make sure the contents of the generated `_site` folder get placed in the appropriate web root directory for your web server.
 
-
 ## Rack-Jekyll
 
 [Rack-Jekyll](https://github.com/adaoraul/rack-jekyll/) allows you to deploy your site on any Rack server such as Amazon EC2, Slicehost, Heroku, and so forth. It also can run with [shotgun](https://github.com/rtomayko/shotgun/), [rackup](https://github.com/rack/rack), [mongrel](https://github.com/mongrel/mongrel), [unicorn](https://github.com/defunkt/unicorn/), and [others](https://github.com/adaoraul/rack-jekyll#readme).

docs/_docs/deployment/third-party.md

@@ -3,17 +3,16 @@ title: 3rd Party
 permalink: /docs/deployment/third-party/
 ---
 
-## Aerobatic
-
-[Aerobatic](https://www.aerobatic.com) has custom domains, global CDN distribution, basic auth, CORS proxying, and a growing list of plugins all included.
-
-Automating the deployment of a Jekyll site is simple. See their [Jekyll docs](https://www.aerobatic.com/docs/static-site-generators/#jekyll) for more details. Your built `_site` folder is deployed to their highly-available, globally distributed hosting service.
 
 ## AWS Amplify
 
 The [AWS Amplify Console](https://console.amplify.aws) provides continuous deployment and hosting for modern web apps (single page apps and static site generators). Continuous deployment allows developers to deploy updates to their web app on every code commit to their Git repository. Hosting includes features such as globally available CDNs, 1-click custom domain setup + HTTPS, feature branch deployments, redirects, trailing slashes, and password protection.
 
-Read this [step-by-step guide](https://medium.com/@FizzyInTheHall/build-and-publish-a-jekyll-powered-blog-easily-with-aws-amplify-529852042ab6) to deploy and host your Jekyll site on AWS Amplify.
+Read this [step-by-step guide](https://medium.com/@jameshamann/deploy-your-jekyll-site-using-aws-amplify-with-only-a-few-clicks-8f3dd8f26112) to deploy and host your Jekyll site on AWS Amplify.
+
+## Bip
+
+[Bip](https://bip.sh) provides zero downtime deployment, a global CDN, SSL, unlimited bandwidth and more for Jekyll websites. Deploy in seconds from the command line. [Visit the Bip website](https://bip.sh) for more information - which is also built with Jekyll.
 
 ## CloudCannon
 
@@ -25,6 +24,15 @@ continuous deployment and [more](https://cloudcannon.com/features/).
 
 Sites on GitHub Pages are powered by Jekyll behind the scenes, so if you’re looking for a zero-hassle, zero-cost solution, GitHub Pages are a great way to [host your Jekyll-powered website for free](/docs/github-pages/).
 
+## GitLab Pages
+
+[GitLab Pages](https://about.gitlab.com/stages-devops-lifecycle/pages/) offers free hosting with custom domains. [Get started with Jekyll](https://docs.gitlab.com/ee/user/project/pages/getting_started_part_four.html#practical-example) and a fully customizable pipeline.
+
+## KeyCDN
+
+[KeyCDN](https://www.keycdn.com) accelerates Jekyll-powered websites with a wide range of other features such as real time image processing including WebP transformation.  
+The [Jekyll hosting tutorial](https://www.keycdn.com/support/jekyll-hosting) provides various options to supercharge Jekyll sites with just a few steps. It combines best flexibility and excellent performance.
+
 ## Kickster
 
 Use [Kickster](http://kickster.nielsenramon.com/) for automated deploys to GitHub Pages when using unsupported plugins on GitHub Pages.
@@ -33,13 +41,34 @@ Kickster provides a basic Jekyll project setup packed with web best practises an
 
 Install the Kickster gem and you are good to go. More documentation can here found [here](https://github.com/nielsenramon/kickster#kickster). If you do not want to use the gem or start a new project you can just copy paste the deployment scripts for [Travis CI](https://github.com/nielsenramon/kickster/tree/master/snippets/travis) or [Circle CI](https://github.com/nielsenramon/kickster#automated-deployment-with-circle-ci).
 
-
 ## Netlify
 
-Netlify provides Global CDN, Continuous Deployment, one click HTTPS and [much more](https://www.netlify.com/features/), providing developers the most robust toolset available for modern web projects, without added complexity. Netlify supports custom plugins for Jekyll and has a free plan for open source projects.
+Netlify provides Global CDN, Continuous Deployment, one click HTTPS and [much more](https://www.netlify.com/features/), providing developers a robust toolset for modern web projects, without added complexity. Netlify supports custom plugins for Jekyll and has a free plan for open source projects.
 
-Read this [Jekyll step-by-step guide](https://www.netlify.com/blog/2015/10/28/a-step-by-step-guide-jekyll-3.0-on-netlify/) to setup your Jekyll site on Netlify.
+Read this [Jekyll step-by-step guide](https://www.netlify.com/blog/2020/04/02/a-step-by-step-guide-jekyll-4.0-on-netlify/) to setup your Jekyll site on Netlify.
+
+## Render
+
+[Render](https://render.com) provides zero config continuous deployment for static sites. The service is free under 100GB monthly bandwidth.
+
+## Hostman 
+
+[Hostman](https://hostman.com) allows you to host websites for free with no configurations. Read [this guide](https://hostman.com/docs/jekyll) to deploy your Jekyll site on Hostman. 
 
 ## Static Publisher
 
 [Static Publisher](https://github.com/static-publisher/static-publisher) is another automated deployment option with a server listening for webhook posts, though it's not tied to GitHub specifically. It has a one-click deploy to Heroku, it can watch multiple projects from one server, it has an easy to user admin interface and can publish to either S3 or to a git repository (e.g. gh-pages).
+
+## Vercel
+
+[Vercel](https://vercel.com/) provides zero config continuous deployment, HTTPS Custom domains, high performance smart CDN, you get instant static deploy for free.
+
+## 21YunBox
+
+[21YunBox](https://www.21yunbox.com) provides blazing fast Chinese CDN, Continuous Deployment, one click HTTPS and [much more](https://www.21yunbox.com/docs/), providing developers a hassle-free solution to launch their web projects in China.
+
+Read this [Jekyll step-by-step guide](https://www.21yunbox.com/docs/#/deploy-jekyll) to deploy your Jekyll site on 21YunBox.
+
+## Layer0
+
+[Layer0](https://www.layer0.co) is an all-in-one platform to develop, deploy, preview, experiment on, monitor, and run your headless frontend. It is focused on large, dynamic websites and best-in-class performance through EdgeJS (a JavaScript-based Content Delivery Network), predictive prefetching, and performance monitoring. Layer0 offers a free tier. Get started in just a few minutes by following [Layer0's guide to deploying Jekyll](https://docs.layer0.co/guides/jekyll).

docs/_docs/front-matter.md

@@ -18,7 +18,7 @@ title: Blogging Like a Hacker
 
 Between these triple-dashed lines, you can set predefined variables (see below
 for a reference) or even create custom ones of your own. These variables will
-then be available to you to access using Liquid tags both further down in the
+then be available for you to access using Liquid tags both further down in the
 file and also in any layouts or includes that the page or post in question
 relies on.
 
@@ -28,14 +28,14 @@ relies on.
     If you use UTF-8 encoding, make sure that no <code>BOM</code> header
     characters exist in your files or very, very bad things will happen to
     Jekyll. This is especially relevant if you’re running
-    <a href="/docs/installation/windows/">Jekyll on Windows</a>.
+    <a href="{{ '/docs/installation/windows/' | relative_url }}">Jekyll on Windows</a>.
   </p>
 </div>
 
 <div class="note">
   <h5>Front Matter Variables Are Optional</h5>
   <p>
-    If you want to use <a href="/docs/variables/">Liquid tags and variables</a>
+    If you want to use <a href="{{ '/docs/variables/' | relative_url }}">Liquid tags and variables</a>
     but don’t need anything in your front matter, just leave it empty! The set
     of triple-dashed lines with nothing in between will still get Jekyll to
     process your file. (This is useful for things like CSS and RSS feeds!)
@@ -72,7 +72,7 @@ front matter of a page or post.
           <li>
             Using <code>null</code> will produce a file without using a layout
             file. This is overridden if the file is a post/document and has a
-            layout defined in the <a href="/docs/configuration/front-matter-defaults/">
+            layout defined in the <a href="{{ '/docs/configuration/front-matter-defaults/' | relative_url }}">
             front matter defaults</a>.
           </li>
           <li>
@@ -117,7 +117,7 @@ front matter of a page or post.
   <h5>Render Posts Marked As Unpublished</h5>
   <p>
     To preview unpublished pages, run `jekyll serve` or `jekyll build`
-    with the `--unpublished` switch. Jekyll also has a handy <a href="/docs/posts/#drafts">drafts</a>
+    with the `--unpublished` switch. Jekyll also has a handy <a href="{{ '/docs/posts/#drafts' | relative_url }}">drafts</a>
     feature tailored specifically for blog posts.
   </p>
 </div>
@@ -204,7 +204,8 @@ These are available out-of-the-box to be used in the front matter for a post.
   <h5>Don't repeat yourself</h5>
   <p>
     If you don't want to repeat your frequently used front matter variables
-    over and over, define <a href="/docs/configuration/front-matter-defaults/" title="Front Matter defaults">defaults</a>
+    over and over, define
+    <a href="{{ '/docs/configuration/front-matter-defaults/' | relative_url }}" title="Front Matter defaults">defaults</a>
     for them and only override them where necessary (or not at all). This works
     both for predefined and custom variables.
   </p>

docs/_docs/github-pages.md

@@ -15,40 +15,20 @@ simply because Jekyll treats files without 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 Documentation](https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages)
+is comprehensive and includes a [a guide to setting up a GitHub Pages site using
+Jekyll](https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll).
+We recommend following this guide.
 
-##  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.
+This page contains some additional information which may be useful when working
+on GitHub Pages sites with Jekyll.
 
 <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>.
+    <a href="https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages">GitHub’s Pages Help section</a>.
     If all else fails, you should contact <a href="https://github.com/contact">GitHub Support</a>.
   </p>
 </div>
@@ -58,12 +38,12 @@ Be sure to run `bundle update` often.
 Sometimes it's nice to preview your Jekyll site before you push your `gh-pages`
 branch to GitHub. 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](/docs/liquid/filters/):
+site builds properly, use the handy [URL filters]({{ '/docs/liquid/filters/' | relative_url }}):
 
 {% raw %}
 ```liquid
 <!-- For styles with static names... -->
-<link href="{{ "/assets/css/style.css" | relative_url }}" rel="stylesheet">
+<link href="{{ 'assets/css/style.css' | relative_url }}" rel="stylesheet">
 <!-- For documents/pages whose URLs can change... -->
 [{{ page.title }}]("{{ page.url | relative_url }}")
 ```
@@ -76,7 +56,7 @@ 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/).
+There are two basic types available: [user/organization and project pages](https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites).
 The way to deploy these two types of sites are nearly identical, except for a
 few minor details.
 
@@ -115,14 +95,14 @@ 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/)
+[user, organization and project pages](https://docs.github.com/en/free-pro-team@latest/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)
 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/options/">“Site Source”</a>
+    GitHub Pages <a href="https://help.github.com/en/github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites">overrides</a>
+    the <a href="{{ '/docs/configuration/options/' | relative_url }}">“Site Source”</a>
     configuration value, so if you locate your files anywhere other than the
     root directory, your site may not build correctly.
   </p>
@@ -135,6 +115,17 @@ to see more detailed examples.
     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="/docs/installation/windows/">Windows-specific docs page</a>.
+    <a href="{{ '/docs/installation/windows/' | relative_url }}">Windows-specific docs page</a>.
   </p>
 </div>
+
+### Running and Testing Locally
+
+Once the project is configured with the github-pages environment, it's quite hard to switch back and forth with the local settings and the production-level settings. For that we can use certain CLI options to make the workflow hassle-free.  
+
+```sh
+bundle exec jekyll serve --baseurl=""
+```
+
+This will run the jekyll server on your local machine i.e. on `http://localhost:4000`. Refer <a href="{{ '/docs/configuration/options/#serve-command-options' | relative_url }}">server options</a> for available options.
+

docs/_docs/history.md

@@ -4,6 +4,333 @@ permalink: "/docs/history/"
 note: This file is autogenerated. Edit /History.markdown instead.
 ---
 
+## 4.2.2 / 2022-03-03
+{: #v4-2-2}
+
+### Bug Fixes
+{: #bug-fixes-v4-2-2}
+
+- Lock `http_parser.rb` gem to `v0.6.x` on JRuby.
+
+### Development Fixes
+{: #development-fixes-v4-2-2}
+
+- Backport [#8830]({{ site.repository }}/issues/8830) for v4.2.x: Add a workflow to build gems consistently ([#8869]({{ site.repository }}/issues/8869))
+- Lock `rubocop-performance` to `v1.11.x`.
+
+
+## 4.2.1 / 2021-09-27
+{: #v4-2-1}
+
+### Bug Fixes
+{: #bug-fixes-v4-2-1}
+
+- Backport [#8620]({{ site.repository }}/issues/8620) for v4.2.x: Revert [#7253]({{ site.repository }}/issues/7253): "Don't reset site.url to localhost:4000 by default" ([#8808]({{ site.repository }}/issues/8808))
+- Backport [#8756]({{ site.repository }}/issues/8756) for v4.2.x: Respect collections_dir config within include tag ([#8794]({{ site.repository }}/issues/8794))
+- Backport [#8786]({{ site.repository }}/issues/8786) for v4.2.x: Fix regression in Convertible module from v4.2.0 ([#8793]({{ site.repository }}/issues/8793))
+
+
+## 4.2.0 / 2020-12-14
+{: #v4-2-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v4-2-0}
+
+- Warn on command-line with permalink conflict ([#8342]({{ site.repository }}/issues/8342))
+- Suppress warning issued for redirect pages ([#8347]({{ site.repository }}/issues/8347))
+- Enhance detection of conflicting destination URLs ([#8459]({{ site.repository }}/issues/8459))
+- Add `:post_convert` hook to modify HTML content before layout ([#8368]({{ site.repository }}/issues/8368))
+- Allow triggering `:post_convert` events atomically ([#8465]({{ site.repository }}/issues/8465))
+- Debug reading Page and Layout objects ([#8100]({{ site.repository }}/issues/8100))
+- Do not reset `site.url` to `http://localhost:4000` by default ([#7253]({{ site.repository }}/issues/7253))
+- Add custom debug strings for Jekyll objects ([#8473]({{ site.repository }}/issues/8473))
+- Debug reading data files in a site ([#8481]({{ site.repository }}/issues/8481))
+
+### Bug Fixes
+{: #bug-fixes-v4-2-0}
+
+- Replace nested conditional with guard clauses ([#8294]({{ site.repository }}/issues/8294))
+- Fix: security bump ([#8349]({{ site.repository }}/issues/8349))
+- Fix path matching regex in post_url Liquid tag ([#8375]({{ site.repository }}/issues/8375))
+- Enable `Performance/ChainArrayAllocation` cop ([#8404]({{ site.repository }}/issues/8404))
+- Enable Lint/NoReturnInBeginEndBlocks Cop ([#8457]({{ site.repository }}/issues/8457))
+- Generate items from `site.include` list only once ([#8463]({{ site.repository }}/issues/8463))
+- Explicitly return nil after site process phase ([#8472]({{ site.repository }}/issues/8472))
+
+### Optimization Fixes
+{: #optimization-fixes-v4-2-0}
+
+- Implement custom delegators for drop methods ([#8183]({{ site.repository }}/issues/8183))
+- Handle `nil` argument to `Jekyll.sanitized_path` ([#8415]({{ site.repository }}/issues/8415))
+- Cache `Jekyll.sanitized_path` ([#8424]({{ site.repository }}/issues/8424))
+- Memoize array of drop getter method names ([#8421]({{ site.repository }}/issues/8421))
+- Reduce string allocations from the `link` tag ([#8387]({{ site.repository }}/issues/8387))
+- Optimize parsing of parameters in `include` tag ([#8192]({{ site.repository }}/issues/8192))
+- Stash documents `write?` attribute in a variable ([#8389]({{ site.repository }}/issues/8389))
+- Reduce string allocations from generating doc URLs ([#8392]({{ site.repository }}/issues/8392))
+- Check if site is in incremental mode optimally ([#8401]({{ site.repository }}/issues/8401))
+- Utilize flexibility of `Site#in_dest_dir` ([#8403]({{ site.repository }}/issues/8403))
+- Reduce allocations from rendering item as liquid ([#8406]({{ site.repository }}/issues/8406))
+- Compute relative_path of pages using PathManager ([#8408]({{ site.repository }}/issues/8408))
+- Reduce allocation from `normalize_whitespace` filter ([#8400]({{ site.repository }}/issues/8400))
+- Use `Regexp#match?` when `MatchData` is not required ([#8427]({{ site.repository }}/issues/8427))
+- Check default front matter scope against symbols ([#8393]({{ site.repository }}/issues/8393))
+- Stash frequently used `Drop` setter keys for reuse ([#8394]({{ site.repository }}/issues/8394))
+- Memoize defaults computed for Convertibles ([#8451]({{ site.repository }}/issues/8451))
+- Reduce array allocations from merging categories ([#8453]({{ site.repository }}/issues/8453))
+- Memoize destination of pages, documents and staticfiles ([#8458]({{ site.repository }}/issues/8458))
+- Reduce allocations from computing item property ([#8485]({{ site.repository }}/issues/8485))
+- Optimize `Page#dir` with a private method ([#8489]({{ site.repository }}/issues/8489))
+- Stash attribute hash for Liquid computed for pages ([#8497]({{ site.repository }}/issues/8497))
+
+### Development Fixes
+{: #development-fixes-v4-2-0}
+
+- Update cucumber gem to version 4.1 ([#8278]({{ site.repository }}/issues/8278))
+- Move permalink styles data to constant ([#8282]({{ site.repository }}/issues/8282))
+- Update rubocop gem to 0.87.1 ([#8287]({{ site.repository }}/issues/8287))
+- Update RuboCop to-do file ([#8296]({{ site.repository }}/issues/8296))
+- Fix `rake console` generating LoadError ([#8312]({{ site.repository }}/issues/8312))
+- Configure Performance cops ([#8369]({{ site.repository }}/issues/8369))
+- Update rubocop gem to 0.90.0 ([#8313]({{ site.repository }}/issues/8313))
+- Refactor `Jekyll::Utils::Platforms` ([#7236]({{ site.repository }}/issues/7236))
+- Bump RuboCop to v0.91.x ([#8391]({{ site.repository }}/issues/8391))
+- Add workflow to build and profile third-party repo ([#8398]({{ site.repository }}/issues/8398))
+- Bump RuboCop to v0.92.x
+- Update cucumber gem version to 5.1.2 ([#8413]({{ site.repository }}/issues/8413))
+- Fix test suite compatibility with JRuby ([#8418]({{ site.repository }}/issues/8418))
+- chore(deps): bump Rubocop to 0.93.0 ([#8430]({{ site.repository }}/issues/8430))
+- Use Ruby 2.7.1 in GitHub Actions ([#8444]({{ site.repository }}/issues/8444))
+- Test that Liquid expressions are not deeply evaled ([#8292]({{ site.repository }}/issues/8292))
+- Test rendering arbitrary Liquid variables by default ([#7414]({{ site.repository }}/issues/7414))
+- Migrate TravisCI jobs to GitHub Actions ([#8492]({{ site.repository }}/issues/8492))
+
+### Documentation
+
+- Update pointer to special permalink variables for collections ([#8274]({{ site.repository }}/issues/8274))
+- Fix special treatment for 'page 1' in docs of pagination ([#8230]({{ site.repository }}/issues/8230))
+- Add Formcake to forms section ([#8283]({{ site.repository }}/issues/8283))
+- Add a note on the rendering process in the docs ([#8291]({{ site.repository }}/issues/8291))
+- Add refactoring type to PULL_REQUEST_TEMPLATE ([#8297]({{ site.repository }}/issues/8297))
+- Update resources.md ([#7864]({{ site.repository }}/issues/7864))
+- Extra apostrophes in an URL ([#8319]({{ site.repository }}/issues/8319))
+- Clarify target of subordinate clause ([#8320]({{ site.repository }}/issues/8320))
+- Cherry-pick commits from conflicting branch `docs-40`
+- Update documentation on third party site ([#8352]({{ site.repository }}/issues/8352))
+- Update default.md with info requested in [#8314]({{ site.repository }}/issues/8314) ([#8353]({{ site.repository }}/issues/8353))
+- Clarify description of `safe` option ([#8354]({{ site.repository }}/issues/8354))
+- Simplifying the Git post-receive hook-example ([#8358]({{ site.repository }}/issues/8358))
+- Add missing doc for build and serve commands ([#8365]({{ site.repository }}/issues/8365))
+- Docs Review: Getting Started ([#8372]({{ site.repository }}/issues/8372))
+- Add note about rebooting system after installation ([#8359]({{ site.repository }}/issues/8359))
+- Use data file to render table at `/docs/configuration/options/#global-configuration` ([#8377]({{ site.repository }}/issues/8377))
+- Use data file(s) to render table(s) at `/docs/configuration/options/` ([#8380]({{ site.repository }}/issues/8380))
+- Improve maintainability of config option data ([#8383]({{ site.repository }}/issues/8383))
+- Remove CircleCI v1 docs ([#8410]({{ site.repository }}/issues/8410))
+- Remove `NOKOGIRI_USE_SYSTEM_LIBRARIES` from Travis CI docs ([#8409]({{ site.repository }}/issues/8409))
+- Add links to all Jekyll themes on GitHub tagged with #jekyll-theme ([#8447]({{ site.repository }}/issues/8447))
+- Document initializing project Gemfile from scratch ([#8450]({{ site.repository }}/issues/8450))
+- Document installation of additional dependencies for installing Jekyll on Fedora ([#8456]({{ site.repository }}/issues/8456))
+- Improve documentation on Hooks in Jekyll ([#8467]({{ site.repository }}/issues/8467))
+- Build docs site with GitHub Actions ([#8201]({{ site.repository }}/issues/8201))
+- Add link to Assets page from `_sass` section in `_docs/structure.md` ([#8486]({{ site.repository }}/issues/8486))
+
+### Site Enhancements
+{: #site-enhancements-v4-2-0}
+
+- Fix rendering of *showcase* images ([#8504]({{ site.repository }}/issues/8504))
+
+
+## 4.1.1 / 2020-06-24
+{: #v4-1-1}
+
+### Bug Fixes
+{: #bug-fixes-v4-1-1}
+
+- Disable page excerpts by default ([#8222]({{ site.repository }}/issues/8222))
+- Revert introduction of PageDrop ([#8221]({{ site.repository }}/issues/8221))
+- Don't generate excerpts for non-html pages ([#8234]({{ site.repository }}/issues/8234))
+- Make page excerpts consistent with doc excerpts ([#8236]({{ site.repository }}/issues/8236))
+
+### Documentation
+
+- Replace deprecated 'show' command with 'info' ([#8235]({{ site.repository }}/issues/8235))
+- Change name to ▲Vercel ([#8247]({{ site.repository }}/issues/8247))
+- Add language and examples to describe how to use the configuration op… ([#8249]({{ site.repository }}/issues/8249))
+- Fix missing yaml front matter colon and adjust/add clarifying language. ([#8250]({{ site.repository }}/issues/8250))
+- correct typo ([#8261]({{ site.repository }}/issues/8261))
+- Allow hyperlinks to specific filter documentation ([#8231]({{ site.repository }}/issues/8231))
+- Update link to Netlify step-by-step guide ([#8264]({{ site.repository }}/issues/8264))
+- Fix grammar in documentation section ([#8265]({{ site.repository }}/issues/8265))
+
+### Site Enhancements
+{: #site-enhancements-v4-1-1}
+
+- Including correct Sketch website ([#8241]({{ site.repository }}/issues/8241))
+- Release post for v4.1.1 ([#8243]({{ site.repository }}/issues/8243))
+
+### Development Fixes
+{: #development-fixes-v4-1-1}
+
+- Bump RuboCop to v0.85.x ([#8223]({{ site.repository }}/issues/8223))
+- Expect drive letter only on vanilla windows ([#8227]({{ site.repository }}/issues/8227))
+
+
+## 4.1.0 / 2020-05-27
+{: #v4-1-0}
+
+### Bug Fixes
+{: #bug-fixes-v4-1-0}
+
+- Memoize `absolute_url` and `relative_url` filters ([#7793]({{ site.repository }}/issues/7793))
+- Fix documentation comment for `Jekyll::Converters::Identity` ([#7883]({{ site.repository }}/issues/7883))
+- Optimize `Jekyll::Filters#item_property` ([#7696]({{ site.repository }}/issues/7696))
+- Allow multiple binary operators in `where_exp` filter ([#8047]({{ site.repository }}/issues/8047))
+- Fix documents custom-ordering logic ([#8028]({{ site.repository }}/issues/8028))
+- Use `layout.path` when rendering the Liquid layout ([#8069]({{ site.repository }}/issues/8069))
+- Reduce array allocations from `StaticFile#path` ([#8083]({{ site.repository }}/issues/8083))
+- Simplify `Jekyll::Renderer#validate_layout` ([#8064]({{ site.repository }}/issues/8064))
+- Add static file's basename to its `url_placeholder` ([#7908]({{ site.repository }}/issues/7908))
+- Clear cached Liquid template scope before render ([#7967]({{ site.repository }}/issues/7967))
+- Cache `URLFilter` results of string inputs per site ([#7990]({{ site.repository }}/issues/7990))
+- Use `platforms` instead of `install_if` in Gemfile ([#8140]({{ site.repository }}/issues/8140))
+- Config include trailing slash ([#8113]({{ site.repository }}/issues/8113))
+- Improve path normalization in liquid_renderer ([#8075]({{ site.repository }}/issues/8075))
+- Switch slugify regex to support more Unicode character groups ([#8167]({{ site.repository }}/issues/8167))
+- Check if entry is a directory once per enumerator ([#8177]({{ site.repository }}/issues/8177))
+- Filter out exclusively excluded entries sooner ([#7482]({{ site.repository }}/issues/7482))
+- Return `relative_url` if site.url is an empty string ([#7988]({{ site.repository }}/issues/7988))
+- Configure kramdown toc_levels as array by default ([#8015]({{ site.repository }}/issues/8015))
+- Reduce `Pathname` objects from front matter defaults ([#8067]({{ site.repository }}/issues/8067))
+- Simplify `Jekyll::Hooks.trigger` logic ([#8044]({{ site.repository }}/issues/8044))
+- Quicker categories for documents without superdirs ([#7987]({{ site.repository }}/issues/7987))
+- Reduce `Jekyll::Renderer` instances during a build ([#7570]({{ site.repository }}/issues/7570))
+- Escape regex characters in paths to match ([#8138]({{ site.repository }}/issues/8138))
+- Provide invokables for common drop query keys ([#8165]({{ site.repository }}/issues/8165))
+- Optimize path sanitization of default front matter ([#8154]({{ site.repository }}/issues/8154))
+- Initialize static files' data hash only if needed ([#8188]({{ site.repository }}/issues/8188))
+- Initialize include-files as Jekyll objects ([#8158]({{ site.repository }}/issues/8158))
+
+### Minor Enhancements
+{: #minor-enhancements-v4-1-0}
+
+- serve: add support for ECC certificates ([#7768]({{ site.repository }}/issues/7768))
+- Update `item_property` to recognize integers ([#7878]({{ site.repository }}/issues/7878))
+- Include `_config.yml` in a new theme's gemspec ([#7865]({{ site.repository }}/issues/7865))
+- Add an option to easily disable disk-cache ([#7928]({{ site.repository }}/issues/7928))
+- Optimize markdown parsing with Kramdown by reusing the options and parser objects ([#8013]({{ site.repository }}/issues/8013))
+- Add `PageDrop` to provide Liquid templates with data ([#7992]({{ site.repository }}/issues/7992))
+- Optimize `Kramdown::JekyllDocument#to_html` calls ([#8041]({{ site.repository }}/issues/8041))
+- Configure default language for syntax-highlighting ([#8035]({{ site.repository }}/issues/8035))
+- Remove dev dependencies from new theme-gem gemspec ([#8042]({{ site.repository }}/issues/8042))
+- Allow disabling import of theme configuration ([#8131]({{ site.repository }}/issues/8131))
+- Allow excerpts to be generated for `Page` objects ([#7642]({{ site.repository }}/issues/7642))
+- Profile various stages of a site's build process ([#6760]({{ site.repository }}/issues/6760))
+- Add find filters to optimize where-first chains ([#8171]({{ site.repository }}/issues/8171))
+- Make `number_of_words` filter respect CJK characters ([#7813]({{ site.repository }}/issues/7813))
+- Allow extensionless document in a strict site ([#7950]({{ site.repository }}/issues/7950))
+- Add `:slugified_categories` URL placeholder ([#8094]({{ site.repository }}/issues/8094))
+
+### Documentation
+
+- Add dropped 'title: Staff' to the code ([#7805]({{ site.repository }}/issues/7805))
+- Clarify docs for static files in collection ([#7812]({{ site.repository }}/issues/7812))
+- Rephrase the CircleCI v2 section ([#7815]({{ site.repository }}/issues/7815))
+- Update old GitHub wiki URL with new one ([#7823]({{ site.repository }}/issues/7823))
+- Update JekyllConf page with 2019 talks ([#7826]({{ site.repository }}/issues/7826))
+- link for memberships ([#7825]({{ site.repository }}/issues/7825))
+- Doc: minor fix, should be greater or equal to min version ([#7856]({{ site.repository }}/issues/7856))
+- Update third-party.md - Fix broken link ([#7857]({{ site.repository }}/issues/7857))
+- clarify _config.yml/collections type ([#7873]({{ site.repository }}/issues/7873))
+- Replace backticks with HTML tags in data file ([#7879]({{ site.repository }}/issues/7879))
+- add new theme source ([#7875]({{ site.repository }}/issues/7875))
+- fixed grammatical error (it's --> its) ([#7887]({{ site.repository }}/issues/7887))
+- Docs: Clarify organizing pages into subfolders ([#7896]({{ site.repository }}/issues/7896))
+- Disambiguate the placeholder of permalink ([#7906]({{ site.repository }}/issues/7906))
+- docs: add short serve command for livereload ([#7919]({{ site.repository }}/issues/7919))
+- docs: add options for watch and force polling ([#7918]({{ site.repository }}/issues/7918))
+- add install instructions for ArchLinux and openSUSE ([#7920]({{ site.repository }}/issues/7920))
+- Improve index page of Jekyll documentation  ([#7926]({{ site.repository }}/issues/7926))
+- Include path in `jekyll new` commands (Usage docs) ([#7931]({{ site.repository }}/issues/7931))
+- Change `affect` to `effect` in the collections docs ([#7937]({{ site.repository }}/issues/7937))
+- Changed deprecated command in themes documentation ([#7941]({{ site.repository }}/issues/7941))
+- Adds some documentation for the `:clean`, `:on_obsolete` hook ([#7954]({{ site.repository }}/issues/7954))
+- docs: fix broken link ([#7955]({{ site.repository }}/issues/7955))
+- Corrected typo ([#7975]({{ site.repository }}/issues/7975))
+- docs: remove watch option in config ([#7940]({{ site.repository }}/issues/7940))
+- Correct a sentence in the documentation ([#7978]({{ site.repository }}/issues/7978))
+- Fix YAML representation of `group_by` result ([#7979]({{ site.repository }}/issues/7979))
+- Move `--baseurl` to build command options ([#7985]({{ site.repository }}/issues/7985))
+- Correct documentation of filters ([#7989]({{ site.repository }}/issues/7989))
+- Document sorting two documents by their `date` ([#7870]({{ site.repository }}/issues/7870))
+- Fix English grammar error ([#7994]({{ site.repository }}/issues/7994))
+- Update 03-front-matter.md ([#7996]({{ site.repository }}/issues/7996))
+- Add Kentico Kontent CMS integration to resources ([#8000]({{ site.repository }}/issues/8000))
+- Update 07-assets.md ([#7413]({{ site.repository }}/issues/7413))
+- Fix file references in Step by Step Tutorial's Assets step ([#8007]({{ site.repository }}/issues/8007))
+- docs: improve highlighting of code blocks ([#8017]({{ site.repository }}/issues/8017))
+- remove leading slash from Sass file location ([#8021]({{ site.repository }}/issues/8021))
+- [Docs] Fix asset link ref in step-by-step tutorial ([#8026]({{ site.repository }}/issues/8026))
+- Corrected command to modify PATH ([#8029]({{ site.repository }}/issues/8029))
+- Corrected command to modify PATH ([#8030]({{ site.repository }}/issues/8030))
+- Docs: Render full contents of just the latest post ([#8032]({{ site.repository }}/issues/8032))
+- docs: improvements for note boxes ([#8037]({{ site.repository }}/issues/8037))
+- Non-deprecated `vendor/bundle` path configuration ([#8048]({{ site.repository }}/issues/8048))
+- Update 09-collections.md ([#8060]({{ site.repository }}/issues/8060))
+- Remove extra paragraph tags ([#8063]({{ site.repository }}/issues/8063))
+- Add default front matter for tutorials collection ([#8081]({{ site.repository }}/issues/8081))
+- Create CSV to table tutorial ([#8090]({{ site.repository }}/issues/8090))
+- Add version badge for Custom Sorting of Documents ([#8098]({{ site.repository }}/issues/8098))
+- Docs: Fix grammar in `_docs/front-matter.md` ([#8097]({{ site.repository }}/issues/8097))
+- Update variables.md ([#8106]({{ site.repository }}/issues/8106))
+- Add help about Gentoo/Linux ([#8002]({{ site.repository }}/issues/8002))
+- Update documentation on third party site ([#8122]({{ site.repository }}/issues/8122))
+- Added Clear Linux ([#8132]({{ site.repository }}/issues/8132))
+- Added note about OS specific installation instructions. ([#8135]({{ site.repository }}/issues/8135))
+- Fix broken URL in the Resources Page on the Documentation Site ([#8136]({{ site.repository }}/issues/8136))
+- Docs: Deploy Jekyll site with GitHub Actions ([#8119]({{ site.repository }}/issues/8119))
+- Clarify `bundle config` in Bundler tutorial ([#8150]({{ site.repository }}/issues/8150))
+- docs: update your-first-plugin.md ([#8147]({{ site.repository }}/issues/8147))
+- Fix typo in documentation on GitHub Actions ([#8162]({{ site.repository }}/issues/8162))
+- Ease discovery of CLI commands (in their entirety) ([#8178]({{ site.repository }}/issues/8178))
+- Remove `sudo` from Travis CI tutorial ([#8187]({{ site.repository }}/issues/8187))
+- Add GitLab Pages to 3rd party list ([#8191]({{ site.repository }}/issues/8191))
+- docs: add 21yunbox for deployment ([#8193]({{ site.repository }}/issues/8193))
+- Improve documentation on tags and categories ([#8196]({{ site.repository }}/issues/8196))
+
+### Development Fixes
+{: #development-fixes-v4-1-0}
+
+- Ci/GitHub actions ([#7822]({{ site.repository }}/issues/7822))
+- Rubocop version upgrade ([#7846]({{ site.repository }}/issues/7846))
+- Split action steps to avoid using `&&` on Windows ([#7885]({{ site.repository }}/issues/7885))
+- Upgrade rake to use version 13 ([#7910]({{ site.repository }}/issues/7910))
+- Update dependency constraint to allow RuboCop v0.76 ([#7893]({{ site.repository }}/issues/7893))
+- Use bash executable consistently ([#7909]({{ site.repository }}/issues/7909))
+- Test with JRuby 9.2.9.0 ([#7779]({{ site.repository }}/issues/7779))
+- Bump RuboCop to v0.79.x ([#7970]({{ site.repository }}/issues/7970))
+- Remove post-install message from gemspec ([#7974]({{ site.repository }}/issues/7974))
+- Attain Ruby 3.0 compatibility ([#7948]({{ site.repository }}/issues/7948))
+- Test `where` filter handling numeric property values ([#7821]({{ site.repository }}/issues/7821))
+- chore(deps): rubocop 0.80.0 ([#8012]({{ site.repository }}/issues/8012))
+- Update unit tests for Kramdown-based converter ([#8014]({{ site.repository }}/issues/8014))
+- Add Visual Studio Code Development Container ([#8016]({{ site.repository }}/issues/8016))
+- chore: simplify require for `Jekyll::VERSION` ([#8057]({{ site.repository }}/issues/8057))
+- Remove version-constraint relaxation for i18n gem ([#8055]({{ site.repository }}/issues/8055))
+- Mirror `spec.homepage` as `metadata["homepage_uri"]` ([#8056]({{ site.repository }}/issues/8056))
+- Bump Ruby versions on Travis builds ([#8088]({{ site.repository }}/issues/8088))
+- chore(ci): cache dependencies ([#8168]({{ site.repository }}/issues/8168))
+
+### Site Enhancements
+{: #site-enhancements-v4-1-0}
+
+- Optimize rendering of the documentation site ([#8020]({{ site.repository }}/issues/8020))
+- Utilize `relative_url` filter in documentation site ([#8089]({{ site.repository }}/issues/8089))
+- Render tutorial metadata in documentation site ([#8092]({{ site.repository }}/issues/8092))
+- Improve syntax-highlighting in documentation site ([#8079]({{ site.repository }}/issues/8079))
+- Site: Filter through just the *docs* collection ([#8170]({{ site.repository }}/issues/8170))
+
+
 ## 4.0.1 / 2020-05-08
 {: #v4-0-1}
 
@@ -21,6 +348,51 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Fix Kramdown converter based tests for v4.0.x ([#8143]({{ site.repository }}/issues/8143))
 
 
+## 3.9.2 / 2022-03-27
+{: #v3-9-2}
+
+### Bug Fixes
+{: #bug-fixes-v3-9-2}
+
+- Lock `http_parser.rb` gem to `v0.6.x` on JRuby ([#8943]({{ site.repository }}/issues/8943))
+- Backport [#8756]({{ site.repository }}/issues/8756) for v3.9.x: Respect collections_dir config within include tag ([#8795]({{ site.repository }}/issues/8795))
+- Backport [#8965]({{ site.repository }}/issues/8965) for v3.9.x: Fix response header for content served via `jekyll serve` ([#8976]({{ site.repository }}/issues/8976))
+
+### Development Fixes
+{: #development-fixes-v3-9-2}
+
+- Update and fix CI for `3.9-stable` on Ruby 3.x ([#8942]({{ site.repository }}/issues/8942))
+- Fix CI for commits to `3.9-stable` branch ([#8788]({{ site.repository }}/issues/8788))
+
+
+## 3.9.1 / 2021-04-08
+{: #v3-9-1}
+
+### Bug Fixes
+{: #bug-fixes-v3-9-1}
+
+- Backport [#8618]({{ site.repository }}/issues/8618) for v3.9.x: Update include tag to be more permissive ([#8629]({{ site.repository }}/issues/8629))
+
+
+## 3.9.0 / 2020-08-05
+{: #v3-9-0}
+
+### Minor Enhancements
+{: #minor-enhancements-v3-9-0}
+
+- Allow use of kramdown v2 ([#8322]({{ site.repository }}/issues/8322))
+- Add default language for kramdown syntax highlighting ([#8325]({{ site.repository }}/issues/8325))
+
+
+## 3.8.7 / 2020-05-08
+{: #v3-8-7}
+
+### Bug Fixes
+{: #bug-fixes-v3-8-7}
+
+- Prevent console warnings with Ruby 2.7 ([#8125]({{ site.repository }}/issues/8125))
+
+
 ## 4.0.0 / 2019-08-19
 {: #v4-0-0}
 
@@ -276,7 +648,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Remove alt attribute from a tags ([#7407]({{ site.repository }}/issues/7407))
 - Fix BASH code-block in ubuntu.md ([#7420]({{ site.repository }}/issues/7420))
 - zlib is missing ([#7428]({{ site.repository }}/issues/7428))
-- Fixed unnecessary aticles and pronouns ([#7466]({{ site.repository }}/issues/7466))
+- Fixed unnecessary articles and pronouns ([#7466]({{ site.repository }}/issues/7466))
 - Store SSL key and cert in site source ([#7473]({{ site.repository }}/issues/7473))
 - Fix typo in tutorial for converting existing site ([#7524]({{ site.repository }}/issues/7524))
 - Check if var exists before include tag ([#7530]({{ site.repository }}/issues/7530))
@@ -291,7 +663,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - fix link to Site Source config ([#7708]({{ site.repository }}/issues/7708))
 - Introduce frontmatter in step 2 ([#7704]({{ site.repository }}/issues/7704))
 - Add @ashmaroli to Core Team listing ([#7398]({{ site.repository }}/issues/7398))
-- Lnk to Tidelift in site's footer ([#7377]({{ site.repository }}/issues/7377))
+- Link to Tidelift in site's footer ([#7377]({{ site.repository }}/issues/7377))
 - Link to OpenCollective backing ([#7378]({{ site.repository }}/issues/7378)
 - Link to sponsor listing in README ([#7405]({{ site.repository }}/issues/7405))
 - Adjust team page listings ([#7395]({{ site.repository }}/issues/7395))
@@ -313,6 +685,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 
 ### Release
 
+- Jekyll v4.0 release ([#7782]({{ site.repository }}/issues/7782))
 - Release post for v4.0.0 beta1 ([#7716]({{ site.repository }}/issues/7716))
 - Release post for v4.0.0.pre.alpha1 ([#7574]({{ site.repository }}/issues/7574))
 - Release post for v3.8.0 ([#6849]({{ site.repository }}/issues/6849))
@@ -466,7 +839,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - doc: add liquid tag plugin jekyll-onebox for html previews ([#6898]({{ site.repository }}/issues/6898))
 - Add `jekyll-w2m` to plugins ([#6855]({{ site.repository }}/issues/6855))
 - Fix tutorials navigation HTML ([#6919]({{ site.repository }}/issues/6919))
-- add Arch Linux instalation troubleshoot ([#6782]({{ site.repository }}/issues/6782))
+- add Arch Linux installation troubleshoot ([#6782]({{ site.repository }}/issues/6782))
 - Docs: Install Jekyll on macOS ([#6881]({{ site.repository }}/issues/6881))
 - Fix CodeClimate badges [ci skip] ([#6930]({{ site.repository }}/issues/6930))
 - Update index.md ([#6933]({{ site.repository }}/issues/6933))
@@ -641,7 +1014,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Fix list appearance by adding missing `ol` tag ([#6421]({{ site.repository }}/issues/6421))
 - Explain how to override output collection index page ([#6424]({{ site.repository }}/issues/6424))
 - Added github-cards to the list of plugins ([#6425]({{ site.repository }}/issues/6425))
-- CoC violation correspondants ([#6429]({{ site.repository }}/issues/6429))
+- CoC violation correspondents ([#6429]({{ site.repository }}/issues/6429))
 - Add a note about Liquid and syntax highlighting ([#6466]({{ site.repository }}/issues/6466))
 - Remove `sudo` from macOS troubleshooting instructions ([#6486]({{ site.repository }}/issues/6486))
 - Add a note on `:jekyll_plugins` group in the docs ([#6488]({{ site.repository }}/issues/6488))
@@ -772,7 +1145,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - add SUPPORT file for GitHub ([#6324]({{ site.repository }}/issues/6324))
 - Rename CODE_OF_CONDUCT to show in banner ([#6325]({{ site.repository }}/issues/6325))
 - Docs : illustrate page.id for a collection's document ([#6329]({{ site.repository }}/issues/6329))
-- Docs: post's date can be overriden in front matter ([#6334]({{ site.repository }}/issues/6334))
+- Docs: post's date can be overridden in front matter ([#6334]({{ site.repository }}/issues/6334))
 - Docs: `site.url` behavior on development and production environments ([#6270]({{ site.repository }}/issues/6270))
 - Fix typo in site.url section of variables.md :-[ ([#6337]({{ site.repository }}/issues/6337))
 - Docs: updates ([#6343]({{ site.repository }}/issues/6343))
@@ -829,7 +1202,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 ### Bug Fixes
 {: #bug-fixes-v3-5-1}
 
-- Backward compatiblize URLFilters module ([#6163]({{ site.repository }}/issues/6163))
+- Backward compatibilize URLFilters module ([#6163]({{ site.repository }}/issues/6163))
 - Static files contain front matter default keys when `to_liquid`'d  ([#6162]({{ site.repository }}/issues/6162))
 - Always normalize the result of the `relative_url` filter ([#6185]({{ site.repository }}/issues/6185))
 
@@ -1342,7 +1715,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 ### Minor Enhancements
 {: #minor-enhancements-v3-2-0}
 
-- Stop testing with Ruby 2.0.x, which is EOL'd. ([#4381]({{ site.repository }}/issues/4381))
+- Stop testing with Ruby 2.0.x EOL ([#4381]({{ site.repository }}/issues/4381))
 - Allow collections to have documents that have no file extension ([#4545]({{ site.repository }}/issues/4545))
 - Add size property to `group_by` result ([#4557]({{ site.repository }}/issues/4557))
 - Site Template: Removed unnecessary nesting from `_base.scss` ([#4637]({{ site.repository }}/issues/4637))
@@ -1368,7 +1741,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Add 'jekyll new-theme' command to help users get up and running creating a theme ([#4848]({{ site.repository }}/issues/4848))
 - `markdownify` and `smartify` should convert input to string before conversion ([#4958]({{ site.repository }}/issues/4958))
 - Run `Site#generate` for 'jekyll doctor' to catch plugin issues ([#5005]({{ site.repository }}/issues/5005))
-- Add `normalize_whitepace` filter ([#4917]({{ site.repository }}/issues/4917))
+- Add `normalize_whitespace` filter ([#4917]({{ site.repository }}/issues/4917))
 - Move bin/jekyll to exe/jekyll to prevent collision with binstubs ([#5014]({{ site.repository }}/issues/5014))
 - Cleaning up site template & theme updates. ([#4922]({{ site.repository }}/issues/4922))
 - Add fetch method to Drops ([#5056]({{ site.repository }}/issues/5056))
@@ -1420,7 +1793,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Fix state leakage in Kramdown test ([#4618]({{ site.repository }}/issues/4618))
 - Unify method for copying special files from repo to site ([#4601]({{ site.repository }}/issues/4601))
 - Refresh the contributing file ([#4596]({{ site.repository }}/issues/4596))
-- change smartify doc from copy/paste of mardownify doc ([#4653]({{ site.repository }}/issues/4653))
+- change smartify doc from copy/paste of markdownify doc ([#4653]({{ site.repository }}/issues/4653))
 - Update Rake & disable warnings when running tests ([#4720]({{ site.repository }}/issues/4720))
 - Fix many warnings ([#4537]({{ site.repository }}/issues/4537))
 - Don't blindly assume the last system when determining "open" cmd ([#4717]({{ site.repository }}/issues/4717))
@@ -1519,7 +1892,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Corrected pagination docs for hidden: true feature ([#4903]({{ site.repository }}/issues/4903))
 - Remove a Broken Link for Refheap Plugin ([#4971]({{ site.repository }}/issues/4971))
 - Instructions on how to install github-gem on Windows ([#4975]({{ site.repository }}/issues/4975))
-- Minor tweak to fix missing apostrophne ([#4962]({{ site.repository }}/issues/4962))
+- Minor tweak to fix missing apostrophe ([#4962]({{ site.repository }}/issues/4962))
 - Instructions on how to install github-gem on Windows (v2) ([#4977]({{ site.repository }}/issues/4977))
 - Fix inaccurate HTTP response header field name ([#4976]({{ site.repository }}/issues/4976))
 - Add post about GSoC project ([#4980]({{ site.repository }}/issues/4980))
@@ -1527,10 +1900,10 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Update normalize.css to v4.0.0. ([#4989]({{ site.repository }}/issues/4989))
 - Add jekyll-tags-list-plugin to list of third-party plugins ([#5000]({{ site.repository }}/issues/5000))
 - Windows docs: Command needs to be called from blog path ([#5006]({{ site.repository }}/issues/5006))
-- Update text to be consitent with example ([#5010]({{ site.repository }}/issues/5010))
+- Update text to be consistent with example ([#5010]({{ site.repository }}/issues/5010))
 - Update template links to point to core Liquid site ([#5012]({{ site.repository }}/issues/5012))
 - Add generator-jekyllized to third-party plugins ([#5027]({{ site.repository }}/issues/5027))
-- Add Jekyll Art Hallery generator plugin to list of third-party plugins ([#5043]({{ site.repository }}/issues/5043))
+- Add Jekyll Art Gallery generator plugin to list of third-party plugins ([#5043]({{ site.repository }}/issues/5043))
 - Add Formingo to the list of Jekyll form SaaS ([#5054]({{ site.repository }}/issues/5054))
 - Highlight help nav item when navigated to. ([#5058]({{ site.repository }}/issues/5058))
 - Update normalize.css to v4.2.0. ([#5096]({{ site.repository }}/issues/5096))
@@ -1708,9 +2081,9 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Reorganize and cleanup the Gemfile, shorten required depends. ([#4318]({{ site.repository }}/issues/4318))
 - Remove script/rebund. ([#4341]({{ site.repository }}/issues/4341))
 - Implement codeclimate platform ([#4340]({{ site.repository }}/issues/4340))
-- Remove ObectSpace dumping and start using inherited, it's faster. ([#4342]({{ site.repository }}/issues/4342))
+- Remove ObjectSpace dumping and start using inherited, it's faster. ([#4342]({{ site.repository }}/issues/4342))
 - Add script/travis so all people can play with Travis-CI images. ([#4338]({{ site.repository }}/issues/4338))
-- Move Cucumber to using RSpec-Expections and furthering JRuby support. ([#4343]({{ site.repository }}/issues/4343))
+- Move Cucumber to using RSpec-Expectations and furthering JRuby support. ([#4343]({{ site.repository }}/issues/4343))
 - Rearrange Cucumber and add some flair. ([#4347]({{ site.repository }}/issues/4347))
 - Remove old FIXME ([#4349]({{ site.repository }}/issues/4349))
 - Clean up the Gemfile (and keep all the necessary dependencies) ([#4350]({{ site.repository }}/issues/4350))
@@ -2066,7 +2439,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Define the `install` step in the CI example `.travis.yml` ([#3622]({{ site.repository }}/issues/3622))
 - Expand collections documentation. ([#3638]({{ site.repository }}/issues/3638))
 - Add the "warning" note label to excluding `vendor` in the CI docs page ([#3623]({{ site.repository }}/issues/3623))
-- Upgrade pieces of the Ugrading guide for Jekyll 3 ([#3607]({{ site.repository }}/issues/3607))
+- Upgrade pieces of the Upgrading guide for Jekyll 3 ([#3607]({{ site.repository }}/issues/3607))
 - Showing how to access specific data items ([#3468]({{ site.repository }}/issues/3468))
 - Clarify pagination works from within HTML files ([#3467]({{ site.repository }}/issues/3467))
 - Add note to `excerpt_separator` documentation that it can be set globally ([#3667]({{ site.repository }}/issues/3667))
@@ -3192,7 +3565,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Add ReadInXMinutes plugin to the plugin list ([#1222]({{ site.repository }}/issues/1222))
 - Remove plugins from the plugin list that have equivalents in Jekyll proper ([#1223]({{ site.repository }}/issues/1223))
 - Add jekyll-assets to the plugin list ([#1225]({{ site.repository }}/issues/1225))
-- Add jekyll-pandoc-mulitple-formats to the plugin list ([#1229]({{ site.repository }}/issues/1229))
+- Add jekyll-pandoc-multiple-formats to the plugin list ([#1229]({{ site.repository }}/issues/1229))
 - Remove dead link to "Using Git to maintain your blog" ([#1227]({{ site.repository }}/issues/1227))
 - Tidy up the third-party plugins listing ([#1228]({{ site.repository }}/issues/1228))
 - Update contributor information ([#1192]({{ site.repository }}/issues/1192))
@@ -3367,7 +3740,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - Adds excerpt attribute to posts which contains first paragraph of content ([#837]({{ site.repository }}/issues/837))
 - Accept custom configuration file via CLI ([#863]({{ site.repository }}/issues/863))
 - Load in GitHub Pages MIME Types on `jekyll serve` ([#847]({{ site.repository }}/issues/847), [#871]({{ site.repository }}/issues/871))
-- Improve debugability of error message for a malformed highlight tag ([#785]({{ site.repository }}/issues/785))
+- Improve debuggability of error message for a malformed highlight tag ([#785]({{ site.repository }}/issues/785))
 - Allow symlinked files in unsafe mode ([#824]({{ site.repository }}/issues/824))
 - Add 'gist' Liquid tag to core ([#822]({{ site.repository }}/issues/822), [#861]({{ site.repository }}/issues/861))
 - New format of Jekyll output ([#795]({{ site.repository }}/issues/795))

docs/_docs/includes.md

@@ -69,7 +69,7 @@ You can also pass parameters to an include. For example, suppose you have a file
 ```
 {% 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:
+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

docs/_docs/index.md

@@ -6,33 +6,50 @@ redirect_from:
   - /docs/quickstart/
   - /docs/extras/
 ---
-Jekyll is a simple, extendable, static site generator. You give it text written
-in your favorite markup language and it churns through layouts to create a
-static website. Throughout that process you can tweak how you want the site URLs
-to look, what data gets displayed in the layout, and more.
+Jekyll is a static site generator. It takes text written in your
+favorite markup language and uses layouts to create a static website. You can
+tweak the site's look and feel, URLs, the data displayed on the page, and more. 
+
+## Prerequisites
+
+Jekyll requires the following:
+
+* Ruby version **{{ site.data.ruby.min_version }}** or higher
+* RubyGems
+* GCC and Make
+
+See [Requirements]({{ '/docs/installation/#requirements' | relative_url }}) for guides and details.
 
 ## Instructions
 
-1. Install a full [Ruby development environment](/docs/installation/)
-2. Install Jekyll and [bundler](/docs/ruby-101/#bundler) [gems](/docs/ruby-101/#gems)
-```
+1. Install all [prerequisites]({{ '/docs/installation/' | relative_url }}).
+2. Install the jekyll and bundler [gems]({{ '/docs/ruby-101/#gems' | relative_url }}).
+```sh
 gem install jekyll bundler
 ```
-3. Create a new Jekyll site at `./myblog`
-```
+3. Create a new Jekyll site at `./myblog`.
+```sh
 jekyll new myblog
 ```
-4. Change into your new directory
-```
+4. Change into your new directory.
+```sh
 cd myblog
 ```
-5. Build the site and make it available on a local server
-```
+5. Build the site and make it available on a local server.
+```sh
 bundle exec jekyll serve
 ```
-6. Now browse to [http://localhost:4000](http://localhost:4000){:target="_blank"}
+6. Browse to [http://localhost:4000](http://localhost:4000){:target="_blank"}
 
-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.
+{: .note .warning}
+If you are using Ruby version 3.0.0 or higher, step 5 [may fail](https://github.com/github/pages-gem/issues/752). You may fix it by adding `webrick` to your dependencies: `bundle add webrick`
+
+{: .note .info}
+Pass the `--livereload` option to `serve` to automatically refresh the page with each change you make to the source files: `bundle exec jekyll serve --livereload`
+
+
+If you encounter any errors during this process, check that you have installed all the prerequisites in [Requirements]({{ '/docs/installation/#requirements' | relative_url }}). 
+If you still have issues, see [Troubleshooting]({{ '/docs/troubleshooting/#configuration-problems' | relative_url }}).
+
+{: .note .info}
+Installation varies based on your operating system. See our [guides]({{ '/docs/installation/#guides' | relative_url }}) for OS-specific instructions.

docs/_docs/installation.md

@@ -4,19 +4,19 @@ description: Official guide to install Jekyll on macOS, GNU/Linux or Windows.
 permalink: /docs/installation/
 ---
 
-Jekyll is a [Ruby Gem](/docs/ruby-101/#gems) that can be installed on most systems.
+Jekyll is a [Ruby Gem]({{ '/docs/ruby-101/#gems' | relative_url }}) that can be installed on most systems.
 
 ## Requirements
 
-* [Ruby](https://www.ruby-lang.org/en/downloads/) version **{{ site.data.ruby.min_version }}** or above, including all development headers (ruby version 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)
+* [Ruby](https://www.ruby-lang.org/en/downloads/) version **{{ site.data.ruby.min_version }}** or higher, including all development headers (check your Ruby version using `ruby -v`)
+* [RubyGems](https://rubygems.org/pages/download) (check your Gems version using `gem -v`)
+* [GCC](https://gcc.gnu.org/install/) and [Make](https://www.gnu.org/software/make/) (check versions using `gcc -v`,`g++ -v`,  and `make -v`)
 
 ## Guides
 
-For detailed install instructions have a look at the guide for your operating system.
+For detailed install instructions, follow the guide for your operating system.
 
-* [macOS](/docs/installation/macos/)
-* [Ubuntu Linux](/docs/installation/ubuntu/)
-* [Other Linux distros](/docs/installation/other-linux)
-* [Windows](/docs/installation/windows/)
+* [macOS]({{ '/docs/installation/macos/' | relative_url }})
+* [Ubuntu]({{ '/docs/installation/ubuntu/' | relative_url }})
+* [Other Linux]({{ '/docs/installation/other-linux/' | relative_url }})
+* [Windows]({{ '/docs/installation/windows/' | relative_url }})

docs/_docs/installation/macos.md

@@ -3,133 +3,92 @@ title: Jekyll on macOS
 permalink: /docs/installation/macos/
 ---
 
-## Install Command Line Tools
-First, you need to install the command-line tools to be able to compile native extensions, open a terminal and run:
+## Supported macOS versions
 
-```sh
-xcode-select --install
-```
+- Monterey (macOS 12)
+- Big Sur (macOS 11)
+- Catalina (macOS 10.15)
+
+Older macOS versions might work, but we don't officially support them.
 
 ## Install Ruby
 
-Jekyll requires **Ruby > {{ site.data.ruby.min_version }}**.
-As macOS Mojave 10.14 comes only with ruby 2.3.x, you'll have to install a newer version of Ruby.
+To install Jekyll on macOS, you need a proper Ruby development environment. 
+While macOS comes preinstalled with Ruby, we don't recommend using that version 
+to install Jekyll. This external article goes over the various reasons 
+[why you shouldn't use the system Ruby](https://www.moncefbelyamani.com/why-you-shouldn-t-use-the-system-ruby-to-install-gems-on-a-mac/).
 
-### With Homebrew {#brew}
-To run the latest Ruby version you need to install it through [Homebrew](https://brew.sh).
+Instead, you'll need to install a separate and newer version of Ruby using a 
+version manager such as [asdf], [chruby], [rbenv], or [rvm]. Version managers 
+allow you to easily install multiple versions of Ruby, and switch between them.
+
+We recommend `chruby` because it's the simplest and least likely to cause issues. 
+
+The instructions below are an excerpt from this detailed external guide to 
+[install Ruby on Mac]. They work best if you're setting up development tools 
+for the first time on your Mac. If you've already tried to install Ruby or 
+Jekyll on your Mac, or if you run into any issues, read that guide. 
+
+[asdf]: https://asdf-vm.com/
+[chruby]: https://github.com/postmodern/chruby
+[rbenv]: https://github.com/rbenv/rbenv
+[rvm]: https://rvm.io/
+[install Ruby on Mac]: https://www.moncefbelyamani.com/how-to-install-xcode-homebrew-git-rvm-ruby-on-mac/
+
+### Step 1: Install Homebrew
+
+[Homebrew](https://brew.sh/) makes it easy to install development tools on a Mac.
 
 ```sh
-# Install Homebrew
-/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-
-brew install ruby
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
 ```
 
-Add the brew ruby path to your shell config :
+### Step 2: Install chruby and the latest Ruby with ruby-install
 
-```
-export PATH=/usr/local/opt/ruby/bin:$PATH
-```
-
-Then relaunch your terminal and check your updated Ruby setup:
+Install `chruby` and `ruby-install` with Homebrew:
 
 ```sh
-which ruby
-# /usr/local/opt/ruby/bin/ruby
+brew install chruby ruby-install
+```
 
+Install the latest stable version of Ruby:
+
+```sh
+ruby-install ruby
+```
+
+This will take a few minutes, and once it's done, configure your shell to 
+automatically use `chruby`:
+
+```sh
+echo "source $(brew --prefix)/opt/chruby/share/chruby/chruby.sh" >> ~/.zshrc
+echo "source $(brew --prefix)/opt/chruby/share/chruby/auto.sh" >> ~/.zshrc
+echo "chruby ruby-{{ site.data.ruby.current_version }}" >> ~/.zshrc
+```
+
+If you're using Bash, replace `.zshrc` with `.bash_profile`. If you're not sure, 
+read this external guide to 
+[find out which shell you're using](https://www.moncefbelyamani.com/which-shell-am-i-using-how-can-i-switch/).
+
+Quit and relaunch Terminal, then check that everything is working:
+
+```sh
 ruby -v
-{{ site.data.ruby.current_version_output }}
 ```
 
-Yay, we are now running current stable Ruby!
+It should show {{ site.data.ruby.current_version_output }} or a newer version.
 
-### With rbenv {#rbenv}
-
-People often use [rbenv](https://github.com/rbenv/rbenv) to manage multiple
-Ruby versions. This is very useful when you need to be able to run a given Ruby version on a project.
-
-```sh
-# Install Homebrew
-/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-
-# 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 you can install the Ruby version of our choice, let's go with current latest stable Ruby:
-
-```sh
-rbenv install {{ site.data.ruby.current_version }}
-rbenv global {{ site.data.ruby.current_version }}
-ruby -v
-{{ site.data.ruby.current_version_output }}
-```
-
-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.
+Next, read that same external guide for important notes about 
+[setting and switching between Ruby versions with chruby](https://www.moncefbelyamani.com/how-to-install-xcode-homebrew-git-rvm-ruby-on-mac/#how-to-install-different-versions-of-ruby-and-switch-between-them).
 
 ## Install Jekyll
 
-Now all that is left is installing [Bundler](/docs/ruby-101/#bundler) and Jekyll.
-
-### Local Install
+After installing Ruby with chruby, install the latest Jekyll gem:
 
 ```sh
-gem install --user-install bundler jekyll
+gem install jekyll
 ```
 
-and then get your Ruby version using
+## Troubleshooting
 
-```sh
-ruby -v
-{{ site.data.ruby.current_version_output }}
-```
-
-Then append your path file with the following, replacing the `X.X` with the first two digits of your Ruby version.
-
-```
-export PATH=$HOME/.gem/ruby/X.X.0/bin:$PATH
-```
-
-To check your that you gem paths point to your home directory run:
-
-```sh
-gem env
-```
-
-And check that `GEM PATHS:` points to a path in your home directory
-
-{: .note }
-Every time you update Ruby to a version with a different first two digits, you will need to update your path to match.
-
-### Global Install
-
-{: .note .warning}
-We strongly recommend against installing Ruby gems globally to avoid file permissions problems and using `sudo`.
-
-#### On Mojave (10.14)
-
-Because of SIP Protections in Mojave, you must run:
-
-```sh
-sudo gem install bundler
-sudo gem install -n /usr/local/bin/ jekyll
-```
-
-#### Before Mojave (<10.14)
-
-You only have to run:
-
-```sh
-sudo gem install bundler jekyll
-```
-
-## Problems?
-
-Check out the [troubleshooting](/docs/troubleshooting/) page or [ask for help on our forum](https://talk.jekyllrb.com).
+See [Troubleshooting]({{ '/docs/troubleshooting/' | relative_url }}) or [ask for help on our forum](https://talk.jekyllrb.com).

docs/_docs/installation/other-linux.md

@@ -2,18 +2,59 @@
 title: Jekyll on Linux
 permalink: /docs/installation/other-linux/
 ---
-Installation on other Linux distributions works similarly as on [Ubuntu](../ubuntu/).
 
-On Fedora, the dependencies can be installed as follows:
+Installation on other Linux distributions works similarly to installing on [Ubuntu](../ubuntu/).
 
- ```sh
-sudo dnf install ruby ruby-devel @development-tools
+## Install prerequisites
+
+### Fedora
+
+```sh
+sudo dnf install ruby ruby-devel openssl-devel redhat-rpm-config @development-tools
+```
+### RHEL8/CentOS8
+
+```sh
+sudo dnf install ruby ruby-devel
+sudo dnf group install "Development Tools"
 ```
 
-On Debian:
+### Debian
 
 ```sh
 sudo apt-get install ruby-full build-essential
 ```
 
-The rest works the same as on [Ubuntu](../ubuntu/).
+### Gentoo
+
+```sh
+sudo emerge -av jekyll
+```
+
+or
+
+```sh
+sudo emerge --ask --verbose jekyll
+```
+
+### ArchLinux
+
+```sh
+sudo pacman -S ruby base-devel
+```
+
+### OpenSUSE
+
+```sh
+sudo zypper install -t pattern devel_ruby devel_C_C++
+sudo zypper install ruby-devel
+```
+
+### Clear Linux
+
+```sh
+sudo swupd bundle-add ruby-basic
+```
+## Install Jekyll
+
+Follow the instructions for [Ubuntu](../ubuntu/).

docs/_docs/installation/ubuntu.md

@@ -2,17 +2,19 @@
 title: Jekyll on Ubuntu
 permalink: /docs/installation/ubuntu/
 ---
-Before we install Jekyll, we need to make sure we have all the required
-dependencies.
+
+## Install dependencies
+
+Install Ruby and other [prerequisites]({{ '/docs/installation/#requirements' | relative_url }}):
 
 ```sh
 sudo apt-get install ruby-full build-essential zlib1g-dev
 ```
 
-It is best to avoid installing Ruby Gems as the root user. Therefore, we need to
+Avoid installing RubyGems packages (called gems) as the root user. Instead, 
 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:
+the gem installation path:
 
 ```sh
 echo '# Install Ruby Gems to ~/gems' >> ~/.bashrc
@@ -21,7 +23,7 @@ echo 'export PATH="$HOME/gems/bin:$PATH"' >> ~/.bashrc
 source ~/.bashrc
 ```
 
-Finally, install Jekyll:
+Finally, install Jekyll and Bundler:
 
 ```sh
 gem install jekyll bundler

docs/_docs/installation/windows.md

@@ -5,29 +5,32 @@ redirect_from:
   - /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.
+While Windows is not an officially-supported platform, it can be used to run Jekyll with the proper tweaks.
 
-
-## Installing Jekyll
+## Installing Ruby and Jekyll
 
 ### Installation via RubyInstaller
 
-The easiest way to run Jekyll is by using the [RubyInstaller](https://rubyinstaller.org/) for Windows.
+The easiest way to install Ruby and Jekyll is by using the [RubyInstaller](https://rubyinstaller.org/) for Windows.
 
 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
+
+We only cover RubyInstaller-2.4 and newer here. Older versions need to
 [install the Devkit](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit) manually.
 
-1. Download and Install a **Ruby+Devkit** version from [RubyInstaller Downloads](https://rubyinstaller.org/downloads/).
+1. Download and install a **Ruby+Devkit** version from [RubyInstaller Downloads](https://rubyinstaller.org/downloads/).
    Use default options for installation.
 2. Run the `ridk install` step on the last stage of the installation wizard. This is needed for installing gems with native
    extensions. You can find additional information regarding this in the
    [RubyInstaller Documentation](https://github.com/oneclick/rubyinstaller2#using-the-installer-on-a-target-system)
 3. 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`
-4. Check if Jekyll installed properly: `jekyll -v`
+   Install Jekyll and Bundler using `gem install jekyll bundler`
+4. Check if Jekyll has been installed properly: `jekyll -v`
+
+{: .note .info}
+You may receive an error when checking if Jekyll has not been installed properly. Reboot your system and run `jekyll -v` again.
+If the error persists, please open a [RubyInstaller issue](https://github.com/oneclick/rubyinstaller2/issues/new).
 
 That's it, you're ready to use Jekyll!
 
@@ -36,19 +39,18 @@ That's it, you're ready to use Jekyll!
 If you are using Windows 10 version 1607 or later, another option to run Jekyll is by
 [installing](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide) the Windows Subsystem for Linux.
 
-*Note:* You must have [Windows Subsystem for Linux](https://msdn.microsoft.com/en-us/commandline/wsl/about) enabled.
+{: .note .info}
+You must have [Windows Subsystem for Linux](https://msdn.microsoft.com/en-us/commandline/wsl/about) enabled.
 
-First let's make sure all our packages / repositories are up to date. Open a new Command Prompt instance, and type the following:
+Make sure all your packages and repositories are up to date. Open a new Command Prompt or PowerShell window and type `bash`.
 
-```sh
-bash
-```
-Your Command Prompt instance should now be a Bash instance. Now we must update our repo lists and packages.
+Your terminal should now be a Bash instance. Next, update your repository 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/),
+
+Next, install Ruby. To do this, let's use a repository from [BrightBox](https://www.brightbox.com/docs/ruby/ubuntu/),
 which hosts optimized versions of Ruby for Ubuntu.
 
 ```sh
@@ -57,27 +59,28 @@ sudo apt-get update
 sudo apt-get install ruby2.5 ruby2.5-dev build-essential dh-autoreconf
 ```
 
-Next let's update our Ruby gems:
+Next, update your Ruby gems:
 
 ```sh
 gem update
 ```
 
-Now all that is left to do is install Jekyll.
+Install Jekyll:
 
 ```sh
 gem install jekyll bundler
 ```
 
-(*Note: no `sudo` here.*)
+{: .note .info}
+  No `sudo` here.
 
-Check if Jekyll installed properly by running:
+Check your Jekyll version:
 
 ```sh
 jekyll -v
 ```
 
-**And that's it!**
+That's it! You're ready to start using Jekyll. 
 
 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.
@@ -85,55 +88,47 @@ 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>
+  the "Running Jekyll as Non-Superuser" instructions in
+  <a href="{{ '/docs/troubleshooting/#no-sudo' | relative_url }}">Troubleshooting</a>.</p>
 </div>
 
-**Note:** Bash on Ubuntu on Windows is still under development, so you may run into issues.
-
+{: .note .info}
+Bash on Ubuntu on Windows is still under development, so you may run into issues.
 
 ## 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.
+If you use UTF-8 encoding, Jekyll will break if a file starts with characters representing a [BOM](https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8). Therefore, remove this sequence of bytes if it appears at the beginning of your file.
 
 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:
+`Liquid Exception: Incompatible character encoding` error during the site generation process. Run the following:
 
 ```sh
 chcp 65001
 ```
 
-## Time-Zone Management
+## 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.
+Since Windows doesn't have a native source of zoneinfo data, the Ruby Interpreter doesn't understand IANA Timezones.
+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
+Though Windows users could alternatively define their blog's timezone by setting the key to use the 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](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+
 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:
+sites *will* have to update their `Gemfile` (and installed gems) 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]
+# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
+# and associated library.
+platforms :mingw, :x64_mingw, :mswin, :jruby do
+  gem "tzinfo", ">= 1", "< 3"
+  gem "tzinfo-data"
+end
 ```
 
-<div class="note warning">
-  <h5>TZInfo 2.0 incompatibility</h5>
-  <p>
-    <code>v2.0</code> of the TZInfo library has introduced a change in how timezone offsets are calculated.
-    This will result in incorrect date and time for your posts when the site is built with Jekyll 3.x on Windows.
-  </p>
-  <p>
-    We therefore recommend that you lock the Timezone library to <code>v1.2</code> and above by listing
-    <code>gem 'tzinfo', '~> 1.2'</code> in your <code>Gemfile</code>.
-  </p>
-</div>
-
 ## Auto Regeneration
 
 Jekyll uses the `listen` gem to watch for changes when the `--watch` switch is specified during a build or serve.

docs/_docs/layouts.md

@@ -24,17 +24,14 @@ from this as needed.
   </p>
 </div>
 
-
 ## Usage
 
 The first step is to put the template source code in `default.html`. `content`
 is a special variable, the value is the rendered content of the post or page
 being wrapped.
 
-
-
 {% raw %}
-```
+```liquid
 <!doctype html>
 <html lang="en">
   <head>
@@ -67,7 +64,7 @@ You can also use
 [front matter defaults](/docs/configuration/front-matter-defaults/) to save you
 from having to set this on every page.
 
-```
+```markdown
 ---
 title: My First Page
 layout: default
@@ -78,7 +75,7 @@ This is the content of my page
 
 The rendered output of this page is:
 
-```
+```html
 <!doctype html>
 <html lang="en">
   <head>
@@ -102,7 +99,6 @@ The rendered output of this page is:
 </html>
 ```
 
-
 ## Inheritance
 
 Layout inheritance is useful when you want to add something to an existing
@@ -115,7 +111,7 @@ layout in front matter. For example this layout will live at
 `_layouts/post.html`:
 
 {% raw %}
-```
+```liquid
 ---
 layout: default
 ---
@@ -134,7 +130,7 @@ using in Liquid, you need to use the `layout` variable instead of `page`. For
 example:
 
 {% raw %}
-```
+```liquid
 ---
 city: San Francisco
 ---

docs/_docs/liquid.md

@@ -5,7 +5,7 @@ redirect_from: "/docs/templates/"
 ---
 
 Jekyll uses the [Liquid](https://shopify.github.io/liquid/) templating language
-to process templates. 
+to process templates.
 
 Generally in Liquid you output content using two curly braces e.g.
 {% raw %}`{{ variable }}`{% endraw %} and perform logic statements by
@@ -15,5 +15,5 @@ out the [official Liquid Documentation](https://shopify.github.io/liquid/).
 
 Jekyll provides a number of useful Liquid additions to help you build your site:
 
-* [Filters](/docs/liquid/filters/)
-* [Tags](/docs/liquid/tags/)
+* [Filters]({{ '/docs/liquid/filters/' | relative_url }})
+* [Tags]({{ '/docs/liquid/tags/' | relative_url }})

docs/_docs/liquid/filters.md

@@ -70,7 +70,7 @@ using [plugins](/docs/plugins/).
     {% for filter in site.data.jekyll_filters %}
       <tr>
         <td>
-          <p class="name"><strong>{{ filter.name }}</strong></p>
+          <p id="{{ filter.name | slugify }}" class="name"><strong>{{ filter.name }}</strong></p>
           <p>
             {{- filter.description -}}
             {%- if filter.version_badge %}
@@ -108,15 +108,21 @@ The default is `default`. They are as follows (with what they filter):
 
 You can use the `where` filter to detect documents and pages with properties that are `nil` or `""`. For example,
 
+{% raw %}
 ```liquid
-// Using `nil` to select posts that either do not have `my_prop` defined or `my_prop` has been set to `nil` explicitly.
-{% raw %}{% assign filtered_posts = site.posts | where: 'my_prop', nil %}{% endraw %}
+// Using `nil` to select posts that either do not have `my_prop`
+// defined or `my_prop` has been set to `nil` explicitly.
+{% assign filtered_posts = site.posts | where: 'my_prop', nil %}
 ```
+{% endraw %}
 
+{% raw %}
 ```liquid
-// Using Liquid's special literal `empty` or `blank` to select posts that have `my_prop` set to an empty value.
-{% raw %}{% assign filtered_posts = site.posts | where: 'my_prop', empty %}{% endraw %}
+// Using Liquid's special literal `empty` or `blank` to select
+// posts that have `my_prop` set to an empty value.
+{% assign filtered_posts = site.posts | where: 'my_prop', empty %}
 ```
+{% endraw %}
 
 ### Binary operators in `where_exp` filter {%- include docs_version_badge.html version="4.0" -%}
 
@@ -125,15 +131,19 @@ conditionals in the operation.
 
 For example, to get a list of documents on English horror flicks, one could use the following snippet:
 
+{% raw %}
 ```liquid
-{% raw %}{{ site.movies | where_exp: "item", "item.genre == 'horror' and item.language == 'English'" }}{% endraw %}
+{{ site.movies | where_exp: "item", "item.genre == 'horror' and item.language == 'English'" }}
 ```
+{% endraw %}
 
 Or to get a list of comic-book based movies, one may use the following:
 
+{% raw %}
 ```liquid
-{% raw %}{{ site.movies | where_exp: "item", "item.sub_genre == 'MCU' or item.sub_genre == 'DCEU'" }}{% endraw %}
+{{ site.movies | where_exp: "item", "item.sub_genre == 'MCU' or item.sub_genre == 'DCEU'" }}
 ```
+{% endraw %}
 
 ### Standard Liquid Filters
 

docs/_docs/liquid/tags.md

@@ -5,12 +5,12 @@ permalink: "/docs/liquid/tags/"
 All of the standard Liquid
 [tags](https://shopify.github.io/liquid/tags/control-flow/) are supported.
 Jekyll has a few built in tags to help you build your site. You can also create
-your own tags using [plugins](/docs/plugins/).
+your own tags using [plugins]({{ '/docs/plugins/' | relative_url }}).
 
 ## Includes
 
 If you have page snippets that you use repeatedly across your site, an
-[include](/docs/includes/) is the perfect way to make this more maintainable.
+[include]({{ '/docs/includes/' | relative_url }}) is the perfect way to make this more maintainable.
 
 ## Code snippet highlighting
 
@@ -18,12 +18,11 @@ Jekyll has built in support for syntax highlighting of over 100 languages
 thanks to [Rouge](http://rouge.jneen.net). Rouge is the default highlighter
 in Jekyll 3 and above.
 
-<div class="note warning">
-  <p>Using Pygments has been deprecated and is not supported in
-  Jekyll 4, the configuration setting <code>highlighter: pygments</code>
-  now automatically falls back to using <em>Rouge</em> which is written in Ruby
-  and 100% compatible with stylesheets for Pygments.</p>
-</div>
+{: .note .warning}
+Using Pygments has been deprecated and is not supported in
+Jekyll 4; the configuration setting <code>highlighter: pygments</code>
+now automatically falls back to using <em>Rouge</em> which is written in Ruby
+and 100% compatible with stylesheets for Pygments.
 
 To render a code block with syntax highlighting, surround your code as follows:
 
@@ -47,7 +46,7 @@ wiki](https://github.com/jayferd/rouge/wiki/List-of-supported-languages-and-lexe
   <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.
-    Since {% include docs_version_badge.html version="4.0" %} you can add <code>render_with_liquid: false</code> in your front matter to disable Liquid entirely for a particular document.</p>
+    Since Jekyll {% include docs_version_badge.html version="4.0" %}, you can add <code>render_with_liquid: false</code> in your front matter to disable Liquid entirely for a particular document.</p>
 </div>
 
 ### Line numbers
@@ -71,8 +70,8 @@ end
 
 In order for the highlighting to show up, you’ll need to include a highlighting
 stylesheet. For Pygments or Rouge you can use a stylesheet for Pygments, you
-can find an example gallery 
-[here](https://jwarby.github.io/jekyll-pygments-themes/languages/ruby.html) 
+can find an example gallery
+[here](https://jwarby.github.io/jekyll-pygments-themes/languages/ruby.html)
 or from [its repository](https://github.com/jwarby/jekyll-pygments-themes).
 
 Copy the CSS file (`native.css` for example) into your css directory and import
@@ -84,8 +83,8 @@ the syntax highlighter styles into your `main.css`:
 
 ## Links
 
-{: .note }
-Since Jekyll {% include docs_version_badge.html version="v4.0"%} you don't need to prepend `link` and `post_url` tags with `site.baseurl`
+{: .note}
+Since Jekyll {% include docs_version_badge.html version="4.0"%}, you don't need to prepend `link` and `post_url` tags with `site.baseurl`.
 
 ### Linking to pages {#link}
 
@@ -117,11 +116,30 @@ The path to the post, page, or collection is defined as the path relative to the
 
 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.
+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.
+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.
+
+The name of the file you want to link 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 link:
+
+{% raw %}
+```liquid
+{% link {{ page.my_variable }} %}
+```
+{% endraw %}
+
+In this example, the `link` tag would render a link to the file `footer_company_a.html`.
 
 ### Linking to posts
 

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

@@ -3,7 +3,7 @@ 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 }
+{: .note .info}
 
 ## Affinity teams & their captains
 

docs/_docs/maintaining/avoiding-burnout.md

@@ -3,7 +3,7 @@ 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 }
+{: .note .info}
 
 # 1. Use Jekyll
 

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

@@ -3,7 +3,7 @@ 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 }
+{: .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.
 
@@ -13,7 +13,7 @@ You want to maintain Jekyll? Use it often. Do weird things with it. Do normal th
 
 ## 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:
+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
 
@@ -25,7 +25,7 @@ As a maintainer, you will be reviewing pull requests which update code. You shou
 
 ## 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).
+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!
 

docs/_docs/maintaining/index.md

@@ -4,7 +4,7 @@ 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 }
+{: .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.
 
@@ -15,6 +15,7 @@ Hello! This is where we document various processes for maintaining Jekyll. Being
 - [Avoiding burnout](avoiding-burnout/)
 - [Special Labels](special-labels/)
 - [Releasing a new version](releasing-a-new-version/)
+- [Releasing a new version off `*-stable` branches](releasing-off-stable-branches/)
 
 Interested in becoming a maintainer? Here is some documentation for **contributors**:
 

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

@@ -3,13 +3,13 @@ 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 }
+{: .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/) 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.
+**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
 
@@ -20,7 +20,7 @@ We have [a helpful little bot](https://github.com/jekyllbot) which we use to mer
 
 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

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

@@ -2,25 +2,107 @@
 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 }
+**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.
+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 hesitate 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
+The version will mostly be of the format `"major.minor.patch"`. At times, we may decide to ship pre-releases which will be in the format
+`"major.minor.patch.suffix"`. `suffix` is not standardized and may be anything like `pre.alpha1`, `pre.rc2`, or simply `beta3`, etc.
 
-Replace the first header of the history document with a version milestone. This looks like the following:
+To determine the correct version, consult the `## HEAD` section of our history document, `History.markdown`, first.
 
-```diff
--## HEAD
-+## 3.7.1 / 2018-01-25
+- If there's a subsection titled `Major Enhancements`
+  - Increment the `major` component of the version string and reset both `minor` and `patch` components to `0`.
+  - Add `suffix` if applicable.
+  - For example, `"3.9.1" => "4.0.0"` or, `"3.9.1 => "4.0.0.alpha1"`.
+  - Skip to next step in the release process.
+
+- If there's a subsection titled `Minor Enhancements`
+  - Increment just the `minor` component and reset the patch component to `0`.
+  - Add `suffix` if applicable.
+  - For example, `"4.0.2" => "4.1.0"` or `"4.1.0" => "4.2.0.pre"`.
+  - Skip to next step in the release process.
+
+- For anything else, increment just the `patch` component or `suffix` component as applicable. For example, `"4.0.2" => "4.0.3"` or
+  `"4.1.0.beta3" => "4.1.0.rc"`.
+
+### Write a release post
+
+In case this wasn't done already, you can generate a new release post scaffold using the included `rake` command:
+
+```sh
+bundle exec rake site:releases:new[3.8.0]
 ```
 
-Adjust the version number and the date. The `## HEAD` heading will be regenerated next time a pull request is merged.
+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 `v3.7.2` is the git tag for the previous release. In case the tag doesn't exist in your repository, run:
+
+```sh
+git pull
+```
+
+Be sure to open a pull request for your release post once its finished.
+
+### Update the History document
+
+Replace the first header of `History.markdown` 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 the next time a pull request is merged.
+
+Rearrange the subsections (as a whole) based on decreasing priorities as illustrated below:
+
+```
+## 4.2.0 / 2020-12-14
+
+### Major Enhancements
+
+...
+
+### Minor Enhancements
+
+...
+
+### Bug Fixes
+
+...
+
+### Security Fixes
+
+...
+
+### Optimization Fixes
+
+...
+
+### Development Fixes
+
+...
+
+### Site Enhancements
+
+...
+```
 
 Once you've done this, update the website by running the following command:
 
@@ -30,60 +112,51 @@ 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.
+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.
 
 ### 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`
+- A release post has been prepared, and is ideally already live via a prior pull request.
+- All of the prior steps are done, especially the change to `lib/jekyll/version.rb` has been staged for commit.
+- Commit staged changes to the local `master` branch preferably with commit message `"Release :gem: v[CURRENT_VERSION]"`.
 
-Really the only thing left to do is to run this command:
+The only thing left to do now is to run this command:
 
 ```sh
-bundle exec rake release
+git push upstream master
 ```
 
-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.
+where `upstream` references `git@github.com:jekyll/jekyll.git`.
 
-And then, you're done! :tada: Feel free to celebrate!
+This will trigger a GitHub Actions workflow that will automatically build the new gem, tag the release commit, push the tag to GitHub and
+then finally, push the new gem to RubyGems. Don't worry about creating a GitHub release either, @jekyllbot will take care of that when the
+release workflow publishes the new tag.
 
-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.
+And then, if the workflow has completed successfully, 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.
+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:
+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
+- Commit changes to default branch preferably with message `"Release :gem: v[CURRENT_VERSION]"`
+- Push to remote repository
 - Rejoice
 
 Be sure to ask your project's maintainers if you're unsure!

docs/_docs/maintaining/releasing-off-stable-branches.md

@@ -0,0 +1,63 @@
+---
+title: Releasing off older stable branches
+---
+
+Apart from having releases cut from the default `master` branch, Jekyll Core may occasionally cut releases containing security patches and
+critical bug-fixes for older versions under maintenance. Such releases are cut from specially named branches, following the pattern
+`[x].[y]-stable` where `[x]` denotes semver-major-version and `[y]`, the semver-minor-version. For example, the branch `3.9-stable` refers to
+commits released as part of `jekyll-3.9.x` series.
+
+Co-ordinating a release off a `*-stable` branch is complicated mainly because the default branch has to inevitably reflect the release as well.
+
+## Requirements
+
+- The maintainer has to have **write-access** to both the concerned `*-stable` and `master` branches.
+- The maintainer needs to complete the task using their **local CLI program** instead of dispatching via GitHub Web UI.
+- The maintainer is abreast with the workflow to [release off `master`]({{ 'docs/maintaining/releasing-a-new-version/' | relative_url }}). The
+  procedure documented in the following section is an abridged adaptation of the workflow for `master`.
+- A release post has been drafted and **is awaiting publish to `master`** via an approved pull request.
+- Stable internet connection.
+
+## Trigger release workflow
+
+1. Ensure that you've **checked out the concerned `*-stable` branch** and is up-to-date with its counterpart at `jekyll/jekyll` at GitHub.
+2. Bump the `VERSION` string in `lib/jekyll/version.rb`.
+3. Update the **History document** as documented [here]({{ 'docs/maintaining/releasing-a-new-version/#update-the-history-document' | relative_url }}).<br/>
+   (**IMPORTANT: Do not run `rake site:generate` on the stable branch though**).
+4. Copy the entire History section pertaining to current release and paste into a new tab / window of your text-editor. We will use this
+   temporary snippet at a future stage.
+5. Commit changes to the version-file and History document with commit message `Release :gem: v[CURRENT_VERSION]`.
+6. Push commit to upstream remote `jekyll/jekyll` at GitHub.
+
+## Publish release post
+
+1. Ensure the `Release Gem` workflow has completed successfully.
+2. Merge release-post pull request to `master`.
+
+## Update default branch to reflect release off the stable branch
+
+1. Locally, check out `master` and ensure it is up-to-date with its remote counterpart at `jekyll/jekyll` at GitHub.
+2. Update History document using the snippet in the temporary tab / window created earlier. The various sections in the History document are
+   primarily in reverse chronological order and secondarily scoped to the semver-major-version. For example, a release section for `v3.9.2`
+   will be listed above the section for `v3.9.1` but under release sections for v4.x.
+   The snippet stashed earlier has to be injected into the correct location manually.
+3. Optionally, update `VERSION` string in `lib/jekyll/version.rb`. (*If existing version is lesser than latest version*).
+4. Now **run `rake site:generate`** to update various meta files:
+     - docs/_config.yml
+     - docs/_docs/history.md
+     - docs/latest_version.txt
+5. Commit changes to various meta files with commit message `Release :gem: v[CURRENT_VERSION]`.
+6. Push commit to upstream remote.
+
+## Publish GitHub Release
+
+Unlike releases cut off the `master` branch, our JekyllBot does not automatically create and publish a GitHub Release for tags created from
+*non-default* branches. Therefore, the maintainer has to **manually create and publish** the concerned GitHub Release.
+1. Choose the newly pushed tag.
+2. Title is same as the name of the selected tag.
+3. The release snippet stashed previously forms the body.
+4. Delete the snippet's title (`## x.y.z / YYYY-MM-DD`) from the release body.
+5. Publish.
+
+Note: The GitHub Release may optionally be *drafted* prior to updating the default branch and then *published* immediately after pushing the
+update commit to the default branch to streamline the procedure.