All 7 Template Engines (Blade & Twig) questions
More in Template Engines (Blade & Twig)
What is a template engine, and how do Blade and Twig help separate a PHP application's presentation logic from its business logic? How do Blade and Twig automatically escape output by default, and why is this an important security feature? How do control structures like loops and conditionals work within Blade and Twig templates, and how do they compare to writing the equivalent raw PHP directly inside an HTML file? What are Blade components and Twig macros, and how do they help you create reusable pieces of template markup that can be used consistently across many different pages? How can template caching and precompilation in Blade and Twig improve the performance of rendering templates on every incoming request? What are the tradeoffs of using a heavier server side template engine like Blade or Twig compared to building a fully client side rendered frontend using a JavaScript framework consuming a PHP API?
Advertisement
Back to results for “Architecture”
PHP › Template Engines (Blade & Twig)

How does template inheritance work in Blade and Twig, allowing you to define a shared base layout that individual pages can extend?

Intermediate

Answer

Template inheritance lets you define a single base layout template containing shared structural elements common to every page, such as the header, navigation menu, and footer, along with one or more named sections left intentionally empty as placeholders, and individual page templates then extend that base layout, filling in only the specific content unique to that particular page within those designated placeholder sections, which avoids duplicating the same shared layout markup across every single page in an application.
{{-- Blade: layout.blade.php --}}
<html><body>@yield('content')</body></html>

{{-- Blade: page.blade.php --}}
@extends('layout')
@section('content')
    <p>Page content here</p>
@endsection
Real-world example A large website defines a single shared base layout containing its consistent header and footer, with every individual page template extending that layout and only providing its own unique main content, avoiding the need to repeat the same header and footer markup across dozens of separate page files.

Common follow-ups: Can a template extend more than one parent layout at the same time?;How do Blade components differ from traditional template inheritance for reusing markup?

MVC Architecture in PHP;Laravel Framework Essentials
All 7 Template Engines (Blade & Twig) questions