Mike:

So, the DrupalCon session that I’m giving with Dave is titled “Planning and Executing a Successful Drupal Implementation.” …. Wait… sorry, I just fell asleep. Yeah, it doesn’t sound very exciting does it? Well, hopefully it will be more interesting than the name let’s on.  In an effort to try to get some folks in the door before heading out to happy hour next Monday, we wanted to share a couple of the topics this week in the blog.

Tip: Build the right team, and let them work together

Your team should not work like a baseball team, only covering the immediate area around them.       

 

 

 

 

 

 

 

 

 

Rather, we’ve found that Drupal lends itself to role flexing quite a bit, more like a soccer team. 

 

 

 

 

 

 

 

Because the administration interface makes it easy for non-programmers to accomplish a lot, Drupal inadvertently draws a very thin line between development and “configuration” tasks. Use this to your advantage. Let other team resources (Analysts and even PMs) jump in and save time by doing things like entering a site’s taxonomy, setting up menus, or building out placeholder pages.

Tip: Allow editors to curate and innovate

Many of our clients are well-known publishers who are always looking for ways to keep people coming back to their site. In order to "mix things up" for their users so they don't get tired of seeing the same old home page every time, it's important to give editors the flexibility to curate and innovate within the templated data-driven structure that we've put in place.

An "Editor's Choice" feature that we used on one project gives editors the ability to deploy Featured Quote, Featured Content, Featured Photo, and Featured Author directly from the administrative interface in just a few clicks.

Check back for more previews throughout the week.