If only someone would just invent a time machine, what I would give to be able to go back in time and warn past me about Drupal …
After 8+ years working with Drupal in various capacities I’ve encountered more than my fair share of hurdles and stumbling blocks along the way. A lot of them I’m sure could have been avoided but there’s the classic problem in which you don’t know what you don’t know. Then spend many many hours learning what you don’t know just to discover down the road that you took the wrong path and need to start over again, that you could have saved yourself hours of time if only someone had pointed you in the right direction at the start.
Over the years I’ve worked on sites ranging in size from local food co-op to Martha Stewart, and with teams of 20+ developers all the way down to just lonely me. I’ve been both completely ignorant of, and later very involved with the Drupal community. I’ve taught hundreds of hours of workshops on Drupal and have watched others stumble over hard concepts and as a result of all these experiences I’ve got a pretty good perspective on what it is that makes Drupal hard, and how to ease those hurdles. Or if nothing else I’ve at least got a lot to say.
Collaborative notes link: http://bit.ly/114BmQ4
In this session I’ll cover
- Some basic Drupal terminology, just so we’re all on the same page
- How, and where, to find good Drupal learning resources
- Using the Google™
- Weeding out modules from the crowd
- How and more importantly WHY you should get involved with the Drupal community
- Various best practices for developing Drupal sites by yourself and with a team