Once more with feeling
Hello world... again!

Hello there! It’s been a hot minute, hasn’t it?
Welcome to my new site! After timoliver.blog went down at the end of 2024, at long last, I am incredibly thrilled to unveil its replacement.
Introducing: tim.dev!
I’ve been sitting on that domain name since I acquired it in 2019. It’s still the most valuable domain I own, and I’ve been constantly promising myself I’ll do something with it to do it justice. Hopefully this site will do.
I’ve been working on and off on this site for about a year and a half now. I decided to take the opportunity of timoliver.blog going down to do a complete ground-up renewal. All of the blog posts and comments have been migrated across, but literally everything else is brand new.
The site aims to be as modern as possible. It has a much more minimal design, with full light/dark mode support, and is far more responsive when viewed on devices with smaller screens. It aims to be as fast as possible as well. Images are lazily loaded on demand, and content linked externally (Like YouTube videos) have local placeholders until you click on them. Hopefully this adds up to a delightful experience, on the level suitable for a great website in 2026.
In addition to my blog, I’ve experienced a few instances in recent times where I got caught flat-footed not having an up-to-date reference of my work. And so, this site is now equal parts blog and portfolio. I’m super proud of all the work I have on display here, and I’m feeling extra motivated now to start expanding those lists!
So, uh. What happened exactly? Why did timoliver.blog go down?
Since the very start, my personal blog has always been a self-hosted WordPress instance. Don’t get me wrong, WordPress has been absolutely fantastic to work with over the years, and I’m glad how easy it made web development, both as a hobby and a profession to so many people.
But times change. In recent years, my WordPress blog started to degrade and maintenance effort went up. The site started slowing down, adding friction to writing posts. I tried to remove plugins and added caching, but it didn’t speed up. Then the Disqus commenting integration went down and I couldn’t diagnose why.
And the final nail in the coffin, more often than not, I’d open WordPress to see there was a pending security patch that needed to be installed. Given how popular WordPress is and how its open source nature, I’d always drop everything and install the patch instead, burning up all my writing time.
All the while, I was looking at statically generated sites going “Why am I even using a full-blown CMS again?”.
At the end of 2024, the site finally fell over, and I realised it was time to go back and start again from the very beginning.
So with all of that in mind, this new site has been designed from the very start to be as fast and frictionless as possible. No more WordPress, this time, it’s completely statically generated, meaning much faster access. And in terms of friction, the site is fully automated (and open source) on GitHub. All I need to do is commit a new file to publish a new post!
True to my work as an iOS developer, the site isn’t generated by PHP anymore (Or Ruby or Python). It’s Swift!
The site’s generator is built over Ignite, a fully open source static site generator written entirely in Swift. I had attended the iOS conference where Paul Hudson announced it and had kept it in the front of my mind for this eventual rewrite.
Ignite has been absolutely lovely to work with, and Paul was gracious enough to accept PRs from me in order to let me customize it just the way I like it.
Since Ignite is just a Swift package, the whole site lives in Xcode like any of my apps, complete with unit tests. And because it runs natively on macOS, I can do really powerful things like render each post’s link preview image with Core Graphics at build time. If you’re a fellow iOS developer looking to make a website, I highly recommend it.
There’s so many more features and aspects of this blog I want to talk about (Like how much internal debating I did on whether to keep the comments or not!), but I’ll save those for some later posts. For now, let’s let the site settle in and wait for the paint to dry.
Thanks for reading! Let me know what you think of the site in the comments!