Improve docs around using GitHub Actions to build and deploy Jekyll sites (#9682)

Merge pull request 9682

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

@@ -2,21 +2,35 @@
 title: GitHub Actions
 ---
 
-When building a Jekyll site with GitHub Pages, the standard flow is restricted for security reasons
+When building a Jekyll site with GitHub Pages, Jekyll runs in an environment restricted for security
-and to make it simpler to get a site setup. For more control over the build and still host the site
+reasons, yet containing numerous [whitelisted plugins and themes][ghp-whitelist] to make it simpler
-with GitHub Pages you can use GitHub Actions.
+to get a site set up.
+
+The only workaround to have control over the build environment and gemset yet use GitHub Pages to
+host the site was previously by building elsewhere and pushing the built directory contents to the
+`gh-pages` branch on your repository.
+
+However, GitHub now provides you with the option to use their in-house CI/CD product named
+*GitHub Actions* to *build and deploy (host)* your Jekyll site with complete control over the build
+environment and gemset.
 
 ## Advantages of using Actions
 
 ### Control over gemset
 
-- **Jekyll version** --- Instead of using the classic GitHub Pages provided version at `3.9.3`, you
+- **Jekyll version** --- Instead of using the classic GitHub Pages-provided version at `3.9.3`, you
   can use any version of Jekyll you want. For example `{{site.version}}`, or point directly to the
-  repository.
+  repository via the Gemfile.
-- **Plugins** --- You can use any Jekyll plugins irrespective of them being on the
+- **Plugins** --- You can use any Jekyll plugins irrespective of them being whitelisted by GitHub,
-  [supported versions][ghp-whitelist] list, even `*.rb` files placed in the `_plugins` directory
+  including any `*.rb` files placed in the `_plugins` directory of your site.
-  of your site.
+- **Themes** --- While using a custom theme is possible without Actions, it is now possible to use
-- **Themes** --- While using a custom theme is possible without Actions, it is now simpler.
+  themes depending on features introduced in newer versions of Jekyll.
+
+{: .note .info}
+If you are migrating from the classic flow but want to keep using a GitHub-hosted theme, you may use
+the [jekyll-remote-theme][remote-theme] plugin, add any required dependencies of your theme
+(previously bundled by default) into your `_config.yml` and `Gemfile` and set the
+`remote_theme: <owner>/<repo_name>` theme repository slug correctly in your `_config.yml`.
 
 ### Workflow Management
 
@@ -24,6 +38,8 @@ with GitHub Pages you can use GitHub Actions.
   steps, use environment variables.
 - **Logging** --- The build log is visible and can be tweaked to be verbose, so it is much easier to
   debug errors using Actions.
+- **Caching** --- The `ruby/setup-ruby` action makes it possible to cache installed gems
+  automatically instead of having to download the bundle on each build.
 
 ## Workspace setup
 
@@ -31,7 +47,7 @@ The first and foremost requirement is a Jekyll project hosted at GitHub. Choose
 project or follow the [quickstart]({{ '/docs/' | relative_url }}) and push the repository to GitHub
 if it is not hosted there already.
 
-The Jekyll site we'll be using for the rest of this page initially consists of just a `_config.yml`,
+The Jekyll site we'll be using for the rest of this page, initially consists of just a `_config.yml`,
 an `index.md` page and a `Gemfile`. The contents are respectively:
 
 ```yaml
@@ -117,5 +133,6 @@ The workflow will build and deploy your site again.
 - [starter-workflows] is the official repository providing the workflow template used in this guide.
 
 [ghp-whitelist]: https://pages.github.com/versions/
+[remote-theme]: https://github.com/benbalter/jekyll-remote-theme
 [timeago-plugin]: https://rubygems.org/gems/jekyll-timeago
 [starter-workflows]: https://github.com/actions/starter-workflows/blob/main/pages/jekyll.yml

docs/_docs/plugins/installation.md

@@ -109,8 +109,10 @@ end
     <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
+    You can still use GitHub Pages to publish your site, but you'll need to either build the site locally and push the generated files to
-    GitHub repository instead of the Jekyll source files.
+    your GitHub repository or use
+    <a href="{{ '/docs/continuous-integration/github-actions/' | relative_url }}" title="GitHub Actions">GitHub Actions</a> to host source
+    files on GitHub yet build and deploy with full control on GitHub Pages.
   </p>
 </div>