If you are like me, maybe you have heard the term, or maybe you are overwhelmed by the many static site generators and don't know what exactly they...
For further actions, you may consider blocking this person and/or reporting abuse
My implementation of the JAMStack has truly decoupled components, a great user experience, and did I mention....
...it tastes great?
This is a great explanation! I love using JAMstack and I try to build with it whenever I can, but it is so hard to convince clients to approve it over something like Wordpress, ever after explaining the benefits. Some people are just averse to change.
Superb explanation indeed. For vuejs, gridsome will be a good choice.
Hey, thanks. I didn't use gridsome but I'll try it.
Gridsome is the best for Vue sites that are truly static, but I also like using Nuxt for more complex Vue SPAs nowadays.
In my opinion, JAMstack is not about specific technologies. JAMstack is a new way of building websites and apps that delivers better performance, higher security, lower cost of scaling, and a better developer experience. It is the combination of underlying tooling that makes JAMstack so exciting. JAMstack is composed of 3 components: Javascript, APIs, and Markup. Read more about JAMstack here 👉 agilitycms.com/resources/posts/top...
Don't want to read? Watch the text converted video: youtu.be/zuJpJTI4qWI .
It's usually good form to A) get permission first, and B) credit the author whose content you used - FYI
I will keep in mind next time.. Thank You
Wow, that's great, what tool did you use?
Just some video editing software.. :)
Is the JAMstack suitable for applications that get its content updated frequently? Let's say: Would be possible to build a site like reddit?
You certainly can, although very large applications with a lot of pages are often better to be rendered on the server side in my opinion. But a Reddit-like JAMStack implementation would probably not be too difficult. You would write a few page layouts: subreddit, post, user settings, etc., then pull in the data to be inserted in these layouts from a serverless backend. This is why JAMStack is so flexible because ideally your content is completely decoupled from its presentation layer.
Then, it should rebuild every time an user submits a new post? I guess that you could somehow do it incrementally, but wouldn't it be a huge bottleneck? Thanks!
No, you can still use
fetchcalls and other dynamic client-side code from a JAMStack app, so you don't rebuild. But this is why I say large applications are better rendered server-side though—you really shouldn't have a static site or SPA that is trying to act like a really dynamic application with a ton of client-side fetch calls.That posts wouldn't get SEO and basically all the benefits of being static are also lost. I get it now, thanks!
What a great description for JAMStack! Thanks for the info Elizabeth!