Andy Chase

I worked through the day’s beastly heat (upper 80’s and humid, not normal weather for early May in New England) and am pleased to announce the launch of jeffmenzies.com, built in Drupal 6 with a custom subtheme based on Interactive Media.

While some work had already been done on the site before this weekend, I would say that about 80% of it was done in the last 36 hours. This is partly due to the power of Drupal’s theme layer, the Drush module, and of course Views and CCK… but I realized that it was also due to the fact that the parameters were refreshingly simple. Now that we’ve gotten used to the ability to slice and dice content in nearly any way imaginable, we have a tendency to overdo it… we try to cram too much information on home pages, and we overstructure content that lives underneath, creating elaborate tagging mechanisms and cross-linked views and meticulously formatted archives, timestamps, bylines, and profiles… often just because we can. I know I haven’t forgotten what it was like to get a static HTML site like this 90% built, only to decide that a font color or some aspect of the layout needed changing; lots of find-and-replace, save, upload via FTP, reload, lather, rinse, repeat. It was miserable, and that was before you even got into working on actual content, which led to its own open-edit-save-upload-reload cycle.

So yes, it’s very tempting to go crazy with multiple meticulous views of your data, because tools like Drupal make it so damn easy. By contrast, this site was a very enjoyable exercise in minimalism, and a useful reminder that in many cases, less can be more.

Last night I decided to get more familiar with CCK and Views integration by way of rebuilding the Chords module, which is functional in its current state but doesn’t do much.

So, I’ve begun work on Chords 2 for Drupal 6. Major architectural changes:

• The original module has been split into two:
  • The Chords API module provides basic functionality around calculating and rendering chords (and keeps the original module namespace)
  • The Chords UI module contains the simple chord builder tool from the original module.
  • New modules are on the way:
  • A Chords Field module will provide a new CCK Chord field and some useful formatters
  • A Chords Views module may provide Views 2 integration, if Chords Field doesn’t cover it.

I know better than to state a timetable, as these things have a way of languishing when other shiny objects catch my interest. However, if you’re interested in playing with the latest and greatest code, check out the CVS HEAD.