Wordpress

As promised, here I am with a blog post about how I shifted to Hugo from Wordpress. What we’ll achieve by the end of this blog post: Migrating your data out of Wordpress (optional) Installing Hugo Creating a new blank Hugo website Importing your wordpress content into your new Hugo site (optional) Committing your new website to Github Setting up a free account with DigitalOcean and linking your GitHub website repo to DigitalOcean apps to enable automated deployments Setting up a custom domain for your website on DigitalOcean Migrating your data out of Wordpress I found the easiest way to do this is to use the WordPress Jekyll Exporter plugin. Just install this on your WordPress site, and download an export. Keep the zip file somewhere safe, we will need it later on. ...

Static site generators have picked up a lot of steam in the past few years. This much neglected blog of mine was running WordPress up until now, and even though it was good enough for me (let’s face it, I wasn’t really doing much with my blog anyway), I wanted to play around with SSGs. The ultimate trigger for me was my host telling me that I’m running out on disk space, and needed to decide if I wanted to go to the next tier of hosting with them. I decided that I had had enough with WordPress, and started looking at alternate ways to host this blog. At first, I looked at Ghost, and even though it was very fancy and easy to use, it was overkill for me, and I really wanted to go database-less. Out of all the SSGs I looked at, I decided to use Hugo for the following reasons: ...

Love it? Hate it? Let me know!

Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately. Longer explanation: This morning we received a note to our security mailing address about unusual and highly exploitable code in WordPress. The issue was investigated, and it appeared that the 2.1.1 download had been modified from its original code. We took the website down immediately to investigate what happened. ...