I hear your frustration and agree that some of us may be a bit too aggressive with the votes to close.
However, I also agree with the sentiments that Michael Lai expressed—especially the notion that this is a multi-disciplenary field. I don't believe it's immediately obvious to uninitiated users what exactly "user experience" entails and how it applies to this site.
Most of what I've seen closed recently are question that address the following out-of-scope topics:
- Product support—"Well, I'm a user, and I'm having trouble with this software"
- Site reviews—"These guys know their stuff, so I'll just get their feedback on my site"
- Attempts to collect survey responses—"They're here to help, so surely they'll take my survey"
- Tool, technologies, or software recommendations—"I need to know what the best tool is for this task / Is there a framework for
- Various other issues that have tangential connections to a user—"User experience... well my problem does affect a user"
My understanding of the proper workflow:
I cast a VTC when I believe a question to be off topic, but I'm always sure to leave a comment (or see that someone has already) with advice on how the question could be made better. I do this immediately because it's fairly common for new users to never be heard from again after their initial post, and I'd rather not let the question settle without addressing it with the appropriate close reason. If the question does get closed, and the user edits, we'll surely see it in the reopen queue (our queues seem to be pretty actively monitored).
Additionally, it's a relatively new field1, which I think may lend itself to a bit more misunderstanding of its scope and what it offers.
So yes, a lot of votes to close, but it's still kind of a niche profession. It's often hard for non-UX-focused people to write a good question when they don't even know what they're trying to ask in the first place. Hence, many questions get posted that are too broad or opinion based.
Regarding the particular question you highlighted: I voted to close that, as I felt that it's only tangentially related to user experience. It reads as more of a product development- or project management-flavored question. I believe there may be a small taste of UX meat to it (e.g. creating pages with consistent layouts will provide the user with a sense of "stability," allowing them to quickly create expectations) ~but~ that did not seem to be what OP was seeking.
"...have UI components that are being used repeatedly..."
"...any good approaches/frameworks that I can use..."
"...only redesign 1 and use it as a template for other 3..."
"...mobile app is a native android app. We will be planning for iOS version later..."
Sounded more implementation- or development-driven.
1: Certainly this field of study has existed in some form for quite some time, but as it applies to interaction with modern technologies, it's still fairly new.