startapp et l’organisation du dossier d’application

A Django project is made of small, focused pieces called apps. Each app handles one feature, like a blog or a shop. 🧱

You make a new app with the startapp command. Django generates a ready-to-edit folder so you never start from a blank page.

That command drops a blog/ folder next to manage.py. Inside are several files, each with one clear job that you will meet next.

The models.py file is where you describe your data as Python classes. Each class becomes a database table later on.

The views.py file holds the logic that runs when a page is requested. A view takes a request and returns a response.

The admin.py file lets you register models so they show up in Django's built-in admin site for easy editing.

The apps.py file holds a small config class that gives your app its name and settings. You rarely touch it at first.

The tests.py file is where your automated tests live. Writing tests here helps you change code without breaking things.

The migrations folder tracks how your database structure changes over time. Django fills it in automatically as your models evolve.

Notice startapp does not create a urls.py for the app. You add one yourself when you want to route pages to your views.

Because each app is self-contained, you can lift a well-made app out of one project and drop it into another with little effort. ♻️

Which file does startapp create for your data models?

You ran startapp and learned each file's job: models for data, views for logic, admin and apps for config. Apps keep features tidy and reusable. 🎉