I don't know why you are getting downvoted, my sentiments exactly. IF you want power/functionality, then you probably need to customize, so why not just build it via Cake or some other MVC framework. IF you want simple and basic, choose wordpress which does a lot of the CMS tasks Drupal does, but makes things like ADDING AN IMAGE to a page simple.
Edit *"does a lot of the CMS tasks" rather than "90%"
Until the "choose wordpress which does 90% of what Drupal does" I was in agreeance.
But unfortunately you're going to have to take this downvote for being completely misguided. I'd have been in agreeance if you had of said "choose wordpress which provides the CMS functionality". But saying Wordpress can do 90% of what Drupal can is completely incorrect. Yes Wordpress as a basic CMS (changing content from an end user perspective and adding a widget here and there) is great, but for much better extensibility you need Drupal, it's already providing the framework and CMS you're talking about trying to custom code/workout multiple systems to provide a solution for you
In the end its at the developers discretion for what they choose to develop within, however after the initial headache of learning how everything works within drupal - it does provide the solution both of you have been discussing in a much easier packaged and quick system. It's not always the answer, but it's rarely not a good answer.
edit: Probably should link to prove my point on the 90% being well off the mark - check drupals core API here
IMO, the point of a CMS is for the End-user to focus on content, and in my experience, unless they are forced to do so (or they are technical), they won't learn the complex usability that Drupal has going on. Thus it FAILS at it's initial task.
Also, I don't get why you'd learn the quirks for a specific system, than to just learn a framework which you can apply in general anywhere. Wordpress for basic sites --> Cake/MVC frameworks for everything else.
I can sorta see what you mean when comparing Drupal to Wordpress, but as I see things, if you develop your Drupal site well, create specific roles for those who will be maintaining the site, and keep the end-user in mind as you develop (creating meaningful vocabularies, fields, etc), then I don't really see there being issues due to an overly complex usability and maintainability. And I've developed for some extraordinarily untechnical people. But I don't mean to take anything away, I think Wordpress is brilliant. Cake though, I never liked, but I know I'm in the minority on that one. :)
2
u/fewpeople Jan 05 '11 edited Jan 05 '11
I don't know why you are getting downvoted, my sentiments exactly. IF you want power/functionality, then you probably need to customize, so why not just build it via Cake or some other MVC framework. IF you want simple and basic, choose wordpress which does a lot of the CMS tasks Drupal does, but makes things like ADDING AN IMAGE to a page simple.
Edit *"does a lot of the CMS tasks" rather than "90%"