In this post I’m going to cover the process I went through to integrate the Partytown library into my Hugo static website.
So what is Partytown? For anyone who hasn’t heard of Partytown, it’s a library by the team at builder.io that moves script processing off the main thread and into a web worker. This is ideal for any third-party asynchronous code that runs on a typical website like analytics, metrics, A/B testing or advertising.
What was covered last time? In the last post, I covered:
Why you should migrate to .NET Core What is .NET 5 and why you don’t need to wait until it is released to migrate My personal high level process for approaching the migration of large applications Explored the first two parts of the migration process, planning and pre-migration Went over what work can and should be performed prior to starting the .
What I’ll cover in the series I’m sure everyone in the .NET ecosystem has heard of .NET Core now, and most people have at least given it a little go.
If you are part of a team that owns any .NET Framework applications, the question will no doubt have been raised of can/when/should we migrate to .NET Core?
Microsoft has some articles and documentation on migrating, however I found detailed information on the process and the various gotchas hard to come by, so I thought it would be worth sharing my own experiences.
The #immutable dream I’ve always loved the idea of having an immutable workstation (with the exception of data storage of course 😝). A PC where you can just blow it away by rebooting and you are back to a known-working state. I’ve looked into many options like VM’s or one-off scripts to install everything - even products like Deep Freeze - but nothing suited all my needs.
What I wanted In order of importance
Inspiration I’ve always been interested in building things to find out how they work, even if it’s something that’s already been done before. My inspiration for this project came when I saw a Hacker News post by Blake Smith showing his adventures in building a USB keyboard.
I was originally thinking of building a full sized keyboard, but I changed my mind after having to enter a load of GUIDs whilst debugging at work.
I recently decided to rebuild my personal website. I made the decision to use Hugo to build out the sites content. For more background on why I chose Hugo, you can read my previous post.
I also made the decision to avoid using any server-side hosting. For all of the details around this decision, again, you could check out my previous post 😏. But the tl;dr of those reasons is:
Just the other day, I decided to rebuild my personal website. This post covers my decision around using Hugo to build out the sites content.
Why not Wordpress? When rebuilding this site, one of my goals was to try and avoid any server-side hosting. There were a few reasons behind doing this:
My site is static content, it doesn’t change apart from when publishing new content - I didn’t even need a contact form