Basics for Djangos
Django basics cover the structure of a project and how a request becomes a response. A project holds settings and URL configuration, apps are self-contained modules, URL patterns map paths to views, and views return responses, often by rendering templates with context. Understanding this flow is the base for every other Django feature.
Stage: Django Core · Part of the Django roadmap · Last reviewed 19 November 2026
What to learn in Basics
- Create a project and an app with django-admin and manage.py
- Map URL paths to views using path() and include()
- Write function-based and class-based views
- Render a template with context, inheritance and template tags
- Serve static files in development
- Explain the request and response cycle through middleware
Basics interview questions
What is the difference between a Django project and an app?
A project is the whole website, with settings and root URL configuration. An app is a reusable module that does one thing, such as blog or accounts, with its own models and views. One project contains several apps, and an app can be reused elsewhere.
What is the difference between function-based and class-based views?
Function-based views are plain functions taking a request and returning a response, which are simple and explicit. Class-based views organise behaviour into methods per HTTP verb and support inheritance and mixins, which reduces repetition for common patterns such as lists and forms.
Where Basics fits in the Django roadmap
Basics belongs to the Django Core stage (beginner level), which takes about 20 hours. Project structure.
Other units in this stage
Back to the full Django roadmap