ต่อยอดเทมเพลตพื้นฐานในหน้าลูก

A child page does not repeat the skeleton. It declares that it extends the base, then fills only the blocks it needs to change. 🔗

The first line of a child template uses extends to name its parent layout. This tells Jinja2 to inherit the base before rendering.

The extends tag has to be the very first thing in the child file. Putting markup above it breaks inheritance and raises a template error.

To replace a slot, redeclare the block with the same name in the child. Whatever you put inside now shows instead of the base default.

This child template extends base.html and overrides two blocks. The rest of the page comes straight from the parent layout.

You only override the blocks you want to change. Any block you leave out keeps the default content defined in the base template.

Inside an overridden block you can call super() to pull in the parent block content, then add your own around it.

Your view returns the child template path. Flask renders the child, which inherits the base, so you never call base.html directly.

Override only works when the child block name exactly matches one in the base. A typo silently leaves the parent default in place.

Dozens of pages can extend the same base.html. Each child stays tiny because it only carries the markup unique to that page.

Change the base header once and every child page updates instantly. That cascade is the real power of template inheritance. 🚀

Where must the extends tag appear in a child template?

Child pages extend a base, override matching blocks, and may reuse parent content with super(). One base now powers many pages. 🎯