Add untracked files

.atom-build.yml

@@ -1,2 +1,13 @@
-cmd: '{FILE_ACTIVE} {FILE_ACTIVE_PATH}'
+cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/blog.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/blog.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-blog" "bundle exec jekyll serve --watch --drafts"'
-name: 'Run build.sh'
+name: 'blog.bryanroessler.com--SERVE'
+targets:
+  blog.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/blog.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/blog.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-blog" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'
+  landing.bryanroessler.com--SERVE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/landing.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/landing.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-landing" "bundle exec jekyll serve --watch --drafts"'
+  landing.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/landing.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/landing.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-landing" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'
+  cv.bryanroessler.com--SERVE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/cv.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/cv.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-cv" "bundle exec jekyll serve --watch --drafts"'
+  cv.bryanroessler.com--BUNDLE-UPDATE:
+    cmd: 'build-wrapper podman-run-wrapper --debug -m ephemeral -o "-it -p 4000:4000 -v /home/bryan/Documents/develop/www/cv.bryanroessler.com:/srv/jekyll -v /home/bryan/Documents/develop/www/cv.bryanroessler.com/vendor/bundle:/usr/local/bundle" -i jekyll/jekyll -n "jekyll-cv" --selinuxfix "chmod a+w /srv/jekyll/Gemfile.lock && bundle update --all"'

blog.bryanroessler.com/.atom-build.yml

@@ -1,2 +0,0 @@
-cmd: '{FILE_ACTIVE} {FILE_ACTIVE_PATH}'
-name: 'Run build.sh'

blog.bryanroessler.com/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: Beautiful Jekyll CI
+on: [push, pull_request]
+jobs:
+  build:
+    name: Build Jekyll
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.3'
+      - name: Install dependencies
+        run: bundle install && bundle exec appraisal install
+      - name: Setup Pages
+        id: configure-pages
+        uses: actions/configure-pages@v5
+      - name: Setup CI config
+        run: |
+          echo "---" > _config_ci.yml
+          echo "baseurl: ${{ steps.configure-pages.outputs.base_path }}" >> _config_ci.yml
+      - name: Build site
+        env:
+          JEKYLL_ENV: production
+        run: bundle exec appraisal jekyll build --future --config _config_ci.yml,_config.yml
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3

blog.bryanroessler.com/.gitignore

@@ -3,10 +3,15 @@ _site
 .sass-cache
 .vagrant
 .bundle
-vendor/bundle
+.jekyll-cache
+vendor
 _drafts
 
 # general
 .DS_Store
 Thumbs.db
 ehthumbs.db
+
+Gemfile.lock
+
+beautiful-jekyll-theme-*.gem

blog.bryanroessler.com/Appraisals

@@ -0,0 +1,6 @@
+appraise "jekyll-3" do
+  gem "jekyll", "3.9.4"
+end
+appraise "jekyll-4" do
+  gem "jekyll", "4.3.3"
+end

blog.bryanroessler.com/CHANGELOG.md

@@ -1,8 +1,180 @@
-# CHANGELOG
+## Unreleased version
+- BREAKING CHANGE: Allow changing the order of the social network links that appear in the footer (#1152)
+- BREAKING CHANGE: `google-scholar` social network link no longer requires the prefix `citations?user=`; if you previously set this parameter, it needs to be updated (#1189)
+- Added `mathjax` YAML parameter to allow support for MathJax, used to write LaTeX expressions (#195)
+- Added explicit support for favicons, you only need to add a `favicon.ico` file to the root directory
+- The footer of a page always sticks to the bottom, even on short pages (#576)
+- Added `author` YAML parameter to allow specifying the author(s) of a post (#1220)
+- Fixed bug where search results broke if a post title had a backslash (#1279)
+- Fixed bug where hovering over search results showed the text "{desc}" (#1156)
+- Added social network links for GitLab, Bluesky, Whatsapp, Untappd (#1168, #1218, #1299, #1307)
+- Support reddit social network link to either be a subreddit or a user (#1371)
+- Use CSS variables (#661)
+- Added instructions and example on how to fix image links in project sites (#1171)
+- Pagination buttons: use nicer arrows, and don't show text on small screens (#1221)
+- Updated Yelp URL format - if you previously used the `yelp` social network config parameter, you might need to update the config value (#1259)
+- Added `title-on-all-pages` config setting, that adds the website title to all page titles (#1272)
+- Change Twitter icon to X (#1193)
+- Upgraded font-awesome to 6.5.2 (#1330)
 
-This file lists all non-trivial changes to Beautiful Jekyll.
+## v6.0.1 (2023-06-08)
 
-I often make small changes to documentation, to the demo site, or to the general look-and-feel. These changes will not be listed here. Any other minor changes will also not be listed here.
+This version has been in the works for a few years. It includes several new features that were highly requested, numerous bug fixes, new documentation, and aggresively encourages migrating from the old Google Universal Analytics to the new Analytics 4.
+
+#### Breaking changes
+
+- As of July 2023, Google Universal Analytics is going away and being replaced by Google Analytics 4. Beautiful Jekyll sites that still use the old analytics tag will show a warning to encourage them to move to Analytics 4 (#1096).
+- More control over RSS feed sharing: previously, an RSS feed was *always* generated, and if the config setting `rss-description` was set then there was an RSS icon in the footer. Now, an RSS feed is only generated when the config setting `rss-description` exists, and an RSS footer icon is only shown if `rss: true` is set in the `social-network-links` config settings.
+
+#### New parameters and settings
+
+- Added `navbar-var-length` config setting that allows the navigation menu to be the same length as the longest sub-menu, so that long words in the submenu are not cut off (#765) 
+- Added `post_search` config setting that creates a Search button in the navbar (#770)
+- Added `edit_page_button` config setting that adds a "Edit page" button to the footer (to edit the current page on GitHub) (#1004)
+- Added `footer-hover-col` config setting to customize the hover colour of links in the footer (#848)
+
+#### New features and improvements
+
+- Made the home page feed more accessible for screen readers (#950)
+- Added support for giscus comments (#886) and CommentBox (#960)
+- Added support for Cloudflare Analytics (#797)
+- Added Reddit in share options of posts (#815)
+
+#### Bug fixes
+
+- Fixed page titles, subtitles, and excerpts rendering correctly when there are special characeters in them (#856) 
+- Fixed bug where navbar secondary level dropdown items didn't inherit the same colour as the primary navbar links
+- Fixed bug where the navbar "burger" collapsed button didn't always revert back to a light colour
+- Fixed bug where using an image as a navbar title did not render in GitHub Project pages that did not have a custom domain
+- Fixed bug where image thumbnails on the feed page were always forced into a square rather than maintaining a proper image aspect ratio
+- Fixed bug where special characters in the title led to broken share tags (#744)
+- Fixed bug where staticman didn't work jQuery slim version is used (#766)
+- Fixed very long strings to wrap around the next line rather than go off-screen (#787)
+
+#### Small changes
+
+- Updated staticman from using v2 (public servers) to v3 (private servers) due to the public servers becoming obsolete (#775)
+- Added social network links for Patreon, Medium, Itch.io, Discord, Kaggle, Hackerrank (#783, #788, #907, #961, #978)
+- Slightly reworked margins and position for avatar image to resolve an alignment issue on Safari
+- Changed the width at which the navbar collapses to a higher threshold because most modern non-mobile browsers are >1000px
+
+
+## v5.0.0 (2020-09-15)
+
+One of the major changes in this version is that a lot of time was spent on rethinking the entire SEO and social media sharing model (how a page looks on eg. Google, Twitter, Facebok). It was redesigned to be more simple and customizable. The new documentation has a section dedicated to SEO and social media sharing of a page. Unfortunately some changes that are not backwards-compatible had to be made.
+
+#### Breaking changes
+
+- Renamed `description` YAML parameter to `share-description` to be more clear
+- Renamed `description` config setting to `rss-description` since it was only used in RSS (the FAQ explains the difference between YAML parameters and config settings if you're confused)
+- Removed YAML parameter `use-site-title` (you can now specify the exact title using `share-title`)
+- Removed undocumented YAML parameters `meta-title` and `meta-description`
+- Removed `link-tags` config setting because it wasn't necessary. If you use tags, there will now always be a tags page created; if you don't use tags there won't be a tags page.
+- The YAML parameter `show-avatar` is now true by default. This has always been the case for GitHub Pages users, but not for `remote_theme` users. For consistency, it's now the default for everyone. (#715)
+
+#### New parameters and settings
+
+- Added `full-width` YAML parameter to allow having full-width pages
+- Added `feed_show_excerpt` config setting to show/hide the post excerpts on the feed page
+- Added `feed_show_tags` config setting to show/hide the list of tags on post previews on the feed page
+- Added `share-title` YAML parameter to give control over the search engine/social media title
+- Added `last-updated` YAML parameter to show a "Last Updated on" date for blog posts
+- Added `before-content` and `after-content` YAML parameters that allow you to add some common HTML before the main content of a page (below the title) or after the main content (above the footer). Works in a similar way to `footer-extra`.
+- Added `head-extra` YAML parameter which is similar to `footer-extra` but is used to include custom HTML code in a page's `<head>` tag
+- Added `site-js` config setting to provide JavaScript files that are used on all pages in the site
+
+#### New features and improvements
+
+- Improved the `footer-extra` YAML parameter to support multiple files instead of only a single file
+- Added automatic navbar color detection (#702)
+- When `nav-short` is turned on, the avatar will also be shorter
+- Changed navbar and footer background colour to be slightly darker, for better contrast with the default white page background for accessibility reasons
+- Changed the behaviour of `site-css` to include site-wide CSS file **before** instead of after page-specific files
+- Renamed internal css/js files from "main" to "beautifuljekyll" to make it easier for users to troubleshoot
+- Added alt text to all images for better accessibility
+- Made thumbnail images square instead of circles, as users reported that circles cut off important parts of images
+
+#### Bug fixes
+
+- Fixed rendering issues with `nav-short` parameter that caused the body of the page to start too low
+- Fixed some CSS styles that broke during the bootstrap 4 migration (#716)
+
+#### Library upgrades
+
+- Upgraded kramdown to version 2.3.0 to fix security issues
+- Upgraded jQuery to version 3.5.1 to fix a couple security vulnerabilities with the previous version
+
+## v4.1.0 (2020-08-08)
+
+- Added Open Graph `site_name` meta field to pages automatically
+- Added `text-col` config setting  for main text color (#694)
+- Added `keywords` config setting to set the meta keywords on all pages (for SEO purposes) (#691)
+- Added `mobile-theme-col` config setting to allow a mobile theme colour (#692)
+- Added `site-css` config setting in the config file to provide CSS files that are used on all pages in the site (#695)
+- Added YAML parameter `description`: creates the meta description on a page, intended to provide a brief description of the page for search engines and when the page is shared (#690)
+
+## v4.0.1 (2020-07-13)
+
+- Fixed staticman comments UI that was broken since the migration to bootstrap 4
+
+## v4.0.0 (2020-07-12)
+
+- **BREAKING CHANGE** Replace `image` YAML parameter with `thumbnail-img` to be more clear
+- **MAJOR BEHAVIOUR CHANGE** Don't use the thumbnail as the avatar image
+- Cover image will automatically be used as thumbnail if none is provided
+- Image to share on social media will use the cover image or thumbnail if none is provided
+- All images (social media share, thumbnail, cover) can use either relative or absoluate paths.
+- Fixed issue where if a dropdown menu was the last item in the menu bar, it did not have a proper margin on the right
+- Added social network links: Mastodon (#646), Google Scholar, ORCID (#670)
+- Added support for sharing pages on new social network: VK (#657)
+- Use Open Graph type 'article' for blog posts (#669)
+- Use Twitter's large sumary card (large image) when there is a cover image, thumbnail image, or share image specified (#668)
+- Made post images in the feed page smaller on smaller devices
+- Fixed jQuery version in staticman (#671)
+
+## v3.0.0 (2020-05-07)
+
+- **BREAKING CHANGE** Upgraded from Bootstrap 3.3.2 to 4.4.1. This involved a major rewrite of most components. This shouldn't affect any users unless you have custom HTML/CSS code which the new Bootstrap could have broken.
+- **BREAKING CHANGE** Renamed `bigimg` YAML parameter to `cover-img`
+- **BREAKING CHANGE** Removed `googlefonts` YAML parameter since googlefonts are just CSS so they can be loaded via `ext-css`
+- **BREAKING CHANGE** Upgraded from jQuery 1.11.2 to 3.4.2. This should not affect most people
+- Added `navbar-border-col` setting in the config file
+- Added accessibility features where possible
+- Made the theme completely responsive by rewriting all CSS to use 'rem' instead of 'px'
+- Rewrote and simplified some JavaScript code to use CSS or Bootstrap alternatives that weren't available in 2015
+- Removed most of the sample posts so that users only have two sample posts to learn from
+- Improvements to the README instructions
+
+## v2.3.0 (2020-04-29)
+
+- Added YAML parameter `footer-extra` for including custom content in the footer
+- Fixed issue: linking to a specific part of a page resulted in scrolling too far (#69)
+- Added YAML parameter `nav-short` to have navbar permanently collapsed
+- Added social network link: Calendly
+- Fixed bug where RSS link in footer was showing even when turned off
+
+## v2.2.0 (2020-04-27)
+
+- Added social network link: Telegram (#625) (thanks @mashed-potatoes)
+- Moved the demo site to an independent URL: https://beautifuljekyll.com
+- Major documentation overhaul and cleanup of old files
+- Fixed a few bugs from the remote_theme migration
+
+## v2.0.0 (2020-04-26)
+
+- Beautiful-Jekyll v2.0.0 available as an official Ruby gem
+- Beautifull-Jekyll now supports the `remote_theme` config (#339) (thanks @gpotter2 and @skalee)
+- Consolidated the demo site, the ruby gem, and the master branch into one
+- Added a `home` layout and used it in the index page
+- Added readtime support for the post header (#622) (thanks @MutMatt and @rubyreads)
+- Removed the dependency on `_data` folder since it doesn't get copied when using `remote_theme` (#614)
+- Added support for configuring lang attribute on `html` tag (#608) (thanks @skalee)
+- Added ability to disable round logo (thanks @gpotter2)
+- Added support for Utterances comments (#596) (thanks @colynn)
+- Removed 'just-comments' as it's getting killed at the end of the year
+- Upgraded font-awesome to 5.12.1 (#587) (thanks @cketti)
+
+## Prior to 2020
 
 **2018-12-24** Add support for Staticman comments (#440) (thanks @VincentTam)
 
@@ -73,3 +245,4 @@ I often make small changes to documentation, to the demo site, or to the general
 ... Many small changes because the site was in its infancy
 
 **2015-03-12** Beautiful Jekyll version 0.0000001 is released!
+

blog.bryanroessler.com/Gemfile

@@ -1,11 +1,5 @@
-source 'https://rubygems.org'
+# frozen_string_literal: true
 
-gem 'jekyll'
+source "https://rubygems.org"
 
-gem "github-pages", '197', group: :jekyll_plugins
+gemspec
-
-# enable tzinfo-data for local build
-# gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
-gem 'jekyll-paginate'
-
-gem 'markdown_helper', '~> 2.5', '>= 2.5.2'

blog.bryanroessler.com/Gemfile.lock

@@ -1,253 +1,172 @@
+PATH
+  remote: .
+  specs:
+    beautiful-jekyll-theme (6.0.1)
+      jekyll (>= 3.9.3)
+      jekyll-paginate (~> 1.1)
+      jekyll-sitemap (~> 1.4)
+      kramdown (~> 2.3)
+      kramdown-parser-gfm (~> 1.1)
+      webrick (~> 1.8)
+
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
+    addressable (2.8.7)
-      i18n (~> 0.7)
+      public_suffix (>= 2.0.2, < 7.0)
-      minitest (~> 5.1)
+    appraisal (2.5.0)
-      thread_safe (~> 0.3, >= 0.3.4)
+      bundler
-      tzinfo (~> 1.1)
+      rake
-    addressable (2.7.0)
+      thor (>= 0.14.0)
-      public_suffix (>= 2.0.2, < 5.0)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.11.1)
     colorator (1.1.0)
-    commonmarker (0.17.13)
+    concurrent-ruby (1.3.4)
-      ruby-enum (~> 0.5)
+    em-websocket (0.5.3)
-    concurrent-ruby (1.1.6)
-    dnsruby (1.61.3)
-      addressable (~> 2.5)
-    em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
+      http_parser.rb (~> 0)
-    ethon (0.12.0)
-      ffi (>= 1.3.0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
+    ffi (1.17.0)
-    faraday (1.0.0)
+    ffi (1.17.0-aarch64-linux-gnu)
-      multipart-post (>= 1.2, < 3)
+    ffi (1.17.0-aarch64-linux-musl)
-    ffi (1.12.2)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
-    gemoji (3.0.1)
+    google-protobuf (3.25.5)
-    github-pages (197)
+    google-protobuf (3.25.5-aarch64-linux)
-      activesupport (= 4.2.10)
+    google-protobuf (3.25.5-arm64-darwin)
-      github-pages-health-check (= 1.16.1)
+    google-protobuf (3.25.5-x86-linux)
-      jekyll (= 3.7.4)
+    google-protobuf (3.25.5-x86_64-darwin)
-      jekyll-avatar (= 0.6.0)
+    google-protobuf (3.25.5-x86_64-linux)
-      jekyll-coffeescript (= 1.1.1)
+    http_parser.rb (0.8.0)
-      jekyll-commonmark-ghpages (= 0.1.5)
+    i18n (1.14.6)
-      jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.11.0)
-      jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.12.1)
-      jekyll-mentions (= 1.4.1)
-      jekyll-optional-front-matter (= 0.3.0)
-      jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.2.0)
-      jekyll-redirect-from (= 0.14.0)
-      jekyll-relative-links (= 0.6.0)
-      jekyll-remote-theme (= 0.3.1)
-      jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.5.0)
-      jekyll-sitemap (= 1.2.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.1.1)
-      jekyll-theme-cayman (= 0.1.1)
-      jekyll-theme-dinky (= 0.1.1)
-      jekyll-theme-hacker (= 0.1.1)
-      jekyll-theme-leap-day (= 0.1.1)
-      jekyll-theme-merlot (= 0.1.1)
-      jekyll-theme-midnight (= 0.1.1)
-      jekyll-theme-minimal (= 0.1.1)
-      jekyll-theme-modernist (= 0.1.1)
-      jekyll-theme-primer (= 0.5.3)
-      jekyll-theme-slate (= 0.1.1)
-      jekyll-theme-tactile (= 0.1.1)
-      jekyll-theme-time-machine (= 0.1.1)
-      jekyll-titles-from-headings (= 0.5.1)
-      jemoji (= 0.10.2)
-      kramdown (= 1.17.0)
-      liquid (= 4.0.0)
-      listen (= 3.1.5)
-      mercenary (~> 0.3)
-      minima (= 2.5.0)
-      nokogiri (>= 1.8.5, < 2.0)
-      rouge (= 2.2.1)
-      terminal-table (~> 1.4)
-    github-pages-health-check (1.16.1)
-      addressable (~> 2.3)
-      dnsruby (~> 1.60)
-      octokit (~> 4.0)
-      public_suffix (~> 3.0)
-      typhoeus (~> 1.3)
-    html-pipeline (2.12.3)
-      activesupport (>= 2)
-      nokogiri (>= 1.4)
-    http_parser.rb (0.6.0)
-    i18n (0.9.5)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    jekyll (4.3.4)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
+      i18n (~> 1.0)
-      jekyll-sass-converter (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.3.3)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-    jekyll-avatar (0.6.0)
+      terminal-table (>= 1.8, < 4.0)
-      jekyll (~> 3.0)
+      webrick (~> 1.7)
-    jekyll-coffeescript (1.1.1)
-      coffee-script (~> 2.2)
-      coffee-script-source (~> 1.11.1)
-    jekyll-commonmark (1.3.1)
-      commonmarker (~> 0.14)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-commonmark-ghpages (0.1.5)
-      commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.11.0)
-      jekyll (~> 3.3)
-    jekyll-gist (1.5.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.12.1)
-      jekyll (~> 3.4)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-mentions (1.4.1)
-      html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
     jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.2.0)
+    jekyll-sass-converter (3.0.0)
-      jekyll (~> 3.0)
+      sass-embedded (~> 1.54)
-    jekyll-redirect-from (0.14.0)
+    jekyll-sitemap (1.4.0)
-      jekyll (~> 3.3)
+      jekyll (>= 3.7, < 5.0)
-    jekyll-relative-links (0.6.0)
-      jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
-      jekyll (~> 3.5)
-      rubyzip (>= 1.2.1, < 3.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.5.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.3)
-      jekyll (~> 3.5)
-      jekyll-github-metadata (~> 2.9)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.1)
-      jekyll (~> 3.3)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.10.2)
+    kramdown (2.5.1)
-      gemoji (~> 3.0)
+      rexml (>= 3.3.9)
-      html-pipeline (~> 2.2)
+    kramdown-parser-gfm (1.1.0)
-      jekyll (~> 3.0)
+      kramdown (~> 2.0)
-    kramdown (1.17.0)
+    liquid (4.0.4)
-    liquid (4.0.0)
+    listen (3.9.0)
-    listen (3.1.5)
+      rb-fsevent (~> 0.10, >= 0.10.3)
-      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.10)
-      rb-inotify (~> 0.9, >= 0.9.7)
+    mercenary (0.4.0)
-      ruby_dep (~> 1.2)
-    markdown_helper (2.5.3)
-    mercenary (0.3.6)
-    mini_portile2 (2.4.0)
-    minima (2.5.0)
-      jekyll (~> 3.5)
-      jekyll-feed (~> 0.9)
-      jekyll-seo-tag (~> 2.1)
-    minitest (5.14.0)
-    multipart-post (2.1.1)
-    nokogiri (1.10.9)
-      mini_portile2 (~> 2.4.0)
-    octokit (4.16.0)
-      faraday (>= 0.9)
-      sawyer (~> 0.8.0, >= 0.5.3)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (3.1.1)
+    public_suffix (6.0.1)
-    rb-fsevent (0.10.3)
+    rake (12.3.3)
-    rb-inotify (0.10.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rouge (2.2.1)
+    rexml (3.3.9)
-    ruby-enum (0.7.2)
+    rouge (4.5.1)
-      i18n
-    ruby_dep (1.5.0)
-    rubyzip (2.2.0)
     safe_yaml (1.0.5)
-    sass (3.7.4)
+    sass-embedded (1.77.5-aarch64-linux-android)
-      sass-listen (~> 4.0.0)
+      google-protobuf (>= 3.25, < 5.0)
-    sass-listen (4.0.0)
+    sass-embedded (1.77.5-aarch64-linux-gnu)
-      rb-fsevent (~> 0.9, >= 0.9.4)
+      google-protobuf (>= 3.25, < 5.0)
-      rb-inotify (~> 0.9, >= 0.9.7)
+    sass-embedded (1.77.5-aarch64-linux-musl)
-    sawyer (0.8.2)
+      google-protobuf (>= 3.25, < 5.0)
-      addressable (>= 2.3.5)
+    sass-embedded (1.77.5-aarch64-mingw-ucrt)
-      faraday (> 0.8, < 2.0)
+      google-protobuf (>= 3.25, < 5.0)
-    terminal-table (1.8.0)
+    sass-embedded (1.77.5-arm-linux-androideabi)
-      unicode-display_width (~> 1.1, >= 1.1.1)
+      google-protobuf (>= 3.25, < 5.0)
-    thread_safe (0.3.6)
+    sass-embedded (1.77.5-arm-linux-gnueabihf)
-    typhoeus (1.3.1)
+      google-protobuf (>= 3.25, < 5.0)
-      ethon (>= 0.9.0)
+    sass-embedded (1.77.5-arm-linux-musleabihf)
-    tzinfo (1.2.6)
+      google-protobuf (>= 3.25, < 5.0)
-      thread_safe (~> 0.1)
+    sass-embedded (1.77.5-arm64-darwin)
-    unicode-display_width (1.6.1)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-mingw-ucrt)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-darwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    thor (1.3.2)
+    unicode-display_width (2.6.0)
+    webrick (1.9.1)
 
 PLATFORMS
-  ruby
+  aarch64-linux
+  aarch64-linux-android
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  aarch64-mingw-ucrt
+  arm-linux-androideabi
+  arm-linux-gnu
+  arm-linux-gnueabihf
+  arm-linux-musl
+  arm-linux-musleabihf
+  arm64-darwin
+  riscv64-linux-android
+  riscv64-linux-gnu
+  riscv64-linux-musl
+  x86-cygwin
+  x86-linux
+  x86-linux-android
+  x86-linux-gnu
+  x86-linux-musl
+  x86-mingw-ucrt
+  x86_64-cygwin
+  x86_64-darwin
+  x86_64-linux-android
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
-  github-pages (= 197)
+  appraisal (~> 2.5)
-  jekyll
+  beautiful-jekyll-theme!
-  jekyll-paginate
+  bundler (>= 1.16)
-  markdown_helper (~> 2.5, >= 2.5.2)
+  rake (~> 12.0)
 
 BUNDLED WITH
-   2.0.2
+   2.5.22

blog.bryanroessler.com/_config.yml

@@ -1,27 +1,24 @@
-# --- General options --- #
+###########################################################
+### Welcome to Beautiful Jekyll!
+### This config file is meant for settings that affect your entire website. When you first
+### set up your website you should go through all these settings and edit them, but after
+### the initial set up you won't need to come back to this file often.
+###########################################################
 
-# url is the full website URL
+############################
-# baseurl is the website's URL without the hostname
+# --- Required options --- #
-
+############################
-# If you are building a simple GitHub user page (http://username.github.io) then use these settings:
-url: "https://blog.bryanroessler.com"
-baseurl: ""
-
-# If you are building a GitHub project page then use these settings:
-#url: "http://username.github.io/projectname"
-#baseurl: "/projectname"
-
-# Of course don't forget to change the username and projectname to YOUR username and project
 
 # Name of website
 title: Bryan Roessler
 
-# Short description of your site
+# Your name to show in the footer
-description: Ordo ab chao
+author: Bryan Roessler
 
-# --- Navigation bar options --- #
+###############################################
+# --- List of links in the navigation bar --- #
+###############################################
 
-# List of links in the navigation bar
 navbar-links:
   Home: "https://bryanroessler.com"
   Blog: "https://blog.bryanroessler.com"
@@ -31,81 +28,152 @@ navbar-links:
     - Syncthing: "https://syncthing.bryanroessler.com"
     - Panel: "https://panel.bryanroessler.com"
 
-# Image to show in the navigation bar - image must be a square (width = height)
+################
+# --- Logo --- #
+################
+
+# Image to show in the navigation bar - works best with a square image
 # Remove this parameter if you don't want an image in the navbar
-avatar: "/img/me_square_sepia_small.jpg"
+avatar: "/assets/img/me_square_sepia_small.jpg"
 
-# If you want to have an image logo in the top-left corner instead of the title text,
+# By default, the image is cut into a circle. You can disable this behaviour by setting 'round-avatar: false'
+round-avatar: true
+
+# If you want to have an image logo in the top-left corner instead of having the title of the website,
 # then specify the following parameter
-#title-img: "./img/me_square_sepia_small.jpg"
+#title-img: /path/to/image
 
-# --- Background colour/image options --- #
 
-# Personalize the colors in your website. Colour values can be any valid CSS colour
+#####################################
+# --- Footer social media links --- #
+#####################################
 
-navbar-col: "#F5F5F5"
+# Select the social network links that you want to show in the footer.
-navbar-text-col: "#404040"
+# You can change the order that they show up on the page by changing the order here.
-navbar-children-col: "#F5F5F5"
+# Uncomment the links you want to show and add your information to each one.
-page-col: "#FFFFFF"
-link-col: "#008AFF"
-hover-col: "#0085A1"
-footer-col: "#F5F5F5"
-footer-text-col: "#777777"
-footer-link-col: "#404040"
 
-# Alternatively, the navbar, footer, and page background can be set to use background images
-# instead of colour
-
-# navbar-img: "/img/bgimage.png"
-# footer-img: "/img/bgimage.png"
-# page-img: "/img/bgimage.png"
-
-# --- Footer options --- #
-
-# Change all these values or delete the ones you don't want.
-# Important: you must keep the "name" parameter, everything else you can remove
-author:
-  name: Bryan Roessler
-
-# Select your active Social Network Links.
-# Uncomment the links you want to show in the footer and add your information to each link.
-# You can reorder the items to define the link order.
-# If you want to add a new link that isn't here, you'll need to also edit the file _data/SocialNetworks.yml
 social-network-links:
-  rss: true
   email: "bryanroessler@gmail.com"
-#  facebook: daattali
+  rss: true
+# facebook:
   github: "https://git.bryanroessler.com"
-#  twitter: daattali
+# twitter:
-#  reddit: yourname
+# reddit:
-#  google-plus: +DeanAttali
+# google-plus:
   linkedin: bryan-roessler-phd-47535a60
-#  xing: yourname
+# youtube:
-#  stackoverflow: "3943160/daattali"
+# medium:
-#  snapchat: deanat78
+# spotify: yourname
-#  instagram: deanat78
+# telephone: +14159998888
-#  youtube: user/deanat78
+# steam: deanat78
-#  spotify: yourname
+# twitch: yourname
-#  telephone: +14159998888
+# yelp: yourname
-#  steam: deanat78
+# telegram: yourname
-#  twitch: yourname
+# calendly: yourname
-#  yelp: yourname
+# mastodon: instance.url/@username
+# bluesky: yourname
+# ORCID: your ORCID ID
+# google-scholar: your google scholar
+# discord: "invite_code" or "users/userid" or "invite/invite_code"
+# kaggle: yourname
+# hackerrank: yourname
+# gitlab: yourname
+# itchio: yourname
+# untappd: yourname
 
-# Select which share links to show in posts
+# If you want your website to generate an RSS feed, provide a description
+# The URL for the feed will be https://<your_website>/feed.xml
+rss-description: Bryan Roessler's Blog
+
+###########################
+# --- General options --- #
+###########################
+
+# Select which social network share links to show in posts
 share-links-active:
   twitter: false
   facebook: false
-  google: false
   linkedin: false
+  vk: false
 
 # How to display the link to the website in the footer
 # Remove this if you don't want a link in the footer
-url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
+url-pretty: "bryanroessler.com"
 
-# --- Web Statistics Section --- #
+# Add the website title to the title of every page
+title-on-all-pages: true
+
+# Excerpt word length - Truncate the excerpt of each post on the feed page to the specified number of words
+excerpt_length: 50
+
+# Whether or not to show an excerpt for every blog post in the feed page
+feed_show_excerpt: true
+
+# Whether or not to show a list of tags below each post preview in the feed page
+feed_show_tags: true
+
+# Add a search button to the navbar
+post_search: true
+
+# Add a button in the footer to edit the current page. Only works if your website is hosted on GitHub
+edit_page_button: true
+
+# Allow sub-menu items (second-level navigation menu items) to be longer than the top-level menu
+# If this setting is off, then long sub-menu words might get cut off
+# See https://github.com/daattali/beautiful-jekyll/issues/765 to understand the issue this setting can solve
+navbar-var-length: false
+
+# The keywords to associate with your website, for SEO purposes
+#keywords: "my,list,of,keywords"
+
+######################################
+# --- Colours / background image --- #
+######################################
+
+# Personalize the colours in your website. Colour values can be any valid CSS colour
+
+page-col: "#FFFFFF"
+text-col: "#404040"
+link-col: "#008AFF"
+hover-col: "#0085A1"
+navbar-col: "#F5F5F5" # #EAEAEA
+navbar-text-col: "#404040"
+navbar-border-col: "#DDDDDD"
+footer-col: "#F5F5F5" # #EAEAEA
+footer-text-col: "#777777"
+footer-link-col: "#404040"
+footer-hover-col: "#0085A1"
+
+# Alternatively, the navbar, footer, and page background can be set to an image
+# instead of colour
+
+#navbar-img: "/assets/img/bgimage.png"
+#footer-img: "/assets/img/bgimage.png"
+#page-img: "/assets/img/bgimage.png"
+
+# Suggest a colour for mobile browsers to use as the browser's theme. This is only supported by a few mobile browsers.
+#mobile-theme-col: "#0085A1"
+
+# For any extra visual customization, you can include additional CSS files in every page on your site. List any custom CSS files here
+#site-css:
+#  - "/assets/css/custom-styles.css"
+
+# If you have common JavaScript files that should be included in every page, list them here
+#site-js:
+#  - "/assets/js/custom-script.js"
+
+#################################
+# --- Web Analytics Section --- #
+#################################
+
+# Fill in your Google Analytics tag ID (or "Measurement ID") to track your website usage
+#gtag: "G-XXXXXXXXXX"
+
+# Fill in your Cloudflare Analytics beacon token to track your website using Cloudflare Analytics
+#cloudflare_analytics: ""
 
 # Fill in your Google Analytics ID to track your website using GA
-#google_analytics: ""
+google_analytics: "UA-158358388-1"
 
 # Google Tag Manager ID
 #gtm: ""
@@ -113,51 +181,82 @@ url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
 # Matomo (aka Piwik) Web statistics
 # Uncomment the following section to enable Matomo. The opt-out parameter controls
 # whether or not you want to allow users to opt out of tracking.
-
 #matomo:
 #  site_id: "9"
 #  uri: "demo.wiki.pro"
 #  opt-out: true
 
+# Google Universal Analytics ID -- deprecated
+# As of July 2023 this is no longer supported by Google! If you are still using `google_analytics`,
+# you should switch to using the `gtag` field above instead.
+#google_analytics: "UA-XXXXXXXX-X"
+
+####################
 # --- Comments --- #
+####################
 
-# Fill in your Disqus shortname (NOT the userid) if you want to support Disqus comments
+# To use Disqus comments, sign up to https://disqus.com and fill in your Disqus shortname (NOT the userid)
-# disqus: ""
+#disqus: ""
 
-# If you want to use JustComments fill with the API Key
+# To use Facebook Comments, create a Facebook app and fill in the Facebook App ID
-#just-comments: "ABCD-EFGH-IJKL"
+#fb_comment_id: ""
 
-# To use Facebook Comments, fill in a Facebook App ID
+# To use CommentBox, sign up for a Project ID on https://commentbox.io
-# fb_comment_id: ""
+#commentbox: "" # Project ID, e.g. "5694267682979840-proj"
 
-# To use Staticman comments, fill in repository, branch, and endpoint
+# To use Utterances comments: (0) uncomment the following section, (1) fill in
-staticman:
+# "repository" (make sure the repository is public), (2) Enable Issues in your repository,
-  repository : # GitHub username/repository eg. "daattali/beautiful-jekyll"
+# (3) Install the Utterances app in your repository https://github.com/apps/utterances
-  branch     : master # If you're not using `master` branch, then you also need to update the `branch` parameter in `staticman.yml`
+# See more details about the parameters below at https://utteranc.es/
-  endpoint   : # URL of your own deployment, with a trailing slash (will fallback to a public GitLab instance) eg. https://<your-api>/v3/entry/github/
+#utterances:
-  reCaptcha:
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
-    # reCaptcha for Staticman (OPTIONAL, but recommended for spam protection)
+#  issue-term: title   # Mapping between blog posts and GitHub issues
-    # If you use reCaptcha, you must also set these parameters in staticman.yml
+#  theme: github-light # Utterances theme
-    siteKey  : # Use your own site key, you need to apply for one on Google
+#  label: blog-comments # Label that will be assigned to GitHub Issues created by Utterances
-    secret   : # ENCRYPT your password by going to https://staticman3.herokuapp.com/v3/encrypt/<your-site-secret>
 
+# To use Staticman comments, uncomment the following section. You may leave the reCaptcha
+# section commented if you aren't using reCaptcha for spam protection.
+# Using Staticman requires advanced knowledge, please consult
+# https://github.com/eduardoboucas/staticman/ and https://staticman.net/ for further
+# instructions. For any support with staticman please direct questions to staticman and
+# not to BeautifulJekyll.
+#staticman:
+#  repository : # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  branch     : master # If you're not using `master` branch, then you also need to update the `branch` parameter in `staticman.yml`
+#  endpoint   : # URL of your deployment, with a trailing slash eg. "https://<your-api>/v3/entry/github/"
+#  reCaptcha:   # (optional, set these parameters in `staticman.yml` as well)
+#    siteKey  : # You need to apply for a site key on Google
+#    secret   : # Encrypt your password by going to https://<your-own-api>/v3/encrypt/<your-site-secret>
+
+# To use giscus comments:
+# (0) Uncomment the following giscus section, (1) Enable Discussions in your GitHub repository,
+# (2) Install the giscus app in your repository (details at https://giscus.app),
+# (3) Fill in *all* the parameters below
+# See more details about giscus and each of the following parameters at https://giscus.app
+#giscus:
+#  hostname: giscus.app # Replace with your giscus instance's hostname if self-hosting
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  repository-id: # ID of your repository, retrieve this info from https://giscus.app
+#  category: Announcements # Category name of your GitHub Discussion posts
+#  category-id: # ID of your category, retrieve this info from https://giscus.app
+#  mapping: pathname
+#  reactions-enabled: 1
+#  emit-metadata: 0
+#  theme: light
+
+################
 # --- Misc --- #
+################
 
-# Facebook App ID
+# Ruby Date Format to show dates of posts
-# fb_app_id: ""
-
-# Excerpt Word Length
-# Truncates the excerpt to the specified number of words on the index page
-excerpt_length: 50
-
-# Character used to separate site title and description in HTML document title
-# and RSS feed title
-title-separator: "-"
-
-# Ruby Date Format
 date_format: "%B %-d, %Y"
 
-# --- Don't need to touch anything below here (but you can if you want) --- #
+# Facebook App ID
+#fb_app_id: ""
+
+#################################################################################
+# --- You don't need to touch anything below here (but you can if you want) --- #
+#################################################################################
 
 # Output options (more information on Jekyll's site)
 timezone: "America/New_York"
@@ -166,6 +265,8 @@ highlighter: rouge
 permalink: /:year-:month-:day-:title/
 paginate: 5
 
+plugins: [jekyll-paginate]
+
 kramdown:
   input: GFM
 
@@ -177,86 +278,27 @@ defaults:
       type: "posts"
     values:
       layout: "post"
-      comments: true  # add comments to all blog posts
+      comments: false  # add comments to all blog posts
       social-share: true # add social media sharing buttons to all blog posts
+      readtime: true # add estimated reading time on all blog posts
   -
     scope:
-      path: "" # all files
+      path: "" # any file that's not a post will be a "page" layout by default
     values:
       layout: "page"
-      show-avatar: true
-
-# Use tags index page and make tags on each post clickable
-link-tags: true
 
 # Exclude these files from production site
 exclude:
   - CHANGELOG.md
   - CNAME
-  - Dockerfile
   - Gemfile
   - Gemfile.lock
   - LICENSE
   - README.md
-  - Vagrantfile
+  - screenshot.png
-
+  - docs/
-# prose.io config
+  - vendor/
-prose:
-  rooturl: '_posts'
-  media: 'img'
-  ignore:
-    - 404.html
-    - LICENSE
-    - feed.xml
-    - _config.yml
-    - /_layouts
-    - /_includes
-    - /css
-    - /img
-    - /js
-  metadata:
-    _posts:
-      - name: "layout"
-        field:
-          element: "hidden"
-          value: "post"
-      - name: "title"
-        field:
-          element: "text"
-          label: "Post title"
-          placeholder: "Title"
-          alterable: true
-      - name: "subtitle"
-        field:
-          element: "textarea"
-          label: "Subtitle"
-          placeholder: "A description of your post."
-          alterable: true
-      - name: "date"
-        field:
-          element: "text"
-          label: "Date"
-          help: "Enter date of post."
-          placeholder: "yyyy-mm-dd"
-          alterable: true
-      - name: "image"
-        field:
-          element: "text"
-          label: "Image"
-          help: "Add a thumbnail image to your post."
-          placeholder: "Thumbnail"
-          alterable: true
-      - name: "published"
-        field:
-          element: "checkbox"
-          label: "Publish"
-          help: "Check to publish post, uncheck to hide."
 
 plugins:
   - jekyll-paginate
   - jekyll-sitemap
-
-exclude: [vendor]
-
-# Beautiful Jekyll / Dean Attali
-# 2fc73a3a967e97599c9763d05e564189

blog.bryanroessler.com/_includes/cloudflare_analytics.html

@@ -0,0 +1,8 @@
+{% if site.cloudflare_analytics %}
+<!-- Cloudflare Web Analytics -->
+<script defer
+    src='https://static.cloudflareinsights.com/beacon.min.js'
+    data-cf-beacon='{"token": "{{ site.cloudflare_analytics}}"}'>
+</script>
+<!-- End Cloudflare Web Analytics -->
+{% endif %}

blog.bryanroessler.com/_includes/commentbox.html

@@ -0,0 +1,7 @@
+{% if site.commentbox %}
+
+    <div class="commentbox"></div>
+    <script src="https://unpkg.com/commentbox.io/dist/commentBox.min.js"></script>
+    <script>commentBox('{{ site.commentbox }}')</script>
+
+{% endif %}

blog.bryanroessler.com/_includes/comments.html

@@ -0,0 +1,8 @@
+{% if page.comments %}
+  {% include disqus.html %}
+  {% include fb-comment.html %}
+  {% include staticman-comments.html %}
+  {% include utterances-comment.html %}
+  {% include giscus-comment.html %}
+  {% include commentbox.html %}
+{% endif %}

blog.bryanroessler.com/_includes/footer-minimal.html

@@ -10,7 +10,7 @@
 
     {% if site.url-pretty %}
       •  
-    <a href="{{ '' | absolute_url }}">{{ site.url-pretty }}</a>
+    <a href="{{ site.url }}">{{ site.url-pretty }}</a>
     {% endif %}
   </div>
 </footer>

blog.bryanroessler.com/_includes/giscus-comment.html

@@ -0,0 +1,16 @@
+{% if site.giscus.repository and site.giscus.hostname %}
+
+<script src="https://{{ site.giscus.hostname }}/client.js"
+        data-repo="{{ site.giscus.repository }}"
+        data-repo-id="{{ site.giscus.repository-id }}"
+        data-category="{{ site.giscus.category }}"
+        data-category-id="{{ site.giscus.category-id }}"
+        data-mapping="{{ site.giscus.mapping }}"
+        data-reactions-enabled="{{ site.giscus.reactions-enabled }}"
+        data-emit-metadata="{{ site.giscus.emit-metadata }}"
+        data-theme="{{ site.giscus.theme }}"
+        crossorigin="anonymous"
+        async>
+</script>
+
+{% endif %}

blog.bryanroessler.com/_includes/mathjax.html

@@ -0,0 +1,12 @@
+{% if page.mathjax %}
+<script type="text/javascript">
+  MathJax = {
+    options: {
+      skipHtmlTags: [
+        'script', 'noscript', 'style', 'textarea', 'pre', 'code'
+      ]
+    }
+  };
+</script>
+<script type="text/javascript" async src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
+{% endif %}

blog.bryanroessler.com/_includes/readtime.html

@@ -0,0 +1,16 @@
+<!--- "ReadTime on GitHub Jekyll" (c) 2020 Ruby Griffith Ramirez, MIT License -->
+
+{% assign ReadTime = page.content | strip_html | number_of_words %}
+{% assign calcReadTime = ReadTime | float %}
+{% assign finalReadTime = calcReadTime | divided_by:200 | round: 2 %}
+{% assign number = finalReadTime | round %}
+{% if number >= 1 %}
+  {% assign yesReadTime = number | append: " minute read" %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ yesReadTime }}</span>
+{% elsif number < 1 %}
+  {% assign minReadTime = '&lt; 1 minute read' %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ minReadTime }}</span>
+{% else %}
+  {% assign nilReadTime = number | replace:'0',' ' %}
+  {{ nilReadTime }}
+{% endif %}

blog.bryanroessler.com/_includes/search.html

@@ -0,0 +1,19 @@
+{% if site.post_search %}
+
+<div id="beautifuljekyll-search-overlay">
+
+  <div id="nav-search-exit" title="Exit search">✕</div>
+  <input type="text" id="nav-search-input" placeholder="Search">
+  <ul id="search-results-container"></ul>
+  
+  <script src="https://unpkg.com/simple-jekyll-search@latest/dest/simple-jekyll-search.min.js"></script>
+  <script>
+    SimpleJekyllSearch({
+      searchInput: document.getElementById('nav-search-input'),
+      resultsContainer: document.getElementById('search-results-container'),
+      json: '{{ site.baseurl }}/assets/data/searchcorpus.json' 
+    });
+  </script>
+</div>
+
+{% endif %}

blog.bryanroessler.com/_includes/social-networks-links.html

@@ -0,0 +1,401 @@
+{% if site.social-network-links %}
+<ul class="list-inline text-center footer-links">
+
+{%- for network in site.social-network-links -%}
+
+  {%- if network[0] == "rss" and network[1] and site.rss-description -%}
+  <li class="list-inline-item">
+    <a href="{{ '/feed.xml' | relative_url }}" title="RSS">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-rss fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">RSS</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "email" -%}
+  <li class="list-inline-item">
+    <a href="mailto:{{ network[1] }}" title="Email me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-envelope fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Email me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "calendly" -%}
+  <li class="list-inline-item">
+    <a href="https://calendly.com/{{ network[1] }}" title="Schedule a meeting with me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-calendar-check fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Schedule a meeting with me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "facebook" -%}
+  <li class="list-inline-item">
+    <a href="https://www.facebook.com/{{ network[1] }}" title="Facebook">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-facebook fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Facebook</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telegram" -%}
+  <li class="list-inline-item">
+    <a href="https://t.me/{{ network[1] }}" title="Telegram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-telegram-plane fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Telegram</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "whatsapp" -%}
+  <li class="list-inline-item">
+    <a href="https://wa.me/{{ network[1] }}" title="Whatsapp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-whatsapp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Whatsapp</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "github" -%}
+  <li class="list-inline-item">
+    <a href="https://github.com/{{ network[1] }}" title="GitHub">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-github fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitHub</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "gitlab" -%}
+  <li class="list-inline-item">
+    <a href="https://gitlab.com/{{ network[1] }}" title="GitLab">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-gitlab fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitLab</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitter" -%}
+  <li class="list-inline-item">
+    <a href="https://twitter.com/{{ network[1] }}" title="X (Twitter)">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-x-twitter fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">X (Twitter)</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "reddit" -%}
+  {% assign reddit_start = network[1] | split: "/" | first -%}
+  {% unless reddit_start == 'r' or reddit_start == 'u' -%}
+    {% assign reddit_url_prefix = 'u/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://reddit.com/{{ reddit_url_prefix }}{{ network[1] }}" title="Reddit">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-reddit fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Reddit</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "linkedin" -%}
+  <li class="list-inline-item">
+    <a href="https://linkedin.com/in/{{ network[1] }}" title="LinkedIn">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-linkedin fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">LinkedIn</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "xing" -%}
+  <li class="list-inline-item">
+    <a href="https://www.xing.com/profile/{{ network[1] }}" title="Xing">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-xing fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Xing</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "stackoverflow" -%}
+  <li class="list-inline-item">
+    <a href="https://stackoverflow.com/users/{{ network[1] }}" title="StackOverflow">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-stack-overflow fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">StackOverflow</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "snapchat" -%}
+  <li class="list-inline-item">
+    <a href="https://www.snapchat.com/add/{{ network[1] }}" title="Snapchat">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-snapchat-ghost fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Snapchat</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "instagram" -%}
+  <li class="list-inline-item">
+    <a href="https://www.instagram.com/{{ network[1] }}" title="Instagram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-instagram fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Instagram</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "youtube" -%}
+  <li class="list-inline-item">
+    <a href="https://www.youtube.com/{{ network[1] }}" title="YouTube">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-youtube fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">YouTube</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "spotify" -%}
+  <li class="list-inline-item">
+    <a href="https://open.spotify.com/user/{{ network[1] }}" title="Spotify">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-spotify fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Spotify</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telephone" -%}
+  <li class="list-inline-item">
+    <a href="tel:{{ network[1] }}" title="Phone">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-phone fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Phone</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "steam" -%}
+  <li class="list-inline-item">
+    <a href="https://steamcommunity.com/id/{{ network[1] }}" title="Steam">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-steam fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Steam</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitch" -%}
+  <li class="list-inline-item">
+    <a href="https://www.twitch.tv/{{ network[1] }}" title="Twitch">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-twitch fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Twitch</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "yelp" -%}
+  <li class="list-inline-item">
+    <a href="https://yelp.com/{{ network[1] }}" title="Yelp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-yelp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Yelp</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "mastodon" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://{{ network[1] }}" title="Mastodon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-mastodon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Mastodon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "bluesky" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://bsky.app/profile/{{ network[1] }}" title="Bluesky">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-square fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Bluesky</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "ORCID" -%}
+ <li class="list-inline-item">
+   <a href="https://orcid.org/{{ network[1] }}" title="ORCID">
+     <span class="fa-stack fa-lg" aria-hidden="true">
+       <i class="fas fa-circle fa-stack-2x"></i>
+       <i class="fab fa-orcid fa-stack-1x fa-inverse"></i>
+     </span>
+     <span class="sr-only">ORCID</span>
+   </a>
+ </li>
+  {%- endif -%}
+
+  {%- if network[0] == "google-scholar" -%}
+  <li class="list-inline-item">
+    <a href="https://scholar.google.com/citations?user={{ network[1] }}" title="Google Scholar">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fa fa-graduation-cap fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Google Scholar</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "patreon" -%}
+  <li class="list-inline-item">
+    <a href="https://patreon.com/{{ network[1] }}" title="Patreon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-patreon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Patreon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "medium" -%}
+  <li class="list-inline-item">
+    <a href="https://medium.com/@{{ network[1] }}" title="Medium">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-medium fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Medium</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "itchio" -%}
+  <li class="list-inline-item">
+    <a href="https://{{ network[1] }}.itch.io/" title="Itchio">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-itch-io fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Itchio</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "discord" -%}
+  {% assign discord_start = network[1] | split: "/" | first -%}
+  {% unless discord_start == 'users' or discord_start == 'invite' -%}
+    {% assign discord_url_prefix = 'invite/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://discord.com/{{discord_url_prefix}}{{network[1]}}" title="Discord">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-discord fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Discord</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "kaggle" -%}
+  <li class="list-inline-item">
+    <a href="https://www.kaggle.com/{{ network[1] }}" title="Kaggle">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-kaggle fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Kaggle</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "hackerrank" -%}
+  <li class="list-inline-item">
+    <a href="https://www.hackerrank.com/{{ network[1] }}" title="Hackerrank">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-hackerrank fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Hackerrank</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "untappd" -%}
+  <li class="list-inline-item">
+    <a href="https://untappd.com/user/{{ network[1] }}" title="Untappd">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-untappd fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Untappd</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+{%- endfor -%}
+
+</ul>
+{% endif %}

blog.bryanroessler.com/_includes/utterances-comment.html

@@ -0,0 +1,13 @@
+{% if site.utterances.repository and site.utterances.issue-term  %}
+
+<script src="https://utteranc.es/client.js"
+        repo="{{ site.utterances.repository }}"
+        issue-term="{{ site.utterances.issue-term }}"
+        theme="{{ site.utterances.theme}}"
+        label="{{ site.utterances.label}}"
+        crossorigin="anonymous"
+        async>
+</script>
+
+{% endif %}
+

blog.bryanroessler.com/_layouts/home.html

@@ -0,0 +1,122 @@
+---
+layout: page
+---
+
+{{ content }}
+
+{% assign posts = paginator.posts | default: site.posts %}
+
+<!-- role="list" needed so that `list-style: none` in Safari doesn't remove the list semantics -->
+<ul class="posts-list list-unstyled" role="list">
+  {% for post in posts %}
+  <li class="post-preview">
+    <article>
+
+      {%- capture thumbnail -%}
+        {% if post.thumbnail-img %}
+          {{ post.thumbnail-img }}
+        {% elsif post.cover-img %}
+          {% if post.cover-img.first %}
+            {{ post.cover-img[0].first.first }}
+          {% else %}
+            {{ post.cover-img }}
+          {% endif %}
+        {% else %}
+        {% endif %}
+      {% endcapture %}
+      {% assign thumbnail=thumbnail | strip %}
+
+      {% if site.feed_show_excerpt == false %}
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-normal">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+      {% endif %}
+
+      <a href="{{ post.url | absolute_url }}">
+        <h2 class="post-title">{{ post.title | strip_html }}</h2>
+
+        {% if post.subtitle %}
+          <h3 class="post-subtitle">
+          {{ post.subtitle | strip_html }}
+          </h3>
+        {% endif %}
+      </a>
+
+      {% if post.author %}
+        <span>By <strong>{{ post.author | strip_html }}</strong></span>
+      {% endif %}
+      <p class="post-meta">
+        {% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+        Posted on {{ post.date | date: date_format }}
+      </p>
+
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-small">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+
+      {% unless site.feed_show_excerpt == false %}
+      {% if thumbnail != "" %}
+      <div class="post-image post-image-short">
+        <a href="{{ post.url | absolute_url }}" aria-label="Thumbnail">
+          <img src="{{ thumbnail | absolute_url }}" alt="Post thumbnail">
+        </a>
+      </div>
+      {% endif %}
+
+      <div class="post-entry">
+        {% assign excerpt_length = site.excerpt_length | default: 50 %}
+        {{ post.excerpt | strip_html | truncatewords: excerpt_length }}
+        {% assign excerpt_word_count = post.excerpt | number_of_words %}
+        {% if post.content != post.excerpt or excerpt_word_count > excerpt_length %}
+          <a href="{{ post.url | absolute_url }}" class="post-read-more">[Read&nbsp;More]</a>
+        {% endif %}
+      </div>
+      {% endunless %}
+
+      {% if site.feed_show_tags != false and post.tags.size > 0 %}
+      <div class="blog-tags">
+        <span>Tags:</span>
+        <!-- role="list" needed so that `list-style: none` in Safari doesn't remove the list semantics -->
+        <ul class="d-inline list-inline" role="list">
+          {% for tag in post.tags %}
+          <li class="list-inline-item">
+            <a href="{{ '/tags' | absolute_url }}#{{- tag -}}">{{- tag -}}</a>
+          </li>
+          {% endfor %}
+        </ul>
+      </div>
+      {% endif %}
+
+    </article>
+  </li>
+  {% endfor %}
+</ul>
+
+{% if paginator.total_pages > 1 %}
+<ul class="pagination main-pager">
+  {% if paginator.previous_page %}
+  <li class="page-item previous">
+    <a class="page-link" href="{{ paginator.previous_page_path | absolute_url }}">
+      <i class="fas fa-arrow-left" alt="Newer Posts"></i>
+      <span class="d-none d-sm-inline-block">Newer Posts</span>
+    </a>
+  </li>
+  {% endif %}
+  {% if paginator.next_page %}
+  <li class="page-item next">
+    <a class="page-link" href="{{ paginator.next_page_path | absolute_url }}">
+      <span class="d-none d-sm-inline-block">Older Posts</span>
+      <i class="fas fa-arrow-right" alt="Older Posts"></i>
+    </a>
+  </li>
+  {% endif %}
+</ul>
+{% endif %}

blog.bryanroessler.com/_plugins/insert_git_code.rb

@@ -0,0 +1,21 @@
+require 'open-uri'
+
+module Jekyll
+    class InsertGitCode < Liquid::Tag
+
+        def initialize(tag_name, url, tokens)
+            super
+            url = url.strip()
+            @filename = File.basename(url)
+            encoded_url = URI.encode(url)
+            @file = URI.parse(encoded_url).read
+        end
+
+        def render(_context)
+            @file
+        end
+
+    end
+end
+
+Liquid::Template.register_tag('insert_git_code', Jekyll::InsertGitCode)

blog.bryanroessler.com/_posts/2018-06-22-strategies-for-maximizing-vps.md

@@ -11,26 +11,31 @@ The rapidly deflating prices of cloud storage (and other low-end) VPS services m
 VPS deal aggregate sites, such as [lowendbox](lowendbox.com), regularly provide offers on storage VPS services that rival shared web hosting or dedicated cloud backup providers. However, while the costs of cloud storage space have dropped dramatically, the CPU and memory configurations offered with the most storage VPS configurations are usually quite limited. Oftentimes a VPS provider will limit virtualized storage VPS instances to only 1 CPU core and <1GB memory (512MB is also common), since the intended use case is to simply provide enough resources for effective backup and retrieval.
 
 ### Selecting an OS
+
 For the purposes of minimizing RAM consumption on a low-end VPS, it is imperative to select an OS  that is lightweight, flexible, well-supported, and capable of running your intended services. Unfortunately, while most compute VPS instances provide a seemingly endless selection of server OSes to choose from, choices are usually limited on storage VPS instances by comparison. Windows Server is not a great choice because of its large memory footprint compared to its Linux-based equivalents. **Ubuntu Server LTS, CentOS, or Debian are usually safe bets**, but make sure to check that any third-party software (_i.e._ not in the repositories) that you intend to run are compatible with the libraries that ship with your Linux distribution of choice. The most common problem is trying to use newer software on older, stable Linux distributions. For example, [JRiver Media Center](https://yabb.jriver.com/interact/index.php/board,58.0.html) is built on Debian 8 Jessie but will not run on CentOS 7 because it ships with older C++ libraries. I prefer Redhat distributions (for reasons I will explain in a later post) but [my storage VPS host](www.time4vps.com) does not offer Fedora as an option (likely due to its short release cycle), which meant that my choices were limited to either Ubuntu 16.04 LTS or Debian 8. Expect for a base Linux OS installation to use ~125MB of RAM.
 
 ### Selecting a web server
+
 [Digital Ocean](https://www.digitalocean.com/community/tutorials/apache-vs-nginx-practical-considerations) offers an in-depth comparison of the two major web servers, Apache and Nginx. Long story short, **Nginx provides better performance and uses fewer resources than Apache** thanks to its asynchronous design. The Nginx process itself is single-threaded, which is perfect for a low-end VPS with only a single CPU core. Nginx can also be used as a [reverse proxy](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/) (using the `proxy_pass` block) to act as a secure front-end for other web services.
 
 ### Selecting a website generator
+
 In the past, web development for the layman necessitated using heavy content management systems like [Wordpress](wordpress.com) to handle website design and editing. Unfortunately, **a single instance of Wordpress can easily use up >256MB of RAM**, which would quickly gobble up the available resources on a low-end VPS. Additionally, Wordpress creates dynamic sites that chew up CPU cycles on the server to serve dynamic content whenever the site is accessed. Luckily there has recently been a shift among (primarily smaller) sites to using static site generators such as [**Jekyll**](https://jekyllrb.com/) (my favorite) or [HUGO](https://gohugo.io/) that compile sites beforehand and only serve static HTML/CSS versions of the page. This results in much lower overhead and resources, since post-compile there is nothing actually running except your web server (of course your OS may cache the site in memory to speed up future accesses).
 
 It's certainly possible to generate your sites locally and only transfer the output to your server's /www directory. However, since content creation in Jekyll is primarily some variation of Markdown language, I prefer using **Git** to push to the server and using post-hooks to generate the site remotely. It only takes a few seconds to generate most sites and as a result your source content is safely duplicated and version controlled on the storage VPS (that is the point of using a storage VPS in the first place, _right_?). As an alternative to git post-hooks (and for a slightly higher performance overhead), you can also use Jekyll's `--incremental` and `--watch` switches to easily and automatically regenerate selected site folders.
 
 ### Additional Services
+
 In addition to a lightweight web server, consider adding the following useful services:
+
 * Private Dynamic DNS
- * Use [MiniDynDNS](https://github.com/arkanis/minidyndns) to listen for IP address updates from your other computers (running a dynamic DNS client).
+  * Use [MiniDynDNS](https://github.com/arkanis/minidyndns) to listen for IP address updates from your other computers (running a dynamic DNS client).
 * File syncing
- * Run an [rsync daemon](https://www.atlantic.net/cloud-hosting/how-to-setup-rsync-daemon-linux-server/) to cache large numbers of incrementally-updated files without opening and closing an ssh connection.
+  * Run an [rsync daemon](https://www.atlantic.net/cloud-hosting/how-to-setup-rsync-daemon-linux-server/) to cache large numbers of incrementally-updated files without opening and closing an ssh connection.
- * For a slightly higher performance penalty, consider using [syncthing](https://syncthing.net/) to keep directories automatically synced between one or more computers. This can be useful when transferring static sites from a build server to the production server. Make sure to enable the file watcher functionality and decrease the full-scan interval to keep the cpu cycles to a minimum.
+  * For a slightly higher performance penalty, consider using [syncthing](https://syncthing.net/) to keep directories automatically synced between one or more computers. This can be useful when transferring static sites from a build server to the production server. Make sure to enable the file watcher functionality and decrease the full-scan interval to keep the cpu cycles to a minimum.
 * Code repository
- * Following Microsoft's recent acquisition of GitHub, many free software advocates are looking to plan B solutions or storing their git repositories online. [GitLab](https://about.gitlab.com/) is a popular alternative, but self-hosting can also make a lot of sense for small or personal projects. While GitLab is available to run on your own site, it is quite resource heavy, making it a poor choice for low-end storage VPS's. Lightweight alternatives include [**Gogs**](https://gogs.io/) and [cgit](https://git.zx2c4.com/cgit/). cgit is the lightest of the bunch, but Gogs presents a more familiar "Github-like" interface that is more comfortable for collaborators or others trying to view or clone your code.  
+  * Following Microsoft's recent acquisition of GitHub, many free software advocates are looking to plan B solutions or storing their git repositories online. [GitLab](https://about.gitlab.com/) is a popular alternative, but self-hosting can also make a lot of sense for small or personal projects. While GitLab is available to run on your own site, it is quite resource heavy, making it a poor choice for low-end storage VPS's. Lightweight alternatives include [**Gogs**](https://gogs.io/) and [cgit](https://git.zx2c4.com/cgit/). cgit is the lightest of the bunch, but Gogs presents a more familiar "Github-like" interface that is more comfortable for collaborators or others trying to view or clone your code.  
 * Certbot
- * Keep your LetsEncrypt HTTPS certificates automatically up-to-date. If you are using Nginx as a reverse proxy with subdomains, the new LetsEncrypt wildcard certificates can be used to secure all of your subdomains in one go. Don't forget to also include the root of your site in the certificate!
+  * Keep your LetsEncrypt HTTPS certificates automatically up-to-date. If you are using Nginx as a reverse proxy with subdomains, the new LetsEncrypt wildcard certificates can be used to secure all of your subdomains in one go. Don't forget to also include the root of your site in the certificate!
 * Media server
- * This can be as simple as an FTP server or as complicated as a dedicated media server program like the aforementioned JRiver Media Center.
+  * This can be as simple as an FTP server or as complicated as a dedicated media server program like the aforementioned JRiver Media Center.

blog.bryanroessler.com/_posts/2018-12-03-deploying-multiple-jekyll-sites.md

@@ -8,11 +8,12 @@ tags: [jekyll, git]
 
 As advertised, Jekyll is an excellent choice for building a simple (and secure!) personal or small business website. However, when compared to its better-known and bigger brethren, scaling the Jekyll workflow to manage multiple sites or subdomains is not readily apparent. In this post I will outline a git-based workflow to build and deploy a website with multiple subdomains.
 
-I prefer storing my work in version controlled git repositories in order to keep track of modifications and to assist in the backup and restore of my environment and data on multiple machines. One of the machines that I use to store this data [is also the cloud storage VPS that I use to run this site.]({{ {% post_url 2018-06-22-strategies-for-maximizing-vps %} | relative_url }}) The storage VPS holds the [bare website repositories](https://git.bryanroessler.com/bryan/www) that I can push to and pull from my other development machines. Since my website repositories contain jekyll site code, all that I need to do is to instruct the VPS to build and deploy that code!
+I prefer storing my work in version controlled git repositories in order to keep track of modifications and to assist in the backup and restore of my environment and data on multiple machines. One of the machines that I use to store this data [is also the cloud storage VPS that I use to run this site.]({% post_url 2018-06-22-strategies-for-maximizing-vps %}) The storage VPS holds the [bare website repositories](https://git.bryanroessler.com/bryan/www) that I can push to and pull from my other development machines. Since my website repositories contain jekyll site code, all that I need to do is to instruct the VPS to build and deploy that code!
 
 There are three steps that need to occur for this to happen seamlessly after the git repos have been created (which is outside the scope of this post).
 
 On the client:
+
 1. Push website changes to the server
 
 On the server:
@@ -29,6 +30,7 @@ For larger websites, I prefer using nested git repositories to simplify website
 By combining the subgit strategy with some structured naming conventions it is possible to push, build, and deploy multiple subdomains or sites using a single git push from the client!
 
 Example:
+
 ~~~bash
 #!/usr/bin/env bash
 "/var/lib/git/gogs/gogs" hook --config='/var/lib/git/gogs/conf/app.ini' post-receive
@@ -38,9 +40,9 @@ TMP_GIT_DIR="/tmp/${GIT_DIR##*/}"
 
 if [[ ! -d "${TMP_GIT_DIR}" ]]; then
     git clone "${GIT_DIR}" "${TMP_GIT_DIR}"
-    cd "${TMP_GIT_DIR}"
+    cd "${TMP_GIT_DIR}" || exit $?
 else
-    cd "${TMP_GIT_DIR}"
+    cd "${TMP_GIT_DIR}" || exit $?
     unset GIT_DIR
     git fetch --all
     git reset --hard origin/master
@@ -48,12 +50,18 @@ else
 fi
 
 for site in *.*/; do
-  [[ ! -d "/var/www/${site}" ]] && mkdir -p "/var/www/${site}" && chgrp -R "/var/www/${site}" && chmod g+s "/var/www/${site}"
+    deploy_dir="/var/www/${site}"
-  pushd "${site}"
+    if [[ ! -d "$deploy_dir" ]]; then
-  bundle install --deployment
+        mkdir -p "$deploy_dir"
-  bundle exec jekyll build --destination "/var/www/${site}"
+        chgrp -R "$deploy_dir"
-  popd
+        chmod g+s "$deploy_dir"
+    fi
+    pushd "${site}" || exit $?
+    ruby -S bundle install --deployment
+    ruby -S bundle exec jekyll build --destination "$deploy_dir"
+    popd || exit $?
 done
 
-exit
+exit 0
+
 ~~~

blog.bryanroessler.com/_posts/2019-02-09-automatic-certbot-namecheap-acme-dns.md

@@ -6,13 +6,13 @@ subtitle: The "less" painful way
 tags: [certbot, acme-dns]
 ---
 
-In early 2018, [Let's Encrypt](https://letsencrypt.org/) began issuing wildcard HTTPS certificates (e.g. for \*.bryanroessler.com), which vastly simplified the process of securing multidomain personal websites for free. The main drawback is that LetsEncrypt requires users to renew their site certificates every three months, which can be a headache if users handle renewals manually. Programs like [certbot-auto](https://certbot.eff.org/docs/install.html) can automate the certificate renewal process but the implementations for wildcard domains have been flaky in the past. An additional complication is that not every DNS provider (like Namecheap) support APIs that allow [ACME challenges](https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html) or may require users to pay an additional fee ($50/mo) for access.
+In early 2018, [Let's Encrypt](https://letsencrypt.org/) began issuing wildcard HTTPS certificates (e.g. for \*.bryanroessler.com), which vastly simplified the process of securing multi-domain personal websites for free. The main drawback is that LetsEncrypt requires users to renew their site certificates every three months, which can be a headache if users handle renewals manually. Programs like [certbot-auto](https://certbot.eff.org/docs/install.html) can automate the certificate renewal process, but the implementations for wildcard domains typically require DNS authentication and API access. Not every DNS provider (including Namecheap) provide an API that supports automating [ACME challenges](https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html) or may require users to pay an additional fee for access.
 
 **Luckily, it is possible for users to run their own DNS authentication server using [acme-dns](https://github.com/joohoi/acme-dns), which completely bypasses DNS provider limitations.**
 
 ### Overview
 
-We will be running a small DNS server called acme-dns to respond to challenges issued by LetsEncrypt's certbot. You can run acme-dns on any computer, but typically it will run on the same host server as your website. Certbot will issue an ACME DNS challenge to your DNS provider, which will then forward the request (via some complicated (not really!) redirects) to your acme-dns server.
+We will be running a small DNS server called acme-dns to respond to challenges issued by LetsEncrypt's certbot. You can run acme-dns on any computer, but typically it will run on the same host server as your website. Certbot will issue an ACME DNS challenge to your DNS provider, which will then forward the request via some redirection to your acme-dns server.
 
 ### Assumptions
 
@@ -27,78 +27,78 @@ I am using Ubuntu 16.04 for this tutorial, but it should not matter which distro
 3. Install acme-dns: `go get github.com/joohoi/acme-dns/…`
 4. Move the binary somewhere sensible since we will be using a systemd service: `sudo cp ~/go/bin/acme-dns /usr/local/bin/acme-dns`
 5. Make the necessary directories: `sudo mkdir /etc/acme-dns/ /var/lib/acme-dns`
-6. Make sure you've removed any existing \_acme-challenge DNS records from your DNS host records
+6. Make sure you've removed any existing _acme-challenge DNS records from your DNS host records
 
 ### acme-dns configuration
+
 1. Create the following file, substituting your site's domain name for <yoursite\> and your server's IP address (yes the naming scheme is dumb, but leave "acme.", "ns1.acme.", etc):
 
-```
+        #/etc/acme-dns/config.cfg
-#/etc/acme-dns/config.cfg
+        [general]
-[general]
+        # DNS interface
-# DNS interface
+        listen = ":53"
-listen = ":53"
+        protocol = "udp"
-protocol = "udp"
+        # domain name to serve the requests off of
-# domain name to serve the requests off of
+        domain = "acme.<yoursite>.com"
-domain = "acme.<yoursite>.com"
+        # zone name server
-# zone name server
+        nsname = "ns1.acme.<yoursite>.com"
-nsname = "ns1.acme.<yoursite>.com"
+        # admin email address, where @ is substituted with .
-# admin email address, where @ is substituted with .
+        nsadmin = "admin.<yoursite>.com"
-nsadmin = "admin.<yoursite>.com"
+        # predefined records served in addition to the TXT
-# predefined records served in addition to the TXT
+        records = [
-records = [
+            "acme.<yoursite>.com. A 176.223.132.72",
-    "acme.<yoursite>.com. A 176.223.132.72",
+            "ns1.acme.<yoursite>.com. A 176.223.132.72",
-    "ns1.acme.<yoursite>.com. A 176.223.132.72",
+            "acme.<yoursite>.com. NS ns1.acme.<yoursite>.com.",
-    "acme.<yoursite>.com. NS ns1.acme.<yoursite>.com.",
+        ]
-]
+        debug = false
-debug = false
 
-[database]
+        [database]
-engine = "sqlite3"
+        engine = "sqlite3"
-connection = "/var/lib/acme-dns/acme-dns.db"
+        connection = "/var/lib/acme-dns/acme-dns.db"
 
-[api]
+        [api]
-api_domain = ""
+        api_domain = ""
-ip = "127.0.0.1"
+        ip = "127.0.0.1"
-disable_registration = false
+        disable_registration = false
-autocert_port = "80"
+        autocert_port = "80"
-port = "8081"
+        port = "8081"
-tls = "none"
+        tls = "none"
-corsorigins = [
+        corsorigins = [
-    "*"
+            "*"
-]
+        ]
-use_header = false
+        use_header = false
-header_name = "X-Forwarded-For"
+        header_name = "X-Forwarded-For"
+
+        [logconfig]
+        loglevel = "debug"
+        logtype = "stdout"
+        logformat = "text"
+
+    A short explanation: you are configuring acme-dns to listen to DNS requests (from certbot via Namecheap) globally on the standard DNS port 53 and configuring the HTTP port for certbot to talk to acme-dns on port 8081 (since you are probably running something way cooler on port 8080).
 
-[logconfig]
-loglevel = "debug"
-logtype = "stdout"
-logformat = "text"
-```
-A short explanation: you are configuring acme-dns to listen to DNS requests (from certbot via Namecheap) globally on the standard DNS port 53 and configuring the HTTP port for certbot to talk to acme-dns on port 8081 (since you are probably running something way cooler on port 8080).
 2. Since certbot has to traverse Namecheap to perform the challenge, we will need to open port 53 in the firewall (traffic on port 8081 is handled on the localhost, so we don't need to open that port): `sudo ufw allow 53/udp && sudo ufw reload`
 
+    **Update 4-10-2021:** Dynamic DNS users, please see [this comment](https://gist.github.com/Nimrodda/af1c35264799fed663088c01b71c9e21#gistcomment-3358700).
 
 3. Let's start the acme-dns program automatically on startup. Create:
 
-```
+        # /etc/systemd/system/acme-dns.service
-# /etc/systemd/system/acme-dns.service
+        [Unit]
-[Unit]
+        Description=Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely
-Description=Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely
+        After=network.target
-After=network.target
 
-[Service]
+        [Service]
-ExecStart=/usr/local/bin/acme-dns
+        ExecStart=/usr/local/bin/acme-dns
-Restart=on-failure
+        Restart=on-failure
 
-[Install]
+        [Install]
-WantedBy=multi-user.target
+        WantedBy=multi-user.target
-```
 
-Note (Ubuntu 17.04+): you can security-harden the above script on distros running newer kernels by executing as a non-privileged user in conjunction with the `AmbientCapabilities=CAP_NET_BIND_SERVICE` line. However, older kernels will cause systemd to choke on that line during service startup. If you choose to execute as a non-root user make sure to chown the `/etc/acme-dns/` and `/var/lib/acme-dns` directories!
+    (Ubuntu 17.04+): you can security-harden the above script on distros running newer kernels by executing as a non-privileged user in conjunction with the `AmbientCapabilities=CAP_NET_BIND_SERVICE` line. However, older kernels will cause systemd to choke on that line during service startup. If you choose to execute as a non-root user make sure to chown the `/etc/acme-dns/` and `/var/lib/acme-dns` directories!
 
- 4. Enable the service to run on startup and run it now: `sudo systemctl daemon-reload && sudo systemctl enable --now acme-dns.service`
+4. Enable the service to run on startup and run it now: `sudo systemctl daemon-reload && sudo systemctl enable --now acme-dns.service`
 
-Great, now you've got a DNS authentication server that can respond to ACME challenges! You just saved yourself $50/month!
+Great, now you've got a DNS authentication server that can respond to ACME challenges!
 
 ### Initial Namecheap configuration
 
@@ -137,41 +137,41 @@ The step I'm sure you've been waiting for.
 
 1. Create the certbot-renew.service (if you are using Apache in lieu of nginx, substitute "nginx" with "httpd"):
 
-```
+        #/etc/systemd/system/certbot-renew.service
-#/etc/systemd/system/certbot-renew.service
+        [Unit]
-[Unit]
+        Description=Certbot Renewal
-Description=Certbot Renewal
+
+        [Service]
+        ExecStart=/usr/bin/certbot renew --post-hook "systemctl restart nginx"
 
-[Service]
-ExecStart=/usr/bin/certbot renew --post-hook "systemctl restart nginx"
-```
 2. Create the associated timer file to run the renewal weekly:
 
-```
+        #/etc/systemd/system/certbot-renew.timer
-#/etc/systemd/system/certbot-renew.timer
+        [Unit]
-[Unit]
+        Description=Timer for Certbot Renewal
-Description=Timer for Certbot Renewal
 
-[Timer]
+        [Timer]
-OnBootSec=300
+        OnBootSec=300
-OnUnitActiveSec=1w
+        OnUnitActiveSec=1w
+
+        [Install]
+        WantedBy=multi-user.target
 
-[Install]
-WantedBy=multi-user.target
-```
 3. Enable the timer: `sudo systemctl enable certbot-renew.timer`
 
 ### What the hell is going on here?
 
 A wild goose chase:
 
-1. LetsEncrypt first asks your <yoursite\>.com domain for the TXT record at \_acme-challenge.example.com to complete the challenge
+1. LetsEncrypt first asks your <yoursite\>.com domain for the TXT record at _acme-challenge.example.com to complete the challenge
-2. The Namecheap DNS server responds with a CNAME record that points to ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite>.com, so LetsEncrypt goes there instead
+2. The Namecheap DNS server responds with a CNAME record that points to ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com, so LetsEncrypt goes there instead
-3. The authoritative DNS server for \*.acme.<yoursite\>.com is ns1.acme.<yoursite\>.com, which points at your server IP (running acme-dns)
+3. The authoritative DNS server for \*.acme.*yoursite*.com is ns1.acme.*yoursite*.com, which points at your server IP (running acme-dns)
-4. LetsEncrypt can finally ask ns1.acme.example.com what is the TXT record for ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite\>.com and acme-dns will answer that question
+4. LetsEncrypt can finally ask ns1.acme.example.com what is the TXT record for ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com and acme-dns will answer that question
 
 ### Additional Considerations
+
 On a critical server it may be a good idea to start and stop acme-dns (and open and close port 53) alongside certbot execution. This can be handled fairly trivially with systemd `Requires=`, but I'll leave that up to you!
 
 ### Conclusions
+
 Congratulations! You have successfully enabled automatic LetsEncrypt site certificate renewal on a finicky DNS host provider!

blog.bryanroessler.com/_posts/2019-05-21-headless-x2go-server-for-remote-gui-applications.md

@@ -39,12 +39,14 @@ We will be using getty to handle autologin for our user. In order to do this, we
 This will open your default system editor to create an override service file for the systemd getty@tty1.service.
 
 2. Enter the following into the drop-in override file you just opened/created and save it (replacing username with your actual username):
-```
+
+```(text)
 [Service]
 Type=simple
 ExecStart=
 ExecStart=-/sbin/agetty --autologin username --noclear %I $TERM
 ```
+
 3. Reload, restart, and enable the service file to load on boot: `sudo systemctl daemon-reload && sudo systemctl restart getty@tty1 && sudo systemctl enable getty@tty1`
 
 Your system will now autologin the user you specified when you reboot!
@@ -54,7 +56,8 @@ Your system will now autologin the user you specified when you reboot!
 In order to run a graphical program or window manager, you will first need to initiate an X server. We can start one automatically using a shell profile file that is sourced during user login. The location of this file (e.g. `/etc/profile.d/`, `~/.profile`, `~/.bash_profile`, `~/.zprofile` (zsh), etc.) depends on your Linux distribution and shell settings. Here I am assuming that you are using bash shell (you can confirm this via the `echo $SHELL` command), thus we will place the relevant commands in `~/.bash_profile`.
 
 1. Add the following to the end of your `~/.bash_profile`:
-```
+
+```(bash)
 # Start X11 automatically
 if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then
         . startx
@@ -65,7 +68,8 @@ fi
 Now that the X server is set to run on login, it needs to be configured to start your window manager, in this case Openbox.
 
 2. Add the following line to `~/.xinitrc` and save the file:
-```
+
+```(bash)
 exec openbox-session
 ```
 
@@ -78,7 +82,8 @@ It's certainly possible to use Openbox to autostart your server's GUI programs b
 Here are the necessary steps to create and activate a systemd service file to start and stop JRiver Media Center.
 
 1. Create the file `/etc/systemd/system/jriver.service` and add the following (replacing username with your username):
-```
+
+```(text)
 [Unit]
 Description=JRiver Media Center 25
 After=graphical.target

blog.bryanroessler.com/_posts/2019-06-12-jriver-client-client-model-with-syncthing.md

@@ -27,6 +27,7 @@ In the course of achieving these goals, my JRMC network has been in a state of f
 JRMC contains a powerful [Media Server](https://wiki.jriver.com/index.php/Media_Server) that enables clients to play and manage media in JRMC as if they were using a local copy of the library. It is certainly possible to use JRMC Media Server exclusively to manage and play your media from the server to your clients in the traditional server-client model.
 
 JRMC Media Server pros:
+
 1. Tag changes are synced seamlessly between all devices
 2. Client devices are easy to add/remove
 
@@ -61,12 +62,12 @@ Although our media files are now in sync, and we have configured JRMC to use loc
 
 The benefits of the client-client model over the server-client model include:
 
-* Automatic redundancy of the media library
+- Automatic redundancy of the media library
-* Each client has access to the media library even when offline
+- Each client has access to the media library even when offline
-* Each client can maintain its own set of views, playlists, and smartlists
+- Each client can maintain its own set of views, playlists, and smartlists
-    * Useful if you want to give read-only access to a client and allow it to store and display its own set of ratings from a custom tag
+  - Useful if you want to give read-only access to a client and allow it to store and display its own set of ratings from a custom tag
-* Low bandwidth and low latency for playback
+- Low bandwidth and low latency for playback
-* Cross-platform since file structure does not have to be identical
+- Cross-platform since file structure does not have to be identical
 
 All that must be done to enable this functionality is to set up Auto-Import on each client to point at your shared (via Syncthing) media folder!
 
@@ -74,7 +75,7 @@ All that must be done to enable this functionality is to set up Auto-Import on e
 
 The real magic here is to store as much information as possible in the file tags so that they are synced via Syncthing between JRMC clients. This can include basic information like ratings, artwork, audio analysis data (R128 normalization) or more advanced information like user-defined fields that can be used to keep smartlists in sync (see [Advanced tagging](#advanced-tagging) below for more information).
 
-##### Sending metadata
+#### Sending metadata
 
 To propagate changes from a client to other clients, we will need to enable *Edit>Edit File Tags When File Info Changes* on any JRMC client that we want to have read-write access to the file metadata. If you leave this option unchecked on a client then that client will maintain its own set of metadata in the JRMC database without propagating changes. If you want to edit the actual file tags without affecting other clients (e.g. you are moving files on the client to a handheld device), then go ahead and enable the option but set your Syncthing client to Receive Only so that it maintains its own local database state. I also recommend enabling automatic file tagging during file analysis upon Auto-Import *Options>Library & Folders>Configure auto-import>Tasks>Write file tags when analyzing audio...* so that analysis only needs to be performed once on the client that performs the initial file import.
 
@@ -88,7 +89,7 @@ In order to receive metadata updates from other clients, you'll want to use JRMC
 
 Below I will describe two examples of expanding the functionality of the client-client model using file tags.
 
-##### Tracking newly added media
+#### Tracking newly added media
 
 Sometimes it is useful to keep track of which client has added a particular file to the Syncthing network. You can do this by creating a custom user-defined string field in JRMC (*Options>Library & Folders>Manage Library Fields*) named *Imported From* and check the box to *Save in file tags (when possible)*. Then configure each client to apply their specific client name to the field upon auto-import: In *Options>Library & Folders>Configure auto-import* select your auto-import directory that you are sharing with Syncthing, click *Edit...* and under *Apply these tags (optional)>Add>Custom* select the field you just created and enter the client name as the value. For instance I have named my clients *HTPC*, *Laptop*, *VPS*, and *Work*. In this manner you can track where your files were originally imported from.
 

blog.bryanroessler.com/_posts/2020-01-23-run-with-podman.md

@@ -6,24 +6,28 @@ subtitle: Now with systemd!
 tags: [atom, podman, containers, ide, systemd, run-with-podman]
 ---
 
-### Overview
+## Note
+
+**The scripts provided in this tutorial have been superseded by the simpler [podmanRun]({% post_url 2020-05-15-podmanrun-a-simple-podman-wrapper %}) wrapper.**
+
+## Overview
 
 In this tutorial we will be using Atom's [build package](https://atom.io/packages/build) (although you are free to use your own IDE) and a container management script to run files/commands on default system images using podman. We will go one step further by enabling systemd support in our build environment. We will also provide the option of masking the program's output from the host using unnamed volumes.
 
-### Introduction
+## Introduction
 
 It is important to remember that a development environment can be just as important as the code itself. Over time, our development environment morphs into a unique beast that are specific to each user. Therefore, it is imperative to test your programs in several default environments prior to distribution.
 
 In the past, this was performed on virtual machines (VMs) that contained a default installation of the distribution that you were targeting. Thanks to their snapshotting abilities it was fairly trivial to restore distributions to their default state for software testing. However, this method had its drawbacks:
 
-*   The default state was never the *current* default state for long. VMs had to be continually upgraded via their package managers to stay up-to-date with the development environment. They also needed to be modified in some cases (e.g. to enable sshd and allow authentication-less sudo) so deploying newer image versions required manual intervention
+* The default state was never the *current* default state for long. VMs had to be continually upgraded via their package managers to stay up-to-date with the development environment. They also needed to be modified in some cases (e.g. to enable sshd and allow authentication-less sudo) so deploying newer image versions required manual intervention
-*   Retroactive changes to existing VMs is difficult
+* Retroactive changes to existing VMs is difficult
-*   VMs are difficult to automate, requiring third-party tools (e.g. kickstart files, Ansible, etc.) to manage them
+* VMs are difficult to automate, requiring third-party tools (e.g. kickstart files, Ansible, etc.) to manage them
-*   Each VM gets its own IP address, which makes it difficult to automate ssh-based program building/script running
+* Each VM gets its own IP address, which makes it difficult to automate ssh-based program building/script running
-*   VMs are computationally heavy. Their footprint is an entire deduplication of the host OS and its virtualization stack, in both memory and disk space. Taking and restoring snapshots is slow.
+* VMs are computationally heavy. Their footprint is an entire deduplication of the host OS and its virtualization stack, in both memory and disk space. Taking and restoring snapshots is slow.
-*   There is a meaningful amount of performance loss between the hypervisor and disk i/o because it is handled using network protocols. For example, an Atom VM build command would normally look something like this:
+* There is a meaningful amount of performance loss between the hypervisor and disk i/o because it is handled using network protocols. For example, an Atom VM build command would normally look something like this:
 
-```
+```bash
 cat {FILE_ACTIVE} | ssh fedora-build-machine.lan "cat > /tmp/{FILE_ACTIVE_NAME} ; mkdir -p {FILE_ACTIVE_NAME_BASE}; cd {FILE_ACTIVE_NAME_BASE}; chmod 755 /tmp/{FILE_ACTIVE_NAME} ; /tmp/{FILE_ACTIVE_NAME}"
 ```
 
@@ -35,27 +39,27 @@ Containers alleviate all of the problems associated with using VMs to execute co
 
 They:
 
-*   Use standardized images of your target distributions and make it possible to execute commands directly on them
+* Use standardized images of your target distributions and make it possible to execute commands directly on them
-*   Allow you to create your own custom base images using Dockerfiles, which are built on top of other rolling images that are automatically maintained
+* Allow you to create your own custom base images using Dockerfiles, which are built on top of other rolling images that are automatically maintained
-*   Support several different networking options, such as automatically using the host network or operating via its own whitelisted service
+* Support several different networking options, such as automatically using the host network or operating via its own whitelisted service
-*   Perform great because the code is running on the same kernel as the OS
+* Perform great because the code is running on the same kernel as the OS
-*   Can be created and destroyed nearly instantaneously which makes them much better for executing frequent build commands (I'm a big F5'er)
+* Can be created and destroyed nearly instantaneously which makes them much better for executing frequent build commands (I'm a big F5'er)
 
 ### Podman and Toolbox
 
 Podman is a container manager by Red Hat that is available on Fedora and CentOS and integral to Silverblue and CoreOS. Red Hat has also shipped some fun stuff built on top of Podman such as [Toolbox](https://fedoramagazine.org/a-quick-introduction-to-toolbox-on-fedora/) that combine system overlays and containers to provide seamless build environments for past and current CentOS and Fedora releases (theoretically you should be able to provide your own custom image although the documentation is currently scant). Toolbox will get you 90% of the way there to automated builds as long as you:
 
-*   only target Red Hat-based distributions
+* only target Red Hat-based distributions
-*   don't develop or test systemd scripts or need to utilize existing systemd services (**systemd does not work in Toolbox**)
+* don't develop or test systemd scripts or need to utilize existing systemd services (**systemd does not work in Toolbox**)
-*   are comfortable with having your entire $HOME exposed to your build environment
+* are comfortable with having your entire $HOME exposed to your build environment
-*   don't need to nest toolboxes
+* don't need to nest toolboxes
 
 Toolbox may make sense if you run separate instances of your IDE from *inside* the toolbox containers, but then you are just back to creating custom build environments within each container, only now separated from the host OS. Unfortunately, Toolbox does not support nesting containers so testing your code on default images from within a toolbox is impossible as of this moment. Additionally, if your scripts change environmental variables, they may be difficult to test as the toolbox is mutable.
 
-
 ### Prerequisites
 
-1.  You have a script or command to execute on build. Let's start with something easy like:
+1. You have a script or command to execute on build. Let's start with something easy like:
+
 ```bash
 #!/usr/bin/env bash
 # ./hello-pwd-ls.sh
@@ -64,26 +68,25 @@ pwd
 ls -al
 exit $?
 ```
-2.  You have [Atom](https://atom.io/) and the [build](https://atom.io/packages/build) package installed
-*   I won't pontificate on why I am using Atom and the build package as my example IDE. The podman commands I will highlight in this post will work equally as well using whichever IDE you choose to use in conjunction with its external build commands.
-3.  You are somewhat familiar with .atom-build.yml (or can copypasta)
-4.  You have podman installed
 
+2. You have [Atom](https://atom.io/) and the [build](https://atom.io/packages/build) package installed (the podman commands I will highlight in this post will work equally as well using whichever IDE you choose to use in conjunction with its external build commands.)
+3. You are somewhat familiar with .atom-build.yml (or can copypasta)
+4. You have podman installed
 
 ### Configuration
 
-
 #### run-with-podman.sh
 
 I created the following script to handle container execution depending on a few arguments. You can download it and place it in your path here:
 
-
 Download [run-with-podman.sh](https://git.bryanroessler.com/bryan/run-with-podman/src/master/run-with-podman.sh) and install to `$HOME/.local/bin`:
-```
+
+```bash
 wget -q -O "${HOME}/.local/bin/run-with-podman" "https://git.bryanroessler.com/bryan/run-with-podman/src/master/run-with-podman.sh"
 ```
 
 If you prefer to copy-paste:
+
 ```bash
 #!/usr/bin/env bash
 
@@ -282,14 +285,13 @@ fi
 
 There are several things to highlight in this script:
 
-1.  The filename is first sanitized so that it can be used to generate a unique container name.
+1. The filename is first sanitized so that it can be used to generate a unique container name.
-2.  Next, we edit SELinux permissions on our `pwd` to allow the container full access to our build directory. Editing SELinux permissions is always a balance between ease-of-use and security and I find setting the container_file_t flag is a nice balance. If your script doesn't do much file i/o it may be possible to run it by only altering permissions on `$FILE_ACTIVE`.
+2. Next, we edit SELinux permissions on our `pwd` to allow the container full access to our build directory. Editing SELinux permissions is always a balance between ease-of-use and security and I find setting the container_file_t flag is a nice balance. If your script doesn't do much file i/o it may be possible to run it by only altering permissions on `$FILE_ACTIVE`.
-3.  According to the mode we either remove and recreate or create a new container
+3. According to the mode we either remove and recreate or create a new container
-4.  We mount the `pwd` in the container
+4. We mount the `pwd` in the container
-5.  If `OUTPUT=0, `we mask the output directory `-v "{FILE_ACTIVE_PATH}/${OUTPUT_DIR}"` by mounting an unnamed volume, so that output is only stored in the container and not on the host filesystem. You can repeat this as many times as necessary to exclude other subdirectories in your build directory.
+5. If `OUTPUT=0`, we mask the output directory `-v "{FILE_ACTIVE_PATH}/${OUTPUT_DIR}"` by mounting an unnamed volume, so that output is only stored in the container and not on the host filesystem. You can repeat this as many times as necessary to exclude other subdirectories in your build directory.
-6.  Enable `--systemd=always` if you plan on interacting with `systemctl` using your script. The default `on` state will only enable systemd when the command passed to the container is `/usr/sbin/init`. Since it is not possible to pass more than one command and we must pass our script, this should be set to `always`.
+6. Enable `--systemd=always` if you plan on interacting with `systemctl` using your script. The default `on` state will only enable systemd when the command passed to the container is `/usr/sbin/init`. Since it is not possible to pass more than one command and we must pass our script, this should be set to `always`.
-7.  Make sure to make the script executable in the container using `chmod 755`
+7. Make sure to make the script executable in the container using `chmod 755`
-
 
 ##### `--file` and `--file-path`
 
@@ -299,16 +301,16 @@ This can be a script running a list of commands (e.g. build script) or a single
 
 ##### `--mode`
 
-0.  Nonpersistent container (always recreate) (Default)
+0. Nonpersistent container (always recreate) (Default)
-1.  Persistent container
+1. Persistent container
-2.  Recreate persistent container
+2. Recreate persistent container
 
 ##### `--mask-dir`
 
 Optionally, one can mask output from the host system (so that it only resides in a container volume) using `--mask-dir`.  As demonstrated in the [prerequisites](#prerequisites), it is important to have your program output to the `--` specified in your `.atom-build.yml` (in this case 'output'). This provides you the ability to optionally mask the output directory with an unnamed volume so that no files are actually written to the host. This has two benefits:
 
-*   If the script is configured to overwrite existing output, it may threaten a live system (like a website or any other running process that depends on the script output)
+* If the script is configured to overwrite existing output, it may threaten a live system (like a website or any other running process that depends on the script output)
-*   If the script is configured to not overwrite existing output, the script may not run correctly
+* If the script is configured to not overwrite existing output, the script may not run correctly
 
 Output masking gives you the power to control these variables independently of one another by writing output to the container only.
 
@@ -322,7 +324,6 @@ If you are going to release software that integrates with systemd, it is certain
 
 The container image to be used to execute the command.
 
-
 #### .atom-build.yml
 
 In your project directory (next to your script), create the following `.atom-build.yml` file in order to call our script using the appropriate arguments whenever a build is triggered.

blog.bryanroessler.com/_posts/2020-02-26-flake-it-till-you-make-it.md

@@ -0,0 +1,18 @@
+---
+layout: post
+title: Flake it till you make it
+subtitle: Excerpt from Soulshaping by Jeff Brown
+cover-img: /assets/img/path.jpg
+thumbnail-img: /assets/img/thumb.png
+share-img: /assets/img/path.jpg
+tags: [books, test]
+author: Sharon Smith and Barry Simpson
+---
+
+Under what circumstances should we step off a path? When is it essential that we finish what we start? If I bought a bag of peanuts and had an allergic reaction, no one would fault me if I threw it out. If I ended a relationship with a woman who hit me, no one would say that I had a commitment problem. But if I walk away from a seemingly secure route because my soul has other ideas, I am a flake?
+
+The truth is that no one else can definitively know the path we are here to walk. It’s tempting to listen—many of us long for the omnipotent other—but unless they are genuine psychic intuitives, they can’t know. All others can know is their own truth, and if they’ve actually done the work to excavate it, they will have the good sense to know that they cannot genuinely know anyone else’s. Only soul knows the path it is here to walk. Since you are the only one living in your temple, only you can know its scriptures and interpretive structure.
+
+At the heart of the struggle are two very different ideas of success—survival-driven and soul-driven. For survivalists, success is security, pragmatism, power over others. Success is the absence of material suffering, the nourishing of the soul be damned. It is an odd and ironic thing that most of the material power in our world often resides in the hands of younger souls. Still working in the egoic and material realms, they love the sensations of power and focus most of their energy on accumulation. Older souls tend not to be as materially driven. They have already played the worldly game in previous lives and they search for more subtle shades of meaning in this one—authentication rather than accumulation. They are often ignored by the culture at large, although they really are the truest warriors.
+
+A soulful notion of success rests on the actualization of our innate image. Success is simply the completion of a soul step, however unsightly it may be. We have finished what we started when the lesson is learned. What a fear-based culture calls a wonderful opportunity may be fruitless and misguided for the soul. Staying in a passionless relationship may satisfy our need for comfort, but it may stifle the soul. Becoming a famous lawyer is only worthwhile if the soul demands it. It is an essential failure if you are called to be a monastic this time around. If you need to explore and abandon ten careers in order to stretch your soul toward its innate image, then so be it. Flake it till you make it.

blog.bryanroessler.com/_posts/2020-02-28-sample-markdown.md

@@ -0,0 +1,95 @@
+---
+layout: post
+title: Sample blog post to learn markdown tips
+subtitle: There's lots to learn!
+gh-repo: daattali/beautiful-jekyll
+gh-badge: [star, fork, follow]
+tags: [test]
+comments: true
+mathjax: true
+author: Bill Smith
+---
+
+{: .box-success}
+This is a demo post to show you how to write blog posts with markdown.  I strongly encourage you to [take 5 minutes to learn how to write in markdown](https://markdowntutorial.com/) - it'll teach you how to transform regular text into bold/italics/tables/etc.<br/>I also encourage you to look at the [code that created this post](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/_posts/2020-02-28-sample-markdown.md) to learn some more advanced tips about using markdown in Beautiful Jekyll.
+
+**Here is some bold text**
+
+## Here is a secondary heading
+
+[This is a link to a different site](https://deanattali.com/) and [this is a link to a section inside this page](#local-urls).
+
+Here's a table:
+
+| Number | Next number | Previous number |
+| :------ |:--- | :--- |
+| Five | Six | Four |
+| Ten | Eleven | Nine |
+| Seven | Eight | Six |
+| Two | Three | One |
+
+You can use [MathJax](https://www.mathjax.org/) to write LaTeX expressions. For example:
+When \\(a \ne 0\\), there are two solutions to \\(ax^2 + bx + c = 0\\) and they are $$x = {-b \pm \sqrt{b^2-4ac} \over 2a}.$$
+
+How about a yummy crepe?
+
+![Crepe](https://beautifuljekyll.com/assets/img/crepe.jpg)
+
+It can also be centered!
+
+![Crepe](https://beautifuljekyll.com/assets/img/crepe.jpg){: .mx-auto.d-block :}
+
+Here's a code chunk:
+
+~~~
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+~~~
+
+And here is the same code with syntax highlighting:
+
+```javascript
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+```
+
+And here is the same code yet again but with line numbers:
+
+{% highlight javascript linenos %}
+var foo = function(x) {
+  return(x + 5);
+}
+foo(3)
+{% endhighlight %}
+
+## Boxes
+You can add notification, warning and error boxes like this:
+
+### Notification
+
+{: .box-note}
+**Note:** This is a notification box.
+
+### Warning
+
+{: .box-warning}
+**Warning:** This is a warning box.
+
+### Error
+
+{: .box-error}
+**Error:** This is an error box.
+
+## Local URLs in project sites {#local-urls}
+
+When hosting a *project site* on GitHub Pages (for example, `https://USERNAME.github.io/MyProject`), URLs that begin with `/` and refer to local files may not work correctly due to how the root URL (`/`) is interpreted by GitHub Pages. You can read more about it [in the FAQ](https://beautifuljekyll.com/faq/#links-in-project-page). To demonstrate the issue, the following local image will be broken **if your site is a project site:**
+
+![Crepe](/assets/img/crepe.jpg)
+
+If the above image is broken, then you'll need to follow the instructions [in the FAQ](https://beautifuljekyll.com/faq/#links-in-project-page). Here is proof that it can be fixed:
+
+![Crepe]({{ '/assets/img/crepe.jpg' | relative_url }})

blog.bryanroessler.com/_posts/2020-03-18-insert-code-blocks-from-repository.md

@@ -0,0 +1,55 @@
+---
+layout: post
+title: Implementing dynamic code blocks in jekyll using liquid tags
+subtitle: Keep your tutorials in sync with upstream code
+#bigimg: /img/path.jpg
+tags: [jekyll, ruby, liquid, tags, git]
+---
+
+### Overview
+
+Blogs are a great way to share code with users searching for solutions to similar problems. However, most code is ever-evolving, and as any programmer will tell you, "code is only finished when it is abandoned." Writing static journal entries containing copy-and-pasted code blocks will lead to divergence from your code repositories as you continue to improve your software.
+
+**Wouldn't it be great if your blog's code blocks could dynamically track the code residing in your version control repository?**
+
+### Github, Gogs, and GitLab
+
+If you are using Github to host your code, there are likely plenty of existing third-party solutions for updating your code blocks in your blogging platform. If you find that the existing solutions do not work then you can also use a similar solution to the one I provide here using [ruby](https://www.ruby-lang.org/en/) and [jekyll](https://jekyllrb.com/). I prefer self-hosting my code using lightweight [gogs](https://gogs.io/) while others prefer [Gitlab](https://about.gitlab.com/) or the myriad other repository solutions that may not have existing third-party solutions for dynamic code blocks.
+
+### Jekyll and other blogging platforms
+
+In this example I will be using jekyll, a lightweight blogging platform built on ruby. Generally, ruby is an easy web language to write and understand with some deficiencies in documentation and debugging, which is why I would like to provide more ready-made solutions to common problems. I generally prefer [python](https://www.python.org/) for most projects but the existing functionality provided by ruby out-of-the-box for web development still outpaces [django](https://www.djangoproject.com/). If you are using a different platform and/or framework then you may be able to adapt my admittedly simple ruby solution to whichever language you require.
+
+### `insert_git_here` ruby plugin
+
+If you are using jekyll to build the site you wish to contain dynamic code blocks, ruby plugins will be read in automatically from the `_plugins` directory located in the root of your build.
+
+**Note:** The `github-pages` gem disallows loading ruby plugins from the `_plugins` directory by default. In this case, you will need to set set the env `DISABLE_WHITELIST=true` or remove `github-pages` and replace it with the vanilla `jekyll` gem in your Gemfile.
+
+In `_plugins`, create the following file:
+
+[insert_git_code.rb](https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb)
+
+{% highlight ruby %}
+{% insert_git_code https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb %}
+{% endhighlight %}
+
+This is a fairly simple Liquid tags plugin that just returns the text in a raw text file from a url.
+
+### Using your tag
+
+In your markdown post or page, include something similar to the following (which is the code verbatim I used to display the dynamic code block shown above):
+
+{% highlight markdown %}
+{{ "{% highlight ruby " }}%}
+{{ "{% insert_git_code https://git.bryanroessler.com/bryan/www/raw/master/blog.bryanroessler.com/_plugins/insert_git_code.rb " }}%}
+{{ "{% endhighlight " }}%}
+{% endhighlight %}
+
+I'm actually using the plugin to display the `insert_git_code.rb` code block above, so if you can see it you can be guaranteed that the plugin is functional.
+
+You can always change the highlighting implementation to match your dynamic code block. The next steps are to add line number slicing for code snippet support, display a link to download the script automatically, error checking, and improving code format detection. By the time that you read this maybe some of these features will have already been implemented in the `insert_git_code` dynamic code block above! Just remember that you will need to restart jekyll in order to load your new plugin (still not fixed upstream) and regenerate your site to pull your updated code.
+
+### Conclusions
+
+In this tutorial we implemented a dynamic code block using a ruby plugin and liquid tags within the jekyll web framework. This strategy can be adapted to other web frameworks in order to keep instructional blog posts in sync with upstream code.

blog.bryanroessler.com/_posts/2020-04-01-prune.md

@@ -0,0 +1,46 @@
+---
+layout: post
+title: prunefiles
+subtitle: An easy way to keep your repositories clean
+tags:
+  - prune
+  - git
+  - repositories
+  - fedora
+---
+
+## Overview
+
+Here's a simple script/function to keep *n* number of the latest files that match your argument(s) in the current directory. I wrote this in order to periodically clean rpm and deb repositories. It will create file lists by matching one or more input arguments and keep only the latest file from each list. The number of files to be kept for each matching list can be set using `-k`. The file can safely be sourced as a function.
+
+### Code
+
+[prunefiles](https://git.bryanroessler.com/bryan/scripts/raw/master/prunefiles):
+
+~~~bash
+{% insert_git_code https://git.bryanroessler.com/bryan/scripts/raw/master/prunefiles %}
+~~~
+
+### Example
+
+~~~bash
+$ ls
+Package-25-1.rpm
+Package-25-2.rpm
+Package-25-3.rpm
+Package-25-4.rpm
+Package-26-1.rpm
+Package-26-2.rpm
+Package-27-1.rpm
+Package-27-2.rpm
+$ prunefiles Package-25 Package-27
+$ ls
+Package-25-4.rpm
+Package-26-1.rpm
+Package-26-2.rpm
+Package-27-2.rpm
+~~~
+
+### Conclusion
+
+I have provided a `prunefiles` script/function that keeps *n* number of latest files in the current directory that match any number of input argument(s).

blog.bryanroessler.com/_posts/2020-05-15-podmanrun-a-simple-podman-wrapper.md

@@ -0,0 +1,93 @@
+---
+layout: post
+title: 'podmanRun'
+date: '2020-05-15 15:36'
+subtitle: A simple podman run wrapper
+tags:
+  - podman
+  - bash
+  - fedora
+  - containers
+---
+
+### Rationale
+
+[In a previous post]({% post_url 2020-01-23-run-with-podman %}) I demonstrated the benefits of running and developing code in containers in order to maintain a clean and predictable development environment. After using [run-with-podman](https://git.bryanroessler.com/bryan/run-with-podman) for several months I often ran into edge cases requiring additional argument handling. In light of this, I have simplified run-with-podman into `podmanRun`, a [podman](https://podman.io/) cli wrapper that can pass arguments directly to podman while maintaining the container management benefits of run-with-podman.
+
+### Who is `podmanRun` intended for?
+
+Anyone that wants to easily run programs in ephemeral or persistent containers. Personally, I use `podmanRun` in order to quickly test code in different Linux distributions, automate compilation, and deploy containerized build services including preprocessors and web servers.
+
+### What does `podmanRun` actually do?
+
+Not much, by design.
+
+1. Generates a unique container name based on the `--name` argument passed to `podman` within the `podmanRun` `--options` string. If no `--name` is specified in the `--options` string, podmanRun will generate a unique container name based on the concatenated options and commands passed by the user. Thus, if any options or commands are changed, a new container will be recreated regardless if `--mode=persistent` was set.
+2. Checks whether a container with that name already exists.
+3. If no matching container was found: the `--options` are passed directly to `podman run` and the commands are executed in the new container.
+4. If a matching container was found:
+
+- `--mode=recreate` will remove the existing container and run the commands in a new container using `podman run` with the provided `--options`.
+- `--mode=persistent` will run the commands in the existing container using `podman exec` and `--options` will be ignored.
+
+5. By default, the container is not removed afterwards (it will only be removed upon subsequent invocations of `podmanRun` using `--mode=recreate`) to allow the user to inspect the container. Containers can be automatically removed after execution by uncommenting the requisite line in `__main()`.
+
+### Usage
+
+For the complete list of up-to-date options, run `podmanRun --help`.
+
+```bash
+podmanRun [-m MODE] [-o OPTIONS] [COMMANDS [ARGS]...] [--help] [--debug]
+```
+
+#### Options
+
+```text
+--mode, -m MODE
+    1. recreate (default) (remove container if it already exists and create a new one)
+    2. persistent (reuse existing container if it exists)
+--options, -o OPTIONS
+    OPTIONS to pass to podman run/exec
+--debug, -d
+    Print debugging
+--help, -h
+    Print this help message and exit
+```
+
+`podmanRun` supports two modes: `recreate` and `persistent`. Recreate will always overwrite an existing container with the same name, while persistent will try to execute commands in an existing container (if found) using `podman exec`.
+
+Podman options can be passed to `--options` as a single string to be split on whitespace or passed multiple times discretely.
+
+##### Examples
+
+Run an ephemeral PHP webserver container using the current directory as webroot:
+
+```shell
+podmanRun -o "-p=8000:80 --name=php_script -v=$PWD:/var/www/html:z php:7.3-apache"
+```
+
+Run an ephemeral PHP webserver container using the current directory as webroot using IDE:
+
+```shell
+podmanRun -o "-p=8000:80 --name=php_{FILE_ACTIVE_NAME_BASE} -v={FILE_ACTIVE_PATH}:/var/www/html:z php:7.3-apache"
+```
+
+Run an ephemeral bash script:
+
+```sehll
+podmanRun -o "--name=bash_script -v=$PWD:$PWD:z -w=$PWD debian:testing" ./script.sh
+```
+
+Run an ephemeral bash script using IDE:
+
+```sehll
+podmanRun -o "--name=bash_{FILE_ACTIVE_NAME_BASE}" \
+          -o "-v={FILE_ACTIVE_PATH}:{FILE_ACTIVE_PATH}:z" \
+          -o "-w={FILE_ACTIVE_PATH}" \
+          -o "debian:testing" \
+          {FILE_ACTIVE} arg1 arg2
+```
+
+## Additional Info
+
+Did you find `podmanRun` useful? [Buy me a coffee!](https://paypal.me/bryanroessler?locale.x=en_US)

blog.bryanroessler.com/_posts/2020-12-14-btrfs-on-wsl2.md

@@ -0,0 +1,111 @@
+---
+layout: post
+title: 'BTRFS on WSL2'
+date: '2020-12-14 15:36'
+subtitle: It works
+tags:
+  - BTRFS
+  - wsl2
+  - windows
+  - fedora
+---
+
+
+### Introduction
+
+Recently I needed to move 20TB worth of data stored on my last remaining Windows HTPC server over to a BTRFS-powered NAS running a *BTRFSized* Fedora 33. However, I was quite limited by the wi-fi speeds of the embedded server running the data array and benchmarks indicated it would take several days to complete. Instead of moving displays around, I figured I would see if it was possible to connect the BTRFS drive array directly to the Windows server using WSL2. Of course, such a situation would've been unthinkable a year ago, but now thanks to the ability to use a full Linux kernel in WSL2, the process is relatively simple as long as you are willing to upgrade to a bleeding edge Windows 10 developer edition to enable the ability to mount block devices in WSL2.
+
+### WSL2
+
+In version 2 of the Windows Subsystem for Linux (WSL2), Microsoft started shipping a full linux kernel on top of its virtualization stack. Since BTRFS is baked into recent Linux kernels, suddenly these "Linux-only" filesystems could now be used on Windows via the WSL2. Unfortunately it was still impossible to interact with hardware block devices (and thus mount multi-drive BTRFS device arrays) until Windows 10 [Build 20211](https://docs.microsoft.com/en-us/windows/wsl/release-notes), which is still a preview build. This means you will need to enable some Microsoft telemetry, join their Insider Program (their unpaid beta testing team), and upgrade to the latest developer build to enable the `wsl --mount` feature. Since this will be the *coup d'état* for this server, I don't worry much about the long-term privacy concerns or stability risks. If this is not the case for you, **it may be a good idea to wait** until all of these awesome features trickle down to more stable builds.
+
+1. Upgrade to a Windows Build >= 20211 by joining the Insider Program from the Windows settings (entails several reboots)
+
+Additional steps I had to perform in Windows:
+
+1. Enable WSL2 VM support: `dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart`
+2. Set my default WSL to version 2: `wsl --set-default-version 2`
+3. If you have an existing WSL installation, you will need to convert it from WSL1 to WSL2: `wsl --set-version Ubuntu 2`
+
+### The array
+
+The BTRFS array consists of 5 disks in a **RAID1c3** configuration that was created on a Fedora 33 server. So-called "3-Copy" support was added to **Linux 5.5** and adds some additional redundancy. Unfortunately, the WSL2 currently ships with a Linux 4.9 by default. It's possible to upgrade the kernel to some extent using [a package from Microsoft](https://docs.microsoft.com/en-us/windows/wsl/install-win10#step-4---download-the-linux-kernel-update-package), but I was still stuck on 5.4 even after installing the update package.
+
+It's certainly possible to build your own Linux kernel from Microsoft's [Linux 5.4 source repository](https://github.com/microsoft/WSL2-Linux-Kernel/tree/linux-msft-wsl-5.4.y) if you wanted to go that route. In my case the BTRFS version in the kernel would still not be able to read my RAID1c3 array.
+
+Luckily, [Nathan Chance](https://github.com/nathanchance/WSL2-Linux-Kernel) has a public repository available of WSL2-compatible Linux kernels tracking upstream. You can build it using his toolchain or use one of his latest pre-compiled [releases](https://github.com/nathanchance/WSL2-Linux-Kernel/releases). As I mentioned earlier, I'm not too concerned with performance or security here so I'm willing to use a third-party solution to save time as this is a one-shot operation. Thanks, Nathan.
+
+After downloading the bzImage you will need to point WSL2 at the new kernel by placing a file at `C:\Users\username\.wslconfig` containing:
+
+```(text)
+[wsl2]
+kernel = C:\\Users\\username\\Downloads\\bzImage
+```
+
+Yes, those are **double slashes**, because Windows.
+
+Now you can restart your wsl instance (`wsl --shutdown`) or just reboot and you should be running a sparkling fresh kernel (confirm with `uname -a`). At the time of this writing, Linux 5.10 kernels were already available.
+
+### Passthrough the BTRFS device (or partition) to WSL2
+
+Now that our tools are up-to-date we can go ahead and mount (passthrough) our block devices and BTRFS partitions. In Windows you will need to identify the **DeviceID** of the disk(s) you wish to passthrough to WSL2 using `wmic diskdrive list brief` in an elevated prompt. In Windows fashion the nomenclature is nonsensical (probably, `\\.\PHYSICALDRIVE2`).
+
+In my case I had to passthrough all five drives in the array. WSL2 does have the ability to mount btrfs partitions directly using the `-t` option, but we will just be passing the bare drives as block devices instead:
+
+```(powershell)
+wsl --mount \\.\PHYSICALDRIVE5 --bare
+wsl --mount \\.\PHYSICALDRIVE6 --bare
+wsl --mount \\.\PHYSICALDRIVE7 --bare
+wsl --mount \\.\PHYSICALDRIVE8 --bare
+wsl --mount \\.\PHYSICALDRIVE9 --bare
+```
+
+These will all become block devices in `/dev/sd*`.
+
+### Mount the BTRFS filesystem and transfer your data
+
+After adding your drives to the WSL2, for good measure run a `sudo btrfs device scan` to make the kernel aware of their existence.
+
+Check for device blocks:
+
+```(shell)
+$ sudo blkid
+/dev/sda: UUID="3255683f-53a2-4fdf-91cf-b4c1041e2a62" TYPE="ext4"
+/dev/sdb: UUID="3255683f-53a2-4fdf-91cf-b4c1041e2a62" TYPE="ext4"
+/dev/sdc: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="bdfea478-7826-48ed-b000-04894aac221d" TYPE="btrfs"
+/dev/sdd: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="95615881-0962-4318-b04d-6aa21d991a33" TYPE="btrfs"
+/dev/sde: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="abc9baa8-4b76-4630-a1d5-e91852dca20c" TYPE="btrfs"
+/dev/sdf: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="e06ddecc-57cd-4458-a4a7-22689f940b02" TYPE="btrfs"
+/dev/sdg: LABEL="array" UUID="6f7065bf-3f6c-4950-b305-e5d3565b9385" UUID_SUB="08f00c39-b1bc-4b01-9f1d-e1efb8686fd4" TYPE="btrfs"
+```
+
+BTRFS is smart enough to mount the whole device array even when specifying a single disk member. So just create a sensible mount point and mount any of your btrfs devices: `sudo mkdir /mnt/array && sudo mount /dev/sdc /mnt/array`.
+
+`cd /mnt/array` into your mounted BTRFS array to make sure everything looks good and your subvolumes are present: `sudo btrfs subvolume list /`
+
+If everything looks good, go ahead and start transferring your data over from your Windows partitions, which are also conveniently mounted in `/mnt` (as you have probably spotted by now if you've been following along).
+
+By default the Windows filesystems are `a+rwx` so it is pretty easy to pull data from them with rsync without too many permission hassles using the `-a` archive option: `rsync -a --info=progress2 /mnt/d/media/ /mnt/e/media/ /mnt/array/media`
+
+As you can see in the above rsync command, I chose to chain several source directories together to simplify the transfer to the new array.
+
+### Cleanup
+
+After you are finished moving data around:
+
+1. Unmount the array in WSL: `sudo umount /dev/array` **Note:** Make sure you aren't currently in the mount point or you will get `target is busy` errors when trying to unmount. `cd ~` first.
+2. Back in Windows, unshare the drive with the WSL2:
+
+```(powershell)
+wsl --unmount \\.\PHYSICALDRIVE5
+wsl --unmount \\.\PHYSICALDRIVE6
+wsl --unmount \\.\PHYSICALDRIVE7
+wsl --unmount \\.\PHYSICALDRIVE8
+wsl --unmount \\.\PHYSICALDRIVE9
+```
+
+And voilà, you are done!
+
+### Conclusions
+
+Even though my aging Windows server was limited to 5 GB/s USB throughput, I was still able to complete the transfer in a matter of hours (not days) and without putting tremendous load on my network for an extended period of time. It is also perhaps bittersweet that I exit the ecosystem just as it achieves some useful level of compatibility with my preferred workflow. In theory one could even share BTRFS devices between Windows and Linux as long as they were not simultaneously mounted. Of course, in most cases it would be more sensible to use a network-based solution but for those seeking optimal performance, the WSL2 offers a compelling option.

blog.bryanroessler.com/_posts/2021-02-18-external-wsl2-access-ubuntu-20-w-powershell.md

@@ -0,0 +1,52 @@
+---
+layout: post
+title: 'Restoring external (remote) WSL2 access'
+date: 2021-02-18 11:01
+tags: [windows, wsl, wsl2, linux, ssh, firewall, ip, ifconfig, powershell]
+---
+
+## Cannot access WSL2 instances remotely
+
+If you rely on external (remote) access to the Windows Subsystem for Linux (WSL2) you may have noticed that your manual port forwards have suddenly stopped working. Microsoft has started issuing WSL2 instances a randomized IP address on startup, which makes it difficult to reliably access services hosted in the Linux subsystem. However, it's still possible to probe the WSL2 instance on startup and open the appropriate ports using Powershell.
+
+Most existing solutions rely on legacy `ifconfig`, which has been deprecated in Ubuntu 20.04 (available in WSL2 via an in-place `do-release-upgrade`) in favor of `ip`.
+
+## Allow WSL2 to bypass the Windows Firewall with a Powershell task
+
+Steps:
+
+1. [Download](https://git.bryanroessler.com/bryan/scripts/raw/master/powershell/wsl2-firewall-rules.ps1) or copy-paste the following Powershell script to a local file:
+{% highlight powershell %}
+{% insert_git_code https://git.bryanroessler.com/bryan/scripts/raw/master/powershell/wsl2-firewall-rules.ps1 %}
+{% endhighlight %}
+2. Edit the port list to add any additional WSL2 ports you wish to expose
+3. Create a startup new task in the Windows Task Scheduler:
+
+    * Name: 'WSL2-Bypass'
+    * Triggers: At log on, for any user
+    * Actions:
+        * Program/Script: `powershell`
+        * Add Arguments: `-ExecutionPolicy Bypass C:\Users\Bryan\Path\To\wsl2-firewall-rules.ps1`
+
+4. Save the task and run it
+
+## Starting WSL2 services automatically at login
+
+You can use your `.bashrc` in the WSL2 or simply append the following line to the beginning of your powershell task:
+
+`bash.exe -c "sudo /usr/sbin/service ssh start; sudo /usr/sbin/service unattended-upgrades start"`
+
+You can add or remove services as necessary. In order to be able to use root privileges without entering a password, you will need to edit the sudoers file using **`visudo`** and adding the following lines:
+
+```(bash)
+bryan ALL = NOPASSWD: /usr/sbin/service start ssh
+bryan ALL = NOPASSWD: /usr/sbin/service start unattended-upgrades
+```
+
+## Troubleshooting
+
+* Make sure that you have already made the appropriate firewall changes within the instance itself.
+* Make sure that your service is running.
+* Try probing for the IP address manually and connecting to the service from the Windows machine.
+
+Enjoy unfettered remote access to your WSL2 services again!

blog.bryanroessler.com/assets/css/beautifuljekyll-minimal.css

@@ -1,12 +1,12 @@
 .main-content {
-  padding-bottom: 50px;
+  padding-bottom: 3.125rem;
 }
 
 footer.footer-min {
   position: fixed;
   bottom: 0;
   width: 100%;
-  padding: 3px;
+  padding: 0.1875rem;
   background-color: #f5f5f5;
   border-top: 1px solid #eeeeee;
   text-align: center;

blog.bryanroessler.com/assets/css/staticman.css

@@ -81,10 +81,10 @@
 /*
  Help text
  ========================================================================== */
-.staticman-comments .help-block {
+.staticman-comments .form-text {
   color: #898c8e;
 }
-.staticman-comments .help-block {
+.staticman-comments .form-text {
   display: block;
   margin-bottom: 1em;
   line-height: 1em;

blog.bryanroessler.com/assets/data/searchcorpus.json

@@ -0,0 +1,23 @@
+---
+layout: null
+---
+[ 
+{% for post in site.posts %} 
+{ 
+"title"    : "{% if post.title != "" %}{{ post.title | strip_html | escape }}{% else %}{{ post.excerpt | strip_html | escape | strip }}{%endif%}", 
+"desc"     : "{% if post.title != "" %}{{ post.title | strip_html | escape }}{% else %}{{ post.excerpt | strip_html | escape | strip }}{%endif%}", 
+"category" : "{{ post.tags | join: ', ' }}", 
+"url"      : "{{ site.baseurl }}{{ post.url | escape }}", 
+"date"     : "{{ post.date | date: "%B %e, %Y" | default: "January 1, 1970" }}" 
+}, 
+{% endfor %} 
+{% for page in site.html_pages %}{% if page.title != "{title}" and page.title != "404 - Page not found" %} 
+{ 
+"title"    : "{% if page.title != "" %}{{ page.title | strip_html | escape }}{% else %}{{ page.excerpt | strip_html | escape | strip }}{% endif %}", 
+"desc"     : "{% if page.title != "" %}{{ page.title | strip_html | escape }}{% else %}{{ page.excerpt | strip_html | escape | strip }}{% endif %}", 
+"category" : "{% if page.tags %}{{ page.tags | join: ', ' }}{% else %}page{% endif %}", 
+"url"      : "{{ site.baseurl }}{{ page.url }}", 
+"date"     : "{{ page.date | date: '%B %e, %Y' | default: "January 1, 1970" }}" 
+}{% unless forloop.last %},{% endunless %} 
+{% endif %}{% endfor %} 
+]

blog.bryanroessler.com/assets/js/beautifuljekyll.js

@@ -0,0 +1,142 @@
+// Dean Attali / Beautiful Jekyll 2023
+
+let BeautifulJekyllJS = {
+
+  bigImgEl : null,
+  numImgs : null,
+
+  init : function() {
+    setTimeout(BeautifulJekyllJS.initNavbar, 10);
+
+    // Shorten the navbar after scrolling a little bit down
+    $(window).scroll(function() {
+        if ($(".navbar").offset().top > 50) {
+            $(".navbar").addClass("top-nav-short");
+        } else {
+            $(".navbar").removeClass("top-nav-short");
+        }
+    });
+
+    // On mobile, hide the avatar when expanding the navbar menu
+    $('#main-navbar').on('show.bs.collapse', function () {
+      $(".navbar").addClass("top-nav-expanded");
+    });
+    $('#main-navbar').on('hidden.bs.collapse', function () {
+      $(".navbar").removeClass("top-nav-expanded");
+    });
+
+    // show the big header image
+    BeautifulJekyllJS.initImgs();
+
+    BeautifulJekyllJS.initSearch();
+  },
+
+  initNavbar : function() {
+    // Set the navbar-dark/light class based on its background color
+    const rgb = $('.navbar').css("background-color").replace(/[^\d,]/g,'').split(",");
+    const brightness = Math.round(( // http://www.w3.org/TR/AERT#color-contrast
+      parseInt(rgb[0]) * 299 +
+      parseInt(rgb[1]) * 587 +
+      parseInt(rgb[2]) * 114
+    ) / 1000);
+    if (brightness <= 125) {
+      $(".navbar").removeClass("navbar-light").addClass("navbar-dark");
+    } else {
+      $(".navbar").removeClass("navbar-dark").addClass("navbar-light");
+    }
+  },
+
+  initImgs : function() {
+    // If the page was large images to randomly select from, choose an image
+    if ($("#header-big-imgs").length > 0) {
+      BeautifulJekyllJS.bigImgEl = $("#header-big-imgs");
+      BeautifulJekyllJS.numImgs = BeautifulJekyllJS.bigImgEl.attr("data-num-img");
+
+      // 2fc73a3a967e97599c9763d05e564189
+      // set an initial image
+      const imgInfo = BeautifulJekyllJS.getImgInfo();
+      const src = imgInfo.src;
+      const desc = imgInfo.desc;
+      BeautifulJekyllJS.setImg(src, desc);
+
+      // For better UX, prefetch the next image so that it will already be loaded when we want to show it
+      const getNextImg = function() {
+        const imgInfo = BeautifulJekyllJS.getImgInfo();
+        const src = imgInfo.src;
+        const desc = imgInfo.desc;
+
+        const prefetchImg = new Image();
+        prefetchImg.src = src;
+        // if I want to do something once the image is ready: `prefetchImg.onload = function(){}`
+
+        setTimeout(function(){
+          const img = $("<div></div>").addClass("big-img-transition").css("background-image", 'url(' + src + ')');
+          $(".intro-header.big-img").prepend(img);
+          setTimeout(function(){ img.css("opacity", "1"); }, 50);
+
+          // after the animation of fading in the new image is done, prefetch the next one
+          //img.one("transitioned webkitTransitionEnd oTransitionEnd MSTransitionEnd", function(){
+          setTimeout(function() {
+            BeautifulJekyllJS.setImg(src, desc);
+            img.remove();
+            getNextImg();
+          }, 1000);
+          //});
+        }, 6000);
+      };
+
+      // If there are multiple images, cycle through them
+      if (BeautifulJekyllJS.numImgs > 1) {
+        getNextImg();
+      }
+    }
+  },
+
+  getImgInfo : function() {
+    const randNum = Math.floor((Math.random() * BeautifulJekyllJS.numImgs) + 1);
+    const src = BeautifulJekyllJS.bigImgEl.attr("data-img-src-" + randNum);
+    const desc = BeautifulJekyllJS.bigImgEl.attr("data-img-desc-" + randNum);
+
+    return {
+      src : src,
+      desc : desc
+    }
+  },
+
+  setImg : function(src, desc) {
+    $(".intro-header.big-img").css("background-image", 'url(' + src + ')');
+    if (typeof desc !== typeof undefined && desc !== false) {
+      $(".img-desc").text(desc).show();
+    } else {
+      $(".img-desc").hide();
+    }
+  },
+
+  initSearch : function() {
+    if (!document.getElementById("beautifuljekyll-search-overlay")) {
+      return;
+    }
+
+    $("#nav-search-link").click(function(e) {
+      e.preventDefault();
+      $("#beautifuljekyll-search-overlay").show();
+      $("#nav-search-input").focus().select();
+      $("body").addClass("overflow-hidden");
+    });
+    $("#nav-search-exit").click(function(e) {
+      e.preventDefault();
+      $("#beautifuljekyll-search-overlay").hide();
+      $("body").removeClass("overflow-hidden");
+    });
+    $(document).on('keyup', function(e) {
+      if (e.key == "Escape") {
+        $("#beautifuljekyll-search-overlay").hide();
+        $("body").removeClass("overflow-hidden");
+      }
+    });
+  }
+};
+
+// 2fc73a3a967e97599c9763d05e564189
+
+document.addEventListener('DOMContentLoaded', BeautifulJekyllJS.init);

blog.bryanroessler.com/assets/js/staticman.js

@@ -0,0 +1,65 @@
+---
+layout: null
+---
+
+(function ($) {
+  $('#new_comment').submit(function () {
+    const form = this;
+
+    $(form).addClass('disabled');
+
+    {% assign sm = site.staticman -%}
+    const endpoint = '{{ sm.endpoint }}';
+    const repository = '{{ sm.repository }}';
+    const branch = '{{ sm.branch }}';
+    const url = endpoint + repository + '/' + branch + '/comments';
+    const data = $(this).serialize();
+
+    const xhr = new XMLHttpRequest();
+    xhr.open("POST", url);
+    xhr.setRequestHeader('Content-Type', 'application/x-www-form-urlencoded');
+    xhr.setRequestHeader('X-Requested-With', 'XMLHttpRequest');
+    xhr.onreadystatechange = function () {
+      if(xhr.readyState === XMLHttpRequest.DONE) {
+        const status = xhr.status;
+        if (status >= 200 && status < 400) {
+          formSubmitted();
+        } else {
+          formError();
+        }
+      }
+    };
+
+    function formSubmitted() {
+      $('#comment-form-submit').addClass('d-none');
+      $('#comment-form-submitted').removeClass('d-none');
+      $('.page__comments-form .js-notice').removeClass('alert-danger');
+      $('.page__comments-form .js-notice').addClass('alert-success');
+      showAlert('success');
+    }
+
+    function formError() {
+      $('#comment-form-submitted').addClass('d-none');
+      $('#comment-form-submit').removeClass('d-none');
+      $('.page__comments-form .js-notice').removeClass('alert-success');
+      $('.page__comments-form .js-notice').addClass('alert-danger');
+      showAlert('failure');
+      $(form).removeClass('disabled');
+    }
+
+    xhr.send(data);
+
+    return false;
+  });
+
+  function showAlert(message) {
+    $('.page__comments-form .js-notice').removeClass('d-none');
+    if (message == 'success') {
+      $('.page__comments-form .js-notice-text-success').removeClass('d-none');
+      $('.page__comments-form .js-notice-text-failure').addClass('d-none');
+    } else {
+      $('.page__comments-form .js-notice-text-success').addClass('d-none');
+      $('.page__comments-form .js-notice-text-failure').removeClass('d-none');
+    }
+  }
+})(jQuery);

blog.bryanroessler.com/beautiful-jekyll-theme.gemspec

@@ -0,0 +1,30 @@
+# frozen_string_literal: true
+
+Gem::Specification.new do |spec|
+  spec.name          = "beautiful-jekyll-theme"
+  spec.version       = "6.0.1"
+  spec.authors       = ["Dean Attali"]
+  spec.email         = ["daattali@gmail.com"]
+
+  spec.summary       = "Beautiful Jekyll is a ready-to-use Jekyll theme to help you create an awesome website quickly. Perfect for personal blogs or simple project websites, with a focus on responsive and clean design."
+  spec.homepage      = "https://beautifuljekyll.com"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0").select { |f| f.match(%r{^(assets|_layouts|_includes|LICENSE|README|feed|404|_data|tags|staticman)}i) }
+
+  spec.metadata      = {
+    "changelog_uri"     => "https://beautifuljekyll.com/updates/",
+    "documentation_uri" => "https://github.com/daattali/beautiful-jekyll#readme"
+  }
+
+  spec.add_runtime_dependency "jekyll", ">= 3.9.3"
+  spec.add_runtime_dependency "jekyll-paginate", "~> 1.1"
+  spec.add_runtime_dependency "jekyll-sitemap", "~> 1.4"
+  spec.add_runtime_dependency "kramdown-parser-gfm", "~> 1.1"
+  spec.add_runtime_dependency "kramdown", "~> 2.3"
+  spec.add_runtime_dependency "webrick", "~> 1.8"
+
+  spec.add_development_dependency "bundler", ">= 1.16"
+  spec.add_development_dependency "rake", "~> 12.0"
+  spec.add_development_dependency "appraisal", "~> 2.5"
+end

blog.bryanroessler.com/index.html

@@ -1,7 +1,7 @@
 ---
-layout: page
+layout: home
 title: 
-subtitle:
+subtitle: Bryan Roessler's Blog
 use-site-title: false
 ---
 

blog.bryanroessler.com/tags.html

@@ -3,6 +3,8 @@ layout: page
 title: 'Tag Index'
 ---
 
+{% assign date_format = site.date_format | default: "%B %-d, %Y" %}
+
 {%- capture site_tags -%}
     {%- for tag in site.tags -%}
         {{- tag | first -}}{%- unless forloop.last -%},{%- endunless -%}
@@ -11,21 +13,21 @@ title: 'Tag Index'
 {%- assign tags_list = site_tags | split:',' | sort -%}
 
 {%- for tag in tags_list -%}
-    <a href="#{{- tag -}}" class="btn btn-primary tag-btn"><i class="fa fa-tag" aria-hidden="true"></i>&nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})</a>
+    <a href="#{{- tag -}}" class="btn btn-primary tag-btn"><i class="fas fa-tag" aria-hidden="true"></i>&nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})</a>
 {%- endfor -%}
 
 <div id="full-tags-list">
 {%- for tag in tags_list -%}
     <h2 id="{{- tag -}}" class="linked-section">
-        <i class="fa fa-tag" aria-hidden="true"></i>
+        <i class="fas fa-tag" aria-hidden="true"></i>
         &nbsp;{{- tag -}}&nbsp;({{site.tags[tag].size}})
     </h2>
     <div class="post-list">
         {%- for post in site.tags[tag] -%}
             <div class="tag-entry">
-                <a href="{{ post.url | relative_url }}">{{- post.title -}}</a>
+                <a href="{{ post.url | relative_url }}">{{- post.title | strip_html -}}</a>
                 <div class="entry-date">
-                    <time datetime="{{- post.date | date_to_xmlschema -}}">{{- post.date | date: site.date_format -}}</time>
+                    <time datetime="{{- post.date | date_to_xmlschema -}}">{{- post.date | date: date_format -}}</time>
                 </div>
             </div>
         {%- endfor -%}

cv.bryanroessler.com/.dockerignore

@@ -0,0 +1,7 @@
+.git
+.git/
+.gitignore
+_site
+.sass-cache
+.DS_Store
+_vendor

cv.bryanroessler.com/Dockerfile

@@ -0,0 +1,11 @@
+FROM ruby:2.7
+
+WORKDIR /home/app
+
+COPY Gemfile* ./
+
+RUN bundle install
+
+COPY . .
+
+CMD [ "bundle", "exec", "jekyll", "serve" ]

cv.bryanroessler.com/Gemfile

@@ -2,4 +2,5 @@ source "https://rubygems.org"
 
 gem 'github-pages'
 gem 'rake'
-gem 'jekyll'
+gem 'webrick'
+

cv.bryanroessler.com/Gemfile.lock

@@ -1,126 +1,159 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (6.0.2.1)
+    activesupport (8.0.0)
-      concurrent-ruby (~> 1.0, >= 1.0.2)
+      base64
-      i18n (>= 0.7, < 2)
+      benchmark (>= 0.3)
-      minitest (~> 5.1)
+      bigdecimal
-      tzinfo (~> 1.1)
+      concurrent-ruby (~> 1.0, >= 1.3.1)
-      zeitwerk (~> 2.2)
+      connection_pool (>= 2.2.5)
-    addressable (2.7.0)
+      drb
-      public_suffix (>= 2.0.2, < 5.0)
+      i18n (>= 1.6, < 2)
+      logger (>= 1.4.2)
+      minitest (>= 5.1)
+      securerandom (>= 0.3)
+      tzinfo (~> 2.0, >= 2.0.5)
+      uri (>= 0.13.1)
+    addressable (2.8.7)
+      public_suffix (>= 2.0.2, < 7.0)
+    base64 (0.2.0)
+    benchmark (0.4.0)
+    bigdecimal (3.1.8)
     coffee-script (2.4.1)
       coffee-script-source
       execjs
-    coffee-script-source (1.11.1)
+    coffee-script-source (1.12.2)
     colorator (1.1.0)
-    commonmarker (0.17.13)
+    commonmarker (0.23.11)
-      ruby-enum (~> 0.5)
+    concurrent-ruby (1.3.4)
-    concurrent-ruby (1.1.6)
+    connection_pool (2.4.1)
-    dnsruby (1.61.3)
+    csv (3.3.0)
-      addressable (~> 2.5)
+    dnsruby (1.72.3)
-    em-websocket (0.5.1)
+      base64 (~> 0.2.0)
+      simpleidn (~> 0.2.1)
+    drb (2.2.1)
+    em-websocket (0.5.3)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
+      http_parser.rb (~> 0)
-    ethon (0.12.0)
+    ethon (0.16.0)
-      ffi (>= 1.3.0)
+      ffi (>= 1.15.0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
+    execjs (2.10.0)
-    faraday (1.0.0)
+    faraday (2.12.1)
-      multipart-post (>= 1.2, < 3)
+      faraday-net_http (>= 2.0, < 3.5)
-    ffi (1.12.2)
+      json
+      logger
+    faraday-net_http (3.4.0)
+      net-http (>= 0.5.0)
+    ffi (1.17.0-aarch64-linux-gnu)
+    ffi (1.17.0-aarch64-linux-musl)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
-    gemoji (3.0.1)
+    gemoji (4.1.0)
-    github-pages (204)
+    github-pages (232)
-      github-pages-health-check (= 1.16.1)
+      github-pages-health-check (= 1.18.2)
-      jekyll (= 3.8.5)
+      jekyll (= 3.10.0)
-      jekyll-avatar (= 0.7.0)
+      jekyll-avatar (= 0.8.0)
-      jekyll-coffeescript (= 1.1.1)
+      jekyll-coffeescript (= 1.2.2)
-      jekyll-commonmark-ghpages (= 0.1.6)
+      jekyll-commonmark-ghpages (= 0.5.1)
-      jekyll-default-layout (= 0.1.4)
+      jekyll-default-layout (= 0.1.5)
-      jekyll-feed (= 0.13.0)
+      jekyll-feed (= 0.17.0)
       jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.13.0)
+      jekyll-github-metadata (= 2.16.1)
-      jekyll-mentions (= 1.5.1)
+      jekyll-include-cache (= 0.2.1)
+      jekyll-mentions (= 1.6.0)
       jekyll-optional-front-matter (= 0.3.2)
       jekyll-paginate (= 1.1.0)
       jekyll-readme-index (= 0.3.0)
-      jekyll-redirect-from (= 0.15.0)
+      jekyll-redirect-from (= 0.16.0)
       jekyll-relative-links (= 0.6.1)
-      jekyll-remote-theme (= 0.4.1)
+      jekyll-remote-theme (= 0.4.3)
       jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.6.1)
+      jekyll-seo-tag (= 2.8.0)
       jekyll-sitemap (= 1.4.0)
       jekyll-swiss (= 1.0.0)
-      jekyll-theme-architect (= 0.1.1)
+      jekyll-theme-architect (= 0.2.0)
-      jekyll-theme-cayman (= 0.1.1)
+      jekyll-theme-cayman (= 0.2.0)
-      jekyll-theme-dinky (= 0.1.1)
+      jekyll-theme-dinky (= 0.2.0)
-      jekyll-theme-hacker (= 0.1.1)
+      jekyll-theme-hacker (= 0.2.0)
-      jekyll-theme-leap-day (= 0.1.1)
+      jekyll-theme-leap-day (= 0.2.0)
-      jekyll-theme-merlot (= 0.1.1)
+      jekyll-theme-merlot (= 0.2.0)
-      jekyll-theme-midnight (= 0.1.1)
+      jekyll-theme-midnight (= 0.2.0)
-      jekyll-theme-minimal (= 0.1.1)
+      jekyll-theme-minimal (= 0.2.0)
-      jekyll-theme-modernist (= 0.1.1)
+      jekyll-theme-modernist (= 0.2.0)
-      jekyll-theme-primer (= 0.5.4)
+      jekyll-theme-primer (= 0.6.0)
-      jekyll-theme-slate (= 0.1.1)
+      jekyll-theme-slate (= 0.2.0)
-      jekyll-theme-tactile (= 0.1.1)
+      jekyll-theme-tactile (= 0.2.0)
-      jekyll-theme-time-machine (= 0.1.1)
+      jekyll-theme-time-machine (= 0.2.0)
       jekyll-titles-from-headings (= 0.5.3)
-      jemoji (= 0.11.1)
+      jemoji (= 0.13.0)
-      kramdown (= 1.17.0)
+      kramdown (= 2.4.0)
-      liquid (= 4.0.3)
+      kramdown-parser-gfm (= 1.1.0)
+      liquid (= 4.0.4)
       mercenary (~> 0.3)
       minima (= 2.5.1)
-      nokogiri (>= 1.10.4, < 2.0)
+      nokogiri (>= 1.16.2, < 2.0)
-      rouge (= 3.13.0)
+      rouge (= 3.30.0)
       terminal-table (~> 1.4)
-    github-pages-health-check (1.16.1)
+      webrick (~> 1.8)
+    github-pages-health-check (1.18.2)
       addressable (~> 2.3)
       dnsruby (~> 1.60)
-      octokit (~> 4.0)
+      octokit (>= 4, < 8)
-      public_suffix (~> 3.0)
+      public_suffix (>= 3.0, < 6.0)
       typhoeus (~> 1.3)
-    html-pipeline (2.12.3)
+    html-pipeline (2.14.3)
       activesupport (>= 2)
       nokogiri (>= 1.4)
-    http_parser.rb (0.6.0)
+    http_parser.rb (0.8.0)
-    i18n (0.9.5)
+    i18n (1.14.6)
       concurrent-ruby (~> 1.0)
-    jekyll (3.8.5)
+    jekyll (3.10.0)
       addressable (~> 2.4)
       colorator (~> 1.0)
+      csv (~> 3.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
+      i18n (>= 0.7, < 2)
       jekyll-sass-converter (~> 1.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (>= 1.17, < 3)
       liquid (~> 4.0)
       mercenary (~> 0.3.3)
       pathutil (~> 0.9)
       rouge (>= 1.7, < 4)
       safe_yaml (~> 1.0)
-    jekyll-avatar (0.7.0)
+      webrick (>= 1.0)
+    jekyll-avatar (0.8.0)
       jekyll (>= 3.0, < 5.0)
-    jekyll-coffeescript (1.1.1)
+    jekyll-coffeescript (1.2.2)
       coffee-script (~> 2.2)
-      coffee-script-source (~> 1.11.1)
+      coffee-script-source (~> 1.12)
-    jekyll-commonmark (1.3.1)
+    jekyll-commonmark (1.4.0)
-      commonmarker (~> 0.14)
+      commonmarker (~> 0.22)
-      jekyll (>= 3.7, < 5.0)
+    jekyll-commonmark-ghpages (0.5.1)
-    jekyll-commonmark-ghpages (0.1.6)
+      commonmarker (>= 0.23.7, < 1.1.0)
-      commonmarker (~> 0.17.6)
+      jekyll (>= 3.9, < 4.0)
-      jekyll-commonmark (~> 1.2)
+      jekyll-commonmark (~> 1.4.0)
-      rouge (>= 2.0, < 4.0)
+      rouge (>= 2.0, < 5.0)
-    jekyll-default-layout (0.1.4)
+    jekyll-default-layout (0.1.5)
-      jekyll (~> 3.0)
+      jekyll (>= 3.0, < 5.0)
-    jekyll-feed (0.13.0)
+    jekyll-feed (0.17.0)
       jekyll (>= 3.7, < 5.0)
     jekyll-gist (1.5.0)
       octokit (~> 4.2)
-    jekyll-github-metadata (2.13.0)
+    jekyll-github-metadata (2.16.1)
       jekyll (>= 3.4, < 5.0)
-      octokit (~> 4.0, != 4.4.0)
+      octokit (>= 4, < 7, != 4.4.0)
-    jekyll-mentions (1.5.1)
+    jekyll-include-cache (0.2.1)
+      jekyll (>= 3.7, < 5.0)
+    jekyll-mentions (1.6.0)
       html-pipeline (~> 2.3)
       jekyll (>= 3.7, < 5.0)
     jekyll-optional-front-matter (0.3.2)
@@ -128,124 +161,154 @@ GEM
     jekyll-paginate (1.1.0)
     jekyll-readme-index (0.3.0)
       jekyll (>= 3.0, < 5.0)
-    jekyll-redirect-from (0.15.0)
+    jekyll-redirect-from (0.16.0)
       jekyll (>= 3.3, < 5.0)
     jekyll-relative-links (0.6.1)
       jekyll (>= 3.3, < 5.0)
-    jekyll-remote-theme (0.4.1)
+    jekyll-remote-theme (0.4.3)
       addressable (~> 2.0)
       jekyll (>= 3.5, < 5.0)
-      rubyzip (>= 1.3.0)
+      jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
+      rubyzip (>= 1.3.0, < 3.0)
     jekyll-sass-converter (1.5.2)
       sass (~> 3.4)
-    jekyll-seo-tag (2.6.1)
+    jekyll-seo-tag (2.8.0)
-      jekyll (>= 3.3, < 5.0)
+      jekyll (>= 3.8, < 5.0)
     jekyll-sitemap (1.4.0)
       jekyll (>= 3.7, < 5.0)
     jekyll-swiss (1.0.0)
-    jekyll-theme-architect (0.1.1)
+    jekyll-theme-architect (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
+    jekyll-theme-cayman (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
+    jekyll-theme-dinky (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
+    jekyll-theme-hacker (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
+    jekyll-theme-leap-day (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
+    jekyll-theme-merlot (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
+    jekyll-theme-midnight (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
+    jekyll-theme-minimal (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
+    jekyll-theme-modernist (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.4)
+    jekyll-theme-primer (0.6.0)
       jekyll (> 3.5, < 5.0)
       jekyll-github-metadata (~> 2.9)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
+    jekyll-theme-slate (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
+    jekyll-theme-tactile (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
+    jekyll-theme-time-machine (0.2.0)
-      jekyll (~> 3.5)
+      jekyll (> 3.5, < 5.0)
       jekyll-seo-tag (~> 2.0)
     jekyll-titles-from-headings (0.5.3)
       jekyll (>= 3.3, < 5.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.11.1)
+    jemoji (0.13.0)
-      gemoji (~> 3.0)
+      gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
-    kramdown (1.17.0)
+    json (2.9.0)
-    liquid (4.0.3)
+    kramdown (2.4.0)
-    listen (3.2.1)
+      rexml
+    kramdown-parser-gfm (1.1.0)
+      kramdown (~> 2.0)
+    liquid (4.0.4)
+    listen (3.9.0)
       rb-fsevent (~> 0.10, >= 0.10.3)
       rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.6.2)
     mercenary (0.3.6)
-    mini_portile2 (2.4.0)
     minima (2.5.1)
       jekyll (>= 3.5, < 5.0)
       jekyll-feed (~> 0.9)
       jekyll-seo-tag (~> 2.1)
-    minitest (5.14.0)
+    minitest (5.25.4)
-    multipart-post (2.1.1)
+    net-http (0.6.0)
-    nokogiri (1.10.9)
+      uri
-      mini_portile2 (~> 2.4.0)
+    nokogiri (1.16.8-aarch64-linux)
-    octokit (4.17.0)
+      racc (~> 1.4)
-      faraday (>= 0.9)
+    nokogiri (1.16.8-arm-linux)
-      sawyer (~> 0.8.0, >= 0.5.3)
+      racc (~> 1.4)
+    nokogiri (1.16.8-arm64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86-linux)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86_64-darwin)
+      racc (~> 1.4)
+    nokogiri (1.16.8-x86_64-linux)
+      racc (~> 1.4)
+    octokit (4.25.1)
+      faraday (>= 1, < 3)
+      sawyer (~> 0.9)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (3.1.1)
+    public_suffix (5.1.1)
-    rake (13.0.1)
+    racc (1.8.1)
-    rb-fsevent (0.10.3)
+    rake (13.2.1)
-    rb-inotify (0.10.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rouge (3.13.0)
+    rexml (3.3.9)
-    ruby-enum (0.7.2)
+    rouge (3.30.0)
-      i18n
+    rubyzip (2.3.2)
-    rubyzip (2.2.0)
     safe_yaml (1.0.5)
     sass (3.7.4)
       sass-listen (~> 4.0.0)
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
       rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.8.2)
+    sawyer (0.9.2)
       addressable (>= 2.3.5)
-      faraday (> 0.8, < 2.0)
+      faraday (>= 0.17.3, < 3)
+    securerandom (0.4.0)
+    simpleidn (0.2.3)
     terminal-table (1.8.0)
       unicode-display_width (~> 1.1, >= 1.1.1)
-    thread_safe (0.3.6)
+    typhoeus (1.4.1)
-    typhoeus (1.3.1)
       ethon (>= 0.9.0)
-    tzinfo (1.2.6)
+    tzinfo (2.0.6)
-      thread_safe (~> 0.1)
+      concurrent-ruby (~> 1.0)
-    unicode-display_width (1.7.0)
+    unicode-display_width (1.8.0)
-    zeitwerk (2.3.0)
+    uri (1.0.2)
+    webrick (1.9.1)
 
 PLATFORMS
-  ruby
+  aarch64-linux
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  arm-linux
+  arm-linux-gnu
+  arm-linux-musl
+  arm64-darwin
+  x86-linux
+  x86-linux-gnu
+  x86-linux-musl
+  x86_64-darwin
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
   github-pages
-  jekyll
   rake
+  webrick
 
 BUNDLED WITH
-   2.0.2
+   2.5.22

cv.bryanroessler.com/README.md

@@ -15,6 +15,13 @@ To test locally, run the following in your terminal:
 2. `bundle exec jekyll serve`
 3. Open your browser to `localhost:4000`
 
+### Running locally with Docker
+
+To test locally with docker, run the following in your terminal after installing docker into your system:
+
+1. `docker image build -t resume-template .`
+2. `docker run --rm --name resume-template -v "$PWD":/home/app --network host resume-template`
+
 ### Customizing
 
 First you'll want to fork the repo to your own account. Then clone it locally and customize, or use the GitHub web editor to customize.
@@ -56,4 +63,4 @@ If you spot a bug, or want to improve the code, or even make the dummy content b
 
 The code and styles are licensed under the MIT license. [See project license.](LICENSE) Obviously you should not use the content of this demo repo in your own resume. :wink:
 
-Disclaimer: Use of Homer J. Simpson image and name used under [Fair Use](https://en.wikipedia.org/wiki/Fair_use) for educational purposes. Project license does not apply to use of this material.
+Disclaimer: Use of Lisa M. Simpson image and name used under [Fair Use](https://en.wikipedia.org/wiki/Fair_use) for educational purposes. Project license does not apply to use of this material.

cv.bryanroessler.com/_config.yml

@@ -12,7 +12,7 @@ sass:
 # Resume settings
 resume_avatar:                  "true"
 resume_name:                    "Bryan C. Roessler"
-resume_title:                   "Research Assistant"
+resume_title:                   "Software Developer"
 
 # used for the contact button in _layouts/resume.html
 resume_contact_email:           "bryanroessler@gmail.com"
@@ -25,10 +25,9 @@ resume_header_contact_info:     "St. Petersburg, FL • bryanroessler@gmail.com"
 display_header_contact_info:    "true"
 
 resume_header_intro: >
-                    <p>I am a computational biologist specializing in molecular
+                    <p>I am a full-stack software developer with a background in high-performance computing and molecular dynamics.
-                    dynamics that is currently seeking a creative and impactful
+                    I excel at breaking complex problems into simple, solvable solutions. In my free time I enjoy contributing
-                    position in the academic, pharmaceutical, or biotechnology
+                    to a variety of open source projects within the Linux ecosystem.</p>
-                    sectors.</p>
 
 # use "yes" to display the email contact button,
 # "no" to display an "I'm not looking for work" message,

cv.bryanroessler.com/_data/experience.yml

@@ -1,23 +1,12 @@
 # Jobs
-- company: University of Alabama at Birmingham
+- company: BRSoftware
-  position: Research Assistant
+  position: Lead Software Developer and Consultant
   duration: Jan 2018 — Present
   summary: >
-    I'm currently completing work on two projects: <ul class="resume-item-list">
+    I create full-stack software solutions for clients in a variety of programming languages.
-    <li>Modifed substrate effects on the binding mechanisms of Sortase A, a
-    revised model. <i>In review.</i></li>
-    <li>The role of constitutive gain-of-function mutations on the structure and dynamics of the cystic fibrosis transmembrane conductance regulator.</li>
 
 - company: University of Alabama at Birmingham
   position: Graduate Research Assistant
-  duration:  Aug 2010 &mdash; Dec 2017
+  duration:  Aug 2010 &mdash; Jan 2018
   summary: >
-    My doctoral thesis focused on the use of computational molecular dynamics to understand the impact of mutations and empirical structural determination methods on the
+    My doctoral thesis utilized computational molecular dynamics to study the effects of mutations on the structure and function of multidrug resistance proteins.
-    function and dynamics of multidrug resistance (specifically, CFTR) and sortase proteins.
-
-- company: U.S. Census Bureau
-  position: Crew Leader
-  duration: Jan 2010  &mdash; May 2010
-  summary: >
-    Supervised a team of enumerators to ensure assigned tasks were completed properly.
-    Monitored and evaluated performance for adjustments and improvements.

cv.bryanroessler.com/_data/interests.yml

@@ -1,8 +1,3 @@
-# Interests
+
-- description: Futurology, Automation & AI
+
-- description: Open-source Software
+
-- description: Computer Hardware
-- description: Fitness & Nutrition
-- description: E-Bikes
-- description: Pet Fostering
-- description: College Basketball (Go Zags!)

cv.bryanroessler.com/_data/skills.yml

@@ -1,33 +1,24 @@
 - skill:
-  name: NAMD & VMD
+  name: Molecular dynamics --- namd, vmd, gromacs, gaussian, charmm, amber
   level: 100%
 - skill:
-  name: Bash, Python, Tcl
+  name: Languages --- python, php, sql, bash, tcl, R, css, html5, ruby, latex, git, gnuplot, matplotlib
+  level: 100%
+- skill:
+  name: Web frameworks --- jekyll, rails, hugo, django
+  level: 100%
+- skill:
+  name: Job control --- sge, slurm, pbs/torque
+  level: 100%
+- skill:
+  name: Linux sysadmin --- rhel & debian, systemd, podman/docker/oci, udev
+  level: 100%
+- skill:
+  name: Cloud admin --- k8s & openshift
   level: 98%
 - skill:
-  name: SGE, Slurm, PBS/Torque
+  name: Networking --- openwrt, pfsense, iptables, gpg
-  level: 98%
-- skill:
-  name: R, gnuplot, matplotlib
-  level: 98%
-- skill:
-  name: Linux SysAdmin (Red Hat & Debian)
-  level: 98%
-- skill:
-  name: LaTeX
   level: 90%
 - skill:
-  name: GROMACS/CHARMM/AMBER
+  name: Graphics design
-  level: 90%
+  level: 10%
-- skill:
-  name: QM/MM (Gaussian & FFTK)
-  level: 90%
-- skill:
-  name: Git
-  level: 90%
-- skill:
-  name: Networking (OpenWRT, pfSense, iptables)
-  level: 85%
-- skill:
-  name: Website Design
-  level: 60%

cv.bryanroessler.com/_data/training.yml

@@ -0,0 +1,14 @@
+# Copyright 2022 Bryan C. Roessler
+# 
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#     http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+

cv.bryanroessler.com/_includes/head.html

@@ -14,5 +14,5 @@
 
   <link rel="stylesheet" href="css/main.css">
   <link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl | prepend: site.url }}">
-  <link rel="icon" type="image/x-icon" href="/favicon.png" />
+  <link rel="icon" type="image/x-icon" href="favicon.png" />
 </head>

cv.bryanroessler.com/_layouts/resume.html

@@ -100,6 +100,42 @@
           <h2>Publications</h2>
         </header>
 
+<<<<<<< HEAD
+        {% for education in site.data.education %}
+        <div class="resume-item" itemscope itemprop="alumniOf" itemtype="http://schema.org/CollegeOrUniversity">
+          <h3 class="resume-item-title" itemprop="name">{{ education.uni }}</h3>
+          <h4 class="resume-item-details group" itemprop="description">{{ education.degree }} &bull; {{ education.year }}</h4>
+          <h5 class="resume-item-details award-title" itemprop="description">{{ education.award }}</h5>
+          <p class="resume-item-copy" itemprop="description">
+            <ul class="resume-item-list">
+              {% for award in education.awards %}
+              <li>{{ award.award }}</li>
+              {% endfor %}
+            </ul>
+
+
+          <p class="resume-item-copy">{{ education.summary }}</p>
+        </div>
+        {% endfor %}
+      </section>
+      <!-- end Education -->
+      {% endif %}
+
+
+      {% if site.resume_section_projects %}
+      <!-- begin Projects -->
+      <section class="content-section">
+        <header class="section-header">
+          <h2>Projects</h2>
+        </header>
+
+        {% for project in site.data.projects %}
+        <div class="resume-item" itemscope itemtype="http://schema.org/CreativeWork">
+          <meta itemprop="creator" content="{{ site.resume_name }}" itemtype="http://schema.org/Person" />
+          <h3 class="resume-item-title" itemprop="name">{% if project.url %}<a href="{{ project.url }}" itemprop="url">{{ project.project }}</a>{% else %}{{ project.project }}{% endif %}</h3>
+          <h4 class="resume-item-details" itemprop="description">{{ project.role }}  &bull; {{ project.duration }}</h4>
+          <p class="resume-item-copy">{{ project.description }}</p>
+=======
         {% for publication in site.data.publications %}
         <div class="resume-item" itemscope itemtype="http://schema.org/ScholarlyArticle">
           <h3 class="resume-item-publication-title" itemprop="title">{% if publication.url %}<a href="{{ publication.url }}" itemprop="url">{{ publication.title }}</a>{% else %}{{ publication.title }}{% endif %}</h3>
@@ -111,6 +147,7 @@
                 <p> {{ publication.abstract }} </p>
             </details>
           </p>
+>>>>>>> 59c0648 (Initial commits)
         </div>
         {% endfor %}
 

landing.bryanroessler.com/.github/issue_template.md

@@ -1,3 +1,3 @@
-Thank you for submitting an issue!
+Please only submit feature suggestions or bug reports if you believe something is broken.
 
-Please only submit bug reports or feature suggestions. Please do not submit support requests and general help questions in this forum.
+If you need help, you can attend the [Office Hours](https://beautifuljekyll.com/officehours) (only available for [sponsors](https://beautifuljekyll.com/plans/)).

landing.bryanroessler.com/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: Beautiful Jekyll CI
+on: [push, pull_request]
+jobs:
+  build:
+    name: Build Jekyll
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '3.3'
+      - name: Install dependencies
+        run: bundle install && bundle exec appraisal install
+      - name: Setup Pages
+        id: configure-pages
+        uses: actions/configure-pages@v5
+      - name: Setup CI config
+        run: |
+          echo "---" > _config_ci.yml
+          echo "baseurl: ${{ steps.configure-pages.outputs.base_path }}" >> _config_ci.yml
+      - name: Build site
+        env:
+          JEKYLL_ENV: production
+        run: bundle exec appraisal jekyll build --future --config _config_ci.yml,_config.yml
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3

landing.bryanroessler.com/.gitignore

@@ -10,3 +10,7 @@ _drafts
 .DS_Store
 Thumbs.db
 ehthumbs.db
+
+Gemfile.lock
+
+beautiful-jekyll-theme-*.gem

landing.bryanroessler.com/404.html

@@ -9,5 +9,5 @@ permalink: /404.html
   <h1>Move along. (404 error)</h1>
   <br/>
 
-  <img src="{{ 'img/404-southpark.jpg' | relative_url }}" />
+  <img src="{{ 'assets/img/404-southpark.jpg' | relative_url }}" alt="Not found" />
 </div>

landing.bryanroessler.com/Appraisals

@@ -0,0 +1,6 @@
+appraise "jekyll-3" do
+  gem "jekyll", "3.9.4"
+end
+appraise "jekyll-4" do
+  gem "jekyll", "4.3.3"
+end

landing.bryanroessler.com/CHANGELOG.md

@@ -1,8 +1,180 @@
-# CHANGELOG
+## Unreleased version
+- BREAKING CHANGE: Allow changing the order of the social network links that appear in the footer (#1152)
+- BREAKING CHANGE: `google-scholar` social network link no longer requires the prefix `citations?user=`; if you previously set this parameter, it needs to be updated (#1189)
+- Added `mathjax` YAML parameter to allow support for MathJax, used to write LaTeX expressions (#195)
+- Added explicit support for favicons, you only need to add a `favicon.ico` file to the root directory
+- The footer of a page always sticks to the bottom, even on short pages (#576)
+- Added `author` YAML parameter to allow specifying the author(s) of a post (#1220)
+- Fixed bug where search results broke if a post title had a backslash (#1279)
+- Fixed bug where hovering over search results showed the text "{desc}" (#1156)
+- Added social network links for GitLab, Bluesky, Whatsapp, Untappd (#1168, #1218, #1299, #1307)
+- Support reddit social network link to either be a subreddit or a user (#1371)
+- Use CSS variables (#661)
+- Added instructions and example on how to fix image links in project sites (#1171)
+- Pagination buttons: use nicer arrows, and don't show text on small screens (#1221)
+- Updated Yelp URL format - if you previously used the `yelp` social network config parameter, you might need to update the config value (#1259)
+- Added `title-on-all-pages` config setting, that adds the website title to all page titles (#1272)
+- Change Twitter icon to X (#1193)
+- Upgraded font-awesome to 6.5.2 (#1330)
 
-This file lists all non-trivial changes to Beautiful Jekyll.
+## v6.0.1 (2023-06-08)
 
-I often make small changes to documentation, to the demo site, or to the general look-and-feel. These changes will not be listed here. Any other minor changes will also not be listed here.
+This version has been in the works for a few years. It includes several new features that were highly requested, numerous bug fixes, new documentation, and aggresively encourages migrating from the old Google Universal Analytics to the new Analytics 4.
+
+#### Breaking changes
+
+- As of July 2023, Google Universal Analytics is going away and being replaced by Google Analytics 4. Beautiful Jekyll sites that still use the old analytics tag will show a warning to encourage them to move to Analytics 4 (#1096).
+- More control over RSS feed sharing: previously, an RSS feed was *always* generated, and if the config setting `rss-description` was set then there was an RSS icon in the footer. Now, an RSS feed is only generated when the config setting `rss-description` exists, and an RSS footer icon is only shown if `rss: true` is set in the `social-network-links` config settings.
+
+#### New parameters and settings
+
+- Added `navbar-var-length` config setting that allows the navigation menu to be the same length as the longest sub-menu, so that long words in the submenu are not cut off (#765) 
+- Added `post_search` config setting that creates a Search button in the navbar (#770)
+- Added `edit_page_button` config setting that adds a "Edit page" button to the footer (to edit the current page on GitHub) (#1004)
+- Added `footer-hover-col` config setting to customize the hover colour of links in the footer (#848)
+
+#### New features and improvements
+
+- Made the home page feed more accessible for screen readers (#950)
+- Added support for giscus comments (#886) and CommentBox (#960)
+- Added support for Cloudflare Analytics (#797)
+- Added Reddit in share options of posts (#815)
+
+#### Bug fixes
+
+- Fixed page titles, subtitles, and excerpts rendering correctly when there are special characeters in them (#856) 
+- Fixed bug where navbar secondary level dropdown items didn't inherit the same colour as the primary navbar links
+- Fixed bug where the navbar "burger" collapsed button didn't always revert back to a light colour
+- Fixed bug where using an image as a navbar title did not render in GitHub Project pages that did not have a custom domain
+- Fixed bug where image thumbnails on the feed page were always forced into a square rather than maintaining a proper image aspect ratio
+- Fixed bug where special characters in the title led to broken share tags (#744)
+- Fixed bug where staticman didn't work jQuery slim version is used (#766)
+- Fixed very long strings to wrap around the next line rather than go off-screen (#787)
+
+#### Small changes
+
+- Updated staticman from using v2 (public servers) to v3 (private servers) due to the public servers becoming obsolete (#775)
+- Added social network links for Patreon, Medium, Itch.io, Discord, Kaggle, Hackerrank (#783, #788, #907, #961, #978)
+- Slightly reworked margins and position for avatar image to resolve an alignment issue on Safari
+- Changed the width at which the navbar collapses to a higher threshold because most modern non-mobile browsers are >1000px
+
+
+## v5.0.0 (2020-09-15)
+
+One of the major changes in this version is that a lot of time was spent on rethinking the entire SEO and social media sharing model (how a page looks on eg. Google, Twitter, Facebok). It was redesigned to be more simple and customizable. The new documentation has a section dedicated to SEO and social media sharing of a page. Unfortunately some changes that are not backwards-compatible had to be made.
+
+#### Breaking changes
+
+- Renamed `description` YAML parameter to `share-description` to be more clear
+- Renamed `description` config setting to `rss-description` since it was only used in RSS (the FAQ explains the difference between YAML parameters and config settings if you're confused)
+- Removed YAML parameter `use-site-title` (you can now specify the exact title using `share-title`)
+- Removed undocumented YAML parameters `meta-title` and `meta-description`
+- Removed `link-tags` config setting because it wasn't necessary. If you use tags, there will now always be a tags page created; if you don't use tags there won't be a tags page.
+- The YAML parameter `show-avatar` is now true by default. This has always been the case for GitHub Pages users, but not for `remote_theme` users. For consistency, it's now the default for everyone. (#715)
+
+#### New parameters and settings
+
+- Added `full-width` YAML parameter to allow having full-width pages
+- Added `feed_show_excerpt` config setting to show/hide the post excerpts on the feed page
+- Added `feed_show_tags` config setting to show/hide the list of tags on post previews on the feed page
+- Added `share-title` YAML parameter to give control over the search engine/social media title
+- Added `last-updated` YAML parameter to show a "Last Updated on" date for blog posts
+- Added `before-content` and `after-content` YAML parameters that allow you to add some common HTML before the main content of a page (below the title) or after the main content (above the footer). Works in a similar way to `footer-extra`.
+- Added `head-extra` YAML parameter which is similar to `footer-extra` but is used to include custom HTML code in a page's `<head>` tag
+- Added `site-js` config setting to provide JavaScript files that are used on all pages in the site
+
+#### New features and improvements
+
+- Improved the `footer-extra` YAML parameter to support multiple files instead of only a single file
+- Added automatic navbar color detection (#702)
+- When `nav-short` is turned on, the avatar will also be shorter
+- Changed navbar and footer background colour to be slightly darker, for better contrast with the default white page background for accessibility reasons
+- Changed the behaviour of `site-css` to include site-wide CSS file **before** instead of after page-specific files
+- Renamed internal css/js files from "main" to "beautifuljekyll" to make it easier for users to troubleshoot
+- Added alt text to all images for better accessibility
+- Made thumbnail images square instead of circles, as users reported that circles cut off important parts of images
+
+#### Bug fixes
+
+- Fixed rendering issues with `nav-short` parameter that caused the body of the page to start too low
+- Fixed some CSS styles that broke during the bootstrap 4 migration (#716)
+
+#### Library upgrades
+
+- Upgraded kramdown to version 2.3.0 to fix security issues
+- Upgraded jQuery to version 3.5.1 to fix a couple security vulnerabilities with the previous version
+
+## v4.1.0 (2020-08-08)
+
+- Added Open Graph `site_name` meta field to pages automatically
+- Added `text-col` config setting  for main text color (#694)
+- Added `keywords` config setting to set the meta keywords on all pages (for SEO purposes) (#691)
+- Added `mobile-theme-col` config setting to allow a mobile theme colour (#692)
+- Added `site-css` config setting in the config file to provide CSS files that are used on all pages in the site (#695)
+- Added YAML parameter `description`: creates the meta description on a page, intended to provide a brief description of the page for search engines and when the page is shared (#690)
+
+## v4.0.1 (2020-07-13)
+
+- Fixed staticman comments UI that was broken since the migration to bootstrap 4
+
+## v4.0.0 (2020-07-12)
+
+- **BREAKING CHANGE** Replace `image` YAML parameter with `thumbnail-img` to be more clear
+- **MAJOR BEHAVIOUR CHANGE** Don't use the thumbnail as the avatar image
+- Cover image will automatically be used as thumbnail if none is provided
+- Image to share on social media will use the cover image or thumbnail if none is provided
+- All images (social media share, thumbnail, cover) can use either relative or absoluate paths.
+- Fixed issue where if a dropdown menu was the last item in the menu bar, it did not have a proper margin on the right
+- Added social network links: Mastodon (#646), Google Scholar, ORCID (#670)
+- Added support for sharing pages on new social network: VK (#657)
+- Use Open Graph type 'article' for blog posts (#669)
+- Use Twitter's large sumary card (large image) when there is a cover image, thumbnail image, or share image specified (#668)
+- Made post images in the feed page smaller on smaller devices
+- Fixed jQuery version in staticman (#671)
+
+## v3.0.0 (2020-05-07)
+
+- **BREAKING CHANGE** Upgraded from Bootstrap 3.3.2 to 4.4.1. This involved a major rewrite of most components. This shouldn't affect any users unless you have custom HTML/CSS code which the new Bootstrap could have broken.
+- **BREAKING CHANGE** Renamed `bigimg` YAML parameter to `cover-img`
+- **BREAKING CHANGE** Removed `googlefonts` YAML parameter since googlefonts are just CSS so they can be loaded via `ext-css`
+- **BREAKING CHANGE** Upgraded from jQuery 1.11.2 to 3.4.2. This should not affect most people
+- Added `navbar-border-col` setting in the config file
+- Added accessibility features where possible
+- Made the theme completely responsive by rewriting all CSS to use 'rem' instead of 'px'
+- Rewrote and simplified some JavaScript code to use CSS or Bootstrap alternatives that weren't available in 2015
+- Removed most of the sample posts so that users only have two sample posts to learn from
+- Improvements to the README instructions
+
+## v2.3.0 (2020-04-29)
+
+- Added YAML parameter `footer-extra` for including custom content in the footer
+- Fixed issue: linking to a specific part of a page resulted in scrolling too far (#69)
+- Added YAML parameter `nav-short` to have navbar permanently collapsed
+- Added social network link: Calendly
+- Fixed bug where RSS link in footer was showing even when turned off
+
+## v2.2.0 (2020-04-27)
+
+- Added social network link: Telegram (#625) (thanks @mashed-potatoes)
+- Moved the demo site to an independent URL: https://beautifuljekyll.com
+- Major documentation overhaul and cleanup of old files
+- Fixed a few bugs from the remote_theme migration
+
+## v2.0.0 (2020-04-26)
+
+- Beautiful-Jekyll v2.0.0 available as an official Ruby gem
+- Beautifull-Jekyll now supports the `remote_theme` config (#339) (thanks @gpotter2 and @skalee)
+- Consolidated the demo site, the ruby gem, and the master branch into one
+- Added a `home` layout and used it in the index page
+- Added readtime support for the post header (#622) (thanks @MutMatt and @rubyreads)
+- Removed the dependency on `_data` folder since it doesn't get copied when using `remote_theme` (#614)
+- Added support for configuring lang attribute on `html` tag (#608) (thanks @skalee)
+- Added ability to disable round logo (thanks @gpotter2)
+- Added support for Utterances comments (#596) (thanks @colynn)
+- Removed 'just-comments' as it's getting killed at the end of the year
+- Upgraded font-awesome to 5.12.1 (#587) (thanks @cketti)
+
+## Prior to 2020
 
 **2018-12-24** Add support for Staticman comments (#440) (thanks @VincentTam)
 
@@ -73,3 +245,4 @@ I often make small changes to documentation, to the demo site, or to the general
 ... Many small changes because the site was in its infancy
 
 **2015-03-12** Beautiful Jekyll version 0.0000001 is released!
+

landing.bryanroessler.com/Gemfile

@@ -1,9 +1,5 @@
-source 'https://rubygems.org'
+# frozen_string_literal: true
 
-gem "github-pages", '197', group: :jekyll_plugins
+source "https://rubygems.org"
 
-gem 'jekyll'
+gemspec
-
-# enable tzinfo-data for local build
-# gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw]
-gem 'jekyll-paginate'

landing.bryanroessler.com/Gemfile.lock

@@ -1,251 +1,172 @@
+PATH
+  remote: .
+  specs:
+    beautiful-jekyll-theme (6.0.1)
+      jekyll (>= 3.9.3)
+      jekyll-paginate (~> 1.1)
+      jekyll-sitemap (~> 1.4)
+      kramdown (~> 2.3)
+      kramdown-parser-gfm (~> 1.1)
+      webrick (~> 1.8)
+
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (4.2.10)
+    addressable (2.8.7)
-      i18n (~> 0.7)
+      public_suffix (>= 2.0.2, < 7.0)
-      minitest (~> 5.1)
+    appraisal (2.5.0)
-      thread_safe (~> 0.3, >= 0.3.4)
+      bundler
-      tzinfo (~> 1.1)
+      rake
-    addressable (2.7.0)
+      thor (>= 0.14.0)
-      public_suffix (>= 2.0.2, < 5.0)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.11.1)
     colorator (1.1.0)
-    commonmarker (0.17.13)
+    concurrent-ruby (1.3.4)
-      ruby-enum (~> 0.5)
+    em-websocket (0.5.3)
-    concurrent-ruby (1.1.6)
-    dnsruby (1.61.3)
-      addressable (~> 2.5)
-    em-websocket (0.5.1)
       eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0.6.0)
+      http_parser.rb (~> 0)
-    ethon (0.12.0)
-      ffi (>= 1.3.0)
     eventmachine (1.2.7)
-    execjs (2.7.0)
+    ffi (1.17.0)
-    faraday (1.0.0)
+    ffi (1.17.0-aarch64-linux-gnu)
-      multipart-post (>= 1.2, < 3)
+    ffi (1.17.0-aarch64-linux-musl)
-    ffi (1.12.2)
+    ffi (1.17.0-arm-linux-gnu)
+    ffi (1.17.0-arm-linux-musl)
+    ffi (1.17.0-arm64-darwin)
+    ffi (1.17.0-x86-linux-gnu)
+    ffi (1.17.0-x86-linux-musl)
+    ffi (1.17.0-x86_64-darwin)
+    ffi (1.17.0-x86_64-linux-gnu)
+    ffi (1.17.0-x86_64-linux-musl)
     forwardable-extended (2.6.0)
-    gemoji (3.0.1)
+    google-protobuf (3.25.5)
-    github-pages (197)
+    google-protobuf (3.25.5-aarch64-linux)
-      activesupport (= 4.2.10)
+    google-protobuf (3.25.5-arm64-darwin)
-      github-pages-health-check (= 1.16.1)
+    google-protobuf (3.25.5-x86-linux)
-      jekyll (= 3.7.4)
+    google-protobuf (3.25.5-x86_64-darwin)
-      jekyll-avatar (= 0.6.0)
+    google-protobuf (3.25.5-x86_64-linux)
-      jekyll-coffeescript (= 1.1.1)
+    http_parser.rb (0.8.0)
-      jekyll-commonmark-ghpages (= 0.1.5)
+    i18n (1.14.6)
-      jekyll-default-layout (= 0.1.4)
-      jekyll-feed (= 0.11.0)
-      jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.12.1)
-      jekyll-mentions (= 1.4.1)
-      jekyll-optional-front-matter (= 0.3.0)
-      jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.2.0)
-      jekyll-redirect-from (= 0.14.0)
-      jekyll-relative-links (= 0.6.0)
-      jekyll-remote-theme (= 0.3.1)
-      jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.5.0)
-      jekyll-sitemap (= 1.2.0)
-      jekyll-swiss (= 0.4.0)
-      jekyll-theme-architect (= 0.1.1)
-      jekyll-theme-cayman (= 0.1.1)
-      jekyll-theme-dinky (= 0.1.1)
-      jekyll-theme-hacker (= 0.1.1)
-      jekyll-theme-leap-day (= 0.1.1)
-      jekyll-theme-merlot (= 0.1.1)
-      jekyll-theme-midnight (= 0.1.1)
-      jekyll-theme-minimal (= 0.1.1)
-      jekyll-theme-modernist (= 0.1.1)
-      jekyll-theme-primer (= 0.5.3)
-      jekyll-theme-slate (= 0.1.1)
-      jekyll-theme-tactile (= 0.1.1)
-      jekyll-theme-time-machine (= 0.1.1)
-      jekyll-titles-from-headings (= 0.5.1)
-      jemoji (= 0.10.2)
-      kramdown (= 1.17.0)
-      liquid (= 4.0.0)
-      listen (= 3.1.5)
-      mercenary (~> 0.3)
-      minima (= 2.5.0)
-      nokogiri (>= 1.8.5, < 2.0)
-      rouge (= 2.2.1)
-      terminal-table (~> 1.4)
-    github-pages-health-check (1.16.1)
-      addressable (~> 2.3)
-      dnsruby (~> 1.60)
-      octokit (~> 4.0)
-      public_suffix (~> 3.0)
-      typhoeus (~> 1.3)
-    html-pipeline (2.12.3)
-      activesupport (>= 2)
-      nokogiri (>= 1.4)
-    http_parser.rb (0.6.0)
-    i18n (0.9.5)
       concurrent-ruby (~> 1.0)
-    jekyll (3.7.4)
+    jekyll (4.3.4)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
-      i18n (~> 0.7)
+      i18n (~> 1.0)
-      jekyll-sass-converter (~> 1.0)
+      jekyll-sass-converter (>= 2.0, < 4.0)
       jekyll-watch (~> 2.0)
-      kramdown (~> 1.14)
+      kramdown (~> 2.3, >= 2.3.1)
+      kramdown-parser-gfm (~> 1.0)
       liquid (~> 4.0)
-      mercenary (~> 0.3.3)
+      mercenary (>= 0.3.6, < 0.5)
       pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
+      rouge (>= 3.0, < 5.0)
       safe_yaml (~> 1.0)
-    jekyll-avatar (0.6.0)
+      terminal-table (>= 1.8, < 4.0)
-      jekyll (~> 3.0)
+      webrick (~> 1.7)
-    jekyll-coffeescript (1.1.1)
-      coffee-script (~> 2.2)
-      coffee-script-source (~> 1.11.1)
-    jekyll-commonmark (1.3.1)
-      commonmarker (~> 0.14)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-commonmark-ghpages (0.1.5)
-      commonmarker (~> 0.17.6)
-      jekyll-commonmark (~> 1)
-      rouge (~> 2)
-    jekyll-default-layout (0.1.4)
-      jekyll (~> 3.0)
-    jekyll-feed (0.11.0)
-      jekyll (~> 3.3)
-    jekyll-gist (1.5.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.12.1)
-      jekyll (~> 3.4)
-      octokit (~> 4.0, != 4.4.0)
-    jekyll-mentions (1.4.1)
-      html-pipeline (~> 2.3)
-      jekyll (~> 3.0)
-    jekyll-optional-front-matter (0.3.0)
-      jekyll (~> 3.0)
     jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.2.0)
+    jekyll-sass-converter (3.0.0)
-      jekyll (~> 3.0)
+      sass-embedded (~> 1.54)
-    jekyll-redirect-from (0.14.0)
+    jekyll-sitemap (1.4.0)
-      jekyll (~> 3.3)
+      jekyll (>= 3.7, < 5.0)
-    jekyll-relative-links (0.6.0)
-      jekyll (~> 3.3)
-    jekyll-remote-theme (0.3.1)
-      jekyll (~> 3.5)
-      rubyzip (>= 1.2.1, < 3.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.5.0)
-      jekyll (~> 3.3)
-    jekyll-sitemap (1.2.0)
-      jekyll (~> 3.3)
-    jekyll-swiss (0.4.0)
-    jekyll-theme-architect (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.5.3)
-      jekyll (~> 3.5)
-      jekyll-github-metadata (~> 2.9)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.1.1)
-      jekyll (~> 3.5)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.1)
-      jekyll (~> 3.3)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    jemoji (0.10.2)
+    kramdown (2.5.1)
-      gemoji (~> 3.0)
+      rexml (>= 3.3.9)
-      html-pipeline (~> 2.2)
+    kramdown-parser-gfm (1.1.0)
-      jekyll (~> 3.0)
+      kramdown (~> 2.0)
-    kramdown (1.17.0)
+    liquid (4.0.4)
-    liquid (4.0.0)
+    listen (3.9.0)
-    listen (3.1.5)
+      rb-fsevent (~> 0.10, >= 0.10.3)
-      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.10)
-      rb-inotify (~> 0.9, >= 0.9.7)
+    mercenary (0.4.0)
-      ruby_dep (~> 1.2)
-    mercenary (0.3.6)
-    mini_portile2 (2.4.0)
-    minima (2.5.0)
-      jekyll (~> 3.5)
-      jekyll-feed (~> 0.9)
-      jekyll-seo-tag (~> 2.1)
-    minitest (5.14.0)
-    multipart-post (2.1.1)
-    nokogiri (1.10.9)
-      mini_portile2 (~> 2.4.0)
-    octokit (4.16.0)
-      faraday (>= 0.9)
-      sawyer (~> 0.8.0, >= 0.5.3)
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    public_suffix (3.1.1)
+    public_suffix (6.0.1)
-    rb-fsevent (0.10.3)
+    rake (12.3.3)
-    rb-inotify (0.10.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rouge (2.2.1)
+    rexml (3.3.9)
-    ruby-enum (0.7.2)
+    rouge (4.5.1)
-      i18n
-    ruby_dep (1.5.0)
-    rubyzip (2.2.0)
     safe_yaml (1.0.5)
-    sass (3.7.4)
+    sass-embedded (1.77.5-aarch64-linux-android)
-      sass-listen (~> 4.0.0)
+      google-protobuf (>= 3.25, < 5.0)
-    sass-listen (4.0.0)
+    sass-embedded (1.77.5-aarch64-linux-gnu)
-      rb-fsevent (~> 0.9, >= 0.9.4)
+      google-protobuf (>= 3.25, < 5.0)
-      rb-inotify (~> 0.9, >= 0.9.7)
+    sass-embedded (1.77.5-aarch64-linux-musl)
-    sawyer (0.8.2)
+      google-protobuf (>= 3.25, < 5.0)
-      addressable (>= 2.3.5)
+    sass-embedded (1.77.5-aarch64-mingw-ucrt)
-      faraday (> 0.8, < 2.0)
+      google-protobuf (>= 3.25, < 5.0)
-    terminal-table (1.8.0)
+    sass-embedded (1.77.5-arm-linux-androideabi)
-      unicode-display_width (~> 1.1, >= 1.1.1)
+      google-protobuf (>= 3.25, < 5.0)
-    thread_safe (0.3.6)
+    sass-embedded (1.77.5-arm-linux-gnueabihf)
-    typhoeus (1.3.1)
+      google-protobuf (>= 3.25, < 5.0)
-      ethon (>= 0.9.0)
+    sass-embedded (1.77.5-arm-linux-musleabihf)
-    tzinfo (1.2.6)
+      google-protobuf (>= 3.25, < 5.0)
-      thread_safe (~> 0.1)
+    sass-embedded (1.77.5-arm64-darwin)
-    unicode-display_width (1.6.1)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-riscv64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86-mingw-ucrt)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-cygwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-darwin)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-android)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-gnu)
+      google-protobuf (>= 3.25, < 5.0)
+    sass-embedded (1.77.5-x86_64-linux-musl)
+      google-protobuf (>= 3.25, < 5.0)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    thor (1.3.2)
+    unicode-display_width (2.6.0)
+    webrick (1.9.1)
 
 PLATFORMS
-  ruby
+  aarch64-linux
+  aarch64-linux-android
+  aarch64-linux-gnu
+  aarch64-linux-musl
+  aarch64-mingw-ucrt
+  arm-linux-androideabi
+  arm-linux-gnu
+  arm-linux-gnueabihf
+  arm-linux-musl
+  arm-linux-musleabihf
+  arm64-darwin
+  riscv64-linux-android
+  riscv64-linux-gnu
+  riscv64-linux-musl
+  x86-cygwin
+  x86-linux
+  x86-linux-android
+  x86-linux-gnu
+  x86-linux-musl
+  x86-mingw-ucrt
+  x86_64-cygwin
+  x86_64-darwin
+  x86_64-linux-android
+  x86_64-linux-gnu
+  x86_64-linux-musl
 
 DEPENDENCIES
-  github-pages (= 197)
+  appraisal (~> 2.5)
-  jekyll
+  beautiful-jekyll-theme!
-  jekyll-paginate
+  bundler (>= 1.16)
+  rake (~> 12.0)
 
 BUNDLED WITH
-   2.0.2
+   2.5.22

landing.bryanroessler.com/LICENSE

@@ -1,6 +1,6 @@
-The MIT License (MIT)
+MIT License
 
-Copyright (c) 2015-2018 Dean Attali
+Copyright (c) 2023 Dean Attali
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -19,12 +19,3 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
-
-
-
-staticman integration
-=================================================================================
-
-The MIT License (MIT)
-
-Copyright (c) 2013-2018 Michael Rose

landing.bryanroessler.com/README.md

@@ -1,85 +1,121 @@
 # Beautiful Jekyll
 
-[![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://www.paypal.me/daattali/20)
 [![Gem Version](https://badge.fury.io/rb/beautiful-jekyll-theme.svg)](https://badge.fury.io/rb/beautiful-jekyll-theme)
 
-> *Copyright 2019 [Dean Attali](https://deanattali.com)*
+> By [Dean Attali](https://deanattali.com) · [Demo](https://beautifuljekyll.com/)
 
-**Beautiful Jekyll** is a ready-to-use template to help you create an awesome website quickly. Perfect for personal sites, blogs, or simple project websites.  [Check out a demo](https://deanattali.com/beautiful-jekyll) of what you'll get after just two minutes.  You can also look at [my personal website](https://deanattali.com) to see it in use, or see examples of websites other people created using this theme [here](#showcased-users-success-stories).
+**Beautiful Jekyll** is a ready-to-use template to help you create a beautiful website quickly. Perfect for personal sites, blogs, or simple project websites.  [Check out a demo](https://beautifuljekyll.com) of what you'll get after just two minutes.  You can also look at [my personal website](https://deanattali.com) or [my consulting website](https://attalitech.com) to see it in use, or see [examples of websites](http://beautifuljekyll.com/examples) other people created using this theme.
 
-**If you enjoy this theme, please consider [supporting me](https://www.paypal.me/daattali/20) for developing and maintaining this template.**
+**If you enjoy Beautiful Jekyll, please consider [supporting me](https://github.com/sponsors/daattali). You'll also gain access to office hours and more features! ❤**
 
-<p align="center">
+## Table of contents
-  <a href="https://www.paypal.me/daattali">
-    <img src="https://www.paypalobjects.com/en_US/i/btn/btn_donate_LG.gif" />
-  </a>
-</p>
 
-### Table of contents
-
-- [Prerequisites](#prerequisites)
-- [Build your website in 3 steps](#build-your-website-in-3-steps)
-- [Add your own content](#add-your-own-content)
-- [Last important thing: YAML front matter ("parameters" for a page)](#last-important-thing-yaml-front-matter-parameters-for-a-page)
 - [Features](#features)
-- [Creating a User Page vs a Project Page](#creating-a-user-page-vs-a-project-page)
+- [Sponsors 🏆](#sponsors)
-- [Showcased users (success stories!)](#showcased-users-success-stories)
+- [**Build your website in 3 steps**](#build-your-website-in-3-steps)
-- [Advanced: local development](#advanced-local-development-using-docker)
+- [Plans](#plans)
-- [FAQ and support](#faq-and-support)
+- [Add your own content](#add-your-own-content)
-- [Credits and contributions](#credits)
+- [Customizing parameters for each page](#customizing-parameters-for-each-page)
+- [Supported parameters](#supported-parameters)
+- [Featured users (success stories!)](#featured-users-success-stories)
+- [Next steps](#next-steps)
+- [Getting help](#getting-help)
+- [Credits and contributions](#contributions)
 
-## Prerequisites
+# Features
 
-- You need to have a GitHub account. If you don't have one, [sign up here](https://github.com/join) - it takes one minute. This is where your website will live - if you sign up with username `johnsmith` then your website will be `https://johnsmith.github.io`.
+__Check out [*What's New?*](https://beautifuljekyll.com/updates/) to see the latest features!__
-- It would be helpful to understand what Markdown is and how to write it. Markdown is just a way to take a piece of text and format it to look a little nicer.  For example, this whole instruction set that you're reading is written in markdown - it's just text with some words being bold/larger/italicized/etc. I recommend taking 5 minutes to learn markdown [with this amazingly easy yet useful tutorial](https://markdowntutorial.com/).
 
-## Build your website in 3 steps
+- **SIMPLE**: The primary goal of Beautiful Jekyll is to allow literally *anyone* to create a website in a few minutes.
+- **Modern**: Uses the latest best practices and technologies to achieve nearly perfect scores on Google Chrome's Audit.
+- **Mobile-first**: Designed to look great on both large-screen and small-screen (mobile) devices.
+- **Highly customizable**: Many personalization settings such as changing the background colour/image, adding a logo.
+- **Flexible usage**: Use Beautiful Jekyll directly on GitHub or via a Ruby gem - choose the best [development method](#build-your-website-in-3-steps) for you.
+- **Battle-tested**: By using Beautiful Jekyll, you'll be joining 50,000+ users enjoying this theme since 2015.
+- **SEO and social media support**: Customize how your site looks on Google and when shared on social media.
+- **Comments support**: Add comments to any page using either [Disqus](https://disqus.com/), [Facebook comments](https://developers.facebook.com/docs/plugins/comments), [Utterances](https://utteranc.es/), [Staticman](https://staticman.net), [giscus](https://giscus.app), or [CommentBox](https://commentbox.io/).
+- **Tags**: Any blog post can be tagged with keywords, and an index page is automatically generated.
+- **Analytics**: Easily integrate Google Analytics, or other analytics platforms, to track visits to your website.
+- **Search**: Let users easily find any page using a Search button in the navigation bar.
+- **Photos support**: Any page can have a full-width cover photo and thumbnail.
+- **RSS**: An RSS feed is automatically created, so you can even host a podcast easily with Beautiful Jekyll.
+
+<h2 id="sponsors">Sponsors 🏆</h2>
+
+Developing and maintaining Beautiful Jekyll takes a lot of time and effort - thank you to anyone who helps fund this effort!
+
+- [DoFollow](https://dofollow.co.uk/)
+- [Varna Sri Raman](https://about.me/varna)
+
+**[Become a sponsor for Beautiful Jekyll and unlock new features\!](https://github.com/sponsors/daattali/sponsorships?tier_id=39856)**
+
+# Build your website in 3 steps
+
+There are a few different ways to build a website using Beautiful Jekyll, and this document will go through the simplest one: using a fork on GitHub. For most people (including myself!), this easy method is the recommended one.
+
+Even if you choose to use one of the [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard), I still suggest you read through the easy method first.
+
+## The easy way (recommended!)
 
 Getting started is *literally* as easy as 1-2-3 :smile:
-Scroll down to see the steps involved, but here is a 40-second video just as a reference as you work through the steps.
 
-![Installation steps](img/install-steps.gif)
+Scroll down to see the steps involved, but here is a 30-second video just as a reference as you work through the steps. If you don't already have a [GitHub account](https://github.com), you'll need to sign up.
 
-### 1. Fork this repository
+![Installation steps](https://beautifuljekyll.com/assets/img/install-steps.gif)
 
-(Assuming you are on this page and logged into GitHub) Fork this repository by clicking the *Fork* button on the top right corner. Forking means that you now copied this whole project and all the files into your account.
+### 1. Fork this project
 
-### 2. Rename the repository to `<yourusername>.github.io`
+Click on the __*Fork*__ button at the top right corner of this page. Forking means that you're copying this entire project and all its files into your account. Do not click on the __*Create fork*__ button on the next page yet.
 
-This will create a GitHub User page ready with the **Beautiful Jekyll** template that will be available at `https://<yourusername>.github.io` within a couple minutes.  To do this, click on *Settings* at the top (the cog icon) and there you'll have an option to rename.
+### 2. Rename the repository to `YOURUSERNAME.github.io`
+
+You'll see the word "repository" used a lot in GitHub - it simply means "project". Under __*Repository name*__ you should see the name `beautiful-jekyll`, this is where you need to rename your project to `YOURUSERNAME.github.io` (replace `YOURUSERNAME` with your GitHub user name). It's important to use this exact name so that GitHub will recognize it and automatically create a website for this project.   
+
+> Tip: If you want to use a different URL for your website, check out the [FAQ](https://beautifuljekyll.com/faq/#custom-domain)
  
 ### 3. Customize your website settings
 
-Edit the `_config.yml` file to change all the settings to reflect your site. To edit the file, click on it and then click on the pencil icon (watch the video tutorial above if you're confused).  The settings in the file are fairly self-explanatory and I added comments inside the file to help you further. Any line that begins with a pound sign (`#`) is a comment, and the rest of the lines are actual settings.
+Edit the `_config.yml` file to change any settings you want. To edit the file, first click on it to view the file, and on the next page click on the pencil icon to edit it (watch the video tutorial above if you're confused).  The settings in the file are self-explanatory and there are comments inside the file to help you understand what each setting does. Any line that begins with a hashtag (`#`) is a comment, and the other lines are actual settings. After changing the settings, click the green __*Commit changes*__ button to save these edits.
 
-Another way to edit the config file (or any other file) is to use [prose.io](https://prose.io/), which is just a simple interface to allow you to more intuitively edit files or add new files to your project.
+> Note: In the video above, only one setting in the `_config.yml` file is edited, but you should go through the rest of the settings as well.
 
-After you save your changes to the config file (by clicking on *Commit changes* as the video tutorial shows), your website should be ready in a minute or two at `https://<yourusername>.github.io`. Every time you make a change to any file, your website will get rebuilt and should be updated in about a minute or so.
+### 4. Congratulations! You have a website!
 
-You can now visit your shiny new website, which will be seeded with several sample blog posts and a couple other pages. Your website is at `https://<yourusername>.github.io` (replace `<yourusername>` with your user name). Do not add `www` to the URL - it will not work!
+If you named your project correctly and made an edit to the config file, your website should be ready in a minute or two at `https://YOURUSERNAME.github.io`. Every time you make a change to any file, your website will get rebuilt and should be updated in about a minute or so. Your website will be initialized with several sample blog posts and a couple other pages.
 
-**Note:** The video above goes through the setup for a user with username `daattalitest`. I only edited one setting in the `_config.yml` file in the video, but **you should actually go through the rest of the settings as well. Don't be lazy, go through all the settings :)**
+## The harder way (for advanced users)
 
-## Add your own content
+The instructions above explain how to use Beautiful Jekyll in the easiest way: by forking on GitHub. There are more [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard) that include either using GitHub Pages with remote themes, or using Ruby gems. They provide you with more control, but are only intended for advanced users.
 
-To add pages to your site, you can either write a markdown file (`.md`) or you can write an HTML file directly.  It is much easier to write markdown than HTML, so I suggest you do that (use the [tutorial I mentioned above](https://markdowntutorial.com/) if you need to learn markdown). You can look at some files on this site to get an idea of how to write markdown. To look at existing files, click on any file that ends in `.md`, for example [`aboutme.md`](./aboutme.md). On the next page you can see some nicely formatted text (there is a word in bold, a link, bullet points), and if you click on the pencil icon to edit the file, you will see the markdown that generated the pretty text. Very easy!
+> Note: Beautiful Jekyll was primarily designed to be used as a GitHub theme, so you will not get any support if you use this theme via Ruby gems. 
 
-In contrast, look at [`index.html`](./index.html). That's how your write HTML - not as pretty. So stick with markdown if you don't know HTML.
+# Plans
 
-Any file that you add inside the [`_posts`](./_posts) directory will be treated as a blog entry.  You can look at the existing files there to get an idea of how to write blog posts.  After you successfully add your own post, you can delete the existing files inside [`_posts`](./_posts) to remove the sample posts, as those are just demo posts to help you learn.
+Beautiful Jekyll is, and always will be, free. But if you want to remove the Beautiful Jekyll ad from your website, use a Dark Mode skin, access office hours, or simply support the development efforts, [check out the different plans](https://beautifuljekyll.com/plans).
 
-As mentioned previously, you can use [prose.io](https://prose.io/) to add or edit files instead of doing it directly on GitHub, it can be a little easier that way.
+# Add your own content
 
-## Last important thing: YAML front matter ("parameters" for a page)
+To add pages to your site, you can either write a markdown file (`.md`) or you can write an HTML file. It's much easier to write markdown than HTML, so that's the recommended approach ([here's a great tutorial](https://markdowntutorial.com/) if you need to learn markdown in 5 minutes).
+
+To see an example of a markdown file, click on any file that ends in `.md`, for example [`aboutme.md`](./aboutme.md). On that page you can see some nicely formatted text (there's a word in bold, a link, a few bullet points), and if you click on the pencil icon to edit the file, you'll see the markdown code that generated the pretty text. Very easy! 
+
+In contrast, look at [`tags.html`](./tags.html). That's how your write HTML - not as pretty. So stick with markdown if you don't know HTML.
+
+Any markdown or HTML file that you create will be available on your website under `https://<yourusername>.github.io/<pagename>`. For example, if you create a file `about.md` (or `about.html`) then it'll exist at `https://<yourusername>.github.io/about`.
+
+Files you create inside the [`_posts`](./_posts) directory will be treated as blog entries. You can look at the existing files there to get an idea of how to write blog posts. Note the format of the blog post files - they must follow the naming convention of `YEAR-MONTH-DAY-title.md`. After you successfully add your own post, you can delete the existing files inside [`_posts`](./_posts) to remove the sample posts, as those are just demo posts to help you learn.
+
+# Customizing parameters for each page
+
+**One last important thing**: In order to have your new pages use this template and not just be plain HTML pages, **you must add [YAML front matter](https://jekyllrb.com/docs/front-matter/) to the top of each page**:
 
-In order to have your new pages use this template and not just be plain pages, you need to add [YAML front matter](https://jekyllrb.com/docs/front-matter/) to the top of each page. This is where you'll give each page some parameters that I made available, such as a title and subtitle. I'll go into more detail about what parameters are available later. If you don't want to use any parameters on your new page (this also means having no title), then use the empty YAML front matter:
 
 ```
 ---
 ---
 ```
 
-If you want to use any parameters, write them between the two lines. For example, you can have this at the top of a page:
+This is where you'll be able to give each page some extra parameters (such as a title, a subtitle, an image, etc - [below is a list of all parameters](#supported-parameters)). Add any parameters you want between these two dashed lines, for example:
 
 ```
 ---
@@ -88,238 +124,116 @@ subtitle: Here you'll find all the ways to get in touch with me
 ---
 ```
 
-You can look at the top of [`aboutme.md`](./aboutme.md) or [`index.html`](./index.html) as more examples.
+If you don't want to use any parameters on a page, you still need to use the two dashed lines. If you don't, then your file will be shown as-is without the Beautiful Jekyll template.
 
-**Important takeaway: ALWAYS add the YAML front matter, which is two lines with three dashes, to EVERY page. If you have any parameters, they go between the two lines.**    
+You can look at the top of [`aboutme.md`](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/aboutme.md) as an example.
-If you don't include YAML then your file will not use the template.
 
-## Features
+**Important takeaway: ALWAYS add the YAML front matter, which is two lines of three dashes, to EVERY page. If you have any parameters, they go between the two lines.**
 
-### Mobile-first
+# Supported parameters
-**Beautiful Jekyll** is designed to look great on both large-screen and small-screen (mobile) devices. Load up your site on your phone or your gigantic iMac, and the site will work well on both, though it will look slightly different.
 
-### Customizable
+Below is a list of the parameters that Beautiful Jekyll supports (any of these can be added to the YAML front matter of any page). Remember to also look in the `_config.yml` file to see additional site-wide settings. If there's a parameter that you want to apply to the entire site instead of one specific page, check out [this FAQ answer](https://beautifuljekyll.com/faq/#default-params).
 
-Many personalization settings in `_config.yml`, such as setting your name and site's description, changing the background colour/image, setting your avatar to add a little image in the navigation bar, customizing the links in the menus, customizing what social media links to show in the footer, etc.
+## Main parameters
 
-### Allowing users to leave comments
+These are the basic YAML parameters that you are most likely to use on most pages.
-
-If you want to enable comments on your site, Beautiful Jekyll supports either the [Disqus](https://disqus.com/) comments plugin, [Facebook](https://developers.facebook.com/docs/plugins/comments) comments, [Staticman](https://staticman.net) or [JustComments](https://just-comments.com). If any of these are set in the configuration file, then all blog posts will have comments turned on by default. To turn off comments on a particular blog post, add `comments: false` to the YAML front matter. If you want to add comments on the bottom of a non-blog page, add `comments: true` to the YAML front matter.
-
-#### Disqus comments
-
-To use Disqus, simply sign up to [Disqus](https://disqus.com/) and add your Disqus shortname to the `disqus` parameter in the `_config.yml` file.
-
-#### Facebook comments
-
-To use Facebook comments, create a Facebook app using [Facebook developers](https://developers.facebook.com/docs/apps/register), and add the Facebook App ID to the `fb_comment_id` parameter in `_config.yml`.
-
-#### Staticman comments
-
-To use Staticman, you first need to invite `staticmanlab` as a collaborator to your repository (by going to your repository **Settings** page, navigate to the **Collaborators** tab, and add the username `staticmanlab`), and then accept the invitation by going to `https://staticman3.herokuapp.com/v3/connect/github/<username>/<repo-name>`. Lastly, fill in the `staticman` parameters in the Staticman section of `_config.yml`. You may also choose a different Staticman instance other than `staticmanlab`.
-
-Optional: You may want to configure a webhook to prevent old inactive branches (representing approved comments) from stacking up.  You can refer to [Staticman's documentation](https://staticman.net/docs/webhooks) for details.  Make sure to input the **Payload URL** according to your chosen `endpoint`.  For example, the default `endpoint` is `https://staticman3.herokuapp.com/v3/entry/github/`, so the corresponding **Payload URL** should be `https://staticman3.herokuapp.com/v1/webhook`.
-
-#### JustComments
-
-To use JustComments you first need to have an account. After you just need to copy the API key to the `just-comments` property in `_config.yml` file.
-
-### Adding Google Analytics to track page views
-
-Beautiful Jekyll lets you easily add Google Analytics to all your pages. This will let you track all sorts of information about visits to your website, such as how many times each page is viewed and where (geographically) your users come from.  To add Google Analytics, simply sign up to [Google Analytics](https://www.google.com/analytics/) to obtain your Google Tracking ID, and add this tracking ID to the `google_analytics` parameter in `_config.yml`.
-
-### Sharing blog posts on social media
-
-By default, all blog posts will have buttons at the bottom of the post to allow people to share the current page on Twitter/Facebook/LinkedIn.  You can choose to enable/disable specific social media websites in the `_config.yml` file. You can also turn off the social media buttons on specific blog posts using `social-share: false` in the YAML front matter.
-
-### RSS feed
-
-Beautiful Jekyll automatically generates a simple RSS feed of your blog posts, to allow others to subscribe to your posts.  If you want to add a link to your RSS feed in the footer of every page, find the `rss: false` line in `_config.yml` and change it to `rss: true`.
-
-### Page types
-
-- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
-- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
-- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
-- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
-
-### YAML front matter parameters
-
-These are the main parameters you can place inside a page's YAML front matter that **Beautiful Jekyll** supports.
 
 Parameter   | Description
 ----------- | -----------
 title       | Page or blog post title
 subtitle    | Short description of page or blog post that goes under the title
-tags        | List of tags to categorize the post. Separate the tags with commas and place them inside square brackets. Example: `[personal, self help, finance]`
+tags        | List of tags to categorize the post. Separate the tags with commas and place them inside square brackets. Example: `[personal, analysis, finance]`
-bigimg      | Include a large full-width image at the top of the page.  You can either give the path to a single image, or provide a list of images to cycle through (see [my personal website](https://deanattali.com/) as an example).
+cover-img   | Include a large full-width image at the top of the page. You can either provide the path to a single image (eg. `"/path/to/img"`) , or a list of images to cycle through (eg. `["/path/img1", "/path/img2"]`). If you want to add a caption to an image, then you must use the list notation (use `[]` even if you have only one image), and each image should be provided as `"/path/to/img" : "Caption of image"`.
-comments    | If you want do add comments to a specific page, use `comments: true`. Comments are automatically enabled on blog posts; to turn comments off for a specific post, use `comments: false`. Comments only work if you enable at least one provider(diqus, staticman, just-comments) in `_config.yml` file.
+thumbnail-img | For blog posts, if you want to add a thumbnail that will show up in the feed, use `thumbnail-img: /path/to/image`. If no thumbnail is provided, then `cover-img` will be used as the thumbnail. You can use `thumbnail-img: ""` to disable a thumbnail.
-show-avatar | If you have an avatar configured in the `_config.yml` but you want to turn it off on a specific page, use `show-avatar: false`. If you want to turn it off by default, locate the line `show-avatar: true` in the file `_config.yml` and change the `true` to `false`; then you can selectively turn it on in specific pages using `show-avatar: true`.
+comments    | If you want do add comments to a specific page, use `comments: true`. Comments only work if you enable one of the comments providers (Facebook, disqus, staticman, utterances, giscus, CommentBox) in `_config.yml` file. Comments are automatically enabled on blog posts but not on other pages; to turn comments off for a specific post, use `comments: false`.
-image       | If you want to add a personalized image to your blog post that will show up next to the post's excerpt and on the post itself, use `image: /path/to/img`.
+mathjax     | If you want to use LaTeX formulas, you need to enable MathJax. Note that in MathJax you need to use `$$` and `\\(` to start and end expressions
-share-img   | If you want to specify an image to use when sharing the page on Facebook or Twitter, then provide the image's full URL here.
+
-social-share | If you don't want to show buttons to share a blog post on social media, use `social-share: false` (this feature is turned on by default).
+## Parameters for SEO and social media sharing
-use-site-title | If you want to use the site title rather than page title as HTML document title (ie. browser tab title), use `use-site-title: true`. When set, the document title will take the format `Site Title - Site Description` (eg. `My website - A virtual proof that name is awesome!`). By default, it will use `Page Title` if it exists, or `Site Title` otherwise.
+
-layout      | What type of page this is (default is `post` for blog posts and `page` for other pages. You can use `minimal` if you don't want a header and footer)
+These parameters let you control what information shows up when a page is shown in a search engine (such as Google) or gets shared on social media (such as Twitter/Facebook).
-js          | List of local JavaScript files to include in the page (eg. `/js/mypage.js`)
+
+Parameter   | Description
+----------- | -----------
+share-title | A title for the page. If not provided, then `title` will be used, and if that's missing then the site title (from `_config.yml`) is used.
+share-description | A brief description of the page. If not provided, then `subtitle` will be used, and if that's missing then an excerpt from the page content is used.
+share-img   | The image to show. If not provided, then `cover-img` or `thumbnail-img` will be used if one of them is provided.
+
+## Less commonly used parameters
+
+These are parameters that you may not use often, but can come in handy sometimes.
+
+Parameter   | Description
+----------- | -----------
+author      | Specify the author of a blog post (useful if a website has multiple authors).
+readtime    | If you want a post to show how many minutes it will take to read it, use `readtime: true`.
+show-avatar | If you have an avatar configured in the `_config.yml` but you want to turn it off on a specific page, use `show-avatar: false`.
+social-share | By default, every blog post has buttons to share the page on social media. If you want to turn this feature off, use `social-share: false`.
+nav-short   | By default, the navigation bar gets shorter after scrolling down the page. If you want the navigation bar to always be short on a certain page, use `nav-short: true`
+gh-repo   | If you want to show GitHub buttons at the top of a post, this sets the GitHub repo name (eg. `daattali/beautiful-jekyll`). You must also use the `gh-badge` parameter to specify what buttons to show.
+gh-badge  | Select which GitHub buttons to display. Available options are: [star, watch, fork, follow]. You must also use the `gh-repo` parameter to specify the GitHub repo.
+last-updated | If you want to show that a blog post was updated after it was originally released, you can specify an "Updated on" date.
+layout      | What type of page this is (default is `post` for blog posts and `page` for other pages). See _Page types_ section below for more information.
+
+## Advanced parameters
+
+These are advanced parameters that are only useful for people who need very fine control over their website.
+
+Parameter   | Description
+----------- | -----------
+footer-extra | If you want to include extra content below the social media icons in the footer, create an HTML file in the `_includes/` folder (for example `_includes/myinfo.html`) and set `footer-extra` to the name of the file (for example `footer-extra: myinfo.html`). Accepts a single file or a list of files.
+before-content | Similar to `footer-extra`, but used for including HTML before the main content of the page (below the title).
+after-content | Similar to `footer-extra`, but used for including HTML after the main content of the page (above the footer).
+head-extra   | Similar to `footer-extra`, but used if you have any HTML code that needs to be included in the `<head>` tag of the page.
+language    | HTML language code to be set on the page's &lt;html&gt; element.
+full-width  | By default, page content is constrained to a standard width. Use `full-width: true` to allow the content to span the entire width of the window.
+js          | List of local JavaScript files to include in the page (eg. `/assets/js/mypage.js`)
 ext-js      | List of external JavaScript files to include in the page (eg. `//cdnjs.cloudflare.com/ajax/libs/underscore.js/1.8.2/underscore-min.js`). External JavaScript files that support [Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) can be specified using the `href` and `sri` parameters eg.<br/>`href: "//code.jquery.com/jquery-3.1.1.min.js"`<br/>`sri: "sha256-hVVnYaiADRTO2PzUGmuLJr8BLUSjGIZsDYGmIJLv2b8="`
 css         | List of local CSS files to include in the page
 ext-css      | List of external CSS files to include in the page. External CSS files using SRI (see `ext-js` parameter) are also supported.
-googlefonts | List of Google fonts to include in the page (eg. `["Monoton", "Lobster"]`)
-gh-repo   | If you want to show GitHub buttons at the top of a post, this sets the GitHub repo name (eg. `daattali/beautiful-jekyll`). You must also use the `gh-badge` parameter to specify what buttons to show.
-gh-badge  | Select which GitHub buttons to display, available options are: [star, watch, fork, follow]. You must also use the `gh-repo` parameter to specify the GitHub repo.
 
-### Advanced features (including how to use a custom URL address for your site)
+## Page types
 
-I wrote [a blog post](https://deanattali.com/2015/03/12/beautiful-jekyll-how-to-build-a-site-in-minutes/) describing some more advanced features that I used in my website that are applicable to any Jekyll site.  It describes how I used a custom URL for my site (deanattali.com instead of daattali.github.io), how to add a Google-powered search into your site, and provides a few more details about having an RSS feed.
+- **post** - To write a blog post, add a markdown or HTML file in the `_posts` folder. As long as you give it YAML front matter (the two lines of three dashes), it will automatically be rendered like a blog post. Look at the existing blog post files to see examples of how to use YAML parameters in blog posts.
+- **page** - Any page outside the `_posts` folder that uses YAML front matter will have a very similar style to blog posts.
+- **home** - The home layout is meant to act as the homepage of your blog posts - it will display all your blog posts, sorted from newest to oldest. A file using the `home` layout must be named `index.html` (not `index.md` or anything else!).
+- **minimal** - If you want to create a page with minimal styling (ie. without the bulky navigation bar and footer), assign `layout: minimal` to the YAML front matter.
+- If you want to completely bypass the template engine and just write your own HTML page, simply omit the YAML front matter. Only do this if you know how to write HTML!
 
-## Creating a User Page vs a Project Page
+# Featured users (success stories!)
 
-If you're not sure what the difference is, you can probably safely ignore this section.
+Visit the [Official website](http://beautifuljekyll.com/examples) to see sample websites using Beautiful Jekyll.
 
-If you want to use this theme to host a website that will be available at `https://YOURUSERNAME.github.io`, then you do not need to read this section. That is called a User Page, you can only have one User Page in your GitHub account, and it is what you get by default when forking this project.
+If you'd like to showcase yourself and join this list, [upgrading to the Individual plan](https://github.com/sponsors/daattali/sponsorships?&tier_id=7362) will give you that publicity plus some other rewards!
 
-If you want to use this theme to create a website for a particular repository, it will be available at `https://YOURUSERNAME.github.io/PROJECTNAME`, and that is called a [Project Page](https://help.github.com/articles/user-organization-and-project-pages/). You can have a Project Page for any repository you have on GitHub.
+# Next steps
 
-**When using this theme for a Project Page, by default your website will be served from the `gh-pages` branch**, so you must take the following steps: 
+Congratulations on making it this far! You now have all the tools to easily build a beautiful website for free. 
 
-1. [Delete the existing `gh-pages` branch](https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)
+- After you get comfortable with the basics of writing in markdown, I suggest taking a look at this [sample post](https://beautifuljekyll.com/2020-02-28-sample-markdown/) and [the code that created it](https://raw.githubusercontent.com/daattali/beautiful-jekyll/master/_posts/2020-02-28-sample-markdown.md) to learn some more advanced tips about markdown.
 
-2. [Create a new branch named `gh-pages` from the `master` branch](https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository#creating-a-branch)
+- I **highly recommend** going over the [*Frequently Asked Questions*](https://beautifuljekyll.com/faq/) to find out answers to questions you may not even know you have. Every few months I suggest checking the [*What's New?*](https://beautifuljekyll.com/updates/) page to see if there are new features, and learn [how to update your site to the newest version](https://beautifuljekyll.com/faq/#updating) when it's time.
 
-Alternatively, instead of the above two steps, you can opt to use the `master` branch instead of `gh-pages` branch as your website's source by choosing that option in the main Settings page. 
+- You can also check out the [advanced installation methods](https://beautifuljekyll.com/getstarted/#install-steps-hard) that give you a little more control but are harder to use. Keep in mind that Beautiful Jekyll was primarily designed to be used as a GitHub theme, so you will not get any support if you choose one of the Ruby installation methods. 
 
-## Showcased users (success stories!)
+- Remember that Beautiful Jekyll is built on top of Jekyll. This means that reading through the [Jekyll documentation](https://jekyllrb.com/) will introduce you to many more features that you might find useful!
 
-To my huge surprise, Beautiful Jekyll has been used in over 500 websites in its first 6 months alone! Here is a hand-picked selection of some websites that use Beautiful Jekyll.
+# Getting help
 
-Want your website featured here? [Contact me](https://deanattali.com/aboutme#contact) to let me know about your website.
+Visit the [FAQ page](https://beautifuljekyll.com/faq) for answers to commonly asked questions.
 
-### Project/company websites
+**If you choose to [become a sponsor](https://beautifuljekyll.com/plans/), you'll have access to my [office hours](https://beautifuljekyll.com/officehours/) where you can ask for help.** You can also use the [Discussions](https://github.com/daattali/beautiful-jekyll/discussions) area to try and get help from the community.
 
-| Website | Description |
+Beautiful Jekyll is used by 50,000+ people with wildly varying degrees of web skills, so it's impossible to answer all the questions that may arise. For any question that's not specifically related to Beautiful Jekyll and is more about Jekyll or web development in general, the answer can often be found on Google, in the [Jekyll documentation](https://jekyllrb.com/), or on the [Jekyll support forum](https://talk.jekyllrb.com/).
-| :------ |:----------- |
-| [repidemicsconsortium.org/](https://www.repidemicsconsortium.org/) | R Epidemics Consortium |
-| [vaccineimpact.org](https://www.vaccineimpact.org/) | Vaccine Impact Modelling Consortium |
-| [derekogle.com/fishR](http://derekogle.com/fishR/) | Using R for Fisheries Analyses |
-| [bigdata.juju.solutions](http://bigdata.juju.solutions) | Creating Big Data solutions Juju Solutions |
-| [joecks.github.io/clipboard-actions](http://joecks.github.io/clipboard-actions/) | Clipboard Actions - an Android app |
-| [deanattali.com/shinyjs](http://deanattali.com/shinyjs/) | shinyjs - an R package |
-| [blabel.github.io](http://blabel.github.io) | Library for canonicalising blank node labels in RDF graphs |
-| [reactionic.github.io](http://reactionic.github.io) | Create iOS and Android apps with React and Ionic |
-| [ja2-stracciatella.github.io](http://ja2-stracciatella.github.io) | Jagged Alliance 2 Stracciatella |
-| [ddocent.com](http://ddocent.com/) | RADSeq Bioinformatics and Beyond |
-| [guitarlessons.org](https://www.guitarlessons.org/) | Free online guitar lessons for all |
-| [terremotocentroitalia.info](https://www.terremotocentroitalia.info/) | Information about the 2016 Italy earthquake |
 
+# Contributions
 
-### Personal websites
+Thank you to [all past contributors](https://github.com/daattali/beautiful-jekyll/graphs/contributors). If you find any problems or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message.
 
-| Website | Who | What |
+You can also contribute by becoming an [official sponsor](https://github.com/sponsors/daattali/sponsorships?tier_id=39856) to help keep Beautiful Jekyll well-maintained!
-| :------ |:--- | :--- |
-| [deanattali.com](https://deanattali.com) | Dean Attali | Creator of Beautiful Jekyll |
-| [ouzor.github.io](http://ouzor.github.io) | Juuso Parkkinen | Data scientist |
-| [derekogle.com](http://derekogle.com/) | Derek Ogle | Professor of Mathematical Sciences and Natural Resources |
-| [melyanna.github.io](http://melyanna.github.io/) | Melyanna | Shows off her nice art |
-| [chauff.github.io](http://chauff.github.io/) | Claudia Hauff | Professor at Delft University of Technology |
-| [kootenpv.github.io](http://kootenpv.github.io/) | Pascal van Kooten | Data analytics |
-| [sjackman.ca](http://sjackman.ca) | Shaun Jackman | PhD candidate in bioinformatics |
-| [anudit.in](http://www.anudit.in/) | Anudit Verma | Engineering student |
-| [sharepointoscar.github.io](http://sharepointoscar.github.io) | Oscar Medina | Independent Hacker |
-| [ocram85.com](https://ocram85.com) | Marco Blessing | A personal blog about PowerShell and automation |
-| [khanna.cc](https://khanna.cc/) | Harry Khanna | Law and software |
 
-## Advanced: Local development using Docker
+# Credits
 
-Beautiful Jekyll is meant to be so simple to use that you can do it all within the browser. However, if you'd like to develop locally on your own machine, that's possible too if you're comfortable with command line. Follow these simple steps set that up with Docker:
+This template was not made *entirely* from scratch. I'd like to give special thanks to [Jekyll Now](https://github.com/barryclark/jekyll-now) and [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from whom I've taken several ideas initially.
-
-1. Make sure you have [Docker](https://www.docker.com/) installed.
-
-2. Clone your repository locally.
-
-    ```bash
-    git clone https://github.com/<your_username>/<your_username>.github.io.git
-    ```
-
-3. Run the following shell commands to build the docker image and start the container for the first time:
-
-    ```bash
-    cd <repository_folder>
-    docker build -t beautiful-jekyll "$PWD"
-    docker run -d -p 4000:4000 --name beautiful-jekyll -v "$PWD":/srv/jekyll beautiful-jekyll
-    ```
-
-
-Now that Docker is set up, you do not need to run the above steps again. You can now view your website at http://localhost:4000/. You can start the container again in the future with:
-
-```bash
-docker start beautiful-jekyll
-```
-
-And you can stop the server with:
-
-```bash
-docker stop beautiful-jekyll
-```
-
-Whenever you make any changes to `_config.yml`, you must stop and re-start the server for the new config settings to take effect.
-
-Disclaimer: I personally am NOT using local development so I don't know much about running Jekyll locally. If you follow this route, please don't ask me questions because unfortunately I honestly won't be able to help!
-
-## FAQ and support
-
-If you need any help, I suggest heading over to the [Jekyll support forum](https://talk.jekyllrb.com/).
-
-Beautiful Jekyll is actively used by thousands of people with wildly varying degrees of competency, so it's impossible to answer all the questions that may arise. Below are answers to a few very common questions. Most questions that I get asked are not directly related to this theme, and instead are more general questions about Jekyll or web development. Many such questions can be answered by reading the [Jekyll documentation](https://jekyllrb.com/) or with Google.
-
-#### How do I change the number of posts per page OR the colour of the navigation bar OR the image in the navigation bar OR ...?
-
-Beautiful Jekyll is built to be very customizable, and as such, many questions about "how do I change ..." can be answered by looking at the `_config.yml` file. The configuration file has many adjustable parameters to customize your site.
-
-#### How do I add a favicon to my site?
-
-Easy! Just place a valid `favicon.ico` (or another valid favicon image) in the root directory of your project. And then wait! It can take a while to update.
-
-#### How do I move the blog to another page instead of having it on the home page?
-
-The default style of Beautiful Jekyll is to feature the blog feed on the front page. But for many sites that's not the ideal structure, and you may want to have a separate dedicated page for the blog posts. To have the blog hosted on a different URL (for example at `<mysite.com>/blog`), copy the `index.html` file into a folder with the same name as the desired page (for example, to `blog/index.html`), and in the `_config.yml` file you need to add a parameter `paginate_path: "/<page name>/page:num/"` (for example `paginate_path: "/blog/page:num/"`).
-
-#### What size do you recommend using for the `bigimg` photos?
-
-Unfortunately, this is a no-answer! There isn't a one-size-fits-all solution to this, because every person will view your site on a different browser with different dimensions. Some browsers will have very wide aspect ratio, some will be narrower, some will be vertical (such as phones), different phones have different screens, etc. The image will always be centered, so the only tip I can give is that you should make sure the important part of the image is in the middle so that it'll always show. Other than that, every browser will show a different clipping of the image.
-
-#### How do I use MathJax equations in my posts?
-
-MathJax can be easily integrated into your website with a one-line addition. You can see [this discussion](https://github.com/daattali/beautiful-jekyll/issues/195) for more information.
-
-#### My project page appear to be broken after a recent update!
-
-In June 2019, some URL related settings have been adjusted to be more in-line with how Jekyll uses them officially. Project Page absolute links might appear to be broken if you haven't propagated all necessary changes to your local templates, or if you have created additional templates making use of old settings. If a link contains a duplicated project path component, this is most likely the cause. In summary:
-
-| &nbsp; | Old behavior | New behavior |
-| --- | --- | --- |
-| `url` setting | `https://user.github.io/projectname` | (unset, GitHub auto detects) |
-| `baseurl` setting | `/projectname` | (unset, GitHub auto detects) |
-| Absolute link construction | `{{ site.url }}/your/path` | `{{ '/your/path' \| absolute_url }}` |
-| Relative link construction | `{{ site.baseurl }}/your/path` | `{{ '/your/path' \| relative_url }}` |
-
-## Credits
-
-This template was not made entirely from scratch. I would like to give special thanks to:
-- [Barry Clark](https://github.com/barryclark) and his project [Jekyll Now](https://github.com/barryclark/jekyll-now), from whom I've taken several ideas and code snippets, as well as some documenation tips.
-- [Iron Summit Media](https://github.com/IronSummitMedia) and their project [Bootstrap Clean Blog](https://github.com/IronSummitMedia/startbootstrap-clean-blog), from which I've used some design ideas and some of the templating code for posts and pagination.
 
 I'd also like to thank [Dr. Jekyll's Themes](https://drjekyllthemes.github.io/), [Jekyll Themes](http://jekyllthemes.org/), and another [Jekyll Themes](http://jekyllrc.github.io/jekyllthemes/) for featuring Beautiful Jekyll in their Jekyll theme directories.
 
-## Contributions
-
-If you find anything wrong or would like to contribute in any way, feel free to create a pull request/open an issue/send me a message.  Any comments are welcome!
-
-Thank you to [all contributors](https://github.com/daattali/beautiful-jekyll/graphs/contributors). Special thanks to  [@OCram85](https://github.com/OCram85) and [@abelcheung](https://github.com/abelcheung) for contributing multiple times as well as helping with discussions.
-
-If you do fork or clone this project to use as a template for your site, I would appreciate if you keep the link in the footer to this project.  I've noticed that several people who forked this repo removed the attribution and I would prefer to get the recognition if you do use this :)
-
-## Known limitations
-
-- If you have a project page and you want a custom 404 page, you must have a custom domain.  See https://help.github.com/articles/custom-404-pages/.  This means that if you have a regular User Page you can use the 404 page from this theme, but if it's a website for a specific repository, the 404 page will not be used.
-
-- If there are many navigation bar links and avatar, some of the links may get partially hidden behind the avatar. 

landing.bryanroessler.com/_config.yml

@@ -1,4 +1,13 @@
-# --- General options --- #
+###########################################################
+### Welcome to Beautiful Jekyll!
+### This config file is meant for settings that affect your entire website. When you first
+### set up your website you should go through all these settings and edit them, but after
+### the initial set up you won't need to come back to this file often.
+###########################################################
+
+############################
+# --- Required options --- #
+############################
 
 # url is the full website URL
 # baseurl is the website's URL without the hostname
@@ -7,16 +16,16 @@
 url: "https://bryanroessler.com"
 baseurl: ""
 
-
 # Name of website
 title: Bryan Roessler
 
-# Short description of your site
+# Your name to show in the footer
-description: Ordo ab chao
+author: Bryan Roessler
 
-# --- Navigation bar options --- #
+###############################################
+# --- List of links in the navigation bar --- #
+###############################################
 
-# List of links in the navigation bar
 navbar-links:
   Home: "https://bryanroessler.com"
   Blog: "https://blog.bryanroessler.com"
@@ -26,52 +35,38 @@ navbar-links:
     - Syncthing: "https://syncthing.bryanroessler.com"
     - Panel: "https://panel.bryanroessler.com"
 
-# Image to show in the navigation bar - image must be a square (width = height)
+################
-# Remove this parameter if you don't want an image in the navbar
+# --- Logo --- #
-avatar: "/img/me_square_sepia_small.jpg"
+################
 
-# If you want to have an image logo in the top-left corner instead of the title text,
+# Image to show in the navigation bar - works best with a square image
+# Remove this parameter if you don't want an image in the navbar
+avatar: "/assets/img/me_square_sepia_small.jpg"
+
+# By default, the image is cut into a circle. You can disable this behaviour by setting 'round-avatar: false'
+round-avatar: true
+
+# If you want to have an image logo in the top-left corner instead of having the title of the website,
 # then specify the following parameter
 #title-img: "./img/me_square_sepia_small.jpg"
 
-# --- Background colour/image options --- #
 
-# Personalize the colors in your website. Colour values can be any valid CSS colour
+#####################################
+# --- Footer social media links --- #
+#####################################
 
-navbar-col: "#F5F5F5"
+# Select the social network links that you want to show in the footer.
-navbar-text-col: "#404040"
+# You can change the order that they show up on the page by changing the order here.
-navbar-children-col: "#F5F5F5"
+# Uncomment the links you want to show and add your information to each one.
-page-col: "#FFFFFF"
-link-col: "#008AFF"
-hover-col: "#0085A1"
-footer-col: "#F5F5F5"
-footer-text-col: "#777777"
-footer-link-col: "#404040"
-
-# Alternatively, the navbar, footer, and page background can be set to use background images
-# instead of colour
-
-# navbar-img: "/img/bgimage.png"
-# footer-img: "/img/bgimage.png"
-# page-img: "/img/bgimage.png"
-
-# --- Footer options --- #
-
-# Change all these values or delete the ones you don't want.
-# Important: you must keep the "name" parameter, everything else you can remove
-author:
-  name: Bryan Roessler
-
-# Select your active Social Network Links.
-# Uncomment the links you want to show in the footer and add your information to each link.
-# You can reorder the items to define the link order.
-# If you want to add a new link that isn't here, you'll need to also edit the file _data/SocialNetworks.yml
 social-network-links:
-  rss: true
   email: "bryanroessler@gmail.com"
-#  facebook: daattali
+# rss: true  # remove this line if you don't want to show an RSS link at the bottom
+# facebook: 
   github: "https://git.bryanroessler.com"
-#  twitter: daattali
+#  twitter:
+#  patreon: DeanAttali
+#  youtube: c/daattali
+#  medium: yourname
 #  reddit: yourname
 #  google-plus: +DeanAttali
   linkedin: bryan-roessler-phd-47535a60
@@ -79,28 +74,114 @@ social-network-links:
 #  stackoverflow: "3943160/daattali"
 #  snapchat: deanat78
 #  instagram: deanat78
-#  youtube: user/deanat78
 #  spotify: yourname
 #  telephone: +14159998888
 #  steam: deanat78
 #  twitch: yourname
 #  yelp: yourname
+#  telegram: yourname
+#  calendly: yourname
+#  mastodon: instance.url/@username
+#  bluesky: yourname
+#  ORCID: your ORCID ID
+#  google-scholar: your google scholar
+#  discord: "invite_code" or "users/userid" or "invite/invite_code"
+#  kaggle: yourname
+#  hackerrank: yourname
+#  gitlab: yourname
+#  itchio: yourname
+#  untappd: yourname
 
-# Select which share links to show in posts
+# If you want your website to generate an RSS feed, provide a description
+# The URL for the feed will be https://<your_website>/feed.xml
+# rss-description: Bryan Roessler's Landing Page
+
+###########################
+# --- General options --- #
+###########################
+
+# Select which social network share links to show in posts
 share-links-active:
   twitter: false
   facebook: false
-  google: false
   linkedin: false
+  vk: false
 
-# How to display the link to the website in the footer
+# How to display the link to your website in the footer
 # Remove this if you don't want a link in the footer
-url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
+url-pretty: "bryanroessler.com"
 
-# --- Web Statistics Section --- #
+# Add the website title to the title of every page
+title-on-all-pages: true
 
-# Fill in your Google Analytics ID to track your website using GA
+# Excerpt word length - Truncate the excerpt of each post on the feed page to the specified number of words
-#google_analytics: ""
+excerpt_length: 50
+
+# Whether or not to show an excerpt for every blog post in the feed page
+feed_show_excerpt: true
+
+# Whether or not to show a list of tags below each post preview in the feed page
+feed_show_tags: true
+
+# Add a search button to the navbar
+post_search: true
+
+# Add a button in the footer to edit the current page. Only works if your website is hosted on GitHub
+edit_page_button: true
+
+# Allow sub-menu items (second-level navigation menu items) to be longer than the top-level menu
+# If this setting is off, then long sub-menu words might get cut off
+# See https://github.com/daattali/beautiful-jekyll/issues/765 to understand the issue this setting can solve
+navbar-var-length: false
+
+# The keywords to associate with your website, for SEO purposes
+#keywords: "my,list,of,keywords"
+
+######################################
+# --- Colours / background image --- #
+######################################
+
+# Personalize the colours in your website. Colour values can be any valid CSS colour
+
+page-col: "#FFFFFF"
+text-col: "#404040"
+link-col: "#008AFF"
+hover-col: "#0085A1"
+navbar-col: "#EAEAEA"
+navbar-text-col: "#404040"
+navbar-border-col: "#DDDDDD"
+footer-col: "#EAEAEA"
+footer-text-col: "#777777"
+footer-link-col: "#404040"
+footer-hover-col: "#0085A1"
+
+# Alternatively, the navbar, footer, and page background can be set to an image
+# instead of colour
+
+#navbar-img: "/assets/img/bgimage.png"
+#footer-img: "/assets/img/bgimage.png"
+#page-img: "/assets/img/bgimage.png"
+
+# Suggest a colour for mobile browsers to use as the browser's theme. This is only supported by a few mobile browsers.
+#mobile-theme-col: "#0085A1"
+
+# For any extra visual customization, you can include additional CSS files in every page on your site. List any custom CSS files here
+#site-css:
+#  - "/assets/css/custom-styles.css"
+
+# If you have common JavaScript files that should be included in every page, list them here
+#site-js:
+#  - "/assets/js/custom-script.js"
+
+#################################
+# --- Web Analytics Section --- #
+#################################
+
+# Fill in your Google Analytics tag ID (or "Measurement ID") to track your website usage
+#gtag: "G-XXXXXXXXXX"
+
+# Fill in your Cloudflare Analytics beacon token to track your website using Cloudflare Analytics
+#cloudflare_analytics: ""
 
 # Google Tag Manager ID
 #gtm: ""
@@ -108,57 +189,88 @@ url-pretty: "bryanroessler.com"  # eg. "deanattali.com/beautiful-jekyll"
 # Matomo (aka Piwik) Web statistics
 # Uncomment the following section to enable Matomo. The opt-out parameter controls
 # whether or not you want to allow users to opt out of tracking.
-
 #matomo:
 #  site_id: "9"
 #  uri: "demo.wiki.pro"
 #  opt-out: true
 
+# Google Universal Analytics ID -- deprecated
+# As of July 2023 this is no longer supported by Google! If you are still using `google_analytics`,
+# you should switch to using the `gtag` field above instead.
+#google_analytics: "UA-XXXXXXXX-X"
+
+####################
 # --- Comments --- #
+####################
 
-# Fill in your Disqus shortname (NOT the userid) if you want to support Disqus comments
+# To use Disqus comments, sign up to https://disqus.com and fill in your Disqus shortname (NOT the userid)
-# disqus: ""
+#disqus: ""
 
-# If you want to use JustComments fill with the API Key
+# To use Facebook Comments, create a Facebook app and fill in the Facebook App ID
-#just-comments: "ABCD-EFGH-IJKL"
+#fb_comment_id: ""
 
-# To use Facebook Comments, fill in a Facebook App ID
+# To use CommentBox, sign up for a Project ID on https://commentbox.io
-# fb_comment_id: ""
+#commentbox: "" # Project ID, e.g. "5694267682979840-proj"
 
-# To use Staticman comments, fill in repository, branch, and endpoint
+# To use Utterances comments: (0) uncomment the following section, (1) fill in
-staticman:
+# "repository" (make sure the repository is public), (2) Enable Issues in your repository,
-  repository : # GitHub username/repository eg. "daattali/beautiful-jekyll"
+# (3) Install the Utterances app in your repository https://github.com/apps/utterances
-  branch     : master # If you're not using `master` branch, then you also need to update the `branch` parameter in `staticman.yml`
+# See more details about the parameters below at https://utteranc.es/
-  endpoint   : # URL of your own deployment, with a trailing slash (will fallback to a public GitLab instance) eg. https://<your-api>/v3/entry/github/
+#utterances:
-  reCaptcha:
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
-    # reCaptcha for Staticman (OPTIONAL, but recommended for spam protection)
+#  issue-term: title   # Mapping between blog posts and GitHub issues
-    # If you use reCaptcha, you must also set these parameters in staticman.yml
+#  theme: github-light # Utterances theme
-    siteKey  : # Use your own site key, you need to apply for one on Google
+#  label: blog-comments # Label that will be assigned to GitHub Issues created by Utterances
-    secret   : # ENCRYPT your password by going to https://staticman3.herokuapp.com/v3/encrypt/<your-site-secret>
 
+# To use Staticman comments, uncomment the following section. You may leave the reCaptcha
+# section commented if you aren't using reCaptcha for spam protection.
+# Using Staticman requires advanced knowledge, please consult
+# https://github.com/eduardoboucas/staticman/ and https://staticman.net/ for further
+# instructions. For any support with staticman please direct questions to staticman and
+# not to BeautifulJekyll.
+#staticman:
+#  repository : # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  branch     : master # If you're not using `master` branch, then you also need to update the `branch` parameter in `staticman.yml`
+#  endpoint   : # URL of your deployment, with a trailing slash eg. "https://<your-api>/v3/entry/github/"
+#  reCaptcha:   # (optional, set these parameters in `staticman.yml` as well)
+#    siteKey  : # You need to apply for a site key on Google
+#    secret   : # Encrypt your password by going to https://<your-own-api>/v3/encrypt/<your-site-secret>
+
+# To use giscus comments:
+# (0) Uncomment the following giscus section, (1) Enable Discussions in your GitHub repository,
+# (2) Install the giscus app in your repository (details at https://giscus.app),
+# (3) Fill in *all* the parameters below
+# See more details about giscus and each of the following parameters at https://giscus.app
+#giscus:
+#  hostname: giscus.app # Replace with your giscus instance's hostname if self-hosting
+#  repository: # GitHub username/repository eg. "daattali/beautiful-jekyll"
+#  repository-id: # ID of your repository, retrieve this info from https://giscus.app
+#  category: Announcements # Category name of your GitHub Discussion posts
+#  category-id: # ID of your category, retrieve this info from https://giscus.app
+#  mapping: pathname
+#  reactions-enabled: 1
+#  emit-metadata: 0
+#  theme: light
+
+################
 # --- Misc --- #
+################
 
-# Facebook App ID
+# Ruby Date Format to show dates of posts
-# fb_app_id: ""
-
-# Excerpt Word Length
-# Truncates the excerpt to the specified number of words on the index page
-excerpt_length: 50
-
-# Character used to separate site title and description in HTML document title
-# and RSS feed title
-title-separator: "-"
-
-# Ruby Date Format
 date_format: "%B %-d, %Y"
 
-# --- Don't need to touch anything below here (but you can if you want) --- #
+# Facebook App ID
+#fb_app_id: ""
+
+#################################################################################
+# --- You don't need to touch anything below here (but you can if you want) --- #
+#################################################################################
 
 # Output options (more information on Jekyll's site)
 timezone: "America/New_York"
 markdown: kramdown
 highlighter: rouge
-permalink: /:year-:month-:day-:title/
+permalink: /:year/:month/:day/:title
 paginate: 5
 
 kramdown:
@@ -176,13 +288,9 @@ defaults:
       social-share: true # add social media sharing buttons to all blog posts
   -
     scope:
-      path: "" # all files
+      path: "" # any file that's not a post will be a "page" layout by default
     values:
       layout: "page"
-      show-avatar: true
-
-# Use tags index page and make tags on each post clickable
-link-tags: true
 
 # Exclude these files from production site
 exclude:
@@ -196,12 +304,11 @@ exclude:
   - CHANGELOG.md
   - CNAME
   - Dockerfile
-  - LICENSE
   - README.md
   - Vagrantfile
-
+  - LICENSE
-
+  - screenshot.png
-
+  - docs/
 
 plugins:
   - jekyll-paginate

landing.bryanroessler.com/_data/SocialNetworks.yml

@@ -1,92 +0,0 @@
-# You can define your custom social network links here.
-# Use the same key you added in _config.yml -> social-network-links.
-# In addition to that you need to specify the following properties:
-#   name: Specify a user-friendly name that will be used as a link title
-#   baseURL: Define a base URL which will be combined with the value of
-#            site.social-network-links.<key>
-#   icon: Specify a valid fontawesome icon class
-
-facebook:
-  name: "Facebook"
-  baseURL: "https://www.facebook.com/"
-  icon: "fa-facebook"
-
-github:
-  name: "GitHub"
-  baseURL: "https://github.com/"
-  icon: "fa-github"
-
-twitter:
-  name: "Twitter"
-  baseURL: "https://twitter.com/"
-  icon: "fa-twitter"
-
-reddit:
-  name: "Reddit"
-  baseURL: "https://reddit.com/u/"
-  icon: "fa-reddit"
-
-email:
-  name: "Email me"
-  baseURL: "mailto:"
-  icon: "fa-envelope"
-
-linkedin:
-  name: "LinkedIn"
-  baseURL: "https://linkedin.com/in/"
-  icon: "fa-linkedin"
-
-xing:
-  name: "Xing"
-  baseURL: "https://www.xing.com/profile/"
-  icon: "fa-xing"
-
-stackoverflow:
-  name: "StackOverflow"
-  baseURL: "https://stackoverflow.com/users/"
-  icon: "fa-stack-overflow"
-
-snapchat:
-  name: "Snapchat"
-  baseURL: "https://www.snapchat.com/add/"
-  icon: "fa-snapchat-ghost"
-
-instagram:
-  name: "Instagram"
-  baseURL: "https://www.instagram.com/"
-  icon: "fa-instagram"
-
-youtube:
-  name: "YouTube"
-  baseURL: "https://www.youtube.com/"
-  icon: "fa-youtube"
-
-spotify:
-  name: "Spotify"
-  baseURL: "https://open.spotify.com/user/"
-  icon: "fa-spotify"
-
-telephone:
-  name: "Phone"
-  baseURL: "tel:"
-  icon: "fa-phone"
-
-rss:
-  name: "RSS"
-  baseURL: "{{ '/feed.xml' | relative_url }}"
-  icon: "fa-rss"
-
-steam:
-  name: "Steam"
-  baseURL: "https://steamcommunity.com/id/"
-  icon: "fa-steam"
-
-twitch:
-  name: "Twitch"
-  baseURL: "https://www.twitch.tv/"
-  icon: "fa-twitch"
-
-yelp:
-  name: "Yelp"
-  baseURL: "https://{{ site.author.yelp }}.yelp.com"
-  icon: "fa-yelp"

landing.bryanroessler.com/_includes/cloudflare_analytics.html

@@ -0,0 +1,8 @@
+{% if site.cloudflare_analytics %}
+<!-- Cloudflare Web Analytics -->
+<script defer
+    src='https://static.cloudflareinsights.com/beacon.min.js'
+    data-cf-beacon='{"token": "{{ site.cloudflare_analytics}}"}'>
+</script>
+<!-- End Cloudflare Web Analytics -->
+{% endif %}

landing.bryanroessler.com/_includes/commentbox.html

@@ -0,0 +1,7 @@
+{% if site.commentbox %}
+
+    <div class="commentbox"></div>
+    <script src="https://unpkg.com/commentbox.io/dist/commentBox.min.js"></script>
+    <script>commentBox('{{ site.commentbox }}')</script>
+
+{% endif %}

landing.bryanroessler.com/_includes/comments.html

@@ -0,0 +1,8 @@
+{% if page.comments %}
+  {% include disqus.html %}
+  {% include fb-comment.html %}
+  {% include staticman-comments.html %}
+  {% include utterances-comment.html %}
+  {% include giscus-comment.html %}
+  {% include commentbox.html %}
+{% endif %}

landing.bryanroessler.com/_includes/disqus.html

@@ -1,17 +1,19 @@
 {%- if site.disqus -%}
-<div class="comments">
+<div class="disqus-comments">
+  <div class="comments">
     <div id="disqus_thread"></div>
     <script type="text/javascript">
-        var disqus_shortname = '{{ site.disqus }}';
+	  var disqus_shortname = '{{ site.disqus }}';
-        /* ensure that pages with query string get the same discussion */
+	  /* ensure that pages with query string get the same discussion */
-            var url_parts = window.location.href.split("?");
+	  var url_parts = window.location.href.split("?");
-            var disqus_url = url_parts[0];
+	  var disqus_url = url_parts[0];
-        (function() {
+	  (function() {
-            var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
+		var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
-            dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
+		dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
-            (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
+		(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
-        })();
+	  })();
     </script>
-    <noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
+    <noscript>Please enable JavaScript to view the <a href="https://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
+  </div>
 </div>
 {%- endif -%}

landing.bryanroessler.com/_includes/ext-css.html

@@ -1,7 +1,7 @@
 {% if include.css.sri %}
   <link href="{{ include.css.href }}" rel="stylesheet" integrity="{{ include.css.sri }}" crossorigin="anonymous">
 {% elsif include.css.href %}
-  <link rel="stylesheet" href="{{ include.css.href }}" />
+  <link rel="stylesheet" href="{{ include.css.href }}">
 {% else %}
-  <link rel="stylesheet" href="{{ include.css }}" />
+  <link rel="stylesheet" href="{{ include.css }}">
 {% endif %}

landing.bryanroessler.com/_includes/fb-comment.html

@@ -1,14 +1,16 @@
 {%- if site.fb_comment_id -%}
 <div class="comments">
-    <div id="fb-root"></div>
+  <div id="fb-root"></div>
-    <script>(function(d, s, id) {
+  <script>
-       var js, fjs = d.getElementsByTagName(s)[0];
+    (function(d, s, id) {
-       if (d.getElementById(id)) return;
+      var js, fjs = d.getElementsByTagName(s)[0];
-       js = d.createElement(s); js.id = id;
+      if (d.getElementById(id)) return;
-       js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.12&appId={{ site.fb_comment_id }}&autoLogAppEvents=1';
+      js = d.createElement(s); js.id = id;
-       fjs.parentNode.insertBefore(js, fjs);
+      js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.12&appId={{ site.fb_comment_id }}&autoLogAppEvents=1';
-    }(document, 'script', 'facebook-jssdk'));</script>
+      fjs.parentNode.insertBefore(js, fjs);
-    <div class="fb-comments" data-href="{{ page.url | absolute_url }}" data-width="100%" data-numposts="5"></div>
+    }(document, 'script', 'facebook-jssdk'));
-    <noscript>Please enable JavaScript to view the comments powered by Facebook.</noscript>
+  </script>
+  <div class="fb-comments" data-href="{{ page.url | absolute_url }}" data-width="100%" data-numposts="5"></div>
+  <noscript>Please enable JavaScript to view the comments powered by Facebook.</noscript>
 </div>
 {%- endif -%}

landing.bryanroessler.com/_includes/footer-minimal.html

@@ -1,16 +1,18 @@
 <footer class="footer-min">
   <div class="text-muted">
-	{{ site.author.name }}
+    {% if site.author %}
-	&nbsp;&nbsp;&bull;&nbsp;&nbsp;
+      {{ site.author }}
-	{% if page.date %}
+      &nbsp;&nbsp;&bull;&nbsp;&nbsp;
-	  {{ page.date }}
+    {% endif %}
-	{% else %}
+    {% if page.date %}
-	  {{ site.time | date: '%Y' }}
+      {{ page.date }}
-	{% endif %}
+    {% else %}
+      {{ site.time | date: '%Y' }}
+    {% endif %}
 
     {% if site.url-pretty %}
-    &nbsp;&nbsp;&bull;&nbsp;&nbsp;
+      &nbsp;&nbsp;&bull;&nbsp;&nbsp;
-    <a href="{{ '' | absolute_url }}">{{ site.url-pretty }}</a>
+      <a href="{{ '/' | absolute_url }}">{{ site.url-pretty }}</a>
     {% endif %}
   </div>
 </footer>

landing.bryanroessler.com/_includes/footer-scripts.html

@@ -9,9 +9,9 @@
     <!-- doing something a bit funky here because I want to be careful not to include JQuery twice! -->
     {% if js contains 'jquery' %}
       <script>
-      	if (typeof jQuery == 'undefined') {
+        if (typeof jQuery == 'undefined') {
           document.write('<script src="{{ js | relative_url }}"></scr' + 'ipt>');
-      	}
+        }
       </script>
     {% else %}
       <script src="{{ js | relative_url }}"></script>
@@ -19,6 +19,12 @@
   {% endfor %}
 {% endif %}
 
+{% if site.site-js %}
+  {% for js in site.site-js %}
+    <script src="{{ js | relative_url }}"></script>
+  {% endfor %}
+{% endif %}
+
 {% if page.ext-js %}
   {% for js in page.ext-js %}
     {% include ext-js.html js=js %}

landing.bryanroessler.com/_includes/footer.html

@@ -1,36 +1,27 @@
 <footer>
-  <div class="container beautiful-jekyll-footer">
+  <div class="container-md beautiful-jekyll-footer">
     <div class="row">
-      <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
+      <div class="col-xl-8 offset-xl-2 col-lg-10 offset-lg-1">
-        <ul class="list-inline text-center footer-links">
+      {% include social-networks-links.html %}
-          {%- for link in site.social-network-links -%}
+      {% if page.footer-extra %}
-            {%- assign curkey = link[0] -%}
+        <div class="footer-custom-content">
-            {%- assign element = site.data.SocialNetworks[curkey] -%}
+          {% for file in page.footer-extra %}
-            <li>
+            {% include {{ file }} %}
-            {%- if curkey == 'rss' -%}
+          {% endfor %}
-              <a href="{{ '/feed.xml' | relative_url }}" title="{{ element.name }}">
+        </div>
-            {%- elsif curkey == 'yelp' -%}
+      {% endif %}
-              <a href="https://{{ site.social-network-links[curkey] }}.yelp.com" title="{{ element.name }}">
-            {%- else -%}
-              <a href="{{element.baseURL}}{{ site.social-network-links[curkey] }}" title="{{ element.name }}">
-            {%- endif -%}
-                <span class="fa-stack fa-lg" aria-hidden="true">
-                  <i class="fa fa-circle fa-stack-2x"></i>
-                  <i class="fa {{ element.icon }} fa-stack-1x fa-inverse"></i>
-                </span>
-                <span class="sr-only">{{ element.name }}</span>
-              </a>
-            </li>
-          {%- endfor -%}
-        </ul>
       <p class="copyright text-muted">
-      {{ site.author.name }}
+      {% if site.author %}
-      &nbsp;&bull;&nbsp;
+        {{ site.author }}
+        &nbsp;&bull;&nbsp;
+      {% endif %}
       {{ site.time | date: '%Y' }}
 
       {% if site.url-pretty %}
-      &nbsp;&bull;&nbsp;
+        &nbsp;&bull;&nbsp;
-      <a href="{{ '' | absolute_url }}">{{ site.url-pretty }}</a>
+        <span class="author-site">
+          <a href="{% if site.url-canonical %}{{ site.url-canonical }}{% else %}{{ '/' | absolute_url }}{% endif %}">{{ site.url-pretty }}</a>
+        </span>
       {% endif %}
 
       {% if site.matomo %}
@@ -39,12 +30,17 @@
           <a href="http://{{- site.matomo.uri -}}/index.php?module=CoreAdminHome&action=optOut" target="_blank" class="text_muted">Do-not-Track</a>
         {% endif %}
       {% endif%}
+
+      {% if site.edit_page_button and site.github.repository_url %}
+        &nbsp;&bull;&nbsp;
+        <a title="Edit this page on GitHub" href="{{ site.github.repository_url }}/edit/{{ site.github.source.branch }}/{{ page.path }}" class="text_muted">Edit page</a>
+       {% endif%}
+
       </p>
-          <!-- Please don't remove this, keep my open source work credited :) -->
+      {% unless site.remove-ads %}<p class="theme-by text-muted">
-    <p class="theme-by text-muted">
+        Powered by
-      Theme by
+        <a href="https://beautifuljekyll.com">Beautiful Jekyll</a>
-      <a href="https://deanattali.com/beautiful-jekyll/">beautiful-jekyll</a>
+      </p>{% endunless %}
-    </p>
       </div>
     </div>
   </div>

landing.bryanroessler.com/_includes/giscus-comment.html

@@ -0,0 +1,16 @@
+{% if site.giscus.repository and site.giscus.hostname %}
+
+<script src="https://{{ site.giscus.hostname }}/client.js"
+        data-repo="{{ site.giscus.repository }}"
+        data-repo-id="{{ site.giscus.repository-id }}"
+        data-category="{{ site.giscus.category }}"
+        data-category-id="{{ site.giscus.category-id }}"
+        data-mapping="{{ site.giscus.mapping }}"
+        data-reactions-enabled="{{ site.giscus.reactions-enabled }}"
+        data-emit-metadata="{{ site.giscus.emit-metadata }}"
+        data-theme="{{ site.giscus.theme }}"
+        crossorigin="anonymous"
+        async>
+</script>
+
+{% endif %}

landing.bryanroessler.com/_includes/google_analytics.html

@@ -1,14 +1,26 @@
 {% if site.google_analytics %}
 <!-- Google Analytics -->
+{% unless site.gtag %}
+<div id="bj-ganalytics-deprecated-msg" style="position: fixed; background: #b90404; bottom: 0; width: 100%; z-index: 10000; color: #f0f0f0; text-align: center; padding: 0.5rem;">
+  <div title="Close" onclick="$(this).parent().remove()" style="position: absolute; right: 5px; top: 0; font-size: 1.5em; line-height: 1; cursor: pointer;">&times;</div>
+  <div style="max-width: 800px; margin: auto; font-size: 1.1em;">
+    This website is using outdated Google Analytics
+    <details style="font-size: 0.8em;">
+      <summary>More info</summary>
+      As of July 2023, Google's Universal Analytics is going away and being replaced by Google Analytics 4. This website is still using the old Universal Analytics. In order to remove this message, the website owner must remove the <code>google_analytics</code> property in the website's config file, and optionally replace it with the new <code>gtag</code> property.
+    </details>
+  </div>
+</div>
+{% endunless %}
 <script>
-    (function (i, s, o, g, r, a, m) {
+  (function (i, s, o, g, r, a, m) {
-        i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function () {
+    i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function () {
-            (i[r].q = i[r].q || []).push(arguments)
+      (i[r].q = i[r].q || []).push(arguments)
-        }, i[r].l = 1 * new Date(); a = s.createElement(o),
+    }, i[r].l = 1 * new Date(); a = s.createElement(o),
-            m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m)
+      m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m)
-    })(window, document, 'script', 'https://www.google-analytics.com/analytics.js', 'ga');
+  })(window, document, 'script', 'https://www.google-analytics.com/analytics.js', 'ga');
-    ga('create', '{{ site.google_analytics }}', 'auto');
+  ga('create', '{{ site.google_analytics }}', 'auto');
-    ga('send', 'pageview');
+  ga('send', 'pageview');
 </script>
 <!-- End Google Analytics -->
 {% endif %}

landing.bryanroessler.com/_includes/gtag.html

@@ -1,11 +1,10 @@
 {% if site.gtag %}
 <!-- Global site tag (gtag.js) - Google Analytics -->
 <script async src="https://www.googletagmanager.com/gtag/js?id={{ site.gtag }}"></script>
-    <script>
+<script>
-          window.dataLayer = window.dataLayer || [];
+  window.dataLayer = window.dataLayer || [];
   function gtag(){dataLayer.push(arguments);}
   gtag('js', new Date());
-
   gtag('config', '{{ site.gtag }}');
 </script>
 {% endif %}

landing.bryanroessler.com/_includes/gtm_body.html

@@ -1,6 +1,5 @@
 {% if site.gtm %}
-    <!-- Google Tag Manager (noscript) -->
+  <!-- Google Tag Manager (noscript) -->
-    <noscript><iframe src="https://www.googletagmanager.com/ns.html?id={{ site.gtm }}"
+  <noscript><iframe src="https://www.googletagmanager.com/ns.html?id={{ site.gtm }}" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
-    height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
+  <!-- End Google Tag Manager (noscript) -->
-    <!-- End Google Tag Manager (noscript) -->
 {% endif %}

landing.bryanroessler.com/_includes/gtm_head.html

@@ -1,9 +1,11 @@
 {% if site.gtm %}
-    <!-- Google Tag Manager -->
+  <!-- Google Tag Manager -->
-    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
+  <script>
-    new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
+    (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
-    j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
+      new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
-    'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
+      j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
-    })(window,document,'script','dataLayer','{{ site.gtm }}');</script>
+      'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
-    <!-- End Google Tag Manager -->
+    })(window,document,'script','dataLayer','{{ site.gtm }}');
+  </script>
+  <!-- End Google Tag Manager -->
 {% endif %}

landing.bryanroessler.com/_includes/head.html

@@ -1,21 +1,68 @@
 <head>
-  <meta charset="utf-8" />
+  <meta charset="utf-8">
-  <meta http-equiv="X-UA-Compatible" content="IE=edge">
+  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, viewport-fit=cover">
 
-  <title>{% if page.use-site-title %}{{ site.title }} {{ site.title-separator }} {{ site.description }}{% elsif page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</title>
+  {% capture pagetitle %}
+    {%- if page.share-title -%}
+      {{ page.share-title | strip_html | xml_escape }}
+    {%- elsif page.title -%}
+      {{ page.title | strip_html | xml_escape  }}
+    {%- else -%}
+      {{ site.title | strip_html | xml_escape }}
+    {%- endif -%}
+  {% endcapture %}
 
-  <meta name="author" content="{{ site.author.name }}" />
+  {% capture title %}
+    {%- if site.title and site.title-on-all-pages and (site.title != pagetitle) -%}
+      {{ pagetitle }} | {{ site.title }}
+    {%- else -%}
+      {{ pagetitle }}
+    {%- endif -%}
+  {% endcapture %}
 
-  {% if page.subtitle %}
+  {% capture description %}
-  <meta name="description" content="{{ page.subtitle }}">
+    {%- if page.share-description -%}
+      {{ page.share-description | strip_html | xml_escape }}
+    {%- elsif page.subtitle -%}
+      {{ page.subtitle | strip_html | xml_escape }}
+    {%- else -%}
+      {%- assign excerpt_length = site.excerpt_length | default: 50 -%}
+      {{ page.content | strip_html | xml_escape | truncatewords: excerpt_length | strip }}
+    {%- endif -%}
+  {% endcapture %}
+
+  <title>{{ title }}</title>
+
+  {% capture author %}
+    {%- if page.author -%}
+      {{  page.author | strip_html }}
+    {%- elsif site.author -%}
+      {{ site.author }}
+    {%- endif -%}
+  {% endcapture %}
+  {% if author != "" %}
+  <meta name="author" content="{{ author }}">
   {% endif %}
 
-  <link rel="alternate" type="application/rss+xml" title="{{ site.title }} {{ site.title-separator }} {{ site.description }}" href="{{ '/feed.xml' | absolute_url }}" />
+  <meta name="description" content="{{ description }}">
+
+  {% if site.mobile-theme-col %}
+  <meta name="theme-color" content="{{ site.mobile-theme-col }}">
+  {% endif %}
+
+  {% if site.keywords %}
+  <meta name="keywords" content="{{ site.keywords }}">
+  {% endif %}
+
+  {% if site.rss-description %}
+  <link rel="alternate" type="application/rss+xml" title="{{ site.title }}" href="{{ '/feed.xml' | absolute_url }}">
+  {% endif %}
 
   {% include gtag.html %}
   {% include gtm_head.html %}
   {% include google_analytics.html %}
+  {% include cloudflare_analytics.html %}
+  {% include mathjax.html %}
 
   {% if layout.common-ext-css %}
     {% for css in layout.common-ext-css %}
@@ -25,13 +72,13 @@
 
   {% if layout.common-css %}
     {% for css in layout.common-css %}
-      <link rel="stylesheet" href="{{ css | relative_url }}" />
+      <link rel="stylesheet" href="{{ css | relative_url }}">
     {% endfor %}
   {% endif %}
 
-  {% if layout.common-googlefonts %}
+  {% if site.site-css %}
-    {% for font in layout.common-googlefonts %}
+    {% for css in site.site-css %}
-      <link rel="stylesheet" href="//fonts.googleapis.com/css?family={{ font }}" />
+      <link rel="stylesheet" href="{{ css | relative_url }}">
     {% endfor %}
   {% endif %}
 
@@ -43,89 +90,86 @@
   
   {% if page.css %}
     {% for css in page.css %}
-      <link rel="stylesheet" href="{{ css | relative_url }}" />
+      <link rel="stylesheet" href="{{ css | relative_url }}">
     {% endfor %}
   {% endif %}
 
-  {% if page.googlefonts %}
-    {% for font in page.googlefonts %}
-      <link rel="stylesheet" href="//fonts.googleapis.com/css?family={{ font }}" />
-    {% endfor %}
-  {% endif %}
-
-    <!-- Facebook OpenGraph tags -->
   {% if site.fb_app_id %}
-  <meta property="fb:app_id" content="{{ site.fb_app_id }}" />
+  <meta property="fb:app_id" content="{{ site.fb_app_id }}">
   {% endif %}
 
-  {% if page.meta-title %}
+  {% if site.title %}
-  <meta property="og:title" content="{{ page.meta-title }}" />
+  <meta property="og:site_name" content="{{ site.title }}">
-  {% elsif page.title %}
-  <meta property="og:title" content="{{ page.title }}" />
-  {% else %}
-  <meta property="og:title" content="{{ site.title }}" />
   {% endif %}
 
-   {% if page.meta-description %}
+  {%- capture img -%}
-  <meta property="og:description" content="{{ page.meta-description }}">
+    {%- if page.share-img -%}
-  {% elsif page.subtitle %}
+      {{ page.share-img }}
-  <meta property="og:description" content="{{ page.subtitle }}">
+    {%- elsif page.cover-img -%}
-  {% else %}
+      {%- if page.cover-img.first -%}
-  <meta property="og:description" content="{{ page.content | strip_html | xml_escape | truncatewords: 50 }}">
+        {{ page.cover-img[0].first.first }}
+      {%- else -%}
+        {{ page.cover-img }}
+      {%- endif -%}
+    {%- elsif page.thumbnail-img -%}
+      {{ page.thumbnail-img }}
+    {%- elsif site.avatar -%}
+      {{ site.avatar }}
+    {% endif %}
+  {%- endcapture -%}
+  {%- assign img=img | strip -%}
+
+  <meta property="og:title" content="{{ title }}">
+  <meta property="og:description" content="{{ description }}">
+
+  {% if img != "" %}
+  <meta property="og:image" content="{{ img | absolute_url }}">
   {% endif %}
 
-
-  <meta property="og:type" content="website" />
-
   {% if page.id %}
-  <meta property="og:url" content="{{ page.url | absolute_url }}" />
+  <meta property="og:type" content="article">
-  <link rel="canonical" href="{{ page.url | absolute_url }}" />
+  {% if author != "" %}
+  <meta property="og:article:author" content="{{ author }}">
+  {% endif %}
+  <meta property="og:article:published_time" content="{{ page.date | date_to_xmlschema }}">
+  <meta property="og:url" content="{{ page.url | absolute_url }}">
+  <link rel="canonical" href="{{ page.url | absolute_url }}">
   {% else %}
-  <meta property="og:url" content="{{ page.url | absolute_url | strip_index }}" />
+  <meta property="og:type" content="website">
-  <link rel="canonical" href="{{ page.url | absolute_url | strip_index }}" />
+  <meta property="og:url" content="{{ page.url | absolute_url | strip_index }}">
+  <link rel="canonical" href="{{ page.url | absolute_url | strip_index }}">
   {% endif %}
 
-  {% if page.share-img %}
+  {% if img != "" and img != site.avatar %}
-  <meta property="og:image" content="{{ page.share-img }}" />
+  <meta name="twitter:card" content="summary_large_image">
-  {% elsif site.avatar %}
-  <meta property="og:image" content="{{ site.avatar | absolute_url }}" />
-  {% endif %}
-
-
-  <!-- Twitter summary cards -->
-  <meta name="twitter:card" content="summary" />
-  <meta name="twitter:site" content="@{{ site.author.twitter }}" />
-  <meta name="twitter:creator" content="@{{ site.author.twitter }}" />
-
-  {% if page.meta-title %}
-  <meta name="twitter:title" content="{{ page.meta-title }}" />
-  {% elsif page.title %}
-  <meta name="twitter:title" content="{{ page.title }}" />
   {% else %}
-  <meta name="twitter:title" content="{{ site.title }}" />
+  <meta name="twitter:card" content="summary">
+  {% endif %}
+  <meta name="twitter:site" content="@{{ site.social-network-links.twitter }}">
+  <meta name="twitter:creator" content="@{{ site.social-network-links.twitter }}">
+
+  <meta property="twitter:title" content="{{ title }}">
+  <meta property="twitter:description" content="{{ description }}">
+
+  {% if img != "" %}
+  <meta name="twitter:image" content="{{ img | absolute_url }}">
   {% endif %}
 
-  {% if page.meta-description %}
-  <meta name="twitter:description" content="{{ page.meta-description }}">
-  {% elsif page.subtitle %}
-  <meta name="twitter:description" content="{{ page.subtitle }}">
-  {% else %}
-  <meta name="twitter:description" content="{{ page.content | strip_html | xml_escape | truncatewords: 50 }}">
-  {% endif %}
-
-  {% if page.share-img %}
-  <meta name="twitter:image" content="{{ page.share-img }}" />
-  {% elsif site.avatar %}
-  <meta name="twitter:image" content="{{ site.avatar | absolute_url }}" />
-  {% endif %}
-
-  {% if site.matomo %}
   {% include matomo.html %}
-  {% endif %}
 
   {% if page.comments and site.staticman.repository and site.staticman.branch %}
-  <!-- Staticman -->
+  <link rel="stylesheet" href="{{ "/assets/css/staticman.css" | relative_url }}">
-  <link rel="stylesheet" href="{{ "/css/staticman.css" | relative_url }}" />
+  {% endif %}
+
+  {% assign favicon_exists = site.static_files | where: "path", "/favicon.ico" | size %}
+  {% if favicon_exists == 1 %}
+  <link rel="icon" href="{{ '/favicon.ico' | relative_url }}" />
+  {% endif %}
+
+  {% if page.head-extra %}
+    {% for file in page.head-extra %}
+      {% include {{ file }} %}
+    {% endfor %}
   {% endif %}
 
 </head>

landing.bryanroessler.com/_includes/header.html

@@ -1,76 +1,65 @@
-<!-- TODO this file has become a mess, refactor it -->
+{% assign date_format = site.date_format | default: "%B %-d, %Y" %}
 
-{% if page.bigimg or page.title %}
+{% if page.cover-img %}
-
+  <div id="header-big-imgs" data-num-img={% if page.cover-img.first %}{{ page.cover-img.size }}{% else %}1{% endif %}
-{% if page.bigimg %}
+    {% for bigimg in page.cover-img %}
-  <div id="header-big-imgs" data-num-img={% if page.bigimg.first %}{{ page.bigimg.size }}{% else %}1{% endif %}
+    {% assign imgnum = forloop.index %}
-    {% for bigimg in page.bigimg %}
+    {% for imginfo in bigimg %}
-	  {% assign imgnum = forloop.index %}
+    {% if imginfo[0] %}
-	  {% for imginfo in bigimg %}
+      data-img-src-{{ imgnum }}="{{ imginfo[0] | absolute_url }}"
-	    {% if imginfo[0] %}
+      data-img-desc-{{ imgnum }}="{{ imginfo[1] }}"
-		  data-img-src-{{ imgnum }}="{{ imginfo[0] | relative_url }}"
+    {% else %}
-		  data-img-desc-{{ imgnum }}="{{ imginfo[1] }}"
+      data-img-src-{{ imgnum }}="{{ imginfo | absolute_url }}"
-		{% else %}
+    {% endif %}
-		  data-img-src-{{ imgnum }}="{{ imginfo | relative_url }}"
+    {% endfor %}
-		{% endif %}
-	  {% endfor %}
     {% endfor %}
   ></div>
 {% endif %}
 
-<header class="header-section {% if page.bigimg %}has-img{% endif %}">
+<header class="header-section {% if page.cover-img %}has-img{% endif %}">
-{% if page.bigimg %}
+<div class="intro-header {% if page.cover-img %} big-img {% endif %}">
-<div class="big-img intro-header">
+  {% if page.cover-img or page.title %}
-  <div class="container">
+  <div class="container-md">
     <div class="row">
-      <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
+      <div class="col-xl-8 offset-xl-2 col-lg-10 offset-lg-1">
         <div class="{{ include.type }}-heading">
-          <h1>{% if page.title %}{{ page.title }}{% else %}<br/>{% endif %}</h1>
+          <h1>{% if page.title %}{{ page.title | strip_html }}{% else %}<br/>{% endif %}</h1>
-		  {% if page.subtitle %}
+          {% if page.subtitle %}
-		    {% if include.type == "page" %}
+            {% if include.type == "page" %}
-            <hr class="small">
+              <hr class="small">
-            <span class="{{ include.type }}-subheading">{{ page.subtitle }}</span>
+              <span class="{{ include.type }}-subheading">{{ page.subtitle | strip_html }}</span>
-			{% else %}
+            {% else %}
-			<h2 class="{{ include.type }}-subheading">{{ page.subtitle }}</h2>
+              <h2 class="{{ include.type }}-subheading">{{ page.subtitle | strip_html }}</h2>
-			{% endif %}
+            {% endif %}
-		  {% endif %}
+          {% endif %}
           
-		  {% if include.type == "post" %}
+          {% if include.type == "post" %} 
-		  <span class="post-meta">Posted on {{ page.date | date: site.date_format }}</span>
+            {% if page.author %}
-		  {% endif %}
+              By <strong>{{ page.author | strip_html }}</strong><br>
+            {% endif%}
+            <span class="post-meta">Posted on {{ page.date | date: date_format }}</span>
+            {% if page.last-updated %}
+              <span class="post-meta">
+                <span class="d-none d-md-inline middot">&middot;</span>
+                Last updated {{ page.last-updated | date: date_format }}
+              </span>
+            {% endif %}
+            {% if page.readtime %}
+              {% include readtime.html %}
+            {% endif %}
+          {% endif %}
         </div>
       </div>
     </div>
   </div>
-  <span class='img-desc'></span>
+  {% endif %}
+  {% if page.cover-img %}<span class='img-desc'></span>{% endif %}
 </div>
+
+{% if page.header-extra %}
+  {% for file in page.header-extra %}
+    {% include {{ file }} %}
+  {% endfor %}
 {% endif %}
-<div class="intro-header no-img">
-  <div class="container">
-    <div class="row">
-      <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
-        <div class="{{ include.type }}-heading">
-          <h1>{% if page.title %}{{ page.title }}{% else %}<br/>{% endif %}</h1>
-		  {% if page.subtitle %}
-		    {% if include.type == "page" %}
-            <hr class="small">
-            <span class="{{ include.type }}-subheading">{{ page.subtitle }}</span>
-			{% else %}
-			<h2 class="{{ include.type }}-subheading">{{ page.subtitle }}</h2>
-			{% endif %}
-		  {% endif %}
 
-		  {% if include.type == "post" %}
-		  <span class="post-meta">Posted on {{ page.date | date: site.date_format }}</span>
-		  {% endif %}
-        </div>
-      </div>
-    </div>
-  </div>
-</div>
 </header>
-
-
-{% else %}
-<div class="intro-header"></div>
-{% endif %}

landing.bryanroessler.com/_includes/just_comments.html

@@ -1,4 +0,0 @@
-{%- if site.just-comments -%}
-<div class="just-comments" data-apikey="{{site.just-comments}}"></div>
-<script async src="https://just-comments.com/w2.js"></script>
-{%- endif -%}

landing.bryanroessler.com/_includes/mathjax.html

@@ -0,0 +1,12 @@
+{% if page.mathjax %}
+<script type="text/javascript">
+  MathJax = {
+    options: {
+      skipHtmlTags: [
+        'script', 'noscript', 'style', 'textarea', 'pre', 'code'
+      ]
+    }
+  };
+</script>
+<script type="text/javascript" async src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
+{% endif %}

landing.bryanroessler.com/_includes/nav.html

@@ -1,57 +1,62 @@
-<nav class="navbar navbar-default navbar-fixed-top navbar-custom">
+<nav class="navbar navbar-expand-xl navbar-light fixed-top navbar-custom {% if page.nav-short %}top-nav-short-permanent{% else %}top-nav-regular{% endif %}">
-  <div class="container-fluid">
-    <div class="navbar-header">
-      <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#main-navbar">
-        <span class="sr-only">Toggle navigation</span>
-        <span class="icon-bar"></span>
-        <span class="icon-bar"></span>
-        <span class="icon-bar"></span>
-      </button>
-      {%- if site.title-img -%}
-        <a class="navbar-brand navbar-brand-logo" href="{{ '' | absolute_url }}"><img src="{{ site.title-img }}"/></a>
-      {%- else -%}
-        <a class="navbar-brand" href="{{ '' | absolute_url }}">{{ site.title }}</a>
-      {%- endif -%}
-    </div>
 
-    <div class="collapse navbar-collapse" id="main-navbar">
+  {%- if site.title-img -%}
-      <ul class="nav navbar-nav navbar-right">
+    <a class="navbar-brand navbar-brand-logo" href="{{ '/' | absolute_url }}"><img alt="{{ site.title }} Logo" src="{{ site.title-img | relative_url}}"/></a>
+  {%- elsif site.title -%}
+    <a class="navbar-brand" href="{{ '/' | absolute_url }}">{{ site.title }}</a>
+  {%- endif -%}
+
+  <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#main-navbar" aria-controls="main-navbar" aria-expanded="false" aria-label="Toggle navigation">
+    <span class="navbar-toggler-icon"></span>
+  </button>
+
+  <div class="collapse navbar-collapse" id="main-navbar">
+    <ul class="navbar-nav ml-auto">
       {%- for link in site.navbar-links -%}
         {%- if link[1].first %}
-          <li class="navlinks-container">
+          <li class="nav-item dropdown">
-            <a class="navlinks-parent" href="javascript:void(0)">{{ link[0] }}</a>
+            <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">{{ link[0] }}</a>
-            <div class="navlinks-children">
+            <div class="dropdown-menu dropdown-menu-right" aria-labelledby="navbarDropdown">
               {%- for childlink in link[1] -%}
-              {%- for linkparts in childlink %}
+                {%- for linkparts in childlink %}
-              <a href="{{ linkparts[1] | relative_url }}">{{ linkparts[0] }}</a>
+                  <a class="dropdown-item" href="{{ linkparts[1] | relative_url }}">{{ linkparts[0] }}</a>
-              {%- endfor -%}
+                {%- endfor -%}
               {%- endfor %}
             </div>
           </li>
         {% else %}
-          <li><a href="{{ link[1] | relative_url }}">{{ link[0] }}</a></li>
+          <li class="nav-item">
+            <a class="nav-link" href="{{ link[1] | relative_url }}">{{ link[0] }}</a>
+          </li>
         {%- endif -%}
       {%- endfor -%}
-      </ul>
+      {% if site.post_search %}
-    </div>
+        <li class="nav-item">
-
+          <a class="nav-link" id="nav-search-link" href="#" title="Search">
-	{% if page.image and (layout.show-avatar or page.show-avatar) %}
+            <span id="nav-search-icon" class="fa fa-search"></span>
-	<div class="avatar-container">
+            <span id="nav-search-text">Search</span>
-	  <div class="avatar-img-border">
+          </a>
-	    <a href="{{ '' | absolute_url }}">
+        </li>
-	      <img class="avatar-img" src="{{ page.image | relative_url }}" />
+      {%- endif -%}
-		</a>
+    </ul>
-	  </div>
-	</div>
-	{% elsif site.avatar and (layout.show-avatar or page.show-avatar) %}
-	<div class="avatar-container">
-	  <div class="avatar-img-border">
-	    <a href="{{ '' | absolute_url }}">
-	      <img class="avatar-img" src="{{ site.avatar | relative_url }}" />
-		</a>
-	  </div>
-	</div>
-	{% endif %}
-
   </div>
+
+  {% if site.navbar-extra %}
+    {% for file in site.navbar-extra %}
+      {% include {{ file }} %}
+    {% endfor %}
+  {% endif %}
+
+  {% if site.avatar and page.show-avatar != false %}
+    <div class="avatar-container">
+      <div class="avatar-img-border">
+        <a href="{{ '/' | absolute_url }}">
+          <img alt="Navigation bar avatar" class="avatar-img" src="{{ site.avatar | relative_url }}" />
+        </a>
+      </div>
+    </div>
+  {% endif %}
+
 </nav>
+
+{% include search.html %}

landing.bryanroessler.com/_includes/readtime.html

@@ -0,0 +1,16 @@
+<!--- "ReadTime on GitHub Jekyll" (c) 2020 Ruby Griffith Ramirez, MIT License -->
+
+{% assign ReadTime = page.content | strip_html | number_of_words %}
+{% assign calcReadTime = ReadTime | float %}
+{% assign finalReadTime = calcReadTime | divided_by:200 | round: 2 %}
+{% assign number = finalReadTime | round %}
+{% if number >= 1 %}
+  {% assign yesReadTime = number | append: " minute read" %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ yesReadTime }}</span>
+{% elsif number < 1 %}
+  {% assign minReadTime = '&lt; 1 minute read' %}
+  <span class="post-meta"><span class="d-none d-md-inline middot">&middot;</span> {{ minReadTime }}</span>
+{% else %}
+  {% assign nilReadTime = number | replace:'0',' ' %}
+  {{ nilReadTime }}
+{% endif %}

landing.bryanroessler.com/_includes/search.html

@@ -0,0 +1,19 @@
+{% if site.post_search %}
+
+<div id="beautifuljekyll-search-overlay">
+
+  <div id="nav-search-exit" title="Exit search">✕</div>
+  <input type="text" id="nav-search-input" placeholder="Search">
+  <ul id="search-results-container"></ul>
+  
+  <script src="https://unpkg.com/simple-jekyll-search@latest/dest/simple-jekyll-search.min.js"></script>
+  <script>
+    SimpleJekyllSearch({
+      searchInput: document.getElementById('nav-search-input'),
+      resultsContainer: document.getElementById('search-results-container'),
+      json: '{{ site.baseurl }}/assets/data/searchcorpus.json' 
+    });
+  </script>
+</div>
+
+{% endif %}

landing.bryanroessler.com/_includes/social-networks-links.html

@@ -0,0 +1,401 @@
+{% if site.social-network-links %}
+<ul class="list-inline text-center footer-links">
+
+{%- for network in site.social-network-links -%}
+
+  {%- if network[0] == "rss" and network[1] and site.rss-description -%}
+  <li class="list-inline-item">
+    <a href="{{ '/feed.xml' | relative_url }}" title="RSS">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-rss fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">RSS</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "email" -%}
+  <li class="list-inline-item">
+    <a href="mailto:{{ network[1] }}" title="Email me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-envelope fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Email me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "calendly" -%}
+  <li class="list-inline-item">
+    <a href="https://calendly.com/{{ network[1] }}" title="Schedule a meeting with me">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-calendar-check fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Schedule a meeting with me</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "facebook" -%}
+  <li class="list-inline-item">
+    <a href="https://www.facebook.com/{{ network[1] }}" title="Facebook">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-facebook fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Facebook</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telegram" -%}
+  <li class="list-inline-item">
+    <a href="https://t.me/{{ network[1] }}" title="Telegram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-telegram-plane fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Telegram</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "whatsapp" -%}
+  <li class="list-inline-item">
+    <a href="https://wa.me/{{ network[1] }}" title="Whatsapp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-whatsapp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Whatsapp</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "github" -%}
+  <li class="list-inline-item">
+    <a href="https://github.com/{{ network[1] }}" title="GitHub">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-github fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitHub</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "gitlab" -%}
+  <li class="list-inline-item">
+    <a href="https://gitlab.com/{{ network[1] }}" title="GitLab">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-gitlab fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">GitLab</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitter" -%}
+  <li class="list-inline-item">
+    <a href="https://twitter.com/{{ network[1] }}" title="X (Twitter)">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-x-twitter fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">X (Twitter)</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "reddit" -%}
+  {% assign reddit_start = network[1] | split: "/" | first -%}
+  {% unless reddit_start == 'r' or reddit_start == 'u' -%}
+    {% assign reddit_url_prefix = 'u/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://reddit.com/{{ reddit_url_prefix }}{{ network[1] }}" title="Reddit">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-reddit fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Reddit</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "linkedin" -%}
+  <li class="list-inline-item">
+    <a href="https://linkedin.com/in/{{ network[1] }}" title="LinkedIn">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-linkedin fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">LinkedIn</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "xing" -%}
+  <li class="list-inline-item">
+    <a href="https://www.xing.com/profile/{{ network[1] }}" title="Xing">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-xing fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Xing</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "stackoverflow" -%}
+  <li class="list-inline-item">
+    <a href="https://stackoverflow.com/users/{{ network[1] }}" title="StackOverflow">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-stack-overflow fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">StackOverflow</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "snapchat" -%}
+  <li class="list-inline-item">
+    <a href="https://www.snapchat.com/add/{{ network[1] }}" title="Snapchat">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-snapchat-ghost fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Snapchat</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "instagram" -%}
+  <li class="list-inline-item">
+    <a href="https://www.instagram.com/{{ network[1] }}" title="Instagram">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-instagram fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Instagram</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "youtube" -%}
+  <li class="list-inline-item">
+    <a href="https://www.youtube.com/{{ network[1] }}" title="YouTube">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-youtube fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">YouTube</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "spotify" -%}
+  <li class="list-inline-item">
+    <a href="https://open.spotify.com/user/{{ network[1] }}" title="Spotify">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-spotify fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Spotify</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "telephone" -%}
+  <li class="list-inline-item">
+    <a href="tel:{{ network[1] }}" title="Phone">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-phone fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Phone</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "steam" -%}
+  <li class="list-inline-item">
+    <a href="https://steamcommunity.com/id/{{ network[1] }}" title="Steam">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-steam fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Steam</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "twitch" -%}
+  <li class="list-inline-item">
+    <a href="https://www.twitch.tv/{{ network[1] }}" title="Twitch">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-twitch fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Twitch</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "yelp" -%}
+  <li class="list-inline-item">
+    <a href="https://yelp.com/{{ network[1] }}" title="Yelp">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-yelp fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Yelp</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "mastodon" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://{{ network[1] }}" title="Mastodon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-mastodon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Mastodon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "bluesky" -%}
+  <li class="list-inline-item">
+    <a rel="me" href="https://bsky.app/profile/{{ network[1] }}" title="Bluesky">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fas fa-square fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Bluesky</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "ORCID" -%}
+ <li class="list-inline-item">
+   <a href="https://orcid.org/{{ network[1] }}" title="ORCID">
+     <span class="fa-stack fa-lg" aria-hidden="true">
+       <i class="fas fa-circle fa-stack-2x"></i>
+       <i class="fab fa-orcid fa-stack-1x fa-inverse"></i>
+     </span>
+     <span class="sr-only">ORCID</span>
+   </a>
+ </li>
+  {%- endif -%}
+
+  {%- if network[0] == "google-scholar" -%}
+  <li class="list-inline-item">
+    <a href="https://scholar.google.com/citations?user={{ network[1] }}" title="Google Scholar">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fa fa-graduation-cap fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Google Scholar</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "patreon" -%}
+  <li class="list-inline-item">
+    <a href="https://patreon.com/{{ network[1] }}" title="Patreon">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-patreon fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Patreon</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "medium" -%}
+  <li class="list-inline-item">
+    <a href="https://medium.com/@{{ network[1] }}" title="Medium">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-medium fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Medium</span>
+    </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "itchio" -%}
+  <li class="list-inline-item">
+    <a href="https://{{ network[1] }}.itch.io/" title="Itchio">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-itch-io fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Itchio</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "discord" -%}
+  {% assign discord_start = network[1] | split: "/" | first -%}
+  {% unless discord_start == 'users' or discord_start == 'invite' -%}
+    {% assign discord_url_prefix = 'invite/' -%}
+  {% endunless -%}
+  <li class="list-inline-item">
+    <a href="https://discord.com/{{discord_url_prefix}}{{network[1]}}" title="Discord">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-discord fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Discord</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "kaggle" -%}
+  <li class="list-inline-item">
+    <a href="https://www.kaggle.com/{{ network[1] }}" title="Kaggle">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-kaggle fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Kaggle</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "hackerrank" -%}
+  <li class="list-inline-item">
+    <a href="https://www.hackerrank.com/{{ network[1] }}" title="Hackerrank">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-hackerrank fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Hackerrank</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+  {%- if network[0] == "untappd" -%}
+  <li class="list-inline-item">
+    <a href="https://untappd.com/user/{{ network[1] }}" title="Untappd">
+      <span class="fa-stack fa-lg" aria-hidden="true">
+        <i class="fas fa-circle fa-stack-2x"></i>
+        <i class="fab fa-untappd fa-stack-1x fa-inverse"></i>
+      </span>
+      <span class="sr-only">Untappd</span>
+   </a>
+  </li>
+  {%- endif -%}
+
+{%- endfor -%}
+
+</ul>
+{% endif %}