กำหนดเทมเพลตพื้นฐานด้วยบล็อก

Every page on your site shares the same header, nav, and footer. Copying that HTML into each template is a maintenance trap. A base template fixes it. 🧩

A base template holds the full HTML skeleton once. Child pages reuse it and only fill in the parts that differ, so shared markup lives in a single file.

Inside the base, a block marks a region that child pages can override. Everything outside a block is fixed and shared by every page.

You open a region with a named block tag and close it with endblock. Anything between them is the default content for that slot.

This base.html wraps the doctype, head, and body once. The title and content blocks are the only parts pages will customize.

Give each block a descriptive name like content, title, or sidebar. Child pages reference blocks by that exact name when they override them.

Content between the block tags is a default. If a child page does not override the block, the visitor sees this fallback text instead.

Keep the layout in your templates folder, usually named base.html. Child templates point back to it by this path when they extend it.

Think about which page areas actually change: title, main body, maybe a sidebar. Each changing area becomes one block in your base layout.

A block may sit inside another block, like a head block holding a styles block. Nesting lets pages tweak fine details without redefining the whole region.

With a base template, updating the nav once changes every page at once. That single source of truth is the whole point of a shared layout. ✨

What is the purpose of a block tag in a base template?

A base template holds shared markup once and exposes named blocks as customizable slots. Next you will extend this base from child pages. 🎯