From Jekyll to Hugo! From GitHub Pages to Netlify!
After a few years of blogging using Jekyll, my website became slow and I stopped enjoying working on fresh content. The effortless integration of this static site generator with GitHub Pages was the only reason why I kept this setup for so long. A smart quote always looks good on a geeky article, so let me smash one by Benjamin Franklin.
“When you are finished changing, you’re finished.”
From Jekyll to Hugo
Jekyll is a great tool and its integration with free GitHub hosting makes it a great pairing to host a tiny website like this one. I elaborate on this setup in a post from three years ago: “Jekyll blog on Github Pages supercharged by CloudFlare”. This website has grown up since then and the Ruby based engine started showing up some performance issues. Enabling incremental regeneration via the
--incremental flag didn’t give my project enough of a boost. The moment for change had arrived.
Looking for a Jekyll replacement didn’t take me long despite the fact that the list of static site generators is enormous. Performance, great documentation and simplicity is all I need — Hugo seemed to be a perfect candidate. It is written entirely in Go which has been made famous by its concurrency (processing of multiple tasks simultaneously). Setting up your first project takes no time at all and the fantastic documentation makes adding custom functionality on top of it a breeze. I am not the only one who thinks that Hugo is fab! Smashing Magazine, 1Password and Let’s Encrypt are also big fans just to name a few.
As a result of this transition I have a smooth workflow, instant builds and most importantly I really enjoy blogging again. The compilation time hasn’t been reduced from minutes to seconds, but to milliseconds. To rebuild over a hundred articles on this page Hugo doesn’t choke at all — 200ms is all it needs. Thank you Bjørn Erik Pedersen, Steve Francia and rest of the team for building this tool!
From GitHub Pages to Netlify
GitHub Pages served me well for years and the continuous integration with Jekyll projects allowed me to forget about things like hosting. Migrating from Jekyll to Hugo forced me to do some research. Although Hugo can be easily hosted on GitHub Pages, I recently heard a lot of good things about Netlify.
If you have never used Netlify and you think that your hosting solution is simple, you’re living a lie my friend. It has a drag and drop interface, an amazing CLI (command line interface), continuous integration with GitHub projects, custom domain management, HTTPS certificates provided by Let’s Encrypt, HTTP 2.0 and tons of other cool features in the free tier. The documentation is superb and full of screenshots, video explainers and code snippets.
The website that you are reading now has been published via a simple
git push, built on a Netlify server and deployed to a powerful content delivery network. Could it be easier?
I swear, neither Hugo’s creators or the Netlify team paid me to throw so many compliments their way. The source code for this website is available on my GitHub account. Got questions? As always I am more than happy to help. Until next time people 🤪
Cool Hugo has an impressive showcase. I am currently using Pelican + AWS for my static site. Seems to work pretty well, but I probably don't have so many articles as you. I have definitely pushed Pelican to its limits though, am often finding things that are tricky to implement. It's troublesome to move away from however as my theme is build entirely from scratch.
I have no experience with this static site generator, but I would suggest moving hosting away from AWS to Netlify. I cannot explain why, but please try Netlify once and you will never look back :)
https://uploads.disquscdn.c... Yes Grandma, I'm almost positive Arachnophobia is not the fear of people from Iraq
https://uploads.disquscdn.c... Why does O.J. Simpson claim that he's not a murderer? He's an ex-murderer.
I am thinking about start blogging and I feel like Hugo + Netlify is definitely a way to go!
Do you still use Cloudflare?
Nah, I ditched CloudFlare because I got all those goodies for free from Netlify. No point to do it anymore - KISS (keep it simple stupid).
Thanks a lot and don't forget to share a link to your blog when it is ready. Peace!
Finally, I managed to set it up and write two posts:
Now, one of the hardest thing behind me, now another one - keep consistency :)
I must admit that choosing Hugo and Netlify was really a great choice...
So, thanks for this post!
I used to spend so much time converting website content into markdown docs, recently found INK for ALL’s Jekyll compatible export functionality: http://bit.ly/2ECXoDa|Was losing a ton of time making site content into Markdown docs. Relieved I discovered Ink for all’s Jekyll compatible export feature. Such a game-changer: http://bit.ly/2ECXoDa
Hello Couldn't be happier with my choice to use a static site with Ink for all's Hugo-compatible export capability
I was investing far too much time converting site content into markdown files, glad I learned about the Ink for All editor’s markdown export functionality|I was losing way too much time making my site content into markdown docs. Happy I started using the Ink for all application’s Hugo compatible export tool. What an innovative thing: http://bit.ly/2ECXoDa