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

Reusable Block Manager: Use of "Published", "Private" and other post editing terms are confusing. #36906

Open
cecoates opened this issue Oct 20, 2019 · 1 comment
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg [Type] Enhancement User Report This issue was created following a WordPress customer report

Comments

@cecoates
Copy link

cecoates commented Oct 20, 2019

Steps to reproduce

  1. Starting at URL: https://wordpress.com/types/wp_block/
  2. Click "add new block"
  3. The language is the exact same as when editing a page/post.
  4. Public/Private, "Publish"/Draft.

What I expected

These terms don't really make sense when applied to blocks. It seems like you should just have "Save" or it just isn't saved.

Even drafts don't make sense because the blocks aren't actually published publicly anywhere. There's zero drawback to just saving a block, versus having a draft. Save/Update covers all those bases.

Similar to the Customizer, having the terms "Published"/"Draft" causes confusion for users. Anytime the word "published" is used users think of content specifically like posts, and updating their followers, the same way you'd publish a newspaper.

What happened instead

You can select the different options such as "private".

The use of private in particular is a bit confusing, as it makes the block invisible to everyone. Even the person who created it. So it's not like you can create blocks that only a specific admin can see.

Similarly, all the regular post/page options are available via the "three dot" button. Including switch to the Classic editor. In the context of the reusable block manager this also seems counter-intuitive.

Browser / OS version

Chrome Version 77.0.3865.105 (Official Build) (64-bit)

Screenshot / Video

Screenshot 2019-10-20 at 11 52 49

Screenshot 2019-10-20 at 11 53 09

Context / Source

2434888-zen

@simison simison added the [Goal] Gutenberg Working towards full integration with Gutenberg label Mar 3, 2020
@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

@kristenzuck kristenzuck added the User Report This issue was created following a WordPress customer report label Apr 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Goal] Gutenberg Working towards full integration with Gutenberg [Type] Enhancement User Report This issue was created following a WordPress customer report
Projects
None yet
Development

No branches or pull requests

4 participants