Right, because at your level, that's the kind of suggestion one can expect. Thanks for proving my points, Dilbert.
I've never found this to be true. Perhaps it's true for you?
Yes, I've known people who tried to monopolize the poor examples of developers and leverage them into force-feeding what would otherwise be completely unnecessary third-party tools that were never central to a core product, but are now and cause maintenance nightmares for anyone who wasn't part of a major team of developers.
But sure, it's possible I'm just throwing things at a wall to see what sticks...
I would reccomend Backdrop CMS - Basicly a clone of Drupal 7 but with a focus on growth in that niche that you are describing.
I'm not describing a niche. I'm describing a PROBLEM.
But I've seen this same old, boring, and tired movie before... It's the same passive dismissal I see all the time whenever someone happens to critique the Drupal trajectory and gets responded to by a roadie who thinks they know anything about the judge and then proceeds to suggest something like Wordpress for blogging. My god. It's like you people are blind to your own institutionalization and never learned anything from this overall quest we're on. The term "well-rounded" must be so alien...
Oh, and thanks for the Backdrop tip. I guess I never would've known anything about that thing in my 18+ years of being involved with Drupal...
The respective developers of a project are free to use whatever tools they believe works for their needs, regardless of whatever perceptions some of us might construe as being "the right tool." Anyone who tries to monopolize their poor examples to then be leveraged into force-feeding what would otherwise be completely unnecessary third-party tools that were never central to core, but are now and cause maintenance nightmares for anyone who isn't part of a major team of developers, are part of the adoption and top-heavy maintenance problems Drupal now faces.
As someone who's been following this mess for years now whose been on the Drupal train since version 6 and has since created a few projects with the latest iterations of Drupal, it's pretty clear that everyone's been jumping ship to get away from Drupal's maintenance obesity that a technical clique thought would somehow part seas back when they initially incorporated the Composer caltrops into its overall stack. Whoever believed that was a good idea did Drupal a major disservice, even if someone somewhere somehow got anything out of it.
I've seen Wordpress websites surpass the functionality that the Drupal 8+ apologists try to marginalize modern critics of whenever they resort to their claims about how anyone who wants to blog should stick to Wordpress and leave the heavy lifting to Drupal in their quest to keep rationalizing the cluster that Drupal has now become... And every time I see someone resort to that quip (or some variation thereof), I just shake my head because it's utter nonsense and myopic beyond belief. Adding to this, Drupal continues to suffer from Dries-itis: It needs new leadership and one which prioritizes the pursuit of balancing technical capability and control with end-user convenience. It's possible to have the best of both worlds, but these latest iterations of Drupal seem to focus solely on the technical alone, much of which haven't resulted in the gains that were promised. Dries plays a part in this because he speaks out of both sides of his mouth. One minute, he's prancing around on some stage somewhere lecturing everyone about an open internet, and in another, he's enabling the very mess we now have today. He needs to go.
The only hope Drupal has at this point is anything that the Starshot initiative can hopefully accomplish with all of this in mind. Last I understood, it was trying to reduce the maintenance fat and increase convenience. That's great! If that key group doesn't reduce the maintenance weight this bloated hog now suffers from, Drupal will die. They need to return to the grass roots of what originally made everyone fall in love with Drupal, which is SIMPLICITY. Throw it on a server, click a thing, type a few values, then BOOM: Installed and extensible without command lines, exterior apps, environment complication, etc. Since 8, they've erred on catering to the developer. From that strategy, maintainers have left in droves with overall Drupal adoption never being as bad as it is today. Those are just the facts. And all of those people who jump ship who have their bitter tastes in their mouths have opinions that spread faster than wild fire. Because of this, Drupal is in some serious trouble. The village idiot gets this. People were trying to stress this concern back when Composer, GIT, Drush, et al first got strong-armed, but the key clique just didn't listen. Well, here we are today and the piper's being paid.
But if the Starshot group can find a way to make Drupal easier to maintain and use--as in returning to what was the tried-and-true allure of updating both modules and core from an easy-to-use interface accessible from */admin without need of non-core apps one has to install and maintain outside of Drupal without sacrificing its enclosed sphere of overall implementation--then it'll return to its prior dominance. If that doesn't happen, then it's just screwed.