There is some discussion on the close reasons - trying to simplify them to the "rep 1" level of understanding.
There was a desire for a close reason of "... what [language | technology | project] should I [learn | read | do] do next ...", however, it was decided that this was not a new user friendly message.
What might work is if each of those message options were a drop down that could template into the custom reason text area - giving the flexibility desired but without having to retype the message each time and furthermore encouraging consistent close reasons.
Much of the comments have gone down the path of examining particular P.SE questions and what close reason those should be closed with. While that is valid different question it more suited to meta.programmers.SE - whether it should have its own off topic message or be one of the predefined not off topic messages is for that community, not stack echange as a whole.
The feature request presented here is that there are times where, in an attempt to make the close reason as appropriate as possible to the question I may find myself typing similar messages again and again with slight variations (swapping out "language", "technology", "project" or "learn" and "do") again and again to match the close reasons as specified in the not about on topic section of the help center.
The options that the community in question are considering are:
- A difficult to read close reason 2 of 6
- A generic off topic close reason about "what next" 4 of 6
- A rather wordy off topic close reason that enumerates all of the options 6 of 6
The idea and feature request yet remains (even if the specific issue of this close message has been resolved by going to a wordy one) - the ability to have a templated message (dropdowns) that populates the 'other' field to allow for a range of close reasons that have a closer fit to the question. This is something that can help guide close votes to have the common reasons that have enough variation to them that completely canned reasons do not.
Just as the specifics of close votes aren't something that MSO for different stack exchanges gets involved in, dwelling on that isn't helpful. The feature request is saying "you gave us some really nice tools that we are going to make use of, if we had this tool too, it would compliment that set nicely in a way that may give a better experience to people who have their questions
closed on hold."