There were a couple of reasons for me to test out Windows 11, but the main reason was to give a new life to a device I hardly used anymore.
Ever since I bought my Mac Mini for the office, my previous desktop device (running Hackintosh) kept turned off. To make sticker printing easier in the office, I thought to give it a new life and install Windows 11. That way, I could see how cool/uncool it is compared to macOS.
Since I installed Windows 11, I started to like it. It is something new, but not only that. Windows has innovated over the years. With Windows Subsystem for Linux (WSL), it became pretty powerful and can use many tools I am used to on macOS.
I wanted to check how easy it is to get my blog developer workflow up and running on Windows 11.
For my blog, I am using Hugo for statically generating my website. Besides that, I use a couple of node.js scripts to create specific pages/content automatically.
On macOS, I would open my terminal and type
brew install hugo. I thought this would not work for Windows, so I went to the documentation. To my surprise, I found out that Homebrew also works on Linux.
WSL is what I will primarily be using because it makes Node.js-based solutions install and run faster and allow me to use NVM. So, Homebrew would be a great approach.
The steps I had to take:
- Install WSL:
wsl --install(optional if you have not yet installed it - more information on how to install WSL on Windows)
- Go to the Homebrew site, and copy the install script. Run the script in your WSL terminal instance.
- Once Homebrew is installed, you need to run a couple of extra commands to make it available (these can be found here: Homebrew on Linux):
- Now that the
brewcommand is available, you can run
brew install hugo.
- Once completed, you will have access to the
hugocommand, generate a new site, or build/serve an existing one.
Important Hugo will only be available in your WSL environment this way. This is not an issue on my end, as WSL is my primary terminal instance.