Tag: Django

Build web applications and backend services with the Django framework.

  • Building a Job Board Website with Django: A Beginner’s Guide

    Hello aspiring web developers! Have you ever wanted to create a website where people can find their dream jobs, and companies can post their openings? A “job board” website is a fantastic project to tackle, and today, we’re going to explore how you can build one using a powerful and friendly tool called Django.

    What is a Job Board Website?

    Imagine a digital bulletin board specifically designed for job postings. That’s essentially what a job board website is! It allows:
    * Job Seekers to browse available positions, filter them by location or industry, and apply.
    * Employers to create accounts, post new job listings, and manage their applications.

    It’s a hub connecting talent with opportunities.

    Why Choose Django for Your Job Board?

    When you decide to build a website, one of the first questions you’ll ask is, “What tools should I use?” For our job board, we’re going with Django.

    What is Django?

    Django is a web framework written in Python.
    * Web framework: Think of a web framework as a complete set of tools, rules, and pre-written code that helps you build websites much faster and more efficiently. Instead of starting from scratch, Django gives you a solid foundation.
    * Python: A very popular and easy-to-read programming language, known for its simplicity and versatility.

    Django follows a pattern called MVT (Model-View-Template). Don’t worry too much about the jargon now, but in simple terms:
    * Model: This is how you describe the data your website needs to store (e.g., a job’s title, description, salary) and how it interacts with your database.
    * View: This is the “brain” of your website. It decides what to do when someone visits a specific web address (URL), fetches data, and prepares it for display.
    * Template: This is the “face” of your website. It’s an HTML file that defines how your data is presented to the user, what the page looks like.

    Benefits of Using Django for a Job Board:

    1. Rapid Development: Django comes with many features “out-of-the-box,” meaning they are already built-in. This includes an excellent admin interface (a control panel for your website data), an ORM (Object-Relational Mapper), and user authentication.
      • ORM (Object-Relational Mapper): This is a cool tool that lets you interact with your database using Python code, without having to write complex database commands (SQL). It makes handling your job postings, users, and applications much simpler.
    2. Security: Building secure websites is super important. Django helps protect your site from many common web vulnerabilities like XSS (Cross-Site Scripting) and CSRF (Cross-Site Request Forgery), giving you peace of mind.
      • XSS (Cross-Site Scripting): A type of attack where malicious code is injected into a website, potentially stealing user information.
      • CSRF (Cross-Site Request Forgery): An attack that tricks users into performing unwanted actions on a website where they are logged in.
    3. Scalability: As your job board grows and more people use it, Django can handle the increased traffic and data efficiently. It’s built to grow with your project.
    4. Rich Ecosystem and Community: Django has a huge and helpful community. This means lots of resources, tutorials, and reusable apps (pieces of code for common tasks) are available, making development even easier.

    Essential Features for Our Job Board

    To make our job board functional, we’ll need to think about these core features:

    • Job Listing: Displaying available jobs with details like title, company, description, location, and salary.
    • Job Detail Page: A separate page for each job with all its specific information.
    • Searching and Filtering: Allowing users to find jobs based on keywords, location, or industry.
    • User Management: Handling user accounts for both job seekers and employers (who can post jobs).
    • Application System: A simple way for job seekers to apply for jobs (e.g., through a contact form or external link).

    Setting Up Your Django Project: A Step-by-Step Guide

    Let’s get our hands a little dirty and set up the basic structure of our job board.

    1. Prerequisites

    Before we start, make sure you have Python installed on your computer. Python usually comes with pip, which is Python’s package installer.

    2. Create a Virtual Environment

    It’s good practice to create a virtual environment for your project.
    * Virtual Environment: This creates an isolated space for your project’s dependencies (the libraries it needs). This prevents conflicts if you’re working on multiple Python projects that require different versions of the same library.

    Open your terminal or command prompt and run these commands:

    python -m venv job_board_env
    

    Now, activate your virtual environment:

    • On macOS/Linux:
      bash
      source job_board_env/bin/activate
    • On Windows (Command Prompt):
      bash
      job_board_env\Scripts\activate.bat
    • On Windows (PowerShell):
      powershell
      job_board_env\Scripts\Activate.ps1

      You’ll see (job_board_env) appear at the beginning of your terminal prompt, indicating it’s active.

    3. Install Django

    With your virtual environment active, install Django:

    pip install django
    

    4. Create Your Django Project

    Now, let’s create the main Django project. This will be the container for all your website’s settings and apps.

    django-admin startproject job_board_project .
    

    The . at the end means “create the project in the current directory,” which keeps your project files neatly organized.

    5. Create a Django App for Jobs

    In Django, projects are typically broken down into smaller, reusable apps. For our job board, we’ll create an app specifically for managing job listings.
    * Django App: A self-contained module within a Django project that handles a specific set of features (e.g., ‘jobs’ app for job listings, ‘users’ app for user accounts).

    Make sure you are in the job_board_project directory (where manage.py is located):

    python manage.py startapp jobs
    

    6. Register Your New App

    Django needs to know about the jobs app you just created. Open the job_board_project/settings.py file and add 'jobs' to the INSTALLED_APPS list.

    INSTALLED_APPS = [
        'django.contrib.admin',
        'django.contrib.auth',
        'django.contrib.contenttypes',
        'django.contrib.sessions',
        'django.contrib.messages',
        'django.contrib.staticfiles',
        'jobs',  # Add your new app here
    ]
    

    Building the Core Components of Your Job Board App

    Now that we have our project structure, let’s look at the basic elements within our jobs app.

    1. Models: Defining Our Job Data

    First, we need to tell Django what kind of data a job posting will have. We do this in jobs/models.py.

    from django.db import models
    
    class Job(models.Model):
        title = models.CharField(max_length=200)
        company = models.CharField(max_length=100)
        location = models.CharField(max_length=100)
        description = models.TextField()
        salary_min = models.IntegerField(blank=True, null=True)
        salary_max = models.IntegerField(blank=True, null=True)
        posted_date = models.DateTimeField(auto_now_add=True)
        application_link = models.URLField(blank=True, null=True)
    
        def __str__(self):
            return f"{self.title} at {self.company}"
    

    Here, we defined a Job model. Each field (like title, company, description) specifies the type of data it will hold. CharField is for short text, TextField for long text, IntegerField for numbers, and DateTimeField for dates and times. blank=True, null=True means these fields are optional.

    2. Database Migrations

    After defining your model, you need to tell Django to create the corresponding tables in your database.

    python manage.py makemigrations
    python manage.py migrate
    
    • makemigrations: This command tells Django to detect changes you’ve made to your models and create migration files.
    • migrate: This command applies those changes to your database, setting up the tables.

    3. Django Admin: Managing Jobs Easily

    One of Django’s most loved features is its automatic admin interface. To add, edit, or delete job postings easily, we just need to register our Job model in jobs/admin.py.

    First, you’ll need a superuser account to access the admin panel:

    python manage.py createsuperuser
    

    Follow the prompts to create a username, email, and password.

    Then, open jobs/admin.py:

    from django.contrib import admin
    from .models import Job
    
    admin.site.register(Job)
    

    Now, run your development server:

    python manage.py runserver
    

    Visit http://127.0.0.1:8000/admin/ in your browser, log in with your superuser credentials, and you’ll see “Jobs” listed! You can click on it to add new job postings.

    4. Views: Displaying Job Listings

    Next, we’ll create views to fetch the job data from the database and prepare it for our users. Open jobs/views.py:

    from django.shortcuts import render, get_object_or_404
    from .models import Job
    
    def job_list(request):
        jobs = Job.objects.all().order_by('-posted_date')
        return render(request, 'jobs/job_list.html', {'jobs': jobs})
    
    def job_detail(request, pk):
        job = get_object_or_404(Job, pk=pk)
        return render(request, 'jobs/job_detail.html', {'job': job})
    
    • job_list: This view fetches all Job objects from the database, orders them by the most recent posted_date, and sends them to a template called job_list.html.
    • job_detail: This view takes a job’s primary key (pk, a unique ID) from the URL, finds that specific job, and sends it to job_detail.html. get_object_or_404 is a handy function that will show a “404 Not Found” error if the job doesn’t exist.

    5. Templates: Making It Look Good

    Our views need templates to display the data. Create a new folder named templates inside your jobs app folder, and inside templates, create another folder named jobs. This structure helps Django find your templates.

    jobs/
    ├── admin.py
    ├── apps.py
    ├── __init__.py
    ├── migrations/
    ├── models.py
    ├── templates/
    │   └── jobs/
    │       ├── job_list.html
    │       └── job_detail.html
    ├── tests.py
    └── views.py
    

    Now, let’s create the template files:

    • jobs/templates/jobs/job_list.html:
      html
      <!DOCTYPE html>
      <html lang="en">
      <head>
      <meta charset="UTF-8">
      <meta name="viewport" content="width=device-width, initial-scale=1.0">
      <title>Job Board - All Jobs</title>
      </head>
      <body>
      <h1>Available Jobs</h1>
      {% if jobs %}
      <ul>
      {% for job in jobs %}
      <li>
      <h3><a href="{% url 'job_detail' pk=job.pk %}">{{ job.title }}</a></h3>
      <p><strong>Company:</strong> {{ job.company }}</p>
      <p><strong>Location:</strong> {{ job.location }}</p>
      <p>Posted on: {{ job.posted_date|date:"F d, Y" }}</p>
      </li>
      {% endfor %}
      </ul>
      {% else %}
      <p>No jobs available at the moment. Check back soon!</p>
      {% endif %}
      </body>
      </html>

      Here, {% for job in jobs %} is a Django template tag that loops through each job. {{ job.title }} displays the job’s title. {% url 'job_detail' pk=job.pk %} creates a link to the detail page for each job.

    • jobs/templates/jobs/job_detail.html:
      html
      <!DOCTYPE html>
      <html lang="en">
      <head>
      <meta charset="UTF-8">
      <meta name="viewport" content="width=device-width, initial-scale=1.0">
      <title>{{ job.title }} - {{ job.company }}</title>
      </head>
      <body>
      <h1>{{ job.title }}</h1>
      <p><strong>Company:</strong> {{ job.company }}</p>
      <p><strong>Location:</strong> {{ job.location }}</p>
      {% if job.salary_min and job.salary_max %}
      <p><strong>Salary Range:</strong> ${{ job.salary_min }} - ${{ job.salary_max }}</p>
      {% elif job.salary_min %}
      <p><strong>Minimum Salary:</strong> ${{ job.salary_min }}</p>
      {% endif %}
      <hr>
      <h3>Job Description</h3>
      <p>{{ job.description|linebreaksbr }}</p>
      {% if job.application_link %}
      <p><a href="{{ job.application_link }}" target="_blank">Apply Now!</a></p>
      {% endif %}
      <p><a href="{% url 'job_list' %}">Back to Job List</a></p>
      </body>
      </html>

    6. URLs: Connecting Everything

    Finally, we need to define the web addresses (URLs) that will trigger our views and display our templates. This involves two urls.py files: one for the entire project and one for our jobs app.

    First, create a urls.py file inside your jobs app folder (jobs/urls.py):

    from django.urls import path
    from . import views
    
    urlpatterns = [
        path('', views.job_list, name='job_list'),
        path('job/<int:pk>/', views.job_detail, name='job_detail'),
    ]
    
    • path('', views.job_list, name='job_list'): This means when someone visits the root of our jobs app (e.g., /jobs/), the job_list view will be called, and we’ve named this URL pattern job_list.
    • path('job/<int:pk>/', views.job_detail, name='job_detail'): This matches URLs like /jobs/job/1/ or /jobs/job/5/. The <int:pk> part captures an integer (the job’s ID) and passes it to the job_detail view as pk.

    Next, we need to include these app-specific URLs in our main project’s urls.py (job_board_project/urls.py):

    from django.contrib import admin
    from django.urls import path, include
    
    urlpatterns = [
        path('admin/', admin.site.urls),
        path('jobs/', include('jobs.urls')), # Include our jobs app's URLs
    ]
    

    Now, when you visit http://127.0.0.1:8000/jobs/, Django will direct the request to your jobs app’s urls.py, which will then call the job_list view and display job_list.html. Clicking on a job will take you to http://127.0.0.1:8000/jobs/job/<id>/, displaying its details.

    Running Your Job Board

    Make sure your server is running (if not, python manage.py runserver).
    1. Go to http://127.0.0.1:8000/admin/ and add a few job postings.
    2. Then, visit http://127.0.0.1:8000/jobs/ in your browser. You should see your job list!

    Congratulations! You’ve just laid the foundation for your very own job board website using Django.

    What’s Next? Further Enhancements!

    This is just the beginning. To make your job board even better, you could add:

    • User Authentication: Allow users to register, log in, and manage their own profiles (as job seekers or employers).
    • Job Application Forms: Create forms for job seekers to submit their resumes and cover letters directly through your site.
    • Search and Filtering: Implement more robust search functionality and filters by category, salary, or experience level.
    • Employer Dashboard: A dedicated section for employers to post new jobs, view applicants, and manage their listings.
    • Deployment: Learn how to put your website live on the internet so everyone can access it.

    Building a job board is a fantastic learning experience that touches on many core web development concepts. Django makes it accessible and enjoyable. Keep experimenting, keep building, and happy coding!

  • Django for Beginners: Building Your First Simple CRUD Application

    Hello future web developers! Are you curious about building websites but feel a bit overwhelmed? You’re in the right place! Today, we’re going to dive into Django, a powerful yet friendly web framework that uses Python. We’ll build a “CRUD” application, which is a fantastic way to understand how web applications handle information.

    What is Django?

    Imagine you want to build a house. Instead of crafting every brick, pipe, and wire yourself, you’d use a construction kit with pre-made components, tools, and a clear plan. That’s essentially what Django is for web development!

    Django is a “web framework” built with Python. A web framework is a collection of tools and components that help you build websites faster and more efficiently. It handles many of the repetitive tasks involved in web development, letting you focus on the unique parts of your application. Django is known for its “batteries-included” philosophy, meaning it comes with a lot of features already built-in, like an administrative interface, an Object-Relational Mapper (ORM), and template system.

    What is CRUD?

    CRUD is an acronym that stands for:

    • Create: Adding new information (like adding a new post to a blog).
    • Read: Viewing existing information (like reading a blog post).
    • Update: Changing existing information (like editing a blog post).
    • Delete: Removing information (like deleting a blog post).

    These are the fundamental operations for almost any application that manages data, and mastering them in Django is a huge step! We’ll build a simple “Task Manager” where you can create, view, update, and delete tasks.


    1. Setting Up Your Development Environment

    Before we start coding, we need to set up our workspace.

    Install Python and pip

    Make sure you have Python installed on your computer. You can download it from python.org. Python usually comes with pip, which is Python’s package installer (a tool to install other Python libraries).

    Create a Virtual Environment

    It’s a good practice to use a “virtual environment” for each project. Think of it as an isolated box for your project’s dependencies. This prevents conflicts between different projects that might use different versions of the same library.

    Open your terminal or command prompt and run these commands:

    python -m venv myenv
    

    This creates a new folder named myenv (you can choose any name) which will hold your virtual environment.

    Next, activate it:

    • On Windows:
      bash
      .\myenv\Scripts\activate
    • On macOS/Linux:
      bash
      source myenv/bin/activate

      You’ll see (myenv) at the beginning of your command prompt, indicating the virtual environment is active.

    Install Django

    With your virtual environment active, let’s install Django:

    pip install django
    

    2. Starting Your Django Project and App

    In Django, a “project” is the entire web application, and “apps” are smaller, reusable modules within that project (e.g., a “blog” app, a “users” app).

    Create a Django Project

    Navigate to where you want to store your project and run:

    django-admin startproject taskmanager .
    

    Here, taskmanager is the name of our project. The . at the end tells Django to create the project files in the current directory, rather than creating an extra taskmanager folder inside another taskmanager folder.

    Create a Django App

    Now, let’s create our first app within the project:

    python manage.py startapp tasks
    

    This creates a new folder named tasks with several files inside. This tasks app will handle everything related to our tasks (like creating, viewing, and managing them).

    Register Your App

    Django needs to know about the new app. Open taskmanager/settings.py (inside your taskmanager folder) and add 'tasks' to the INSTALLED_APPS list:

    INSTALLED_APPS = [
        'django.contrib.admin',
        'django.contrib.auth',
        'django.contrib.contenttypes',
        'django.contrib.sessions',
        'django.contrib.messages',
        'django.contrib.staticfiles',
        'tasks', # Our new app!
    ]
    

    3. Defining Your Data (Models)

    In Django, you describe how your data looks using “models.” A model is a Python class that defines the structure of your data and tells Django how to store it in a database.

    Open tasks/models.py and let’s define our Task model:

    from django.db import models
    
    class Task(models.Model):
        title = models.CharField(max_length=200)
        description = models.TextField(blank=True, null=True)
        completed = models.BooleanField(default=False)
        created_at = models.DateTimeField(auto_now_add=True)
    
        def __str__(self):
            return self.title
    
    • title: A short text field for the task name. max_length is required.
    • description: A longer text field. blank=True means it can be left empty, null=True means the database can store NULL for this field.
    • completed: A true/false field, default=False means a new task is not completed by default.
    • created_at: A date and time field that automatically gets set when a task is created.
    • def __str__(self): This special method tells Django how to represent a Task object as a string, which is helpful in the Django admin and when debugging.

    Make and Apply Migrations

    After defining your model, you need to tell Django to create the corresponding table in your database. This is done with “migrations.” Migrations are Django’s way of propagating changes you make to your models into your database schema.

    In your terminal (with the virtual environment active), run:

    python manage.py makemigrations
    python manage.py migrate
    

    makemigrations creates migration files (instructions for changes), and migrate applies those changes to your database.


    4. Making Things Happen (Views)

    “Views” are Python functions or classes that receive web requests and return web responses. They are the heart of your application’s logic. For CRUD operations, Django provides helpful “Class-Based Views” (CBVs) that simplify common tasks.

    Open tasks/views.py and add these views:

    from django.views.generic import ListView, DetailView, CreateView, UpdateView, DeleteView
    from django.urls import reverse_lazy
    from .models import Task
    
    class TaskListView(ListView):
        model = Task
        template_name = 'tasks/task_list.html' # HTML file to display list of tasks
        context_object_name = 'tasks' # Name for the list of tasks in the template
    
    class TaskDetailView(DetailView):
        model = Task
        template_name = 'tasks/task_detail.html' # HTML file to display a single task
        context_object_name = 'task'
    
    class TaskCreateView(CreateView):
        model = Task
        template_name = 'tasks/task_form.html' # HTML form for creating a task
        fields = ['title', 'description', 'completed'] # Fields to show in the form
        success_url = reverse_lazy('task_list') # Where to go after successfully creating a task
    
    class TaskUpdateView(UpdateView):
        model = Task
        template_name = 'tasks/task_form.html' # HTML form for updating a task
        fields = ['title', 'description', 'completed']
        success_url = reverse_lazy('task_list')
    
    class TaskDeleteView(DeleteView):
        model = Task
        template_name = 'tasks/task_confirm_delete.html' # HTML page to confirm deletion
        success_url = reverse_lazy('task_list') # Where to go after successfully deleting a task
    
    • ListView: Displays a list of objects.
    • DetailView: Displays a single object’s details.
    • CreateView: Handles displaying a form and saving a new object.
    • UpdateView: Handles displaying a form and updating an existing object.
    • DeleteView: Handles confirming deletion and deleting an object.
    • reverse_lazy(): A function that helps Django figure out the URL name from our urls.py file, even before the URLs are fully loaded.

    5. Creating the User Interface (Templates)

    Templates are HTML files that Django uses to display information to the user. They can include special Django syntax to show data from your views.

    First, tell Django where to find your templates. Create a folder named templates inside your tasks app folder (tasks/templates/). Inside tasks/templates/, create another folder named tasks/ (tasks/templates/tasks/). This structure helps organize templates for different apps.

    Your folder structure should look like this:

    taskmanager/
    ├── taskmanager/
    │   ├── ...
    ├── tasks/
    │   ├── migrations/
    │   ├── templates/
    │   │   └── tasks/  <-- Our templates will go here!
    │   ├── __init__.py
    │   ├── admin.py
    │   ├── apps.py
    │   ├── models.py
    │   ├── tests.py
    │   └── views.py
    ├── manage.py
    └── db.sqlite3
    

    Now, let’s create the basic HTML files inside tasks/templates/tasks/:

    task_list.html (Read – List all tasks)

    <!-- tasks/templates/tasks/task_list.html -->
    <h1>My Task List</h1>
    <a href="{% url 'task_create' %}">Create New Task</a>
    
    <ul>
        {% for task in tasks %}
        <li>
            <a href="{% url 'task_detail' task.pk %}">{{ task.title }}</a>
            - {{ task.description|default:"No description" }}
            - Status: {% if task.completed %}Completed{% else %}Pending{% endif %}
            - <a href="{% url 'task_update' task.pk %}">Edit</a>
            - <a href="{% url 'task_delete' task.pk %}">Delete</a>
        </li>
        {% empty %}
        <li>No tasks yet!</li>
        {% endfor %}
    </ul>
    

    task_detail.html (Read – View a single task)

    <!-- tasks/templates/tasks/task_detail.html -->
    <h1>Task: {{ task.title }}</h1>
    <p>Description: {{ task.description|default:"No description" }}</p>
    <p>Status: {% if task.completed %}Completed{% else %}Pending{% endif %}</p>
    <p>Created: {{ task.created_at }}</p>
    
    <a href="{% url 'task_update' task.pk %}">Edit Task</a> |
    <a href="{% url 'task_delete' task.pk %}">Delete Task</a> |
    <a href="{% url 'task_list' %}">Back to List</a>
    

    task_form.html (Create & Update)

    <!-- tasks/templates/tasks/task_form.html -->
    <h1>{% if form.instance.pk %}Edit Task{% else %}Create New Task{% endif %}</h1>
    
    <form method="post">
        {% csrf_token %} {# Security token required by Django for forms #}
        {{ form.as_p }} {# Renders form fields as paragraphs #}
        <button type="submit">Save Task</button>
    </form>
    
    <a href="{% url 'task_list' %}">Cancel</a>
    

    task_confirm_delete.html (Delete)

    <!-- tasks/templates/tasks/task_confirm_delete.html -->
    <h1>Delete Task</h1>
    <p>Are you sure you want to delete "{{ task.title }}"?</p>
    
    <form method="post">
        {% csrf_token %}
        <button type="submit">Yes, delete</button>
        <a href="{% url 'task_list' %}">No, go back</a>
    </form>
    

    6. Connecting URLs (URL Routing)

    URL routing is how Django maps incoming web addresses (URLs) to the correct “views” in your application.

    First, create a urls.py file inside your tasks app folder (tasks/urls.py).

    from django.urls import path
    from .views import TaskListView, TaskDetailView, TaskCreateView, TaskUpdateView, TaskDeleteView
    
    urlpatterns = [
        path('', TaskListView.as_view(), name='task_list'), # Home page, lists all tasks
        path('task/<int:pk>/', TaskDetailView.as_view(), name='task_detail'), # View a single task
        path('task/new/', TaskCreateView.as_view(), name='task_create'), # Create a new task
        path('task/<int:pk>/edit/', TaskUpdateView.as_view(), name='task_update'), # Edit an existing task
        path('task/<int:pk>/delete/', TaskDeleteView.as_view(), name='task_delete'), # Delete a task
    ]
    
    • path('', ...): Matches the base URL of this app.
    • path('task/<int:pk>/', ...): Matches URLs like /task/1/ or /task/5/. <int:pk> captures the task’s primary key (a unique ID) and passes it to the view.
    • name='...': Gives a unique name to each URL pattern, making it easier to refer to them in templates and views.

    Next, you need to include these app URLs into your project’s main urls.py. Open taskmanager/urls.py:

    from django.contrib import admin
    from django.urls import path, include # Make sure 'include' is imported
    
    urlpatterns = [
        path('admin/', admin.site.urls),
        path('', include('tasks.urls')), # Include our tasks app's URLs here
    ]
    

    Now, when someone visits your website’s root URL (e.g., http://127.0.0.1:8000/), Django will direct that request to our tasks app’s urls.py file.


    7. Running Your Application

    You’ve done a lot of work! Let’s see it in action.

    In your terminal, make sure your virtual environment is active, and you are in the directory where manage.py is located. Then run:

    python manage.py runserver
    

    You should see output indicating the server is running, usually at http://127.0.0.1:8000/. Open this address in your web browser.

    You should now see your “My Task List” page! Try to:
    * Click “Create New Task” to add a task (Create).
    * See the task appear in the list (Read – List).
    * Click on a task’s title to view its details (Read – Detail).
    * Click “Edit” to change a task (Update).
    * Click “Delete” to remove a task (Delete).

    Congratulations! You’ve successfully built your first simple CRUD application using Django.


    Conclusion

    You’ve just built a complete web application that can manage data – a huge accomplishment for a beginner! You learned about:

    • Django projects and apps: How to organize your code.
    • Models: Defining your data structure.
    • Migrations: Syncing models with your database.
    • Views: Handling requests and responses using Django’s powerful Class-Based Views.
    • Templates: Creating dynamic HTML pages.
    • URL Routing: Connecting web addresses to your application logic.

    This is just the beginning of your Django journey. There’s so much more to explore, like user authentication, forms, static files, and deploying your application. Keep practicing, keep building, and don’t be afraid to experiment! Happy coding!