 I'm working as a front-end developer with Freshworks. So before beginning the talk, I have just few quick questions for you to set the context. Number one is, how many of you have a portfolio site here? Just raise your hands. Cool. And how many of you are too lazy, don't have a portfolio site, but want to build one? Me, me, me. Cool. So yeah, this talk is going to be beneficial for you. And coming to the previous talks that we had till now, because those are amazing talks, I've learned something. I've learned how you guys are processing with micro-architectures, monolithics, and all. But what if I tell you that you don't need monolithic architectures or micro-frontends or something, at least some cases, like portfolio website or maybe a small shopping cart or maybe for your blog, I say. So that is what I am precisely going to talk about. So people, let's talk Jamstack. How many of you here are aware of Jamstack? That's a quite less number. So let me give you a brief introduction about Jamstack. So Jamstack is a new architecture that is framed with existing technology around us. So Jamstack is basically a front-end way of implementing things that don't need a server, a database, a caching mechanism, cache bursting mechanism, security, nothing. Just have a front-end developer, just have a CDN code, deploy, and forget. I'm telling you, you can do this, you can implement this for your blog, for portfolio, or maybe you're selling your small goodies or swag on some website, you can do that. So what is the reason for Jamstack? Why do people term it? So we must know, most of us all are aware of tools like WordPress, Zoomla, Squarespace, Wix, and all right. How many of you feel that they are complex? I mean, they need your attention. They're like a small cat or something, they need your attention all the time. It's not like you deploy forget or something, you keep on updating it, you just have to take back up frequent times. And more than that, they're definitely not pocket friendly. So you agree with me right on that? So they're definitely not pocket friendly. But Jamstack does exactly opposite to you is completely developer friendly. So let's discuss. So Jamstack is made of three components, J for JavaScript, A for APIs, and M for Markup. So let me begin with introducing Markup. Markup is nothing but your HTML code, pre-rendered HTML code, that is one component of Jamstack. Second component is APIs. APIs in a sense, I said no service, right? But you need extra functionalities, maybe a comment section or payment gateway or something. So there are some third party APIs that has been provided by Stripe or Discuss or something. If you want to use those APIs, you can use this here. And JavaScripts who clubs these two and place on them. So this is basic introduction. And let's see how do you build a Jamstack website? So Jamstack needs three components. We've seen the methodologies of Jamstack, but it needs three major components to build any Jamstack website. Number one is Static Site Generator. So number two is GitHub. Number three is a CDN service. That's all. So let me start with Static Site Generators. So I'm a guy who works with Ember and React.js, and I use my own Static Site Generators. How many of you work here with Vue.js or any other framework like Angular and all? Cool. You guys might have heard about Static Site Generators already. So these things are not new. So these things are not new. They are already existing. These are like templating engines that you pre-built your content with. Basically, they include three components. One is layout. Second is route. Third is content. When you run the generator, it combines your input into a pre-rendered HTML file and generates your output. Number two, Git. Git is kind of very important here because our Jamstacks expect your source code to be on Git and it also expects atomic deploys. That means you do something, it deploys and it builds and it deploys. It's called atomic deploys. And third player is CDN. CDN is very crucial here because we don't have servers, we don't have database. All our content, including HTML, CSS, JavaScript is being served from the CDN. So these are the three concepts. It seems simple, but how do you implement it is up to you. JavaScript, pure vanilla guy, you work with ReactJs, Amber, you have a static site generator. And these generators will help you in using any third party plugins and build the site that you were expected to build with. And while how do you host your Jamstack website? Well, there are two ways in this. Number one is use out-of-the-box providers was like Netlify, Zait, Surge and all and GitHub pages as well. And number two is set up your own pipeline that builds your script, that puts your script somewhere in S3 or something and then that takes care of auto deploys and puts your script in S3 or something. So these are two ways, how do you implement it? I guess it's time's up. I'm learning new. If you have any doubts on the Jamstack, I'll be sitting here on here. If you just see me, just come and talk to me. I can help you with that. Thank you guys.