It's more of a framework than a boilerplate solution, but highly recommend checking it out!

To answer your questions:

1) Because the router in next.js embeds really well into the model of pages, prefetching, etc. while still keeping the mechanisms simple, here's how to use with redux: https://github.com/zeit/next.js/tree/master/examples/with-re... 2) now.sh is in no way mandatory. To deploy anywhere, `next build` and `next start` will run the node.js server, so you're free to deploy it anywhere you'd like: https://github.com/zeit/next.js#production-deployment

1. We have plenty of examples with interoperation with Redux. Check out the `./examples` folder :)

We currently use global state at https://zeit.co to keep the authenticated user in memory without re-checking for every page transition.

You can think of Next.js's Router as a "strict subset" of RR. Definitely possible for us to simplify our codebase by switching to RR in the future.

2. Nothing about this framework is dependent on now.sh. We, however, did design now.sh to make deployment of applications as this as easy, fast and scalable as possible with collaboration in mind.

I tried to do a project with next.js but their router was just too awkward and limiting. Unless you're doing straight 1:1 route to code, you're basically on your own.

https://github.com/zeit/next.js#custom-server-and-routing

That's the opposite of what that page is trying to explain. We'll take a look at the wording in case it's confusing.

tl;DR: You can do any sort of routing! We use a /:org/:project scheme similar to GitHub at https://zeit.co :)

Some examples:

- https://github.com/zeit/next.js/tree/master/examples/paramet...

- https://github.com/zeit/next.js/tree/master/examples/with-ne...

- https://github.com/zeit/next.js/tree/master/examples/with-pr...

The named routes example is probably pretty close to what I was looking for. Oh well, maybe next time.

Does next-routes work in a static build?

Is http://mern.io/ still cool? What problems did it have that made people look for something else?

2. You can deploy it anywhere! :)