Unify communication and terminology around the block editor vs Gutenberg across WordPress.org and associated venues (such as WordCamps, social media ++)

[Clorith]

This isn't a new topic by any stretch of the imagination, but it is one that it would really help to ensure we have a consistent voice about across dotorg; The use of "Gutenberg" as a terminology for the editor.
I know that re-branding is hard, especially because as a project we shot our self in the foot early on by using it as the name for the editor, and ecosystem adoption made it hard to change, tutorials, articles hyping it up pre-release, post-release, etc. adds to that difficulty.

In addition, there's the wordpress.org/gutenberg page, where the first thing you see is "Say Hello to Gutenberg, the WordPress Editor", further solidifying this.
Gutenberg is a project name for a bigger overhaul of many WordPress aspects, it started with the content editor, it's now dealing with the whole site structure, widgets, and menus. In addition it is the basis for the upcoming admin redesign/reinvention, very likely the new media management flow, and phase 4 being introducing multilingual support to core (which covers many more aspects again) ... it's just so much more than the editor that when someone says "Gutenberg", you either don't know what they mean, or they're not "part of the community", so to them it's either the content editor or the plugin; and that's that.

This confusion is added to when you consider things like the Core handbook, that says "don't say Gutenberg, say this instead...".

There's been some efforts by folks to point this out, blogposts form third parties etc, but as a project we keep making the same mistake, including things such as presentations at WordCamps using it as a term for the block editor, and in our own marketing material (the WordPress.org website being the obviously prominent part of that).

It would be fantastic if we as a project could align and be consistent, that means we can actually have guidelines for WordCamps that "this is what X means if you are presenting", and if the final result is "Gutenberg means the block editor", then this would likely need to be a larger discussion as the confusion from all features being bundled in the Gutenberg code repository/plugin will maintain that confusion. (And for the sake of history, the problem of the plugin vs core vs features has been brought up in #core many years ago, but the idea of splitting up the features between multiple plugins was shut down by the Gutenberg team at the time, but it's worth revisiting if needed as things may have changed over the years, tooling making it easier, and so on 🙂)