18/08/2018
Since 2008, my website has been running on a self-hosted Wordpress installation. Don’t get me wrong – I still think Wordpress is the most powerful content management platform out there. But since this here is my personal sandbox, I decided to shake things up and switch everything to static content.
But why did I decide to do this? Let’s compare the two:
So, with Jekyll, instead of writing a post in the admin panel and publishing the content to the database, I write the posts in Markdown format, and Jekyll compiles the .html files of the static pages.
It may seem a bit inconvenient to publish this way, but there are some advantages:
In other words, maintaining a server with PHP + MySQL and a Wordpress installation and its plugins that need constant updates just to serve a site that I update infrequently seems like overkill. I even considered Medium, but you, the reader, deserve more than pop-ups asking you to subscribe to the service, and I deserve more than a platform that uses my content to promote itself.
If you’re interested and want to do something similar, here is an article that provides a step-by-step guide on how to set up a blog using Jekyll Now, and explains the fundamental concepts of Jekyll.
P.S.: I took advantage of this migration to experiment with the fascinating Bulma, as a CSS framework.
Contents: