-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Prefer primary buttons in block placeholders #20441
Conversation
Size Change: +16 B (0%) Total Size: 865 kB
ℹ️ View Unchanged
|
From my perspective, there are potentially two competing design principals here:
If we turn these into primary buttons, it will violate item 1 since the publish button (in the top right corner) is already a primary button. On the other hand, if we do make them primary buttons, it likely satisfies item 2 better since completing the block setup is likely the thing they'd want to do next. Question: For blocks like the image block, where there are multiple buttons, which would we select? I don't have an opinion here, but I call it out simply to identify one additional issue that would need to be worked out. |
@davemart-in That's exactly what this PR is doing, the placeholder you're sharing (the image one) is already updated in master to have a single primary button and two tertiary ones. This PR does the same for the remaining placeholders. |
|
a2c73dc
to
ed27e9c
Compare
So should we merge this as a step towards these designs? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per the conversation, this is definitely good to test in the plugin.
Refs #18667
Similarly to the MediaPlaceholder, this PR updates the block placeholders to use primary buttons.
Before
After
Notes
Seems like there's a small visual glitch on the RSS block placeholder.