It’s not that the frustration is with which editor is being utilized but rather how the editor affects the customizable experience. Developers love the option to customize the edit screen (and more), and with the current build, that customization experience is quite lacking or is simply unavailable. A lot of work is being done in Gutenberg, yes, but a lot of work needs to be done still, and on top of that, developers (especially plugin developers) will have to spend great amounts of time trying to make the experience work again. It’s challenging and often frustrating moving out of one system and into the next when there were so many things about the old system that millions became accustomed to. It’s not to say the adaptation will be too much, but rather the path to get there is unknown at this time, and could potentially be detrimental to freelancers, agencies, etc., should the project get adopted and cause countless sites/plugins to break. That’s a serious concern.
@alfredg thank you for taking the time to leave a review. What excites you the most about the new editor?
@jjcarlson it’s interesting to note you are both talking about different users. That’s an important point right here. As a community we have to work through to get a solution for all users across the range.
Hi Tammie,
What exited me most was the clean interface and how light is seemed to work. I also saw room for improvement but you are still working on the project. For instance making a link to the original picture I had to insert a link while in the old situation I could give it a target rigt away.
In my opinion also html code could be insterted. Maybe I’m an average user but for me it was enough to be very hopefull.
Also it is known that every change gives resistance. I’ve seen it in other implementation project, now that things are not new anymore people don’t want to go back, so that gives hope for Gutenberg.
By the way, I can freely switch between the old and the new editor, mayby it should stay that way so everybody can be happy!
Tammie,
Precisely. It’s a challenge to meet the needs, or at least wants, of all parties. SquareSpace doesn’t have the ideal solution; Drupal doesn’t have the ideal solution; and WordPress hasn’t had the ideal solution. I’ve had clients ask if their site will be super easy to edit and make all sorts of changes to, and my response in my head is that their site will probably never be able to do everything they can dream up. I prefer avoiding themes with all the bells and whistles, because of they too do not cover all bases, and they have limitations. Build toward the project, then scale. I think that’s the ideal solution for a client, but it’s a hard thing to create.
Thanks!
We usually develop custom type that uses description section to get detailed information on particular post. We have been using wordpress because it made every thing easier as shown on the image link below. (NOTE I am using WooCommerce for example)
View post on imgur.com
The page looks very different after installing Gutenberg as shown below.
View post on imgur.com
This is very confusing because we do not intend to submit a post but we are only adding product description. The Classic Editor had advantage of Keeping It Simple and Smart(KISS).
Gutenberg should only be used on adding blog post and should not replace every area custom types are used. There should be an option to choose whether to use Gutenberg or not when developing custom types.
Example: We have customs type for Job, Faqs and Testimonials. Why would I need Gutenberg when posting? The post description is usually one paragraph or two and does not require column,blocks etc.
Suggestion: Let use use Gutenberg on submitting post, but on custom types let us allow the use of classic editor where it is needed.
.
