StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><em>For Laravel 5.4, <a href="https://laravel.com/docs/5.4/blade#components-and-slots" rel="nofollow noreferrer">Components & Slots</a> may be useful for you. The following solution is for Laravel 4.x, and likely <= 5.3 as well.</em></p> <hr> <p>In my opinion, this is a silly use case for the <code>@include</code> syntax. The amount of HTML retyping you're saving is negligible, especially since the only potentially-complicated part of it is the <code>inner</code> content. Keep in mind, the more parsing that needs to be done, the more overhead your application has, also.</p> <p>Also, I don't know the inner workings of the <code>@yield</code> & <code>@section</code> features, so I can't say how "proper" it is to work your includes this way. Includes typically utilize a key => value pair passed as a parameter in the include call:</p> <pre><code>@include('panel', ['heading' => 'Welcome', 'inner' => '<p>Some stuff here.</p>']) </code></pre> <p>Not the most ideal place to pack a bunch of HTML, but that's the "designed" way (as far as I know, at least).</p> <p><strong>That said...</strong></p> <p>Use the <code>@section ... @overwrite</code> syntax mentioned in the <a href="https://laravel.com/docs/4.2/templates#other-blade-control-structures" rel="nofollow noreferrer">"Other Control Structures"</a> part of the template docs page.</p> <pre><code>@extends('default') @section('content') {{-- First Panel --}} @section('heading') Welcome, {{ $user->name }} @overwrite @section('inner') <p>Welcome to the site.</p> @overwrite @include('panel') {{-- Second Panel --}} @section('heading') Your Friends @overwrite @section('inner') <ul> @foreach($user->friends as $friend) <li>{{ $friend->name }}</li> @endforeach </ul> @overwrite @include('panel') @stop </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload