🌟 [EPIC] Visibility options for posts

[sushidave]

🌟 EPIC

As a user I would like to restrict the visibility of my posts.

• Public: Post is shown in the post feed, internal search results, and search engines. Requires [EPIC][Settings] Privacy Settings #286
• Registered: Post is shown in the post feed and internal search results.
• Not listed: Post can be accessed by anyone via URL, does not appear anywhere on the post feed and in search results. Can be used for private communication with other users and as a workaround for private messaging.
• Friends only: Only friends can see the post.
• Private: Post is visible to the post creator only.

And I would like to save posts as drafts:

• Draft: Post draft is visible to the post creator only. 🚀 [Feature] Draft status and auto-save feature for posts #3252

User Problem

1.) Currently all posts are Registered.

• Users cannot privately communicate in the network with other users.

2.) Currently posts can either be published or cancelled.

• Users cannot save their posts as drafts and work on them/publish them later.

Implementation

• 1. Add a privacy selection field to the post editing page.
• 2. Add a privacy selection field to the user settings to let the user chose his default.
• 3. Restrict access to private posts for other users. More detailed: Exclude privat posts from the post feed, from search query, unlogged requests, and search engines.
• 4. Restrict 'Registered' posts to registered users.
• 5. Make 'Public' post visible for unregistered users and search engines.
• 6. When coosing at least one category, the post is automatically public.

Design & Layout

Make a post visible for the public, when category is set:

Make a post visible just for connections, if no category is set:

Menu with more options (Draft and Registered):

Additional context

• Old already closed issue is 🚀 [Feature] Visibility of Contribution – not for Migration to Nitro? (second Alpha) #784 .
• @roschaefer startet a PR on this feat: post visibility can be set to "public" or "registered users" #3169 .
• A related issue is as well Scheduled Posts #288 .

[DennisHack]

Super!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Tirokk]

I would put the draft as well in the Visibility menu, or?
@alina-beck

[sushidave]

Let's have a look at how WordPress does it:

They offer a draft status and other visibility options, too. In the UI the two functions are seperated for a good reason: Draft and public are statuses of publication while the other ones restrict visibility for groups of people.

In the UI, WordPress shows the publication options in a fixed bar on top of the post and the visibility options in a scrollable sidebar:

1) Publication options:

There are sets of publication options (both offering a preview function, too):

a) For new posts or saved drafts:

By clicking the Publish... button a visibility selection menu appears:

b) For published posts:

2) Visibility options:

Apart from the top bar, visibility options can also be found in the post settings of the sidebar:

[sushidave]

The top bar and the sidebar of WordPress offer some advantages compared to the current post editing layout of HC. If the goal is to implement the credential free access to the network (wiki mode) as quickly as possible a part of the concept of WordPress could be used. Here is proposal for an intermediate solution for the UI:

1) Post editing page:

a) For new posts or saved drafts:

b) For published posts:

2) Visibility statuses

Imho, a visibility status private is not required if there is a draft publication status.

3) Display statuses

The draft status as well as the post visibility status should be shown on the post preview and on the post detail page and be visible for the appropriate users. To be defined in more detail.

4) Access denied message

An access denied message should be shown to users who try to access content with publication and/or visibility restrictions. To be defined in more detail.

[alina-beck]

I think it's good we're having this discussion but would like to point out that marking posts as visible for registered users vs public and saving posts as drafts are two very different features.

Right now I think the public mode has top priority and I would definitely not want to display options to users that have no effect. So let's maybe start with two visibility settings: public and registered users and then expand the list later, when we have features like friends and drafts?

[mattwr18]

I agree with @alina-beck ... let's keep it simple to start!

[alina-beck]

@mattwr18 you sound like @roschaefer 😄

[sushidave]

@alina-beck @mattwr18

Thanks for your comments.

Would you agree if we split this issue into two and reduce the statuses as follows:

1. Publication statuses: draft, published
2. Visibility status: for registered users, not listed

These are statuses that can be implemented independant from a "public mode".

After talking to @DennisHack about his points for the priority of the public mode I strongly recommend to set the "public mode" back in favour of enhancing the social network (increasing user satisfaction and motivation to donate) and put this issue here on hold. Let's discuss the next steps on Zoom.

[sushidave]

@alina-beck According to our today's chat I created #3252 for the draft status part, so this issue here can be used for the publication statuses only.