This will kill WordPress

  • For everyone’s sake – make Gutenberg optional.
    99% of my page edits are made directly to the page HTML, not even using the old WYSIWYG editor. Not only is Gutenberg appalling UX design but it also makes life difficult for more technical admins who do more with WordPress than just simple sites.
    If WordPress continue to force this new editor onto their users, they will find users move to other platforms.
    If it’s not broken, don’t fix it!

Viewing 2 replies - 1 through 2 (of 2 total)

  • While I really hate Gutenberg like you do, the HTML mode should always be the exception. Why? Because most users can’t handle HTML. It’s a very bad idea to use complex markup like DIV tags in the editor. Editors will very likely mess it up. Having said this, Gutenberg’s HTML mode is a joke. No doubt about that.

    He said HE uses it because apparently, HE knows hows HTML. We import posts into the WP through HTML tab too, because they are pre-edited in our in-house platform. So we just copypaste them through the HTML tab.

    I am also a guy that likes to try new things and won’t discredit them just being new. Change is a part of life. I know what they wanted to do with the blocks, but frankly, they just are not up to par with other visual editors. Sorry.

    If you build simple sites, simple blogs, then sure. If you want specific stuff, specific placements, good luck.

    This whole thing looks like it was built by devs who use WordPress for their own personal blogs on a basic level so they can’t really see what the catch is and will hardly see what the catch is because, well, they will stick to their guns because it took so long to build it. A classic programmer’s approach to solving things – if it’s good for them it MUST be good for everyone.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘This will kill WordPress’ is closed to new replies.