nextjs-custom-server VS next-web3-boilerplate

With MongoDB out of the way, first, create a new repository using a template at payloadcms/nextjs-custom-server, and clone that to your local machine. Unlike forking, creating a new repository from a template resets the commit history and disassociate it from an original template repository.

For example this repo says you can install with npm install and you will end up with both.

Next.js works great with Payload. One cool feature of Payload is the Local API, which works awesome for server side rendered pages. You get your data from Payload right in your `getServerSideProps` functions.

You'd be interested in the example repo: https://github.com/payloadcms/nextjs-custom-server

The example is set up to manage Pages, but with a few tweaks you'd be able to manage blogs posts instead.

I recommend Payload CMS for simple sites and complex apps alike. Check out the next.js starter we have up to get server side rendering for a boilerplate website. https://github.com/payloadcms/nextjs-custom-server

Check out payloadcms.com. We just created a new NextJS boilerplate if that is the direction you want to take for the frontend https://github.com/payloadcms/nextjs-custom-server.

We just added a boilerplate that gives you a nice next.js starting point too so you can do get a frontend fast also! https://github.com/payloadcms/nextjs-custom-server

I tried https://github.com/mirshko/next-web3-boilerplate. Worked pretty well