WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#45002 closed enhancement (invalid)

Make Publish, Preview button stick to bottom and introduce Back to Top for Admin

Reported by: s3w47m88 Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9.8
Component: Editor Keywords: 2nd-opinion ux-feedback ui-feedback
Focuses: Cc:

Description

This is apart of a bigger project for my staff and I, you can find the context here https://www.theportlandcompany.com/2017/09/10/proposed-improvements-to-the-wordpress-ui/.

Our goal is to clean up the UI with two principles in mind:

  • Context Visibility - Only show something when it's in context.
  • Add With Purpose - If something, such as padding or margins, don't serve a purpose, don't add them.
  • Simplify Number of Actions - If a step can be avoided in a process, avoid it.

When a page runs long, users have to scroll back to the top to Publish or Preview their work because the Publish panel is fixed to the top of the page.

We developed this Plugin as a solution to this problem: https://wordpress.org/plugins/wppc-bottom-publish-button/

  • Introduces a back to top button to eliminate the need for scrolling.
  • Sticks the Publish and Preview buttons to the bottom of the page.

Built with jQuery. We're happy to make revisions in the interest of persuading the WP Core leadership to accept the feature.

Change History (5)

#1 follow-up: @joyously
2 years ago

  • Component changed from General to Editor
  • Type changed from defect (bug) to enhancement

If the buttons stick to the bottom, why the need to jump to top?

I think this should stay as a plugin.

#2 in reply to: ↑ 1 @s3w47m88
2 years ago

Replying to joyously:

If the buttons stick to the bottom, why the need to jump to top?

Great question. In my experience there are other reasons to jump to the top again than just clicking Publish and Preview. Such as to edit the title, or access something in the navigation.

I think this should stay as a plugin.

Would you be willing to explain why you think it should remain a Plugin? Even in the vanilla WordPress if you have all the panels open and expanded this is relevant. We also aimed to make it invisible until scroll and consistent with WordPress UI so it was as non-invasive as possible. Also, if jQuery isn't the optimal implementation we're willing to recode it in some other way.

Thank you for the swift reply!

#3 @joyously
2 years ago

In my view, it's not broken, and I don't like things to be invisible until scrolled or hidden until hovered. It's harder to find things.

It should stay as a plugin because it's not very accessible. Buttons need to be where they are in the source of the page for tab order to work right and for the Page Reader announce to make sense.

Some of us have years of habit with the primary buttons at the top, so it's preferable to keep them there.

Also, the editor page is changing in 5.0, so this would only be applicable to the Classic editor plugin. The new editor page doesn't have the same button layout.

#4 @s3w47m88
2 years ago

  • Resolution set to invalid
  • Status changed from new to closed

There might be a little confusion about this one.

This Plugin does not hide the Publish and Preview buttons. Rather, it keeps them visible.

Also, this Plugin does not remove the existing Publish panel and respective buttons. :) I can share a video if that would help?

However, you're absolutely right this issue is solved with Gutenberg. I'm way behind the times with Gutenberg and only started using it last week on select sites. So I guess you're right! This is a moot point. Sorry to waste time but thank you! :)

#5 @netweb
2 years ago

  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.