Eric Volkernick
Full-stack Drupal Developer at DevCollaborative
I'm a full-stack Drupal engineer and I've been working with Drupal for more than a dozen years (as my job, "full-time", since around when Drupal 7 launched). Back-end development is my area of expertise, but I also enjoy working with cross-disciplinary teams to solve problems.
Outside of Drupal, I have recently (the past year or two) become interested in living a more sustainable, healthier lifestyle. For me, this means following a whole-food plant-based diet, lifting weights, and running.
This presentation is designed to teach you about the Drupal Recipe initiative, but more specifically: how to use one or more recipes to add features to one or more Drupal sites.
We'll answer the following questions:
- What is a recipe?
- Why use a recipe / what problem can I solve with a recipe?
- How do I create a recipe?
- How do I apply (use) a recipe?
- What happens after I apply a recipe and how do recipes work together?
- What are the current limitations of recipes? How can I help the initiative?
There are several methods available to preprocess content. It can be challenging to choose the correct one, but if we have an understanding of how to use the most common methods – and understand their advantages and disadvantages – we can make more informed choices and produce sustainable websites that are easy to work with.
This session will provide a technical overview for beginner to intermediate developers. Specifically, we’ll look at how to use preprocess hooks, twig logic, field formatters, display fields, and custom twig functions and filters. While looking at each technique, we’ll discuss its pros and cons while evaluating its maintainability, chance for collateral damage, and chance for misuse.