• The concept behind Gutenberg, that being to create a true WYSIWYG editor for WordPress is very good and admirable.

    But this is where the goodness ends. I am not opposed to these things just because they are new.I know they’ve been worked on for years. However, I am always opposed to the “new” when it breaks decades of good coding behavior and will replace the classic editor.

    From a simple business productivity point of view – it takes 5-10x longer to do anything.

    Form useability it takes many more mouse clicks to do anything in this editor.

    It also lacks the flexibility of using the standard WordPress convention of using PHP, and using the functions.php file to turn on/off these features (like menus, thumbnails and literally everything else in WordPress).

    The new editor relies heavily on REACT js, so moving away from the core functionality of PHP which has been the bedrock of WordPress since day dot. For developers this now requires yet another set of tools to load & learn.

    This should not be forced on users, the classic editor should be part of the standard release and users should be given the option to choose either classic or Gutenberg.

    Forcing Gutenberg on users will only cause splintering of the WordPress community as people stay on 4.9.x or look to other CMS alternatives

  • The topic ‘Horrible editing experience which will be forced on everyone’ is closed to new replies.