Leilukin's Hub

Changelog: 21 November 2024

2024-11-20T16:55:40Z

Officially launch my Pokémon Omega Ruby and Alpha Sapphire shrine to celebrate the 10th anniversary of the games' release.

Changelog: 19 November 2024

2024-11-19T14:19:00Z

Expand the home page of my Cassette Beasts shrine by adding a "Cassette Beasts — My Ultimate Comfort Media" section.

Changelog: 28 October 2024

2024-10-28T09:17:22Z

New blog post: "Re: Social Media Hasn't Killed the Personal Blog Just Yet"

Re: Social Media Hasn't Killed the Personal Blog Just Yet | Blog

2024-10-28T09:16:14Z

Jim Mitchell wrote a blog post, "Social Media Hasn't Killed the Personal Blog Just Yet", discussing the decline of personal blogs after social media took off, and the question of if social media killed personal blogs, and if personal blogging can make a comeback. This post caught me by surprise when I discovered it, because recently I have been reflecting on my blogging history, and how social media changed that, with my thoughts ended up being incredibly similar to Jim's.

Blogs have always had a special place in my heart and my history with the web, because blogging was my first foray into creating things and sharing things about myself on the web way back in the 2000s as a teenager. Teenage me was deeply fascinated by the concept of writing a personal journal on the web, and being able to connect with other people on the internet through reading and commenting on each other's online journal. I have loved writing and like to express myself through writing since I was a child, so blogging seemed to be a great way to do so.

Then social media began to take off. Jim Mitchell wrote:

Personal blogs didn’t just disappear in one big poof. It was more like a slow fade. As Facebook, Instagram, and Twitter took off, people – me included – found it easier to share bite-sized pieces of life. Why write a long, reflective post to publish on your personal site when you could sum it up in a quick status update that some “friend” you don’t really even know could give you a mindless like?

I can attest to that, because I was there when bloggers began to use social media, and how social media platforms gradually replaced their personal blogs as means share their thoughts and life updates. I was introduced to Facebook in the late 2000s by other Malaysian Chinese bloggers. As more of us bloggers use Facebook, updates of our personal blogs have gradually decreased.

Jim Mitchell's post talked about the shift to niche or professional blogging, which is a phenomenon I have noticed as well. I do not think blogs ever died, and in fact, even before discovering the personal web and coding my own website from scratch for the first time in 2022, I still found niche blogs to follow and subscribed to their RSS feeds, but social media and search engine optimisation (SEO) have made personal blogs obscure and more difficult to find than niche and professional blogs.

That said, exploring the web outside social media and seeing the resurgence of personal websites and blogs on platforms like Neocities and Bear Blog, gave me hope. I am happy to see people on the personal web are bringing back personal blogs too, which motivated me to include a blog to my website.

As Jim Mitchell concluded in his post:

Is social media the death of the personal blog? Not quite. It may have nearly killed it, yes. But for those of us willing to carve out our own space in the digital landscape, personal blogs still have a heartbeat. It just takes more effort to keep it alive.

Changelog: 17 September 2024

2024-09-17T05:58:34Z

Add Pantson Color Club section to my adoptables page, including my own colour card for the pixel club.

Changelog: 6 September 2024

2024-09-06T15:16:00Z

Replace the estimated reading time of articles and blog posts with word count, by using the eleventy-plugin-wordcount-extended plugin.
Create 200×40 pixel size version of Leilukin's Hub site button.

Changelog: 18 August 2024

2024-08-18T12:33:42Z

New blog post about me officially becoming a professional web developer, "From Hobbyist to Professional Web Developer".

From Hobbyist to Professional Web Developer | Blog

2024-08-18T12:28:21Z

I am pleased to announce that I am officially a professional web developer now — starting from 16 August 2024, I am working for a local traditional Chinese medicine (TCM) healthcare company, with my job involving web development, UX design and graphic design. I owe much to this very website for inspiring me to pursue web development as a profession.

My Web Design Origin Story

My interest in web design and development go back as far as my teenage years in the 2000s. I had a GeoCities account, but by the time I started to participate on the web when I was around 14, blogs were on the rise, so blogging was my first foray into creating on the internet, so I did not experience creating and coding a personal website like other GeoCities users did. That said, I got my start on HTML and CSS through blogging, by editing the codes of widgets and blog themes, while being inspired by many other blogs.

In particular, there was a Taiwanese blogger who was a professional designer whose blog had a gorgeous header made with Flash, who ended up being an inspiration for me to aspire to become a graphic designer when I grew up. I did study graphic design, earn a diploma and began working as a graphic designer. However, years in the field, I got burned out; there were multiple factors contributing to my burnout from the graphic design field, but the short version is that the reality of graphic design work, at least in my experience, did not turn out as great as what my younger self had expected and hoped for.

Rekindled Interest in Web Design

Fast forward to 2022, my interest in web design was rekindled when I discovered Neocities through Tumblr and the resurgence of creating personal websites, so I decided to build and code my own website to gather various stuff I have created and curated across various online spaces. For this, I re-learned HTML and CSS, and began to truly experience the joy of carving one's own space on the web, and the more I worked on my website, the more I learned about not only web design, but also web development, by dabbling in JavaScript.

Furthermore, despite being burned out from graphic design as a profession, my graphic design background does come in handy in building Leilukin's Hub, by designing and creating graphics for my website, including header image, site button, favicon, etc., as well as applying my design knowledge and skill to design my own website, from colour schemes to layout.

Web Development: More than a Hobby

Over time, my interest in web development evolved enough to take online coding courses, starting with freeCodeCamp, then Scrimba shortly after. Taking these courses made me realise that these languages have evolved a lot since more than a decade ago. I applied the HTML, CSS and JavaScript skills and knowledge I learned from these courses to make improvements to my website.

Meanwhile, learning that there were people who became developers without a computer science degree inspired me to consider switching my career path to web development. In other words, web design and development have become more than a hobby to me. I did not expect it to be easy, so I did put as much as I could in learning and practising web development. That said, Leilukin's Hub remains a hobby project, and it serves as a good platform for me to practice and experiment my front end web development.

After teaching myself to code for almost two years, and received multiple code and tech-related certifications, I updated my résumé with information about my interest in switching career from graphic design to web development, and hope for transferring my creativity and design expertise into building the web. I started to try hunting for front end web developer jobs, but my attempts to apply for the job for many companies did not succeed, then I received a surprised belated birthday present in the form of a job interview invitation.

New Job Interview: A Surprise Belated Birthday Present

On 29 July 2024, a day after my birthday, I received an invitation by the managing director of a local traditional Chinese medicine company to attend an interview with him. The company was looking for someone with web development expertise to work on and improve their website, which is built with WordPress, and the managing director discovered my résumé on a Malaysian job hunting website I had registered an account on.

During my interview, I explained to the managing director that I have been looking to switch career from graphic design to web development. Turned out, the company was also interested in hiring a web developer with design expertise to improve the front end of their website, so my 8 years worth of graphic design experience was a bonus. A week after the interview, the managing director sent me a job offer, and I accepted and got hired, with my responsibilities include web development, UX design and graphic design.

WordPress Developer by Day, Eleventy Developer by Night

Starting my professional web development journey with WordPress is going to be a new experience for me. I had brief experience with working on WordPress websites as a website administrator in one of my previous jobs, but never as a developer. Furthermore, prior to receiving this job offer, I never studied WordPress development, nor built my own website with WordPress.

That said, I hope to apply the programming knowledge and skills I learned from the coding courses I had taken to adapt to learning WordPress development. My confidence in my ability to learn new tech skills was bolstered by the time I created a fork for the fanlisting script BellaBuffs with SMTP support despite my inexperience with PHP. I am looking forward to learning more about PHP with my new job as well.

Although now I work on WordPress in my day job, my personal website will continue to be built with Eleventy. One of the reasons I wanted to pursue web development as a profession is the freedom to learn and use different tools outside day job while continuing to grow as a developer.

None of the coding courses I took taught about Eleventy or any static site generator, but rebuilding Leilukin's Hub with Eleventy in April 2024 allowed me to learn more about web development, not to mention I do have a lot of fun with using Eleventy. Therefore, I am content to be a WordPress developer by day, Eleventy developer by night.

Wrapping Up

Looking back, even I am amazed by the fact that building this very website kickstarted my path to become a professional web developer, especially since I did not come from a tech educational or industrial background, but I am glad that it happened.

I am happy to be able to switch my career path to web development despite not having a computer science degree, and that my prior working experience as a graphic designer helped with getting this new opportunity.

Changelog: 11 August 2024

2024-08-11T14:46:00Z

Improve the site's RSS feed:
- Make RSS feeds automatically discoverable by feed readers
- Use time and time zone to make feed items' timestamps accurate

Changelog: 6 August 2024

2024-08-06T13:20:00Z

New article: "How I (Tried to) Implement Accessible Footnotes", which is also my entry for 32-Bit Cafe's Community Code Jam #5: Back to School.

How I (Tried to) Implement Accessible Footnotes | Articles

2024-08-05T16:04:00Z

(32-Bit Cafe "Back to School" button made by Loren)

32-Bit Cafe is holding its fifth community code jam, titled "Back to School", from 4 to 17 August 2024. I have been looking forward to participating in 32-Bit Cafe's community code jam for the first time, so I am excited. This motivates me to finally write a how-to article I have been meaning to do for a while: how to implement accessible footnotes on Leilukin's Hub, or at least, I tried to do so to the best of my abilities.

On 32-Bit Cafe's Discourse forum, I made a post on 28 June 2024 in response to solaria's thread "Handling Citations and/or Footnotes" to share my methods of adding footnotes on my website. Now, I am writing an extended version of that post of mine in the form of this article, so I could share what I learned about web page footnotes on my website as well.

(Note: This article assumes a foundational familiarity with HTML and CSS)

About Footnotes

Plagiarism.org defines footnotes as notes placed at the bottom of a page, and what footnotes do is to cite references or comment on a designated part of the text above it.

My use case of footnotes is citing sources of information, particularly citing the same source multiple times on the same page when information from the same source is spread across my page. As of this writing, my website pages that use footnotes include the trivia page of my A Summer’s End — Hong Kong 1986 shrine 1 and the facts page of my Cassette Beasts shrine. You are free to look at the HTML and CSS for reference, including when you are reading this article as I am explaining how I implement the footnotes.

Footnotes are used both on print and on the web. However, maintaining footnotes on the web can be tedious, especially if you want to update a web page to add or remove them, since you will need to change the number references of existing footnotes.

Attempted to Use CSS Counters

When I was searching for how to implement accessible footnotes, I discovered Kitty Giraudel's article, "Accessible Footnotes with CSS" which teaches the method of using the combination of HTML aria-describedby attribute and CSS counters to add numbered references, to reduce the hassle of manually re-numbering all existing footnotes in case you want to update or reorder the references.

Her article also teaches adding a highlight background colour when heading to a footnote from a reference, as well as providing back links to head back to a reference from a footnote, by using the combination of the backlink Unicode icon (↩) and the HTML aria-label attribute with a value of “Back to content”. The uses of ARIA labels make footnotes more screen reader-friendly.

Furthermore, Kitty created the eleventy-plugin-footnotes plugin for the static site generator Eleventy, and wrote a blog post about it, "Footnotes in 11ty". Since I already had begun to use Eleventy to build my website, I tried Kitty's plugin.

Unfortunately, a known limitation of using CSS counter method to generate footnotes is not being able to reference the same footnote multiple times. As I want to be able to reference the same footnote more than once when I am citing sources on my shrine pages, I had to give up the plugin and look for an alternative.

Starting with markdown-it-footnote Plugin's Default Footnote Markup

Kitty Giraudel's blog post about creating footnotes in Eleventy mentioned markdown-it-footnote, the footnotes plugin for markdown-it Markdown parser, which is integrated in Eleventy by default to convert Markdown to HTML. Kitty commented on the accessibility shortcomings of markdown-it-footnote in the blog post:

[...]it’s not super accessible (let alone by default), even considering all the customisation options. That’s because the footnote references end up being numbers (e.g. [1]) which are meaningless when listed or tabbed through because devoid of their surrounding context.

That said, since the plugin is customisable, I still wanted to give it a shot to see if I could make configurations to improve its accessibility, so I installed markdown-it-footnote and looked into the plugin's default HTML markup output.

Here is a sample of what the HTML markup output of markdown-it-footnote looks like:

<p>This is a paragraph with the first footnote reference. <sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup></p>

<p>Here is the second paragraph with the second footnote reference. <sup class="footnote-ref"><a href="#fn2" id="fnref2">[2]</a></sup></p>

<p>This the third paragraph, but with a foootnote reference that points to the first footnote. <sup class="footnote-ref"><a href="#fn1" id="fnref1:1">[1:1]</a></sup></p>

<hr class="footnotes-sep">
<section class="footnotes">
    <ol class="footnotes-list">
        <li id="fn1" class="footnote-item">First footnote <a href="#fnref1" class="footnote-backref">↩︎</a> <a href="#fnref1:1" class="footnote-backref">↩︎</a></li>
        <li id="fn2" class="footnote-item">Second footnote <a href="#fnref2" class="footnote-backref">↩︎</a></li>
    </ol>
</section>

This is what this HTML markup will look like on a live web page:

What this HTML markup does:

Adding a footnote reference as a superscript by using the <sup> tag with numbers as the content.
Using a <hr> horizontal line element to separate the main body of the page and the footnote section;
Using the <ol> tag to render the footnotes as a numbered list;
Each footnote list item has an id attribute
If a footnote is referenced more than once, the additional footnote references are labelled with colons.

(Note: the class names were added by markdown-it-footnote, but if you do not use it, you can rename the class name to whatever you want, and even if you use markdown-it-footnote, you can still change the class names if you want to go deep into it)

Next step is trying to improve this HTML markup by making it accessible.

Make markdown-it-footnote's Markup More Accessible

Clarify Footnote Reference Labels

As pointed out by Kitty Giraudel, labelling the footnote reference as mere numbers like [1] is an accessibility shortcoming, because these reference links become meaningless when being focused on by tabbing through the links, as these reference links would be devoid of context.

What I did to tackle this was changing the reference labels by adding a word "Footnote" to clarify that these links are for footnotes. For example, [1] becomes [Footnote #1], so when screen readers focus on a footnote reference link, it will be read out as "Footnote number one link".

<sup class="footnote-ref">
	<a href="#fn1" id="fnref1">[1]</a>
</sup>

Optionally, if you want your footnote labels to still display only numbers on screen, you can use a CSS class to visually hide the extra characters in the footnote label. This .visually-hidden utility class is a useful tool in your arsenal for accessible web design, as it is often used to hide a content that you do not mean to show on screen, but you still want it to be read by assistive technology.

.visually-hidden {
    clip: rect(0 0 0 0);
    clip-path: inset(50%);
    height: 1px;
    overflow: hidden;
    position: absolute;
    white-space: nowrap;
    width: 1px;
}

To make my footnote reference labels display only a number on screen, I use a span tag with visually-hidden as the value of the class attribute to wrap around "Footnote #", so on screen, [Footnote #1] is changed to [1].

<sup class="footnote-ref">
	<a href="#fn1" id="fnref1">
		[<span class="visually-hidden">Footnote #</span>1]
	</a>
</sup>

Add ARIA Label to Footnote Back Links

Next step is adding an ARIA label to the footnote backlinks, by adding an aria-label attribute with "Back to reference #[Insert reference number]" as its value. For example:

<a aria-label="Back to reference #1" href="#fnref1" class="footnote-backref">↩︎</a>

When a footnote back link is focused on via tabbing, screen readers will read it out as "Back to reference number one link".

Add Heading to Footnote Section

To make it clear that the section is for footnotes, I add a HTML heading before the list of footnotes, such as:

<h2>Footnotes</h2>

Final HTML Markup for Accessible Footnotes

Here is my final HTML markup sample to create accessible footnotes:

<p>This is a paragraph with the first footnote reference. <sup class="footnote-ref"><a href="#fn1" id="fnref1">[<span class="visually-hidden">Footnote #</span>1]</a></sup></p>

<p>Here is the second paragraph with the second footnote reference. <sup class="footnote-ref"><a href="#fn2" id="fnref2">[<span class="visually-hidden">Footnote #</span>2]</a></sup></p>

<p>This the third paragraph, but with a foootnote reference that points to the first footnote. <sup class="footnote-ref"><a href="#fn1" id="fnref1:1">[<span class="visually-hidden">Footnote #</span>1:1]</a></sup></p>

<hr class="footnotes-sep">
<section class="footnotes">
	<h2>Footnotes</h2>
    <ol class="footnotes-list">
        <li id="fn1" class="footnote-item">
	        First footnote
	        <a aria-label="Back to reference #1" href="#fnref1" class="footnote-backref">↩︎</a>
	        <a aria-label="Back to reference #1:1" href="#fnref1:1" class="footnote-backref">↩︎</a>
	    </li>
        <li id="fn2" class="footnote-item">
	        Second footnote
	        <a aria-label="Back to reference #2" href="#fnref2" class="footnote-backref">↩︎</a>
	    </li>
    </ol>
</section>

As for the CSS, in addition to using the .visually-hidden utility class, I refer to Kitty Giraudel's "Accessible Footnotes with CSS" article to style the highlight background color when heading to a footnote from a reference.

Configure markdown-it-footnote in Eleventy's Configuration File

(If you do not use Eleventy, you may skip this section)

My final step was to configure the markdown-it-footnote plugin, by editing Eleventy's configuration file (I named mine eleventy.config.js), so the plugin would render my accessible footnote HTML markup.

// markdown-it plugins
const markdownIt = require("markdown-it");
const markdownItFootnote = require("markdown-it-footnote");
let markdownLibrary;

module.exports = function (eleventyConfig) {
    /* Markdown Overrides */
    markdownLibrary = markdownIt({
        html: true,
    }).use(markdownItFootnote);

    // Configure markdown-it-footnote
    markdownLibrary.renderer.rules.footnote_block_open = () => (
        '<hr class="footnotes-sep">\n' +
        '<section class="footnotes">\n' +
        `<h2>Footnotes</h2>\n`
    );

    markdownLibrary.renderer.rules.footnote_anchor = (tokens, idx, options, env, slf) => {
        let id = slf.rules.footnote_anchor_name(tokens, idx, options, env, slf);

        if (tokens[idx].meta.subId > 0) id += `:${tokens[idx].meta.subId}`;

        /* ↩ with escape code to prevent display as Apple Emoji on iOS */
        return ` <a aria-label="Back to reference #${id}" href="#fnref${id}" class="footnote-backref">\u21a9\uFE0E</a>`;
    };

    const renderRules = {
        footnote_caption: ['[', '[<span class="visually-hidden">Footnote #</span>'],
    };
    Object.keys(renderRules).map(rule => {
        let defaultRender = markdownLibrary.renderer.rules[rule];
        markdownLibrary.renderer.rules[rule] = (tokens, idx, options, env, self) => {
            return defaultRender(tokens, idx, options, env, self).replace(...renderRules[rule]);
        }
    });

    /* This is the part that tells 11ty to swap to our custom config */
    eleventyConfig.setLibrary("md", markdownLibrary);
}

If you are a fellow Eleventy user, feel free to borrow my markdown-it-footnote configurations in your own. Make sure you install markdown-it-footnote first by keying in the installation command in the terminal:

npm install markdown-it-footnote --save

Bonus: Alternatives to Footnotes

As you likely have realised, footnotes are really tricky to implement on web pages, so you may be wondering: is there any alternative to footnotes?

For extra comments and tangents, by favourite approach is using HTML's details disclosure element with the <details> tag, with a <summary> element and a sibling element wrapping the content displayed when the disclosure is expanded.

I have been using the disclosure element for additional comments or information on this website, like in my blog post, "My Cassette Beasts Fanlisting Application has been Approved". As for the styling, initially I indented the content inside the disclosure to differentiate the disclosure content from the rest of the content of the page, but recently I switched to adding top and bottom borders after being inspired by Starbreaker's website, who also has a post about footnotes, "Footnotes: No Fun to Create, Either".

More ways to use <details> and <summary> elements

<details> and <summary> have become among my favourite HTML elements due to how useful they are. In addition to extra comments and info, Leilukin's Hub has also used the elements for the following purposes:

Table of contents, like the one this very article has
Hiding spoilers, like in my Cassette Beasts shrine article, "How Cassette Beasts is Much More than a Pokémon Clone"
Content warnings, like in my A Summer’s End — Hong Kong 1986 shrine's gallery page, with its styling being inspired by another Kitty Giraudel's blog post, "A content warning component"

As for citing sources, the simplest way would be naming and linking to the source in the main text of your page, though it does mean you may end up repeating the title of the source if you want to attribute to it more than once on your page. This was once the approach of my shrine pages, though I found the pages looked rather cluttered, so I eventually chose to use markdown-it-footnote alongside Eleventy.

Wrapping Up

Creating and maintaining footnotes on web pages is tricky, so I hope my article about accessible footnotes is helpful if you want to create them.

I am still not completely certain if my method is the best, although I tried to the best of my abilities, so I am interested in hearing feedback for my way of implementing accessible footnotes.

Changelog: 2 August 2024

2024-08-02T07:42:00Z

Added my first publicly released code snippet on this website: Responsive Disability Pride Flag CSS Background.

Leilukin's Hub Has Migrated to Hostinger | Blog

2024-07-26T16:44:00Z

Starting with 25 July 2024, Leilukin's Hub and all its subsites, including its tumbleblog and fanlisting collective, have been migrated to Hostinger. In other words, I have moved hosts again almost two months after moving Leilukin's Hub to Netlify.

Before talking about why I chose Hostinger as my new website host, I want to talk about why I was considering to move hosts again.

Why Decided to Move Hosts Again

Owning Both Static and Dynamic Sites

The first major reason is that leilukin.com has evolved into more than a static site; since I have also begun to dip my toe into PHP to build dynamic sites, including a tumbleblog, fanlistings and a fanlisting.

Netlify, which previously hosted the main site of Leilukin's Hub, does not support PHP hosting, so I hosted my tumbleblog and fanlisting collective on InfinityFree, one of the very few platforms to provide PHP and MySQL website hosting for free. InfinityFree has been a decent platform for PHP and MySQL beginners to experiment with the languages, however as you might have expected, its free hosting plan comes with limitations.

Limitations of InfinityFree's Free Hosting

InfinityFree places their own security measures on websites on their free hosting plan to ensure only regular browsers can access these websites. While it is understandable to apply these security measures on free websites to prevent abuse, it can be a dealbreaker depending on your needs.

In my case, the thing that frustrated me the most about InfinityFree's security system on their free websites is the fact that my tumbleblog was unable to provide RSS feed in a usual way. Chyrp Lite, which powers my tumbleblog, includes the feature of providing blog RSS feeds, but InfinityFree's security system blocks feed readers from reading feeds from websites on their free hosting, so I had to use Feedburner to proxy my tumbleblog's feeds to get around it.

Invested in Webmastery Enough to Spend Money

Lastly, I am invested in building my own websites enough to spend money on them, as already evident in my purchase and registration of a custom domain name leilukin.com for this website.

That said, I do need to consider carefully about how much money I am going to spend on my hobbies, which factors in why I eventually chose Hostinger to host my websites.

Why Hostinger

Affordable Price with Regional Pricing

The biggest draw about Hostinger is its pricing — it is not only cheap, but also offering regional pricing. This is a huge deal for people who live in countries with weaker currencies than US Dollars and Euro, as the pricing scales to the level we are more comfortable spending, without worrying about currency conversion rates.

For reference, as of this writing, 1 USD equals approximately 4.6 Malaysian Ringgit (MYR), while the minimum wage in Malaysia is 1,500 MYR, which approximately equals to 321.03 USD, per month. Therefore, if a Malaysian like me is going to spend money, every USD counts.

Compare the pricing of the 48-month Premium Shared Hosting plan, which was what I ended up spending to host my websites, of Hostinger.my to Hostinger.com: The plan costs 7.99 per month in MYR (approximately 1.71 USD), while 2.99 per month in USD (approximately 13.97 MYR). This means I ended up saving almost 6 MYR per month by purchasing the plan on the Malaysian branch of Hostinger. This is just comparing Hostinger's own hosting plan with different currencies, let alone comparing Hostinger's hosting plan to its competitors.

As a bonus, being able to purchase Hostinger's hosting plans in Malaysian Ringgit means I can pay by directly transferring money from a Malaysian bank account.

Being cheap is not even the only reason I chose Hostinger; what is better than being cheap is to provide many, many features at the same time.

Many, Many Features at a Cheap Price

The cheap price of the Premium Shared Hosting Plan of Hostinger is jam-packed with many features, including but not limited to:

Ability to create up to 100 websites (Netlify allows you to deploy 500 sites, but 100 sites are still significantly more than enough for average users)
100 GB SSD storage
Unlimited bandwidth (InfinityFree's free hosting also allows unlimited bandwidth, but Netlify has a limit of 100GB per month)
Unlimited MySQL databases (while Infinity has a limit of 400 databases)
Email accounts included for free
Built-in Git support, which allows me to continue deploying my main site from its Git repository
And more!

On the subject of email accounts, it is worth pointing out that Hostinger's Premium Shared Hosting plan allows you to create an email account for each website you made, and you can have up to 100 addresses and forwarders for each email account.

A Birthday Present for Myself

Last but not least, another motivator for me to purchase a premium website hosting plan for my websites now is the fact that my birthday is coming soon on July 28, so I spent money on premium hosting for my websites as a birthday present for myself this year.

Domain Names Remaining at Porkbun

While Hostinger provides domain registration and transfer service, I chose to have the leilukin.com domain name stay with Porkbun, because I already spent money on the domain name, so Hostinger's hosting plan providing domain name registration for free for the first year does not benefit me.

In addition, Porkbun's renewal rate for domain names is cheaper than Hostinger. For example, Porkbun renews the .com domain extension at 10.37 USD per year, while Hostinger renews at 15.99 USD per year. Even the Malaysian Ringgit pricing of Hostinger's domain renewal rate for .com, 55.99 MYR per year, is still more expansive than Porkbun's approximately 48.3 MYR per year rate.

Wrapping Up

Leilukin's Hub's migration to Hostinger has been smooth. There was no significant change on the front end of my websites after the switch, aside from changing the theme of my tumbleblog, so my websites will continue to operate as usual, as well as improved site performance for my tumbleblog and fanlisting collective by loading custom web fonts faster to the extent I intended by preloading the fonts.

Moving hosts for my website again reminds me of one of the benefits of owning a custom domain name of making the host migration more seamless, since it saves the trouble of having to change and update my website's address every time I move hosts.

Changelog: 27 July 2024

2024-07-26T16:32:00Z

Leilukin's Hub and all its subsites have been migrated to Hostinger
New blog post: Leilukin's Hub Has Migrated to Hostinger
Change the theme of Leilukin's Hub Tumbleblog to a custom theme based on the Umbra theme from Chyrp Lite
Add a link to contact me via email to the website's footer

Changelog: 22 July 2024

2024-07-22T01:35:00Z

Add a Salad Magazine section to my Adoptables pages.