There is considerable dispute about when questions about code should be closed. As far as I can see, this mostly applies to questions about HTML, CSS, or similar and not to questions about scripting graphic-design tools (correct me if I am wrong). Obviously it would be good to establish some clear guidelines for this and hence I am asking:
What is a good criterion (or set of criteria) for which code questions should be closed?
Answering and voting
Suggest one criterion (or set of criteria) per answer. Ideally, an answer comprises all relevant cases.
As I consider this a problem of previous discussions on this topic: Please try not to rely on examples too much. There is nothing wrong with using examples for the purpose of illustration of a criterion, but defining via examples is problematic: It leaves room for interpretation and requires that everybody is familiar with the example’s context and understands why you evaluate the example the way you do.
Indicate agreement and disagreement on answers by voting.
Food for thought
Could we base a criterion on whether the task in question can also be performed with “classical” design software?
Would it be reasonable to categorically exclude implementing interactive or conditional aspects, such as, user interactions or querying the platform, a database, or forms?
What kind of questions actually lead to problems as collected here? The main issue will probably be that we cannot evaluate answers to such questions.
Is it a reasonable to ban questions that ask for help with producing valid HTML, CSS, or whatever?
There is no rule that questions cannot be on-topic on multiple sites in the Stack Exchange network.