This should remain a plugin and not the default editor! Just horrible.

  • This editor has a 2.5 average rating yet its being built into core? What kind of backwards thinking is this? I tried it for 5 minutes and it is nowhere near as functional as other front-end editors, it is super clunky and very limiting.

    I don’t know what Matt and the team over at WP are thinking, but this is going to piss off a lot of loyal developers who use WP to build web applications to make a living, including myself.

    This should remain a plugin just like all of the other 3rd party page builders.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tammie Lister

    (@karmatosed)

    @viablethought first thanks for taking time to test. I would like to first clarify this isn’t intended at this stage to be a front end editor. It is in phase one an editor (in the admin) and the next phase will move onto Customization, more page building features.

    That said, I would love to learn what experience you feel right now is the best front-end editor? You seem to have some insights there if possible would be great to hear. Thanks.

    Thread Starter Jason Ryan

    (@viablethought)

    @karmatosed –

    Being a developer, I personally don’t like front-end builders. However, to stay on top of whats out there I do research everything in order to have an some sort of awareness of other plugins and products available that “may” make it easier for non-developers or non-designers to edit their applications. So far the only two that I have found to somewhat interesting is Beaver Builder and Elementor. But by no means have I ever moved forward with including them in projects nor would I ever suggest that they be a part of core.

    That being said, the allure of WordPress has always been the fact that it is a great bare-bones content management system right out of the box that can be completely customized the way you see fit for yourself, or for your clients. Again, this being forced into core is taking away from that bar-bones aspect and adding something I know that myself nor any of my clients would even use. And I will never “enable” it as the default editor because it will just create chaos and we certainly don’t have the resources in house to handle the conflicts with this plugin if they should arise.

    We have a really great setup that works perfectly for our clients and it will continue to stay that way. Sorry, but I nor anyone on our team is a fan of this plugin.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘This should remain a plugin and not the default editor! Just horrible.’ is closed to new replies.

Tags