> Are you saying, that NextJS encourages a design, which keeps no script in mind?

It quasi enables it, a NextJS site has three rendering stages:

1. static at build time 2. server side at request time 3. dynamic in the browser

It leverages React hydration for 1-2 and client side React for 3.

If you avoid 3, or rather build your site with progressive enhancement in mind (`noscript` can help but is often not necessary) then this framework makes it very easy for you.

I think https://reactjs.org/ is built with Gatsby (a similar framework, but not as dev friendly in my opinion). And you can browse it just fine with JS off last time I checked.

1. Next renders the React page server-side and sends it as html/css. Once everything is done loading on the client, it becomes a regular React page. Requires a server. 2. Next pre-renders your whole website with data fetched at build time, like Hugo or Jekyll. Drop it on a CDN and you're golden.