Moving to Hugo from Wordpress
A static site generator offers all the goodies of CMS systems like WordPress — templates, content types, taxonomies, menus, shortcodes, etc. As well as some advanced features like minifying all your site assets when it's built.
The beauty is that once you've created your site, the static site generator takes the source files you've used to create your website, and then generates them into entirely static HTML pages.
There were a few reasons that pushed me to make the move. My site is so simple, even something like WordPress seemed overkill. In a nutshell, here were my reasons:
- Simplicity. A static site keeps it simple. No need to pull out unwanted/unneeded functionality from Wordpress. You build a static site from the ground up and make it as simple or complex as desired.
- Performance. With a static site, there is little to no server-side functionality. No database queries, template building, and no processing on each request.
- Security. As said with performance, a static site has little or no server-side functionality. No login page. You can't access it via scripting or database security holes.
- Reliability. At the end of the day, it's only a web server serving static HTML pages. I don't have to worry about the fat-fingering something in the code that will 500 the site or cause a database connection error.
Now every time I push changes to my git repository, Netlify will re-build and re-deploy the site — automatically.
Netlify has a super simple step-by-step walkthrough on how to set this up.
At the end of the day, the biggest win in making the move was that it made building a website fun again. Once you get the hang of it, everything about a static site generator is easy — the syntax, theming, building, deploying — everything.
Here's to a static site! 🍻