One of the interesting new opportunities - and thus pitfalls until you understand them - is Drupal 6's built in block caching. As a developer, I'm generally used to creating hook_block by just specifying the 'info' data in hook_block, and letting the other options be set by the admin via the blocks page. However, you can't set the caching level there, and more troublesome, you can't change the caching level of a block once it's been put into your site.

Have a great idea that can lower technical barriers in Drupal? Want to help provide powerful tools for digital publication? Have a way to encourage people to improve their communities by supporting the free exchange of information and ideas?

Want a GRANT to make it happen?

Digital publishing can help people improve their communities by giving them tools to connect people and ideas.

For the second year now we've won multiple Horizon Interactive Awards for websites we've developed.

Among the winning sites are Popular Science (Gold in the Magazine & News category), RedBlueAmerica (Silver in the Blog category and Bronze in the Magazine & News category), and Spectrum Magazine (Bronze in the Public Service category).

Of course, we developed all of these sites using Drupal, which itself just won repeat honors in the CNET Webware 100 Awards for best publishing platform.

One of the challenges in providing the architecture for a Drupal 6 site is leveraging existing contributed modules. A client might say they want to be able to forward content to a friend. Oh, well there are a couple contrib modules you can use but how do you find out if a module will be updated to Drupal 6 and where it might be in that process if at all?

Well, it's that time of year again where Google doles out the readies to the young and eager of the programming world.

Thanks Google and thanks to all those involved in setting it up.

There's plenty been said about GSoC in blogs already so I'm not going to repeat. I just wanted to add a personal novelty factor and sense of achievement.