Why templates separate presentation from logic in Laravel - See It in Action

Why Templates Separate Presentation from Logic in Laravel

📖 Scenario: You are building a simple Laravel web page that shows a list of products with their prices. You want to keep the code clean and easy to manage by separating the data and logic from the HTML that displays it.

🎯 Goal: Create a Laravel Blade template that displays product names and prices passed from a controller. Learn how separating the data logic from the HTML presentation helps keep your code organized and easier to maintain.

📋 What You'll Learn

Create a PHP array of products with names and prices in the controller.

Pass the products array to a Blade template.

Use Blade syntax to loop through the products and display them.

Keep the PHP logic in the controller and only HTML with Blade directives in the template.

💡 Why This Matters

🌍 Real World

Separating logic and presentation is common in web development to keep code clean and easy to update. Laravel uses Blade templates to help with this separation.

💼 Career

Understanding how to separate data logic from HTML is essential for working with Laravel and many other web frameworks. It improves teamwork and code quality.

1

Create the products array in the controller

In your Laravel controller, create a variable called $products that is an array with these exact entries: ['Apple' => 1.2, 'Banana' => 0.5, 'Cherry' => 2.0].

Laravel

<?php

namespace App\Http\Controllers;

use Illuminate\Http\Request;
use App\Http\Controllers\Controller;

class ProductController extends Controller
{
    public function index()
    {
        // Create the products array here
        // Your code here
    }
}

Hint

Use a PHP array with product names as keys and prices as values.

2

Pass the products array to the Blade template

In the index method, return the view called 'products' and pass the $products array to it using the compact function.

Laravel

 1.2, 'Banana' => 0.5, 'Cherry' => 2.0];
        // Return the 'products' view and pass $products
        // Your code here
    }
}

Hint

Use return view('products', compact('products')); to send data to the Blade template.

3

Create the Blade template to display products

In the resources/views folder, create a Blade template file called products.blade.php. Use a @foreach loop with variables $name and $price to iterate over $products and display each product name and price inside an unordered list.

Laravel

Hint

Use Blade syntax: @foreach ($products as $name => $price) and {{ $name }}, {{ $price }} inside list items.

4

Explain why templates separate presentation from logic

Add a comment at the top of products.blade.php explaining that keeping PHP logic in the controller and HTML in the Blade template helps keep code clean, easier to read, and maintain.

Laravel

    @foreach ($products as $name => $price)
        {{ $name }}: ${{ $price }}
    @endforeach

Hint

Write a clear comment about why separating logic and presentation is helpful.

Practice

1. Why do Laravel templates separate presentation from logic?

easy

A. To prevent any changes to the website layout

B. To make the website load faster by combining code and design

C. To allow users to write PHP code directly in HTML

D. To keep the design and code easier to manage and update

Solution

1. Step 1: Understand the purpose of separation

   Separating presentation from logic means keeping design (HTML) apart from code (PHP) to avoid confusion and complexity.

2. Step 2: Benefits of separation in Laravel

   This separation makes it easier to update the look without breaking the code and vice versa, improving maintainability.

3. Final Answer:

   To keep the design and code easier to manage and update -> Option D

4. Quick Check:

   Separation improves manageability = A [OK]

Hint: Templates separate design and code for easier updates [OK]

Common Mistakes:

• Thinking templates speed up loading by combining code
• Believing users write PHP directly in HTML templates
• Assuming separation prevents any layout changes

2. Which of the following is the correct way to display a variable in a Laravel Blade template?

easy

A. {{ $name }}

B. <?php echo $name; ?>

C. [[ $name ]]

D. echo($name)

Solution

1. Step 1: Identify Blade syntax for variables

   Laravel Blade uses double curly braces {{ }} to safely display variables in templates.

2. Step 2: Compare options

   {{ $name }} uses the correct Blade syntax. <?php echo $name; ?> is plain PHP, not Blade. [[ $name ]] and echo($name) are invalid syntax in Blade.

3. Final Answer:

   {{ $name }} -> Option A

4. Quick Check:

   Blade variable display = {{ $name }} [OK]

Hint: Use {{ }} to show variables in Blade templates [OK]

Common Mistakes:

• Using raw PHP tags instead of Blade syntax
• Trying non-standard brackets like [[ ]]
• Using echo() without PHP tags in Blade

3. Given this Blade template snippet:

<h1>Hello, {{ $user }}!</h1>
<p>You have {{ $messages }} new messages.</p>

What will be the output if $user = 'Anna' and $messages = 3?

medium

A. Hello, Anna!You have 3 new messages.

B. Hello, $user!You have $messages new messages.

C. Hello, !You have new messages.

D. Syntax error due to missing PHP tags

Solution

1. Step 1: Substitute variables in Blade syntax

   The Blade template replaces {{ $user }} with 'Anna' and {{ $messages }} with 3.

2. Step 2: Render the final HTML output

   The output becomes <h1>Hello, Anna!</h1><p>You have 3 new messages.</p>, which is valid HTML.

3. Final Answer:

   <h1>Hello, Anna!</h1><p>You have 3 new messages.</p> -> Option A

4. Quick Check:

   Blade variables replaced correctly = D [OK]

Hint: Variables inside {{ }} show their values in output [OK]

Common Mistakes:

• Expecting variable names to appear literally
• Confusing Blade with raw PHP output
• Thinking missing PHP tags cause errors in Blade

4. This Blade template code has an error:

<ul>
  @foreach($items as $item)
    <li>{{ $item }}</li>
  @endforeach
</ul>

What is the likely cause if the page shows no list items?

medium

A. Blade does not support loops inside templates

B. The @foreach directive is misspelled

C. The $items variable is empty or not passed to the view

D. The {{ $item }} syntax is incorrect

Solution

1. Step 1: Check the loop and variable usage

   The @foreach directive and {{ $item }} syntax are correct Blade patterns for looping and displaying.

2. Step 2: Identify why no items show

   If no list items appear, the $items variable is likely empty or missing data passed from the controller.

3. Final Answer:

   The $items variable is empty or not passed to the view -> Option C

4. Quick Check:

   Empty data causes no output = C [OK]

Hint: Empty or missing data means loops show no output [OK]

Common Mistakes:

• Assuming syntax errors when code is correct
• Thinking Blade cannot loop over arrays
• Confusing variable display syntax with errors

5. You want to keep your Laravel Blade templates clean by avoiding complex PHP logic inside them. Which approach best follows the principle of separating presentation from logic?

hard

A. Write all PHP logic directly inside Blade templates using @php blocks

B. Put all data processing and decisions in the controller, pass only final data to the template

C. Mix HTML and PHP code freely in the Blade template for flexibility

D. Use JavaScript inside templates to handle all logic instead of PHP

Solution

1. Step 1: Understand separation of concerns

   Logic like data processing belongs in controllers, while templates handle only display.

2. Step 2: Evaluate options for best practice

   Putting all data processing and decisions in the controller and passing only final data to the template keeps templates simple and maintainable. Writing all PHP logic directly inside Blade templates using @php blocks or mixing HTML and PHP code freely mixes logic and presentation, making code messy. Using JavaScript inside templates to handle all logic shifts logic to the client-side, which is not the Laravel way for server-side rendering.

3. Final Answer:

   Put all data processing and decisions in the controller, pass only final data to the template -> Option B

4. Quick Check:

   Keep logic in controller, templates for display = A [OK]

Hint: Keep logic in controllers, templates only show data [OK]

Common Mistakes:

• Putting complex PHP logic inside Blade templates
• Mixing HTML and PHP code without separation
• Relying on JavaScript for server-side logic