 So yesterday, we saw how to set up the virtual environment, install Django. So now we'll be just understanding what actually yesterday with it, like what actually is Django, what is the framework, what are the advantages, and some more things related to web development. And then we'll proceed ahead. So I'll share my screen. Yeah. So obviously, we are aware that Django is pumpkin-based, number one. And yeah, Django is a web framework. So understanding web framework is quite important. So web framework will basically give you building blocks for your website, which are very common building blocks, like the login, which is almost in all the websites, so session handling. So all these things will be readily available in your web framework. It will be like a skeleton. You have to only focus on the business logic that you want to develop. So web framework is quite helpful. It provides you with the initial structure, as I say, it's skeleton for the web app development. Then yeah, it also helps you develop your application in a standard way. So it will enforce that you write your code, you develop it in the standard way that is usually done. We'll see how it helps us. Obviously, we have installed Django, which is a web framework. We'll understand how it helps us in development in a standard manner. Yeah, it is also useful. It helps us in deployment as well. This is slightly advanced, but yeah, it is quite helpful. Yeah, the third thing is it makes development easier and faster, because already provides us with all the basic things that are required in web development. It is readily available. We just have to implement it. Then yeah, so let's take an example of a car. So for a car, we need wheels. We need the doors, the outer structure, which is quite common in all the cars. All right, but what is going to change is basically the engine. It will be different in different cars. So web framework is similar. Like we can compare it with this car that wheels and doors are all almost there in all the cars. And then it is readily available. And OK, the person can focus only on the engine, which will give quality to that car. So that is how web framework helps us. So yeah, we can focus on the coding part. That is the business logic when we have some web development. So yeah, so authentication, session and link, some basic add, edit operations, which are quite common in a web app. So this will be handled by web framework. And we just have to focus on the logic that is quite important for a web app. So yeah, and yeah, there are many more things. As you develop, as you work on it, you will learn about it. Yeah, coming back to Django. So advantages, it is definitely fast, scalable. And yeah, security is also there. So quite a few advantages. It's a free and open source. And you don't need to know SQL. It's not necessary because Django has its own ORM, that is Object Manager. So these are a few things related to Django. Django installation has been done yesterday. Ankit has done that. So yeah, and you also have a virtual environment. It's a good practice to always create a virtual environment. We'll see a couple of things. I am sure yesterday Ankit spoke about this, about the virtual environment. So you all are aware of it, but still we'll talk about it. So obviously it will help you isolate system packages and the packages that you install on the system. So you have an isolated environment. So if you do something happen, something goes wrong in that environment, it won't affect your system packages because packages sometimes have dependency on other packages. So definitely it won't break your system, install Python packages. So good practice to have a virtual environment. Now there is always a question that Python and Django versions, we always have which Python version, Django version. OK, so according to me, any Django version you can use, it is definitely there is not much changes in the versions. There are definitely, but not quite tremendous changes. You will see. So yeah, the core remains the same. So that is why you can use any, but obviously it is better to go for the latest version. There are a couple of reasons. So we can use the latest version of Python if we have the latest Django version. And yeah, the security is main thing. The security improves with the version, so quite important. Yeah, so I am sure everyone is aware about the request response model between client and the server. So it's quite a common thing that we are aware of. That is what we are going to do right now. So the client will be sending a request to the server, HTTP request, the server where our Django relies will process it, and in return will send HTTP response. So we have Django, which is on the server side, will roughly look like this, which is, MVT will not go much on the MVT architecture, that is model view template. So basically Django, as I told you at the start, it helps you develop in a very standard way. So you will find your database, that is yesterday, I think Ankit gave you a brief introduction about all these files. So when you create a Django app, you'll see in app you have URLs, views, models, all these files waited for you. So whenever a request comes to the Django server, it hits the URL. So from URL, the views are wired by admins. It is for each URL, you have a view connected. So that particular view is called, which is your actual logic, the views, where you write your business logic. And here it is, basically it may have a database call, which is your models contains the database details. And once it processes all the data, it has obviously HTML, which will be its response. So it will call the templates, necessary templates, and then it will render accordingly and it will send back its response to the client. So point is the views, which is your logic, is separate from your templates, which will be seen by the user and the models, the database is separate. So you basically write your code on a, it is segregated. So that is the standard way. You don't write all the thing at one place and then it becomes difficult to maintain, difficult to scale, and difficult for someone who is new to understand your code and to scale it further. So quite a good practice of segregating your code. So yeah, all right, thank you. So this was more of a short kind of understanding what yesterday you all did. That is, what is Django? What is virtual environment? What is web framework? So what exactly is going to happen? How we are going to send a request, HTTP request to the server, and how we'll process it and we'll send a response back to the client. This is a basic goal for now. And yeah.