Watching a really good webinar from the Los Angeles Drupal User Group on how to use Git for version control (Drupal.org is moving from CVS to Git with Drupal 7).
If you're familiar with CVS or Subversion this is a great introduction that provides some comparisons between methodologies and commands. If you're new to version systems then Git is a great place to start.
I'll be giving a presentation in a couple days at Washtenaw Community College. I've been invited by Brad Czerniak to speak as part of Refresh Detroit's monthly meeting on using Drupal to solve real-world problems. The presentation is entitled Applied Drupal: Leveraging The Nature of Open Source to Deliver Great Websites for Clients.
Presenters are Brad Czerniak, Alex Fisher and Steve Colson.
Have you ever wanted to change the way Drupal displays pages for certain content types? Drupal has built-in functionality that allows you to add additional template files to your Drupal themes. However, as of Drupal 6, it will not allow you to override page.tpl.php based on content type. You change this by adding a small amount of code to your Theme's template.php file:
There are two types of people who design websites. The first, who I'll refer to as Type 1, is someone who's less experienced or not fully focused on web design and lets technical issues or the constraints of an off-the-shelf template dictate the end web site product. The second, called Type 2, is someone who figures out what the site must do to be relevant and meet business goals and then designs the site so it does exactly that.
Creating a Drupal based website with a blog on a page other than the front page can be frustrating and a bit confusing. By default, when Drupal is installed it has two content types, Story and Page, and lists on the front page any stories or pages you create and mark as Published and "Promoted to front page". However, many sites want their front page to be a static or semi-static Page and a blog in a different section of the site.
When I originally set out to create a form with dynamic select boxes I thought it'd be easy enough to just create some fields, throw some values into the fields, and then repeatedly modify the options on one field based on the option selected in another field. While Drupal is built around forms (and provides many ways for creating and changing them) the best way for handling dynamic select boxes populated from an external database wasn't obvious.