I'd say there are several important topics to cover when writing a guide on how to ask good questions.
The author of a question should always first search the web for an answer. I have seen too many situations on Hashnode where I could just quote the first google result as an answer, or link to a question which was asked just a few hours earlier. For me, as a person who mostly writes answers, these kind of questions are rather annoying and cause an internal conflict between wanting to help and just posting a lmgtfy link.
A good question should always start with a summary. In one short sentence. That should be the subject / heading. The question body should contain relevant information, but still be brief. I don't want to read an epic just to understand a problem. If there is a problem in code, the OP should create a minimum reproducible example. Bonus for embedding it in an online sandbox which we can run. If it's a discussion about techy stuff, links to relevant sites can make our life easier. If the OP needs help with a project, they should explain their situation, because most of the time, the answer depends™ on that.
In addition to that, imho the tone of the question and any further communication is very important. By helping people and writing answers, we donate our precious life-time to the OP. I am not paid to help anyone, so the least I want is a friendly tone. Of course, this should always be a mutual gesture.
In that sense, I feel like this very question is a positive example. It has a one-sentence summary as subject and a brief, friendly description of the situation and problem as the body. 👍
I sometimes see people write a question, but in the body ask for something else or even a few additional, unrelated things. For me, a good question is just one topic, sticking to the subject line, which is the summary. If the OP wants details on different parts, that's ok.
When asking a question, it's often not needed that there are >10 answers. Questions which require in-depth knowledge are welcome, and they might only receive one or two answers. However, imho, a good question which best fits the context of Hashnode, is a question which is simple, broad and asks for an opinion. Everyone has an opinion, and the simpler the question, the more replies it will get. Simple, personal questions usually yield many high-quality answers.
A good factor to get answers is also to gamify a question. Make it rewarding to answer.
After the question is released, the OP should be responsive. By replying to an answer, a discussion may spawn which piques the interest of more people and may lead to some good information exchange instead of just keeping all question-repliers to themselves. Also, writing just a sentence as a reply will be appreciated by the answer author and it's likely that they will answer more of the OP's questions.