“Secure Custom Fields” is not Advanced Custom Fields

Big fan of and checking in but what I don’t like is having to add extra elements to present a nice look and feel for them. Dealing with the disclosed content also requires extra elements if you want to apply a layout, for example. It looks like that is changing though! I’m especially looking forward to giving the new ::details-content...

FYI We have news! We're in the home straight, finishing up Complete CSS and with that, we have a launch date: November 26 at 12pm GMT. Sign up to get updates and we'll email you as soon as it is live. We've been working on Complete CSS since February 2024. The aim of the game for me was to pull together all of the stuff I've been talking about...

Josh is here again with another stunner of an article and they’ve done a fantastic job of demonstrating how useful container queries can be in the real world. This is a really important part: I don’t think most designers are even aware that they have this exciting new capability. It’s our job to share these developments with them, so that they...

This post is a great run down of how much thought and consideration goes into making form validation actually useful. This part really stood out to me: However, if not well-designed, in-line error messages can become overwhelming. For example, flagging a field as incorrect after just one character can be disruptive, especially if the person...

A big thing you need to contend with when working on design systems is anticipating all the different ways someone may use a component. The idea here is that you then preemptively provide sensible behavior and safeguards to keep things working well. An example of this is a “Simple List” component I was helping to make. It’s a workhorse component,...