Gutenberg is not a builder, TinyMCE never was WYSIWYG.
And isn’t enough for you to disable Gutenberg and use the old editor? there are like a hundred different ways to do so now. Disable Gutenberg plugin comes to mind as the best right now for this task.
@ogalinski
You are talking semantics. I am well aware what gutenberg is and if you read carefully my comments and understood my points, it is that the “block” approach is similar to a builder and if you want to go that route, it is better to use a page builder that works well. Gutenberg is just a terrible approach to creating the block content. Also, a point I was making is that it does not work well with builders.
Regarding your comments about disabling gutenberg, is not addressing the issues I am raising with gutenberg being a core part of WordPress now. Adding additional plugins to disable something in the core of WP that most people do not like is not really a fix but a bandaid. Wouldn’t it be much better to solve problems at the route causes and frustrations?
So, while you make valid points about what gutenberg is defined as, you don’t actually make any valid points to why this feature is actually good. I go back to the overwhelmingly negative response to this feature and that fact that it is not a step forward like the WP team intended it to be, in my opinion.
-
This reply was modified 5 years, 4 months ago by tdcribb.
@tdcribb
It’s not semantics; there is a very distinct set of features that separate a builder from Gutenberg; in the future it will be a builder, but right now it isn’t. As for not playing well with other builders, well, it plays great with Elementor.
As for Gutenberg now in core, and this is strictly personal preference, as long as is not forced to be the only way to edit content, is ok by me. But like I said, this is strictly personal. I like this option specially for those who make a living out of WordPress, in a way that they *have* an option to keep their business as always.
As for why Gutenberg is good, this is why: for me the old way to edit content was never comfortable; I believe that we got used to compose content by way of a mashup of the editor, shortcodes, plugins and some magic incantations to edit the content the way we wanted. I believe its easier with Gutenberg. And I’m talking 5000-8000 word, images and media posts, not the typical (no offense) 300 word all-text post.
Then again, I will concede that there are many use cases that could be outside of what Gutenberg offers.
Cheers
@ogalinski
I appreciate your comments and thank you for elaborating on your thoughts. I think we disagree with some items regarding Gutenberg, but I can understand where you are coming from. Thanks.
Thank you for your cogent analysis, @tdcribb. You are expressing a rational and common response to the Gutenberg mess.
Unfortunately, I think your plea to “Please read these reviews and you can clearly see that no one actually likes this change” is falling on deaf ears.
> there is a very distinct set of features that separate a builder from Gutenberg; in the future it will be a builder, but right now it isn’t.
Is this really happening? Is Gutenberg destined to be a full-blown page builder? That’s exactly what we want to avoid at all costs! When working with corporate clients, maintaining consistency with layout and brand are paramount to the success of those sites, and the LAST thing we want to do is give site editors tools to go make their own content layouts on a whim. If the future of WordPress involves more fully resembling Wix or SquareSpace, and if WordPress cannot commit to indefinitely supporting the classic editor, that’s going to eliminate our ability to use WordPress with roughly 75% of our clients.
Our second CMS of choice is Craft; this may need to replace WordPress for our builds going forward.
@studio1337
Craft is ok, but a) is not free (for professional use), and b) doesn’t have the ecosystem WordPress has.
On support of classic editor, they have commited to support it until 2021, then well see what happens.
Check Matt Mullenweg State of the Word at WCUS 2018 (is on YouTube), you’ll see what the future holds for WordPress.