This has been a pretty interesting conversation on Slack regarding this. There is a defined reason why we thought about going in this direction. Perhaps the use of the tag as defined was not the best suited.
To explain a little further, Cassidy and I spent a little time looking at the salesforce.stackexchange.com site last night. They started kind of like our site did. Grassroots by the community, adopted by the Salesforce corporate, and then turned into a pretty large Q&A site that attracts users of all levels. Marketers, Users, beginner dev, advanced devs.. It spans the gambit.
This fell in line with a thought going through my head of, how do we entice marketers, users, etc to use the site as well. The types of questions are very hard, some very specific, mostly all technical. What happens it the normal marketer comes in? Would they be intimidated by such highlevel questions and decide not to ask? Would the community be so elite (no offense intended here, just making an example) that they would immediately VTC easy topics.
This got me wondering what would happen. So this is a beta. And I tossed 4 softball questions out into the open. Two of them have actually had really good responses thus far. This is a Public Beta, thought process was, let's try it out and see how the community reacts.
But our reasoning didn't stop there.
We're looking ahead to the
Documentation feature of Stack Exchange and realizing there's a place for a large number of our questions, including these easy ones. Once the
Documentation feature is open, we would migrate these types of questions to the Documentation feature of Stack Exchange for this site.
So, after some good conversation, we changed the tags to documentation on those questions to highlight the need to move them once the
Documentation feature is available to us.
Thanks for starting this meta topic though. I invite others to chime in.