• In case of Gutenberg: I expect problems with customers’ websites and performance penalty.

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

    (@karmatosed)

    Hi and thanks for leaving a review. There will always be a way you can turn off Gutenberg. Due to that, a lot of the issues with existing sites will be able to be resolved.

    That said, as the project grows more and more the hope is that turning off will not be something you have to do. What exactly do you feel would be a problem? It would be great to get some feedback on that. Thanks.

    Thread Starter hapke

    (@hapke)

    Thank you for your reply! WordPress becomes more and more a huge system. I see performance problems. I know some developers who say goodbuy to WordPress and now use an own or other content management system.

    Gutenberg should only be an option for those why like pagebuilding, but without loading too many files if I won’t use Gutenberg. My customers’ website use a framework. I’m sure there will be conflicts. To handle it will cost time. Customers do not understand this and will not pay for additional work.

    I’m sure that WordPress will loose it’s attractiveness among professionals.

    Avrom

    (@dividendninja)

    It already has. We can only assume when 5.0 rolls out, the option to switch off Gutenberg will be limited time.

    We have another CMS lined up. But as hapke points out, what do we do with the client’s who are already on WordPress?

    While WordPress has been an amazing framework in the past, the future of it as a development framework is now questionable. We have no choice but to be proactive and look for alternatives. How unfortunate.

    @hapke, what framework are you using? I just had to deal with Fusion – which was fine I guess. I ended up putting my work in widgets which I then placed in new “Widget Sections” in Fusion so I wouldn’t have to hook into any Fusion code. Works with no problem, but the Fusion editor just shows “Widget Area,” so I’m not sure my editor users understand how to edit the widgets. It’s a two step process now, one step on the Widgets page and one step on the Edit page. In other words, we’re using widgets as content blocks.

    We also have real widgets in sidebars, but that’s another matter. Like one of the rants in these forums mentioned, author editing of pages and posts is a lot different than designing the site. I guess Fusion was good at separating those tasks, and using widgets as content blocks was an OK way to go. For real widgets in sidebars, I just edited a few child theme files where we needed to add or remove sidebar areas.

    • This reply was modified 7 years, 1 month ago by kitchin. Reason: tags
    • This reply was modified 7 years, 1 month ago by kitchin.
    Thread Starter hapke

    (@hapke)

    @kitchin On one website I use xtreme one that is based on YAML. In the future I will change the theme completely, maybe I will use a standard one. I will still use a childtheme in the future as well.

    • This reply was modified 7 years, 1 month ago by hapke.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Keep WordPress lean’ is closed to new replies.