Horrible Forced Adoption

  • The great thing about WordPress was it just worked. Business owners, freelancers, agencies, and more loved it because you could make it fit whatever your specific needs were. With this ridiculous move by WordPress to force adoption of a content editor that doesn’t work with 99% of the existing plugins for WordPress they started going down a horrible path. The biggest benefit of WordPress was the plugin base. You’ve now broken that. Give people the option to use one or the other but don’t break existing functionality like ACF.

    Horrible decision to force adoption without getting community input ahead of time. Agencies hate Gutenburg it doesn’t fit into the model of locking down a client’s design. This was a massive mistake and until they fix it, they will hurt the overall WordPress community.

Viewing 1 replies (of 1 total)

  • Yes! The biggest flaw in Gutenberg isn’t its bugs or its over-encumbered workflow, though these are certainly issues worthy of low marks. The biggest flaw is that it goes against the whole principle that a well made site with strict branding guidelines should NOT allow end users to arbitrarily use any object of their choice in any order they wish on any page they choose. With tools like ACF, you can very narrowly define how end users manage their pages so they have as much or as little flexibility as they SHOULD have, not as much as WordPress wants EVERYONE to have. There’s a reason developers who use WordPress are not using Wix or SquareSpace. Making WordPress more like those platforms, and making it the core WP experience, defeats that position. Maybe all of this can be worked around, but fighting the editor tooth and nail to pare it down and mold it into something usable is not a worthy use of time, especially when after you’ve done all that, it’s still buggy and still painful for people to use.

    Wordpress will only remain useful so long as meta boxes are supported and the classic editor is available. Gutenberg is terrible, not (just) because it’s buggy, but because it fundamentally breaks strong, well managed workflows that developers have established and customized uniquely to each of their clients. It should be optional, at best, and it should prove its value the old-fashioned way, by becoming such an important and beloved tool that moving it into core is a no-brainer, kind of how ACF is all of that right now.

Viewing 1 replies (of 1 total)
  • The topic ‘Horrible Forced Adoption’ is closed to new replies.