In all the years of designing for Drupal, the one thing I have learned is to always borrow from the best and build it into a base theme. Now, I know you’re saying to yourself — not another base theme. But why not? If I told you your theme could be responsive from the start, have flexible regions that you didn't have to design for, and that you could avoid the JQuery conflicts that plague Drupal 7, would you be interested?

1. All Your Base Are Belong to Us

2. Who is Chaz Chumley?
+ Technical Director - Saforian
+ Author - Lynda.com
+ Govt. to Non-profit to Corporate
+ Over 7 years of Drupal experience
+ HTML5, CSS3, Responsive Design

3. Topics
+ Why another base theme?
+ Creating a Base Theme
+ Integrating Bootstrap
+ Preprocess, Process and Hook Alter
+ Fusion Apply
+ Best Practices
+ Extending base theme
+ Next Steps

4. Why another base theme?
Because I want a best practices approach that encompasses
Twitter Bootstrap, provides for dynamic regions, avoids having to
use Drupal's an-equated use of JQuery and allows for me to
focus more on theming and less on coding...

5. Creating a base theme
.info, folder structures and templates

6. Integrating Bootstrap
why reinvent when we can implement

7. Preprocess, Process and Hook Alter
Drupal output - Avoiding JQuery issues - Providing theming flexibility

8. Fusion Apply
creating dynamic regions

9. Best Practices
rinse, repeat and reuse

10. Extending our Base Theme
settings and overrides

11. Next Steps
practice, refine, experiment

12. Questions?

13. Thank You.