Why?
-
This isn’t a review of the plugin itself, it is a review of the process. I have had WP for over 3 years. Multiple sites and a lot of time spent to ensure my sites work with little or no maintenance. Now I see that there’s a plugin to be integrated into core which could (yes, could) jeopardise this. The question is, why? Other platforms release new products with new major features and still support the older versions for a number of years. Why are out sites being put at risk by changing the fundamental core software for no other apparent reason that to add a funky new feature that will change the lives of people installing product for the first time. Leave GB out of the core for existing users who are quite happy with the status quo of feature and by all means add it to a new fork for new users. This is the right way to do it. Not risking the good reputation WP has with existing users for no real reason. Thank you.
-
@buzztone You are right… but how long will the Classic Editor be supported? I can imagine that it will last for five years, maybe more, but sooner or later it will disappear, possibly with unpredictable consequences for older content.
Like @shane_o, I am a relatively recent newcomer to WP. I had one WP site since 2010, and after a few years I had become so much convinced that I moved most of my sites to WP starting about three years ago. Months of work, but I was very happy to do it because I felt that I had found a solution offering continuity for decades to come – evolving, true, but in continuity.
My problem is the logic of blocks for the editor. For some websites, it will be great. Not for most of the websites that I am editing, where texts are not dealt with as blocks, but as a whole. I have created a mock site for testing Gutenberg. At each new release, I have tested it again. Not convinced for my needs.
Please, WP management, do not add Gutenberg to the core! Or run side by side a Gutenberg WP fork and a Classical WP. Or make a commitment that the Classical Editor or any kind of successor with a continuity to the Classical Editor will remain available within Gutenberg WP for the very long term (I mean here not five years, but a much longer time perspective).
If I had known what would come, I would never have selected WP as the CMS for my sites, but I would have looked for another one. I am still hoping that Gutenberg will develop in a way acceptable to me, but I do not see it at this point: the kind of editor that I need is far away from the Gutenberg. Too bad – and feeling betrayed (I had tested CMS and editors with a block approach, but it had taken little time to understand that it was not what I needed).
The topic ‘Why?’ is closed to new replies.
