Published: 05 December 2017
The two main reasons were speed and HTTPS.
More specifically, after five years’ worth of blog posts, Jekyll stared to become a bit slow to regenerate the website. Initial tests with Hugo however proved that it was very quick. The other reason was that I was thinking of migrating over to HTTPS. This cannot be done out of the box when using a custom domain name on GitHub Pages, and instead you have to resort to using something like Cloudflare.
I stumbled across Netlify by chance one day and I decided to give them a try, and so far I am extremely happy with them. In this blog post I’ll list eight features which I have used and really like.
You cannot beat Free, especially when combined with all the other reasons I’ll mention. They have paid plans, but those will typically only come into play once you start working in a team setup where you need multiple people to be able to access your account.
Combine a static website with their global CDN and what you get is a super speedy website. No matter from where in the world people visit your website, they will have a great experience.
It is very easy to configure continuous deployment from GitHub. And it works with plain static websites, static website generators (like Hugo) or even more advanced scenarios like using front-end build tools like NPM, Gulp or Grunt. Once you have configured the continuous deployment, you just need to commit to your GitHub repository and Netlify will take care of the rest.
Along with Continuous Deployment, you also get versioning and rollback. You can see a full history of all your deployments:
And even switch back to one of your old deployments if your current deployment proves problematic (this has happened to me before!). Simply hit the Publish deploy button on the build you want to revert to:
Netlify will automatically build previews of branches and pull requests. Here you can see a preview build for the branch containing this blog post:
To view a preview of the deployment, simply click on the deployment in the list and then click the Preview deploy link:
Want to configure your site to use SSL? Click one button and Netlify will automatically provision a certificate from Let’s Encrypt. You can even force SLL for all requests, which will redirect from HTTP to HTTPS and add Strict Transport Security headers to all requests.
Netlify allows easy configuration of redirect and rewrite rules by adding a
_redirects file to the root of your website where you can configure all the rules and optionally the HTTP Status codes, for example:
/home / 302 /blog/my-post.php /blog/my-post /news /blog /google https://www.google.com
Listed above are eight reasons why I like Netlify. While I have used all eight of those features, there are many more reasons why you may fall in love with Netlify. Here are a few more interesting features which I have not found use for yet, but which looks interesting:
I really like Netlify. There is not a single thing about it so far which has frustrated or irritated me. Instead, it just keeps on surprising me - in a pleasant way. If you are currently hosting a static website or Single Page Application somewhere else, then I suggest you give Netlify a try.
PS: If you found this content valuable and want to return the favour, then please feel free to ☕ buy me a coffee ☕
I publish a weekly newsletter with all the best ASP.NET related news and blog posts of the previous week.
Sign up with your email address below to get it delivered to your Inbox every Friday!
Not sure whether to sign up? Why don't you check out some of the past issues?