\n\n\n\n

This layout has placeholders (@yield) for the title and the main content. Now, let’s say you’re creating a home page. You can extend this layout like this:
\n<\/p>\n\n

@extends('layout')\n\n@section('title', 'Home Page')\n\n@section('content')\n    
Welcome to the Home Page!<\/h1>\n@endsection\n<\/pre>\n\n\n\n
By using @extends, you link to the layout, and @section allows you to fill in the placeholders with your specific content. This keeps your code DRY (Don’t Repeat Yourself) and super manageable. Blade simplifies your workflow, allowing you to focus more on what matters—building great web applications.<\/p>\n\n
<\/p>\n\n
\n  \n  \n  Blade Components\n<\/h2>\n\n
Blade components are like little building blocks for your UI. Imagine them as Lego pieces—you create a small, reusable part of your interface and can snap it into place wherever you need it. This makes your code cleaner and more maintainable.<\/p>\n\n
You can define a component once and use it throughout your application. Need a button that looks the same across different pages? Create a Blade component for it! Even better, you can pass attributes to these components to make them flexible and adaptable.<\/p>\n\n
Here’s a simple example of a button component:
\n<\/p>\n\n
\n{{ $slot }}<\/button>\n\n\nClick Me<\/x-button>\n<\/pre>\n\n\n\n
You can make your components dynamic by using a component class. This lets you pass in attributes like type or class to customize the button’s behavior or style.
\n<\/p>\n\n
\/\/ In a component class\npublic function render()\n{\n    return view('components.button', [\n        'type' => $this->type,\n        'class' => $this->class,\n    ]);\n}\n\n\/\/ In the Blade component\n\n\n\n\n
\n  \n  \n  Including Subviews\n<\/h2>\n\n
Sometimes, you’ll want to break your templates into smaller pieces for better organization and reusability. Blade makes this easy with the @include directive. Think of it as a way to insert a smaller view (or subview) into a larger one.<\/p>\n\n
<\/p>\n\n
\n  \n  \n  Blade Directives\n<\/h2>\n\n
Blade comes packed with handy directives that make common tasks a breeze. Here are a few:
\n@csrf: CSRF token to your forms, protecting them from cross-site request forgery attacks
\n@method: specifies the HTTP method for forms
\n@auth: checks if a user is authenticated
\n@guest: checks if a user is a guest (not authenticated)
\n<\/p>\n\n
\n    @csrf\n    @method('PUT')\n    Submit<\/button>\n<\/form>\n<\/pre>\n\n\n\n
Need something more customized? You can create your own Blade directives for reusable logic.<\/p>
For instance, let’s say you often need to format dates. You can define a custom directive like this:
\n<\/p>\n\n
Hello, {{ $name }}!<\/h1>\n<\/pre>\n\n\n\n
<\/p>\n\n
\n  \n  \n  Other Features\n<\/h2>\n\n
Blade comes with some really handy features that make your life as a developer smoother. Let’s dive into a few of them.<\/p>\n\n
\n  \n  \n  Managing Asset URls\n<\/h3>\n\n
Need to link your CSS or JavaScript files? The asset() helper function has you covered. It generates the correct URL for your assets, so you don’t have to worry about paths:
\n<\/p>\n\n
@if ($user)\n    
Welcome, {{ $user->name }}!<\/p>\n@else\n    
Please log in.<\/p>\n@endif\n<\/pre>\n\n\n\n
\n  \n  \n  Handling Empty Arrays or Collections\n<\/h3>\n\n
Blade’s @forelse directive is a lifesaver when dealing with empty arrays or collections. It lets you loop through items and also handles the case where there are no items elegantly:
\n<\/p>\n\n
\n\n\n