Make your Drupal 8 theme easier to maintain with this one weird trick (Twig’s “extends” concept)

Published 27 October 2013

WHAT is Twig’s “extends” concept?

Drupal 8 has a new templating system called Twig that comes from the Symfony world.
I recommend learning about Twig and Drupal 8’s use of it by watching a video of one of the many recent conference presentations on the topic like this one from Drupalcon Portland.
Twig contains within it a different model for overriding templates that can be used in combination with Drupal’s traditional naming-based template overrides.
Read Twig’s own documentation of “extends” here to see how it allows child templates to be much simpler than their parents. Or just keep reading until the ‘HOW’ section of this post.

WHY is it helpful?

Last weekend I was working on a personal Drupal project ( and ran into a common theme development pain point.
I wanted to print some fields separate from the rest of the $content variable for only one node type.
In Drupal 7 (and prior versions) this process involves making a complete copy of the node.tpl.php file (See the documentation of this process here).

Copying every line of node.tpl.php to node--article.tpl.php only to change a few lines makes the theme of a given Drupal site extremely WET (Write Everything Twice).
What if instead of duplicating the entire node template file to a node-type specific name, I could make that node-type specific file contain only the overrides?

That’s what Twig “extends” concept does!

HOW is it used?

Here’s an example node--article.html.twig that moves field_image.

{% extends "themes/sub_bartik/templates/node.html.twig" %}

{# Override the header_fields block to put field_image there because this site
   needs it there. #}
{% block header_fields %}
  {{ content.field_image }}
{% endblock %}

{# Override the content block to hide the field_image subvariable because
   it is being rendered in header_fields. #}
{% block content %}
  {% hide(content.field_image) %}
  {{ content }}
{% endblock %}

Compare that to the amount of code in the parent template being overridden.

To make this kind of overriding possible, the parent template needs to declare which sections can be overridden. In this example I’ve declared two “blocks” (the Drupal community might start calling these pieces “codeblocks” to reduce confusion with Drupal core’s Block module) that designates which pieces of the template can be replaced.

Here’s one addition to node.html.twig in a copy of Bartik’s version:

{# This empty block allows child templates to insert markup into this
   place in the header without re-writing the entire template. #}
{% block header_fields %}
{% endblock %}

Addition two in node.html.twig is:

{# By wrapping the content variables in a block, this template allows child
   templates to insert markup into this spot without re-writing the entire
   template. #}
{% block content %}
  {{ content }}
{% endblock %}

WHERE does this code go?

The complete example code, which is a sub-theme of Bartik, is here in an alternate branch of the github repo of this blog you’re reading.
To test the theme git clone that branch into /themes of a Drupal 8 site and enable it.
Notice that the “parent” node.html.twig is in this sub-theme.
By having a node.html.twig in the sub-theme, Drupal (and Twig) completely ignore the node.html.twig in Bartik and node module.
That kind of overriding, where a template file in the theme completely supersedes Core, is the same as previous versions of Drupal.

WHO should write these “blocks”?

This example illustrates how “extends” can be used by a site owner in a site-specific theme.
I have shown this code around at BADCamp this weekend and the reaction from Carl Wiedemann and other Twig-interested-developers has mainly been something like “Drupal Core shouldn’t put these blocks in templates yet (or maybe ever) because we don’t have enough experience with them.”
I agree.
Drupal has a pattern of proving concepts in the contrib space and then moving those concepts into core.
And even before making a contrib base theme using Twig blocks, someone has to use them on a real site.

WHEN will developers start using “blocks”?

Heavy use of the “extends” concept in Twig will start when developers start building Drupal 8 sites and adding site-specific themes.
Scott Reeves pointed out to me that Jen Lampton’s experimental Twig base theme for Drupal 8 used this concept already. I’m glad I’m not the only Drupal developer who wants to use this functionality.

WHAT is next?

Drupal developers will bikeshed extensively on a rubric for when a block (or is it a codeblock?) should be completely empty in the parent template as I did with my header_fields block and Jen did with her infobar block.
When should the parent template’s block contain something as I did with my content block?
Should these blocks be named with an underscore like header_fields or without like infobar?
Is it too confusing for Drupal to add another concept for overriding a template? I have no “right” answers yet.
I want to use this tool for real first and see what new pain points we get while solving the existing ones.

blog comments powered by Disqus