8

Right now, we can use three custom off-topic reasons. This is what we have:

  • Theme or plugin recommendation requests are off-topic as they're rarely helpful to others. For more information, visit meta.

  • Programming questions not specific to WordPress are off-topic here, but can be asked on Stack Overflow.

  • Questions on problems with a specific host or provider are off-topic here. Please contact the appropriate support department instead.

We have to catch the old too localized here, so we need to change those pre-made reasons.

The last one is not common enough, or it can be grouped with other problems, for example.

Your suggestions?

2

New close reason are live. Discussed suggestions in chat and had to do some shuffling to fit under character limits and pack everything needed into three slots.

9

The close reason about programming questions is too narrow. How about this?

Questions about programming, HTML, CSS or JavaScript and not specific to WordPress are off-topic here, but can be asked on Stack Overflow.

  • We also have unspecific blogging/management and generic server config as not in scope. Maybe make close reason more generic and link to that for full details? ~ "Questions about generic concepts and technologies which are not specific to WordPress (even if they happen in its context), see [link]...". – Rarst Jun 29 '13 at 14:27
  • @Rarst Please add your own suggestions as separate answers. – fuxia Jun 29 '13 at 14:31
4

Questions with extremely narrow requirements, requiring hands-on involvement (hacks recovery) or access (code behind paywalls) are not a good fit for QA format and scope of the site.

This picks up "too localized" and bolts free-work/need-access to it to fit more stuff in 3 reason slots.

4

Recommendations for products (plugins, themes, books, hosting providers and other) were made out of scope of the site in line with community decision on meta.

Expands on recommendations, both more generic and mentions more specific things (so we don't get "but I asked for a book/hosting/puppy, not a plugin!" confusion).

  • Not so sure about the other. Every answer recommends something: a solution. – fuxia Jun 29 '13 at 16:29
  • @toscho as in "other products", not "other anything". – Rarst Jun 29 '13 at 16:31
  • Ah, missed that somehow. What about Give me all the links about X? – fuxia Jun 29 '13 at 16:33
  • @toscho I think depending on context "too broad" or "primarily opinion based" likely to cover that one. – Rarst Jun 29 '13 at 16:41
4

Our most common too localized questions were about syntax errors or themes and plugins with closed source. So I suggest a close reason for that:

Questions about syntax errors, hacked sites, or plugins and themes whose code is not accessible are off-topic because they will not help any future visitors. See How do I ask a good question?

  • Not sure if this isn't too narrow. On the other hand we could extend to "(...) and impossible to answer without public code/source". – kaiser Jun 29 '13 at 6:51
  • This sounds to me as "off-topic because without code". I think the more accurate way to formulate is "impossible to answer without code". Even question about no-source product can be useful and net good answers, if specific of code itself aren't involved. – Rarst Jun 29 '13 at 14:30
  • @Rarst & toscho: Live example. I'm not sure how to word a custom vote to close message. Would this proposal be "Questions about syntax errors or plugins and themes whose code is not accessible are off-topic because it's impossible to answer without code.? Maybe: "without the relevant portions of the code"? – brasofilo Jul 1 '13 at 17:10
2

Questions should be specific to WordPress within defined scope (merely happening in its context is insufficient). Might be better asked at other site of SE network.

Emphasis on "specific" (better than "not not specific" since mind tends to jumps over "not"s when reading). Not much space for multiple stacks recommendations so just link to list of stacks, filtered to technology.

2

This one is similar to @Rarst's proposal, but mixed with Stack Overflow text. Instead of explicitly declaring our discussion to make plugin/theme recommendations off-topic, simply link it inside "product".

Questions asking us to recommend a product (plugins, themes, books, hosting providers), tool, library or favorite off-site resource are out of scope of the site, as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .