Las etiquetas url y static

Typing URLs and file paths by hand breaks the moment they change. Django gives you the url and static tags to build them safely. 🔗

The url tag turns a route name into its real path. Rename the URL pattern later and every link updates automatically.

For url to work, give each pattern a name in urls.py. That name is the stable handle the template refers to.

If a route needs a value, pass it after the name. Django slots the argument into the path where the converter expects it.

When an app sets an app_name, reference routes with a prefix like blog:detail to avoid clashing with other apps.

The static tag builds the correct URL to a CSS, JS, or image file, even when storage paths differ in production.

Before using the tag you must load static near the top of the template, which pulls the tag into that file.

Combine the pieces to link a stylesheet the safe way, so the path stays valid no matter where files are served from.

The same static tag works for images. Point it at a file under your static folder and Django resolves the full URL.

In production, assets often move to a CDN or hashed path. The static tag hides that, so your templates never need editing.

Both tags share a purpose: let Django compute paths so you do not. Use url for views and static for files.

You learned to build view paths with the url tag and asset paths with static, after loading static. That wraps up rendering HTML with data.