When deciding on close reasons, the community upvoted Implementation QuestionImplementation Question to the top. And as the answer was written then, I agree to it. Which css rule to use or which software to buy, is surely off topic. But OP also had doubts on the title, which is mentioned several times in the post.
I feel that over time the close reason "Implementation Question" have slipped to be interpreted to something that could be used in every implementation scenario, remotely. I dislike this shift toward an academic approach of User Experience where "the true meaning of" is more important and valid than "how can we overcome the problem of" questions.
To me User Experience is worth nothing if it's not implemented. In my work I implement User Experience as much as possible, and I take the knowledge from here into the real world. I thought this was the original idea behind UX.SE. I'm afraid where slipping away from that. Is it just me, or do you feel the same? What do you want UX to be?