Not for us
-
We still can’t find a place for Guts as we lovingly call it. I cant train clients to use it, I personally dont see anything that will help my work flow as a web dev and I really cant handle the HTML code and the messy messy way they setup the raw code views.
I spend most of my time removing Gutenberg’s frankly horrid code from users’ sites so they can get back to an editor that is not confusing and very black-box. As a dev I just cant see an advantage, the HTML is so mangled as its created. Also the recent block changes to WooCommerce really messed up a lot of sites I manage.
I have used a variety of builders and just hard code in the classic editor as for me this is the ceiling of what site owners want and also what they can handle. I think this is being built by folks who with all respect dont use WP in a real world way.
This is a nice idea, but there are so many builders that work, these could be aquired easily and brought into core. This is not working as is, there has been years and years of this and its barely at alpha stages, it also is not faster or easy to use straight out of the box, it is missing features. When Guts is done I fear it will be either anemic for features or like JetPack just a total overload.
Not a single new business inquiry related to Gutenberg either, other than folks who dont know what it is, but that their site looks defaced, after the builder messed something up.
This project needs imo to be scrapped or moved out of core, how likely this is now I dont know. But it has no real goal, no real way to measure what it meant to do and where it is going.
- The topic ‘Not for us’ is closed to new replies.