When is custom code appropriate? When should contrib solutions be investigated, and when are they overkill? Is there an acceptable way to hack Drupal? Tune in to hear my take on these, and other codebase-related questions, such as:
Drupal 8 uses Twig as its default templating engine. This has generated a lot of excitement but Twig isn't the only thing that has changed in the Drupal 8 Theme System - Twig has been a tool that has allowed us to make many other changes.
In this presentation I will give an overview of how markup should be printed in Drupal 8. I will also walk through some of the changes that have made outputting markup more complex and how to cope with them.
Topics in this session includes:
Now that Drupal 8 has been released it's time to dive in. But with so many innovations in Drupal 8 where to start. This presentation will explore the most valuable innovations in Drupal 8 and offer examples illustrating why these features will become invaluable. We'll be stepping through some examples of how to use new features and what they may mean to developing with Drupal as they mature.
Drupal 8 Innovation we'll be exploring
Debugging is more than fixing broken code. It is about logically thinking through steps and using the appropriate tools to solve problems.
Dive into code-driven details with a backstory, discovering a complete solution which achieves consistency using secure and open-sourced automation. Introduce harmony to your infrastructure and Agile workflow while adding business value and reducing risk.
Presented by the devopsgroup.io Catapult team - you may know our other projects, vagrant-digitalocean and vagrant-hostmanager.
Seth Reeser and Steve Britton