006

We are all familiar with the story—massive project, naive client, overly ambitious developer.  Too often, it turns into a tragedy, with the client investing wasted dollars, energy, and time into a stalled or failed project.  As development shops, we do our best to avoid inheriting these scenarios, because the risks and responsibility are real.  Client fatigue, budgetary limitations, unreasonable expectations, and bad code would seem to doom an engagement before it even begins.  But is it possible to transform a failing project and make it work for both the client and the vendor?

In Drupal 7, for all but the most simple sites it seemed like no one used the core Block system. If you wanted to manage any kind of complicated layout you probably used Panels or the Context module.

Luckily for Drupal 8 the Block system has been vastly improved by a few key features:

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.

Learn how Stony Brook University leverages the paragraphs module, Drupal templates and a Pattern Lab based styleguide to help develop a robost system that allows content owners greater control over page layout and content presentation while also reducing the amount of unstructured content and systematically adhearing to University branding and accessibility guidelines.

This talk will mainly feature Drupal 7 examples, but the principles should be applicable to D8.

Front End: SASS, jQuery, Bootstrap, GULP, Pattern Lab

Drupal 8 revolutionizes the theming experience with the switch to Twig as the default templating engine, but the changes don't stop there. Many significant improvements have been made to make theming easier, more future proof, and give themers the flexibility and control they've never had before.

Some of what we'll cover:

• CSS and inclusion of SMACSS categorization
• Libraries
• Twig basics
• API changes
• Classy and Stable, the new base themes in Drupal core