Align Status and Visibility settings in Site Editor and Post Editor #52643
Labels
[Feature] Site Editor
Related to the overarching Site Editor (formerly "full site editing")
Needs Design Feedback
Needs general design feedback.
[Type] Bug
An existing feature does not function as intended
Description
#52632 aims to align soem edit features in the Site and Post editorl. However, seems to me the edit features aren't the only things that would need to be better aligned. Some important parts of the UI aren't 'aligned' as well.
I'm not sure I understand why in the Site editor, when editing a page, the Status and Visibility properties are all mixed together under a group and popover named 'Status':
To me, that's extremely confusing as these properties have always been separated into two groups: Status and Visibility.
In the Post editor instead:
Providing two different UIs doesn't seem ideal to me. For example, the 'Private' setting in the Site editor is placed in a completely different spot compared to the Post editor, and so on. I think users will be greatly confused and forced to explore the UI every time they need to find one of these settings. There's no consistency in the two editors, nor the UI provide a sufficient affordance.
Not to mention that, in terms of UI, these properties have always been split into two separate groups in the Classic admin interface. Users are familiar with that and I'm not sure I see a good reason to change that convention. The screenshot below illustrates how these properties used to be presented in the Classic editor:
Visibility:
Status:
Lastly, there's some wrong terminology in use e.g.
That's a visibility setting: 'Published' should be 'Public'.
Marking this issue as Bug and not as Enhancement because IMHO the UI in the Site Editor is greatly unclear and provides a subpar experience for users.
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: