Skip to content

Recipes

Jump to bottom
Muhammet Şafak edited this page Jun 11, 2026 · 1 revision

Recipes

Practical patterns for everyday use. All examples assume an adapter has been registered with View::via().

Header / content / footer layout

The simplest layout: render three views in one call. They share the same data.

echo view(['layout/header', 'pages/home', 'layout/footer'], [
    'title' => 'Home',
    'user'  => $currentUser,
]);

views/layout/header.php:

<!doctype html>
<html lang="en">
<head><title><?= htmlspecialchars($title) ?></title></head>
<body>

views/layout/footer.php:

</body>
</html>

A wrapping layout (content injected into a shell)

When the layout needs the page's HTML inside it (not just before/after), render the inner view first and pass its output to the layout.

views/layout/main.php:

<!doctype html>
<title><?= htmlspecialchars($title) ?></title>
<main><?= $content ?></main>
$content = view('pages/home', ['user' => $currentUser]);

echo view('layout/main', [
    'title'   => 'Home',
    'content' => $content,   // already-rendered, trusted HTML
]);

The two view() calls are independent — the adapter resets between them, so the inner data never leaks into the layout.

Partials and loops (Pure PHP)

Render a partial per item and concatenate:

$rows = '';
foreach ($products as $product) {
    $rows .= view('partials/product-row', ['product' => $product]);
}

echo view('layout/main', ['title' => 'Catalogue', 'content' => $rows]);

Escaping untrusted data (Pure PHP)

The Pure PHP adapter does not auto-escape. Escape in the template, or define a short helper:

function e(string $value): string
{
    return htmlspecialchars($value, ENT_QUOTES, 'UTF-8');
}
<h1><?= e($title) ?></h1>

Blade ({{ }}) and Twig auto-escape by default.

Returning a view from a controller

view() returns a string, so feed it straight into your response:

final class HomeController
{
    public function index(): string
    {
        return view('pages/home', ['title' => 'Home']);
    }
}

With a PSR-7 response (e.g. initphp/http):

$html = view('pages/home', ['title' => 'Home']);
$response->getBody()->write($html);

Choosing the engine by environment

Register one adapter at bootstrap based on configuration; the rest of the app uses view() unchanged.

use InitPHP\Views\Facade\View;
use InitPHP\Views\Adapters\PurePHPAdapter;
use InitPHP\Views\Adapters\TwigAdapter;

View::via($useTwig
    ? new TwigAdapter(__DIR__ . '/views', __DIR__ . '/cache')
    : new PurePHPAdapter(__DIR__ . '/views'));

Global data on every Blade view

With the Blade adapter, share() exposes data to all views without passing it each time:

$blade = new BladeAdapter(__DIR__ . '/views', __DIR__ . '/cache');
$blade->share('appName', 'InitPHP');
$blade->share('year', date('Y'));
View::via($blade);
<footer>{{ $appName }} © {{ $year }}</footer>

Global data with Twig

$twig = new TwigAdapter(__DIR__ . '/views', __DIR__ . '/cache');
$twig->getEnvironment()->addGlobal('appName', 'InitPHP');
View::via($twig);
<footer>{{ appName }}</footer>

Building an email body

Rendering is just string-building — render a template to a variable and hand it to your mailer (e.g. initphp/mailer):

$body = view('emails/welcome', [
    'name' => $user->name,
    'link' => $activationUrl,
]);

$mailer->setMessage($body)->send();

See also

initphp/views · MIT License · part of the InitPHP family

Source · Issues · Discussions · Packagist · Contributing · Security Policy

Home

Getting Started

Adapters

Reference

Guides

Other

Clone this wiki locally