When OpenAI released GPT-4, the consensus online was that front-end development jobs would be totally eliminated within a year or two. Well, it’s been more than two years since then, and I thought it was worth revisiting some of those early predictions, and seeing if we can glean any insights about where things are headed.

If you’re a designer who’d like to give in-browser mockups a try in your own work, this article could be your starting point. My intent here isn’t to evangelize this way of doing things: I’ve met too many amazing designers with too many different processes to believe one size fits all. These are simply a few tips I’ve seen resonate with designers on client teams who have a spark of interest or curiosity, but aren’t sure where to begin.

What should you be worried about when it comes to web performance in 2025? How should you even start? I'm a web performance engineer, and I see a lot of common mistakes across the board when web developers and website owners try to understand and fix web performance, or "Core Web Vitals" in popular parlance.

Keyboard navigation is a vital aspect of accessible web design, and a detail-oriented approach is crucial. Prioritizing keyboard navigation prioritizes the user experience for a diverse audience, extending your reach while simultaneously fostering a more inclusive web environment.

Using path() in clip-path can’t be responsive; you can’t write CSS rules so that the path adapts to the size of the element. This is where the new shape() function comes in.