Yeah, but it only makes sense to do so on a page that already is using react. If you are using some other JS framework it will add 140kb dep on react+react-dom - which might be a problem (or not depending on your use case).
Definitely a good point. Just wanted to note that you could write a renderer in some server language that outputs static HTML. And only use the editor to make that static content editable (loaded asynchronously or on a different route). The serialized state is easy to parse by design.
That is an excellent idea!
Yes, it’s Backend-agnostic and designed to be embeddable into any web app. It’s basically an editor framework to define your own editor and you write the glue code to your web app.
TBH my suggestion is to work on making this more clear of who it's for. Maybe add a comparison to other current solutions out there, since at first I was a bit confused what it's trying to do. Maybe use like intro.js or something for it.