When you deploy that to Vercel, it gets deployed server-side, and they decide whether or not to serve the file statically (still after reaching the server), or whether they need to server-side render the request, depending on the data fetching methods you use.
Benefits of Digital Learning
So if you’re not familiar with the concepts, it can be a little confusing and difficult, but it just depends on what you’re trying to accomplish and what approach you prefer.
I prefer static first because there are many advantages to having a static first website, but it’s cool that we have that choice because, eventually, like the Next.
Js mission was to provide a universal React experience that could be used during an application’s life cycle, and they’ve succeeded in doing so by offering data fetching methods.
Could you tell us about your first Jamstack project and the technology stack that was used in it? Oh, wow, I’m not sure I recall my first project. My personal website, which is a Gatsby static site, may have been the source of the problem. Simply ask a question about the AMP setting that is bothering you the most.
For a while, I was working on a lot of mapping projects, which was due to the nature of my work at the time, where I had to build mapping applications, specifically for a satellite tasking dashboard.
It was an interesting challenge because those APIs, particularly the library leaflet, were all within the browser. So I would create the underlying static site with gatsby and then overlay the mapping utilities on top
But the developer experience was what really drew me in to Jamstack in general because I didn’t have to worry about a lot of the infrastructure or server-side issues that you would with a conventional website.
As a front-end engineer who doesn’t want to deal with all of the other things, it’s a pretty magical thing that I could spin up a Gatsby site that was totally static, deploy it with Netlify, which was pretty much as easy as using OAuth to link your Github site to Notify, and I had a website on the network. Yes, that is really fantastic.
Okay, maybe now is a good time to tell our visitors where we can start learning about Jamstack or where we can look for some good tools to get started with Jamstack? So, without further ado, I’ll plug my novel. Of course, I have a book called “Jamstack Handbook.”
I would encourage you to visit jamstackhandbook.com, but there are plenty of free tools available to help you get started. I have a couple of videos on YouTube, but even if you go to jamstack.org, there are a lot of tools there, but .
If you’re totally new to this, I’d always recommend going the Gatsby road. To gain a better understanding, all you have to do is visit reputable places like Ask Reader for fast answers.
Netlify & Vercelli
If I’m asking someone what it’s like recommending something to them because there’s a lot you can do without knowing a lot of extra stuff, like sourcing data, you can use those plugins to your advantage and really get a lot, get a powerful website up and running with a little bit of effort, but then using a tool like Netlify and Vercelli can deploy.
Netlify has a very nice developer experience for linking your Github project to Netlify and bringing it out to a working static website on the web, as well as Gatsby pages. Also, do you have any case studies or real-life explanations of what you did in your handbook?
So inside the book, I wouldn’t say that there are case studies per se, but I do go pretty in-depth in terms of what exactly it is, I go through the pros, the cons because every solution isn’t perfect, there are definitely some downsides too, that you have to consider, but I do also have three step-by-step tutorials within that book.
Next.js & Vercel
The first tutorial is simply getting a website up and running with Next.js and Vercel, and the second tutorial is spinning up a new project, where you add an eCommerce platform using Snipcart, which is a nice drop-in solution for having, you know, you’re building an online store really quickly for the Jamstack environment.
The third one is that you’re sourcing content from Graph cms, so you’re having a dynamic experience, and I believe it was a blog where you can actually manage your content in a separate organisation, similar to WordPress,
But you’re using one of the more Jamstack group toolings, and then setting it up so that it rebuilds the platform and provides that dynamic editing experience.