Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Comments on Should we modify the default (front) page for anonymous visitors?
Parent
Should we modify the default (front) page for anonymous visitors?
A complaint we've heard a lot is that when a community's front page has many questions that are not well-received, it deters visitors. (It also deters some people who are already here, I know.) This is not a good look:
I'm trying not to embarrass any individuals (though you can go to the obvious community and look). These posts are from several different people, not one.
Should we filter the question list for people who are not logged in? If so, should we also filter it for new users (to be defined), so they don't get a shock right after signup?
I don't think we can (with good performance) do something like "no more than one post meeting these criteria"; I think if we're going to filter things out of the logged-out view, we need to be able to evaluate each post on its own.
(I'll make my proposal an answer, so it will be on equal footing with others' proposals.)
I suggest we show questions in the list differently depending on their rating. Good questions are show as they are now. …
2y ago
How about having another tab (next to "Activity", "Age", "Score", "Random") in the category listing called "Positive", t …
2y ago
As a starting point for discussion, I suggest that the logged-out view not show any posts that are closed or have a scor …
2y ago
I agree that such a front page looks bad. I also agree with a comment that trying to simply hide poorly received post …
2y ago
Maybe the ordering of the default tab should be more sophisticated, both for logged-out and logged-in users, new or othe …
2y ago
Post
As a starting point for discussion, I suggest that the logged-out view not show any posts that are closed or have a score worse than that of +0/-1. We're not trying to pretend that downvotes never happen, just mitigate their aggregate effect.
I'm proposing this for the default view only. Someone who sorts by age or does a search or chooses a tag would see everything. A direct link to a post would still always work. This is about first impressions.
I also suggest that we keep some filtering in place at least temporarily after the visitor creates an account. I have several ideas here, but none of them really baked. We could tie lifting it to an ability, or account age, or tour completion (maybe we add a "show me everything" button to the end of the tour?), or user activity (maybe lift it when you post for the first time), or...?
I would also like us to add durable, user-defined filters, an idea that was illustrated in Matt's design mockup sometime back. I'm planning to make a separate feature request about that. If we had that, then we could give new users a default filter, its presence would be visible, and they could turn it off whenever they want by adjusting the filter.
2 comment threads