I am using Google to translate this, so apologies if anything didn’t translate coorrectly, I wanted to give you a reply though.
I would like to dig more into why for you @spadilha there is no reason for Gutenberg. What are you using WordPress to create? Do you use any existing visual builders? I would also love to know what other fields are inerferred with for you. Are you for example using heavily custom fields?
Hi Tammie, we can talk in english.
Yes, I’m a heavy user of custom fields with ACF PRO. I build websites with WordPress based on layouts exclusively designed for the projects. I don’t use any “base theme”. As I like to say, I “motorize” the layouts with WordPress. So for my point of view “the_content” was just one field, sometimes the most important field (like the main content of a page or post), but sometimes unnecessary.
Here are some prints of a custom post type that I did without the main content:
View post on imgur.com
View post on imgur.com
View post on imgur.com
another example:
View post on imgur.com
View post on imgur.com
As you can see I organize the custom fields per my clients needs. I don’t wanna let them freely add blocks on the page. I have a very specific field for each information the user must enter.
I know I can still use the classic editor plugin, but what’s going to happen in 2021 when its support end? Many developers build complex websites for clients and they must have control of the page structure. If you see WP as a CMS it makes much more sense to see the content as just one simple field.
Gutenberg can be a good feature, but it shouldn’t be mandatory. It shouldn’t take control of the whole page. Although I don’t use page builders (cause I am the page builder) I know there’re many plugins on the market that do a great job. They have their audience, specially with people that don’t code, but I don’t see why the framework should use this approach. It’s a complete change of paradigm, but I think not in a good direction.
