Now that Statamic is just a package inside a Laravel application, it means you can take advantage of Laravel features. There's a Laravel feature called Maintenance Mode which means visitors will see a 'site down' message.

This morning I opened my laptop like any other work morning, attempted to run my test suite and got a nice friendly error. In the end, I reset my laptop, ran my dotfiles and got back up and running in a matter of hours.

Statamic v3 is still in beta and I've started to use it on a few production sites. One thing that's still missing from v2 is Spock. While Spock hasn't been ported to v3, I've came up with my own home grown solution using Laravel Forge.

Setting up for developing a Statamic 3 addon can be tough. Especially if you've never done package development before. In this post, I guide you through the process of getting everything setup.

I've never written one of these before but I thought it would be a good time to start, especially as I've had a year where quite a few things changed in my life.

This was a very stressful hour and a half. Somehow my servers went rouge, tried to process 50,000 jobs at once. Each of those calls hit a Google API, racking me up a total in the region of £2700+. Thankfully, I managed to get it adjusted.

Recently, I've been working on building a Progressive Web App for a web application of mine. However in the process I somehow managed to cache the main page of my app, meaning users with the worker installed were stuck with the same HTML. I managed to figure out how to fix it.

An essay I wrote for one of my school exams about whether or not Christmas has become overly commercialised. It's led people to believe Christmas is Simon Cowel's birthday, so that's just mad.

An essay I wrote for a school exam about how school has shaped me. I talked about my experiences at both of my primary schools and about when I moved to secondary school.

I recently redesigned/rebuilt and migrated my entire website to a new Laravel app. I talk a little bit about why I did it.