Rendering Pages with Twig

Twig is an awesome option for rendering HTML. It got some nice features like blocks and inheritance. That’s why we use and love Twig.

Which Twig-Template is used?

In Creating a Page Template we learned how to define a template.

<?xml version="1.0" ?>
<template xmlns=""



In the page template the view could be set. Internally Sulu appends the format of the request to find the correct template to render the response. As an example sulu uses for a html request the template templates/pages/default.html.twig or templates/pages/default.xml.twig for a xml request. With this feature you are able to define different output format for a single page.

Rendering the Content

If you don’t use your custom controller and modify the output the Sulu Controller renders, Sulu passes some default variables to Twig.


In the content everything you defined in your template is saved. If you got a title you could easily obtain it from the content-var.

<h1>{{ content.title }}</h1>


In the extension var Sulu writes content from Sulu extensions. Typically stuff that is defined in separate tabs in the Sulu content section. At the moment there is the SEO and the excerpt extension, that could be used. This extensions are available on every page no matter which template you chose.

Here is an example how it could look like in the backend. Notice the “Excerpt & Categories” tab next to the SEO tab.


You could include the SEO meta tags like this:

{% include "@SuluWebsite/Extension/seo.html.twig" with {
    "seo": extension.seo|default([]),
    "content": content|default([]),
    "localizations": localizations|default([]),
    "shadowBaseLocale": shadowBaseLocale|default(),
    "defaultLocale": app.request.locale
} %}

The excerpt data is available from:

{{ extension.excerpt.title }}
{{ extension.excerpt.description }}
{{ extension.excerpt.more }}
{{ extension.excerpt.icon[0].thumbnails['50x50'] }}
{{ extension.excerpt.images[0].thumbnails['300x300'] }}


In the view variable Sulu writes the view data of the defined properties in your template. As an example the media_selection stores the displayOption there.

{{ }}

Other Variables

  • request.webspaceKey: Contains the key for the current webspace

  • request.webspaceName: Contains the name for the current webspace

  • request.portalKey: Contains the key for the current portal

  • request.portalName: Contains the name for the current portal

  • request.locale: Contains the locale for the current request

  • request.portalUrl: Contains the root URL to the current portal

  • request.resourceLocatorPrefix: Contains the prefix for the current portal

  • request.resourceLocator: Contains the resourceLocator to the current page

  • uuid: Contains the uuid of the current page

  • template: Contains the template key of the current page

  • creator: Contains the id of the creator of the current page

  • changer: Contains the id of the changer of the current page

  • created: Contains the timestamp of the creation of the current page

  • changed: Contains the timestamp of the latest change of the current page

  • published: Contains the timestamp of the publishing of the current page

  • urls: Contains urls of all locales (deprecated)

  • localizations: Contains all localizations including the URLs for the current page

  • segments: Contains all segments including the URLs to change the segment and redirect back to the page


You can also use {{ dump() }} in the template to see all available variables if you are in dev mode.


If there are images defined in your template you could render them by using this code:

{% for image in content.images %}
    <img src="{{ image.thumbnails['200x100'] }}" alt="{{ image.title }}"/>
    <p>{{ image.title }}</p>
{% endfor %}

Image formats need to be defined in the image_formats.xml in your config.


You can organize and build your website assets the way you are most familiar with. If you want to use Symfony’s Webpack Encore, have a look at the Using Webpack Encore for your website assets.