While I slide in to my new role as a Cloud Ops Advocate for Microsft Azure, I’ve been kicking around ideas for both learning the platform as well as showing off a few things you can do with the service.
Every so often I decide that my website (jasonhand.com) is dumb and needs a complete overhaul. But inevitably I run out of time or energy to do any of the work.
Reality and ambition don’t always play well together.
I’ve sworn off CMS systems such as Wordpress, Drupal, and Joomla due to excessive time spent troubleshooting bugs and plugin conflicts. The ROI for my efforts were ALWAYS extremely low.
Squarespace and many others make it stupid-simple to get a site up and running, yet there are limitations (and costs) associated with going that route.
A few other communities and projects that I’m involved with (DevOpsDays & the Community Pulse Podcast) both leverage Hugo (gohugo.io) for designing, building, and managing their site. So, I decided to go with that for my personal site as well.
Hugo may be one of the favorite new tools for faux-webmasters like myself but designing, building, and maintaining a site is only part of the story. I still have to host the site somewhere that can serve it up to the public.
Many who have fallen in love with Hugo uses services such as Netlify to deploy and host their site.
However, in just a few simple steps (6 to be exact) I can deploy and host my site on Azure. Since my site is static HTML, it doesn’t require a lot of compute resources and I can get everything up and running on a small (FREE) virtual machine (actually we’ll use an App Service).
And .. if for some reason my site begins to experience a high number of visitors or load on the resources, I can always scale up in a matter of seconds.
I’m not going to cover the process of getting Hugo setup and working in your development environment. The “Quick Start Guide” is where I always go to remind myself of the steps.
It’s fairly straight forward but I will give you this advice:
Choosing your theme should be one of the earliest steps.
It seems that slight variations in how themes are setup dictate how and where you’ll design and configure your site.
So play around with a few different themes. See how they are different and then choose the one that not only has the look and feel you like but you understand the Taxonomy of the site and which files you will need to edit (or create).
Once you have familiarized yourself with Hugo and you have your new site working in your development environment, I suggest placing the code of the site in to a version control repository system. I know. You are probably doing this already.. but some folks are still catching on to version/source control best practices. Hit me up on Twitter if you have any questions on this.
I’ll be using GitHub where I have a public repository that contains all files associated with my site. You can use a private one, but for the purposes of demonstration I’m leaving mine open.
When you’re ready, check out “Six Easy Steps to Deploying Static HTML on Azure”.