Drupal

“Modern Drupal is more geared towards coders rather than smaller folks.”

“This current strategy of Drupal has high risks in terms of maintainability, stability, security and privacy”

“I like to think of Drupal as the worst CMS, except for all the others.”

“It's a solid framework to build on without having to reinvent the CMS wheel.”

“What came after was such a different beast it should have just been its own thing.”

“it is genuinely a very good product now, and one that LLMs are incredibly good at building with”

“I wouldn't put Drupal or Wordpress near the top of the pile for good ones anyway, but I'd still put them above any bespoke CMS I've ever seen.”

“Drupal has been absolute mess for maintenance, backwards compatibility, responsive ness (code/dev wise).”

“it's vulnerable to one of the most serious and easily-exploitable RCEs in the history of computing”

“That's Drupal's strength and I don't think there's anything better for it.”

“Better code, better community, better architecture etc.”

“I came to have a lot of respect for how configuration works in modern Drupal”

“To be fair, they did it once, from v7 to v8. But yeah, a major release does break APIs.”

“When I last tried the Windows version, it didn't work and just gave the old Drupal white screen of death in the browser.”

“There's no way you're using modern Drupal without SSH access and using command line to install and update.”

“The reason Drupal can do what it does today is because of this willingness to rebuild”

“battle tested without having to make all the decisions that get you there”

“Drupal's features and functionality match the requirements of your project the best.”

“Drupal earned that reputation for so many architectural upheavals and pointless version churning”

“But that rewriting the base system, every couple of years, was why I dropped it.”

“Drupal can do what it does today because it continually rebuilt it's foundation”

“It has understood and workable flows for things like content approval, timed releases, etc.”

“The scale of publishing + users + need for governance is exploding.”

“I don't think there is a place for Drupal outside of higher educations marketing.”

“It's actually a great target for agentic coding, because it has such a well-established internal API.”

“build on top of a lot of well discussed well thought through solutions to these sorts of problems that the Drupal community has dealt with for a couple of decades”

“at least you do have a choice or path forward when the situation arises”

“Drupal is no paragon of security”

“will check that it can't write to anything but its designated file uploads directory”

“has had a commit credit system going for years that has worked well enough that people are constantly trying to game it”

“I loved its templating system (the fact that HTML was assembled on the back end) and it was so powerful!”

“Drupal and WP etc all have plugins to switch stuff on in minutes, however, customising and making it as your client wants would take a lot of time.”

“I totally saw the value for the client but I really disliked my experience, so I avoided it afterwards.”

“had literally thousands of developers volunteering code to the core development project, a dedicated security team”

“I recommended we use Drupal in 2011. That was killed because everything had to be MS.”

“the overall ecosystem is so expandable and the community is great”

“Drupal was even better, but the barrier to entry was higher.”

“I always liked the pragmatism surrounding it, reaching to the point of saving php code into the mysql database”

“if you fully buy into Drupal, it can do most everything without programming”

“it's stood the (multi-decade) test of time”