Mail templates in Laravel - Step-by-Step Execution

Concept Flow - Mail templates

Create Mailable Class

↓

Define build() method

↓

Select Mail Template View

↓

Pass Data to View

↓

Send Mail Using Mailable

↓

Mail Rendered with Template and Data

This flow shows how Laravel uses a Mailable class to select a mail template, pass data, and send the email.

Execution Sample

Laravel

class OrderShipped extends Mailable {
  public $order;

  public function __construct($order) {
    $this->order = $order;
  }

  public function build() {
    return $this->view('emails.shipped')
                ->with(['order' => $this->order]);
  }
}

Mail::to($user)->send(new OrderShipped($order));

This code creates a mail template class that uses a Blade view and sends it to a user with order data.

Execution Table

Step	Action	Evaluation	Result
1	Create OrderShipped Mailable instance	new OrderShipped($order)	Instance with order data stored
2	Call build() method	return view('emails.shipped') with order data	Selects Blade template and attaches data
3	Call Mail::to($user)->send()	Send email using Mailable	Email queued for sending with rendered template
4	Render Blade template	Replace {{order}} placeholders	Final email content with order details
5	Email sent to user	User receives email	User sees formatted email with order info

💡 Email sent successfully with the selected template and data.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
order	undefined	Order object passed	Passed to view data	Used in email content	Remains unchanged
mailable	undefined	Instance created	build() returns view with data	Used to send email	Instance used for rendering
email_content	undefined	undefined	Rendered with order data	Sent to user	Delivered email content

Key Moments - 3 Insights

Why do we use a Mailable class instead of sending raw HTML directly?

The Mailable class organizes email logic and templates clearly. As shown in step 1 and 2 of the execution_table, it helps pass data and select templates cleanly.

How does the Blade template get the order data?

In step 2, the build() method attaches the order data with ->with(['order' => $this->order]). This makes the data available inside the Blade view.

When is the email content actually rendered?

Step 4 shows the Blade template rendering happens just before sending, replacing placeholders with real data.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at Step 2?

A The Mailable instance is created

B The email is sent to the user

C The build() method selects the mail template and attaches data

D The Blade template is rendered

💡 Hint

Check the 'Action' and 'Result' columns at Step 2 in the execution_table

At which step is the email content rendered with order details?

A Step 3

B Step 4

C Step 1

D Step 5

💡 Hint

Look for 'Render Blade template' in the 'Action' column of execution_table

If we do not pass order data in build(), what changes in variable_tracker?

A email_content renders without order data

B order remains undefined in all steps

C order is passed but empty

D mailable instance is not created

💡 Hint

Check the 'order' row in variable_tracker and consider what happens if data is not passed

Concept Snapshot

Laravel Mail Templates:
- Create a Mailable class with build() method
- Use ->view('template') to select Blade template
- Pass data with ->with([...])
- Send mail with Mail::to()->send(new Mailable)
- Blade renders template with data before sending

Full Transcript

In Laravel, mail templates are managed by creating a Mailable class. This class has a build() method where you select a Blade template and pass data to it. When you send the mail using Mail::to()->send(), Laravel renders the Blade template with the data and sends the email. The process starts by creating the Mailable instance with data, then selecting the template, rendering it with data, and finally sending the email to the user. This organized flow helps keep email logic clean and reusable.

Practice

1. What is the main purpose of using mail templates in Laravel?

easy

A. To create reusable and consistent email designs

B. To store user passwords securely

C. To manage database migrations

D. To handle HTTP requests routing

Solution

1. Step 1: Understand mail templates role

   Mail templates are used to design emails that can be reused for sending consistent messages.

2. Step 2: Compare with other options

   Options B, C, and D relate to security, database, and routing, which are unrelated to mail templates.

3. Final Answer:

   To create reusable and consistent email designs -> Option A

4. Quick Check:

   Mail templates = reusable email designs [OK]

Hint: Mail templates are for email design reuse [OK]

Common Mistakes:

• Confusing mail templates with database or routing features
• Thinking mail templates handle security
• Assuming mail templates manage HTTP requests

2. Which artisan command creates a new mail class with a markdown template in Laravel?

easy

A. php artisan make:mail -m

B. php artisan make:mail --markdown

C. php artisan mail:create --template

D. php artisan make:mail --template

Solution

1. Step 1: Recall the correct artisan command

   The correct command to create a mail class with a markdown template is php artisan make:mail MailName --markdown.

2. Step 2: Check other options

   Options B, C, and D are incorrect because they use wrong flags or commands that do not exist.

3. Final Answer:

   php artisan make:mail --markdown -> Option B

4. Quick Check:

   Correct artisan command = php artisan make:mail --markdown [OK]

Hint: Use --markdown flag with make:mail command [OK]

Common Mistakes:

• Using shorthand -m which is invalid here
• Trying non-existent commands like mail:create
• Using --template instead of --markdown

3. Given this mail class snippet, what will be the value of $this->name inside the markdown template?

class WelcomeMail extends Mailable {
    public $name;
    public function __construct($name) {
        $this->name = $name;
    }
    public function build() {
        return $this->markdown('emails.welcome')->with(['name' => $this->name]);
    }
}

If you send new WelcomeMail('Alice'), what is $name in the template?

medium

A. 'Alice'

B. null

C. 'name'

D. An error occurs

Solution

1. Step 1: Understand constructor assignment

   The constructor sets $this->name to the passed value 'Alice'.

2. Step 2: Check data passed to template

   The with() method passes ['name' => $this->name], so 'Alice' is passed as 'name'.

3. Final Answer:

   'Alice' -> Option A

4. Quick Check:

   Passed name = 'Alice' [OK]

Hint: Constructor sets property, with() passes it to template [OK]

Common Mistakes:

• Assuming $name is null if not explicitly set in build()
• Confusing property name with string 'name'
• Expecting an error due to missing data

4. Identify the error in this mail class code snippet:

class NotifyUser extends Mailable {
    public function build() {
        return $this->markdown('emails.notify')->with('user', $user);
    }
}

medium

A. with() method requires an array, not two arguments

B. The markdown method should be markdownView()

C. Variable $user is undefined in build() method

D. Class must extend Mail instead of Mailable

Solution

1. Step 1: Check variable usage in build()

   The variable $user is used but not defined or passed to the method.

2. Step 2: Verify method names and parameters

   markdown() is correct; with() accepts key-value pairs or array, so usage is okay if $user existed.

3. Final Answer:

   Variable $user is undefined in build() method -> Option C

4. Quick Check:

   Undefined variable $user causes error [OK]

Hint: Check all variables are defined before use [OK]

Common Mistakes:

• Assuming with() needs only arrays
• Thinking markdown() method name is wrong
• Confusing Mailable with Mail class

5. You want to send a mail with a markdown template that shows a list of products. Which approach correctly passes the products array to the template?

hard

A. Pass products as a constructor argument but do not use with()

B. Set a private property $products but do not pass it to the template

C. Call markdown('emails.products', $products) directly

D. Use with(['products' => $products]) in the build() method

Solution

1. Step 1: Understand data passing to templates

   Data must be passed explicitly using with() or public properties.

2. Step 2: Evaluate each option

   Use with(['products' => $products]) in the build() method correctly uses with() to pass the products array. Pass products as a constructor argument but do not use with() misses passing data to template. Call markdown('emails.products', $products) directly uses wrong markdown method signature. Set a private property $products but do not pass data sets property but does not pass data.

3. Final Answer:

   Use with(['products' => $products]) in the build() method -> Option D

4. Quick Check:

   Pass data with with() method [OK]

Hint: Always pass data with with() or public properties [OK]

Common Mistakes:

• Not passing data to template after setting property
• Using markdown() with wrong parameters
• Assuming constructor argument auto-passes data