As I tried to explain above, the intent is really to have one codebase for a multi-page application (i.e. one shared bundle and one js file per page. Not an issue having manual work to add another page), and using low-level/self-designed tools to render visualisations and animations in either SVG, canvas, or maybe even WebGL (though I’m miles away from the last one) that the code finds by doing .getElementById when it’s loaded in.
I understand the ReScript idea of just having a .res/.resi → .js converter that works with the entire JS ecosystem out of the box. It’s great, because ReScript can just leverage the existing tools out there, which is super nice.
But let me be clear on something: I’ll be more than happy to just have a link to a tutorial for all the common tools, and how they interact with JavaScript-code. Then, if there’s some gotchas that needs to be addressed that can come after that link – though I assume that’s not really the case if you can run rescript -w in another terminal window, and the tools pick up .js changes. I don’t expect you to make a tutorial for the JS tooling itself (and neither do I think it’s sensible, unless there are enough caveats in the setup)