redis-cache VS wordpress-to-jekyll-exporter

Ah yes, good catch. For caching I use Redis (which is installed/setup on the server, and connected via the Redis Object Cache plugin). I tend to also implement a good amount of caching in the theme itself using WP's built in caching functions, as well as utilizing Cloudflare. All assets (SCSS, JS etc...) are compressed/minified before being pushed up to the theme's repo.

If your hosting has Redis available: https://wordpress.org/plugins/redis-cache/

As I said in the other post, the plugin I use is Redis Object Cache. Install and configure it is not hard. Out of the box, it will try to connect to a Redis instance in the same server (127.0.0.1) on port 6379 using Redis database number 0.

This is the plugin I used to convert my files from WP to Jekyll and it cut down my work by half. However, I wanted control over every aspect of my content (posts, files, pages, etc.) so much of the time was used on learning how different Jekyll themes work (I settled on one called rain). The problems I did encounter is that I had to rewrite the theme I chose (called Rain) and edit a lot of files while at the same time learning the Jekyll format and reading lots of tutorials. I started during Christmas and had finished building and transferring content by 11th or 12th Jan. GitHub then decided to flag my account and the site went down, so I again began testing GitLab Pages and BitBucket until I landed on Netlify.