รวม URL ของแอปและตั้งชื่อเส้นทาง

Django splits routing into the project's urls.py and each app's own. The project includes app URLs to keep things tidy.

Giving each app its own URL file keeps routes reusable and self-contained. You can drop an app into any project cleanly.

To delegate to an app, you use include. Import it alongside path from django.urls in the project file.

In the project urls.py, point a prefix at an app's URL module with include. All its routes hang under that prefix.

The project prefix joins the app route. So blog/ plus an app route of post/ serves the full path blog/post/.

Give each route a name so you never hardcode its URL. You refer to the route by this stable name everywhere else.

If a URL changes, hardcoded links break. A named route lets you change the path once and every link still works.

Use reverse to build a URL from a route name in your view code. Django returns the current path for that name.

Set app_name in an app's urls.py to namespace its routes. Then names look like blog:detail, avoiding clashes between apps.

With a namespace set, you reference routes as namespace:name. This keeps blog:detail and shop:detail clearly separate.

The redirect helper also accepts a route name. Send users somewhere by name instead of a fragile literal path.

Recall what include() does in the project's urls.py.

Use include to mount app URLs under a prefix, and name routes so reverse and redirect stay solid when paths change. 🧭