Do you care if React is involved? Or are you happy as long as you can do HTML and use libs like three.js?

If there is a value to be had from using React in this setting, I would not reject it. I just thought this is a tool to be used for SPAs.

Actually, my concern is that React can be a headspinner. But most CLJS libs sit atop it. What did you think of Reagent, if your research covered that? https://github.com/reagent-project/reagent/blob/master/README.md I did this with Reagent and it seemed approachable, but my tolerance for UI pain is pretty high after forty years. https://github.com/kennytilton/hiringagent/blob/main/README.md

Also, if this un-framework approach https://tilton.medium.com/simplejx-aweb-un-framework-e9b59c12dcff is what you have in mind, @U04JD5WSD9P, and if you do not mind being one of the first ten users, I am about to ship a CLJS version: https://github.com/kennytilton/web-mx/blob/main/doc/intro-counter.md. I will be happy to "onboard" you, and esp. happy to help get P5 or three.js wrapped. I have wrapped charting libraries in my old Common Lisp UIs, but it would be nice to have a substantial example of wrapping external JS libraries in the Web/MX samples. btw, have you looked at #clojuredart , the Flutter wrapper? It's not clear to me if your frontend inexperience will be a hindrance or a help. Flutter is a massive OO framework, but that may be OK if you are not already deep into HTML. I have that wrapped, too: https://github.com/kennytilton/flutter-mx

Maybe https://github.com/borkdude/quickblog or https://github.com/magnars/stasis

Or try out Clerk! #C035GRLJEP8

https://jsxgraph.mentat.org/

For example, lots of good reagent stuff woven in with text. http://MathBox.Mentat.org wraps a declarative library over threejs too…

If you are thinking of building someting like a blog or simple web application then you should probably build a server side rendered application with libraries like https://github.com/weavejester/hiccup, https://github.com/ring-clojure/ring and https://github.com/weavejester/compojure. Server side rendered apps have just as good performance as client side rendered apps, have better SEO and are simpler to build (only one codebase, fewer/smaller libraries to work with and no API to build). You may not need any ClojureScript at all, just Clojure. If you do need greater interactivity down the line you can sprinkle some https://github.com/bigskysoftware/htmx and/or https://github.com/hyperhype/hyperscript into your hiccup (no clojure libraries required).

you can call cljs.repl/source-fn providing a env (you can obtain with &env in macros) and the symbol of the var

thanks!

It depends on the tool. GCL is pretty good at telling you when to use the JS web API over its own tools. So, in these cases just look out for the comments. For everything else, it's best to read over the source ( when you're in question) to determine what to use. For example, if we were determining whether to use goog.data.Date or Date we would see that goog's version is using Date under the hood and is itself providing some conveniences. So, you would have to determine if you want those conveniences. If you don't, opt for Date.

Aside from implementation details, if you lean on GCL in other parts of your app, you may want to opt to continue using GCL for consistency or because GCL functions tend to work nicely with each other.

Final note: experiment with things. You, generally speaking, can't go wrong with using GCL, so write your code with GCL and then write it with the JS web API. You will start to develop an opinion on how/when to use.