# 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:** 4

<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 27, 2018, 8:56am UTC](https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912/4 "2018-09-27T08:56:27Z")

</div>

I did the same experiment with `next.js` and it also works ok-ish.

> **[thheller/next-cljs](https://github.com/thheller/next-cljs)**
>
> Contribute to thheller/next-cljs development by creating an account on GitHub.

The “major” problem however is that their SSR support serializes all data to JSON which means it’ll lose important CLJS type such as sets, keywords, symbols when converting back to EDN. This however could probably be worked around.

As with `gatsby` I don’t think this is a good fit for CLJS but it does work ok-ish.

---

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