Hearst Annex A1

Room capacity: 

Using the Javascript Module Pattern, and more modern JS practices, with Drupal

The JavaScript Module pattern uses immediately-invoked functional expressions (IIFE) that return objects, that include closures. This provides a way of wrapping various public and private methods and variables in a "module". This prevents them from "leaking" into the global name scope and cluttering it up or worse, colliding with other code. With this pattern only a public "API" is returned, while maintaining privacy on everything else. Additionally, I'll discuss how to split up and organize your js files for maintainability and reuse.

Drupal 8 Theming - No More <div>-itis

Drupal 8 has many new exciting features, but none are as radical or as needed as the changes made to the theme system*!

For 10 years Drupal's front end was design and built by developers that tried their very best to figure out what the front end needed; the lack of dedicated front-enders in core; resulted in front end architecture that was "less than ideal" for the challenges that the front end has faced for the last 5 years.

Drupal 8 and twig changed it all!

Drush in the Composer Era

Composer is now required to install Drush, and more and more Drupal sites are using Composer to manage their modules, themes and Drush extensions.  In this session, we'll talk about how these developments are affecting the way Drush works, and how you can make sense out of managing your Drush extensions and configuration, whether you are using Composer, or still running your site without it.  We will discuss how Drush fits in to your development workflow, when you may have multiple Drupal sites requiring different versions of Drush, and will also review the relationship between Drush and yo

Subscribe to RSS - Hearst Annex A1