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

Add block 'badges' to communicate at-a-glance information #26632

Closed
jameskoster opened this issue Nov 2, 2020 · 5 comments
Closed

Add block 'badges' to communicate at-a-glance information #26632

jameskoster opened this issue Nov 2, 2020 · 5 comments
Labels
[Feature] Blocks Overall functionality of blocks [Type] Discussion For issues that are high-level and not yet ready to implement.

Comments

@jameskoster
Copy link
Contributor

In #26594 a need arose for a stylised "beta" token that would be applied to the Site Editor menu item in the wp-admin navigation.

This affordance may also be useful on a per-block level in the Site Editor as it becomes more prominent over time, to remind folks that many features are still a work in progress.

Screenshot 2020-11-02 at 13 31 24

We can apply a similar style treatment to the Site Editor link in the wp-admin navigation for consistency, if there is perceived value in doing so:

Screenshot 2020-11-02 at 13 42 10


Taking one step back, this feature may also be handy in the future for communicating other at-a-glance block information such as newness, secondary grouping (e.g. to indicate which blocks were added by a specific plugin), or whether an upgrade is required (for blocks with premium features).

Screenshot 2020-11-02 at 13 40 02

@jameskoster jameskoster added [Feature] Blocks Overall functionality of blocks [Type] Discussion For issues that are high-level and not yet ready to implement. labels Nov 2, 2020
@priethor
Copy link
Contributor

Block badges came as feedback during the Go/No-go demo on April 14th with the goal of marking block themes as "Lab" blocks, denoting they are stable (not beta) and can be used, but the user experience might not be polished yet.

@hedgefield
Copy link

This looks excellent and will indeed be very useful. I'd maybe bold the label text as the white on black is kinda hard to read at a small size. Otherwise I say go for it!

Small aside, I don't know if "Lab" is really going to be a word that means anything to the average user out of context like that. But I agree "Beta" or "Experimental" might make it sound too unstable. Perhaps something in the vein of "Early access", "Rough" or "Basic".

@hedgefield hedgefield removed the Needs Design Feedback Needs general design feedback. label Apr 29, 2021
@priethor
Copy link
Contributor

I think "Early access" is the option that best conveys the message.

@youknowriad
Copy link
Contributor

This didn't make the 5.8 cut, I'm removing it from the board. also cc @mtias in case you have thoughts about this, I know that we decided against such an API previously.

@mtias
Copy link
Member

mtias commented Jun 22, 2021

Yes, I worry about making it an API because it can get out of control without a clear indication of what we want to signal — are badge terms related to a specific taxonomy? Can they be used for anything? Would people use them as tags? Can you have many? Can they be extended? Can you remove existing ones? I'd expect we would also receive requests for colors, or icons, or making them actionable (act as a button), etc, if we are not clear about purpose and boundaries.

@mtias mtias closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Blocks Overall functionality of blocks [Type] Discussion For issues that are high-level and not yet ready to implement.
Projects
None yet
Development

No branches or pull requests

5 participants