A while back I wrote about my first weekend with Drupal, which after exploring other content management systems and a little bit of soul searching, I decided to use for the International Transplant Nurses Society site.

While I had already built the site according to a Dreamweaver/Contribute model with custom PHP/MySQL functionality for certain features, a new set of requirements entered the picture that called for features that either I would have to learn to develop, consuming much time and energy, or that I would have to hire another developer to produce.

But what if?ǨI thought?Ǩthere?ǨѢs a CMS out there that could support my strict adherence to web standards while offering the flexibility and scalability I required. After looking into Joomla and Mambo, Drupal seemed the most appropriate for my project for its community focus.

Fast forward two months?Ǩ

After probably a bout of being over cautious, I relaunched the site, now powered by Drupal. It?ǨѢs pretty much the same site as before. In fact, I haven?ǨѢt told my client yet that about the switch?Ǩkind of a test to see if they notice. So far, nope.

The toughest part about going to the CMS is developing within web forms instead of Dreamweaver. It?ǨѢs not because I use Dreamweaver as a crutch (I?ǨѢve been hand-coding since 1996), but it?ǨѢs hard to give up the site management tools and CSS support.

I realize it?ǨѢs a trade off, and I?ǨѢm looking forward to tapping into Drupal?ǨѢs many modules that will help me deliver a much more integrated and professional site than previously planned.

But at the moment, it still feels a bit awkward. Though overall, I?ǨѢm very happy with Drupal. And I imagine as I go forward I?ǨѢll get more used to it.