Yeah, I would love to put Drupal through its paces, but my experiences with it so far were pretty bad.
Here’s a little story about Drupal:
I was hired to do a DRUPAL project (yes, knowing that I’d have to first learn the entire CMS). So the idea was this: I built out the entire backend (there was a fair amount of custom 3rd party data that had to be added). So I jumped into the famed Drupal CCK (content constructor kit), and after much swearing and the help from some Perl scripts, I got the CSV dumps loaded up into Drupal with all the required taxonomies.
The plan was to hand the project over to the other developer (the one who had insisted that we use Drupal in the first place), and he was going to integrate all the custom templates (HTML/CSS) that he had designed. He was a Drupal expert, so he had designed the templates in a Drupal friendly way... but the guy kinda disappeared. Flaked out. Poof.
So at that point we had an unskinned Drupal site, a handful of HTML/CSS files that demonstrated the desired layout, and only $5k remaining in the budget for the integration. I started soliciting bids from eLance and from friends for any Drupal dudes to finish the project. NOT ONE OF THEM WOULD EVEN LOOK AT THE INTEGRATION FOR LESS THAN $10k. With the gun to my head, I said "F this", and I ported the whole thing over to MODx Revo and integrated the templates myself, and even with the time I spent porting the site, it was still ended up being a well-paying gig for that remaining $5k.
The lesson there was that that particular project would have been much cheaper to do in MODx. That was a pretty big FU to Drupal in my book: its template integrations and the way it handles customized data were truly painful in comparison to MODx.
And here it is:
http://greenjobscalifornia.org/