Herencia de plantillas con extends y block

Every page shares a header, nav, and footer. Template inheritance lets you write that shell once and reuse it everywhere. 🧱

A base template holds the common HTML skeleton. Child pages will plug their unique content into spots you leave open.

A block marks a section a child can replace. You name it, leave optional default content, then close it with endblock.

This base wraps a title block and a content block in real HTML. Children will fill those two named holes.

The extends tag must be the first line of a child template. It tells Django which base layout to build upon.

In the child you redefine a block with the same name. Whatever you put inside replaces the base default for that page.

If a child skips a block, the base content shows instead. That makes a default a safe placeholder for shared text.

Call block.super to keep the parent block content and add your own around it, instead of replacing it entirely.

A child can itself be a base for deeper pages. Layered layouts let sections share a sub-shell while still using the global one.

Only one extends is allowed and it must lead the file. Anything before it, even a comment, breaks the inheritance.

Think of a page as a base full of blocks that children fill. This keeps every page consistent and edits in one place.

Recall how a child connects to its layout.

You learned to define blocks in a base and fill them with extends in children, even keeping parent content via block.super. Next: linking routes and assets.