This sounds great. I still think there is a need for better Elm specific documentation around custom elements (I wrote a more specific list here).
Iām curious what exactly your tooling offers? Generally in my experience the custom elements work is mostly twofold:
- Doing a lot of minute work with DOM apis to get the java/type-script side to its job.
- Doing fancy elm API design to put enough lipstick on the pig
The actual communication between these two modules tends to be a small minority of the code involved.