Search

Craft CMS has the ability to accept environment variables as well as aliases. It can be worthwhile understanding how these two seemingly similar concepts differ, and when you might want to use one over the other.

Notes from my second fully remote conference, this time Sparkbox's UnConference. Being able to freely access talks from the US is a rare bonus of everything going on right now, and this did not disappoint. Musical cameos, great talks on UX, accessibility, design systems, and amazing speakers. Great event (despite the time difference).

There are several strong arguments for moving away from using "master branch" as default terminology, but what should it be replace with? Personally, I like the idea of extending the tree abstraction that we use when talking about branches, so have started using "trunk".

The idea of a great divide in front-end development resonated with me. I'm worried about how the erosion of certain skills could lead to a less inclusive, accessible web, for both users and developers. On the other hand, there are some massive advantages to our new tools. It's a double-edged sword.

The combination of the Carbon design system and NextJS should make for rapid website development, but I ran into a few small hurdles getting them to play nicely with one another using existing documentation and community guidelines.

A look at how I've been using Git aliases to remove repetitive tasks, automate workflows, and generally optimise working on the command line. They're small tips, but they've had a big impact on me.

Using pseudo-selectors like :where and :not to invert style rules, allowing for better code encapsulation and context sharing across a codebase.

Have you noticed something a little bit different around here?

A look back over 2024, a year dominated by travel and friends ‒ and, particularly, travel WITH friends!