openchakra VS web.dev

Are you using opencharka[0] then? I investigated that a while ago and was not very impressed or happy with any code that it generated, but curious to see if you've figured something else out.

[0] https://github.com/premieroctet/openchakra

Do you know of any open source drag and drop builders? I would love to be able to create my own components and drag and drop to combine them. If you know of any that are React specific, that would be great, but any builder would be helpful.

One example that I know of is https://openchakra.app/ for React apps that are using Chakra UI.

The original idea and inspiration for the Crayons Playground came from the full-featured visual editor and code generator for React using Chakra UI called openchakra. All the underlying architecture, code organization and design & communication patterns are borrowed from openchakra. The only difference is Crayons Playground doesn't make use of any JavaScript framework whereas openchakra is completely built using React.

In a nutshell, I wanted to easily add in all the components / design system from Material UI or Ant Design into the drag and drop interface, so I can play around with them, in a way similar to https://openchakra.app/

I started doing some mock-ups in my brain. Then I recreated some of them on Figma and then decided to start building. I started with OpenChakra (because I am using Chakra UI, more on that later).

Would you two be able to share some take-aways from that conversation at some point? Maybe write up a short comparison of the projects as they are now and any differences in roadmap/vision that could be relevant.

I always appreciate when OSS projects put in effort to understand and position themselves in relation to competitors (or potential collaborators).

Also want to mention some open-source React visual drag and drop page editors that might be useful for inspiration or to eliminate possible duplicate work. There's OpenChakra [0] and Blocks [1], which are apps, and then there's craft.js, a library that aims to modularize "the building blocks of a page editor" and seems to have more emphasis on customizing the actual editor UI.

Best of luck to you both!

[0] https://github.com/premieroctet/openchakra

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