Return to Answer

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.

I don't know about other tags, but the c++ tag gets enough silly questions that we started to create a list of FAQs to quickly close the worst ones as dupes. So it seems there is incentive enough to create such content.

In fact, just linking to FAQ entries matching the tags might help quite a bit. I have found a few questions tagged c++ and operator-overloading that could all be closed with a link to the C++ operator overloading FAQ entry. It might be relatively easy to setup a system where when a low-rep user tries to submit a question tagged c++ and operator-overloading the system makes the user first having to look at the list of FAQ entries containing the tags c++-faq and operator-overloading. (Ideally there would be one item in that list, but with arbitrary tag combinations, it might be a list.)

This might be a simplification of what yi_H had in mind, but it has the advantage that there already is existing content, that the regulars in the tag have already shown commitment to produce content, and that new content can be automatically linked to by just looking at the tags. The rest, however, has to be provided by the SO team.