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

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

.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

@@ -1,4 +1,4 @@
-blank_issues_enabled: false
+blank_issues_enabled: true
 contact_links:
   - name: Jekyll Community Forum
     url: https://talk.jekyllrb.com/

.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/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/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

@@ -3,101 +3,71 @@ name: Continuous Integration
 on:
   push:
     branches:
-    - master
-    - /.*-stable/
+      - master
+      - "*-stable"
   pull_request:
     branches:
-    - master
-    - /.*-stable/
+      - master
+      - "*-stable"
 
 jobs:
   ci:
-    if: "!contains(github.event.commits[0].message, '[ci skip]')"
-    name: 'Ruby ${{ matrix.ruby_version }}'
-    runs-on: 'ubuntu-latest'
-
+    name: "Run Tests (${{ matrix.label }})"
+    runs-on: "ubuntu-latest"
     strategy:
       fail-fast: false
       matrix:
-        ruby_version:
-        - 2.5
-        - 2.7
-        - jruby-9.2.11.1
-
+        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:
-    - uses: actions/checkout@v2
-      with:
-        fetch-depth: 5
-    - name: "Set up Ruby ${{ matrix.ruby_version }}"
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby_version }}
-        bundler-cache: true
-    - name: Run Unit Tests
-      run: bash script/test
-      env:
-        CI: true
-    - name: Run Cucumber Features
-      run: bash script/cucumber
-      env:
-        CI: true
-    - name: Sanity Check
-      run: bash script/default-site
+      - 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
 
-  style_check:
-    if: "!contains(github.event.commits[0].message, '[ci skip]')"
-    name: 'Code Style Check (Ruby ${{ matrix.ruby_version }})'
-    runs-on: 'ubuntu-latest'
+  xtras:
+    name: "${{ matrix.job_name }} (Ruby ${{ matrix.ruby_version }})"
+    runs-on: "ubuntu-latest"
     strategy:
       fail-fast: false
       matrix:
-        ruby_version:
-        - 2.5
+        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:
-    - uses: actions/checkout@v2
-      with:
-        fetch-depth: 5
-    - name: "Set up Ruby ${{ matrix.ruby_version }}"
-      uses: ruby/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby_version }}
-        bundler-cache: true
-    - name: Run RuboCop
-      run: bash script/fmt
-
-  profile_docs:
-    if: "!contains(github.event.commits[0].message, '[ci skip]')"
-    name: 'Profile Docs Site (Ruby ${{ matrix.ruby_version }})'
-    runs-on: 'ubuntu-latest'
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby_version:
-        - 2.4 # Minimum required Ruby version in gemspec
-    steps:
-    - uses: actions/checkout@v2
-      with:
-        fetch-depth: 5
-    - name: "Set up Ruby ${{ matrix.ruby_version }}"
-      uses: actions/setup-ruby@v1
-      with:
-        ruby-version: ${{ matrix.ruby_version }}
-    - name: Cache dependencies
-      uses: actions/cache@v1
-      with:
-        path: vendor/bundle
-        key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-gems-
-    - name: 'Update Rubygems and Bundler'
-      run: |
-        gem update --system --no-document
-        gem update bundler --no-document
-    - name: Set up bundle
-      run: |
-        bundle config path vendor/bundle
-        bundle install --jobs 4 --retry 3
-    - name: Build Docs site with --profile
-      run: bash script/profile-docs
-    - name: Profile memory usage of building Docs site
-      run: bash script/memprof
+      - 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

@@ -12,23 +12,16 @@ 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@v2
-      - uses: actions/setup-ruby@v1
+      - uses: actions/checkout@v3
+      - uses: ruby/setup-ruby@v1
         with:
           ruby-version: ${{ env.RUBY_VERSION }}
-      - name: Setup cache for Bundler
-        id: cache
-        uses: actions/cache@v2
-        with:
-          path: vendor/bundle
-          key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-gems-
-      - name: Set up dependencies
-        run: |
-          bundle install --path=vendor/bundle --jobs 4 --retry 3
-          bundle clean
+          bundler-cache: true
       - name: Clone target branch
         run: |
           REMOTE_BRANCH="${REMOTE_BRANCH:-gh-pages}"

.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

@@ -11,35 +11,27 @@ 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@v2
+      uses: actions/checkout@v3
       with:
         fetch-depth: 5
         path: jekyll
     - name: Checkout Third-Party Repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
       with:
         repository: ashmaroli/tomjoht.github.io
         path: sandbox
     - name: Set up Ruby
-      uses: actions/setup-ruby@v1
+      uses: ruby/setup-ruby@v1
       with:
         ruby-version: 2.7
-    - name: Set up Dependencies Cache
-      uses: actions/cache@v1
-      with:
-        path: sandbox/vendor/bundle
-        key: ubuntu-latest-gems-${{ hashFiles('**/Gemfile.lock') }}
-        restore-keys: |
-          ubuntu-latest-gems-
-    - name: Set up Dependencies
-      run: |
-        gem update --system --no-document
-        gem update bundler --no-document
-        bundle config gemfile sandbox/Gemfile
-        bundle config path vendor/bundle
-        bundle install --jobs 4 --retry 3
+        bundler-cache: true
     - name: Run Jekyll Build 3 times
       run: |
         bundle exec jekyll build -s sandbox -d sandbox/_site --trace

.rubocop.yml

@@ -2,7 +2,10 @@
 inherit_from: .rubocop_todo.yml
 
 require:
+  - rubocop-minitest
   - rubocop-performance
+  - rubocop-rake
+  - rubocop-rspec
   - ./rubocop/jekyll
 
 Jekyll/NoPutsAllowed:
@@ -10,7 +13,7 @@ Jekyll/NoPutsAllowed:
     - rake/*.rake
 
 AllCops:
-  TargetRubyVersion: 2.4
+  TargetRubyVersion: 2.7
   Include:
     - lib/**/*.rb
     - test/**/*.rb
@@ -22,6 +25,8 @@ AllCops:
     - vendor/**/*
     - tmp/**/*
 
+Gemspec/DateAssignment:
+  Enabled: true
 Layout/BeginEndAlignment:
   Enabled: true
 Layout/EmptyComment:
@@ -30,14 +35,14 @@ Layout/EmptyLinesAroundAttributeAccessor:
   Enabled: true
 Layout/EndAlignment:
   Severity: error
-Layout/HashAlignment:
-  EnforcedHashRocketStyle: table
-Layout/IndentationWidth:
-  Severity: error
 Layout/FirstArrayElementIndentation:
   EnforcedStyle: consistent
 Layout/FirstHashElementIndentation:
   EnforcedStyle: consistent
+Layout/HashAlignment:
+  EnforcedHashRocketStyle: table
+Layout/IndentationWidth:
+  Severity: error
 Layout/LineLength:
   Exclude:
     - !ruby/regexp /features\/.*.rb/
@@ -52,17 +57,23 @@ 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:
@@ -71,10 +82,10 @@ Lint/DuplicateElsifCondition:
   Enabled: true
 Lint/DuplicateRegexpCharacterClassElement:
   Enabled: true
-Lint/DuplicateRescueException:
-  Enabled: true
 Lint/DuplicateRequire:
   Enabled: true
+Lint/DuplicateRescueException:
+  Enabled: true
 Lint/EmptyBlock:
   Enabled: true
 Lint/EmptyClass:
@@ -89,6 +100,8 @@ Lint/HashCompareByIdentity:
   Enabled: true
 Lint/IdentityComparison:
   Enabled: true
+Lint/LambdaWithoutLiteralBlock:
+  Enabled: true
 Lint/MissingSuper:
   Enabled: false
 Lint/MixedRegexpCaptureTypes:
@@ -98,22 +111,34 @@ Lint/NestedPercentLiteral:
     - test/test_site.rb
 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
 Lint/TopLevelReturnWithArgument:
   Enabled: true
 Lint/TrailingCommaInAttributeDeclaration:
   Enabled: true
+Lint/TripleQuotes:
+  Enabled: true
+Lint/UnexpectedBlockArity:
+  Enabled: true
 Lint/UnmodifiedReduceAccumulator:
   Enabled: true
 Lint/UnreachableCode:
@@ -154,14 +179,43 @@ Metrics/MethodLength:
   Max: 20
   Severity: error
 Metrics/ModuleLength:
-  Max: 240
   Exclude:
     - lib/jekyll/filters.rb
+  Max: 240
 Metrics/ParameterLists:
   Max: 4
 Metrics/PerceivedComplexity:
   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:
@@ -216,22 +270,24 @@ Security/YAMLLoad:
     - !ruby/regexp /features\/.*.rb/
     - !ruby/regexp /test\/.*.rb$/
 
-Style/ArgumentsForwarding:
-  Enabled: false
-Style/ArrayCoercion:
-  Enabled: true
 Style/AccessModifierDeclarations:
   Enabled: false
 Style/AccessorGrouping:
-  Enabled: false
+  Enabled: true
 Style/Alias:
   EnforcedStyle: prefer_alias_method
 Style/AndOr:
   Severity: error
+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
@@ -241,16 +297,18 @@ Style/CollectionCompact:
   Enabled: true
 Style/CombinableLoops:
   Enabled: true
-Style/Documentation:
-  Enabled: false
 Style/DocumentDynamicEvalDefinition:
   Enabled: true
+Style/Documentation:
+  Enabled: false
 Style/DoubleNegation:
   Enabled: false
-Style/ExponentialNotation:
+Style/EndlessMethod:
   Enabled: true
 Style/ExplicitBlockArgument:
   Enabled: false
+Style/ExponentialNotation:
+  Enabled: true
 Style/FormatStringToken:
   Exclude:
     - lib/jekyll/utils/ansi.rb
@@ -264,8 +322,12 @@ 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:
@@ -275,6 +337,8 @@ Style/HashTransformKeys:
   Enabled: false
 Style/HashTransformValues:
   Enabled: true
+Style/IfWithBooleanLiteralBranches:
+  Enabled: true
 Style/KeywordParametersOrder:
   Enabled: true
 Style/MixinUsage:
@@ -292,13 +356,13 @@ 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:
@@ -328,13 +392,13 @@ Style/SlicingWithRange:
   Enabled: false
 Style/SoleNestedConditional:
   Enabled: true
-Style/StringLiterals:
-  EnforcedStyle: double_quotes
 Style/StringConcatenation:
   Enabled: true
   Exclude:
     - lib/jekyll/commands/*.rb
     - test/**/*.rb
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
 Style/StringLiteralsInInterpolation:
   EnforcedStyle: double_quotes
 Style/SwapValues:

.rubocop_todo.yml

@@ -1,11 +1,17 @@
 # This configuration was generated by
 # `rubocop --auto-gen-config --auto-gen-only-exclude`
-# on 2020-11-23 15:56:48 UTC using RuboCop version 1.4.0.
+# 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:
@@ -17,9 +23,3 @@ Style/CombinableLoops:
 Style/OptionalBooleanParameter:
   Exclude:
     - 'lib/jekyll/log_adapter.rb'
-
-# Offense count: 1
-# Configuration parameters: Methods.
-Style/RedundantArgument:
-  Exclude:
-    - 'lib/jekyll/tags/link.rb'

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

@@ -5,6 +5,10 @@ gemspec :name => "jekyll"
 
 gem "rake", "~> 13.0"
 
+if ENV["LIQUID_VERSION"] && ENV["LIQUID_VERSION"] != ""
+  gem "liquid", ENV["LIQUID_VERSION"]
+end
+
 group :development do
   gem "launchy", "~> 2.3"
   gem "pry"
@@ -23,14 +27,21 @@ group :test do
   gem "nokogiri", "~> 1.7"
   gem "rspec"
   gem "rspec-mocks"
-  gem "rubocop", "~> 1.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
 
 #
@@ -66,8 +77,9 @@ 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 "rdoc", "~> 6.3.0"
   gem "tomlrb"
 
   platforms :ruby, :mswin, :mingw, :x64_mingw do
@@ -79,7 +91,7 @@ group :jekyll_optional_dependencies do
   # Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
   # and associated library
   platforms :jruby, :mswin, :mingw, :x64_mingw do
-    gem "tzinfo", "~> 1.2"
+    gem "tzinfo", ENV["TZINFO_VERSION"] if ENV["TZINFO_VERSION"]
     gem "tzinfo-data"
   end
 end

History.markdown

@@ -1,9 +1,154 @@
+## 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)
-  * Supress warning issued for redirect pages (#8347)
+  * 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)
@@ -247,7 +392,7 @@
   * 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)
+  * Add GitLab Pages to 3rd party list (#8191)
   * docs: add 21yunbox for deployment (#8193)
   * Improve documentation on tags and categories (#8196)
 
@@ -294,6 +439,25 @@
 
   * 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
@@ -557,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)
@@ -572,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)
@@ -723,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)
@@ -879,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)
@@ -995,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)
@@ -1043,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)
 
@@ -1513,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)
@@ -1539,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)
@@ -1588,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)
@@ -1686,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)
@@ -1694,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)
@@ -1849,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)
@@ -2184,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)
@@ -3179,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)
@@ -3332,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

@@ -3,12 +3,10 @@
 [![Gem Version](https://img.shields.io/gem/v/jekyll.svg)][ruby-gems]
 [![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]
-[![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
-[hakiri]: https://hakiri.io/github/jekyll/jekyll/master
 [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
 
@@ -18,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
 
@@ -26,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
 
@@ -45,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
@@ -58,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
 

appveyor.yml

@@ -14,6 +14,10 @@ environment:
   BUNDLE_WITHOUT: "benchmark:development"
   matrix:
     - 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"
@@ -22,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

@@ -34,7 +34,7 @@ puts "  #{'where + first'.cyan} results in #{TEMPLATE_1.render(SITE.site_payload
 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! Procceding to run benchmarks.'.green
+  puts 'Success! Proceeding to run benchmarks.'.green
   puts ''
 else
   puts 'Something went wrong. Aborting.'.magenta

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/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

docs/_config.yml

@@ -1,5 +1,5 @@
 ---
-version: 4.2.0
+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

docs/_data/config_options/build.yml

@@ -20,7 +20,7 @@
 - name: Layouts
   description: >-
     Specify layout directory instead of using <code>_layouts/</code> automatically.
-  option: "layout_dir: DIR"
+  option: "layouts_dir: DIR"
   flag: --layouts DIR
 
 
@@ -55,7 +55,7 @@
   flag: --lsi
 
 
-- name: Limit Posts
+- name: Limit posts
   description: Limit the number of posts to parse and publish.
   option: "limit_posts: NUM"
   flag: --limit_posts NUM
@@ -69,31 +69,44 @@
 
 - name: Verbose output
   description: Print verbose output.
+  option: "verbose: BOOL"
   flag: -V, --verbose
 
 
-- name: Silence Output
+- 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 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.
+    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
+- 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

docs/_data/config_options/global.yml

@@ -1,10 +1,10 @@
-- name: Site Source
+- name: Site source
   description: Change the directory where Jekyll will read files
   option: "source: DIR"
   flag: -s, --source DIR
 
 
-- name: Site Destination
+- name: Site destination
   description: Change the directory where Jekyll will write files
   option: "destination: DIR"
   flag: -d, --destination DIR
@@ -17,7 +17,7 @@
   flag: --safe
 
 
-- name: Disable Disk Cache
+- 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
@@ -57,7 +57,7 @@
   option: "keep_files: [DIR, FILE, ...]"
 
 
-- name: Time Zone
+- 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

docs/_data/config_options/serve.yml

@@ -1,28 +1,28 @@
-- name: Local Server Port
-  description: Listen on the given port.
+- 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.
+- name: Local server hostname
+  description: Listen at the given hostname. The default is `localhost`.
   option: "host: HOSTNAME"
   flag: "-H, --host HOSTNAME"
 
 
-- name: Live Reload
+- 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
+- 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
+- name: Live reload min/max delay
   description: Minimum/Maximum delay before automatically reloading page.
   options:
     - "livereload_min_delay: SECONDS"
@@ -32,7 +32,7 @@
     - "--livereload-max-delay SECONDS"
 
 
-- name: Live Reload Port
+- name: Live reload port
   description: Port for LiveReload to listen on.
   flag: "--livereload-port PORT"
 
@@ -55,17 +55,17 @@
   flag: "--skip-initial-build"
 
 
-- name: Show Directory Listing
+- 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
+- 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
+- name: X.509 (SSL) certificate
   description: "SSL Public certificate, stored or symlinked in the site source."
   flag: "--ssl-cert"

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'

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
@@ -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/ruby.yml

@@ -1,3 +1,3 @@
 min_version: 2.5.0
-current_version: 2.7.2
-current_version_output: ruby 2.7.2p137 (2020-10-01 revision 5445e04352)
+current_version: 3.1.1
+current_version_output: ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236)

docs/_data/showcase.yml

@@ -72,13 +72,6 @@
     - software
     - blog
 
-- name: AWS Amplify
-  url: https://aws-amplify.github.io/
-  image: amplify-framework.png
-  categories:
-    - open-source
-    - marketing-site
-
 - name: Freedom of Information Act
   url: https://www.foia.gov/
   image: foia-gov.png
@@ -299,7 +292,7 @@
     - software
     - marketing-site
 
-- name: Ionic Framwork
+- name: Ionic Framework
   url: https://ionicframework.com/
   image: ionic-framework.png
   categories:

docs/_docs/assets.md

@@ -79,6 +79,8 @@ 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
 
 To enable Coffeescript in Jekyll 3.0 and up you must

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,8 +16,8 @@ collections:
   - staff_members
 ```
 
-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:
+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:

docs/_docs/community/community.md

@@ -10,13 +10,20 @@ As contributors and maintainers of this project, and in the interest of fosterin
 
 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]({{ '/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 who are willing to point you in the right direction.
 

docs/_docs/configuration.md

@@ -14,5 +14,6 @@ executable in the terminal.
 * [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

@@ -10,7 +10,7 @@ file or on the command-line.
 <div class="note info">
   <h5>Be aware of directory paths</h5>
   <p>
-    Make directory path values in configuration keys like `plugins_dir` relative to the current working directory, not the site source. 
+    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>
 

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' | relative_url }}">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>
 

docs/_docs/configuration/liquid.md

@@ -23,8 +23,8 @@ 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:
 

docs/_docs/configuration/markdown.md

@@ -5,61 +5,64 @@ 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:
 
-### Example Usage
 ```yaml
 kramdown:
-  html_to_native: true
+  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).
 

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,26 +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
 
-Since v2, CircleCI is a Docker-based system. The example `circle.yml` below demonstrates how to
+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
-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:
@@ -105,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:
@@ -119,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

@@ -6,13 +6,12 @@ When building a Jekyll site with GitHub Pages, the standard flow is restricted f
 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 `4.0.0`, or point directly to the repository.
+  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.
@@ -25,16 +24,15 @@ with GitHub Pages you can use GitHub Actions.
 - **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
+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 `master` branch in this page. Therefore, ensure that you
-are working on the `master` 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
+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}
@@ -53,6 +51,7 @@ title: "Jekyll Actions Demo"
 ```
 
 {% raw %}
+
 ```liquid
 ---
 ---
@@ -64,15 +63,15 @@ Welcome to My Home Page
 - Original date - {{ date }}
 - With timeago filter - {{ date | timeago }}
 ```
-{% endraw %}
 
+{% endraw %}
 
 ```ruby
 # Gemfile
 
 source 'https://rubygems.org'
 
-gem 'jekyll', '~> 4.0'
+gem 'jekyll', '~> 4.2'
 
 group :jekyll_plugins do
   gem 'jekyll-timeago', '~> 0.13.1'
@@ -93,51 +92,62 @@ 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). Here we shall employ
-[Jekyll Actions][jekyll-actions] from the Marketplace for its simplicity.
+`.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:
-      - master
+      - main # or master before October 2020
 
 jobs:
   github-pages:
-    runs-on: ubuntu-16.04
+    runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v2
-      - uses: helaili/jekyll-action@2.0.1
-        env:
-          JEKYLL_PAT: ${{ secrets.JEKYLL_PAT }}
+      - 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 `master` branch only --- this prevents
+- 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.
-- We specify our selected **action** and **version number** using `helaili/jekyll-action@2.0.0`.
-  This handles the build and deploy.
-- We set a reference to a secret **environment variable** for the action to use. The `JEKYLL_PAT`
-  is a *Personal Access Token* and is detailed in the next section.
+- 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 
+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 * * *'
+    - cron: "0 0 * * *"
 ```
 
 Note that this string must be quoted to prevent the asterisks from being evaluated incorrectly.
@@ -145,12 +155,18 @@ Note that this string must be quoted to prevent the asterisks from being evaluat
 [on.schedule]: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#onschedule
 [crontab guru]: https://crontab.guru/
 
-
 ### Providing permissions
 
-The action needs permissions to push to your `gh-pages` branch. So you need to create a GitHub
-**authentication token** on your GitHub profile, then set it as an environment variable in your
-build using _Secrets_:
+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.
@@ -159,23 +175,23 @@ build using _Secrets_:
    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 `JEKYLL_PAT` (*important*). Give it a value using the value copied
+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 `master`, the action will be triggered and the build will
+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.
+  - 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.
+  - 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.
@@ -204,10 +220,13 @@ successful deploy from the Action.
 - [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/datafiles.md

@@ -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
@@ -148,3 +148,30 @@ 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/' | 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/automated.md

@@ -19,6 +19,7 @@ We have guides for the following providers:
 * [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
 

docs/_docs/deployment/manual.md

@@ -25,7 +25,7 @@ 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
 

docs/_docs/deployment/third-party.md

@@ -4,12 +4,6 @@ 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.
@@ -55,7 +49,11 @@ Read this [Jekyll step-by-step guide](https://www.netlify.com/blog/2020/04/02/a-
 
 ## Render
 
-[Render](https://render.com) provides zero config continuous deployment for static sites. The service is free under 100GB monthly bandwith.
+[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
 
@@ -70,3 +68,7 @@ Read this [Jekyll step-by-step guide](https://www.netlify.com/blog/2020/04/02/a-
 [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/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>
@@ -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,7 +95,7 @@ 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">
@@ -138,3 +118,14 @@ to see more detailed examples.
     <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,32 @@ 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}
 
@@ -11,7 +37,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 {: #minor-enhancements-v4-2-0}
 
 - Warn on command-line with permalink conflict ([#8342]({{ site.repository }}/issues/8342))
-- Supress warning issued for redirect pages ([#8347]({{ site.repository }}/issues/8347))
+- 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))
@@ -268,7 +294,7 @@ note: This file is autogenerated. Edit /History.markdown instead.
 - 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))
+- 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))
 
@@ -322,6 +348,32 @@ 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}
 
@@ -596,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))
@@ -611,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))
@@ -787,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))
@@ -962,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))
@@ -1093,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))
@@ -1150,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))
 
@@ -1663,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))
@@ -1689,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))
@@ -1741,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))
@@ -1840,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))
@@ -1848,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))
@@ -2029,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))
@@ -2387,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))
@@ -3513,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))
@@ -3688,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/index.md

@@ -24,23 +24,26 @@ See [Requirements]({{ '/docs/installation/#requirements' | relative_url }}) for
 
 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`.
-```
+```sh
 jekyll new myblog
 ```
 4. Change into your new directory.
-```
+```sh
 cd myblog
 ```
 5. Build the site and make it available on a local server.
-```
+```sh
 bundle exec jekyll serve
 ```
 6. Browse to [http://localhost:4000](http://localhost:4000){:target="_blank"}
 
+{: .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`
 

docs/_docs/installation/macos.md

@@ -3,148 +3,90 @@ title: Jekyll on macOS
 permalink: /docs/installation/macos/
 ---
 
-## Install Command Line Tools
-To install the command line tools 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 v{{ site.data.ruby.min_version }}** or higher.
-macOS Catalina 10.15 ships with Ruby 2.6.3. Check your Ruby version using `ruby -v`.
+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/).
 
-If you're running a previous version of macOS, you'll have to install a newer version of Ruby.
+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.
 
-### With Homebrew {#brew}
-To run the latest Ruby version you need to install it through [Homebrew](https://brew.sh).
+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
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
-
-# Install Ruby
-brew install ruby
 ```
 
-Add the brew ruby path to your shell configuration:
+### Step 2: Install chruby and the latest Ruby with ruby-install
 
-```bash
-# If you're using Zsh
-echo 'export PATH="/usr/local/opt/ruby/bin:$PATH"' >> ~/.zshrc
-
-# If you're using Bash
-echo 'export PATH="/usr/local/opt/ruby/bin:$PATH"' >> ~/.bash_profile
-
-# Unsure which shell you are using? Type
-echo $SHELL
-```
-
-Relaunch your terminal and check your 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 }}
 ```
 
-You're now running the current stable version of 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
-/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
-
-# Install rbenv and ruby-build
-brew install rbenv
-
-# Set up rbenv integration with your shell
-rbenv init
-
-# Check your installation
-curl -fsSL https://github.com/rbenv/rbenv-installer/raw/master/bin/rbenv-doctor | bash
-```
-
-Restart your terminal to apply your changes.
-Next, you can install the Ruby version you want. Let's install the latest stable version:
-
-```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 to [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
 
-After installing Ruby, install Jekyll and Bundler.
-
-### Local Install
-
-Install the bundler and jekyll gems:
+After installing Ruby with chruby, install the latest Jekyll gem:
 
 ```sh
-gem install --user-install bundler jekyll
-```
-
-Get your Ruby version:
-
-```sh
-ruby -v
-{{ site.data.ruby.current_version_output }}
-```
-
-Append your path file with the following, replacing the `X.X` with the first two digits of your Ruby version:
-
-```bash
-# If you're using Zsh
-echo 'export PATH="$HOME/.gem/ruby/X.X.0/bin:$PATH"' >> ~/.zshrc
-
-# If you're using Bash
-echo 'export PATH="$HOME/.gem/ruby/X.X.0/bin:$PATH"' >> ~/.bash_profile
-
-# Unsure which shell you are using? Type
-echo $SHELL
-```
-
-Check that `GEM PATHS:` points to your home directory:
-
-```sh
-gem env
-```
-
-{: .note .info}
-Every time you update Ruby to a version in which the first two digits change, update your path to match.
-
-### Global Install
-
-{: .note .warning}
-We recommend not installing Ruby gems globally to avoid file permissions problems and using `sudo`.
-
-#### On Mojave (10.14)
-
-Because of SIP Protections in Mojave, run:
-
-```sh
-sudo gem install bundler
-sudo gem install -n /usr/local/bin/ jekyll
-```
-
-#### Before Mojave (<10.14)
-
-Run:
-
-```sh
-sudo gem install bundler jekyll
+gem install jekyll
 ```
 
 ## Troubleshooting

docs/_docs/installation/other-linux.md

@@ -47,6 +47,7 @@ sudo pacman -S ruby base-devel
 
 ```sh
 sudo zypper install -t pattern devel_ruby devel_C_C++
+sudo zypper install ruby-devel
 ```
 
 ### Clear Linux

docs/_docs/installation/windows.md

@@ -29,7 +29,7 @@ We only cover RubyInstaller-2.4 and newer here. Older versions need to
 4. Check if Jekyll has been installed properly: `jekyll -v`
 
 {: .note .info}
-You may receive an error when checking if Jekyll has been installed properly. Reboot your system and run `jekyll -v` again.
+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!
@@ -42,7 +42,7 @@ If you are using Windows 10 version 1607 or later, another option to run Jekyll
 {: .note .info}
 You must have [Windows Subsystem for Linux](https://msdn.microsoft.com/en-us/commandline/wsl/about) enabled.
 
-Make sure all your packages and repositories are up to date. Open a new Command Prompt or Powershell window and type `bash`.
+Make sure all your packages and repositories are up to date. Open a new Command Prompt or PowerShell window and type `bash`.
 
 Your terminal should now be a Bash instance. Next, update your repository lists and packages:
 
@@ -97,7 +97,7 @@ 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. If they don't, Jekyll will break. 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. Run the following:
@@ -121,22 +121,14 @@ While 'new' blogs created with Jekyll v3.4 and greater, will have the following
 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>
-    Version 2.0 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 version 1.2 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/maintaining/becoming-a-maintainer.md

@@ -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

@@ -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

@@ -9,7 +9,7 @@ title: "Merging a Pull Request"
 
 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
 

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.
+**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.

docs/_docs/pages.md

@@ -33,7 +33,7 @@ If you have a lot of pages, you can organize them into subfolders. The same subf
 
 ## Changing the output URL
 
-You might want to have a particular folder structure for your source files that changes for the built site. With [permalinks](/docs/permalinks) you have full control of the output URL.
+You might want to have a particular folder structure for your source files that changes for the built site. With [permalinks](/docs/permalinks/) you have full control of the output URL.
 
 ## Excerpts for pages
 

docs/_docs/permalinks.md

@@ -229,7 +229,7 @@ Here's the full list of placeholders available:
       <td>
         <p>
             Title from the document’s filename. May be overridden via
-            the document’s <code>slug</code> front matter.
+            the document’s <code>slug</code> front matter. Preserves case from the source.
         </p>
       </td>
     </tr>
@@ -409,6 +409,7 @@ Collections have the following placeholders available:
           variable value if any is present in the document; if none is
           defined then <code>:title</code> will be equivalent to
           <code>:name</code>, aka the slug generated from the filename.
+          Preserves case from the source.
         </p>
       </td>
     </tr>

docs/_docs/plugins/filters.md

@@ -19,6 +19,8 @@ end
 Liquid::Template.register_filter(Jekyll::AssetFilter)
 ```
 
+For more details on creating custom Liquid Filters, head to the [Liquid docs](https://github.com/Shopify/liquid/wiki/Liquid-for-Programmers#create-your-own-filters).
+
 <div class="note">
   <h5>ProTip™: Access the site object using Liquid</h5>
   <p>

docs/_docs/plugins/generators.md

@@ -3,36 +3,34 @@ title: Generators
 permalink: /docs/plugins/generators/
 ---
 
-You can create a generator when you need Jekyll to create additional content
-based on your own rules.
+You can create a generator when you need Jekyll to create additional content based on your own rules.
 
-A generator is a subclass of `Jekyll::Generator` that defines a `generate`
-method, which receives an instance of
-[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb). The
-return value of `generate` is ignored.
+A generator is a subclass of `Jekyll::Generator` that defines a `generate` method, which receives an instance of
+[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb). The return value of `generate` is ignored.
 
-Generators run after Jekyll has made an inventory of the existing content, and
-before the site is generated. Pages with front matter are stored as
-instances of
-[`Jekyll::Page`]({{ site.repository }}/blob/master/lib/jekyll/page.rb)
-and are available via `site.pages`. Static files become instances of
+Generators run after Jekyll has made an inventory of the existing content, and before the site is generated. Pages with
+front matter are stored as instances of [`Jekyll::Page`]({{ site.repository }}/blob/master/lib/jekyll/page.rb) and are
+available via `site.pages`. Static files become instances of
 [`Jekyll::StaticFile`]({{ site.repository }}/blob/master/lib/jekyll/static_file.rb)
-and are available via `site.static_files`. See
-[the Variables documentation page](/docs/variables/) and
-[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb)
-for details.
+and are available via `site.static_files`. See [the Variables documentation page](/docs/variables/) and
+[`Jekyll::Site`]({{ site.repository }}/blob/master/lib/jekyll/site.rb) for details.
 
-For instance, a generator can inject values computed at build time for template
-variables. In the following example, the template `reading.html` has two
-variables `ongoing` and `done` that are filled in the generator:
+In the following example, the generator will inject values computed at build time for template variables. The template
+named `reading.html` has two undefined variables `ongoing` and `done` that will be defined or assigned a value when
+the generator runs:
 
 ```ruby
 module Reading
   class Generator < Jekyll::Generator
     def generate(site)
-      ongoing, done = Book.all.partition(&:ongoing?)
+      book_data = site.data['books']
+      ongoing = book_data.select { |book| book['status'] == 'ongoing' }
+      done = book_data.select { |book| book['status'] == 'finished' }
 
-      reading = site.pages.detect {|page| page.name == 'reading.html'}
+      # get template
+      reading = site.pages.find { |page| page.name == 'reading.html'}
+
+      # inject data into template
       reading.data['ongoing'] = ongoing
       reading.data['done'] = done
     end
@@ -40,42 +38,80 @@ module Reading
 end
 ```
 
-The following example is a more complex generator that generates new pages. In this example, the generator will create a series of files under the `categories` directory for each category, listing the posts in each category using the `category_index.html` layout.
+The following example is a more complex generator that generates new pages.
+
+In this example, the aim of the generator is to create a page for each category registered in the `site`. The pages are
+created at runtime, so their contents, front matter and other attributes need to be designed by the plugin itself.
+* The pages are intended to render a list of all documents under a given category. So the basename of the rendered file
+would be better as `index.html`.
+* Having the ability to configure the pages via [front matter defaults](/docs/configuration/front-matter-defaults/)
+would be awesome! So assigning a particular `type` to these pages would be beneficial.
 
 ```ruby
-module Jekyll
-  class CategoryPageGenerator < Generator
+module SamplePlugin
+  class CategoryPageGenerator < Jekyll::Generator
     safe true
 
     def generate(site)
-      if site.layouts.key? 'category_index'
-        dir = site.config['category_dir'] || 'categories'
-        site.categories.each_key do |category|
-          site.pages << CategoryPage.new(site, site.source, File.join(dir, category), category)
-        end
+      site.categories.each do |category, posts|
+        site.pages << CategoryPage.new(site, category, posts)
       end
     end
   end
 
-  # A Page subclass used in the `CategoryPageGenerator`
-  class CategoryPage < Page
-    def initialize(site, base, dir, category)
-      @site = site
-      @base = base
-      @dir  = dir
-      @name = 'index.html'
+  # Subclass of `Jekyll::Page` with custom method definitions.
+  class CategoryPage < Jekyll::Page
+    def initialize(site, category, posts)
+      @site = site             # the current site instance.
+      @base = site.source      # path to the source directory.
+      @dir  = category         # the directory the page will reside in.
 
-      self.process(@name)
-      self.read_yaml(File.join(base, '_layouts'), 'category_index.html')
-      self.data['category'] = category
+      # All pages have the same filename, so define attributes straight away.
+      @basename = 'index'      # filename without the extension.
+      @ext      = '.html'      # the extension.
+      @name     = 'index.html' # basically @basename + @ext.
 
-      category_title_prefix = site.config['category_title_prefix'] || 'Category: '
-      self.data['title'] = "#{category_title_prefix}#{category}"
+      # Initialize data hash with a key pointing to all posts under current category.
+      # This allows accessing the list in a template via `page.linked_docs`.
+      @data = {
+        'linked_docs' => posts
+      }
+
+      # Look up front matter defaults scoped to type `categories`, if given key
+      # doesn't exist in the `data` hash.
+      data.default_proc = proc do |_, key|
+        site.frontmatter_defaults.find(relative_path, :categories, key)
+      end
+    end
+
+    # Placeholders that are used in constructing page URL.
+    def url_placeholders
+      {
+        :category   => @dir,
+        :basename   => basename,
+        :output_ext => output_ext,
+      }
     end
   end
 end
 ```
 
+The generated pages can now be set up to use a particular layout or output at a particular path in the destination
+directory all via the config file using front matter defaults. For example:
+
+```yaml
+# _config.yml
+
+defaults:
+  - scope:
+      type: categories  # select all category pages
+    values:
+      layout: category_page
+      permalink: categories/:category/
+```
+
+## Technical Aspects
+
 Generators need to implement only one method:
 
 <div class="mobile-side-scroller">
@@ -99,6 +135,10 @@ Generators need to implement only one method:
 </table>
 </div>
 
-If your generator is contained within a single file, it can be named whatever you want but it should have an `.rb` extension. If your generator is split across multiple files, it should be packaged as a Rubygem to be published at https://rubygems.org/. In this case, the name of the gem depends on the availability of the name at that site because no two gems can have the same name.
+If your generator is contained within a single file, it can be named whatever you want but it should have an `.rb`
+extension. If your generator is split across multiple files, it should be packaged as a Rubygem to be published at
+https://rubygems.org/. In this case, the name of the gem depends on the availability of the name at that site because
+no two gems can have the same name.
 
-By default, Jekyll looks for generators in the `_plugins` directory. However, you can change the default directory by assigning the desired name to the key `plugins_dir` in the config file.
+By default, Jekyll looks for generators in the `_plugins` directory. However, you can change the default directory by
+assigning the desired name to the key `plugins_dir` in the config file.

docs/_docs/plugins/hooks.md

@@ -249,7 +249,7 @@ The complete list of available hooks:
 ## Hooks for custom Jekyll objects
 
 You can also register and trigger hooks for Jekyll objects introduced by your plugin. All it takes is placing `trigger` calls under a suitable
-`owner` name, at positons desired within your custom class and registering the `owner` by your plugin.
+`owner` name, at positions desired within your custom class and registering the `owner` by your plugin.
 
 To illustrate, consider the following plugin that implements custom functionality for every custom `Excerpt` object initialized:
 

docs/_docs/plugins/installation.md

@@ -3,77 +3,123 @@ title: Plugins
 permalink: /docs/plugins/installation/
 ---
 
-You have 3 options for installing plugins:
+Jekyll has built-in support for using plugins to extend the core functionality.
 
-1. In your site source root, make a `_plugins` directory. Place your plugins
-   here. Any file ending in `*.rb` inside this directory will be loaded before
-   Jekyll generates your site.
+Primarily, any file with extension `.rb` placed within a `_plugins` directory at the root of the site's `source`, will be automatically loaded
+during a build session.
 
-2. In your `_config.yml` file, add a new array with the key `plugins` (or `gems` for Jekyll < `3.5.0`) and the
-   values of the gem names of the plugins you'd like to use. An example:
+This behavior can be configured as follows:
 
-   ```yaml
-   # This will require each of these plugins automatically.
-   plugins:
-     - jekyll-gist
-     - jekyll-coffeescript
-     - jekyll-assets
-     - another-jekyll-plugin
-   ```
+- The `_plugins` directory may be changed either directly via the command-line or via the configuration file(s).
+- Plugins in the `_plugins` directory (or its equivalent(s)) will not be loaded when Jekyll is running in `safe` mode.
+- This route cannot be used to extend the Jekyll CLI.
 
-   Then install your plugins using `gem install jekyll-gist jekyll-coffeescript jekyll-assets another-jekyll-plugin`
+To work with plugins packaged as gems, one has to list the desired gems in the configuration file under a top-level key named `plugins`.
+Additionally, if you're building in `safe` mode, the gem needs to be listed under a top-level key named `whitelist`. For example:
 
-3. Add the relevant plugins to a Bundler group in your `Gemfile`. An
-   example:
+```yaml
+plugins:
+  - jekyll-gist
+  - jekyll-coffeescript
+  - jekyll-seo-tag
+  - some-other-jekyll-plugin
 
-   ```ruby
-   group :jekyll_plugins do
-     gem "jekyll-gist"
-     gem "jekyll-coffeescript"
-     gem "jekyll-assets"
-     gem "another-jekyll-plugin"
-   end
-   ```
+# Enable safe mode
+safe: true
 
-   Now you need to install all plugins from your Bundler group by running single command `bundle install`.
+# Whitelist plugins under safe mode.
+# Note that `some-other-jekyll-plugin` is not listed here. Therefore,
+# it will not be loaded under safe mode.
+whitelist:
+  - jekyll-gist
+  - jekyll-coffeescript
+  - jekyll-seo-tag
+```
+
+In the absence of a Gemfile, one must manually ensure that listed plugins have been installed prior to invoking Jekyll. For example, the
+latest versions of gems in the above list may be installed to a system-wide location by running:
+
+```sh
+gem install jekyll-gist jekyll-coffeescript jekyll-remote-theme some-other-jekyll-plugin
+```
+
+## Using a Gemfile
+
+The maintenance of various gem dependencies may be greatly simplified by using a Gemfile (usually at the root of the site's source) in
+conjunction with a Rubygem named `bundler`. The Gemfile however **should** list all the primary dependencies of your site, including Jekyll
+itself, not just gem-based plugins of the site because Bundler narrows the scope of installed gems to just *runtime dependencies* resolved by
+evaluating the Gemfile. For example:
+
+```ruby
+source "https://rubygems.org"
+
+# Use the latest version.
+gem "jekyll"
+
+# The theme of current site, locked to a certain version.
+gem "minima", "2.4.1"
+
+# Plugins of this site loaded during a build with proper
+# site configuration.
+gem "jekyll-gist"
+gem "jekyll-coffeescript"
+gem "jekyll-seo-tag", "~> 1.5"
+gem "some-other-jekyll-plugin"
+
+# A dependency of a custom-plugin inside `_plugins` directory.
+gem "nokogiri", "~> 1.11"
+```
+
+The gems listed in the Gemfile can be collectively installed by simply running `bundle install`.
+
+### The `:jekyll_plugins` Gemfile group
+{: #the-jekyll_plugins-group}
+
+Jekyll gives a special treatment to gems listed as part of the `:jekyll_plugins` group in a Gemfile. Any gem under this group is loaded at
+the very beginning of any Jekyll process, irrespective of the `--safe` CLI flag or entries in the configuration file(s).
+
+While this route allows one to enhance Jekyll's CLI with additional subcommands and options, or avoid having to list gems in the configuration
+file, the downside is the necessity to be mindful of what gems are included in the group. For example:
+
+```ruby
+source "https://rubygems.org"
+
+# Use the latest version.
+gem "jekyll"
+
+# The theme of current site, locked to a certain version.
+gem "minima", "2.4.1"
+
+# Plugins of this site loaded only if configured correctly.
+gem "jekyll-gist"
+gem "jekyll-coffeescript"
+
+# Gems loaded irrespective of site configuration.
+group :jekyll_plugins do
+  gem "jekyll-cli-plus"
+  gem "jekyll-seo-tag", "~> 1.5"
+  gem "some-other-jekyll-plugin"
+end
+```
 
 <div class="note info">
   <h5>Plugins on GitHub Pages</h5>
   <p>
-    <a href="https://pages.github.com/">GitHub Pages</a> is powered by Jekyll.
-    All Pages sites are generated using the <code>--safe</code> option
-    to disable plugins (with the exception of some
-    <a href="https://pages.github.com/versions">whitelisted plugins</a>) for
-    security reasons. Unfortunately, this means
-    your plugins won’t work if you’re deploying to GitHub Pages.<br><br>
-    You can still use GitHub Pages to publish your site, but you’ll need to
-    convert the site locally and push the generated static files to your GitHub
-    repository instead of the Jekyll source files.
+    <a href="https://pages.github.com/">GitHub Pages</a> is powered by Jekyll. All GitHub Pages sites are generated using the
+    <code>--safe</code> option to disable plugins (with the exception of some
+    <a href="https://pages.github.com/versions">whitelisted plugins</a>) for security reasons. Unfortunately, this means your plugins won't
+    work if you’re deploying via GitHub Pages.<br><br>
+    You can still use GitHub Pages to publish your site, but you’ll need to build the site locally and push the generated files to your
+    GitHub repository instead of the Jekyll source files.
   </p>
 </div>
 
 <div class="note">
   <h5>
-    <code>_plugins</code>, <code>_config.yml</code> and <code>Gemfile</code>
-    can be used simultaneously
+    <code>_plugins</code>, <code>_config.yml</code> and <code>Gemfile</code> can be used simultaneously
   </h5>
   <p>
-    You may use any of the aforementioned plugin options simultaneously in the
-    same site if you so choose. Use of one does not restrict the use of the
-    others.
+    You may use any of the aforementioned plugin routes simultaneously in the same site if you so choose.
+    Use of one does not restrict the use of the others.
   </p>
 </div>
-
-### The jekyll_plugins group
-
-Jekyll gives this particular group of gems in your `Gemfile` a different
-treatment. Any gem included in this group is loaded before Jekyll starts
-processing the rest of your source directory.
-
-A gem included here will be activated even if its not explicitly listed under
-the `plugins:` key in your site's config file.
-
-{: .note .warning}
-Gems included in the <code>:jekyll-plugins</code> group are activated
-regardless of the <code>--safe</code> mode setting. Be aware of which
-gems are included under this group!

docs/_docs/security.md

@@ -0,0 +1,36 @@
+---
+title: Security Policy
+permalink: "/docs/security/"
+note: This file is autogenerated. Edit /.github/SECURITY.markdown instead.
+---
+
+## 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.

docs/_docs/step-by-step/01-setup.md

@@ -4,59 +4,58 @@ title: Setup
 menu_name: Step by Step Tutorial
 position: 1
 ---
-Welcome to Jekyll's step-by-step tutorial. The goal of this tutorial is to take
-you from having some front end web development experience to building your
-first Jekyll site from scratch — not relying on the default gem-based theme.
-Let's get into it!
+Welcome to Jekyll's step-by-step tutorial. This tutorial takes
+you from having some front-end web development experience to building your
+first Jekyll site from scratch without relying on the default gem-based theme.
 
 ## Installation
 
-Jekyll is a Ruby program so you need to install Ruby on your machine to begin
-with. Head over to the [install guide](/docs/installation/) and follow the
+Jekyll is a Ruby gem. First, install Ruby on your machine. 
+Go to [Installation]({{ '/docs/installation/' | relative_url }}) and follow the
 instructions for your operating system.
 
-With Ruby setup you can install Jekyll by running the following in your
-terminal:
+With Ruby installed, install Jekyll from the terminal:
 
 ```sh
 gem install jekyll bundler
 ```
 
-To create a new `Gemfile` to list your project's dependencies run:
+Create a new `Gemfile` to list your project's dependencies:
 
 ```sh
 bundle init
 ```
 
-Now edit the `Gemfile` and add jekyll as a dependency:
+Edit the `Gemfile` in a text editor and add jekyll as a dependency:
 
 ```ruby
 gem "jekyll"
 ```
 
-Finally run `bundle` to install jekyll for your project.
+Run `bundle` to install jekyll for your project.
 
 You can now prefix all jekyll commands listed in this tutorial with `bundle exec`
 to make sure you use the jekyll version defined in your `Gemfile`.
 
 ## Create a site
 
-It's time to create a site! Create a new directory for your site, you can name
-it whatever you'd like. Through the rest of this tutorial we'll refer to this
-directory as “root”.
+It's time to create a site! Create a new directory for your site and name
+it whatever you want. Through the rest of this tutorial we'll refer to this
+directory as **root**.
+
+You can also initialize a Git repository here.
 
-If you're feeling adventurous, you can also initialize a Git repository here.
 One of the great things about Jekyll is there's no database. All content and
-site structure are files which a Git repository can version. Using a repository
-is completely optional but it's a great habit to get into. You can learn more
-about using Git by reading through the
+site structure are files that a Git repository can version. Using a repository
+is optional but is recommended. You can learn more
+about using Git by reading the
 [Git Handbook](https://guides.github.com/introduction/git-handbook/).
 
-Let's add your first file. Create `index.html` in the root with the following
+Let's add your first file. Create `index.html` in **root** with the following
 content:
 
 ```html
-<!doctype html>
+<!DOCTYPE html>
 <html>
   <head>
     <meta charset="utf-8">
@@ -70,22 +69,33 @@ content:
 
 ## Build
 
-Jekyll is a static site generator so we need Jekyll to build the site
-before we can view it. There are two commands you can run in the root of your site
-to build it:
+Since Jekyll is a static site generator, it has to build the site
+before we can view it. Run either of the following commands to build your site:
 
 * `jekyll build` - Builds the site and outputs a static site to a directory
 called `_site`.
-* `jekyll serve` - Does the same thing except it rebuilds any time you make
-a change and runs a local web server at `http://localhost:4000`.
+* `jekyll serve` - Does `jekyll build` and runs it on a local web server at `http://localhost:4000`, rebuilding the site any time you make a change.
+
+{: .note .info}
+When you're developing a site, use `jekyll serve`. To force the browser to refresh with every change, use `jekyll serve --livereload`.
+If there's a conflict or you'd like Jekyll to serve your development site at a different URL, use the `--host` and `--port` arguments,
+as described in the [serve command options]({{ '/docs/configuration/options/#serve-command-options' | relative_url }}).
+
+{: .note .warning}
+The version of the site that `jekyll serve` builds in `_site` is not suited for deployment. Links and asset URLs in sites created
+with `jekyll serve` will use `https://localhost:4000` or the value set with command-line configuration, instead of the values set
+in [your site's configuration file]({{ '/docs/configuration/' | relative_url }}). To learn about how to build your site when it's
+ready for deployment, read the [Deployment]({{ '/docs/step-by-step/10-deployment/' | relative_url }}) section of this tutorial.
 
-When you're developing a site you'll use `jekyll serve` as it updates with any
-changes you make.
 
 Run `jekyll serve` and go to
 <a href="http://localhost:4000" target="_blank" data-proofer-ignore>http://localhost:4000</a> in
 your browser. You should see "Hello World!".
 
-Well, you might be thinking what's the point in this? Jekyll just copied an
-HTML file from one place to another. Well patience young grasshopper, there's
+At this point, you might be thinking, "So what?". The only thing that happened was that Jekyll copied an
+HTML file from one place to another. 
+
+Patience, young grasshopper, there's
 still much to learn!
+
+Next. you'll learn about Liquid and templating.

docs/_docs/step-by-step/02-liquid.md

@@ -3,28 +3,25 @@ layout: step
 title: Liquid
 position: 2
 ---
-Liquid is where Jekyll starts to get more interesting. Liquid is a templating
-language which has three main parts: [objects](#objects), [tags](#tags) and
-[filters](#filters).
+Liquid is where Jekyll starts to get more interesting. It is a templating
+language which has three main components: 
+  * [objects](#objects)
+  * [tags](#tags) 
+  * [filters](#filters)
 
 ## Objects
 
-Objects tell Liquid where to output content. They're denoted by double curly
-braces: {% raw %}`{{`{% endraw %} and {% raw %}`}}`{% endraw %}. For example:
+Objects tell Liquid to output predefined [variables](../../variables/) as content on a page. Use double curly braces for objects: {% raw %}`{{`{% endraw %} and {% raw %}`}}`{% endraw %}. 
 
-{% raw %}
-```liquid
-{{ page.title }}
-```
-{% endraw %}
-
-Outputs a variable called `page.title` on the page.
+For example, {% raw %}`{{ page.title }}`{% endraw %} displays the `page.title` variable.
 
 ## Tags
 
-Tags create the logic and control flow for templates. They are denoted by curly
-braces and percent signs: {% raw %}`{%`{% endraw %} and
-{% raw %}`%}`{% endraw %}. For example:
+Tags define the logic and control flow for templates. Use curly
+braces and percent signs for tags: {% raw %}`{%`{% endraw %} and
+{% raw %}`%}`{% endraw %}. 
+
+For example:
 
 {% raw %}
 ```liquid
@@ -36,13 +33,16 @@ braces and percent signs: {% raw %}`{%`{% endraw %} and
 ```
 {% endraw %}
 
-Outputs the sidebar if `page.show_sidebar` is true. You can learn more about the
-tags available to Jekyll [here](/docs/liquid/tags/).
+This displays the sidebar if the value of the `show_sidebar` page variable is true. 
+
+Learn more about the tags available in Jekyll [here](/docs/liquid/tags/).
 
 ## Filters
 
 Filters change the output of a Liquid object. They are used within an output
-and are separated by a `|`. For example:
+and are separated by a `|`. 
+
+For example:
 
 {% raw %}
 ```liquid
@@ -50,12 +50,13 @@ and are separated by a `|`. For example:
 ```
 {% endraw %}
 
-Outputs `Hi`. You can learn more about the filters available to Jekyll
-[here](/docs/liquid/filters/).
+This displays `Hi` instead of `hi`. 
+
+[Learn more about the filters](/docs/liquid/filters/) available.
 
 ## Use Liquid
 
-Now it's your turn, change the Hello World! on your page to output as lowercase:
+Now, use Liquid to make your `Hello World!` text from [Setup](../01-setup/) lowercase:
 
 {% raw %}
 ```liquid
@@ -65,7 +66,7 @@ Now it's your turn, change the Hello World! on your page to output as lowercase:
 ```
 {% endraw %}
 
-To get our changes processed by Jekyll we need to add [front matter](../03-front-matter/) to the top of the page:
+To make Jekyll process your changes, add [front matter](../03-front-matter/) to the top of the page:
 
 ```yaml
 ---
@@ -73,11 +74,28 @@ To get our changes processed by Jekyll we need to add [front matter](../03-front
 ---
 ```
 
-Our "Hello World!" will now be downcased on render.
+Your HTML document should look like this:
 
-It may not seem like it now, but much of Jekyll's power comes from combining
-Liquid with other features.
+{% raw %}
+```html
+---
+---
 
-In order to see the changes from `downcase` Liquid filter, we will need to add front matter.
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <title>Home</title>
+  </head>
+  <body>
+    <h1>{{ "Hello World!" | downcase }}</h1>
+  </body>
+</html>
+```
+{% endraw %}
 
-That's next. Let's keep going.
+When you reload your browser, you should see `hello world!`. 
+
+Much of Jekyll's power comes from combining Liquid with other features. Add frontmatter to pages to make Jekyll process the Liquid on those pages.
+
+Next, you'll learn more about frontmatter.

docs/_docs/step-by-step/03-front-matter.md

@@ -3,9 +3,10 @@ layout: step
 title: Front Matter
 position: 3
 ---
-Front matter is a snippet of [YAML](http://yaml.org/) which sits between two
-triple-dashed lines at the top of a file. Front matter is used to set variables
-for the page, for example:
+Front matter is a snippet of [YAML](http://yaml.org/) placed between two
+triple-dashed lines at the start of a file.
+
+You can use front matter to set variables for the page:
 
 ```yaml
 ---
@@ -13,8 +14,8 @@ my_number: 5
 ---
 ```
 
-Front matter variables are available in Liquid under the `page` variable. For
-example to output the variable above you would use:
+You can call front matter variables in Liquid using the `page` variable. For
+example, to output the value of the `my_number` variable above:
 
 {% raw %}
 ```liquid
@@ -24,7 +25,7 @@ example to output the variable above you would use:
 
 ## Use front matter
 
-Let's change the `<title>` on your site to populate using front matter:
+Change the `<title>` on your site to use front matter:
 
 {% raw %}
 ```liquid
@@ -44,15 +45,14 @@ title: Home
 ```
 {% endraw %}
 
-Note that in order for Jekyll to process any liquid tags on your page,
-you _must_ include front matter on it. The most minimal snippet of front matter
-you can include is:
+{: .note .info }
+You _must_ include front matter on the page for Jekyll to process any Liquid tags on it. 
+
+To make Jekyll process a page without defining variables in the front matter, use:
 
 ```yaml
 ---
 ---
 ```
 
-You may still be wondering why you'd output it this way as it takes
-more source code than raw HTML. In this next step, you'll see why we've
-been doing this.
+Next, you'll learn more about layouts and why your pages use more source code than plain HTML.

docs/_docs/step-by-step/04-layouts.md

@@ -3,27 +3,27 @@ layout: step
 title: Layouts
 position: 4
 ---
-Websites typically have more than one page and this website is no different.
-
 Jekyll supports [Markdown](https://daringfireball.net/projects/markdown/syntax)
-as well as HTML for pages. Markdown is a great choice for pages with a simple
+in addition to HTML when building pages. Markdown is a great choice for pages with a simple
 content structure (just paragraphs, headings and images), as it's less verbose
-than raw HTML. Let's try it out on the next page.
+than raw HTML. 
 
-Create `about.md` in the root.
+Create a new Markdown file named `about.md` in your site's root folder. 
 
-For the structure you could copy `index.html` and modify it for the about page.
-The problem with doing this is duplicate code. Let's say you wanted to add a
-stylesheet to your site, you would have to go to each page and add it to the
-`<head>`. It might not sound so bad for a two page site, imagine doing it
-for 100 pages. Even simple changes will take a long time to make.
+You could copy the contents of `index` and modify it for the About page. However,
+this creates duplicate code that has to be customized for each new page you add
+to your site. 
+
+For example, adding a new stylesheet to your site would involve adding the link
+to the stylesheet to the `<head>` of each page. For sites with many pages, this
+is a waste of time.
 
 ## Creating a layout
 
-Using a layout is a much better choice. Layouts are templates that wrap around
-your content. They live in a directory called `_layouts`.
+Layouts are templates that can be used by any page in your site and wrap around page content.
+They are stored in a directory called `_layouts`.
 
-Create your first layout at `_layouts/default.html` with the following content:
+Create the `_layouts` directory in your site's root folder and create a new `default.html` file with the following content:
 
 {% raw %}
 ```liquid
@@ -40,14 +40,17 @@ Create your first layout at `_layouts/default.html` with the following content:
 ```
 {% endraw %}
 
-You'll notice this is almost identical to `index.html` except there's
-no front matter and the content of the page is replaced with a `content`
-variable. `content` is a special variable which has the value of the rendered
-content of the page it's called on.
+This HTML is almost identical to `index.html` except there's
+no front matter and the content of the page is replaced by a `content`
+variable. 
 
-To have `index.html` use this layout, you can set a `layout` variable in front
-matter. The layout wraps around the content of the page so all you need in
-`index.html` is:
+`content` is a special variable that returns the rendered
+content of the page on which it's called.
+
+## Use layouts
+
+To make `index.html` use your new layout, set the `layout` variable in the front
+matter. The file should look like this:
 
 {% raw %}
 ```liquid
@@ -59,16 +62,14 @@ title: Home
 ```
 {% endraw %}
 
-After doing this, the output will be exactly the same as before. Note that you
-can access the `page` front matter from the layout. In this case `title` is
-set in the index page's front matter but is output in the layout.
+When you reload the site, the output remains the same.
 
-## About page
+Since the layout wraps around the content on the page, you can call front matter like `page` 
+in the layout file. When you apply the layout to a page, it uses the front matter on that page.
 
-Back to the about page, instead of copying from `index.html`, you can use the
-layout.
+## Build the About page
 
-Add the following to `about.md`:
+Add the following to `about.md` to use your new layout in the About page:
 
 ```markdown
 ---
@@ -83,5 +84,6 @@ This page tells you a little bit about me.
 Open <a href="http://localhost:4000/about.html" target="_blank" data-proofer-ignore>http://localhost:4000/about.html</a>
 in your browser and view your new page.
 
-Congratulations, you now have a two page website! But how do you
-navigate from one page to another? Keep reading to find out.
+Congratulations, you now have a two page website!
+
+Next, you'll learn about navigating from page to page in your site. 

docs/_docs/step-by-step/10-deployment.md

@@ -143,7 +143,21 @@ to do this is to run a production build:
 JEKYLL_ENV=production bundle exec jekyll build
 ```
 
-And copy the contents of `_site` to your server.
+And then copy the contents of `_site` to your server.
+
+<div class="note warning">
+  <h5>Destination folders are cleaned on site builds</h5>
+  <p>
+    The contents of <code>_site</code> are automatically cleaned, by default, when
+    the site is built. Files or folders that are not created by your site's build
+    process will be removed.
+  </p>
+  <p>
+    Some files could be retained by specifying them within the <code>keep_files</code>
+    configuration directive. Other files could be retained by keeping them in your
+    assets directory.
+  </p>
+</div>
 
 A better way is to automate this process using a [CI](/docs/deployment/automated/)
 or [3rd party](/docs/deployment/third-party/).

docs/_docs/structure.md

@@ -25,6 +25,10 @@ A basic Jekyll site usually looks something like this:
 │   ├── _base.scss
 │   └── _layout.scss
 ├── _site
+├── .jekyll-cache
+│   └── Jekyll
+│       └── Cache
+│           └── [...]
 ├── .jekyll-metadata
 └── index.html # can also be an 'index.md' with valid front matter
 ```
@@ -160,6 +164,22 @@ An overview of what each of these does:
         </p>
       </td>
     </tr>
+    <tr>
+      <td>
+        <p><code>.jekyll-cache</code></p>
+      </td>
+      <td>
+        <p>
+          Keeps a copy of the generated pages and markup (e.g.: markdown) for
+          faster serving. Created when using e.g.: <code>jekyll serve</code>.
+          Can be disabled with
+          <a href="/docs/configuration/options/">an option and/or flag</a>.
+          This directory will not be included in the generated site. It’s
+          probably a good idea to add this to your <code>.gitignore</code>
+          file.
+        </p>
+      </td>
+    </tr>
     <tr>
       <td>
         <p><code>.jekyll-metadata</code></p>
@@ -168,9 +188,11 @@ An overview of what each of these does:
         <p>
           This helps Jekyll keep track of which files have not been modified
           since the site was last built, and which files will need to be
-          regenerated on the next build. This file will not be included in the
-          generated site. It’s probably a good idea to add this to your
-          <code>.gitignore</code> file.
+          regenerated on the next build. Only created when using
+          <a href="/docs/configuration/incremental-regeneration/">
+          incremental regeneration</a> (e.g.: with <code>jekyll serve -I</code>).
+          This file will not be included in the generated site. It’s probably
+          a good idea to add this to your <code>.gitignore</code> file.
         </p>
       </td>
     </tr>

docs/_docs/themes.md

@@ -21,7 +21,7 @@ See also: [resources](/resources/).
 
 When you [create a new Jekyll site](/docs/) (by running the `jekyll new <PATH>` command), Jekyll installs a site that uses a gem-based theme called [Minima](https://github.com/jekyll/minima).
 
-With gem-based themes, some of the site's directories (such as the `assets`, `_layouts`, `_includes`, and `_sass` directories) are stored in the theme's gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll's build process.
+With gem-based themes, some of the site's directories (such as the `assets`, `_data`, `_layouts`, `_includes`, and `_sass` directories) are stored in the theme's gem, hidden from your immediate view. Yet all of the necessary directories will be read and processed during Jekyll's build process.
 
 In the case of Minima, you see only the following files in your Jekyll site directory:
 
@@ -46,7 +46,7 @@ The goal of gem-based themes is to allow you to get all the benefits of a robust
 
 ## Overriding theme defaults
 
-Jekyll themes set default layouts, includes, and stylesheets. However, you can override any of the theme defaults with your own site content.
+Jekyll themes set default data, layouts, includes, and stylesheets. However, you can override any of the theme defaults with your own site content.
 
 To replace layouts or includes in your theme, make a copy in your `_layouts` or `_includes` directory of the specific file you wish to modify, or create the file from scratch giving it the same name as the file you wish to override.
 
@@ -117,6 +117,7 @@ To modify any stylesheet you must take the extra step of also copying the main s
 Jekyll will look first to your site's content before looking to the theme's defaults for any requested file in the following folders:
 
 - `/assets`
+- `/_data`
 - `/_layouts`
 - `/_includes`
 - `/_sass`
@@ -126,6 +127,49 @@ Note that making copies of theme files will prevent you from receiving any theme
 {: .note .info}
 Refer to your selected theme's documentation and source repository for more information on which files you can override.
 
+### Themes with `_data` directory {%- include docs_version_badge.html version="4.3.0" -%}
+{: #themes-with-data-directory }
+
+Starting with version 4.3.0, Jekyll also takes into account the `_data` directory of themes. This allows data to be distributed across themes. 
+
+A typical example is text used within design elements.
+
+Imagine a theme provides the include file `testimonials.html`. This design element creates a new section on the page, and puts a h3 heading over the list of testimonials.
+
+A theme developer will probably formulate the heading in English and put it directly into the HTML source code.
+
+Consumers of the theme can copy the included file into their project and replace the heading there.
+
+With the consideration of the `_data` directory there is another solution for this standard task.
+
+Instead of entering the text directly into the design template, the designer adds a reference to a text catalog (e.g. `site.data.i18n.testimonials.header`) and create a file `_data/i18n/testimonials.yml` in the data directory of the theme.
+
+In this file the header is put under the key `header` and Jekyll takes care of the rest.
+
+For theme developers, this, at first sight, is of course a bigger effort than before.
+
+However, for the consumers of the theme, the customization is greatly simplified.
+
+Imagine the theme is used by a customer from Germany. In order for her to get the translated header for the testimonials design element in, she just has to create a data file in her project directory with the key `site.data.i18n.testimonials.header`, put the German translation or a header of her choice on top of it and the design element is already customized.
+
+She no longer has to copy the included file into her project directory, customize it there and, what weighs heaviest, waiver all updates of the theme, simply because the theme developer offered her the possibility to make changes to text modules centrally via text files.
+
+{: .note .warning}
+Data files provide a high degree of flexibility. The place where theme developers put text modules may differ from that of the consumer of the theme which can cause unforeseen troubles!
+
+Related to above example the overriding key `site.data.i18n.testimonials.header` from the theme's `_data/i18n/testimonials.yml` file on the consumer site can be located in three different locations:
+
+- `_data/i18n.yml` with key `testimonials.header`
+- `_data/i18n/testimonials.yml` with key `header` (which mirrors the layout of the given example)
+- `_data/i18n/testimonials/header.yml` without any key, the headline can go straight into the file
+
+Theme developers should have this ambiguity in mind, when supporting consumers that feel lost in setting their text modules for the design elements the theme provides.
+
+{: .note .info}
+When using the data feature ask yourself, is the key that you introduce something that changes the behaviour of the theme when present or not, or is it just data that's displayed anyway. If it's changing the behaviour of the theme it should go into `site.config` otherwise it's fine to be provided via `site.data`.
+
+Bundling data that modifies the behavior of a theme is considered an **anti-pattern** whose use is strongly discouraged. It is solely up to the author of the theme to ensure that every provided data can be easily overridden by the consumer of the theme if they desire to.
+
 ## Converting gem-based themes to regular themes
 
 Suppose you want to get rid of the gem-based theme and convert it to a regular theme, where all files are present in your Jekyll site directory, with nothing stored in the theme gem.

docs/_docs/troubleshooting.md

@@ -208,6 +208,15 @@ you don't have a proper JavaScript runtime. To solve this, either install
 
 ## Problems running Jekyll
 
+### macOS
+
+Jekyll is compatible with macOS with ARM64 architecture.
+However, `bundle exec jekyll serve` may [fail with older version `ffi`](https://github.com/ffi/ffi/issues/870).
+
+You may need to run `bundle update` or update `ffi` to at least `1.14.2` manually.
+
+### Debian or Ubuntu
+
 On Debian or Ubuntu, you may need to add `/var/lib/gems/1.8/bin/` to your path
 in order to have the `jekyll` executable be available in your Terminal.
 

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

@@ -128,7 +128,7 @@ certain features are desired outside of kramdown's core functionality.
 Out of all the extensions listed in the report linked above, gem
 `kramdown-parser-gfm` is automatically installed along with Jekyll 4.0. The
 remaining extensions will have to be manually installed by the user depending on
-desired funtionality, by listing the extension's gem-name in their `Gemfile`.
+desired functionality, by listing the extension's gem-name in their `Gemfile`.
 
 Notes:
   * `kramdown-converter-pdf` will be ignored by Jekyll Core. To have Jekyll convert Markdown to PDF

docs/_layouts/tutorials.html

@@ -27,6 +27,13 @@ layout: default
           {% endif %}
         </header>
         {{- content -}}
+        {% if page.plugin_disclaimer %}
+          <div class="disclaimer-ribbon">
+            Disclaimer: The Jekyll Core Team does not endorse the Ruby code in this tutorial and is
+            not liable to resolve any bugs therein or issues arising otherwise from the use of the
+            provided example(s) in production builds.
+          </div>
+        {% endif %}
         {%- include section_nav_tutorials.html -%}
       </article>
     </div>

docs/_posts/2013-05-12-jekyll-1-0-2-released.markdown

@@ -12,7 +12,7 @@ releases, and fix some other annoying bugs:
 * Backwards-compatibilize relative permalinks ([#1081][])
 * Add `jekyll doctor` command to check site for any known compatibility problems ([#1081][])
 * Deprecate old config `server_port`, match to `port` if `port` isn't set ([#1084][])
-* Update pygments.rb and kramdon versions to 0.5.0 and 1.0.2, respectively ([#1061][], [#1067][])
+* Update pygments.rb and kramdown versions to 0.5.0 and 1.0.2, respectively ([#1061][], [#1067][])
 * Fix issue when post categories are numbers ([#1078][])
 * Add a `data-lang="<lang>"` attribute to Redcarpet code blocks ([#1066][])
 * Catching that Redcarpet gem isn't installed ([#1059][])

docs/_posts/2014-06-28-jekyll-turns-21-i-mean-2-1-0.markdown

@@ -19,7 +19,7 @@ things to look forward to:
 - Add support for `hl_lines` in `highlight` tag (#2532)
 - Post categories now merge with directory, front matter, and defaults (#2373)
 - New `--skip_initial_build` flag for `jekyll serve` (#2477)
-- A bajilion bug fixes and site updates!
+- A bajillion bug fixes and site updates!
 
 Let's go party!
 

docs/_posts/2015-11-17-jekyll-3-0-1-released.markdown

@@ -15,7 +15,7 @@ Hey, folks! Bunch of bug fixes here. Notables:
 * All hooks should now be properly registered & documented
 
 And a bunch more changes which you can see over in the
-[changelog](/docs/history).
+[changelog](/docs/history/).
 
 Thanks to the 17 developers who contributed code and documentation to this
 patch release: Alfred Xing, Christian Trosell, Jordan Thornquest, Jordon

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

@@ -18,7 +18,7 @@ Today, we released v3.1.4 in an effort to bring more stability to the v3.1.x ser
 
 The fixes for `layout` may not be seamless for everyone, but we believe they will be the "right thing to do" going forward.
 
-We are alwawys striving to make Jekyll more straight-forward to use. Please do open an issue if you believe an aspect of Jekyll's user experience isn't up to par.
+We are always striving to make Jekyll more straight-forward to use. Please do open an issue if you believe an aspect of Jekyll's user experience isn't up to par.
 
 For a full history of our changes, [see the changelog](/docs/history/#v3-1-4).
 

docs/_posts/2017-10-19-diversity-open-source.markdown

@@ -21,7 +21,7 @@ No matter which Code of Conduct you pick, the most important thing is to actuall
 
 The problem that puts people off the most is incomplete or missing documentation, as revealed through GitHub's [open source survey](http://opensourcesurvey.org/2017). A very popular myth in programming is that good code explains itself, which might be true, but only for the person writing it. It's important, especially once you put your project out there for the world to see, to document not only your code, but also the process by which you maintain it. Otherwise, it's going to be extremely hard for newcomers to even figure out where to begin contributing to your project.
 
-Jekyll has [an entire section of its docs](/docs/contributing) dedicated to information on how to contribute for this very reason. Every documentation page has a link to directly edit and improve it on GitHub. It's also important to realize that not all contributions are code. It can be documentation, it can be reviewing pull requests, but it can also just be weighing into issues, and all of this should be recognized in the same way. At Jekyll, out of 397 total merged pull requests in the last year, __204__ were documentation pull requests!
+Jekyll has [an entire section of its docs](/docs/contributing/) dedicated to information on how to contribute for this very reason. Every documentation page has a link to directly edit and improve it on GitHub. It's also important to realize that not all contributions are code. It can be documentation, it can be reviewing pull requests, but it can also just be weighing into issues, and all of this should be recognized in the same way. At Jekyll, out of 397 total merged pull requests in the last year, __204__ were documentation pull requests!
 
 ## Create newcomer-friendly issues
 

docs/_posts/2018-01-02-jekyll-3-7-0-released.md

@@ -11,7 +11,7 @@ We're happy to release a new minor for the new year.
 Here are a few of the latest additions from our contributors:
 
  * LiveReload is available as an option during development: with `jekyll serve --livereload` no more manual page refresh. A big thanks to @awood for this feature and to @andreyvit, LiveReload author.
- * New `collections_dir` configuration option allows you to store all your [collections](/docs/collections) in a single folder. Your source root folder should now look cleaner :sparkles: .
+ * New `collections_dir` configuration option allows you to store all your [collections](/docs/collections/) in a single folder. Your source root folder should now look cleaner :sparkles: .
  * If you're using a [gem-based theme](/docs/themes/) in coordination with the `--incremental` option, you should notice some significant speed during the regeneration process, we did see build time went down **from 12s to 2s** with @mmistakes [minimal-mistakes theme](https://github.com/mmistakes/minimal-mistakes) during our tests.
  * Jekyll will now check to determine whether host machine has internet connection.
  * A new `latin` option is available to better [handle URLs slugs](/docs/liquid/filters/#options-for-the-slugify-filter).

docs/_posts/2018-02-19-meet-jekyll-s-new-lead-developer.markdown

@@ -6,7 +6,7 @@ author: parkr
 categories: [team]
 ---
 
-Jekyll has a new Lead Developer: [Olivia](https://liv.cat/)!
+Jekyll has a new Lead Developer: Olivia!
 
 After over 5 years of leading Jekyll, many releases from 0.12.1 to 3.6.0, and
 countless conversations in GitHub Issues, Pull Requests, Jekyll Talk, and
@@ -19,8 +19,8 @@ community lead. Olivia joined the Jekyll Core Team with experience in the
 Node.js community, both online and as a volunteer organizer with JSConf EU.
 
 In my conversations with Olivia, it is clear that Jekyll's vision of
-simplicity for the user ([no magic!](/philosophy#1-no-magic)) and letting
-users' [content be king](/philosophy#3-content-is-king) will remain a top
+simplicity for the user ([no magic!](/philosophy/#1-no-magic)) and letting
+users' [content be king](/philosophy/#3-content-is-king) will remain a top
 priority. In just the last few weeks as the transition has been occurring,
 we have seen some incredible work on performance that will make future
 versions of Jekyll work better at scale. She will be prioritizing work on

docs/_posts/2018-03-14-development-update.md

@@ -21,7 +21,7 @@ That being said, the development period of version 4.0 begins _now_. This means
 
 As for a release date, we're currently aiming for late summer, around September or so. However, keep in mind that this project is purely volunteer-run, and as such, delays might occur and we might not hit that release date.
 
-Finally, this is a great time for newcomers to open-source to make their first contribution. We'll be doing our best to mark recommended contributions and create newcomer-friendly issues, as well as to provide mentoring throughout the contribution process (although we'd like to think that we're already pretty proficient at that). So if you've always been hestitant about contributing to a large open-source project, Jekyll is a good place to start!
+Finally, this is a great time for newcomers to open-source to make their first contribution. We'll be doing our best to mark recommended contributions and create newcomer-friendly issues, as well as to provide mentoring throughout the contribution process (although we'd like to think that we're already pretty proficient at that). So if you've always been hesitant about contributing to a large open-source project, Jekyll is a good place to start!
 
 Happy Jekylling! :wave:
 

docs/_posts/2020-05-27-jekyll-4-1-0-released.markdown

@@ -38,8 +38,6 @@ of time taken during various stages of the *build process*.
 * Jekyll's development server now supports certificates based on Elliptic-curve cryptography.
 
 For the interest of plugin authors:
-* `Jekyll::Page` now uses a Liquid Drop to expose attributes for Liquid templates. However, its subclasses will continue
-using the legacy `ATTRIBUTES_FOR_LIQUID` hash by default. More details in the [associated documentation][page-drop-docs]
 * Excerpts won't be generated for `Jekyll::Page` subclasses automatically unless such instances have an `excerpt` key in
 their `data` hash.
 
@@ -53,9 +51,6 @@ released gem, please remove `|_config\.yml` from the regular expression in the g
 [{{ filter_slug }}-filter]: {{ filter_slug | prepend: '/docs/liquid/filters/#' | relative_url }}
 {% endfor %}
 
-[page-drop-docs]: {{ 'docs/pages/#for-plugin-developers' | relative_url }}
-
-
 ### Have questions?
 
 Please reach out on our [community forum](https://talk.jekyllrb.com)

docs/_posts/2021-04-08-jekyll-3-9-1-released.markdown

@@ -0,0 +1,28 @@
+---
+title: 'Jekyll 3.9.1 Released'
+date: 2021-04-08 10:51:12 -0400
+author: parkr
+version: 3.9.1
+categories: [release]
+---
+
+This patch release of the 3.9 series is released to fix a bug where the
+`include` tag does not allow valid filename characters. For example, this
+would previously fail:
+
+{% raw %}
+```text
+{% include my-logo@2x.svg %}
+```
+{% endraw %}
+
+This release adds support for the following characters in filenames:
+
+- `@`
+- `-`
+- `(` and `)`
+- `+`
+- `~`
+- `#`
+
+Happy Jekylling!

docs/_posts/2021-09-14-goodbye-dear-frank.markdown

@@ -0,0 +1,32 @@
+---
+title: 'Goodbye, Dear Frank.'
+date: 2021-09-14 11:28:02 -0500
+author: ashmaroli
+categories: [team, community]
+---
+
+Over the weekend, the Jekyll core team learned of the passing of one of our own: *Frank Taillandier*, popularly known
+by his GitHub username @DirtyF.
+
+Ruby not being his forte, he chose to avoid code-level changes and instead focus on what he did best — *engage with
+the community*.
+
+He helped resolve complaints reported on the GitHub issue tracker, ensured that Jekyll documentation remained simple for
+novice users yet detailed enough for advanced users seeking additional information.
+
+He also served as the administrator for Jekyll's public [discourse forum](https://talk.jekyllrb.com/) where he not only
+addressed queries from users and provided tips to improve Jekyll workflow, he also shared feedback on Jekyll sites
+created by the community, and used the forum as a platform to gather feedback on unreleased iterations of Jekyll and
+in-house plugins.
+
+Abreast with latest developments in the Web-verse, Frank was always quick to introduce technologies that vastly improved
+maintenance in the Jekyll organization. He was instrumental in setting up deploy previews for patches to Jekyll's
+documentation site and later wiring GitHub Actions to handle continuous integrations for Jekyll and in-house projects.
+
+In spite of spiritually moving away from Jekyll during the later part of his career, choosing to concentrate efforts on
+furthering JAMstack projects, he greatly remained active on Jekyll's development channel on Slack relaying key feedback
+from the community or discuss concerns regarding the future of Jekyll at length.
+
+Having untimely left Jekyll and our community with an unfillable void, he will be missed immensely. :broken_heart:
+
+Rest in Peace, friend and colleague. :bouquet:

docs/_posts/2021-09-27-jekyll-4-2-1-released.markdown

@@ -0,0 +1,40 @@
+---
+title: "Jekyll 4.2.1 Released"
+date: 2021-09-27 14:45:46 +0530
+author: ashmaroli
+version: 4.2.1
+category: release
+---
+
+Hello Jekyllers!
+
+The Jekyll team is happy to announce the release of `v4.2.1` which fixes a couple of
+regressions introduced in `v4.2.0` and another bug inherited from Jekyll 3.
+
+In `v4.2.0`, we decided to stop overriding {% raw %}`{{ site.url }}`{% endraw %} with
+the *localhost* address when running the command `jekyll serve` with the default
+*development* mode. While the intent behind the change was to avoid forcing users to
+generate a *production build* separately by invoking `jekyll build`, it however had an
+unforeseen consequence — absolute URLs for assets now pointed to
+resources that were at times not yet been deployed to the configured `site.url`. That
+broke the users' local development workflow.
+
+`v4.2.0` also added a series of optimizations surrounding the generation of Liquid
+representation for a site's standalone pages and layouts. However, that prevented
+{% raw %}`{{ page.content }}`{% endraw %} and other mutable attributes from reflecting
+the latest state of the requested attribute, thereby breaking the render of all resources
+that were dependent on such mutable attributes.
+
+The last fix included in this release addresses the issue where incremental regeneration
+ignored changes to documents in collections when the site is configured to use a custom
+`collections_dir` for all collections.
+
+Special thanks to @benik for helping us understand the regression caused by the decision
+to stop overriding `site.url` and proposing to revert the change. Another special thanks
+to @pdmosses for helping us discover the regression surrounding Liquid representation of
+pages by providing with a test repository.
+
+<div style="padding:8px 0 2px;text-align:center;background:rgba(240,0,0,0.1)">
+  :bouquet: <span style="margin:0 6px;font-size:0.75em;vertical-align:top">
+  Dedicated to our colleague Frank who passed away recently</span> :bouquet:
+</div>

docs/_posts/2022-03-03-jekyll-4-2-2-released.markdown

@@ -0,0 +1,30 @@
+---
+title: "Jekyll 4.2.2 Released"
+date: 2022-03-03 19:15:20 +0530
+author: ashmaroli
+version: 4.2.2
+category: release
+---
+
+Hello Jekyllers!
+
+Jekyll 4.2.2 has been released. Unlike prior releases, this is a simple maintenance release and may be skipped.
+
+For those who are still curious about the current release, here is some technical context: The previous `jekyll-4.2.1` package was built and
+published using a Windows system. A side-effect of that action was that every file bundled into the gem ended up with Windows-style CRLF
+line-endings instead of Unix-style LF line-endings.
+
+For our end-users, this difference holds no significance. However, a third-party entity vendoring the release faced a roadblock. The executable
+program `jekyll` apparently misplaced the executable bit because of the change in line-endings.
+
+To that end, the Jekyll team decided to use the GitHub Actions service to build and publish releases. In-house plugins have already published
+releases via this route serving as trials. Henceforth, and unless explicitly reported, all Jekyll releases will be built on GitHub Actions'
+Ubuntu platform and published to Rubygems by @jekyllbot irrespective of the maintainer overseeing the release.
+
+That is all for now.
+Happy Jekyllin'!!
+
+*P.S.: Jekyll 4.3.0 will be bringing you some new features very soon.. Also, our sass-converter plugin has been [enhanced][sass-220] to support
+modern improvements to Sass.*
+
+[sass-220]: https://github.com/jekyll/jekyll-sass-converter/tree/v2.2.0#sass-embedded

docs/_posts/2022-03-27-jekyll-3-9-2-released.markdown

@@ -0,0 +1,19 @@
+---
+title: 'Jekyll 3.9.2 Released'
+date: 2022-03-27 13:20:00 -0700
+author: parkr
+version: 3.9.2
+categories: [release]
+---
+
+Hey Jekyllers,
+
+Quick bug-fix release for you all today:
+
+1. Ruby 3.0 and 3.1 support :tada: (you will need to run `bundle add webrick` for `jekyll serve` to work)
+2. `jekyll serve` will no longer inject a charset into the MIME type for
+binary types
+3. Incremental regeneration now handles includes in collection files
+   correctly
+
+That's all, Happy Jekylling!

docs/_sass/_font-awesome.scss

@@ -1,13 +1,15 @@
 @font-face {
   font-family: 'FontAwesome';
+  font-weight: normal;
+  font-style: normal;
+  font-display: swap;
   src: url('../fonts/FontAwesome.eot?9h6hxj');
   src: url('../fonts/FontAwesome.eot?9h6hxj#iefix') format('embedded-opentype'),
        url('../fonts/FontAwesome.woff?9h6hxj') format('woff'),
        url('../fonts/FontAwesome.ttf?9h6hxj') format('truetype'),
        url('../fonts/FontAwesome.svg?9h6hxj#FontAwesome') format('svg');
-  font-weight: normal;
-  font-style: normal;
 }
+
 .fa {
   display: inline-block;
   font: normal normal normal 14px/1 FontAwesome;
@@ -16,9 +18,11 @@
   -webkit-font-smoothing: antialiased;
   -moz-osx-font-smoothing: grayscale;
 }
+
 .fa-link:before {
   content: "\f0c1";
 }
+
 .fa-pencil:before {
   content: "\f040";
 }