Hi ,
It definitely can bring in great speed in your website. Here are few reasons for which I would choose Gatsby as my front-end
The speed of Gatsby websites are phenomenal: my entire Blog is Gatsby based, you can navigate and check for yourself : tharunshiv.com
The availability of plugins: there are a lot of plugins that are available which you can use to do huge tasks easily.
It is react based: so there are many components which you can use that are already available.
Ease of use with markdown: you can use markdown files to run an entire website, now how cool is that?
No doubt that JAMStack is the present and the future. This power when combined with PWA, will rule the domain of web development for a long time.
Thanks for asking.
Even if you have dynamic content, since you said it's only a little bit, you can use GraphQL and databases to pull dynamic data into the application right?
You mentioned that you're gonna use an API service, so this shows that you're gonna isolate your front end and backend, so you would be using services like GraphQL, Axios or Firebase like services which would help you make requests and populate the website. May I know how your thought process is currently?
Well with my team we agreed to use Next.js that seems more suitable for our project. So Gatsby is out of the table..
Thank you for your time Tharun, really appreciate it :)
Hi ,
It definitely can bring in great speed in your website. Here are few reasons for which I would choose Gatsby as my front-end
No doubt that JAMStack is the present and the future. This power when combined with PWA, will rule the domain of web development for a long time.
Thanks for asking.
Tharun Shiv
😊
Thank you Tharun for your answer. The good speed of Gatsby websites is definitely a pros to use Gatsby !
Even if you have dynamic content, since you said it's only a little bit, you can use GraphQL and databases to pull dynamic data into the application right?
You mentioned that you're gonna use an API service, so this shows that you're gonna isolate your front end and backend, so you would be using services like GraphQL, Axios or Firebase like services which would help you make requests and populate the website. May I know how your thought process is currently?
Well with my team we agreed to use Next.js that seems more suitable for our project. So Gatsby is out of the table..
Thank you for your time Tharun, really appreciate it :)
Sure.. :)
I'm just curious about the pros of Next.js, can you help me with that? Like what made you choose Next.js over Gatsby. :)
The main reason was that our project might evolve and its dynamical part might be more important in the future ^^
Alright.. thanks for the knowledge. :) All the best with your project!