April 17, 2012
About a year ago, Carl and I were doing a training in Washington DC. When we got to teaching Drupal themes to a bunch of qualified people with HTML, CSS and some PHP knowledge, we listened to our own explanations, looked at each other, and both thought "it shouldn't have to be this complicated!" Drupal 6 theme development was different than Drupal 5, and Drupal themes in general were still a beast unlike anything else, but with a little explanation, people got it, and people learned to appreciate Drupal 6 theme development rather quickly.
February 01, 2012
I recently gave a talk at SANDCamp on how to set up a WYSIWYG editor, and after the session Graham asked me why my preference was for the TinyMCE editor over the CKeditor, or any other. I figured I'd write up my preferences here, in case anyone was wondering the same thing.
November 10, 2011
Chapter Three will be heading down south for some warmer weather (we hope) and a little Texas charm. We'll be attending DrupalCamp Austin, November 19th and 20th, 2011.
September 28, 2011
Two of the top companies in the Drupal ecosystem, Lullabot and Chapter Three, are joining forces to deliver some of the highest caliber Drupal training offered today.
September 07, 2011
Drupal camps are different from DrupalCons in several very important ways. I helped organize DrupalCon San Francisco in 2010, and I've been an organizer for BADcamp since 2007. BADcamp has been growing in size each year, but I still want to voice what I think the key differences are between camps and cons.
August 02, 2011
Three years after our first round of formal usability testing on Drupal 6, the UX team returned to the University of Minnesota in May 2011 to uncover usability issues and patterns for Drupal 7. After making broad changes in D7, it was critical for us to validate if we are inching forward in our goal. With this aim in mind, we tested eight participants and asked them to perform some tasks. All the participants were site builders with no experience with Drupal.
May 15, 2011
There are a lot of great things about being a Drupal Trainer. My favorite is getting to see -- first hand -- how the code we write affects the community. I noticed that with the release of Drupal 7 - the demand for training on theme development increased dramatically. It took me a while to figure out why - exactly - but after a night of heated Debate in IRC with chx, mikey_p, HedgeMage, heyrocker, and yoroy (among others) we may have arrived at a conclusion.
May 11, 2011
Three years after our first round of formal usability testing on Drupal 6, the UX team returned to the University of Minnesota in May 2011 to uncover usability issues and patterns for Drupal 7. We tested eight participants who had no experience with Drupal and asked them to perform some tasks. The intent of the session is to share findings from the study, and discuss how these findings might be helpful for a more usable Drupal 8. Attend this panel presentation if you are interested in understanding the user experience and the usability road map for Drupal 8.
May 11, 2011
The idea for my keynote session Taking Drupal back came to me during several heated discussions with fellow Drupalvangelists about the current state of our favorite CMS, and where we're headed - both as a platform, and as a community. Drupal is growing, and growing fast. How are we going to manage these growing pains in a way that keeps the technology moving forward, but doesn't hurt the community that made us what we are today? The answer: by taking Drupal back!
May 10, 2011
Three years after our first round of formal usability testing on Drupal 6, the UX team returned to the University of Minnesota to put Drupal 7 through another round of tests to benchmark our progress and to identify new areas for improvement. Be the first in the Drupal community to learn of the preliminary results of this new round of testing and join us for a brief panel presentation of our findings. (Co-Presented with Angie Byron, Bojhan Sommers, Brad Bowman, Chad Fennell, Dharmesh Mistry, David Rothstein.)