We don't use any "framework" with Clojure. We use a combination of libraries. Ring is core to almost everything. We use Compojure for routing in nearly all our apps (we use Bidi in one). We mostly use the embedded Jetty web server (via the "standard" Ring adapter) but all our apps can also start up http-kit instead, based on a command-line argument and/or an environment variable. We use Netty directly for one app that relies heavily on SocketIO stuff (via Java interop).
We use a lot of other libraries in different combinations across about a dozen services. A few of those are server-side rendered HTML -- we use Selmer for nearly all of the HTML rendering, with Hiccup used in one place for rendering an HTML fragment from Clojure data.
We originally looked at ClojureScript as a possible frontend back in 2015 but the ecosystem was very rough and the tooling seemed brittle (and, back then, the delta between Clojure and ClojureScript was a lot bigger than it is now). So we decided to build our customer-facing application using JS and React.js / Redux / Immutable.js etc. We have a frontend team dedicated to JS.
If we were doing the same project again today, I think we would evaluate ClojureScript again as a serious contender because the ecosystem has evolved dramatically in the last 4-5 years. I don't know whether we'd go with JS or cljs at that point.