Divjoy VS Web.dev by Google

Agreed, check https://divjoy.com, has almost everything and helps work on the core product. Source: 10 months ago

Some boilerplates do offer some choices - usually around the front end, which tends to be a manageable piece to bite off. The two I'm aware of that do this reasonably well are my product SaaS Pegasus (for Python/Django) and DivJoy (for React/JS), though I'm sure there's more. Source: about 1 year ago

I built something I wanted that I knew I would have paid for if it existed (https://divjoy.com). If I was looking for a side hustle now I'd 100% be playing with GPT-3/ChatGPT and building small tools. There's a good chance your first few experiments won't catch on, but that you'll end up being in the right place at the right time, see an opportunity, and already have the code/knowledge to get an MVP out quickly. - Source: Hacker News / over 1 year ago

A few years ago I was frustrated with how difficult it was to setup a solid React.js stack with auth, payments, etc so I built the codebase generator at https://divjoy.com It does around $5-10k in sales a month. Fairly passive. A few hours of support a week. Was full-time on it for the first few years, but decided to join a company recently and keep growing this on the side. - Source: Hacker News / over 1 year ago

Picked a random from the list, https://divjoy.com/ and just to export a stock React Code is like $199. Not sure who they are marketing this for but good luck! Source: over 1 year 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 / 29 days 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 / 7 months ago

The lifecycle of an interaction. Source: web.dev. - Source: dev.to / 3 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: 5 months ago

I noticed the same for Google's site https://web.dev/ The last article pushed to the feed was "Changes to the web.dev infrastructure" few months ago https://web.dev/blog/webdev-migration The feed still there but with no updates https://web.dev/feed.xml and on the site you can see new articles published. Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at... - Source: Hacker News / 5 months ago