I’ve been finding it increasingly challenging to position Drupal with clients when WordPress tends to feel more stable in comparison. The Drupal 7 → 8 migration was already a tough sell for some clients, and now the CKEditor 4 → 5 migration feels like another uphill climb.

Many of the CKEditor ecosystem modules (Linkit, CKEditor Templates, etc.) have taken a long time to fully catch up, and some are still buggy. On top of that, core and contributed modules often need patches to work as expected, and sometimes updates introduce new issues rather than resolving them.

I’d love to hear how others approach this:

• How do you frame Drupal’s value when clients are frustrated by bugs and regressions?
• What strategies do you use to maintain stability and client confidence? Testing my own custom code is one thing, but I expect contributed modules to do this for themselves. I guess that’s a wrong assumption. Having a dev, staging, and production site are good too, but they only go so far for the sneaky regressions that make their way into a live site.
• Do you think we could move toward stronger automated testing for contrib, maybe even with AI to help increase coverage?

Is anyone else a little weary of CKEditor at this point? It’s surprising that in 2025 we still don’t have a truly smooth WYSIWYG experience in Drupal. It reminds me of the growing pains we had with media in early Drupal 8.