When I recently joined Scott Reynen as maintainer of the @font-your-face module (blog post), one of the first tasks on my list was to enable site builders to save their font settings using Features. For those not known with Features; it’s a module that saves database settings (views, content types, variables etc) to code.

Last week Google announced their Font API and Font Directory, which provides a simple, cross-browser method for using any font in the Google Font Directory on your web page. That announcement made me very excited and I decided to spent my evening to make a Google Fonts Drupal module. Building the module didn't took me long (thanks to the powerful Drupal API) so I was able to release a working version of the module the same evening.

The project I'm currently working on involves several authors writing a lot of content. They tag all articles and pages with self-entered terms (free-tagging). Because not every author uses the same case for these terms/tags the layout became quite messy. By using the termcase module you can improve the layout of your tags by automatically transforming all terms to vocabulary-specific case formatting. Read on!

Recently I created a book in Drupal using two Content Types. One type called Book Description (which has a cover, an ID and some other CCK fields) and another type called Book Page. So far so good. Problems arose when I tried to setup Pathauto. For the Book Description I entered book/[field_book_id-raw], which worked great. For the Book Pages I needed something like book/[field_book_id-raw]/title-of-my-page. This is where I got stuck.