# Creating websites with shadow-cljs + gatsby or next.js

**URL:** https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912
**Category:** shadow-cljs
**Created:** [September 24, 2018, 6:29pm UTC](https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912 "2018-09-24T18:29:53Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![thheller](https://clojureverse.org/user_avatar/clojureverse.org/thheller/32/534_2.png) [@thheller](https://clojureverse.org/u/thheller)
#### Post date: [September 28, 2018, 7:20am UTC](https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912/7 "2018-09-28T07:20:30Z")

</div>

`transit` is probably possible but still won’t be very efficient since I don’t think you can hook into this globally. So you end up with maybe calling `transit` once per Object. I did not spend too much time with `next.js` though, so it may be possible to customize all of this.

After looking at both options however I do agree that we can probably build something more usable in CLJS itself. I may experiment myself a bit given how much of the heavy-lifting shadow-cljs in regards to CLJS/JS already does. Generating a bit of boilerplate code + HTML should not be that difficult.

---

_[View the full topic](https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912)._
