Actually, the DNC has a contractual and fiduciary responsibility to stay neutral in a primary, because they sign contracts to that affect.
Section 4 of the Democratic Party charter reads this way:
"In the conduct and management of the affairs and procedures of the Democratic National Committee, particularly as they apply to the preparation and conduct of the Presidential nomination process, the Chairperson shall exercise impartiality and evenhandedness as between the Presidential candidates and campaigns. The Chairperson shall be responsible for ensuring that the national officers and staff of the Democratic National Committee maintain impartiality and evenhandedness during the Democratic Party Presidential nominating process."
The chairperson was Debbie Wasserman Schultz, who resigned / was fired earlier today. The CEO of the DNC is Amy Dacey. But look at their emails and tell me if that lives up the charter.
Some of us are suing.
Get a new boss.
Seriously, I have been contributing to Drupal for 13 years and have a pretty sophisticated understanding of how it works. The organizations that are successful with it are similar to ones that work with other platforms.
They are realistic with expectations. No CMS is a silver bullet.
They all seem so bad until you consider any alternative, and the work that goes into maintaining it over time.
Vi. Amazing what you can do with macros.
So, I agree with any advice about finding a decision table and making up your own mind. Take what they have to say with a grain of salt, however, and realize each table has it's own focus which may or may not be what is important to you.
That said, Drupal is the best CMS right now, and it's doing work to stay in that role for a long time to come.
From a usability perspective, the core team has done a lot of work to make it simpler to work with Drupal and interact with content. It's very easy to spin up new content types, add fields, and create pages / widgets that present that information. Now that views is in core, you can actually author a site using only drag-and-drop tools. Which is great for people just looking to get a single site up and running.
From a technical perspective, symphony is now installed as part of core, which opens a whole lot of possibilities around what you can actually do with it. One of my favorite features is the CMI initiative, which allows you to author a site using a config file, and use that to spin up lots and lots of sites. Which is great for enterprises, looking to adopt a CMS in a big way.
From an extensibility perspective, one of the most powerful features in the platform is native support for REST and JSON. Drupal can serve as a provider of data for single page applications, where people author content in Drupal and you load it through apps authored in Angular / Ember / React. Drupal simply serves as an API endpoint in this context, which allows you to pull data from it whenever you need it.
I realize you can do these things with Wordpress as well, but not as easily or as scalably. Whenever you get past trivial use cases, there's always something getting in the way with Wordpress that makes it less appealing. And other commercial enterprise content management systems, like SiteCore, are simply not extensible. The moment you go outside the sandbox they set up for you, it becomes very hard to make them work.
The first sign of maturity is the discovery that the volume knob also turns to the left.