Blog Migration Tips

Why I move the blog

My previous blog was hosted in GitHub, using Jekyll-now. The main reason to again move my blog is the will power needed to maintain the blog is annoyingly high. This took away time from the actual writing itself. So I have been thinking about moving the blog for a while. I need a platform where that is not too time consuming to post and maintain a blog.

That is when came across Hashnode. The main features that sold me on Hashnode was simple export feature and GitHub backup, also no charge for custom domain, and (what I previously thought) custom CSS.

The experience moving to Hashnode

The moving was not at all painful. I used the bulk import from markdown feature, and Hashnode takes care of 80% of the problem. The rest is making sure the post have the right images and tags.

The tags part is a bit annoying, since Hashnode did not import any tags from my markdown🤷‍♂️. For images, luckily, I do not have a lot of post with images. But to avoid future pain, for when I inevitably move to another platform again, I am now hosting them in google photos instead of locally on the blog platform.

For now, let see how if I beat the previous record in Jekyll (Nov 1st, 2019 - August 8th, 2024).

Moving the blog

Comments

More from this blog

Detection Pipeline for CloudTrail Detection Engine

About idleak.net

CloudTrail Detection Engine

If I were to start validating my cloud detection...

What Are Indicators of Compromise (IOCs) and Why Do They Matter?

Why I move the blog

The experience moving to Hashnode

Command Palette

Comments

More from this blog

Why I move the blog

The experience moving to Hashnode