[D856C]

It really depends on what you want to accomplish. Most people are looking at the CMS from the most superficial basis: What kind of cool layout gimmickry can it do.

A CMS isn't an online version of Frontpage. And the quality of a CMS is not about how easy it is for a developer to slap up this week's design fad.

Here's a novel thought: What kind of content -- FYI the "C" in CMS -- will there be? Dare I ask what the client objectives are? ...Or [cough] what the user profile or site purpose is? A news site might need the information architecture structure and publishing oversight Drupal offers -- even when the developer has more work to do. Another kind of client might be better served by Wordpress.

Will it be used for brand journalism or plogging? Does anyone currently looking for the most primitive kind of online pasteup even know what a plog or brand journalism is? (no the "p" is not a typo) Because, contrary to popular opinion, that's a content management application.

Sorry to say, being developer friendly is somewhat less important than suitability to (end user) task. Getting 'a' site up is only part of the task -- getting the right kind of site up is the critical part.

In other words, you can't look at the CMS to fulfill the same purpose as an online version of Frontpage. Despite being used that way, they were never designed for that.