Make it optional

  • Why build this into the core of WordPress? Frankly I don’t care for it. I manage at least 20 WordPress sites for clients and for everyone one I utilize some of the most amazing third party page builders such as site origins, wp bakery’s visual composer and theme.co’s Pro and cornerstone. I say let other developers like these run wild. WordPress shouldn’t force their own half assed builder into the core and make it difficult for those who use something else.

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

    (@karmatosed)

    @tech4eleven thanks for taking the time to leave a review and test the new editor. You mention you use visual composer and theme.co’s Pro. Could I ask what specifically from those you think should be learnt?

    Thread Starter Tech4Eleven

    (@tech4eleven)

    Hi Tammie. thanks for the reply.

    I personally think that WordPress should not integrate a visual page builder of any kind into the core. I think if WordPress wants to, they should make it optional by default. I like that, right now, you can install the classic editor plugin and it overrides Gutenberg. I hope at least it stays this way when v5 is released. I think if anything can be learned from third party visual page builders it should be that wordpress should build wordpress in such a way that allow developers to shine. WordPress has the greatest resource of plugins, themes and other extensions from 3rd party developers and i hate see anything hinder that.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Make it optional’ is closed to new replies.