WordPress.org

Make WordPress Core

Opened 19 months ago

Closed 19 months ago

Last modified 18 months ago

#44999 closed enhancement (invalid)

Proposed Enhancements to the Permalink Bar

Reported by: s3w47m88 Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.9.8
Component: Posts, Post Types Keywords: ux-feedback ui-feedback 2nd-opinion
Focuses: ui, administration 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.

This ticket is specifically proposing this Plugin we developed is rolled into the core: https://wordpress.org/plugins/hide-permalink-until-title-is-selected/

  • It hides the permalink bar until the user selects or hovers overs the Title. We found that users almost never edit their permalink, and when they do it's usually to correct a typo that was made in the Title as well.
  • It introduces a "View Page" button. Similar to the "Preview" button except that the Preview button shows the draft version of the page, not the live version. We found that 100% of dozens of clients we tested with had difficulty locating - or couldn't locate at all - a way to view the *published* version of their page. This is because there is no *button* to do this, and the only link on the link you can click is not in the Publish panel where other related buttons are located.
  • It also eliminates the need to click "Edit" to edit the slug. Removing one step for the user.

We're happy to hear feedback or apply revisions. We did what we thought was most sensible and least invasive.

Change History (5)

#1 @audrasjb
19 months ago

Hello and thanks for your ticket,

Just a small thought: I'm wondering such changes to the classic editor are still relevant since the new editor (G.) is going to be released with 5.0.

#2 @SergeyBiryukov
19 months ago

  • Component changed from General to Posts, Post Types
  • Focuses ui administration added

#3 @s3w47m88
19 months ago

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

@audrasjb sadly, that's a really good point. I wish I would have released this when I built it a year ago! LOL. Maybe this will be relevant for those who don't adopt Gutenberg?

#4 @netweb
19 months ago

  • Milestone Awaiting Review deleted

#5 @garrett-eclipse
18 months ago

Hi @s3w47m88 you can suggest this on the Classic Editor plugin for those who don't adopt Gutenberg, it's Github can be found here;
https://github.com/WordPress/classic-editor/issues

Note: See TracTickets for help on using tickets.