The majority of tools are submitted by the community. They usually come from places like Twitter or Reddit. Then I manually review them to ensure everything looks good before pushing to the site, which is findcool.tools. - Source: dev.to / 8 months ago

I just wrapped up my 3rd launch on Product Hunt for findcool.tools where we received #3 Product of the Day (just wrote a thread about this project's launch stats on twitter if you're interested). Source: 8 months ago

It may be ran by Google, but https://web.dev/ is one good source for keeping up with new web technologies. - Source: Hacker News / 2 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