A Beautiful Site

I keep discovering macOS features I should've known about for years.

I stopped using Sass awhile ago.

From a maintainer's perspective, AI-generated pull requests are just piles of potential slop that we have to sort through.

As software engineers, we take pride in hand-written code and knowing how everything we build works in detail.

I've already written about FOUCE twice…it's that annoying Flash of Unstyled Custom Element that occurs when the page first loads.

I've been hooked on CSS nesting for awhile.

I launched ColorCopy on May 18.

A tweet from Jamon Holmgren inspired some thoughts about how software has changed, from a developer's perspective.

I built the dictation app I wanted.

My second macOS app, ColorCopy, was approved by the Mac App Store today!

I just launched my first macOS app, TongueType.

I believe artificial intelligence is a powerful and valuable tool that can significantly improve how we create, solve problems, and bring ideas to life.

I like using GitHub issues for actionable things such as bugs and backlog items I've committed to doing.

It's been awhile since I wrote about FOUCE and I've since come up with an improved solution that I think is worth a post.

It’s disappointing that some of the most outspoken individuals against Web Components are framework maintainers.

Components are like little machines.

I've been struggling with the idea of reflecting attributes in custom elements and when it's appropriate.

In the Web Component world, attribute reflection is commonly used to style custom elements both internally and as public APIs for consumers.

In a SemVer world, major releases are those which contain incompatible API changes.

I often get asked why I use Lit to build web components.

It's hard to put a value on a design system.

They say there's no such thing as bug-free code.

I often worry about framework churn.

Let's build a button that accepts one color and calculates its hover and focus states automatically.

Web Component authors already know how powerful slots are, but what if you could do even more with them?

I recognize the need for all users, regardless of ability or device, to have undeterred access to the websites and applications that are created with my software.

I needed to convert a URL object to a plain object yesterday.

You've likely heard the term "headless component" tossed around.

It's been three years since I broke ground on Shoelace 2.0.

Although Shoelace is a web component library, it ships React wrappers that lets you use the library idiomatically in React.

The topic of custom element event names comes up every now and then, especially from Shoelace users who get confused when events of the same name are emitted from different components.

Similar to how every custom element must contain a dash, I like to pretend that every custom event must also contain a dash.

It's been more than two years since the beta release of Shoelace 2.0, which was the first version of the project to ship Web Components.

Gather 'round, it's story time.

In the early days of Web browsers, it was extremely common to see user agent checks in JavaScript.

There's a post from 2016 entitled Buttons shouldn't have a hand cursor that's been making its way around social media this week.

2026-04-20 - Times change, and so do feelings.

Buttons are one of my favorite components.

In a previous post, I explored valid names for CSS parts and discovered that there are very few restrictions in what you can call them.

I was recently asked a really good question on Twitter: when shouldn't an element be a CSS Part?

CSS Shadow Parts, colloquially known as CSS Parts, are used to expose elements inside a web component's shadow root so they can be styled by consumers with CSS.

We live in a world where front end developers are fatigued from the framework wars.

On the eve of February, I was inspired to tweet about web components.

I've concluded that successful "makers" have one thing in common: luck.

Update (December 23, 2024): Check out my latest post on this topic: Revisiting FOUCE Web components are defined and registered with JavaScript.

Somewhere buried in my dusty basement lives a signed copy of Dan Cederholm's classic book Bulletproof Web Design.

The question of whether or not component APIs should be locked down at the code level comes up quite a bit.

The EyeDropper API has landed in Chrome and Edge 95!

Love them or hate them, web components ("custom elements") are making a huge dent in the world of front-end development.

I stumbled upon a short post that intrigued me.