[wp-meta] [Making WordPress.org] #7593: Remove the non-block editor

Making WordPress.org noreply at wordpress.org
Thu Apr 18 03:04:03 UTC 2024


#7593: Remove the non-block editor
----------------------------+---------------------
 Reporter:  dd32            |       Owner:  (none)
     Type:  task (blessed)  |      Status:  new
 Priority:  low             |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------

Comment (by Cybr):

 > [...] but opinion needs to be backed up with data and examples.

 Yes, but the data must be analyzed with the proper perspective. Or should
 I say a different perspective? Allow me.

 > Given the option to disable the editor is already hidden in the user
 profile [...]

 Indeed, the adoption rate of the non-block editor is low because it isn't
 obvious that it has a toggle. We may see very different adoption rates if
 the toggle were underneath the editor.

 The opposite adoption rate was there for Gutenberg versus the Classic
 Editor: Right before WP 5.0 was shipped,
 [https://web.archive.org/web/20181205022206/https://wordpress.org/plugins/gutenberg/
 only 700,000] out of [https://trends.builtwith.com/cms/WordPress
 22,500,000 WordPress sites] used Gutenberg --- 97.69% of users stuck to
 the Classic Editor or another page builder. This number aligns with your
 findings above, but then for opposite ends.

 Yet there's one big difference: Gutenberg's plugin was more in-your-face.
 It is a featured plugin. I even recall
 [https://make.wordpress.org/core/2018/08/02/try-gutenberg-callout-in-
 wordpress-4-9-8/ notifications about it in our dashboard]. Yet,
 contrasting what would be logical, and only because of Gutenberg's
 insignificant adoption, the decision was made to foist WordPress 5.0's
 release with a 3-day notice. Otherwise, developers wouldn't be inclined to
 support the pre-alpha software with incoherent API and arcane coding
 standards, which subsequently caused WordPress.com to fail to compete
 against Wix because the Block Editor was suffering from plugin
 incompatibilities. Anyway... excuse my indulgent digression about the
 past.

 Then, about this:
 > Those not using the block-editor don't add alt tags to their images.

 I always added the alt-tags until I found they were removed during the
 saving process; perhaps this was a temporary issue, so I'll try it again
 later when I need to post images again. Still, this bug and the missing
 alt-text interface are why alt-tags are under-utilized, and it shouldn't
 be used as an argument in favor of the Block Editor.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7593#comment:10>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list