wordpress-to-jekyll-exporter VS jetpack

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.

JetPack

Uptime refers to the amount of time your website is available and accessible to users. Monitoring uptime is crucial as frequent downtime can negatively impact your SEO rankings and user experience. Tools like Uptime Robot, Pingdom, and Jetpack’s downtime monitoring can notify you the moment your site goes down, allowing you to take immediate action.

The former is possible, as mentioned here, but the latter isn't. Emails include no trackers. It is however possible that at some point in the future, email openings for Jetpack Subscription emails will be available as part of Jetpack Stats. This suggestion is currently tracked here.

If they are using Jetpack, they could be appearing in the WordPress Reader on the app.

I didn't spend time looking for specific features, as much as pointing out the standard is to be extremely hand wrangled and therefore prone to such issues. I have no idea if this sort of nonsense (this is an official Automattic plugin) is going to work in SQLite:

https://github.com/Automattic/jetpack/blob/2447e267e40f2d133...

But certainly creating a new table with ENGINE= which you can also find in that file isn't likely to work as intended on other platforms.

We must understand Jetpack for WordPress as an extension of WordPress functionalities that technically and theoretically should be included in the native WordPress base installation, but because that would overload the WordPress “core” a lot, they are distributed in a mega-plugin: Jetpack for WordPress.

Can anyone help with this? It's hard to believe that setting up shipping is this cumbersome. I'm assuming WordPress.COM wants you to install something else. I use WordPress.ORG. Yes, I've also set up JetPack.com. IDK what other rabbit hole Automattic tricks you into going down, but I've gotten this far and quite frankly, the front end should be much easier than installing Linux+AWS Infrastructure. Anyways can anyone help?

so THAT’S why my site using jetpack.com‘s site accelerator completely fucking melted

Not to mention that hovering over the link would've shown it was jetpack.com.