Last week I hit my first anniversary working for MariaDB. I’ve been looking back and recently realised one of the things I have been neglecting is my blog.
As an experiment my previous blog ran using Pelican blog system. I really liked using this because I have a lot of experience writing documentation in reStructuredText format using Sphinx. Pelican allows you to blog using the reStructuredText format to generate a static HTML site.
The downside of Pelican along with similar tools for generating blog content is they are a pain to edit on a mobile device and can take a lot of time to manage. This is one of the reasons I have been neglecting my blog, it has been too much work to manage and I have little time beyond work and personal life to manage it.
So, I have moved over to WordPress hosted on wordpress.com, I can leave backend management to them and I’m able to edit the content easily on any device that I need to.
I look forward to hopefully writing some interesting content in the future.
Image credit: American White Pelican by Manjith Kainickara, used under a Creative Commons license
Some things happening in this industry are making me feel old lately. Problems we hit…
I was working on benchmarking some new code on a Raspberry Pi Pico today and…
What should have been a straightforward CD32 recap turned into something far more interesting. The…
Back in the 80s and early 90s, when games often came on floppy disks, the…
A while back I built a 486-based machine to play with some late 80s /…
I managed to score an Amiga 600 motherboard which was faulty for £41. This weekend…
View Comments
My dream come true: Hugo, Netlify, and Forestry.io — it’s how I manage my blog. The result is a fast, secure, static site that’s even easier to manage than a WordPress site. Now, about finding time to write…
I figured a fresh start would encourage me, so far it has worked. I have a couple more posts that I'm already working on.
Are you talking about self-hosted WordPress? or the hosted WordPress solution from WordPress.com (obviously under a custom domain)? You’re not really clear on that point.
Whatever solution you went for, I hope you’ll stay motivated. I left static-site generation behind over similar concerns. (Plus, it’s hard to manage scheduled publishing without a dynamic backend.)
Hi Daniel,
Good point. I am using WordPress.com with a custom domain. I want to manage as little as possible (especially the updates).
I will update the blog post shortly to clarify.