What if you could make a card like a 3D portal, with layers of depth? You probably should just click to see, it’s a very compelling look.
It maintains space for where a scrollbar would be, whether there actually is one or not. But do you always want that?
I recently came across this CodePen demo by Vivi Tseng, which creates the blur extension effect by placing a square div with a blur() beneath the img element and I couldn’t help but think a simpler solution should be possible with a single img element and minimal CSS. So let’s first take a look at […]
It’s already quite impressive you can build a carousel with no JS at all (in Chrome, for now, anyway) and with some checkbox-hack stuff we can control dynamically what is shown.
Just a simple link tag in HTML can point to an online wallet to take payments, and a JavaScript API to react to them. But it’s (still) early days.
Repeat the same content over and over on top of each other, and you can move each of them just a smidge in 3D space creating the illusion of shape.
There is quite a bit of interesting design possibility with `random()` coming to CSS. It pairs nicely with animation, particularly animation-composition for agumenting those generated values.
I think it’s cool our industry has these high quality documentaries documenting the stories behind some of the transformative tech in what we do. The Vite one just came out about a month ago.
What would you pick if you could pick the next one? I wouldn’t mind hearing about early-days AWS or Docker. Maybe CSS itself or even just web standards (we have Jay Hoffman’s book here, which is nice). The jQuery Reunion is coming up, maybe they should take the opportunity to get those folks.
Dan Abramov has an interesting article How to Fix Any Bug where he’s having Claude write the code, but a bug shows up he needs to fix. Claude just isn’t getting it and it keeps saying it’s fixed when it isn’t (classic).
Claude was repeatedly wrong because it didn’t have a repro.
Meaning Claude couldn’t see the bug for itself. My first thought was: Dan! You gotta get Chrome DevTools MCP! This essentially makes the browser context for Claude, which is in my experience pretty damn helpful. But Dan actually had the Playwright MCP going, so it was a more complicated issue than just that. The path to a solution:
This exact workflow—removing things one by one while ensuring the bug is still present—saved my ass many times.
Reminds me of the lesser-known git feature git-bisect.
Paul Smith made these Classic Mac OS System 1 Patterns, which are super tiny (in size) graphics that work with background-repeat to make old school “textures”. They have an awfully nostalgic look for me, but they are so simple I can see them being useful in modern designs as well.
A satisfying little rant from Justin Fagnani: Stop Using CustomEvent.
One point is that you’re forcing the consumer of the event to know that it’s custom and you have to get data out of the details property. Instead, you can subclass Event with new properties and the consumer of that event can pull that data right off the event itself.
Little boosts of front-end development news, information, and advice — right to your feed reader of choice.
RSSHere's our page on guest writing. It's a win-win-win!
Frontend Masters donates to open source projects through thanks.dev and Open Collective, as well as donates to non-profits like The Last Mile, Annie Canons, and Vets Who Code.
