web.dev VS Publii

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 good introduction to rendering on the web that can help you understand rendering options.

The lifecycle of an interaction. Source: web.dev

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

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 least for now).

Upon testing on Firefox and Mi Browser, there was no triggering of the BeforeInstallPrompt event, as expected. However, I noticed that web.dev manages to display a prompt on these browsers, even though they theoretically lack support for the BeforeInstallPrompt event.

web.dev, maintained by Google, including posts by Chrome developers and their co-workers,

In a old web.dev articleI came across the word "Incremental (Re)Hydration" which is linked to a Glimmer.js-Blog post (also called "Incremental Rendering" there) confuses me. Is Incremental (Re)Hydration the same as Progressive (Re)Hydration? Reading the Glimmer-Blog article it seems so, but in the web.devarticle it seems to be something different.

Web.dev newsletter - though it's not a weekly newsletter and it's only content from web.dev (though really high quality content)

Just open up a text edi web developers are self-taught. a website. That's what I did. Some people like this: https://web.dev

Those have complicated stacks that likely won't serve the person that can't grasp a CLI SSG.

https://getpublii.com has a simple GUI and is just a directory on your computer (inside the Dropbox directory for crude backup?).

Very nice! It looks a bit like Publii [0], but the editor part is cloud hosted instead of running as an app on your machine.

[0] https://getpublii.com/

Publii is one of the few competent attempts at a desktop CMS app.

https://getpublii.com/

They do a lot of things right.

Most SSGs, or if you want to have it easy: https://getpublii.com/ - generates static sites, can publish to github pages (among others), has themes.

I also consider https://getpublii.com interesting, but I have not yet had any personal experience with it.

I'd like to ask for some help regarding on how to "migrate" my website to my personal storage, more specifically how to do that while having everything made with Publii.

I haven't used it, but Publii[0] might be along the lines of what you're thinking of. I ran across it in a previous HN discussion, and it seems to be static site generator with a pretty user-friendly graphical interface.

[0]: https://getpublii.com/