Model Architecture Planning

Django is based on the Model-View-Template software design architecture, which means that the Model takes care of our data and logic, the views will take care of what the users will see in the browser when you render your site, and the templates will take care of what we render as HTML, CSS, Javascript and our dynamic content.

It's good to visualize our models before defining them in our models.py for us to see how our model structure would be laid out. The figure below shows how we will determine the database of the blog we're building.

Models.py of the blog models.py

We've created the models for Post and Category. The figure we created also shows the relationship between both models including its multiplicities. According to moz://a are the numbers on the figure that shows the numbers (maximum and minimum) of each model that may be present in the relationship.- moz://a.

Now that we know ow we'll layout our models, let's start creating our project with the Cookiecutter-Django framework so we won't have too much of a hard time deploying our app in production.

Model Architecture Planning

Comments

Creating a blog with Cookiecutter-Django & deploying it to Heroku

Creating the models.py, views.py, urls.py, admin.py & the superuser

More from this blog

Deploying Cookiecutter Django on a DigitalOcean Droplet (Ubuntu 24.04 LTS)

Automating Cloudflare WARP Based on WiFi SSID (Linux Guide)

Hunting Disk Hogs on Ubuntu: A Shell Script for Finding the Largest Files

Renaming 1000+ Pages Worth of "Levels" Without Losing My Mind

How to Manually Backup WordPress Sites via SSH

Command Palette

Comments

Creating a blog with Cookiecutter-Django & deploying it to Heroku

Creating the models.py, views.py, urls.py, admin.py & the superuser

More from this blog