รวมส่วนประกอบที่นำกลับมาใช้ได้

A navbar or footer appears on many pages but is not the whole layout. For these chunks you reach for include instead of inheritance. 🧱

Use extends to inherit a full skeleton, but use include to drop a small reusable snippet into the current template at that spot.

The include tag pastes another template file right where you place it. The included file renders as if its markup were written inline.

A partial is an ordinary template holding only a fragment, like a nav bar. Naming it _navbar.html signals it is meant to be included.

You can include a partial inside the base so every page that extends it gets the navbar automatically, with no repeated markup.

An included partial can read the same variables as the page that includes it, so a navbar can show the logged-in user name.

You can hand a partial its own values with with, scoping variables so the snippet stays focused and predictable.

Add ignore missing so a missing partial is skipped silently instead of crashing the page render.

A good partial does one job: a footer, a flash message bar, a single card. Small, focused fragments are easy to reuse and reason about.

Group fragments under a partials subfolder and reference them by that path. It keeps full pages and reusable snippets clearly separated.

Fix the footer in its partial and every page that includes it updates together. That single edit is exactly why include exists. ✨

When should you reach for include instead of extends?

Use include to embed small shared snippets like navbars and footers. Keep them tiny, folder-organized, and edit them in one place. 🎯