Cloud Cannon VS Web.dev by Google

Solutions like CloudCanon or TinaCMS use this approach. - Source: dev.to / 8 months ago

Great news — active development of Eleventy will continue, with Git-based CMS CloudCannon supporting the project and Zach taking a Developer Advocate job there. (Also 'Project Slipstream' sounds cool, from a static web perspective — removing less popular template syntax from core and moving to plugins.). Source: 10 months ago

A Git-based CMS like CloudCannon takes a different approach. It syncs your files from your repository and provides an editing interface to update the content. When you save a file, the CMS commits it back to the repository, so you always maintain control and ownership over your content. - Source: dev.to / about 1 year ago

Because I use CloudCannon to manage content on the sites I create, and because our product developers have been so busy over the last year, I’ve been able to put a much wider range of SSGs through their paces than I’d thought would be possible, working both locally and through CloudCannon’s web interface. - Source: dev.to / over 1 year ago

Thank you, this was helpful! We started looking at Cloudcannon and it seems well enough for what we need. 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