October 30th, 2023
As we are not seeing anything that needs to be debated at this point in time. I am going to accept the answer I proposed to the community. Of course, this policy doesn't need to be permanent, and if the community believes it should be updated and changed, it is welcome to do so through regular community discussion.
Update October 20th, 2023
The answer below is a good-faith effort at combining the two most highly upvoted answers received during this exercise. I had several CMs review to make sure they thought it was sufficient.
Please take a look and decide if you find the answer satisfactory. If not, we can create a chatroom to discuss what changes we need to make to get it over the finish line.
This discussion period will stay open till October 27th, 2023. However, we can extend if necessary.
Update October 5th, 2023
Thank you to everyone who weighed in with answers or comments. We got a lot of good input. We have a few different upvoted answers that are categorically similar but bring up some good points.
To avoid any debates on this matter in the future and put it to rest the CM team will review what has been shared and craft an agreeable policy from these, and then share that with the community here.
You can expect to see that by October 20th at the latest, but we hope to have that completed earlier than that.
The Web Applications Stack Exchange site is in an interesting position regarding the topic of showing research has come up several times over the past years. As a community manager, I wanted to give the discussion a fresh start to help the community come to a consensus. However, if we can not reach a consensus as a community, I will discuss it with a few CMs to come to an agreement for a site policy to put it to rest.
To set the stage, I see two perspectives after reviewing past discussions on the matter:
Little to no research is required
Support of this viewpoint is under the premise that question asking on web apps is to seek help first and that imposing research requirements might discourage users from asking questions. Closing questions should be based on their lack of context and clarity, rather than a lack of research. They believe that not requiring research creates a welcoming environment, especially for new users, and allows for more active participation.
Demonstration of Research Efforts
On the other hand, requiring research argues that providing context about what has been tried and where the user is stuck is more beneficial than simply asking a question. This not only helps in a better understanding of a question but will also prevent duplication of efforts by the answerer. Showing research can make a question more engaging and relevant while giving it better odds of receiving a response and participation from the community. Questions that do not demonstrate research effort appropriately should then be considered for closure. However, it might encourage new askers not to ask due to the higher bar for participation.
Given the previous discussion on research in the web application community, I would like to pose the question to you all: What level of research needs to be demonstrated for a question to be acceptable?
Furthermore, should it become a requirement for users to show some level of research, like searching the help center of the web application in question before posting it? How best should that be demonstrated, and to what degree, if any, must it be established?
We will leave this open for community input for four weeks and stop considering feedback to the question on October 5th, 2023. After that point, if there is overwhelming support for one option, we will adopt that as policy. If there is not, the CM team will craft something sensible between all suggestions offered and existing network norms.