Presentations We've Given

In the vast majority of Drupal projects most of the site architecture is defined by clicking around in the admin area. This ends up being both extremely powerful and dangerous. To help avoid some of the dangers I propose we start taking site building as seriously as software engineers take their data and object models.

After the site launches and the project is over, there are two paths: developers and project managers can shake client's hands, pat backs, and all head our separate ways. Or we can continue to build a relationship - continue being a part of our client's success. Strong long-term relationships benefit clients by providing trust and security, like a familiar mechanic or the barber we have had since we were a kid. As merchants, we also benefit. Happy clients mean referrals and recurring income.

How can you help your team or your client leverage Drupal’s baked-in strengths and avoid its weaknesses so that your project excels? How can you communicate technical Drupal concepts to non-technical clients while relating client needs to developers in more technical terms?

Your Drupal site launched! Now you need to know the best ways to support your site as it grows. Or maybe you've had your site for awhile and its starting to show some wear and tear. In this session, we will talk about methods and tools for supporting your site over the long-term.

With the power of Panels, you never have to make a .tpl file ever again! Okay, that's not true at all, but what Panels does give you is the ability you to create Drupal aware layouts that can be reused between dozens of other sites. If you create custom Panel pages per-content type, per-node, per-anything (instead of custom .tpl's for each) you will significantly reduce the number of .tpls you have to keep create and keep track of while saving a significant amount of time. Say goodbye to crowded templates folders!

Twig, a new theme engine created by the creators of Symfony, is coming to Drupal 8. All theme functions in core will be replaced by twig template files, meaning that for someone who needs to adjust markup - there will be only one way to do it: override a template file (not a theme function). Twig can flatten & sanitize all at the time of printing, meaning we can remove the whole "process" layer that exists in Drupal 7. Let's discuss!

With the power of Panels, you never have to make a .tpl file ever again! Okay, that's not true at all, but what Panels does give you is the ability you to create Drupal aware layouts that can be reused between dozens of other sites. If you create custom Panel pages per-content type, per-node, per-anything (instead of custom .tpl's for each) you will significantly reduce the number of .tpls you have to keep create and keep track of while saving a significant amount of time. Say goodbye to crowded templates folders!

By the end of the session, you'll be able to create your own themes, sub-themes and rock Drupal's world like you never have before - all while fulfilling the mantra of a themer: "Make it pretty." Now updated with a screenshare from the session!

Building amazing Drupal sites takes planning and skillful project management, not just savvy design and good programing. With Drupal's modular nature and with so much being possible, it is important the team and project stays focused on what is important.