Make WordPress Core

Opened 14 years ago

Last modified 10 days ago

#18400 new task (blessed)

Suggested label change for "Stick this post to the front page"

Reported by: designsimply's profile designsimply Owned by:
Milestone: 6.8 Priority: normal
Severity: normal Version:
Component: Posts, Post Types Keywords: has-patch needs-copy-review
Focuses: administration, ui-copy Cc:

Description

In the Publish meta box, it would be more clear to say "Stick this post to the top of the front page" compared to saying "Stick this post to the front page".

Attachments (4)

18400.diff (1.5 KB) - added by designsimply 14 years ago.
18400.1.diff (1.5 KB) - added by designsimply 13 years ago.
18400.2.diff (1.6 KB) - added by danielbachhuber 11 years ago.
Refresh patch against trunk
18400.3.diff (1.6 KB) - added by kellenmace 7 years ago.
Use "Stick this post to the posts page" wording

Download all attachments as: .zip

Change History (37)

@designsimply
14 years ago

#1 @ocean90
14 years ago

I prefer the same label as we use in Quick Edit "Make this post sticky". Sticky posts aren't always on front page, even less on top.

Last edited 14 years ago by ocean90 (previous) (diff)

#2 @danielbachhuber
14 years ago

  • Cc d@… added

#3 @designsimply
13 years ago

  • Keywords ui-feedback removed

Thanks. Re-patched with 18400.1.diff.

#4 @nacin
13 years ago

  • Keywords ux-feedback added

#5 @SergeyBiryukov
12 years ago

  • Component changed from UI to Text Changes

@danielbachhuber
11 years ago

Refresh patch against trunk

#6 @danielbachhuber
11 years ago

  • Keywords commit added; ux-feedback removed
  • Milestone changed from Awaiting Review to 3.9

This ticket was mentioned in IRC in #wordpress-dev by helen. View the logs.


11 years ago

#8 follow-up: @nacin
11 years ago

  • Keywords 2nd-opinion added; commit removed

The problem with "Make this post sticky" is it doesn't describe what "sticky" means. I understand the brevity in Quick Edit, but it should probably be descriptive when editing a post. Otherwise it lacks any meaning for the user.

"Stick this post to the front page" seems OK to me as-is. It is a good balance of descriptiveness and clarity. "Stick this post to the top of the front page" feels less accurate as you can have multiple sticky posts (it also causes awkward text wrapping in English). Also, sticky posts *are* always on the front page, so that part isn't inaccurate either. Even if posts_per_page is 10, if you have 11 sticky posts, they'll all display.

#9 @nacin
11 years ago

designsimply, I'm guessing this came out of seeing some feedback from users, though it was pretty easy for ocean90 to pivot things to another string, so I'm not sure :-)

I wouldn't mind considering other variants; I'm just not sure anything so far proposed is any better. While some users might be less confused with "to the top", other users might be more confused.

#10 @nacin
11 years ago

  • Milestone changed from 3.9 to Future Release

Getting this out of 3.9; we can bring it back in if there is a consensus for changing it.

#11 in reply to: ↑ 8 @celloexpressions
11 years ago

Replying to nacin:

Also, sticky posts *are* always on the front page, so that part isn't inaccurate either. Even if posts_per_page is 10, if you have 11 sticky posts, they'll all display.

I think the issue here is that the user may have a static front page, in which case "Stick this post to the front page" is inaccurate. Themes also do special things with sticky posts sometimes (Twenty Fourteen, even), so we should keep it as generic as possible. I would call that an edge case, but the default theme does it out-of-the-box (where, incidentally, the "front page" statement is valid). In fact the best solution might be to lose some clarity and go with "Make this post sticky", since "sticky" can mean different things in different themes (although the general idea is almost always the same).

#12 @designsimply
11 years ago

designsimply, I'm guessing this came out of seeing some feedback from users

Correct.

I think the issue here is that the user may have a static front page, in which case "Stick this post to the front page" is inaccurate.

Correct again.

#13 @helen
10 years ago

#30248 was marked as a duplicate.

#14 @philiparthurmoore
10 years ago

In #30248 I've proposed to change "front" to "home", since front is incorrect. At a minimum I'd advocate for this change because it's in line with how themes treat the terms "home" and "front". As has been mentioned above, front as it's used now is incorrect when a static front page is used. Consistency here with the Customizer and other WordPress admin areas would be nice.

#15 @chriscct7
9 years ago

  • Focuses administration added
  • Severity changed from minor to normal

#16 @kellenmace
7 years ago

I'm proposing we change this wording on the single post edit screen from "Stick this post to the front page" to "Stick this post to the posts page".

Reasons why:

  1. When users are using a static front page and a different page for their posts, the current "Stick this post to the front page" wording is inaccurate and misleading.
  2. The "front" and "home" terms can be confusing to end users, as noted by others on this ticket. We can avoid that confusion altogether by referring to it as the "posts page" instead.
  3. Using "posts page" makes this label consistent with the "— Posts Page" label that is applied to that page on the Pages edit.php screen.

https://cldup.com/KMnnBxaFbB-300x300.png

@kellenmace
7 years ago

Use "Stick this post to the posts page" wording

#18 @garrett-eclipse
5 years ago

  • Component changed from Text Changes to Posts, Post Types
  • Focuses ui-copy added

#19 @Presskopp
7 months ago

I just came across this 'issue' explaining a customer what he needs to do and I find the solution @kellenmace offered very helpful (18400.3.diff). The arguments have been made, "Stick this post to the front page" can be inaccurate and misleading. +1 from me, and it's never too late.

This ticket was mentioned in Slack in #core by presskopp. View the logs.


6 months ago

This ticket was mentioned in Slack in #core by presskopp. View the logs.


6 months ago

#22 follow-up: @desrosj
6 months ago

Before moving forward with any text changes, I would like to see someone break down all of the places that the "sticky" concept is now surfaced in the UI of the block and site editors. The last suggestion was 7 years ago, which was a year before the block editor shipped in Core.

The Query Loop block and maybe the posts list block likely have new contexts where sticky is presented to users, so we should consider those here as well.

#23 in reply to: ↑ 22 @Presskopp
6 months ago

Replying to desrosj:

I think you're reaching too far. This ticket is exclusively about clarifying the wording in connection with the front page. There are only 2 strings that this concerns.

The second one is:

Blog posts can be “stickied”, a feature that places them at the top of the front page of posts, keeping it there until new sticky posts are published.

As you can see it speaks about the "front page of posts".

Another string is mentioning

... making it stay at the top of your blog ...

#24 @sabernhardt
6 months ago

  • Keywords needs-refresh added
  • Milestone changed from Future Release to 6.7

GB62782 just added "Pin this post to the top of the blog" as help text for the Sticky block editor control (though GB63386 notes that the control is more difficult to find now). It probably would be good to coordinate both, so that the Classic Editor uses the same string (with any improvements) as its label in the next release, too.

Other translations:

  • strings including "stick" (note that some of those strings relate to CSS sticky positioning, and GB63999 just changed the "Blog posts can be “stickied”..." text for the Query Loop block to "Sticky posts always appear first, regardless of their publish date.")
  • additional strings in admin

This ticket was mentioned in PR #7388 on WordPress/wordpress-develop by @rockykev2b.


5 months ago
#25

  • Keywords needs-refresh removed

This ticket was mentioned in Slack in #core by chaion07. View the logs.


5 months ago

#27 @chaion07
5 months ago

  • Keywords dev-feedback added

Thanks @designsimply for reporting this. We reviewed this Ticket during a recent bug-scrub session. Here's the summary of the feedback received:

  1. We believe the need for dev-feedback before changing the sticky text for metabox.
  2. We also need to ping Stephen to check if this Ticket falls in their radar for 6.7 or not.

Thanks.

Props to @mukesh27

Cheers!

#28 @sabernhardt
5 months ago

  • Keywords needs-copy-review added; 2nd-opinion dev-feedback removed

I marked the ticket for copy review.

The new Gutenberg wording is still "Pin this post to the top of the blog" since GB62782, and I would prefer consistency instead of creating two new strings in 6.7.

#29 @peterwilsoncc
5 months ago

  • Type changed from enhancement to task (blessed)

I've converted this to a task. As the two editors are using different strings for the same thing, it would be good to unify them to avoid additional load on translators.

#30 @Presskopp
5 months ago

I don't think "Pin this post to the top of the blog" is the best choice, because, as mentioned above, a sticky post can be shown anywhere posts are listed which not necessarily is "the blog".

#31 @desrosj
4 months ago

  • Milestone changed from 6.7 to 6.8

This still needs more discussion. 6.7 RC1 is due out any moment. Punting to 6.8.

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


10 days ago

#33 @audrasjb
10 days ago

As per today's bug scrub: it would be better to see a more universal wording here: maybe something as simple as "Stick this post" or "Make this post sticky".

The current Gutenberg label is "Pin this post to the top of the blog"
Which is, I think, incorrect (the "top of the blog part").

Also, we should stay with stick/sticky because that's used everywhere in our User Docs.
This should be addressed on both Core and Gutenberg side.

Note: See TracTickets for help on using tickets.