Need advice about which tool to choose?Ask the StackShare community!
Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.
As a Frontend Developer I wanted something simple to generate static websites with technology I am familiar with. GatsbyJS was in the stack I am familiar with, does not need any other languages / package managers and allows quick content deployment in pure HTML
or Markdown
(what you prefer for a project). It also does not require you to understand a theming engine if you need a custom design.
Hey guys,
My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!
Pros of Hugo
- Lightning fast45
- Single Executable27
- Easy setup24
- Great development community23
- Open source22
- Write in golang13
- LiveReload built in7
- Not HTML only - JSON, RSS7
- Hacker mindset7
- Gitlab pages integration4
- Easy to customize themes4
- Fast builds3
- Well documented2
- Easy to learn2
- Very fast builds2
Pros of Next.js
- Automatic server rendering and code splitting41
- Built with React35
- Easy setup28
- Universal JavaScript22
- TypeScript21
- Zero setup21
- Static site generator16
- Simple deployment11
- Incremental static regeneration11
- Just JavaScript10
- Frictionless development9
- Filesystem as an API9
- Testing8
- Isomorphic React applications7
- Everything is a function7
- Well Documented7
- Not nuxt6
- Has many examples and integrations6
- Not vue4
- File based routing + hooks built in2
- Deployment1
- Not angular1
Sign up to add or upvote prosMake informed product decisions
Cons of Hugo
- No Plugins/Extensions4
- Template syntax not friendly2
- Quick builds1
Cons of Next.js
- Not Vue8
- Structure is weak compared to Angular(2+)7
- Is no Angular2
- Not flutter2
- Not Angular 21