render() et le contexte du gabarit

A template is an HTML file with little placeholders. Your view fills those blanks with real data before it reaches the browser. 🎨

The context is just a Python dictionary your view hands to the template. Its keys become the variables you can print inside the page.

The render() shortcut takes the request, a template name, and a context, then returns a finished HttpResponse for you.

Here a view passes one value to a template. Notice how render() does all the loading and response work in a single line.

Inside the template you print a context value with double braces. Django swaps {{ name }} for whatever your view sent.

Django looks for templates in a templates folder, usually one per app. Keeping them there lets the loader find each file by name.

Nesting templates under an app-named subfolder is a namespace. It stops two apps from fighting over the same file name.

The template language uses a dot for everything: dictionary keys, object attributes, and list items all read as value.key.

If a context variable is missing, Django prints an empty string instead of crashing. This silent failure keeps pages from breaking on small gaps.

Your context can hold as many keys as you like, mixing strings, numbers, lists, and objects. The template reads each by its key.

Do heavy work in the view, not the page. The template should mostly display data, keeping presentation and logic comfortably separate.

Think about how data travels from a view to a page.

You learned that render() joins a request, a template, and a context dict into one response, and that {{ }} prints those values. Next up: tags and filters.