After some thought.. here's my take....
What is "graphic design" if not problem solving in general??
To work or play as a designer you must have at least an entry level ability to solve problems. And that has nothing to do with experience levels. Even the youngest, newest, designer must be able to solve problems for themselves the same way they must understand measurement systems. If you don't know what an inch or pica or millimeter is, you can't be a designer. If you can't actively try and solve problems you encounter, you can't be a designer.
Lazy questions which show an inability to Google search or use the application help files do one clear thing to me... they show a complete lack of problem-solving abilities and a desire to have others do your work for you. Is that why everyone's here?
Bad questions are bad questions. MOST of the software or tech-support questions I see here are these lazy questions and that has always been my primary issue with them on the site.
On a personal level, I'd have no problem answering anything and everything someone asked of me. However, on a StackExchange site, if you can't even be bothered to spend 15 minutes trying to solve your own issue, you shouldn't be posting a question.
Looking at the proposal, all of the sample questions could easily be answered with 15 minutes of research and Google. None of those questions require a deep level understanding of the application or expert knowledge. The answers are easily found and steps or procedures clearly explained in application help files.
So... my inclination is the proposal would be, as others have stated, a "garbage bin" for lack-of-effort, easily answered, questions and ultimately no more valuable than any web site which currently displays the answers (of which there are many).
After some discussion in chat about on and off topic things I've come to some further realizations.
I do not think all tech support here is bad.
Much of it can be, but there are very valuable tech support issues which we should handle here. The difference primarily is when answers would provide technical knowledge as opposed to application troubleshooting.
This question stirred a discussion:
How to get consistent color in Photoshop when using the [Print Screen] command?
Now, is that tech support and off topic or on topic?
I feel it's on topic for some clear reasons:
- Any answers would provide technical knowledge about how to calibrate a monitor or set color settings within Photoshop.
- Any answers would provide information which would be valuable to hundreds of visitors, even if they were somewhat experienced.
- Any answers would not need to be specific to a users hardware or configuration.
That being posted I agree that it is a tech support question. So I can see why it would possibly get close votes. But when a question would provide knowledge every designer may find valuable, there's still a lot of merit in the tech support question.
These types of tech support questions belong here and should be allowed to stay. The intent is to further knowledge needed in the graphic design field.
The Grey area
This question falls between what's above and below:
Why is Illustrator not making sublayers for each new path?
Is this tech support? To me, yes. However, it's not really asking for application support. It's asking more about workflow support. Yes, the answer is simple, straight-forward, and merely takes some knowledge of the application settings. However, if you don't know what you don't know, where else can someone ask this? Why not allow some of these questions to remain. This question, although basic, clearly shows some thought behind it.
In fact I've even purposefully posted such rudimentary questions to have answers available: How do I apply a gradient across multiple objects in Illustrator?
This type of question is admittedly a very, very, very large grey area and I don't begin to try and define these with definitive boundaries.
Would they fit with the proposal? Probably, yes. But only if they show effort, are clear, and not duplicates, in which case they also fit here, don't they?
The Garbage Bin
By comparison, these closed questions are rightly closed:
Error opening EPS in GIMP 2.8
https://graphicdesign.stackexchange.com/questions/53321/mac-truetye-font-defaults-to-bold-style
https://graphicdesign.stackexchange.com/questions/46728/panel-gone-too-big-in-workspace
Why? Because these deal with error messages or hardware issues which are specific to the user's environment. Application error messages don't always elude to tech support issues, but they can be a large contributing factor for me. Error messages can elude to workflow problems which are not related to the host systems. Each question is unique and depending upon error messages, and my application understanding, I judge what i feel is accordingly.
So in summary, I feel this proposal is geared to handling these topics we are closing (the grey area or garbage bin). And seeing that, I can't understand how these types of off-topic tech support questions would make a valuable stack in itself.
I do think, at times, questions which fall under technical knowledge get unfair close votes. And I'm not claiming that I'm perfect by any means. This post is merely seeking to elaborate upon what I feel is on and off-topic and why a proposal for our closed questions may not be warranted.