Create or allow for a community-wiki editable home page per tag. One where we could place essentially the tag-specific FAQ and other tag-specific links.
Further to Brad's - the most common dups, too (I haven't added links, but you get the idea):
- Frequent C# Questions
- What are the correct version numbers ;-p
- Parameter passing "by ref" vs "by type", and "value type" vs "reference type"
foreachloop only sees the last value
- When to use
- Why should I use properties?
This is now done.
Every tag has a tag info page, for example: faq if you have more than 100 upvotes on non-wiki answers with that tag you are entitled to edit the wiki section.
Since I just posted PostType = Wiki, Wiki + Reputation can it be done? I would like to explain how I would see these features tie together.
When you click on a tag, it's really nice to have a list of questions in the sort order you choose. I do not feel a different look and feel for each tag home page would be a good idea. I also do not think that we should dictate sort orders or filtering to users.
However, I think we have enough space (6/8 lines) that can show up first (where the ad is now) and presents common / highly voted, wiki topics on the tag.
So, for example, clicking on C# you would have a little box:
- Getting started with C#
- Common issues with C#
- Hidden feature of C#
Also I would make the tag front page Google indexable, so when people google
C# Stack Overflow shows up first.
A very simple way to implement this would be to allow users with a gold badge in a tag to pin up to 6 questions to a tag.
I think that these types of pages would become stable fairly quickly, so a good FAQ could be compiled for all of the major tags. Also, if something controversial is added, then it needs to be stated as such or removed outright. Voting is probably the answer for dealing with this.
I also completely agree with Jon Skeet's idea (from user voice) of having a reputation barrier per tag. In other words, you must have earned 1000 reputation in
Java tagged questions in order to contribute to that FAQ.
This request appears stagnant, yet I think it would be very useful. The issue just came up (well, I helped it come up): see comments at How to force overriding a method in a descendant, without having an abstract base class?.
If nobody can think of a really good reason to not do this, I think I might just get started.
I propose a CW "question" named "C# Frequently Asked Questions (FAQ)" with "header" information, like related tags, index of other FAQ articles, etc. Then subsequent CW "questions" like "C# FAQ - Covariance and Contravariance in C# (Variance)".
I think for this to work, there would need to be an "authority" or an authoratative group and I don't think that can be managed within the current system. Possibly you could have moderator specific tags like we do on meta, but that would create a lot of overhead work for the moderators, and I'm certain there are tags where none of the moderators are experts and therefore wouldn't know what should be made part of the faq.
In the end, perhaps a feature where once a user has earned silver or gold in a tag would allow them to vote on adding/removing questions from that tags faq might work, but I think there's probably a lot of design that would have to go into it. But until some new feature is implemented to address, I believe current system cannot make this work well enough for it to be beneficial. Too many users are able to modify tags and/or edit questions and answers without need for "community support", and therefore, too often I think debates and/or edit wars would result.
I started this already for Python here. I don't know if this is what you had in mind, but I suppose starting is the only way for things to happen
I'm totally in favour of this. There are some questions that pop up all the time, so often that marking them as dupes becomes really, really cumbersome. Also, it's hard to spot the "best" question among dozens when looking for dupes. We really need reference answers (covering all possibilities and edge cases) to some of those questions.