Learn from the Worst: Lessons taken from Drupal Rescues
Learn from the Worst: Lessons taken from Drupal Rescues
Room:
tags
When life gives you bad role models, make rolemodelade.
We learn so much in life from the mistakes of others. Can a best practice really be identified until a worst practice comes along that makes us laugh and cry?
Drupal's flexibility allows endless possibilities to mangle sites. The Drupal "Clean Up and Rescue" job has become all too common. This unforeseen "additional phase" occurs when a client has to hire a new team to fix what a less experienced team built. By fixing all the worst practices in site architecture and coding that destroy the performance, security, maintainability, stability, and functionality of botched Drupal sites, valuable best practices and "what not to dos" emerge.
In this session I'll cover some of the most common ways I've seen Drupal projects botched and what it takes to both fix them in your clean-up work and make sure you and your team never make these mistakes. It will focus on site architecture, site building, and custom module development do-not's and do's.
For example, we'll look at ways to abuse CCK and the theme layer to add unnecessary layers of complexity to your site, how to destroy site performance with javascript, how to make parts of Drupal no longer dynamic, and how to ensure that the upgrade to the next Drupal version will take longer than the original build.
This looks like an awesome
This looks like an awesome session! I think it's of particular interest to those involved in training. These are the kinds of conversations I've had with colleagues at Acquia. Common errors highlight common misconceptions we can teach to avoid. Really looking forward to it, Jody! I hope this gets in :)