We can use `shape()` to carve away the edges of an element to look like a folder tab. By hand.
Svelte 5 introduces significant improvements in reactivity, state management, and prop handling, maintaining its user-friendly Developer Experience (DX).
You should know that in-app browser can and do literally inject JavaScript into the websites you visit with them with tracking scripts from the app you’re inside of. And that’s just one thing that sucks about them.
Danila Fedorin’s article about unique UX features in blogs is fun. Here’s some extra thoughts, resources, and opinions.
Having a named block of styles to apply in CSS can be useful, and newfangled Style Queries are pretty close to that. We look at one use case here, how Sass did mixins better, and hope for a native solution.
CSS allows setting different overflow behaviors for x and y directions. It doesn’t actually work with the `hidden` value, but it does with `clip`!
The navigation in this game works with the arrow keys, which is made possible with scroll driven animations, faked collision detection, and maintaining state with CSS custom properties.
Erick Merchant has some ideas for questions to ask a senior front-end-developer (as in, interview questions). They seem pretty decent to me, so if you’re shooting for a senior role, you should probably have answers for these things with a bit more detail than Erick lists.
If video game development appeals to you on your journey into design and development, you should check out js13kGames, a “coding competition for web game developers, with a 13KB size limit.” The 2024 winners were recently announced, and I find the lot of them outstanding. 13KB is a heck of a constraint. jQuery is like 30k lol. So building a game with graphics, logic, state, etc in that size is incredible. I have no doubt this cauldron of constraint produces really great general web developers where writing performant code is forever desirable.
Are you using Sass as part of your build process? If you’re using Vite or webpack and importing SCSS files in lots of different components, be aware you should probably switch to sass-embedded instead of sass, as it can, as James Stuckey Weber wrote, “allows you to reuse a single instance of Sass for multiple compilations” instead of Sass spinning up and down for every single import.
Victor Ayomipo saw our post about using container units for everything. He was more optimistic than I that our result was good. My thinking is that there are plenty of things you straight up don’t want to use container units for. Victor did a similar exercise with (over?)-using min() and viewport units. Turns out there are lots of niceties, and I agree that min() is underused, but that you still can’t dogmatically say one particular sizing approach is always best. Personally, I’m rocking min() for container “width”, like .wrapper { inline-size: min(300px, 100dvw); on the regular now.
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.
