Blog weeks – Blog systems next to Wordpress

My Experiences with WordPress

This year's Blog Week 2025 is focusing on systems beyond WordPress. I asked myself: Why is WordPress so successful? I couldn't understand why, so I asked ChatGPT. The answer briefly:

WordPress is successful because it bridges the gap between simplicity and technical depth. Whether you're a newbie or a seasoned developer, everyone will find their way.

There were several compelling arguments in favour of WordPress, including SEO-friendliness, a large community, numerous plugins, and open-source status. Additionally, every hosting provider offers an affordable package. So there are no hurdles for the newbie – okay, I get it.

But I'm not a newbie, I'm a seasoned developer. Thanks to impostor syndrome, I often feel like a newbie, but despite all its simplicity, I wouldn't use WordPress for one crucial reason: the database. The first time I faced the challenge of pushing my development work to the production environment, I had a meltdown. I couldn't upload my local database because a lot had happened between my current status and the completion of the development due to the client's content maintenance. Ultimately, I attempted to recreate and update everything one-to-one in the production system. An experienced WordPress developer might chuckle now and know solutions for this. I've been done with WordPress since this experience.

Which alternative(s) do I use?

For some time, I worked with the Static Site Builder Jekyll. It was convenient, and I didn't have to mess around with a database. The system reached its limits when clients wanted to update their content. Initially, I used the SaaS Cloud Cannon as a temporary solution. At some point, their prices became unaffordable. When I just checked, I just saw that they've backtracked and are now offering a small pay-as-you-go plan.

Then, thanks to Maurice, I discovered my love for the file-based CMS Kirby. Maurice and I explained why we use the system both privately and professionally in a German blog post. In another article, we explained our reasons more specifically based on a customer project (see English article). Essentially, it's about our ability to master the tool as developers and meet customer requirements. Hosting isn't a problem for us, and thanks to plugins, we're just as flexible as others with WordPress.

Conclusion

There are numerous alternatives available that are suitable for various use cases. I think all those that rely on the Jamstack tech stack are worth a look. At the beginning of a project, I spend 30 minutes researching whether there's a tool more suited to the challenge than Kirby CMS, and then discuss the results with the team. And I'm excited to see which new system or framework I'll be working on next.

#BlogWeeks2025