Creating a Twig Template ======================== 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. Build the HTML template ----------------------- We recommend to build the HTML templates in a first draft with plain HTML and some dummy texts. That means absolutely no placeholders for template engines. This ensures that your HTML is working across all browsers (at least if you test it correctly), and it is easier to test, since there are guaranteed no errors caused by the some wrong template variables. Please make also sure that your HTML is valid, and use HTML tags in a semantic way, so that your website will achieve the best results in terms of search engine optimization. Which Twig-Template is used? ---------------------------- In :doc:`adding-a-template` we learned how to define a template. .. code-block:: xml :linenos: In the page template the view could be set. 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. Content ^^^^^^^ 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. .. code-block:: html

{{ content.title }}

Extension ^^^^^^^^^ 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. .. figure:: ../../img/admin-extension-seo.png :align: center You could include the SEO meta tags like this: .. code-block:: html {{ sulu_seo(extension, content) }} The excerpt is available in: .. code-block:: html {{ extension.excerpt }} Navigation ---------- There is a Twig function that obtains the menu. You need to pass the key of the navigation context you defined in your webspace (:doc:`setup-a-webspace`). While editing a page the navigation context could be defined in *settings > Navigation context*. Here we'll render the main navigation. .. code-block:: html :linenos: Images ^^^^^^ If there are images defined in your template you could render them by using this code: .. code-block:: html :linenos: {% for image in content.images %}
{{ image.name }}

{{ image.title }}

{% endfor %} Image formats need to be defined in the `image_formats.xml`_ in your config. More examples ------------- You could find more examples of how content could be accessed in our `example file`_. Default Template ---------------- Just have a look at our `default theme`_, that ships with our standard installation as long with our `default page templates`_ over at github. .. _default theme: https://github.com/sulu-io/sulu-standard/tree/master/src/Client/Bundle/WebsiteBundle/Resources/themes/default .. _default page templates: https://github.com/sulu-io/sulu-standard/tree/master/app/Resources/pages .. _example file: https://github.com/sulu-io/sulu-standard/blob/master/src/Client/Bundle/WebsiteBundle/Resources/themes/default/templates/example.html.twig .. _image_formats.xml: https://github.com/sulu-io/sulu-standard/blob/master/src/Client/Bundle/WebsiteBundle/Resources/themes/default/config/image-formats.xml