#55947 closed enhancement (fixed)
Permalinks screen, add guiding introduction to structure selection.
| Reported by: | kebbet | Owned by: | SergeyBiryukov |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.1 |
| Component: | Permalinks | Version: | |
| Severity: | normal | Keywords: | has-patch has-screenshots needs-copy-review needs-user-docs |
| Cc: | Focuses: | ui, administration, ui-copy |
Description
Enhancement-suggestion to add a guiding paragraph below the heading ”Common Settings”. Suggested phrasing:
Select the permalink structure for your website. A structure that includes the post name makes sharing links to others more understandable.
This is a breakout from #55498 and is partly related to #55557 which all focus on enhancing the Permalink-screen.
Attachments (6)
Change History (23)
#4
@
4 years ago
As per the previous discussion ref
https://github.com/WordPress/wordpress-develop/pull/2557#discussion_r847052998
The short guiding paragraph would be nice from my point of view.
#5
@
4 years ago
- Keywords needs-refresh added
Hi there!
Thanks for the ticket and patch.
Can you please remove the single space before _e in you 55947-permalink-guidence.diff patch because right now it has two spaces before it?
#6
@
4 years ago
- Keywords needs-refresh removed
Thanks for noticing @mukesh27! New patch is on its way.
55947-permalink-guidence-v2.diff removes the extra single space before _e
#7
@
4 years ago
- Keywords needs-copy-review needs-testing added
Steps to Test Patch
- Navigate to
Settings > Permalinks. - Observe the added paragraph between the heading
Common Settingsand the structure selection form below.
#9
@
4 years ago
Attached a mobile screenshot of 55947-permalink-guidence-v2.diff to show there are no issues on smaller screens.
Select the permalink structure for your website. A structure that includes the post name makes sharing links to others more understandable.
- The second sentence means that sharing links is more understandable, but it is the link itself that is easier to understand.
- It may be useful to change "post name" to
<code>%postname%</code>so the user knows exactly what to use. This would mean changing from_e()to something like:
printf( /* translators: %s: the %postname% tag. */ __( '... includes the %s tag ...' ), '<code>%postname%</code>' );
- The post name can also help with SEO.
If you agree with the above, what about this variation?
Select the permalink structure for your website. Including the
%postname%tag makes links easy to understand, and can help your posts rank higher in search engines.`
This ticket was mentioned in PR #2947 on WordPress/wordpress-develop by kebbet.
4 years ago
#10
Trac ticket:
#11
@
4 years ago
Thanks for reviewing and the feedback. I do agree on all points, a new patch is attached to the ticket. The linked PR at Github was made to make sure tests pass.
#13
@
4 years ago
Linked PR (https://github.com/WordPress/wordpress-develop/pull/2947) is now updated after [53706] was merged to trunk.
SergeyBiryukov commented on PR #2947:
4 years ago
#16
Thanks for the PR! Merged in r53711.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Ping @sabernhardt