The number of questions I vote to close has dropped significantly since I became a moderator. I now try to only close the most obviously off topic questions, and generally let the community at large handle close votes. Please remember that this is a volunteer position, and we are all trying our best.
I stand by my closing of your most recent question.
How you could fix the original question
As written, your post is a solicitation for design ideas. This makes it both opinion based (judging which is best is purely subjective), as well as quite broad (there are nearly infinite possible solutions). I closed it for the latter reason, but the former would certainly be appropriate as well.
The format for this site is specific questions and answers. You did a good job including what you have tried so far, but asking how to make some UI attractive/responsive is not on topic, and is instead likely to lead to significant back-and-forth. If you wanted to ask something along the lines of how you could convert this menu structure to use SLDS, that could well be on topic. That is specific enough that one could post a clear answer and be confident it is correct, would help you, and would be useful for others in the coming years.
How you could fix this Meta post
Your original wording contained rude/abusive language, and your edit did remove some of that problem. However, your post still contains much content which is not fact based, assumes the worst, and adds nothing to a discussion whose end goal is to actually resolve any problem.
- Stating the closure is "meaningless" is not productive.
- It would be better to instead ask why the post was closed, or what changes could be made to get it reopened.
- Stating that "the moderator doesn't understand the question" is an (incorrect) assumption and throws unnecessary shade.
- Ordering "You really need to do something" doesn't fit with the general approach on Meta, where we try to seek consensus about the best path forward.
- Implying some sort of "abuse of power and/or gaming the system" is a bit nonsensical and again assumes the worst.
- We are volunteers
- We signed up to be moderators because we get a lot of value out of this community and want to keep it great.
- There is no system to game, I obtain no specific personal benefit from closing posts, other than looking out for the overall health of the exchange.
- I try to be as careful as possible about using these privileges.
- Pointing out specific questions and stating that they are "far broader, far more opinion based or just plain off topic" makes no attempt to move forward and resolve your situation, nor to understand the reasoning behind the system.
Why are those posts on-topic?
Each of the questions you linked to are/were relevant to a large number of developers. Aside from the exception handling post, your coloring of my questions as broad or opinion based is not correct.
(Why) Should I Use Lightning Apps?
In 2015, the lightning platform was not very mature, and despite its rollout and buzzword status, did not feel like the right tool for the job in most UI applications. The question boiled down to something very specific and objectively answerable:
What do Lightning Applications do better than VisualForce Pages? What types of problems are they worse at handling?
Ultimately, it was more about can/cannot than better/worse, but it was possible to answer concisely and objectively.
Why Are Data Silos Important in Unit Tests?
I found a shortcoming in the official documentation, and asked a specific question which can be addressed with objective arguments.
Why is it important to create our own data when we write unit tests?
Yes, it is somewhat broad, in that you could probably write entire dissertations on the topic. But as the answers demonstrated, it is possible to write a concise, relatively complete, high quality answer. Each of the other users who posted an answer there could be reasonably confident they had addressed my question in a satisfactory manner which would not require dozens of follow up questions.
Pokemon Catch - Generic Exception Handling In Apex
There was some back and forth on this one, and it is certainly true that you could close it for many of the same reasons. It comes back around to how widely applicable the question is. We strongly advise against something in our best practice guidelines, but at that time did not have a clear, concrete justification for why. So I asked a very specific question which can be addressed via objective arguments, measurements, and facts:
Is it ever acceptable (or even preferable) to catch a generic Exception in Apex? Are there repercussions to watch out for?
Is it opinion based? Yes, it is. But the key reasons it was reopened and remains open is that this question can be addressed via objective arguments and it is very broadly applicable (it affects most developers on a week in, week out basis).
How I handled a similar situation
If you read through the comments on that last post you mention, you may notice:
This question was reopend based on community votes and a topic in our meta.
This question was closed, and I also brought it up on Meta. And while it's true that I do call someone out specifically, the only subjective/negative thing I say about them is that they are clearly disgruntled. That is a far cry short of saying someone is power crazy, or that they are gaming or abusing the system, or that they don't understand the question. Those are character judgments which quite frankly feel hurtful and unfair.
Outside of my one subjective observation, I stated facts about what happened, explained why I thought the flag was incorrect, then asked the community if they agreed.
