Search

Desmond has written a great overview of the current state of "post types" within the IndieWeb community, but the takeaway that struck me as most interesting/valuable is their distinction …

Progressive summarisation may not be ideally suited for me right now, but it's an idea which stuck with me whilst I was undergoing my own taxonomy building process. It's worth stepping through the …

By reordering the steps that I go through when capturing photos I've been able to make my overall workflow more efficient and much more enjoyable.

I always enjoy hearing others' thoughts on taxonomies, and Lea's ideas are well thought through and come with some interesting challenges (and findings) around using hackable URLs, folksonomies, and …

Lots of companies rely on Microsoft Word for internal documentation and training, but code snippets are a readability nightmare. They don't have to be; with some reusable formatting, we can make clear code blocks in any version of Word.

Migrating assets to a new CMS can be a complete pain, but working out which files go with each page or article on a website doesn't have to be a nightmare if you start with a solid foundation. For me, that means tightly coupling my folder structure on the server with my content structure on the website, a workflow that Craft is particularly nifty at automating.

In which I start off asking a simple question: what content categories should I use on this website? Four hours later, I've discoverd information gardening, now pages, digital-me libraries, and oh so much more. And yes, I think I've answered that first question. Fancy a trip down the rabbit hole?

Well, it only took about a week of dazed puzzling, data tables, and tearing my hair out in clumps, but I think I may finally have a rough content taxonomy for theAdhocracy. A rough first version, that is. Let me explain...

An interesting look at using padding only on the very lowest element within a hierarchy (as Samantha says, the atoms of your design) and therefore setting it globally. It's a logical approach, though …

A great breakdown from Dave as to why the typical card UI pattern has some inherent issues. Some elements – like making cards all the same height and dealing with responsively collapsing card lists …

A great overview of techniques to help improve text legibility, working with the browser rather than against it to be as inclusive as …

A solution for an annoying bug in Lightroom where keyword searches stopped indexing new tags.

A quick overview of React Server Components and some of the mental models that are useful when thinking about how they might be applied, in …

I'm still enjoying the wombo-combo of Sass and CSS Modules, but my React-ified brain occasionally blanks on how to approach certain problems. The one that catches me out the most: style inheritance.

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