Further comments.
SEO
If you are generating a **sitemap.xml` file, I would recommend also setting this in your config. Including protocol. And no trailing slash or path.
url: https://example.com
So that the absolute URLs with the full domain will appear in your sitemap file.
<url>https://example.com/about.html</url>
Besides the sitemap, you’ll want to have pages on your site setup as relative URLs without the domain.
e.g.
<a href="/about.html">About</a>
<link href="/styles.css">
If you use a subpath like my site - https://michaelcurrin.github.io/jekyll-blog-demo/
Then you will need to make that a relative URL and set baseurl in config as /my-repo
.
Use the link
tag to give you an error if the page does not exist, plus it will add the prefix for you.
<a href="{% link about.md %}">About</a>
<link href="{% link styles.css %}">
Result:
<a href="/my-repo/about.html">About</a>
<link href="/my-repo/styles.css">
Automated deploys
I’m assuming you manually deployed to a self-hosted server or used FTP.
I highly recommend rather using a platform like Netlify or GitHub Pages to deploy your site. Free hosting, free automated deploys, no servers to manage. And you can add your bought custom domain on top of the site at no additional cost!
Netlify will support Jekyll 4 and custom plugins. GitHub Pages by default will not.
My Netlify site
My guide to configuring Netlify - Configure | Code Cookbook
You only need a config of a few lines!
If you want to use GitHub Pages and also Jekyll 4 (to override the default 3.9), then you’ll need GitHub Actions to deploy your site for you. I setup a site like that. See .github
directory. That config is much longer than the Netlify one but it does the same thing.