Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a way to identify the source of a block #16521

Closed
Otto42 opened this issue Jul 10, 2019 · 7 comments
Closed

Provide a way to identify the source of a block #16521

Otto42 opened this issue Jul 10, 2019 · 7 comments
Labels
[Feature] Block Directory Related to the Block Directory, a repository of block plugins [Type] Enhancement A suggestion for improvement.

Comments

@Otto42
Copy link
Member

Otto42 commented Jul 10, 2019

With the prevalence of new blocks and possibly the start of a new block directory, it seems like more and more it is possible for users to be using a block without knowing where it came from.

Example:

https://www.reddit.com/r/Wordpress/comments/cb58se/why_is_my_gutenberg_table_of_contents_non/

TL;DR: User asked about a table of contents block, when asked what plugin added it, they thought it was a default block.

Blocks need to have some way to identify themselves and where they come from to the end-user. Simple "branding" isn't going to be enough, this should be built into the structure of the block system and exposed somewhere as a standard item.

@brentswisher brentswisher added [Type] Enhancement A suggestion for improvement. [Feature] Block Directory Related to the Block Directory, a repository of block plugins labels Jul 10, 2019
@TimothyBJacobs
Copy link
Member

💯 I see this at our local meetup as well.

@marekhrabe
Copy link
Contributor

I have noticed the Plugin directory started to list block in the detail view by their name (prefix/block format). See for example https://wordpress.org/plugins/atomic-blocks/#blocks.

It might be good to show this block name somewhere in the UI of Gutenberg. What about the sidebar with block settings? Would that be too prominent?

Screenshot 2019-07-31 at 17 22 46

I guess the block name was always considered something that users don't directly see but with those being slowly exposed in other places and the issue with identifying blocks, this might become important.

@marekhrabe marekhrabe added the Needs Design Feedback Needs general design feedback. label Aug 1, 2019
@marekhrabe
Copy link
Contributor

marekhrabe commented Aug 1, 2019

The Block Manager could be another good place where this would make sense and won't be on eyes all the time.

Screenshot 2019-07-31 at 17 30 28

Or the new Help Panel being developed in #16813.

@mtias
Copy link
Member

mtias commented Aug 2, 2019

If we instrument collections (#16866), it could be surfaced next to the block name / description in the sidebar.

@richtabor richtabor removed the Needs Design Feedback Needs general design feedback. label Feb 4, 2020
@richtabor
Copy link
Member

We chatted about this in today's design meeting (Slack). Adding the source under the title in the Settings Sidebar seems logical, though two notes:

  1. Perhaps we could employ a more natural label "from CoBlocks".

  2. Do core blocks need this, or only third party blocks?

@StevenDufresne
Copy link
Contributor

StevenDufresne commented May 12, 2020

Perhaps we could employ a more natural label "from CoBlocks".

This makes the most sense to me since the block type is a technical detail and not expected to be surfaced this visibly.

Riffing on this idea.... I believe, as the block directory evolves and more third party blocks are used, users will want access to more meta information about the block than just its author. Based on the current block directory flow, it isn't apparent where I can go to learn more about the block (at least until some of the new block directory wp-admin views are implemented). Moreover, as blocks become more complex, space in the BlockInspector will be very valuable (Some conversations are already happening in the plugin guidelines).

Potential Solutions

  1. Could we make the block title a link?
  2. Add the natural label as @richtabor suggests and link to details.

*Note: I'm making the assumption that all plugins will have a details view.

These links could open up a new page with the block details open?

Settings

This would help make sure that the editor and the block inspector are focused on fulfilling its first mission, building.... and delegating secondary tasks elsewhere.

@annezazu
Copy link
Contributor

annezazu commented Sep 6, 2024

So much has changed in the five years since this was opened (!!!). I'm going to close this out as a result in favor of a more recent issue that matches current designs on the same topic: #64532

@annezazu annezazu closed this as completed Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Block Directory Related to the Block Directory, a repository of block plugins [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

No branches or pull requests

8 participants