Migrating to Hugo
Migrating from Pelican to Hugo
1About 53,000 results (0.27 seconds)
If you put that title into a Google search query that is the number of results you come up with. I'll spare you the long winded article on the details, let alone it isn't quite relevant to make an automated script to perform the transfer when I only had 4 blog posts to begin with ;-).
Who knew static site generation was such an exciting blog topic? (Read: SEO optimization has gone too far)
Why migrate, or make a post about it at all?
I haven't updated this blog in some time, and I hope to change that. Life priorities change, and new chapters start, but that shouldn't mean that taking time to articulate your thoughts, especially in an age where more content will be purely produced by AI, without a human aspect to it.
I recently fell into a software role professionally that relies on using Go for our infrastructure, and I enjoyed diving deep into becomming proficient in developing with it, especially coming from a science role mainly focused on python and analysis. Thus it's nice to play around with products made in the language you are dealing with at the time.
Hosting methods
In addition to changing static site generators I have also changed hosting methods. This site was originally hosted by a google cloude engine VM running NGINX with a static IP, since then it has now changed to hosting on google cloud storage.
Conclusion
- Yet another blog post on migrating static site generators.
- Revitalizing a blog by making it easier to deploy posts
- Here is to 2025