Gutenberg: Widgets editor: Is it "Block Areas" or "Widgets"?

[noisysocks]

In some places we call the new block-based widgets editor screen _Widgets_ and in other places we call it _Block Areas_. We ought to settle on one name so as to avoid user confusion.

[aristath]

"Block Areas" seems more future-proof than "widgets" considering widgets is basically legacy and we're moving away from them... Everything is a block.

[ZebulanStanphill]

Although "Block Areas" is a bit vague, I can't think of a more descriptive title, and "Widgets" is even more vague, and far less accurate of description, in my opinion. Using the "Block Areas" terminology could also help avoid confusing with the "Widgets" category in the inserter, which does not directly relate to this screen. So I'd definitely prefer the "block area" terminology.

[draganescu]

In the Widget editor I would use the same terminology that the current Widgets screen uses: "Widget Areas". Also I believe block areas are a feature which means more than placing blocks in the widget area, and are unrelated to widgets.

My opinion is to keep as close as we can with the copy, headings and concepts from the old editor: Widgets / Widget Areas / Sidebars

cc @mapk @mtias

[mapk]

A lot of that UI should be changing, @noisysocks. I remember getting feedback on "Block areas" not being very adequate. This page is really used in relation to older themes that don't yet support block-based structures and still rely on widget areas. So with that in mind, keeping "Widgets" is the way to go.

The UI should evolve into something like below.

1. "Widgets" is used in the topbar as a clear h1 heading for this page.
2. This helps communicate to users that this page is still used for widgets when it ultimately replaces that particular page.
3. The Inspector now only shows the widget area that is focused. In the example below, the "Sidebar".

[draganescu]

Should we close this then?

[draganescu]

Hey @mapk :) should we do anything here? Thank you!

[mapk]

As long as we're moving toward the desired UI, I don't think keeping this open is necessary. Unless, @noisysocks would like to keep it open until this has been implemented.

[annezazu]

Chatted with @noisysocks briefly about this and have moved this to needs dev. As Rob said to me, let’s not close this issue until this update is made.