1. Site adoption rates, especially in the enterprise space. You're absolutely right, the developer community isn't growing, and I think the blame for that lies

1. Site adoption rates, especially in the enterprise space. You're absolutely right, the developer community isn't growing, and I think the blame for that lies squarely with the core codebase's deathmarch towards becoming Sharepoint. There was a point in time (circa D5, early D6) when coding with Drupal was still kinda fun. Core architecture didn't get in the way as much. 2. There are user groups, I've organized two of them. They are frequently full of people who have basic problems and a few exasperated and grizzly veterans who offer arcane solutions to non-arcane problems. Best outcomes typically occur when one or more local dev shops get involved with the group and use community support as a way to build their brand. Anecdotally this describes most tech user groups. 3. Yes, this is a feature. It's objectively better because you are not writing code. In addition to the obvious benefits (no fucking code) this puts the task at hand (at least theoretically) within the reach of non-technical or semi-technical individuals. 4. I dislike Drupal's internals for diverse and varied reasons I will not go into here. I dislike Wordpress's internals for many of the same reasons, and Wordpress is substantially more limited in it's capabilities than Drupal. Same general set of problems, many fewer features. Also, I agree Drupal's documentation sucks hard. Unfortunately there's nothing to be done about it. It would take close to 10,000 man-hours to write shitty, blatantly misinformed documentation for the current body of contributed modules, assuming you budgeted 30 minutes to examine the module and 30 minutes to write about it.