"Configure block" button text in the Block Library is confusing [#1875780]

This issue is a duplicate of #1950700: Rename "Add block" to "Place block" on the blocks admin page

Problem/Motivation

This is a folllowup issue for #1535868: Convert all blocks into plugins.

When adding a new block instance from the block library, users need to click the "Configure block" button. This button text is confusing because the user is trying to add something new, not configure something that already exists.
When the custom block module is enabled, there is a button to "Add custom block" at the top of the block library table, which further confounds the issue.
Currently, the "Add custom block" button both creates the custom block and an instance of it, so the end result is the same as clicking "Configure block" for (e.g.) a menu block.

Proposed resolution

Change the "Configure block" button text to "Add block".
Consider placing "Add new custom block" in the block library table as its own row (possibly as a followup).

Remaining tasks

Related issues

Comment	File	Size	Author
#2	block-1875780.patch	673 bytes	xjm

Comments

Comment #1

xjm

she/her

English

commented 4 January 2013 at 17:22

Status:

Postponed

» Active

Comment #2

xjm

she/her

English

commented 7 January 2013 at 06:56

Status:

Active

» Needs review

Status	File	Size
new	block-1875780.patch	673 bytes

So just changing the link text is pretty simple, but I still think the "Add custom block" link might be confusing here. It might make more sense to have a special "New custom block" row at the top of the table instead?

A header above the block library table might help too.

Comment #3

gábor hojtsy

he/him

Hungarian

Hungary

commented 7 January 2013 at 14:36

Yeah I agree "Add block" works better vs. "Add custom block" because you might just add a block that is not yet placed but is shipped with a module or core, not really custom. You get to there by configuring an already provided block, yeah, but that is just due to the confusion caused by not using the "block instance" terminology on the UI and trying to call both block instances and to-be-configured blocks the same.