It may be ran by Google, but https://web.dev/ is one good source for keeping up with new web technologies. - Source: Hacker News / 10 days ago

“If the sanitization logic in DOMPurify is buggy, your application might still have a DOM XSS vulnerability. Trusted Types force you to process a value somehow, but don’t yet define what the exact processing rules are, and whether they are safe.” — this caution from web.dev makes me want to play around with TrustedTypes more and get a better understanding. - Source: dev.to / about 2 months ago

Before we start creating pages in our application, it's important to understand how Next.js renders content. The framework supports multiple rendering methods including server-side rendering (SSR), static site rendering (SSG), and client-side rendering (CSR). There are many pros and cons to each rendering method (too many to cover in this post) so if these concepts are new to you, Google’s web.dev site has a very... - Source: dev.to / 8 months ago

The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 4 months ago

Probably not, it's the CSS used so far, so if there are elements you've not interacted with, that's an issue. This web.dev article gives some tools you can use https://web.dev/articles/extract-critical-css. Source: 6 months ago

If you want to benchmark yourself when you learn React. I’ve completed most of the medium/hard react problems at https://practice.dev to get my job. Source: over 2 years ago

It took me a few months to build practice.dev. Here I extracted the IDE and added live collaboration and npm resolver. It took me 1 week to release live-ide.dev. Source: over 2 years ago

The idea of practice.dev is to create basics tutorials (currently it's in progress) similar to FreeCodeCamp, and create hundreds of challenges with greater difficulty. Think of it like leetcode/codewars for frontend. Source: almost 3 years ago