Opened 21 months ago

Last modified 4 months ago

#18418 new enhancement

Clarifying what "Private" means in post visibility

Reported by: danielbachhuber Owned by: danielbachhuber
Priority: normal Milestone: Future Release
Component: Text Changes Version:
Severity: minor Keywords: has-patch ui-focus
Cc:

Description

When choosing visibility for a single post, “Private” doesn’t make much sense as a label and requires extra explanation as to whom the post will be private to.

Context: At the Newbie Workshop during WCSF 2011, we had to talk brand new users through the myriad of features offered in WordPress. "Private" as a post visibility required extra explanation and even I realized I didn't know what it did.

"Private" should be replaced with text like "Private to blog editors and administrators"

Attachments (1)

privatetext.18418.1.patch (2.6 KB) - added by danielbachhuber 21 months ago.
Replace "Private" text with "Private to blog editors and administrators"

Download all attachments as: .zip

Change History (10)

  • Type changed from defect (bug) to enhancement

Replace "Private" text with "Private to blog editors and administrators"

  • Milestone changed from Awaiting Review to 3.3
  • Keywords has-patch added

Maybe just “Private to editors and administrators”, without “blog”?

That makes sense to me too

I'm not sure that adding this longer string actually improves this much.

Private posts are confusing in general and we don't support them very well - I think we need to step back and decide whether or not we want to keep them at all and how they should be presented from a UX perspective.

  • Component changed from General to UI

Agree with westi. I don't want that long of a string cluttering up things. Also @danilbachhuber, you were doing the newbie workshop using wordpress.com, which has an entirely additional level of confusion because of the existence of private blogs there. I would rather .org support a fully private blog than individual private posts, as realistically you could just save posts as draft in a lot of the use cases for that feature.

Version 0, edited 21 months ago by jane (next)
  • Milestone changed from 3.3 to Future Release

Punting enhancements from 3.3.

  • Component changed from UI to Text Changes
  • Keywords ui-focus added; ux-feedback removed
Note: See TracTickets for help on using tickets.