-3

I'm curious if it's possible, and if possible advisable to use both Gatsby and Next js. From a beginner's eyes, it seems like the choice of which to use could come down to a page by page need, rather than a site by site need. The project I'm working on now has pages that could easily benefit from being static HTML/JS/CSS pages, but other pages are dynamic and would benefit from React/Next.

Is there any reason you can't combine the two in a single site on a page-by-page need, and if so anybody knows of resources of how to do this efficiently?

Thank you in advance.

Ferran Buireu
  • 28,630
  • 6
  • 39
  • 67
Brett Williams
  • 141
  • 1
  • 13

1 Answers1

0

There's so much overlap between them that I’m not sure there’s sufficient reason to do this—they can both do the job you're referring to.

You may run into some collisions in the build output and they aren't going to route client-side across app boundaries, so overall it'd be a worse user experience anywhere the user goes from one to the other. Otherwise, though, it seems viable.

coreyward
  • 77,547
  • 20
  • 137
  • 166
  • Oh I see. I was under the assumption that Next could not create static HTML that it was exclusively on demand server-side delivery. I'll have to look more into the features of both it seems. Thank you for the response – Brett Williams Dec 04 '21 at 22:33