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

Align Status and Visibility settings in Site Editor and Post Editor #52643

Closed
afercia opened this issue Jul 14, 2023 · 1 comment
Closed

Align Status and Visibility settings in Site Editor and Post Editor #52643

afercia opened this issue Jul 14, 2023 · 1 comment
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

Comments

@afercia
Copy link
Contributor

afercia commented Jul 14, 2023

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':

site editor Status Visibility properties mixed together

To me, that's extremely confusing as these properties have always been separated into two groups: Status and Visibility.

In the Post editor instead:

  • the Visibility properties live in a dedicated 'Visibility" group / popover:
Screenshot 2023-07-14 at 16 06 18
  • the Status properties (Published, Scheduled, Pending review, Draft) work a bit differently: they're either inherently set (for example based on the publish date) or have separated settings.

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:

classic

Visibility:

  • Public
  • Private
  • Password protected

Status:

  • Published
  • Scheduled (shown conditionally based on the publish date)
  • Pending review
  • Draft

Lastly, there's some wrong terminology in use e.g.

Published
Visible to everyone

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

  • Go to the Site editor > Pages > any page
  • In the Settings panel, edit the page Status
  • Observe the Status and Visibility properties are all mixed together within the same group / popover.

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

@afercia afercia added [Type] Bug An existing feature does not function as intended Needs Design Feedback Needs general design feedback. [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Jul 14, 2023
@youknowriad
Copy link
Contributor

This has been addressed in a previous release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants