Marc Skov Madsen

+1. Would love this feature too.

> I think I'm going to go with core & recipes Sounds good. Alternative you could use Tutorials and How-to guide terminology of Diataxis.

WTF! Where did data go? Are parameter values now on model? And What about state etc? And remember that after layout and delete life cycle hooks are still needed.

> Ah, got you. I was trying to copy the API of anywidget which does not separate `data` and `model`. For consistency that's probably not a great idea, so will...

Regarding: "Give users the ability to write Preact components". Remember the purpose is not to enable preact. The purpose is to make it easy for users to create react components...

Please consider adding the requirements from https://github.com/holoviz/panel/issues/5550 to your todo list in the first post 😄

One open question is also if you can use code in `_esm` to insert Panel objects? See https://github.com/holoviz/panel/issues/5551

Thanks. It was meant as a joke. But not perceived that way.

... and also considering whether `ReactiveESM` is the right name? I don't think `AnyWidget` name would be right for us because a widget is an *input* component in our terminology....

I think building a `MaterialUI` component using the ESM and (P)React functionality would be a really good test if you have done this right.