I rebuilt leilukin.com's Git repository, after realising that old versions and commits of my website, when I was a much less experienced web weaver, ended up ballooning the .git folder and the size of my repo to whopping 75 MB.
I also decided to move the majority of the images of leilukin.com to a dedicated subdomain for hosting files to avoid inflating the size of the website's Git repository.
Leilukin's Hub had been migrated from its original host on Neocities for almost a year, but I still log in to Neocities and share updates about my website.
After the migration, I posted about Leilukin's Hub's updates manually. However, inspired by Owl of Beep Bird, I am experimenting publishing the latest changelogs of Leilukin's Hub to Neocities to inform followers of updates, by making use of the Neocities command line interface (CLI).
Specifically, I wrote a shell script so after I generate the website output of Leilukin's Hub with Eleventy, I run the shell script to copy the Leilukin's Hub changelog page of the current year to a different folder for Neocities, then to use Neocities CLI to push the changelog page to my Neocities files.
I have converted the Git repository of Leilukin's Hub main site on 32-Bit Cafe's Gitea instance from a mirror repository to a regular repository.
Originally, Leilukin Hub's Git repository was hosted on GitHub, with its repo on 32-Bit Cafe's Gitea instance being a mirror. GitHub Actions were the primary reason for using GitHub to host Leilukin's Hub's Git repository, as GitHub Actions allow me to deploy my static websites to a remote server Hostinger.
Recently in March, 32-Bit Cafe's Gitea instance added support for Gitea Actions, which are compatible with GitHub Actions. This encouraged me to consider using Gitea actions to deploy Leilukin's Hub.
Therefore, yesterday I converted Leilukin's Hub's Gitea repository from a mirror repo to a regular repo, and today I finally managed to set up the deployment workflow with Gitea Actions!
As part of my effort of removing most favicon markup from my websites, I use ImageMagick, which can create ICO format favicons from one source of image file, by converting the source image to multiple resolutions in PNG (for higher resolutions) and BMP (for resolutions 192x192 and below) formats.
That said, I noticed that mobile version of browsers may be unable to fetch a favicon that includes more than one image format, so in my ImageMagick command line, I specified the output resolution to 192x192 as the highest, so the favicon will contain only BMP format images.
I removed the markup and unnecessary assets for my websites' default favicon from the HTML <head> tag, after learning more about favicons from Get out of my <head>'s guide, "Zero byte favicon markup".
The only pages where I still add a favicon markup are my shrine pages on the main site and my individual fanlistings, where I use icons relevant to the page's topic as the favicon.
I have set up SSH access to the server of my Hostinger premium shared hosting plan, including generating a pair of SSH keys for this server. This means now I can directly access my websites' folders and files from my local machine's terminal.
I have been trying to obfuscate my email address on Leilukin's Hub to hopefully stop email spams as much as possible. Today I came across this article that has the most comphrehensive list of methods to do so, along with the effectiveness of those methods.
Currently, I chose to use the CSS display: none and HTTP redirect methods.
Decided to create remote repositories for my tumbleblog and fanlisting collective on 32-Bit Cafe's Gitea instance, so in case I lost my local repositories, I can still pull from a remote copy.
My tumbleblog's repository is public at https://git.32bit.cafe/Leilukin/leilukin-tumbleblog
However, my fanlisting collective repository is private, since it contains sensitive data such as passwords.
My hobby websites' migration to Hostinger has finally completed.
Today's unexpected lifesaver for Leilukin's Hub is the CSS overflow-x: clip property, which turned out to be the solution to the unintended page overflow problem with the web pages that include both website buttons and tooltips when they are viewed on a narrow screen.