Zachary says pretty much everything I would comment on this matter. But I will try to exemplify what SSE is meant to be, and why it differs significantly from traditional "forum" sites like Community.
So I recently bought a new car. And a new phone. And why is this relevant? You see, the car comes with some new fancy tech; wireless charging. For this to work, it requires that your phone supports this feature - any normal battery won't just be recharged with this technology.
So I find a wireless charging kit for my phone, and now went online to investigate whether this kit was compatible with the car. A few searches later, this is the forum answer I end up with.
Read through this, and see if you can determine the answers to the following questions:
- Can the iPhone 7 be made to fit in the BMW 4 series? (which is discussed in the thread)
- Does the Mophie induction kit for iPhone work in the BMW?
- Will the iPhone 7 including the Mophie kit fit in the center console?
- There's 2 pages worth of "posts" on this thread. How many of the posts add relevant information to the subject?
Now you can read through this if you like, or you can entirely skip it as irrelevant. I just wanted to pull out an example which is very real to me, and I was really annoyed that this seemingly simple information I was looking for, was so hard to dig out.
So what is SSE?
Well it's different. The Stack Exchange sites - not just ours - to put it broadly, aim to be "the first and last stop on your search journey". In the ideal situation, they should fill up with all the questions people have on a particular subject. And to go with that; ideally there would be at least 1 valid answer for each and every one of them. Preferably a few, if the answer isn't clearly black & white, but has nuances.
And now we're getting to the core of this issue. "What questions?". See the thing is, not all questions are good - in the sense of "good" being something that achieves our goal. To be visible on searches, to provide answers. On our site, these questions typically (not always) take a form along one of these lines:
- Upgrade troubles. Upgrading from version X to Y, something went wrong, maybe user error, maybe system error, maybe just simple oversight
- "What am I missing?" - including it's variants; "I did everything right and still it fails", and so on.
- The "ongoing situation". Where OP is typically in the process of debugging something, and via community comments and so on advances the story, edits and updates as the situation evolves.
There are more, but I believe the above to be some of the main types of posts that we end up closing on the site.
So should we close these and send them to Community?
No. First of all, we are not really a "Policy Driven" site. We do have several community guidelines, but any action the moderator team takes is always on a case by case basis. And forget about moderation for a minute - because we're technically here to deal with flags. Moderator attention flags. The community is supposed to do the heavy lifting in so far as what content the community wants.
Asking a question - such as this one - is really an indication of a lack of understanding of this basic fact. That posts like these, and all posts, should be considered part of the joint community effort that SSE really is - and the fact that we have "a lot of these posts" that have been put on hold is a sign of a healthy community effort. It doesn't indicate a problem.
This is an important point, so I'll repeat it. Having posts put on hold (which is not the same as closed, locked or even deleted - something moderators can do) does not indicate a problem. In many cases, OP got their issue resolved. And then it was deemed, the Q and A was not beneficial to the community at large, as the case was unique (for example) or it was resolved in a manner that would be unlikely to help anyone in the future.
These posts are not gone. They're still here, and part of our knowledge base.
So what then?
Just carry on :-) The community is expected and requested to continue helping us make the greatest Sitecore Q&A site in the world. And we do this by asking good questions, giving them good answers and actively participating in the meta around these questions. This is not just upvotes and answer markings, but also post edits, votes to close for content that didn't really help and so on.
And as Zach rightly points out; this is a lot of work. Far more than the mod team can handle on their own. And as mentioned, that's not really what we're here for.