MVT splits a Django app into three parts: a model, a view and a template. In Model-View-Controller (MVC) terms, the controller is the framework itself, the URL dispatcher that sends each request to the right view.
The model defines the data structure and the business logic tied to that data. It works with the database through the Django ORM, which maps classes to tables.
The view holds the business logic for one request and acts as the bridge between model and template. It takes the request and returns a response.
The template is the presentation layer, usually HTML. It defines how the data is displayed to users.
The URL dispatcher routes each request to a view. The view processes the request and works with the models. It then renders a template with the data, and Django sends the response to the user.
Rewriting in plainer words…
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
