4 ms·
I think the Drupal community needs to get a really solid grip on what Drupal is (CMS) and how it compares to alternatives, and make sure they aren't leading peo
by lotyrin 14y ago
I think the Drupal community needs to get a really solid grip on what Drupal is (CMS) and how it compares to alternatives, and make sure they aren't leading people astray. There's this attitude that Drupal is some end-all solution to any web problem, when simply put, it's just a collection of many solutions to even greater (and growing) number of problems surrounding content.
If you want to capitalize on Drupal, your project needs to be well inside that problem set and you should have a tier of users that can and will learn arcane rituals and minutiae such as which of the five modules for X doesn't suck -- people who are going to be more productive doing so than if you were to have them writing code. These shouldn't be developers, these should be that class of person that is content to spend months complicating together a single spreadsheet, it's that same kind of work.
I've been doing Drupal full time for several years and I often say that if you're working on a Drupal project and you're in a code editor, you're probably doing something wrong. Most of the time, either there's a module for whatever you're doing, or you shouldn't have used Drupal.
Drupal agencies seem to sell Drupal as if it were bespoke development: hourly rates, design from scratch and lofty goals -- until it gets handed to a site builder "developer" who weeps because module X doesn't have support for module Y yet and fixing that properly exceeds the budget and their own skill set.
The Drupal service industry has to realize that Drupal and contrib is an IKEA and they should seek to serve clients as interior decorators do, not as carpenters - although I suspect it won't be quite as lucrative for them under that model, as well as many egos in the way.
Actual developers do exist in the ecosystem, but their time is best spent increasing the breadth and quality of the catalog of solutions for site builders, not cleaning up messes and creating endless one-off cludges on an over-promised project.
I've not yet had my conviction broken that there is a market for CMS, but whether Drupal is a suitable implementation of CMS, whether agencies can sell CMS properly, and whether I want to do this anymore are big questions for me right now.
- davedx 14y agoSounds a lot like most enterprise development. You don't write much code in that line of work day-to-day, you do lots of plumbing instead. With Java I found myself spending as much time writing XML to get A wired up to B as I was writing Java code. I also remember using Hippo CMS on a project that wasn't well suited to it. That was the double whammie of enterprise Java and all its warts (complicated maven build system, XML coming out of my ears) AND the 'square peg, round hole' problem whereby the sold solution isn't actually remotely possible with the technology chosen out of the box. It was around that time I quit that job.