would that I could turn away anoying clients - I’d probably never build another site!
In the past I hd always build CMSs bespoke, so I really didn’t know too much about EE or Drupal.
As it turns out, the client was correct - EE would not have been able to handle this project - Drupal did it with ease.
I amd not saying that either architecture is better than the other - just that they both have their strengths and weaknesses.
I disagree that a project can be done in Drupal but not EE. Forget about Drupal and EE, there is really just PHP and MySql. The difference between the two systems is ultimately the finished code which is available. If you can do something in Drupal but not EE then I am assuming you are saying there was a 3rd party module available for Drupal which has no equivalent in EE yet.
I do agree they both have strengths and weaknesses though I am not sure what they are. Last time I did anything with Drupal I swore I would rather stab out my eyeballs with a fork. The templating system was just ridiculous and I am not sure it is any better now. Joomla is the same way. With as horrible as a templating system these things have I wonder why they even have a templating system at all. Why not just use raw PHP?
Since then… I found EE and template love.
Yes, Drupal is much easier for making the control panel look like the rest of the site. In fact, when you get a template, that template styles the front end and the back end. I always though this was a problem though. The design for the front end typically has totally different goals than the control panel. Because of this, they need totally different designs. This is the way EE, Joomla and Wordpress does things. Civicspace fixed this problem at one time and I am not sure if Drupal has moved farther in that direction.
Coding in the EE templates can be a pain for developers new to EE (if you can’t find EE tags to solve your problems.) The parse order gets in the way sometimes, but this is typically a problem only for new developers. If you know the system then you can get around these issues.
I believe Drupal seems closer to that “bespoke” CMS that you feel comfortable in. I think that is because the templating system for Drupal is not as abstracted. Drupal even has multiple templating systems that can be used (including Smarty.) That means the template will be a PHP developers joy and a designers nightmare. Sounds like you are on the PHP developer side of the fence. 😉
I have worked with other PHP developers who have made the same arguments about the “problems” of EE and how Drupal gets around those problems better. In each case the real problem was that the developer I was working with just didn’t know EE very well.