A large part of Drupal's appeal lies in its flexibility. The fact that a developer can alter, extend, and enhance almost any aspect of Drupal without having to hack core. Knowing what systems are available for doing so, and how to make use of them is critical for anyone developing with Drupal.

Drawing from my experience helping to document and explain these new patterns in various formats I hope to answer these questions:

- What are hooks, plugins, events, and services?
- What problems do these patterns seek to solve?
- How do I decide which method to use and when?
- Looking ahead to the future, how do these patterns affect the code I write today?

If you're currently writing modules for Drupal 8, porting modules from Drupal 7, or think that you might have to sometime in the future, or even if you're just curious how the module ecosystem fits together behind the scenes this session contains critical information for you. After attending this session you should have all the background information you need to make informed decisions about how your custom code can, and should, talk to Drupal in order to uphold best practices and write modules that are easy to maintain and play well with others.


Comments are closed.

Thanks for sharing your insights regarding how things have changed in Drupal 8. Being familiar with Drupal 7, it was interesting to hear and see how things have changed for D8 and where things might be headed in the future.

I was impressed at the level of detail Joe was able to dig into in such a short time (although it did go over and I had to leave before he was done to get to the next session I wanted to go to). I am very familiar with Drupal 7 but hadn't done anything with 8 yet. It was great to get "caught up" on the changes and feel like when I do use Drupal 8 now I won't be completely lost.