This blog is a static website hosted on Netlify. As static site builder, I use the awesome Hugo, which is written in Go and amazingly fast. This page with currently more than 300 pages build in less than 500ms. But as the name “static” suggest - just static files that are served by a simple HTTP server - it doesn’t have a dynamic backend with the option to schedule posts, so scheduling isn’t possible the same way it is with systems like WordPress.
When I wrote, that I switched from a Ghost-based blog to a static site generated by Hugo, I made the following statement: I don’t use a service like GitHub pages or Netlify, because using my own server really guarantees me full control. But it would be a good alternative, if you don’t want to manage your own server. Netlify can also cover the automatic deploy process. Since then I switched all my blogs from Ghost to Hugo, but also started using Netlify for the hosting of my static sites.
Hugo is a framework to build static websites. Yesterday I migrated this blog from Ghost - a dynamic NodeJS based CMS - to Hugo, not only to reduce the hardware requirements (a static page uses way less resources), but also to simplify my setup. I already use Hugo for two basic homepages (my personal one and the AndroidPub one), where I don’t have that many requirements regarding “blogging”, because I don’t use them for blogs.
I used Pagekit for quite some time with my personal homepage. Pagekit gave me a nice Admin UI and there were also nice themes and plugins, which I could use. But Pagekit is PHP and the setup isn’t that optimal. So I switched back to a static site setup with Hugo. Some years ago I used Jekyll to build a lot of websites. Jekyll was really easy to use and you could host your sites on GitHub for free, I didn’t rent a server yet back then.