Welcome to my Blog!

This blog is going to be somewhere for me to post about topics I care about, rant about random things and generally express myself and scream pointlessly into this void we call the internet.

My Site's Stack.

I decided to go with Nuxt, Vue, Nuxt Content and Tailwind for my site. It's a fairly simple stack but there's a lot of power in simplicity. Nuxt/Vue is my go-to framework for new web projects. It's so simple and so powerful. I'm aware that using Nuxt for small single page projects and apps probably incurs a significant processing overhead but I'm fine with that. Nuxt Content was recommended to me by a fantastic, talented coworker of mine, Chloe Guttridge. After playing around with it for a bit I found that, other than the small issue of filtering by tags in my post metadata, it was perfect. Simple and elegant, exactly what I like in my stack.

Speaking of simple and elegant, that brings me nicely onto my last stack component; TailwindCSS. Tailwind is an absolute staple for me now. Yes, I know the HTML you write with it looks horrific. But once you get past that, it's incredible. I love the modifier syntax (hover:, md:, etc) and the power of tree-shaking means I don't have to worry about deploying awful, huge bundles!

Lessons Learned.

I think if I were to start this project again from scratch there are a couple of things I'd do differently, both to do with CSS and the styling of the site. I think firstly I'd choose a breakpointing system and stick with it. Too many times in this project I decided "ooh that breaks at 687.21px, better chuck a breakpoint in!" I now know that's just atrocious development, it's messy, ugly, unmanageable and a huge headache. Tailwind comes with custom breakpoints built in (I swear this post isn't sponsored!) which makes custom breakpointing a breeze. The second thing I'd do differently is to make the mobile site first and expand outwards. It's so much easier to add than to take away and Tailwind's structure lends itself perfectly to this.